Country coverage

Required in paymentMethod is what that corridor's schema demands beyond type and countryCode, labelled by payout method; Also required covers everything outside paymentMethod. Country names link to a complete, validated request body.

Confirm against GET /schema/{countryCode} — see Schemas — before going live. The schema is authoritative on field-level requirements, and corridors change.

Every corridor listed here has been validated end to end. GET /schema/{countryCode} may return a schema for a country that is not in this table — a schema defines the payload shape, it does not mean the corridor is ready to carry money. Treat anything missing here as unavailable until your Inyo contact confirms otherwise.

Coverage is not the same as enablement. A country here has a schema; whether your account has a route to it is separate. A valid payload to an unrouted corridor fails with PAY_001.

Reading the table

• additionalData on its own means the schema requires the object to be present but demands nothing inside it — send "additionalData": {}.
• (on Bank) / (on Wallet) marks a requirement that applies to only one payout method in that corridor, expressed in the schema as an if/then conditional.
• accountNumberType appears only on the alias rails because it is the field that selects the rail, not one the schema demands. Sending it is how you choose the alias rail; omit it and the corridor takes its conventional one — see Bank deposit.
• A dash in Required in paymentMethod means the schema pins formats but marks no field required. You still need an account identifier for the payout to reach anyone.

What's Next

• Examples — Complete request bodies, grouped by region
• Payout methods — Field reference per payout type