> ## Documentation Index
> Fetch the complete documentation index at: https://developers.circle.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Before reading these docs, install the relevant Circle Skill to get pre-loaded context — skills are LLM-optimized and cover architecture decisions, correct flows, and common pitfalls. In Claude Code: run /plugin marketplace add circlefin/skills then /plugin install circle-skills@circle. With Vercel Skills CLI: run npx skills add circlefin/skills. Available skills: use-usdc https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-usdc/SKILL.md (balances, transfers, approvals on EVM and Solana); EURC has no skill — see https://developers.circle.com/stablecoins/what-is-eurc.md; bridge-stablecoin https://github.com/circlefin/skills/blob/master/plugins/circle/skills/bridge-stablecoin/SKILL.md (crosschain transfers via CCTP, USDC, EURC, and third-party assets); use-arc https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-arc/SKILL.md (Arc chain config, contract deployment, USDC bridging — Arc docs: https://docs.arc.io/llms.txt); use-circle-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-circle-wallets/SKILL.md (choose wallet type); use-developer-controlled-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-developer-controlled-wallets/SKILL.md (custodial wallets for payouts and treasury); use-user-controlled-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-user-controlled-wallets/SKILL.md (embedded wallets with Web2 login); use-modular-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-modular-wallets/SKILL.md (smart contract wallets with passkeys and ERC-4337); use-gateway https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-gateway/SKILL.md (unified USDC balance, nanopayments); use-smart-contract-platform https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-smart-contract-platform/SKILL.md (deploy, interact, monitor contracts). Pair any skill with the Circle MCP server for live SDK signatures, contract addresses, and chain IDs: {"mcpServers":{"circle":{"url":"https://api.circle.com/v1/codegen/mcp"}}}.
> Read the product overview first. Each product has an overview explaining when and why to use it. Read it before quickstarts.
> Pick the right wallet type. Developer-controlled (you hold keys), user-controlled (end user holds keys via PIN/social login), or modular (smart contract wallets with passkeys). See https://developers.circle.com/wallets.md.
> Use CCTP V2 for crosschain transfers. CCTP natively transfers USDC and EURC via burn-and-mint, and supports permissionless wrapping of third-party assets via lock-and-mint. V1 is legacy; always use V2 unless V1 is specified or the chain requires it (Noble, Sui, and Aptos still require V1). Migration guide: https://developers.circle.com/cctp/migration-from-v1-to-v2.md.
> Use Bridge Kit for frontend bridging. Wraps CCTP with a simpler SDK for user-facing apps. Use CCTP directly for backend transfers.
> Gas Station vs Paymaster. Gas Station sponsors gas for Circle Wallet transactions. Paymaster lets users pay gas in USDC. Different use cases — read both overviews.
> Gateway Nanopayments for sub-cent payments. Gasless USDC micropayments down to $0.000001 via x402 and batched settlement. For pay-per-request APIs, AI agent payments, streaming.
> Look up USDC addresses per chain. Never hardcode — use https://developers.circle.com/stablecoins/usdc-contract-addresses.md.
> Prefer SDKs over raw API calls. Node.js and Python SDKs handle auth, retries, and errors.
> API key required. Bearer token in Authorization header. Testnet and mainnet use separate keys and may use different base URLs depending on the product.
> Set up webhooks when available. Most operations are async. Webhooks deliver transaction confirmations and state changes.
> When calling list endpoints, paginate using pageSize and pageAfter until no nextPageAfter cursor is returned—stopping at the first page silently misses records.
> Building an AI agent? Start with the Agent Stack—Circle CLI, agent wallets, and nanopayments built for autonomous use cases: https://developers.circle.com/agent-stack.md.

# How-to: Wire deposits and withdrawals

> Link bank accounts, deposit fiat, and withdraw stablecoins through wire transfers

Link your end customers' bank accounts to their Digital Asset Accounts so they
can move money between traditional banking and stablecoins. Wire deposits
convert fiat into stablecoins. Wire withdrawals redeem stablecoin balances and
send funds to the linked bank account.

## Prerequisites

Before you begin:

* Obtain an API key for Digital Asset Accounts from Circle.
* Have an onboarded and active account with an `accountId`.
* Review whether Strong Customer Authentication (SCA) applies. Circle requires
  SCA headers on withdrawals and when linking wire accounts for end users in the
  European Economic Area (EEA). See
  [Implement SCA](/digital-asset-accounts/howtos/strong-customer-authentication).
