Skip to main content
GET
Get the field requirements for a payout corridor

Authorizations

Authorization
string
header
required

Enter Auth0 JWT token

Query Parameters

currency
string
required

Destination currency (e.g. NGN, EUR, USD, GBP)

Pattern: ^[A-Za-z]{3,10}$
Example:

"EUR"

route
enum<string>

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.

Available options:
sepa_inst,
sepa_credit,
bank_transfer,
ach,
fedwire,
swift,
crypto,
mobile_money
Example:

"swift"

country
string

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.

Pattern: ^[A-Za-z]{2}$
Example:

"CM"

Response

Field requirements for both parties of a payout into the corridor

beneficiary
object
required

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.

sender
object
required

What the originator must and may carry, for each sender type, and whether senderInfo can be omitted at all.