Quote a payout
Lock a price against a real 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.
Headers
Idempotency-KeystringOptionalSame semantics as
Idempotency-Keyon the money routes (replay on the same body,409on a different one, released by a4xx), but optional here: without it the request simply runs once with no replay. EveryPOST,PATCHandDELETEhonors it; send one whenever your client might retry.
Body
This endpoint expects a JSON object.
amountstringRequiredDecimal string with at most six fractional digits. Its currency is selected by
amountLeg.destinationAccountIdstringRequiredFrom the recipient's
paymentMethods[].destinationAccountId.purposeOfPaymentstringOptionalCorridor-defined payment purpose, from
GET /payment-reasons. Required for payouts to INR, GHS, CNY and BRL (400 VALIDATION_ERRORnaming the field, before anything is priced); validated against the catalog whenever you send it; never defaulted. Do not invent a default for regulated payments.amountLegstringOptionalDefaults to"source"sourceprices the amount to debit.destinationlocks the amount the recipient receives in their currency.source_netstarts with an amount in your source currency, converts it at the published market rate, and locks that destination amount. The two exact-output modes requirecapabilities.exactOutput: truefrom the corridors call.Allowed values:sourcedestinationsource_net
Behavior
Returns a snapshot with the locked rate and the amount the recipient
receives. No money moves. Your caps and screening run here too, so
an over-cap amount or a refused recipient fails before a quote is
spent (422).
Where an underfunded balance fails depends on the environment. The
sandbox checks it here (400 BAD_REQUEST, "Insufficient USD balance
… Top up with POST …/sandbox/fund"). Live, the balance is held when
you accept the quote, so 400 INSUFFICIENT_BALANCE comes from
POST /quotes/accept or POST /payouts.
Quotes expire. Price and send close together.
Responses
200A locked quote snapshot
Body · QuoteSnapshot
idstringOptionalPass as
snapshotIdwhen sending.best_quote_idstringOptionalPass as
quoteIdwhen sending.expires_atstring<date-time>Optionalquotesarray of objectOptionalShow 6 properties
idstringOptionalinobjectOptionalShow 2 properties
amountstringOptionalcurrencystringOptional
outobjectOptionalShow 2 properties
amountstringOptionalcurrencystringOptional
feesobjectOptionalShow 2 properties
totalstringOptionalcurrencystringOptional
ratestringOptionalThe rail's own indicative rate, passed through for display. Its direction and whether the fee is inside it differ by rail, so do not expect
out = (in - fees.total) x rateto hold. Reconcile oninandout;Payout.rateis the one derived from the amounts.expires_atstring<date-time>Optional
Errors
400Nothing was sent.
VALIDATION_ERROR: a field is malformed;errorsnames it.QUOTE_NOT_POSITIVE: fees would leave the recipient with zero or less. Increase the amount and re-quote.EXACT_OUTPUT_UNSUPPORTED:amountLeg: destinationorsource_neton a routing withoutcapabilities.exactOutput.INDICATIVE_PRICING_UNAVAILABLE:amountLeg: source_neton a routing that publishes no market rate. SendamountLeg: destinationinstead.BAD_REQUEST: an unsupported corridor, an amount outside the corridor's minimum or maximum, or (sandbox only) an underfunded balance;detailsays which.IDEMPOTENCY_KEY_INVALID: a malformedIdempotency-Key.
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.
403USE_POST_PAYOUTS: this organization has an approval threshold or a velocity cap, and onlyPOST /payoutsenforces them. Nothing was sent; send the payout throughPOST /payouts, which may answer202 pending_approval. Also the refusals every write can answer:FORBIDDEN(a key for a different organization),ACCOUNT_BLOCKED,LIVE_KEY_ORG_NOT_APPROVEDandINSUFFICIENT_SCOPE.404DESTINATION_ACCOUNT_NOT_FOUND: no payment method with thisdestinationAccountIdbelongs to your organization. Nothing was sent. Use adestinationAccountIdfrom a recipient you created.422A control refused it and nothing was sent.
PAYOUT_LIMIT_EXCEEDED: over a single, daily, or per-end-user daily cap. The message names which; split it or ask us to raise the cap.PAYOUT_REFUSED: this payout cannot be sent to this recipient; do not retry, contact us with therequestId.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.
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?