Transfers (V2)
Move funds between fiat and stablecoins for your Customers.
A transfer moves funds from a Customer to a recipient.
Transfers (V2) replaces the deprecated Transfers (V1).
| Action | Endpoint |
|---|---|
| Create a quote | POST /api/v2/transfers/quotes |
| Get the transfer requirements | GET /api/v2/transfers/quotes/{quote_id}/requirements |
| Create a transfer | POST /api/v2/transfers |
| Retrieve a transfer | GET /api/v2/transfers/{transfer_uuid} |
| List all transfers | GET /api/v2/transfers |
With this API, you can:
- On-Ramp: convert fiat to stablecoins, such as USD to USDC.
- Off-Ramp: convert stablecoins to fiat, such as USDC to MXN.
- On-Chain: move stablecoins between wallets or blockchains, such as USDC from Ethereum to Polygon.
How It Works
Every transfer starts with a quote. The quote locks the exchange rate and fees until it expires, so the transfer uses the same values you showed your Customer.
You also use the quote id to get the transfer requirements: the fields the transfer needs, such as the recipient's bank details. They're different for each country, currency and payment method.
A transfer takes three steps:
Then follow its status by retrieving it, or with Webhooks. See Transfer Lifecycle.
More in This Section
- Transfer Purpose: a required field in
destinationthat states the reason for the transfer, for compliance purposes. - Recipients: save a beneficiary's details and reuse them.
- Transfer to Local Currency: pay recipients in their own currency, through local payment networks.
- Pay First, Bind Later: start a debit card payout before you have the card details.
- Transfer Limits: the limits on your Customers' transfers.
- Transfer RFI: when a transfer needs more information.
To fund an on-ramp from a linked bank account (ACH Pull), see Link Bank Account.
Updated 29 days ago