Skip to main content
This guide shows how to send a stablecoin payout with Managed Payments. You add a blockchain recipient to your address book. You wait until the recipient is active. You create a payout from a sub-account or the main wallet. You confirm that the payout completes.

Prerequisites

Before you start, ensure you have:
  • Managed Payments onboarding done and API keys for the environment you use. This guide uses the sandbox host api-sandbox.circle.com.
  • Roles for address book and stablecoin payouts for your setup. Circle sets roles when you onboard.
  • A sub-account wallet ID for source when you don’t pay from the main wallet alone. Read Managed Payments and Sub-account architecture.
  • (Optional) A webhook endpoint for address book and payout events. See Set up a webhook endpoint.

Sequence diagram

Steps

  1. Create an address book recipient
  2. Wait until the recipient is active
  3. Create a payout
  4. Confirm the payout completed

1. Create an address book recipient

Outbound sends use destinations in your address book. Create a recipient with create an address book recipient.
Circle Singapore (CIRCLE_SG) entities must include beneficiary identity and ownership on create. For a hosted (custodial) beneficiary, add:
Obtain vaspId from list address book VASPs (GET /v1/addressBook/vasps). For a self-hosted beneficiary, set ownership.custody.type to self_hosted (omit vaspId) and provide the nested PII object matching identity.type for Travel Rule compliance. See create an address book recipient for the full SG schema.Circle LLC (United States) entities register a recipient with just chain and address; the VASP directory and vaspId don’t apply and aren’t available.
Don’t create a payout until the recipient is active. The status you get when you create a recipient depends on your setup. For example, delayed withdrawals can keep a new entry inactive until it activates (see the following note).
Delayed withdrawals are off by default for Managed Payments. You can’t turn them on or off yourself; contact Circle customer support if your setup needs a different configuration. When delayed withdrawals are on, new address book entries start inactive. Wait until they’re active before you pay.
Response

2. Wait until the recipient is active

You cannot pay an inactive recipient. Use webhooks or polling until status is active.

Option 1: Webhook notification

After you subscribe, you get updates when address book recipients change. This sample shows an active recipient.
Address book recipient webhook notification

Option 2: Poll the recipient

Call get an address book recipient until data.status is active.
Response

3. Create a payout

Create the payout with create a payout. Set destination to the address book entry. Set amount and optional toAmount. Set source when you use a sub-account. If you omit source, the API withdraws from the main wallet.
Receiving currency and Travel Rule: If you omit toAmount.currency, the API uses amount.currency as the receiving currency.The source.identities object is required for payouts greater than or equal to $3,000. The object describes the originator (your organization), not the recipient, for Financial Crimes Enforcement Network (FinCEN) Travel Rule compliance.Circle Singapore (CIRCLE_SG) purpose of transfer: These entities must set purposeOfTransfer on the payout using a code from the payment reason codes reference.
Main wallet funding: For Managed Payments, source.useMainWalletFunding defaults to true. When it is true, the API tops up from the main wallet if the source wallet lacks funds. Set source.useMainWalletFunding to false to require the full amount on the source wallet only.Insufficient funds: If a payout fails because funds are not ready yet, confirm your wire completed and USDC is available for the source wallet. See the Wires API and Settlement flows.
The example uses a sub-account as source, sets useMainWalletFunding on source, and uses an amount that needs identities for Travel Rule coverage. Replace placeholder IDs with your own values.
Response

4. Confirm the payout completed

Use webhooks or polling with get a payout to confirm the payout finished onchain.

Option 1: Webhook notification

Payout webhook notification

Option 2: Poll the payout

Response