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. The documentation block is the default policy baseline and does not reflect per-customer exceptions or enforce-mode carve-outs (amount-triggered EDD, CRR-band mappings); the customer’s actual requirement is enforced by the create request, which rejects with 422 DOCUMENTATION_REQUIRED (listing the accepted document types) when a document is required and none is attached. (whitelist is purpose-invariant and matches enforcement exactly.)
Authorizations
Query Parameters
Declared business purpose of the payout. Drives the documentation and whitelist requirements.
intercompany, treasury_management, payment_for_goods_or_services, payroll, investments, other, prefunding Payout rail. crypto for an on-chain withdrawal; fedwire/rtp/fednow/swift for fiat. Input is case-insensitive.
crypto, fedwire, rtp, fednow, swift 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 is country-agnostic). Forbidden for crypto.