Create a Payout

Facades: payout

Body Params
double
required

The payout amount in the requested currency. The minimum amount per instruction is $5 USD equivalent.

string
required

Currency code set for the payout amount (ISO 4217 3-character currency code).

string
required

Ledger currency code set for the payout (ISO 4217 3-character currency code), it indicates on which ledger the payout will be recorded. Supported ledger currency codes for payouts are EUR, USD, GBP, CAD, NZD, AUD, ZAR, JPY, BTC, BCH, GUSD, USDC, PAX, XRP, BUSD, DOGE, ETH, WBTC, DAI.

string

Present only if specified by the merchant in the request. Merchants can pass their own unique identifier in this field for reconciliation purposes or for querying. Maximum string length is 100 characters.

string

Merchant email address for notification of payout status change.

string

URL to which BitPay sends webhook notifications. If a notificationURL is not passed, the payout will default to using the merchant account level payout IPN if populated. This can be set by the following flow: Settings > General > Payout Settings > Payout IPN. HTTPS is mandatory.

string

Email address of a recipient. If the recipient email is not found, the recipient will be invited as well.

Note: In the future, BitPay may allow Recipients to update the email address tied to their personal account. BitPay encourages the use of recipientId or shopperId when programmatically creating payouts.

string

Bitpay recipient id of an active recipient, assigned by BitPay for a given recipient email during the onboarding process (see Recipients resource).

string

This is the unique id assigned by BitPay if the shopper used their personal BitPay account to authenticate and pay an invoice. For customers signing up for a brand new BitPay personal account, this id will only be created as part of the payout onboarding.

The same field would also be available on paid invoices if the customer signed in with their BitPay personal account before completing the payment. This can allow merchants to monitor the activity of a customer (deposits & payouts).

string

For merchant use, pass through - can be the customer name or unique merchant reference assigned by the merchant to to the recipient.

string

Effective date and time (UTC) for the payout. ISO-8601 date format yyyy-mm-dd. If not provided, defaults to date and time of creation.

boolean

Boolean to prevent email updates on a specific payout. Defaults to false if not provided - you will receive emails unless specified to true.

string
required

Approved payout facade token.

boolean
Defaults to false

Boolean to prevent payout requests to inactive recipients. Defaults to false if not provided - you will invite and create requests for all the provided email addresses unless specified to true.

Headers
string
required
Defaults to application/json

Must be set to application/json for requests to the BitPay API

string
required
Defaults to 2.0.0

Must be set to 2.0.0 for requests to the BitPay API

string
required

The hexadecimal public key generated from the client private key. This header is optional for this endpoint when using the public facade, and required when using a merchant facade token.

string
required

The ECDSA signature of the full request URL concatenated with the request body, signed with your private key. This header is optional for this endpoint when using the public facade, and required when using a merchant facade token.

Response

Language
Response
Choose an example:
application/json