* Run a device check for the end user and keep the `deviceId` it returns. Every
  money movement and bank account request carries it in `riskSignals`. See
  [Collect device risk signals](/end-user-onboarding/howtos/collect-device-risk-signals).
* Install cURL on your development machine.

<Note>
  The Digital Asset Accounts API base URL is `https://api-sandbox.circle.com` for
  sandbox and `https://api.circle.com` for production. Set your API key in the
  `Authorization` header using the format `Bearer YOUR_API_KEY`. See
  [Sandbox environment](/digital-asset-accounts/references/testing-in-sandbox) and
  [Going to production](/digital-asset-accounts/references/going-to-production)
  for environment details.
</Note>

## Steps

### Step 1. Link a bank account

Link your end customer's bank account by providing the bank details and billing
information.

```shell theme={null}
curl --request POST \
  --url https://api-sandbox.circle.com/v1/banks/wires \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer ${YOUR_API_KEY}' \
  --header 'Content-Type: application/json' \
  --data '
{
  "clientEntityId": "${CLIENT_ENTITY_ID}",
  "idempotencyKey": "${RANDOM_UUID}",
  "accountNumber": "123456789",
  "routingNumber": "021000021",
  "billingDetails": {
    "name": "Acme Corp",
    "line1": "100 Money Street",
    "city": "Boston",
    "district": "MA",
    "postalCode": "01234",
    "country": "US"
  },
  "bankAddress": {
    "bankName": "Chase Bank",
    "city": "New York",
    "country": "US",
    "line1": "270 Park Avenue",
    "district": "NY"
  },
  "riskSignals": {
    "ipAddress": "${END_USER_IP}",
    "sessionId": "${SESSION_ID}",
    "deviceId": "${DEVICE_ID}"
  }
}
'
```

**Response**

```json theme={null}
{
  "data": {
    "id": "b8a025e7-d5e5-4e5a-8e35-2f3a7d1c9b4a",
    "status": "complete",
    "description": "CHASE BANK ****6789",
    "trackingRef": "CIR3XXXYYY",
    "virtualAccountEnabled": false,
    "fingerprint": "abc123def456",
    "billingDetails": {
      "name": "Acme Corp",
      "line1": "100 Money Street",
      "city": "Boston",
      "postalCode": "01234",
      "district": "MA",
      "country": "US"
    },
    "bankAddress": {
      "bankName": "Chase Bank",
      "city": "New York",
      "country": "US"
    },
    "createDate": "2026-03-15T10:00:00Z",
    "updateDate": "2026-03-15T10:00:00Z"
  }
}
```

#### Link a European (EUR) bank account

For end users in the European Economic Area (EEA), EUR funding uses the same
wire flow. Provide the account's `iban` instead of `accountNumber` and
`routingNumber`. EUR deposits mint EURC.

```shell theme={null}
curl --request POST \
  --url https://api-sandbox.circle.com/v1/banks/wires \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer ${YOUR_API_KEY}' \
  --header 'Content-Type: application/json' \
  --data '
{
  "clientEntityId": "${CLIENT_ENTITY_ID}",
  "idempotencyKey": "${RANDOM_UUID}",
  "iban": "DE31100400480532013000",
  "billingDetails": {
    "name": "Acme GmbH",
    "line1": "Friedrichstrasse 1",
    "city": "Berlin",
    "postalCode": "10117",
    "country": "DE"
  },
  "bankAddress": {
    "bankName": "Commerzbank",
    "city": "Frankfurt",
    "country": "DE",
    "line1": "Kaiserplatz 16"
  },
  "riskSignals": {
    "ipAddress": "${END_USER_IP}",
    "sessionId": "${SESSION_ID}",
    "deviceId": "${DEVICE_ID}"
  }
}
'
```

To retrieve EUR-denominated instructions, pass `currency=EUR` when you get wire
instructions in the next step.

### Step 2. Get wire instructions

Retrieve the wire instructions for the linked bank account. Share these with
your end customer so they can send a wire deposit from their bank.

```shell theme={null}
curl --request GET \
  --url 'https://api-sandbox.circle.com/v1/banks/wires/${WIRE_ID}/instructions?accountId=${ACCOUNT_ID}' \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer ${YOUR_API_KEY}'
```

**Response**

