Country requirements vary with the destination country and the transaction rail. You do not
need to know the field names in advance: find the destination country below and expand it to
see the requirements that apply when the transaction is processed through the SWIFT network.
As with the currency rules, these qualify Conditional fields only — fields marked
Mandatory in the Payout API must always be supplied.
Note
RHUB's own wording for these rules is reproduced below, unchanged.
Fields marked as Mandatory in the Payout Api must always be provided, irrespective of whether the correspondent requires them or not. These fields are enforced at the application level and are non-negotiable.
Fields marked as Conditional are subject to correspondent-specific requirements. Such fields are mandatory only when explicitly required by the selected correspondent, as described in the corresponding conditions section below.
Users are required to validate and comply with correspondent rules only for fields marked as Conditional in the Payout Api. Mandatory fields defined in this documentation(Payout Api) take precedence and must be supplied in all cases.
SWIFT Transaction Requirements
AR – Argentina, BB – Barbados, BM – Bermuda, BN – Brunei, BS – Bahamas, CO – Colombia, DZ – Algeria, EC – Ecuador, FJ – Fiji, HN – Honduras, JM – Jamaica, JP – Japan, KE – Kenya, KR – South Korea, KY – Cayman Islands, MO – Macao, MW – Malawi, NG – Nigeria, NI – Nicaragua, NP – Nepal, NZ – New Zealand, PE – Peru, SZ – Eswatini, TH – Thailand, UG – Uganda, ZA – South Africa
For the countries listed above, when transactions are processed through the SWIFT network, the following bank-related fields are mandatory for successful transaction processing:
businessBankName, receiverBankName - used to capture Bank name details
businessAccountNumber, receiverAccountNumber - used to capture Bank Account Number details
businessSwiftCode, receiverSwiftCode - used to capture Swift Code details
businessAccountHolderName, receiverAccountHolderName – used to capture beneficiary name details
In the table below, the column headers represent the applicable API field requirements for both business and customer contexts.
note
Note: “YES” indicates that the field is mandatory and accepts the value/information specified above. If a different value/information is accepted, it is explicitly mentioned in the table. “NO” indicates that it is optional.
AE – United Arab Emirates, AL – Albania, AT – Austria, BE – Belgium, BG – Bulgaria, BH – Bahrain, CH – Switzerland, CR – Costa Rica, CY – Cyprus, CZ – Czech Republic, DE – Germany, DK – Denmark, EE – Estonia, ES – Spain, FI – Finland, FR – France, GR – Greece, GT – Guatemala, HR – Croatia, HU – Hungary, IE – Ireland, IL – Israel, IT – Italy, JO – Jordan, KW – Kuwait, KZ – Kazakhstan, LB – Lebanon, LI – Liechtenstein, LT – Lithuania, LU – Luxembourg, LV – Latvia, MC – Monaco, MT – Malta, MU – Mauritius, MZ – Mozambique, NL – Netherlands, NO – Norway, OM – Oman, PK – Pakistan, PL – Poland, PT – Portugal, QA – Qatar, RO – Romania, RS – Serbia, SA – Saudi Arabia, SE – Sweden, SI – Slovenia, SK – Slovakia, TN – Tunisia, TR – Turkey, UA – Ukraine
For the countries listed above, when transactions are processed through the SWIFT network, the following bank-related fields are mandatory for successful transaction processing:
businessBankName, receiverBankName – used to capture bank name details
businessAccountNumber, receiverAccountNumber – used to capture IBAN details
businessSwiftCode, receiverSwiftCode – used to capture SWIFT code details
businessAccountHolderName, receiverAccountHolderName – used to capture beneficiary name details
In the table below, the column headers represent the applicable API field requirements for both business and customer contexts.
note
Note: “YES” indicates that the field is mandatory and accepts the value/information specified above. If a different value/information is accepted, it is explicitly mentioned in the table. “NO” indicates that it is optional.
For the countries listed above, when transactions are processed through the SWIFT network, the following bank-related fields are mandatory for successful transaction processing:
businessBankName, receiverBankName – used to capture bank name details
businessAccountNumber, receiverAccountNumber – used to capture bank account number details
businessSwiftCode, receiverSwiftCode – used to capture SWIFT code details
businessBankCode, receiverBankCode – used to capture bank sort code details
businessAccountHolderName, receiverAccountHolderName – used to capture beneficiary name details
In the table below, the column headers represent the applicable API field requirements for both business and customer contexts.
note
Note: “YES” indicates that the field is mandatory and accepts the value/information specified above. If a different value/information is accepted, it is explicitly mentioned in the table. “NO” indicates that it is optional.
LK – Sri Lanka, MA – Morocco, TT – Trinidad and Tobago
For the countries listed above, when transactions are processed through the SWIFT network, the following bank-related fields are mandatory for successful transaction processing:
businessBankName, receiverBankName – used to capture bank name details
businessAccountNumber, receiverAccountNumber – used to capture bank account number details
businessSwiftCode, receiverSwiftCode – used to capture SWIFT code details
businessBankCode, receiverBankCode – used to capture bank code details
businessBankCountry, receiverBankCountry – used to capture branch code details
businessAccountHolderName, receiverAccountHolderName – used to capture beneficiary name details
In the table below, the column headers represent the applicable API field requirements for both business and customer contexts.
note
Note: “YES” indicates that the field is mandatory and accepts the value/information specified above. If a different value/information is accepted, it is explicitly mentioned in the table. “NO” indicates that it is optional.
For the countries listed above, when transactions are processed through the SWIFT network, the following bank-related fields are mandatory for successful transaction processing:
businessAccountHolderName, receiverAccountHolderName – used to capture beneficiary name details
businessBankName, receiverBankName – used to capture bank name details
businessAccountNumber, receiverAccountNumber – used to capture bank account number details
businessSwiftCode, receiverSwiftCode – used to capture SWIFT code details
In the table below, the column headers represent the applicable API field requirements for both business and customer contexts.
note
Note: “YES” indicates that the field is mandatory and accepts the value/information specified above. If a different value/information is accepted, it is explicitly mentioned in the table. “NO” indicates that it is optional.
For the countries listed above, when transactions are processed through the SWIFT network, the following bank-related fields are mandatory for successful transaction processing:
businessBankName, receiverBankName – used to capture bank name details
businessAccountNumber, receiverAccountNumber – used to capture bank account number details
businessSwiftCode, receiverSwiftCode – used to capture SWIFT code details
businessBankCode, receiverBankCode – used to capture bank code details
businessAccountHolderName, receiverAccountHolderName – used to capture beneficiary name details
In the table below, the column headers represent the applicable API field requirements for both business and customer contexts.
note
Note: “YES” indicates that the field is mandatory and accepts the value/information specified above. If a different value/information is accepted, it is explicitly mentioned in the table. “NO” indicates that it is optional.
For the countries listed above, when transactions are processed through the SWIFT network, the following bank-related fields are mandatory for successful transaction processing:
businessBankName, receiverBankName – used to capture bank name details
businessAccountNumber, receiverAccountNumber – used to capture bank account number details
businessSwiftCode, receiverSwiftCode – used to capture SWIFT code details
businessAccountType, receiverAccountType – used to capture account type details
businessAccountHolderName, receiverAccountHolderName – used to capture beneficiary name details
In the table below, the column headers represent the applicable API field requirements for both business and customer contexts.
note
Note: “YES” indicates that the field is mandatory and accepts the value/information specified above. If a different value/information is accepted, it is explicitly mentioned in the table. “NO” indicates that it is optional.
AU – Australia, BR – Brazil, CA – Canada, CL – Chile, EG – Egypt, ID – Indonesia, IN – India, IS – Iceland, MX – Mexico, PH – Philippines, SG – Singapore, US – United States
For the countries listed above, when transactions are processed through the SWIFT network, the following bank-related fields are mandatory for successful transaction processing:
businessBankName, receiverBankName – used for Bank name details
businessAccountNumber, receiverAccountNumber – used for Bank Account Number details
businessSwiftCode, receiverSwiftCode – used for Swift Code details
businessBankCountry, receiverBankCountry – used to capture branch code details
businessBankCode, receiverBankCode – used to capture bank code/ IFSC/ BSB NO/ Routing no details based on country
businessAccountType, receiverAccountType – used to capture account type details
businessAccountHolderName, receiverAccountHolderName – used to capture beneficiary name details
In the table below, the column headers represent the applicable API field requirements for both business and customer contexts.
note
Note: “YES” indicates that the field is mandatory and accepts the value/information specified above. If a different value/information is accepted, it is explicitly mentioned in the table. “NO” indicates that it is optional.