A stablecoin payout is POST /v1/payouts with a wallet as the instrument and stablecoin as the rail_type. Anton checks it before anything goes on-chain, so the call answers at once and the payout then climbs through block_confirmations until it reaches required_confirmations.
Set up the payee and the wallet first with Register a payee and Register an instrument. To top up the balance, see Fund your balance.
GET /v1/corridors?rail_type=stablecoin lists the networks, currencies, confirmation counts and delivery estimates your account can pay out through.
Create the wallet instrument
A wallet is an instrument with method: "crypto". Anton tokenizes the credentials on receipt, so the address never sits in Anton's database in the clear.
{
"wallet_address": "0x...",
"network": "ethereum",
"token_symbol": "USDC"
}GET /v1/instruments/methods?country=XX lists the exact fields and the allowed network values. See Create an instrument.
The network belongs to the instrument. Check it against what the payee expects before you pay. Funds sent on the wrong network are usually lost.
Send the payout
source_amount and destination_amount are both here, with fixed_side saying which one you promise, as in Send a payout. In USDC to USDC the two are the same number. To pin the fee first, request a pricing quote and send its id as quote_id.
Amounts are strings, and USDC allows up to 6 decimal places. The call returns 201.
curl -X POST \ https://api.antonpayments.dev/v1/payouts \ -H "Authorization: DPoP $ANTON_ACCESS_TOKEN" \ -H "DPoP: $DPOP_PROOF" \ -H "Idempotency-Key: pay-INV-1042" \ -H "Content-Type: application/json" \ -d '{ "beneficiary_id": "ben_01HX8Z9K0M2N3P4Q5R6S7T8UA1", "instrument_id": "ins_01HX8Z9K0M2N3P4Q5R6S7T8UA3", "source_amount": "1000.000000", "source_currency": "USDC", "destination_amount": "1000.000000", "destination_currency": "USDC", "method": "stablecoin", "rail_type": "stablecoin", "fixed_side": "fixed_destination", "purpose": "contractor_payment", "reference": "INV-1042" }'
network is an optional hint on the request. Leave it out and Anton routes the payout. If you send it, use a chain from the Network enum: ethereum, bitcoin, tron, solana, polygon, arbitrum, optimism, base, avalanche, bsc, lightning, stellar or ripple. Which of them carry USDC for you is a corridor question, not a schema one.
Every status change reaches you as a payout.* event. Track payouts with webhooks covers receiving them.
Follow the chain
A payout can also move to pending_approval (your own approval policy), on_hold, failed, cancelled or returned. completed, failed, cancelled and returned are final. Treat a status you don't recognize as still moving.
The payout object gains fields as the transfer progresses:
transaction_hashappears once the payout is sent.block_confirmationscounts the confirmations seen so far.required_confirmationsis the number needed before the payout iscompleted.network_feeandnetwork_fee_currencyshow the gas cost. It comes out of the settlement, not out of your balance.
completed is final: the funds are in the payee's wallet. A payout in on_hold is under review and can't be cancelled while it waits. It never comes with a reason, so show your user a pending state.
When it goes wrong
GET /v1/currencies lists each precision.request_id.Idempotency-Key is still running. Wait and retry.A payout that fails after creation shows status: "failed" with a failure_code, and it won't change again. Errors lists every code.
Idempotency
Derive the Idempotency-Key from your own invoice or order, so a retry never pays twice. Idempotency has the rest.
Sandbox credentials work against https://api.antonpayments.dev and production credentials against https://api.antonpayments.com. They don't cross over. See Environments.