Table of Contents
Paying a vendor, contractor, or customer in USDC or EURC isn't the same as moving funds between wallets your business already owns. Circle's Stablecoin Payouts API is the third-party path: register a recipient in the address book, wait until status is active, then POST /v1/payouts from a funded Mint wallet.
Own-wallet moves stay on Transfer Onchain / the Core API. Payouts need explicit activation on Circle Mint, separate from base Mint access, and book through Circle LLC (US), CIRCLE_SG, or CIRCLE_FR (Circle SAS).
This guide walks prerequisites as of September 12, 2026, the address-book lifecycle (including the 24-hour delayed-withdrawals hold), LLC vs Singapore vs France Travel Rule rules, purposeOfTransfer PMT codes, confirmation via webhook or GET, and the failure modes that force a new idempotencyKey or a brand-new recipient.
Key Takeaways
- Stablecoin Payouts send USDC/EURC to third-party recipients only; use Transfer Onchain for wallets your business owns.
- Register recipients with POST /v1/addressBook/recipients; delayed withdrawals ON keeps new recipients inactive for 24 hours before active.
- Circle LLC Travel Rule starts at ≥ $3,000 USD-equivalent via source.identities[]; CIRCLE_SG and CIRCLE_FR require Travel Rule on every payout.
- CIRCLE_SG/FR need recipient identity + ownership, hosted vaspId from GET /v1/addressBook/vasps, and purposeOfTransfer PMT000–PMT030 except PMT006.
- Named downside: you can't PATCH identity (2036) or ownership (2037); self-hosted wallets aren't supported yet on SG/FR; async transaction_denied (3220) and sync 5020 are common fails.
What Circle Stablecoin Payouts is (and isn't)
Circle documents Stablecoin Payouts as onchain USDC or EURC sends to third-party recipients such as vendors, contractors, or customers. The product is available through Circle LLC (US), Circle Singapore (CIRCLE_SG), and Circle SAS (CIRCLE_FR).
If the destination wallet is one your business owns or controls, Circle points you to Transfer Onchain instead. Don't force first-party treasury moves through the payouts address book.
Activation is explicit: Stablecoin Payouts must be enabled on the Circle Mint account. Contact Circle Mint if the product isn't on yet. See how to open a Circle Mint account for the base account path.
Prerequisites (as of Sep 12, 2026)
Before the first payout, Circle's howto requires:
- Stablecoin Payouts enabled on Circle Mint (LLC, CIRCLE_SG, or CIRCLE_FR).
- A Circle Mint sandbox (or production) API key.
- A source wallet id (source.id) with funds available for payouts.
- For CIRCLE_SG and CIRCLE_FR: the hosted VASP that holds the recipient's wallet.
- A destination address on a chain supported by Stablecoin Payouts.
XRP destinations: classic address only (example format rPEPPER7kfTD9w2To4CQk6UCfuHM9c6GDY) plus addressTag. Circle does not support the x-address format on this API.
Conceptual model: How stablecoin payments work.
Step 1. Register the recipient in the address book
Call POST /v1/addressBook/recipients with at least idempotencyKey, chain, and address. Optional metadata fields include nickname, email, and bns.
On Circle LLC, identity and ownership aren't required at create time for the basic flow. On CIRCLE_SG and CIRCLE_FR, you must attach beneficiary identity and ownership (hosted custody + vaspId) on that same create call.
Recipient status starts at pending, then moves toward active. It can also land as denied. Don't submit a payout until status is active.
Delayed withdrawals and the 24-hour hold
Circle's Mint Console Delayed withdrawals setting controls how fast a new recipient becomes active.
- Delayed withdrawals ON: new recipients stay inactive for 24 hours, then become active.
- Delayed withdrawals OFF: recipients can become active in seconds.
Subscribe to addressBookRecipients webhooks, or poll GET /v1/addressBook/recipients/{id} until status is active.
CIRCLE_SG / CIRCLE_FR: look up vaspId first
For hosted-wallet recipients on Singapore or France flows, call GET /v1/addressBook/vasps and set ownership.custody.vaspId to a listed VASP. Self-hosted wallets aren't yet supported on CIRCLE_SG or CIRCLE_FR Stablecoin Payouts flows.
CIRCLE_FR business recipients can optionally include identity.lei, a 20-character alphanumeric code under ISO 17442. Circle validates the format.
Step 2. Send the payout
Call POST /v1/payouts with source wallet id, destination type address_book id, amount, and toAmount.
Circle LLC (US): Travel Rule at $3,000+
For payouts below $3,000 USD-equivalent, Circle LLC allows a lighter body (wallet source + address-book destination + amounts). At ≥ $3,000 USD-equivalent, include source.identities[] describing the originator. See Circle's Travel rule compliance reference for the schema.
CIRCLE_SG and CIRCLE_FR: Travel Rule on every amount
Singapore (MAS PSN02) and France (EU Transfer of Funds Regulation) apply Travel Rule to every third-party payout. Always send source.identities[], and set purposeOfTransfer to a payment reason code PMT000–PMT030 except PMT006. Missing or invalid purpose codes can return synchronous error 5020.
Sandbox examples in Circle's docs show networkFees around $0.30 USD (illustrative sandbox figure, not a production SLA).
Step 3. Confirm completion
Wait until payout status is complete. Subscribe to payouts webhooks, or poll GET /v1/payouts/{id} on an interval.
Ops that pay contractors or run payroll in USDC usually wire this confirm step into the same treasury runbook. See how to pay contractors in USDC and how to run payroll in USDC.
Entity comparison: LLC vs CIRCLE_SG vs CIRCLE_FR (as of Sep 12, 2026)
| Entity | Travel Rule trigger | Recipient extras | purposeOfTransfer | Named limitation |
|---|---|---|---|---|
| Circle LLC (US) | ≥ $3,000 USD-equivalent (source.identities[]) | Address + chain; metadata optional | Not required for standard LLC Travel Rule collection | Below $3k lighter body; some LLC accounts may still need PMT codes |
| CIRCLE_SG | Every payout amount (MAS PSN02) | identity + ownership + hosted vaspId | Required: PMT000–PMT030 except PMT006 | Self-hosted destinations not yet supported |
| CIRCLE_FR (Circle SAS) | Every payout amount (EU Transfer of Funds Regulation) | identity + ownership + hosted vaspId; optional identity.lei (ISO 17442) | Required: PMT000–PMT030 except PMT006 | Self-hosted destinations not yet supported |
Full identity schemas and payment-reason codes live in Circle's Travel rule compliance reference (as of Sep 2026).
Failure modes to budget for
Circle groups failures into sync HTTP 4xx (fix the body and retry) and async accepts (HTTP 201) that later flip to status failed (resubmit with a new idempotencyKey).
| Signal | Type | What it means | Fix |
|---|---|---|---|
| transaction_denied / reason 3220 | Async | Travel Rule data missing or invalid | Review identities, recipient identity/ownership, vaspId, purposeOfTransfer; new idempotencyKey |
| insufficient_funds | Async | Source wallet can't cover amount + fees | Fund the wallet; new idempotencyKey |
| 5020 | Sync HTTP 400 | purposeOfTransfer missing/invalid | Valid PMT code other than PMT006 |
| 2024–2037 | Sync HTTP 400 | Address-book validation (identity/ownership/vaspId) | Fix on create; for 2036/2037 register a new recipient |
Stablecoin Insider's take
Related Stablecoin Insider playbooks
Open Mint first: how to open a Circle Mint account.
ACH or wire exit: how to off-ramp USDC to ACH or wire.
Payroll path: how to run payroll in USDC.
FAQ
How do I send a Circle stablecoin payout to a third party?
Enable Stablecoin Payouts on Mint, register an address-book recipient until status is active, then POST /v1/payouts with source wallet id, address-book destination id, amount, and toAmount.
What's the difference between Stablecoin Payouts and Transfer Onchain?
Payouts are for third-party recipients your business doesn't own. Transfer Onchain / Core API is for wallets your business owns.
When does Circle LLC require Travel Rule data?
At or above $3,000 USD-equivalent, include source.identities[]. CIRCLE_SG and CIRCLE_FR require Travel Rule data on every payout amount.
What purposeOfTransfer values are valid?
PMT000 through PMT030 except PMT006. Invalid or missing codes can return error 5020 on SG/FR (and some LLC) payouts.
Can I edit identity or ownership on an existing recipient?
No. Errors 2036 (identity) and 2037 (ownership) block PATCH. Register a new recipient.
Should I use Stablecoin Payouts for self-hosted wallets on CIRCLE_SG or CIRCLE_FR?
Not yet. Circle's Sep 2026 docs state self-hosted wallets aren't supported on those flows; use a listed hosted VASP.
Next step
Confirm Stablecoin Payouts is activated on your Mint entity, register one sandbox recipient, wait for active (respect the 24-hour hold if delayed withdrawals are ON), send a below-threshold LLC payout or a fully identified SG/FR payout, and don't leave sandbox until webhooks show status complete and your 3220/5020 handlers are tested.
Still opening Mint before payouts?
This content is provided for informational and educational purposes only and does not constitute financial, investment, legal, or tax advice; no material herein should be interpreted as a recommendation, endorsement, or solicitation to buy or sell any financial instrument, and readers should conduct their own independent research or consult a qualified professional.
){kind=link}