API Questions

An Entity refers to an individual or business whose identity is verified through KYC before any transactions can be made.

Both individual and business entities are supported for KYC and onboarding.

Status values include: not_started, initiated, reviewing, approved, rejected. Use webhook events or polling to track progress.

Call POST /transfers/simulate with the source, destination, currency, and amount. You’ll receive a breakdown of fees and estimated final amount.

Use POST /transfers/execute with the required parameters. Be sure to simulate beforehand to confirm fees.

This allows pre-funding a centralized wallet which is then used to process future transactions faster and cheaper.

Call GET /payments/balance to get a deposit address. Transfer funds and then call POST /payments/deposit with the transaction hash and signature.

Use the same GET /payments/balance endpoint to view your available funds and wallet info.

Call PUT /utility/webhook with your webhook URL to receive event notifications

We currently support webhook events for: kyc.transitioned, transfers.status, and webhook.updated.

Every webhook payload includes a z-webhook-signature header. Verify it using HMAC-SHA256 with your x-api-token.

Yes, webhooks are retried up to 3 times with exponential backoff for all non-2xx responses. Ensure your endpoint returns 200 to acknowledge.