```json theme={null}
{
  "data": {
    "trackingRef": "CIR3XXXYYY",
    "beneficiary": {
      "name": "Circle Internet Financial Inc",
      "address1": "99 High Street",
      "address2": "Boston, MA 02110"
    },
    "virtualAccountEnabled": false,
    "beneficiaryBank": {
      "name": "Silicon Valley Bank",
      "routingNumber": "121140399",
      "accountNumber": "1234567890",
      "currency": "USD",
      "country": "US"
    }
  }
}
```

The `trackingRef` is a unique reference code that identifies the wire deposit.
Your customer must include it in their wire transfer so Circle can match the
payment to the correct account.

<Warning>
  Your end customer must include the `trackingRef` when sending the wire transfer.
  Without this reference, the deposit cannot be matched to the correct account.
</Warning>

### Step 3. Deposit fiat (sandbox simulation)

In the sandbox environment, simulate a wire deposit using the mock payments
endpoint. In production, your end customer sends a real wire transfer using the
instructions from the previous step.

```shell theme={null}
curl --request POST \
  --url https://api-sandbox.circle.com/v1/mocks/payments/wire \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer ${YOUR_API_KEY}' \
  --header 'Content-Type: application/json' \
  --data '
{
  "trackingRef": "${TRACKING_REF}",
  "amount": {
    "amount": "10000.00",
    "currency": "USD"
  },
  "beneficiaryBank": {
    "accountNumber": "1234567890",
    "routingNumber": "121140399"
  }
}
'
```

**Response**

```json theme={null}
{
  "data": {
    "trackingRef": "CIR3XXXYYY",
    "beneficiaryBank": {
      "routingNumber": "121140399",
      "accountNumber": "1234567890"
    },
    "amount": {
      "amount": "10000.00",
      "currency": "USD"
    },
    "status": "pending"
  }
}
```

### Step 4. Check the balance

Confirm that the deposit has been credited to the account.

```shell theme={null}
curl --request GET \
  --url https://api-sandbox.circle.com/v1/accounts/${ACCOUNT_ID} \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer ${YOUR_API_KEY}'
```

**Response**

```json theme={null}
{
  "data": {
    "balances": [
      {
        "amount": "10000.00",
        "currency": "USD"
      }
    ]
  }
}
```

### Step 5. Withdraw to a bank account

To withdraw stablecoins as fiat, create a withdrawal that specifies the amount,
the destination wire account, and the source account.

```shell theme={null}
curl --request POST \
  --url https://api-sandbox.circle.com/v1/accounts/withdrawals \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer ${YOUR_API_KEY}' \
  --header 'Content-Type: application/json' \
  --data '
{
  "idempotencyKey": "${RANDOM_UUID}",
  "destination": {
    "type": "wire",
    "id": "${WIRE_ID}"
  },
  "amount": {
    "amount": "5000.00",
    "currency": "USD"
  },
  "source": {
    "type": "account",
    "id": "${ACCOUNT_ID}"
  },
  "riskSignals": {
    "ipAddress": "${END_USER_IP}",
    "sessionId": "${SESSION_ID}",
    "deviceId": "${DEVICE_ID}"
  }
}
'
```

**Response**

```json theme={null}
{
  "data": {
    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "sourceAccountId": "1017381855",
    "destination": {
      "type": "wire",
      "id": "b8a025e7-d5e5-4e5a-8e35-2f3a7d1c9b4a"
    },
    "amount": {
      "amount": "5000.00",
      "currency": "USD"
    },
    "toAmount": {
      "amount": "5000.00",
      "currency": "USD"
    },
    "status": "pending",
    "createDate": "2026-03-15T14:00:00Z",
    "updateDate": "2026-03-15T14:00:00Z"
  }
}
```

The withdrawal processes asynchronously. Monitor the status by polling the
withdrawals endpoint or by setting up
[webhook notifications](/api-reference/webhook-endpoints#v2-notifications).

If the source account has insufficient funds, the API returns an error:

```json theme={null}
{
  "code": 2,
  "message": "Insufficient funds. The source account does not have enough balance to complete this withdrawal."
}
```

Verify the account balance before initiating a withdrawal.

## List and retrieve wire accounts

You can query linked wire accounts at any time.

**List all wire accounts for an end user**

```shell theme={null}
curl --request GET \
  --url 'https://api-sandbox.circle.com/v1/banks/wires?clientEntityId=${CLIENT_ENTITY_ID}' \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer ${YOUR_API_KEY}'
```

**Get a specific wire account**

```shell theme={null}
curl --request GET \
  --url https://api-sandbox.circle.com/v1/banks/wires/${WIRE_ID} \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer ${YOUR_API_KEY}'
```