File Based Payouts

You can instruct a payout through a file based upload in the portal or through a secure file transfer (SFTP). The file must capture all the required fields as per the guidance below (some mandatory fields will vary depending on the country - see the country coverage guide for more details). If any mandatory fields are not captured, the entire file will be rejected.

Create a batch of up to 5000 payouts within the file and initiate a single request to have these processed.

Requirements

Payout files must be:

  • submitted as CSV (Comma Separated Value) files
  • submitted using a different file name each time
  • using type "text" when using Microsoft Excel - failure to do this, may result in leading zeros within fields such as 'accountNumber' being removed
Note

Field Names starting with remitter_ should only be provided when additional information about the party, sending the funds, is required. This information is communicated during the onboarding process.

Payout level parameters

Field NameDescriptionData Type/FormatRequired?Min-Max LengthValidation Criteria
entityThis 6-digit reference is given to you by your Implementation Manager during the onboarding process.ANConditional6Special characters are restricted. The value supplied is checked to be valid. It must also match the entity for which authorization has been supplied.
transactionReferenceUnique reference for the payout request provided by you.AN6-50Special characters are allowed.
countryCodeCountry code of the payout destination.A2ISO 3166-1 Alpha-2 code
sourceCurrencySource currency for the payout (if different to target currency FX is applied).A3ISO 4217

Valid currency codes.
sourceAmountSource amount (if target amount is not stated, this amount is used). FX rate of the payout is applied by us, therefore, only one of the sourceAmount or targetAmount is required in your request.NConditional1-10Must be a positive value up to 2 decimal places.
targetCurrencyTarget currency sent in the payout request (if different to source currency FX, is applied).A3ISO 4217

Valid currency codes.
targetAmountTarget amount (if source amount is not specified, this amount is used). FX rate of the payout is applied by us, therefore, only one of the sourceAmount or targetAmount is required in your request.NConditional1-10Must be a positive value up to 2 decimal places.
narrativeReference that may appear on beneficiary statements.String6-50Special characters are allowed.
purposeOfPaymentCodeThe code that represents the purpose of payment. This is mandatory for some payout routes - please check country specific requirements.AValueFor the full list of values see the appendix.
purposeOfPaymentNarrativeDescription for purpose of payment.String1-35Special characters are allowed.
fastPaymentFlag for a fast payment. If a value is provided, it must always be "Y".AValueThe value supplied for the field must be "Y" or left blank.
transactionTypeCodeType of transaction code (for example "TT04" that refers to "Business to Customer"). This is mandatory for some payout routes - please check country specific requirements.ANValueFor the full list of values see the appendix.
channelPreferable channel for the payment (for example "WIRE").AValueFor the full list of values see the appendix.
quoteIdID of the FX quote for the payment request. This must be a valid, active quote which is for the same source and target currencies as the payout request. It must have valid intent of "FORWARD FX" or "PAYOUT".String
scheduleDateScheduled date of the payout request.date10Must be a Gregorian calendar date with ISO format 8601 YYYY-MM-DD
bankDetails_beneficiaryAccountTypeCodeType of account code (for example "AC01" that refers to "Checking").ANValueFor the full list of allowed values see the appendix.
bankDetails_beneficiaryAccountNumberBeneficiary bank account number. You must either provide an account number or an IBAN.StringConditional1-35Special characters are allowed.
bankDetails_ibanBeneficiary IBAN. You must either provide an account number or an IBAN.ANConditional1-34
bankDetails_branchCodeBeneficiary account branch code.String1-35Special characters are allowed.
bankDetails_bankCodeBeneficiary account bank code.String1-35Special characters are allowed.
bankDetails_swiftBicBeneficiary bank account SWIFT/BICAN8 or 11Special characters are allowed.
bankDetails_bankNameBeneficiary bank nameString1-35Special characters are allowed.
bankDetails_address_streetStreet address of the beneficiary's bank.String1-35Special characters are allowed.
bankDetails_address_additionalAddressLineAdditional address line of the beneficiary's bank.String1-35Special characters are allowed
bankDetails_address_cityCity of the beneficiary's bank.String1-35Special characters are allowed
bankDetails_address_stateState or province of the beneficiary's bank.String2-35Special characters are allowed
bankDetails_address_postCodeOrZipCodePostcode or ZipCode of the beneficiary's bank.String1-35Special characters are allowed
bankDetails_address_countryCodeCountry code of the beneficiary's bank.A2ISO 3166-1 Alpha-2 code
beneficiary_customerPartyIdThe ID of the remitter: Domain ID, Account Number, Tax ID, BIC, Internal Customer ID or any other numerical or alphanumerical unique identifier of the customer where the payment request has originated. This field will be available for use as part of the future enhancements to the Account Payouts API in 2025AN1-35Special characters are restricted. Value supplied must be in the format of 1-35 alphanumeric characters.
beneficiary_typeCodeEntity description code for the beneficiary (for example "PD02" that refers to "Individual").ANValueFor the full list of allowed values see the appendix.
beneficiary_titleCodeTitle code for the Individual (applicable if beneficiary_typeCode is "Individual"). Must not be provided when type is not "Individual".ANConditionalValueFor the full list of allowed values see the appendix.
beneficiary_firstNameFirst name of the beneficiary. Mandatory if beneficiary_typeCode is "Individual".ANConditional1-50Special characters are allowed.
See formatting rules
beneficiary_middleNameMiddle name of the beneficiary (applicable if beneficiary_typeCode is "Individual").AN1-50Special characters are allowed.
See formatting rules
beneficiary_lastNameLast name of the beneficiary. Mandatory if beneficiary_typeCode is is "Individual".ANConditional1-50Special characters are allowed.
See formatting rules
beneficiary_companyNameName of the party if not an individual. Mandatory if beneficiary_typeCode is "Institution", "Government" or "Company". Must not be provided when type is "Individual".StringConditional1-140Special characters are allowed.
beneficiary_dateOfBirthDate of birth or date of incorporation of the beneficiary.Date10Must be a Gregorian calendar date with ISO 8601 format YYYY-MM-DD.
beneficiary_emailE-mail address of the beneficiary. This field will be available for use as part of the future enhancements to the Account Payouts API in 2025StringA valid e-mail address format
beneficiary_telephony_phoneNumberPhone number of the beneficiary. Mandatory if prefix has been provided.NConditional1-20Special characters are restricted.
beneficiary_telephony_prefixPhone dialing country code of the beneficiary. Mandatory if phoneNumber has been provided.NConditional1-3Special characters are restricted.

