> ## 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.

# Create a fiat payout

> Create a fiat payout to a registered beneficiary. Set `destination.type` to
`fiat_address_book` and supply a locked quote from `POST /v1/payouts/quotes`. The
beneficiary must be in `ACTIVE` status.

This is the same `POST /v1/payouts` endpoint that creates stablecoin payouts. The
`destination.type` value selects the payout type. To track a fiat payout, call
`GET /v1/payouts/{id}` or subscribe to the payout state change webhook.




## OpenAPI

````yaml openapi/managed-payments.yaml post /v1/payouts
openapi: 3.0.2
info:
  version: ${version}
  title: Managed Payments API
  description: |
    The Managed Payments API enables Payment Service Providers (PSPs) to create
    and manage sub-client accounts for stablecoin settlement, and to send fiat
    payouts to registered beneficiaries worldwide.
servers:
  - url: https://api-sandbox.circle.com
  - url: https://api.circle.com
security: []
tags:
  - name: Managed Payments Accounts
    description: Create and manage sub-client accounts for Managed Payments PSPs.
  - name: Managed Payments Credit
    description: Get credit line details and wire instructions for repayment.
  - name: Managed Payments Credit Transfers
    description: Create and manage credit transfers (drawdowns) against a credit line.
  - name: Managed Payments Transfers
    description: >-
      Create and manage internal account-to-account transfers for Managed
      Payments.
  - name: Managed Payments Fiat Payouts
    description: >
      Register and manage fiat payout beneficiaries, discover supported
      corridors and

      field requirements, and create locked FX quotes for cross-border fiat
      payouts.
paths:
  /v1/payouts:
    post:
      tags:
        - Managed Payments Fiat Payouts
      summary: Create a fiat payout
      description: >
        Create a fiat payout to a registered beneficiary. Set `destination.type`
        to

        `fiat_address_book` and supply a locked quote from `POST
        /v1/payouts/quotes`. The

        beneficiary must be in `ACTIVE` status.


        This is the same `POST /v1/payouts` endpoint that creates stablecoin
        payouts. The

        `destination.type` value selects the payout type. To track a fiat
        payout, call

        `GET /v1/payouts/{id}` or subscribe to the payout state change webhook.
      operationId: createPayout
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ManagedPaymentsFiatPayoutCreationRequest'
      responses:
        '201':
          description: Successfully created a fiat payout.
          headers:
            X-Request-Id:
              $ref: '#/components/headers/XRequestId'
          content:
            application/json:
              schema:
                title: CreateFiatPayoutResponse
                properties:
                  data:
                    type: object
                    properties:
                      id:
                        $ref: '#/components/schemas/Id'
                      sourceWalletId:
                        type: string
                        description: >-
                          The identifier of the source wallet used to fund the
                          payout.
                        example: '1000000001'
                      destination:
                        type: object
                        properties:
                          type:
                            type: string
                            enum:
                              - fiat_address_book
                          id:
                            type: string
                            format: uuid
                            description: Beneficiary UUID.
                            example: a1b2c3d4-e5f6-7890-abcd-ef1234567890
                      amount:
                        type: object
                        properties:
                          amount:
                            type: string
                            example: '95.50'
                          currency:
                            type: string
                            example: USDC
                      quoteId:
                        type: string
                        format: uuid
                        example: 66666666-7777-8888-9999-000000000000
                      useCase:
                        type: string
                        enum:
                          - B2B
                          - B2C
                          - C2B
                          - C2C
                        example: B2C
                      reasonForPayment:
                        type: string
                        example: PMT001
                      customerRefId:
                        type: string
                        example: order-9876
                      status:
                        $ref: '#/components/schemas/PayoutStatus'
                      createDate:
                        $ref: '#/components/schemas/UtcTimestamp'
                      updateDate:
                        $ref: '#/components/schemas/UtcTimestamp'
              examples:
                Fiat Payout (Managed Payments):
                  value:
                    data:
                      id: f1e2d3c4-b5a6-7890-abcd-ef0987654321
                      sourceWalletId: '1000000001'
                      destination:
                        type: fiat_address_book
                        id: a1b2c3d4-e5f6-7890-abcd-ef1234567890
                      amount:
                        amount: '95.50'
                        currency: USDC
                      quoteId: 66666666-7777-8888-9999-000000000000
                      useCase: B2C
                      reasonForPayment: PMT001
                      customerRefId: order-9876
                      status: pending
                      createDate: '2026-08-12T00:10:00.000Z'
                      updateDate: '2026-08-12T00:10:00.000Z'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/NotAuthorized'
      security:
        - bearerAuth: []
