Create a disbursement
Creates a merchant-initiated payment of funds from a CDP account owned by the merchant to a Coinbase user account or onchain address. Used for standalone refunds, goodwill disbursements, rebates, and other merchant-driven payouts that are not tied to a specific payment session.
This is an asynchronous operation. The disbursement is returned in pending status and transitions to succeeded (with associated onchainTransactions) or failed (with error).
Authorizations
A JWT signed using your CDP API Key Secret, encoded in base64. Refer to the Generate Bearer Token section of our Authentication docs for information on how to generate your Bearer Token.
Headers
An optional string request header for making requests safely retryable. When included, duplicate requests with the same key will return identical responses. Refer to our Idempotency docs for more information on using idempotency keys.
1 - 128Body
A request to create a disbursement.
The source from which to fund the disbursement.
The target receiving the disbursement.
- Disbursement Coinbase Target
- Disbursement Wallet Target
A decimal representation of the amount to disburse, denominated in asset.
"25.00"
The symbol of the asset for the disbursement amount.
1 - 42"usdc"
Human-readable reason for the disbursement.
"Goodwill disbursement for delayed shipment."
A merchant-provided internal identifier for this disbursement, from the merchant's own system—not visible to the payer. It must not contain personally identifiable information (PII) or payment credentials.
256"disbursement-2026-04-1234"
Optional customer-facing display data for this disbursement, shown to the payer. If referenceCode is omitted, one is auto-generated — disbursements have no payment session to fall back to, unlike every other action type.
Optional metadata as key-value pairs. Use this to store additional structured information on a resource, such as customer IDs, order references, or any application-specific data. Up to 10 key/value pairs may be provided. Keys and values are both strings. Keys must be ≤ 40 characters; values must be ≤ 500 characters.
Compliance context for this disbursement. Carries recipient information required by some entity configurations to meet regulatory requirements.
Response
Successfully created disbursement.
A Disbursement represents a merchant-initiated payment of funds from a CDP account they own to a Coinbase account or onchain address. Used for standalone refunds, goodwill disbursements, rebates, and other merchant-driven payouts that are not tied to a specific payment session.
Disbursements are asynchronous: the resource is returned in pending status and transitions to succeeded (with associated onchainTransactions) or failed (with error).
The unique identifier of the disbursement.
^disbursement_[a-f0-9\-]{36}$"disbursement_82c879c1-84e1-44ed-a8c2-1ac239cf09ad"
The source from which the disbursement is funded.
The target receiving the disbursement.
- Disbursement Coinbase Target
- Disbursement Wallet Target
A decimal representation of the disbursed amount, denominated in asset.
"25.00"
The symbol of the asset for the disbursement amount.
1 - 42"usdc"
The current status of the disbursement.
pending, succeeded, failed "pending"
The UTC ISO 8601 timestamp at which the disbursement was created.
"2026-04-17T17:00:00.000Z"
The UTC ISO 8601 timestamp at which the disbursement was last updated.
"2026-04-17T17:00:00.000Z"
Human-readable reason for the disbursement.
"Goodwill disbursement for delayed shipment."
A merchant-provided internal identifier for this disbursement, from the merchant's own system—not visible to the payer. It must not contain personally identifiable information (PII) or payment credentials.
256"disbursement-2026-04-1234"
Customer-facing display data for this disbursement, shown to the payer. Always present: if the create request omits referenceCode, one is auto-generated, since disbursements have no payment session to fall back to.
Optional metadata as key-value pairs. Use this to store additional structured information on a resource, such as customer IDs, order references, or any application-specific data. Up to 10 key/value pairs may be provided. Keys and values are both strings. Keys must be ≤ 40 characters; values must be ≤ 500 characters.
Error details, present only when the disbursement failed.
The onchain transactions associated with this disbursement.