Get payment corridor details
Returns availability, amount limits, and destination-specific data and compliance requirements for the selected corridor. Apply these alongside the baseline requirements in the payout schemas.
Identify the corridor using sourceCurrency, destinationCountry, and destinationCurrency.
Authorization
Default AuthorizationBearer <token>
In: header
Query Parameters
sourceCurrency*string
Funding currency.
destinationCountry*string
ISO 3166-1 alpha-2 destination country.
Match
^[A-Z]{2}$destinationCurrency*string
Destination currency to be delivered to the beneficiary.
Header Parameters
X-Request-Id?string
Optional request identifier for tracing and support. A UUID is recommended. Axiym echoes it in X-Request-Id, or generates one when omitted.
Format
uuidResponse Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json