Get Started

Input File Format 

Table 3 Fields - Input File Format


Field Name Description M/C/O Data Type / Length
BeneName Beneficiary Legal Name O* Char(35)
BeneficiaryID Client-assigned, unique ID for a payee C1 Char(35)
BeneficiaryStreetAddress Beneficiary street address O Char(35)
BeneficiaryCity Beneficiary city O Char(35)
BeneficiaryStateProvince Beneficiary state or province O Char(35)
BeneficiaryPostalCode Beneficiary postal code O Char(20)
BeneficiaryCountry Beneficiary ISO country code O* Char(2)
BeneficiaryEmailAddress Beneficiary e-mail address O Char(255)
BankName Beneficiary bank name O * Char(35)
BankCountry Beneficiary bank country ISO code O * Char(2)
BankAccount Beneficiary bank account numbers O * Char(34)
BankSwiftAddress Beneficiary Bank Swift Address O * Char(11)
BankRoutingCode Beneficiary bank local routing code O * Char(29)
BankStreetAddress Beneficiary bank street address O * Char(35)
BankCity Beneficiary city O * Char(35)
BankStateProvince Beneficiary bank state or province O * Char(35)
BankPostalCode Beneficiary bank postal code O Char(20)
Swiftbranchdetails Beneficiary bank Swift details O Char(45)
IBankName Intermediary bank name O Char(35)
IBankCountry Intermediary bank ISO country code O Char(2)
IBankAccount Intermediary bank account number O Char(34)
IBankSwiftAddr Intermediary bank Swift address O Char(11)
IBankRoutingCode Intermediary bank local routing code O Char(35)
IBankStreetAddress Intermediary bank street address O Char(35)
IBankCity Intermediary bank city O Char(35)
IBankStateProvince Intermediary bank address state or province O Char(35)
IBankPostalCode Intermediary bank postal code O Char(20)
PaymentID Client-assigned, unique payment ID O1 Char(35)
Currency Payment ISO currency code C Char(3)
Amount Payment amount M Float
PayBy “ach”, “draft” "Draft2Bene" or “eft” C2 Char(8)
ReleaseDate Payment release date O Date(mm/dd/yyyy)
Ref1 Client reference sent with payment O Char(34)
Ref2 Client reference sent with payment O Char(34)
AmountExpression “target” or “settlement” M1 Char(10)
FundedBy “holding” or “fxtrade” M1 Char(7)
DeductFeesFromFa   O  
ClientRate  Reference rate O  
SettlementMethod  Code for the method by which the client intends to settle with WESTERN UNION BUSINESS SOLUTIONS.Value may be “BACS”, “CertChk”, “CHAPS”, “Check”, “Cheque”, “DirCred”, “DrawDown”, “Edebit”, “Holding”, “QuickCHK” or “Wire” O  
SettlementAccount*  Account number of the account from which WESTERN UNION BUSINESS SOLUTIONS will initiate settlement from the client O  
ClientFileID  Client generated file ID O Char(35)
BankAccountType  Account type used in the settlement. Valid values are: “Checking”, “Saving”, and “G/L”    
TaxID      
BeneficiaryPhoneNumber Beneficiary's Phone Number    
BeneficiaryContactName Full Name of a contact at the beneficiary. O  
AlternateShipToName   O  
PaymentPurpose Purpose of Payment options: Advertising Fees, Expense Reimbursement, Financial, Legal, Medical Reimbursement, Other, Payroll, Processing, Trade Related, Transaction between Banks, Transportation Costs, Travel Related. M3 Char (100)
WUMobilePhoneNumber Mobile Phone Number for Beneficiary C3 Char (20)
WUReceiverFirstName Beneficiary First Name M3 Char (35)
WUReceiverLastName Beneficiary Last Name M3 Char (35)
WUReceiverCity City of Payment Receipt C4 Char(40)
WUReceiverState State of Payment Receipt C5 Char (5)
WUReceiverCountry Country of Payment Receipt M3 Char (2)
WUSecretAnswer Test Answer C6 Char (20)
RemitterAccountNumber*  Remitter’s account number or unique identifier  M if client is a Broker  
RemitterName*  Remitter’s full name (business or first and last of person) O  
RemitterFirstName Remitter's First Name, if individual O Char(35)
RemitterLastName Remitter's Last Name, if individual O  
RemitterAddressLine1*  Remitter’s street address line 1 M if client is a Broker Char(50)
RemitterAddressLine2*  Remitter’s street address line 1  O Char(50)
RemitterCity*  Remitter’s city M if client is a Broker  
RemitterState*  Remitter’s State M if client is a Broker  
RemitterProvince* Remitter’s Province  O Char(52)
RemitterPostalCode*  Remitter’s Postal Code  M if client is a Broker Char(52)
RemitterCountry*  Remitter’s ISO country code M if client is a Broker Char(36)
RemitterFIAccountNumber*  Remitter’s financial institution’s account number or unique identifier  “M” if Remitter’s FI info is required Char(30)
RemitterFISwift  Remitter’s financial institution’s SWIFT number  “M” if Remitter’s FI info is required Char(30)
RemitterFIFullName*  Remitter’s financial institution’s full name (business or first and last of person)  “M” if Remitter’s FI info is required Char(20)
RemitterFIAddressLine1*  Remitter’s financial institution’s street address line 1  “M” if Remitter’s FI info is required Char(2)
RemitterFIAddressLine2*  Remitter’s financial institution’s street address line 2  O Char(50)
RemitterFICity*  Remitter’s financial institution’s city  “M” if Remitter’s FI info is required  
RemitterFIStateProvince*  Remitter’s financial institution’s state or province  O Char(50)
RemitterFIPostalCode* Remitter’s financial institution’s postal code  M” if Remitter’s FI info is required Char(52)
RemitterFICountry*  Remitter’s financial institution’s country  M” if Remitter’s FI info is required Char(52)
Reference1*  Internal reference for the client; not sent with the payment  O Char(255)
Reference2* Internal reference for the client; not sent with the payment  O Char(255)
Reference3* Internal reference for the client; not sent with the payment  O Char(255)
Reference4*  Internal reference for the client; not sent with the payment  O Char(255)
Reference5* Internal reference for the client; not sent with the payment  O Char(255)
Reference6* Internal reference for the client; not sent with the payment  O Char(255)
Reference7* Internal reference for the client; not sent with the payment  O Char(255)
Reference8* Internal reference for the client; not sent with the payment  O Char(255)
Reference9* Internal reference for the client; not sent with the payment  O Char(255)
Reference10* Internal reference for the client; not sent with the payment   O Char(255)
SwiftUETR Unique SWIFT payment reference. Only use if passing a file generated from SWIFT, any other values will be removed.  O Char(255)
BeneficiaryRegistrationNumber    O Char(255)
FamiliarName Unique name amount your beneficiaires. Will store in the Familiar Name field in WUBS.  O Char(255)
YourID Can be used as an internal reference number for the user booking payments. Will travel with the payment.  O Char(255)
NotesToVerifier Can be used to pass instructions to a payment approval. Will travel with the payment and be visible to approvers and Western Union.  O Char()