International country calling code following ITU-T standard.

Must be 1-3 digits
e.g. "44" or "420"
beneficiary_identity_identityTypeCodeType of identification. Mandatory if identityNumber is populated.ANConditionalValueFor the full list of allowed values see the appendix.
beneficiary_identity_identityNumberIdentification number that is presented in the identification type. Mandatory if IdentityTypeCode is populated.StringConditional1-35Special characters are allowed.
beneficiary_identity_issuingCountryCountry of identification type origin. Mandatory if identityTypeCode/identityNumber is populated.AConditional2ISO 3166-1 Alpha-2 code
beneficiary_identity_issuingInstitutionIssuing institution that provided identification type.String1-35Special characters are allowed. Cannot be provided if the conditional fields in the identity section are missing.
beneficiary_identity_startDateIdentification type start date.Date10Must be a Gregorian calendar date with ISO 8601 format YYYY-MM-DD. Cannot be provided if conditional fields in the identity section are missing.
beneficiary_identity_endDateIdentification type end date.Date10Must be a Gregorian calendar date with ISO 8601 format YYYY-MM-DD. Cannot be provided if conditional fields in the identity section are missing.
beneficiary_address_addressTypeCodeType of beneficiary address code (for example "AD02" that refers to "Business").ANValueFor the full list of allowed values see the appendix.
beneficairy_address_streetStreet address of the beneficiary.String1-35Special characters are allowed.
beneficiary_address_additionalAddressLineAdditional address line of the beneficiary.String1-35Special characters are allowed.
beneficiary_address_cityCity of the beneficiary's address.String1-35Special characters are allowed.
beneficiary_address_stateState or province of the beneficiary's address.String2-35Special characters are allowed.
beneficiary_address_postCodeOrZipCodePostcode/ZipCode of the beneficiary's address.String1-35Special characters are allowed.
beneficiary_address_countryCodeCountry code (for example "GB") of the beneficiary address.A2ISO 3166-1 Alpha-2 code
beneficiary_address_residentialStatusCodeType of residency code (for example "RS01" that refers to "Resident").ANValueFor the full list of allowed values see the appendix.
remitter_customerPartyIdThe ID of the remitter: Domain ID, Account Number, Tax ID, BIC, Internal Customer ID or any other numerical or alphanumerical unique identifier of the customer where the payment request has originated. This field will be available for use as part of the future enhancements to the Account Payouts API in 2025AN1-35Special characters are restricted. Value supplied must be in the format of 1-35 alphanumeric characters.
remitter_typeCodeEntity description code for the remitter (for example "PD02" that refers to "Individual").ANValueFor the full list of allowed values see the appendix.
remitter_titleCodeTitle code for the Individual (applicable if remitter_typeCode is "Individual"). Must not be provided when type is not "Individual".ANConditionalValueFor the full list of allowed values see the appendix.
remitter_firstNameFirst name of the remitter. Mandatory if remitter_typeCode is "Individual".ANConditional1-50Special characters are allowed.
See formatting rules
remitter_middleNameMiddle name of the remitter (applicable if remitter_typeCode is "Individual").AN1-50Special characters are allowed.
See formatting rules
remitter_lastNameLast name of the remitter. Mandatory if remitter_typeCode is "Individual".ANConditional1-50Special characters are allowed.
See formatting rules
remitter_companyNameName of the party if not an individual. Mandatory if remitter_typeCode is "Institution", "Government" or "Company". Must not be provided when type is "Individual".StringConditional1-140Special characters are allowed.
remitter_dateOfBirthDate of birth or date of incorporation of the remitter.Date10Must be a Gregorian calendar date with ISO 8601 format YYYY-MM-DD.
remitter_emailE-mail address of the remitter. This field will be available for use as part of the future enhancements to the Account Payouts API in 2025StringA valid e-mail address format
remitter_telephony_phoneNumberPhone number of the remitter. Mandatory if prefix has been provided.NConditional1-20Special characters are restricted.
remitter_telephony_prefixPhone dialing country code of the remitter. Mandatory if phoneNumber has been provided.NConditional1-3Special characters are restricted.

