Discover payout requirements
Returns the fields[] a payout body must carry for a given (purpose, rail, recipientType) — the top-level virtualAccountId to debit (fiat), the destination.* discriminators, and the recipient fields — plus whether a supporting document is required (and the accepted types), whether the recipient must be whitelisted/registered first (intercompany payouts), and the jurisdictions payouts are blocked to. Build a valid POST /v2/payouts body from this response. documentation.required is a baseline for the purpose alone. The answer a given customer gets can differ from it in either direction, because it also depends on that customer and on the payout itself, and the create request enforces that answer. For the customer-specific answer before you submit, send the candidate payout body to POST /v2/payouts/requirements. documentation.due does reflect your organization: due: pre_acceptance means a payout carrying no document is rejected with 422 DOCUMENTATION_REQUIRED, so collect the document before you submit; due: post_acceptance means the payout is accepted without one, an rfi.published webhook asks you for the document, the read-back shows stage: awaiting_customer_action with hasRfi: true, and the payout stays held, with its amount still reserved, until you answer, rejected only if the document you send is declined. An organization with no portal user reads due: pre_acceptance, since nobody can receive the request. (due and whitelist are purpose-invariant and match enforcement exactly.)
Authorizations
Query Parameters
Declared business purpose of the payout. Drives the documentation and whitelist requirements. A chaps query cannot declare other: the CHAPS scheme carries an ISO 20022 purpose code and other names none.
intercompany, treasury_management, payment_for_goods_or_services, payroll, investments, other, prefunding Payout rail. crypto for an on-chain withdrawal; fedwire/rtp/fednow/ach/swift/sepa for fiat. Input is case-insensitive.
crypto, fedwire, rtp, fednow, ach, swift, sepa, faster_payments, chaps Whether the fiat recipient is an individual or a business. Required for fiat rails, forbidden for crypto.
individual, business Beneficiary country ISO 3166-1 alpha-2 or alpha-3 code. Informational: requirements are selected by rail (domestic rails always target a US account; swift and sepa are country-agnostic). Forbidden for crypto.
Response
The rail this answer describes, echoing the rail the query named.
crypto, fedwire, rtp, fednow, ach, swift, sepa, faster_payments, chaps Countries this rail cannot pay to, as ISO 3166-1 alpha-3 codes. A payout whose recipient country appears here is rejected.
AFG, ALB, DZA, ASM, AND, AGO, AIA, ATA, ATG, ARG, ARM, ABW, AUS, AUT, AZE, BHS, BHR, BGD, BRB, BLR, BEL, BLZ, BEN, BMU, BTN, BOL, BES, BIH, BWA, BVT, BRA, IOT, BRN, BGR, BFA, BDI, CPV, KHM, CMR, CAN, CYM, CAF, TCD, CHL, CHN, CXR, CCK, COL, COM, COG, COD, COK, CRI, CIV, HRV, CUB, CUW, CYP, CZE, DNK, DJI, DMA, DOM, ECU, EGY, SLV, GNQ, ERI, EST, SWZ, ETH, FLK, FRO, FJI, FIN, FRA, GUF, PYF, ATF, GAB, GMB, GEO, DEU, GHA, GIB, GRC, GRL, GRD, GLP, GUM, GTM, GGY, GIN, GNB, GUY, HTI, HMD, VAT, HND, HKG, HUN, ISL, IND, IDN, IRN, IRQ, IRL, IMN, ISR, ITA, JAM, JPN, JEY, JOR, KAZ, KEN, KIR, PRK, KOR, KWT, KGZ, LAO, LVA, LBN, LSO, LBR, LBY, LIE, LTU, LUX, MAC, MDG, MWI, MYS, MDV, MLI, MLT, MHL, MTQ, MRT, MUS, MYT, MEX, FSM, MDA, MCO, MNG, MNE, MSR, MAR, MOZ, MMR, NAM, NRU, NPL, NLD, NCL, NZL, NIC, NER, NGA, NIU, NFK, MKD, MNP, NOR, OMN, PAK, PLW, PSE, PAN, PNG, PRY, PER, PHL, PCN, POL, PRT, PRI, QAT, REU, ROU, RUS, RWA, BLM, SHN, KNA, LCA, MAF, SPM, VCT, WSM, SMR, STP, SAU, SEN, SRB, SYC, SLE, SGP, SXM, SVK, SVN, SLB, SOM, ZAF, SGS, SSD, ESP, LKA, SDN, SUR, SJM, SWE, CHE, SYR, TWN, TJK, TZA, THA, TLS, TGO, TKL, TON, TTO, TUN, TUR, TKM, TCA, TUV, UGA, UKR, ARE, GBR, USA, UMI, URY, UZB, VUT, VEN, VNM, VGB, VIR, WLF, ESH, YEM, ZMB, ZWE