Inyo

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.

CountryISO3CurrencyRequired in paymentMethodAlso required
AndorraANDEURBank: accountNumberβ€”
AustriaAUTEURBank: accountNumberβ€”
BangladeshBGDBDTBank: accountNumber, bankCode
Wallet: walletId, walletOperator, walletType
additionalData.paymentPurpose (on Bank)
BelgiumBELEURBank: accountNumberβ€”
BrazilBRABRLBank: accountNumber, accountType, bankCode, routingNumber
PIX: key, keyType
recipient.address
recipient.documents
additionalData
BulgariaBGRBGNBank: accountNumberβ€”
CanadaCANCADBank: accountNumberrecipient.address
additionalData.paymentPurpose
ChileCHLCLPBank: accountNumber, accountType, bankCoderecipient.address
recipient.documents
ChinaCHNCNYWallet: walletId, walletOperator, walletTypeadditionalData.paymentPurpose
ColombiaCOLCOPBank: accountNumberrecipient.address
recipient.documents
recipient.email
additionalData.paymentPurpose
CyprusCYPEURBank: accountNumberβ€”
CΓ΄te d'IvoireCIVXOFWallet: walletId, walletOperator, walletTypeβ€”
EgyptEGYEGPBank: accountNumberadditionalData.paymentPurpose
EstoniaESTEURBank: accountNumberβ€”
FinlandFINEURBank: accountNumberβ€”
FranceFRAEURBank: accountNumberβ€”
GermanyDEUEURBank: accountNumberβ€”
GreeceGRCEURBank: accountNumberβ€”
GuineaGINGNFWallet: walletId, walletOperator, walletTypeβ€”
IcelandISLEURBank: accountNumberβ€”
IndiaINDINRBank Β· BBAN: accountNumber, accountNumberType, accountType, bankCode
Bank Β· UPI: accountNumber, accountNumberType
recipient.address
additionalData.paymentPurpose
IndonesiaIDNIDRBank: accountNumber, bankCodeadditionalData.paymentPurpose
IrelandIRLEURBank: accountNumberβ€”
ItalyITAEURBank: accountNumberβ€”
KenyaKENKESBank: accountNumber, bankCode
Wallet: walletId, walletOperator, walletType
recipient.address (on Bank)
recipient.documents (on Bank)
LatviaLVAEURBank: accountNumberβ€”
LiechtensteinLIECHFBank: accountNumberβ€”
LithuaniaLTUEURBank: accountNumberβ€”
LuxembourgLUXEURBank: accountNumberβ€”
MadagascarMDGMGAWallet: walletId, walletOperator, walletTypeβ€”
MalaysiaMYSMYRBank: accountNumber, bankCoderecipient.address
additionalData.paymentPurpose
MaliMLIXOFWallet: walletId, walletOperator, walletTypeβ€”
MaltaMLTEURBank: accountNumberβ€”
MexicoMEXMXNBank Β· BBAN: accountNumber, accountNumberType
Bank Β· DIMO: accountNumber, accountNumberType, bankCode
recipient.address
additionalData
MonacoMCOEURBank: accountNumberβ€”
MongoliaMNGMNTBank: accountNumberrecipient.address
recipient.phoneNumber
MoroccoMARMADBank: accountNumberadditionalData
NepalNPLNPRBank: accountNumberrecipient.address
additionalData.paymentPurpose
NetherlandsNLDEURBank: accountNumberβ€”
NigeriaNGANGNWallet: walletId, walletOperator, walletTypeβ€”
PakistanPAKPKRBank: accountNumber, bankCoderecipient.address
additionalData.paymentPurpose
PhilippinesPHLPHPBank: accountNumber, bankCode
Wallet: walletId, walletOperator, walletType
additionalData.paymentPurpose (on Bank)
PortugalPRTEURBank: accountNumberβ€”
San MarinoSMREURBank: accountNumberβ€”
SingaporeSGPSGDBank: accountNumber, bankCoderecipient.address
additionalData.paymentPurpose
SlovakiaSVKEURBank: accountNumberβ€”
SloveniaSVNEURBank: accountNumberβ€”
South KoreaKORKRWBank: accountNumberrecipient.address
recipient.phoneNumber
additionalData.paymentPurpose
SpainESPEURBank: accountNumberβ€”
Sri LankaLKALKRBank: accountNumber, bankCode, routingNumberrecipient.address
SwitzerlandCHECHFBank: accountNumberβ€”
ThailandTHATHBBank: accountNumber, bankCodeadditionalData.paymentPurpose
The GambiaGMBGMDWallet: walletId, walletOperator, walletType
Bank: accountNumber
additionalData.paymentPurpose
TurkeyTURTRYBank: accountNumberrecipient.address
recipient.documents
United KingdomGBRGBPBank Β· BBAN: accountNumber, accountNumberType, bankCode
Bank Β· IBAN: accountNumber, accountNumberType
β€”
UzbekistanUZBUZSCARD: cardTokenIdβ€”
VietnamVNMVNDBank: accountNumber, bankCoderecipient.address
additionalData.paymentPurpose

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.
  • 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