Skip to main content
Use the Stablecoin Payouts API to send USDC or EURC onchain to a third-party recipient, such as vendors, contractors, or customers. For the underlying model, see How stablecoin payments work.
Stablecoin Payouts are for third-party recipients (wallets your business does not own or control). To move funds between wallets your business owns, see Transfer Onchain.

​
Prerequisites

Before you begin:
  • Stablecoin Payouts is enabled on your Circle Mint account. The product is available through Circle LLC (US), Circle Singapore (CIRCLE_SG), and Circle SAS (CIRCLE_FR). To request activation, contact Circle Mint.
  • A Circle Mint sandbox API key. See Get started with Circle Mint.
  • A source wallet ID (source.id) with funds available for payouts.
  • For CIRCLE_SG and CIRCLE_FR: the Virtual Asset Service Provider (VASP) that holds the recipient’s wallet, when the wallet is hosted.
  • The destination address is on a blockchain supported by the Stablecoin Payouts API. See Supported chains and currencies.
For XRP destinations (chain: "XRP"), the Stablecoin Payouts API supports only the classic-address format (for example, rPEPPER7kfTD9w2To4CQk6UCfuHM9c6GDY). The x-address format is not supported. Use the addressTag field to specify the destination tag.

​
Steps

The flow differs by Circle entity: Circle LLC (US) applies Travel Rule data at a $3,000 USD-equivalent threshold, while Circle Singapore (CIRCLE_SG) and Circle SAS (CIRCLE_FR) require beneficiary identity, wallet ownership, and a payment reason code on every payout. Circle SAS recipients can include an optional legal entity identifier (LEI). Select the tab for the Circle entity that books your payout.

​
Step 1. Register the recipient

Add the recipient to your address book with POST /v1/addressBook/recipients. Provide idempotencyKey, chain, and address. The metadata fields (nickname, email, bns) are optional.
curl -X POST https://api-sandbox.circle.com/v1/addressBook/recipients \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "idempotencyKey": "9352ec9e-5ee6-441f-ab42-186bc71fbdde",
    "chain": "BASE",
    "address": "0x65BFCf1a6289a0b77b4D3F7d12005a05949FD8C3",
    "metadata": {
      "nickname": "Acme Corp payout address",
      "email": "ap@acme.example",
      "bns": "acme.base.eth"
    }
  }'

{
  "data": {
    "id": "dff5fcb3-2e52-5c13-8a66-a5be9c7ecbe1",
    "chain": "BASE",
    "address": "0x65bfcf1a6289a0b77b4d3f7d12005a05949fd8c3",
    "metadata": {
      "nickname": "Acme Corp payout address",
      "email": "ap@acme.example",
      "bns": "acme.base.eth"
    },
    "status": "pending",
    "createDate": "2026-05-01T14:16:34.985353Z",
    "updateDate": "2026-05-01T14:16:34.985353Z"
  }
}
The recipient transitions out of pending according to your Mint Console Delayed withdrawals setting. When delayed withdrawals are on, new recipients stay inactive for 24 hours before becoming active. When delayed withdrawals are off, recipients become active in seconds.

​
Step 1.1. Wait for active status

The recipient must be active before you submit a payout.
Subscribe to addressBookRecipients notifications. Circle sends an event when the recipient is created and when its status changes.
{
  "clientId": "a03a47ff-b0eb-4070-b3df-dc66752cc802",
  "notificationType": "addressBookRecipients",
  "version": 1,
  "addressBookRecipient": {
    "id": "dff5fcb3-2e52-5c13-8a66-a5be9c7ecbe1",
    "chain": "BASE",
    "address": "0x65bfcf1a6289a0b77b4d3f7d12005a05949fd8c3",
    "status": "active",
    "createDate": "2026-05-01T14:16:34.985353Z",
    "updateDate": "2026-05-01T14:18:02.123456Z"
  }
}

​
Step 2. Send the payout