Notes on Table 3

  • O - Optional field.
  • O* - If BeneficiaryID is not provided in the file, then these fields have to be populated.
  • M- Mandatory field.
  • M1 – The values can be stored for the client and need not be transmitted with the payment file.
  • M3 – Required for Retail Payment Transactions.
  • C1—If VendorID is provided, the legal name, address, and banking information are disregarded. Note that the fx360 template for the upload file currently refers to “BeneficiaryID.” This is the client-assigned “Client Vendor ID” that you provided when entering a beneficiary in GlobalPay.
  • C2—If VendorID is provided, PayBy defaults to the beneficiary’s stored method of payment; unless a PayBy method is entered in the PayBy field. If VendorID is not provided, PayBy entry is mandatory.
  • C3 – If the transaction is a Retail Payment Mobile payment this field is required. Retail Payment Agent payments do not require this field.
  • C4 - City is required for Retail Payment Transactions that are destined for US or Mexico.
  • C5 - State is required for Retail Payment Transactions that are destined for US or Mexico.
  • C6 - Test answer is required for certain Retail Payment destination countries.
  • Do not exceed the width of any character field or your input will be truncated.
  • Regardless of the date entered, release date is the current date, as fx360 currently is for spot payments only.
  • If USD payment is made from a non US bank to US based beneficiary with a US based account through NACHA network, then as per IAT regulations, the beneficiary details are mandatory, fields 3 to 7.
  • PaymentID is an optional, preferably unique code you use in your accounting or ERP system to identify the payment item. Your code is returned in the fx360 Completed Payment File (CPF).
  • In comma separated values (CSV) files, enter characters without quote strings.
  • XML documents must be well-formed. XML requires that “entity references” be used instead of certain symbols in character fields. For example, use “&” instead of an ampersand (“&”). “Smith & Company” would be “Smith& Company” in an XML payment upload file.
  • The target currency is that in which payment to the beneficiary/payee is denominated.
  • The settlement currency is that in which you, the client, settle/pay Western Union Business Solutions.
  • Do not specify “holding” for FundedBywhen AmountExpression is “settlement.”
  • The two FundedBy options are:
  • funding from your account’s Holding Balance in the target currency, or
  • funding by purchasing the currency from Wester Union Business Solutions.
  • If the File does not contain values for FundedBy and AmountExpression fields, the default values stored in GlobalPayfor the client will be used.
  • NA – Data can be received but not processed till further notice.