International country calling code following ITU-T standard.

Must be 1-3 digits
e.g. "44" or "420"
remitter_identity_identityTypeCodeType of identification. Mandatory if identityNumber is populated.ANConditionalValueFor the full list of allowed values see the appendix.
remitter_identity_identityNumberIdentification number that is presented in the identification type. Mandatory if identityTypeCode is populated.StringConditional1-35Special characters are allowed.
remitter_identity_issuingCountryCountry of identification type origin. Mandatory if identityTypeCode/identityNumber is populated.AConditional2ISO 3166-1 Alpha-2 code
remitter_identity_issuingInstitutionIssuing institution that provided identificationType.String1-35Special characters are allowed. Cannot be provided if the conditional fields in the identity section are missing.
remitter_identity_startDateIdentification type start date.Date10Must be a Gregorian calendar date with ISO 8601 format YYYY-MM-DD. Cannot be provided if conditional fields in the identity section are missing.
remitter_identity_endDateIdentification type end date.Date10Must be a Gregorian calendar date with ISO 8601 format YYYY-MM-DD. Cannot be provided if conditional fields in the identity section are missing.
remitter_address_addressTypeCodeType of remitter address code (for example "AD02" that refers to "Business").ANValueFor the full list of allowed values see the appendix.
remitter_address_streetStreet address of the remitter.String1-35Special characters are allowed.
remitter_address_additionalAddressLineAdditional address line of the remitter.String1-35Special characters are allowed.
remitter_address_cityCity of the remitter's address.String1-35Special characters are allowed.
remitter_address_stateState or province of the remitter's address.String2-35Special characters are allowed.
remitter_address_postCodeOrZipCodePostcode/ZipCode of the remitter's address.String1-35Special characters are allowed.
remitter_address_countryCodeCountry code (for example "GB") of the remitter address.A2ISO 3166-1 Alpha-2 code
remitter_address_residentialStatusCodeType of residency code (for example "RS01" that refers to "Resident").ANValueFor the full list of allowed values see the appendix.
expandableKeyValuePairsJSON object of key-value pairs used to supply additional data. The keys and values that you might need to process an account payout to a specific destination, are communicated during the onboarding process.ANDuplicate key names are not allowed