Global | Crypto Payouts
Market specifications
This specification applies to all markets where crypto payouts are available. Payouts deliver USDC or USDT stablecoins to a beneficiary’s wallet address via a specified blockchain network.
Crypto payouts are processed via direct stablecoin transfer to a blockchain wallet. This method requires specific beneficiary and crypto-specific parameters and is processed synchronously.
Asset and Network Reference
| Asset | Supported Networks |
|---|---|
| USDC | ETHEREUM, POLYGON, BSC |
| USDT | ETHEREUM, TRON, BSC |
Mandatory parameters
All fields listed below are required for crypto payouts. For successful processing, ensure correct formatting and value types.
| Parameter | B2C | B2B | P2P |
|---|---|---|---|
external_id | Yes | Yes | Yes |
payment_method_id | Yes | Yes | Yes |
flow_type | Yes | Yes | Yes |
purpose | Yes | Yes | Yes |
currency_to_pay | Yes | Yes | Yes |
amount | Yes | Yes | Yes |
beneficiary.first_name | Yes | - | Yes |
beneficiary.last_name | Yes | - | Yes |
beneficiary.business_name | - | Yes | Yes |
beneficiary.nationality | Yes | Yes | Yes |
beneficiary.document.id | Yes | Yes | Yes |
beneficiary.birth_info.date | Yes | Yes | Yes |
beneficiary.crypto.id | Yes | Yes | Yes |
beneficiary.crypto.network | Yes | Yes | Yes |
remitter.first_name | - | - | Yes |
remitter.last_name | - | - | Yes |
remitter.nationality | - | - | Yes |
remitter.document.id | - | - | Yes |
Parameter specification
All fields listed below are required for crypto transfer payouts.
| Mandatory parameter | Description |
|---|---|
external_id | Payout identification at the merchant's end. Maximum 100 characters. |
payment_method_id | Payment method identifier. Use CRYPTO for crypto transfers. |
flow_type | Payout flow type. Valid values: B2C (Business to Consumer), B2B (Business to Business), or P2P (Person to Person). |
purpose | Payout purpose code. See purpose codes reference. |
currency_to_pay | Asset to be paid out. Use USDC or USDT. |
amount | Payout amount in the asset set in currency_to_pay. Use up to 2 decimal places. |
beneficiary.first_name | Beneficiary's first name. Maximum 50 characters. Mandatory for B2C and P2P. |
beneficiary.last_name | Beneficiary's last name. Maximum 50 characters. Mandatory for B2C and P2P. |
beneficiary.business_name | Beneficiary's business name. Mandatory only for B2B. |
beneficiary.nationality | Beneficiary's nationality. ISO 3166-1 alpha-2 code. |
beneficiary.document.id | Beneficiary's document number (e.g., CPF for BR individuals). |
beneficiary.birth_info.date | Beneficiary's date of birth in YYYY-MM-DD format. |
beneficiary.crypto.id | Destination wallet address (string). |
beneficiary.crypto.network | Blockchain network (string). Accepted values vary by currency_to_pay. |
remitter.first_name | Remitter's first name. Mandatory only for P2P. |
remitter.last_name | Remitter's last name. Mandatory only for P2P. |
remitter.nationality | Remitter's nationality (ISO 3166-1 alpha-2). Mandatory only for P2P. |
remitter.document.id | Remitter's document number. Mandatory only for P2P. |
Example requests
{
"external_id": "b2c-crypto-98765",
"payment_method_id": "CRYPTO",
"flow_type": "B2C",
"purpose": "OTHER_SERVICES",
"currency_to_pay": "USDC",
"amount": 150.00,
"beneficiary": {
"first_name": "Maria",
"last_name": "Silva",
"nationality": "BR",
"document": {
"id": "12345678900"
},
"birth_info": {
"date": "1990-05-15"
},
"crypto": {
"id": "0xAb5801a7D398351b8bE11C439e05C5B3259aeC9B",
"network": "ETHEREUM"
}
}
}
{
"external_id": "b2b-crypto-12342",
"payment_method_id": "CRYPTO",
"flow_type": "B2B",
"purpose": "CAPITAL_CONTRIBUTION",
"currency_to_pay": "USDT",
"amount": 2500.00,
"beneficiary": {
"business_name": "Acme Imports LTDA",
"nationality": "BR",
"document": {
"id": "12345678000199"
},
"crypto": {
"id": "bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh",
"network": "TRON"
}
}
}
Updated about 18 hours ago
