Overview
AliX Pay powers digital asset platforms by providing payments infrastructure and regulatory compliance across global markets. Our mission is to build the bridge that gives people in every part of the world access to a fairer and more equitable financial system.
What the API does
You hold a crypto fund with AliX. The API turns that fund into fiat payouts — into a recipient's bank account, or to a merchant your customer scanned. AliX handles the payment rails, the liquidity, and the compliance; you handle your customer.
| Service | Use it to |
|---|---|
| Scan-to-Pay | Let your user pay a merchant by QR code. Decode the QR, quote it, pay it. |
| Cashout | Pay fiat out to a recipient's bank account directly. |
Around those sit authentication, the KYC that gates them, your fund and its ledger, and bank-account resolution. Payouts settle asynchronously and tell you the outcome by webhook.
Where to start
- Quick start — an end-to-end integration in six steps: authenticate, verify a user, quote, create an order, settle it.
- Concepts — how authentication, the response envelope, orders, KYC, webhooks, and every error code work.
- API Explorer — the reference: every endpoint, with its full request and response schema, ready-made code samples, and a live test client pointed at the sandbox.
Build against https://sandbox.alixpay.com first. It mirrors production and lets you
force an order to succeed or fail on demand, so you can test both
branches of your integration before any money moves.
Already integrated on v2?
Everything above describes API v3, the current API, whose paths are rooted at /v3. The older v2
API — paths rooted at /api/v2 — is frozen but still live and still supported. It is a
genuinely different API, not an older spelling of this one: it has no access tokens, it signs every
request body with RSA, and it returns a different response envelope.
If your integration calls /api/v2/*, read API v2 (legacy) instead — nothing on this page
applies to you.