Add a payment method
Add another way to pay an existing recipient.
Path parameters
orgIdstringRequiredThe opaque organization id issued to you, normally CUID-shaped (for example
cmsx…). It is not anorg_-prefixed alias. Pass it unchanged in every organization-scoped path.recipientIdstringRequiredOpaque recipient id returned by this API. Pass it unchanged.
Headers
Idempotency-KeystringRequiredA unique value per logical operation, 1-255 chars of
A-Z a-z 0-9 _ . : -.More
Reuse it to retry. Same key with the same body replays the stored response; same key with a different body is a
409, because answering with the first call's result would hand you a receipt for a payout you did not request. A4xxreleases the key, so you can fix the body and reuse it.Reuse it; do not generate one per attempt. A key minted per attempt defeats replay entirely: every retry looks like a new request, so every retry pays. We also watch for an identical body arriving under a different key within 15 minutes and refuse it with
DUPLICATE_REQUEST_DETECTED.Records are kept for 7 days. That is a retention window only: there is no path where an expired key is re-executed.
Body
This endpoint expects a JSON object.
Fiat bank destination
kindstringRequiredSend the literal string
fiatfor a bank destination.currencystringRequiredISO 4217 payout currency. Matching is case-insensitive.
railstringOptionalOptional. The corridor's payout rail. Omit it and the corridor's default rail is used, which is what almost every integration wants. It has no example, so a generated request does not carry one.
recipientDetailsobjectRequiredThe selected corridor's fields, keyed exactly by field
id. Values are normally strings; nested objects are accepted where the field definition represents a structured address. Fields in thebank_addressgroup (the recipient's own postal address, on corridors that require one) may be sent flat or nested underbank_address.
Cryptocurrency destination
kindstringRequiredSend the literal string
cryptofor a wallet destination.addressstringRequiredValid EVM, Solana, or Bitcoin address. Leading and trailing whitespace is ignored.
Behavior
Use this when the same person can be paid in more than one currency or over more than one rail. Creating a second recipient instead duplicates them in your book and in ours.
The response is the whole recipient, with method naming the one this
call added.
Responses
201The recipient, with method set to the payment method just added
Body · BeneficiaryRegistration
idstringOptionalnamestringOptionalemailstring | nullOptionalThe contact address you supplied, or null when none was sent.
countrystring | nullOptionalISO 3166-1 alpha-2. Null when none was stored (crypto recipients).
externalIdstring | nullOptionalYour id for the recipient, or null when none was sent.
endUserIdstring | nullOptionaltypestringOptionalAllowed values:individualbusinessphonestring | nullOptionalscreeningStatusstring | nullOptionalInternal compliance state. Returned today but not part of the contract, and it will be removed. Do not read it.
screeningReasonstring | nullOptionalInternal compliance state. Returned today but not part of the contract, and it will be removed. Do not read it.
screenedAtstring<date-time> | nullOptionalInternal compliance state. Returned today but not part of the contract, and it will be removed. Do not read it.
deletedAtstring<date-time> | nullOptionalAlways null on a read (deleted recipients are not returned). It will be removed.
createdAtstring<date-time>OptionalupdatedAtstring<date-time>OptionalorganizationIdstringOptionalThe organization id you authenticate with, the same one you put in the URL, for test and live keys alike.
paymentMethodsarray of objectOptionalShow 10 properties
idstringOptionalkindstringOptionalAllowed values:fiatcryptocurrencystring | nullOptionallast4string | nullOptionalstatusstringOptionalAllowed values:activependingfaileddestinationAccountIdstring | nullOptionalPass this as
destinationAccountIdwhen pricing a payout.addressstring | nullOptionalCrypto methods only. The destination wallet address.
chainstring | nullOptionalCrypto methods only. The network the address is on.
labelstring | nullOptionalrailstring | nullOptionalAn internal routing label. Returned today but not part of the contract, and it will be removed. Do not read it.
methodobjectOptionalThe payment method this call registered, or on a repeat the one it matched. Keep
method.destinationAccountId. Absent only if the call could not name a single method; then read the recipient again rather than choosing one.Show 6 properties
idstringOptionalkindstringOptionalcurrencystring | nullOptionallast4string | nullOptionalstatusstringOptionaldestinationAccountIdstring | nullOptional
Errors
400Validation failed, or a corridor field is missing
401The key was refused. Nothing ran.
UNAUTHORIZED: missing, invalid or revoked, or a key on a route that does not accept one.KEY_EXPIRED: the key passed the expiry it was issued with. Issue a new one; an expired key cannot be rotated.KEY_IP_NOT_ALLOWED: the key is pinned to source addresses and this request came from another.
403A valid key that may not make this write. Nothing was changed.
FORBIDDEN: the key belongs to a different organization.ACCOUNT_BLOCKED: API access for your organization is suspended.LIVE_KEY_ORG_NOT_APPROVED: a live key, before we have approved your business verification. Use a test key until then.INSUFFICIENT_SCOPE: a read-only key. Issue one with thewritescope.
404Unknown or deleted recipient
409BANK_ACCOUNT_ALREADY_LINKED: this bank account is already saved on a recipient (existingRecipientId,existingMethodId). Or an idempotency conflict (IDEMPOTENCY_KEY_CONFLICT,IDEMPOTENCY_KEY_REQUEST_IN_PROGRESS).429Too many requests. The default ceiling is 100 requests per minute per API credential on a 60-second window. High-volume payout and reconciliation routes declare a 600/minute override, and batch submission a 30/minute ceiling. A separate 2,000/minute per-source-IP abuse ceiling always applies.
Obey
Retry-After; it is in seconds and is authoritative. A 429 means the request was refused before the handler ran. Retry reads normally; retry an idempotent mutation with its sameIdempotency-Key.503Provider registration is temporarily unavailable; retry safely.
Error body · Error
typestringRequiredStable machine-readable code.
detailstringRequiredWhat went wrong, in a sentence. Always a string, so
detail.toLowerCase()is safe.More
This is the field to read on
BAD_REQUESTandPROVIDER_REJECTED, where the type alone does not name the condition.messagestringRequiredThe same text as
detail, kept for integrations written beforedetailexisted. Readdetail.resolutionstringOptionalWhat to do about it, when there is a specific answer. It is not on every error (it is absent on
BAD_REQUEST,NOT_FOUND,PAYOUT_NOT_CANCELABLEandDESTINATION_ACCOUNT_NOT_FOUND), so treat it as optional and fall back todetail.statusintegerRequiredHTTP status, repeated in the body.
statusCodeintegerRequiredThe same value as
status, kept for integrations written beforestatusexisted. Readstatus.requestIdstringRequiredQuote this to support and we can find the exact request. Also sent as the
x-request-idresponse header, which is the only place it appears on a successful response. Success bodies do not carry it. Send your ownx-request-idon the request and we use it, so your trace and ours share one identifier; otherwise we mint one.errorsarray of stringOptionalPresent on VALIDATION_ERROR; names each field that failed.
originalIdempotencyKeystringOptionalOn
DUPLICATE_REQUEST_DETECTEDonly. Send the request again with this to receive the original payout instead of making a second one. Without it there is no way to recover except by risking a double payment.originalPayoutIdstringOptionalOn
DUPLICATE_REQUEST_DETECTEDonly. The payout the first request created.originalBatchIdstringOptionalOn a batch
DUPLICATE_REQUEST_DETECTED. The run the first request created.originalRequestIdstringOptionalOn a
409 PAYOUT_OUTCOME_UNKNOWNreplay. TherequestIdof the call whose outcome is unknown; quote it to support.existingRecipientIdstringOptionalOn
BANK_ACCOUNT_ALREADY_LINKED. The recipient in your organization that already holds this account.existingMethodIdstringOptionalOn
BANK_ACCOUNT_ALREADY_LINKED. The payment method on that recipient.
Branch on type, never on the status or the message. Every error type is listed with what to do about it.
Was this page helpful?