components:
  schemas:
    ManagedPaymentsFiatPayoutCreationRequest:
      title: Managed Payments fiat payout
      description: >
        For Managed Payments entities sending fiat payouts to a registered
        beneficiary.

        Set `destination.type` to `fiat_address_book` and supply a locked quote
        from

        `POST /v1/payouts/quotes`. The beneficiary must be in `ACTIVE` status.
      type: object
      required:
        - idempotencyKey
        - destination
        - amount
        - quoteId
        - useCase
        - reasonForPayment
        - customerRefId
      properties:
        idempotencyKey:
          $ref: '#/components/schemas/IdempotencyKey'
        source:
          type: object
          properties:
            type:
              type: string
              enum:
                - wallet
            id:
              type: string
              description: Wallet ID to debit. Defaults to the entity master wallet.
              example: '1000000001'
        destination:
          type: object
          required:
            - type
            - id
          properties:
            type:
              type: string
              enum:
                - fiat_address_book
            id:
              type: string
              format: uuid
              description: >-
                Beneficiary UUID from `POST /v1/beneficiaries`. Must be
                `ACTIVE`.
              example: a1b2c3d4-e5f6-7890-abcd-ef1234567890
        amount:
          type: object
          required:
            - amount
            - currency
          properties:
            amount:
              type: string
              description: >-
                Amount in source currency. Must match the `from.amount` on the
                quote.
              example: '95.50'
            currency:
              type: string
              description: Source cryptocurrency (e.g. `USDC`, `EURC`).
              example: USDC
        quoteId:
          type: string
          format: uuid
          description: >
            Locked quote identifier from `POST /v1/payouts/quotes`. Quotes
            expire at

            `expiresAt`; submitting an expired quote returns a `400`.
          example: 66666666-7777-8888-9999-000000000000
        useCase:
          type: string
          enum:
            - B2B
            - B2C
            - C2B
            - C2C
          description: |
            Use case describing the originator and recipient relationship.
            - `B2B` — business originator, business recipient.
            - `B2C` — business originator, individual recipient.
            - `C2B` — individual originator, business recipient.
            - `C2C` — individual originator, individual recipient.
          example: B2C
        reasonForPayment:
          type: string
          description: >
            Payment reason code. See [Crypto Payouts payment reason
            codes](https://developers.circle.com/circle-mint/crypto-payouts-payment-reason-codes).
          example: PMT001
        customerRefId:
          type: string
          description: Customer-provided reference identifier for this payout.
          example: order-9876
        originatorMode:
          type: integer
          description: >
            Travel rule originator nesting mode. `0` = standalone (default), `1`
            = nested

            (originator is acting on behalf of another party).
          default: 0
          example: 0
        travelRule:
          type: object
          description: >
            Originator travel rule information. Required fields depend on
            `originatorMode`

            and the destination corridor. Keys match the field names returned by

            `GET /v1/beneficiaries/requirements`.
          additionalProperties: true
          example:
            ORIGINATOR_NAME: Acme Corp
            ORIGINATOR_ADDRESS:
              STREET: 1 Main St
              CITY: New York
              STATE_PROVINCE: NY
              POSTAL_CODE: '10001'
              COUNTRY: US
    Id:
      type: string
      description: Unique system generated identifier for the entity.
      format: uuid
      example: b8627ae8-732b-4d25-b947-1df8f4007a29
    PayoutStatus:
      type: string
      description: >-
        Status of the payout. Status `pending` indicates that the payout is in
        process; `complete` indicates it finished successfully; `failed`
        indicates it failed.
      enum:
        - pending
        - complete
        - failed
    UtcTimestamp:
      type: string
      description: ISO-8601 UTC date/time format.
      example: '2020-04-10T02:13:30.000Z'
    IdempotencyKey:
      type: string
      description: >-
        Universally unique identifier (UUID v4) idempotency key. This key is
        utilized to ensure exactly-once execution of mutating requests.
      format: uuid
      example: ba943ff1-ca16-49b2-ba55-1057e70ca5c7
  headers:
    XRequestId:
      description: >-
        Universally unique identifier (UUID v4) for the request. Helpful for
        identifying a request when communicating with Circle support.
      schema:
        type: string
        format: uuid
        example: 2adba88e-9d63-44bc-b975-9b6ae3440dde
  responses:
    BadRequest:
      description: The request cannot be processed due to a client error.
      headers:
        X-Request-Id:
          $ref: '#/components/headers/XRequestId'
      content:
        application/json:
          schema:
            type: object
            title: BadRequest
            required:
              - code
              - message
            properties:
              code:
                type: integer
                example: 400
              message:
                type: string
                example: Something went wrong.
            example:
              code: 400
              message: Bad request.
          examples:
            response:
              value:
                code: 400
                message: Bad request.
    NotAuthorized:
      description: >-
        The request has not been applied because it lacks valid authentication
        credentials.
      headers:
        X-Request-Id:
          $ref: '#/components/headers/XRequestId'
      content:
        application/json:
          schema:
            type: object
            title: NotAuthorized
            required:
              - code
              - message
            properties:
              code:
                type: integer
                example: 400
              message:
                type: string
                example: Something went wrong.
            example:
              code: 401
              message: Malformed authorization.
          examples:
            response:
              value:
                code: 401
                message: Malformed authorization.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer

````