Get the field requirements for a payout corridor
Returns what a payout into a corridor requires of both parties: the beneficiary fields and the senderInfo keys that must and may be provided, reported for an individual and for a business of each party so a caller never has to declare one type to learn the other. Pass route (and, for mobile money or SWIFT, country) to narrow the answer to one corridor; without them it is combined across every rail serving the currency, so satisfying it satisfies the most demanding one. For the recipient it also reports the rules a field value must satisfy, such as an individual name that must split into a first and a last name, as a pattern to validate against before submitting. Each rule is enforced at submit with a 400 naming the field and carrying a stable code; without route, a combined rule is enforced only where the provider that pays out applies it.
Authorizations
Enter Auth0 JWT token
Query Parameters
Destination currency (e.g. NGN, EUR, USD, GBP)
^[A-Za-z]{3,10}$"EUR"
The rail the payout will take, as sent on POST /v1/payouts. Narrows both parties to the rules of that corridor: without it the answer is combined across every rail serving the currency, so satisfying it satisfies the most demanding one.
sepa_inst, sepa_credit, bank_transfer, ach, fedwire, swift, crypto, mobile_money "swift"
An ISO 3166-1 alpha-2 country code. With route=mobile_money it is the destination country, and narrows rules that apply to one country of a currency, such as the sender phone a mobile-money payout into Cameroon carries. With route=swift it is the beneficiary's country, which decides the provider that pays out and so the recipient rules that apply. Ignored on any other rail, and ignored when no route is named.
^[A-Za-z]{2}$"CM"
Response
Field requirements for both parties of a payout into the corridor
What the recipient must and may carry, for each recipient type: the fields that must and may be provided, and the rules their values must satisfy, such as a corridor that addresses an individual recipient by first and last name separately.
What the originator must and may carry, for each sender type, and whether senderInfo can be omitted at all.