Both USDT and USDC are supported as the source currency.
What it solves
Sending a payout normally means setting up each party and their bank account before the transaction itself. With the Unified Transaction API, one call replaces that groundwork:- One request, not several. Sender, beneficiary, bank account and transaction details travel together. You do not call separate Create User, KYC or Bank Account Linkage endpoints.
- No sender management. Saber resolves or creates the sender for you. You do not create senders, store sender IDs or maintain sender-to-beneficiary mappings.
- First-party and third-party payouts. The sender and the beneficiary can be the same person or different people. The relationship is captured on each transaction, so one sender can pay many beneficiaries and one beneficiary can receive from many senders.
- Status you can track. Each stage — sender KYC, beneficiary KYC, bank account verification and payout — is reported as a transaction status, by webhook and by polling.
How it works
The create call returns immediately. Everything after that runs asynchronously, so your integration listens for webhooks and reads the authoritative state with a status request when needed.What is supported
Endpoints
Before you integrate
1
Fund your pool wallet
Payouts are debited from your pool wallet, so keep it funded before creating transactions. See Pool Account Overview.
2
Get your API keys
Generate your API key and secret from the dashboard. See Developer Section and API Authentication.
3
Configure webhooks
Add your callback URL and webhook credentials to receive status updates. See Webhook Configuration.
Next steps
Unified Transaction API
Create a payout, track its status and reconcile, with request and response examples and mandatory fields.