Build cross-border financial services into your product

One API key, one signing scheme, one idempotency contract. Accounts and KYC, cross-border remittances, QR payments, virtual and physical cards, stablecoin accounts and wealth products: 6 products with 149 endpoints under a shared contract.

Make your first call in 5 minutes Signature Debugger Download Postman Collection

Start here

Account CenterThe platform layer shared by all products: tokens and signing, merchant accounts and funding, member registration, KYC, webhooks, sandbox, statements and reports. · 47 endpoints POST/connect/tokenGET/merchantGET/membersGET/kyc View all 47 →

Choose your products

Global AccountCross-border remittances: corridors and currencies, payee registration, quotes, orders, supplementary information and reconfirmation, plus merchant currency conversions for funding. · 25 endpoints GET/remit/corridorsGET/remit/payee-form-schemaGET/remit/products View all 25 →

Global AcquiringQR payments: a member scans a merchant QR code; we debit the member’s crypto-asset balance and our payment provider pays the equivalent fiat amount to the recipient merchant. · 7 endpoints GET/qrpay/orders/{id} View all 7 →

Card IssuanceThe complete lifecycle of virtual and physical cards: products and BINs, issuance, top-ups, withdrawals, spending controls, secure card details, closure and replacement. · 42 endpoints GET/cards/productsPOST/cards/applicationsGET/cards View all 42 →

Stablecoin AccountHold and move digital assets: balances, deposit reporting, on-chain withdrawals and address books, transaction history, internal conversions and transfers. · 18 endpoints GET/balancesGET/transactionsGET/deposits View all 18 →

WealthFlexible and fixed-term products: products and rates, subscriptions, redemptions, interest accrual and distribution, rollovers and interest settlement with merchants. · 10 endpoints GET/earn/productsGET/earn/positionsPOST/earn/subscription-quotes View all 10 →

Essential reading

Authentication and SigningTwo values per key; include PATH in the signing string IdempotencyWhen to reuse a key and when to generate a new one WebhookVerify signatures, deduplicate and retry; payloads contain only IDs and status Error ContractBranch on code, not the HTTP status

Three rules to read before you integrate

Represent amounts as fixed-point strings with the asset's ledger_scale. BSC's 18 decimal places exceed 2^53; parsing these amounts as JSON numbers loses precision.
Retry a 504 with the same idempotency key (we may already have processed the request); use a new key after a business failure (reusing the same key replays that failure).
Treat unknown status values as unknown and raise an alert; do not fall back to “processing”. New enum values are announced in the Changelog before they are added.

Platform Status

2 known issues

L2 enhanced verification has no submission endpoint in the Open APIWorkaround →

The same individual cannot have separate accounts under two merchantsWorkaround →

We do not display an unverified “all systems operational” indicator. A green light that cannot detect real incidents is misleading. This section lists the issues we know about. View all →