Call POST /v1/payouts with the source wallet, the recipient id as the destination, and the amounts.
Travel Rule applies to payouts of $3,000 USD-equivalent or more. Include source.identities[] to describe the originator (your organization or your end customer). See Travel rule compliance for the schema and failure modes.
curl -X POST https://api-sandbox.circle.com/v1/payouts \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "idempotencyKey": "ba943ff1-ca16-49b2-ba55-1057e70ca5c7",
    "source": {
      "type": "wallet",
      "id": "12345"
    },
    "destination": {
      "type": "address_book",
      "id": "dff5fcb3-2e52-5c13-8a66-a5be9c7ecbe1"
    },
    "amount": {
      "amount": "500.00",
      "currency": "USD"
    },
    "toAmount": {
      "currency": "USD"
    }
  }'

{
  "data": {
    "id": "b8627ae8-732b-4d25-b947-1df8f4007a29",
    "sourceWalletId": "12345",
    "destination": {
      "type": "address_book",
      "id": "dff5fcb3-2e52-5c13-8a66-a5be9c7ecbe1"
    },
    "amount": {
      "amount": "3000.14",
      "currency": "USD"
    },
    "toAmount": {
      "amount": "3000.14",
      "currency": "USD"
    },
    "status": "pending",
    "createDate": "2026-05-01T14:20:30.000Z",
    "updateDate": "2026-05-01T14:20:30.000Z"
  }
}

​
Step 3. Confirm completion

Wait for the payout to reach status: complete.
Subscribe to payouts notifications. The payload includes the payout under the payout key.
{
  "clientId": "a03a47ff-b0eb-4070-b3df-dc66752cc802",
  "notificationType": "payouts",
  "version": 1,
  "payout": {
    "id": "b8627ae8-732b-4d25-b947-1df8f4007a29",
    "sourceWalletId": "12345",
    "destination": {
      "type": "address_book",
      "id": "dff5fcb3-2e52-5c13-8a66-a5be9c7ecbe1"
    },
    "amount": {
      "amount": "3000.14",
      "currency": "USD"
    },
    "toAmount": {
      "amount": "3000.14",
      "currency": "USD"
    },
    "fees": {
      "amount": "0.00",
      "currency": "USD"
    },
    "networkFees": {
      "amount": "0.30",
      "currency": "USD"
    },
    "status": "complete",
    "createDate": "2026-05-01T14:20:30.000Z",
    "updateDate": "2026-05-01T14:21:12.000Z"
  }
}

​
Failure modes

Failures fall into two categories. Synchronous validation errors return HTTP 4xx, so you fix the request body and retry. Asynchronous risk evaluation accepts the request with HTTP 201, then transitions the payout to status: failed. Resubmit with a new idempotencyKey after correcting the underlying data.
CodeTypeCauseResolution
transaction_deniedAsynchronousTravel Rule data is missing or invalid. The response carries riskEvaluation.decision: denied and riskEvaluation.reason: 3220.Review source.identities, the recipient’s identity and ownership (CIRCLE_SG and CIRCLE_FR), the vaspId (CIRCLE_SG and CIRCLE_FR), and purposeOfTransfer (CIRCLE_SG and CIRCLE_FR). Resubmit with a new idempotencyKey.
insufficient_fundsAsynchronousThe source wallet does not have enough balance for amount plus fees.Fund the source wallet, then resubmit with a new idempotencyKey.
5020Synchronous (HTTP 400)purposeOfTransfer is missing or invalid on a CIRCLE_SG or CIRCLE_FR payout.Provide a valid PMT code other than PMT006.
2024 to 2037Synchronous (HTTP 400)Address Book validation failures on CIRCLE_SG and CIRCLE_FR: missing identity, missing ownership, missing or disallowed vaspId, or PATCH attempted on identity or ownership.Add the missing or corrected field on the initial create call. For 2036 and 2037 PATCH errors, register a new recipient instead.
See Travel rule compliance for schema details and API errors for the full error code reference.

​
See also