Merchants submitting United States (U.S.) transactions must enter eight different pieces of information for each line in the file. Do not include the customer code. If you are using a text based program like Notepad, follow each piece of transaction data with a comma.
Merchants submitting U.S. transactions using customer codes or secure payment profiles, must enter six pieces of information in each line of the file. Leave the commas in lieu of transit number, account number, and account code. For spreadsheet files include blank spaces. For text based programs like Notepad, follow each piece of transaction data with a comma.
- All banking information and customer codes are mandatory.
- Do not mix customer codes and banking information, otherwise transactions with banking information will not be processed.
- The Customer profile must have an active status.
- When you are finished, save your file again in .csv format.
|A||Designates the type of transaction record. Enter A for ACH.|
|C or D||Indicates the type of bank payment being processed.
C – Credit recipient bank accounts.
D – Debit an outside bank account and depositing funds into your own account.
|9-digit transit number||Enter the Transit Routing Number from the customer’s check. See image below for details.|
|5-15 digit account number||Enter the number of the customer’s bank Account Numberas it appears on their void check.|
|2-letter Account Code||Enter an Account Code to designate the type of bank account to be credited.
PC – Personal Checking
PS – Personal Savings
CC – Corporate Checking
CS – Corporate Savings
|Transaction amount in pennies||Enter the total transaction amount in pennies. Do not include a decimal point. e.g. for $45.99 enter 4599|
|Optional reference number||You can create an internal reference number of up to 19 digits. If you don't want a reference number, enter 0 (zero).|
|Recipient Name||Full name of the person you are paying.|
|Customer Code||Enter the 32-character customer code located in the payment profile. Do not populate bank account fields in the file when processing against a customer code.|
|Dynamic Descriptor||By default the Bambora merchant company name will show on your customer's bank statement. You can override this default by populating the Dynamic Descriptor field.|
|SEC Code||Standard Entry Code. Tells the network the type of bank transaction being performed. By default this field must be blank or not provided, and Bamborawill automatically insert a value. This will be based on the Account Code of the transaction where a PPD will be assigned for personal account and CCD for corporate.
PPD – US Personal Checking and Personal Savings
CCD – US Corporate Checking and Corporate Savings
CTX – Corporate trade exchange
WEBS – Non-recurring web transaction
WEBR – Recurring web transaction
Important: The merchant must have SEC code permission to populate this field. If the field is populated without permission, the transaction will be rejected.
|Addendum Data||Entry Detail Addenda Record (Optional). Used for CCD, CTX, and PPD Standard Entry Code (SEC) classes. The Addenda information contains additional payment related information. This field accepts a maximum of 80 characters for CCD and PPD transactions, and up to 799920 characters for CTX transactions. Important: The merchant must have SEC code permission and must pass an SEC Code in their transaction to use this field.|
Typical United States Check Format
Carefully review all bank account information. Files with incorrect transit or account numbers are rejected. Do not enter the check number anywhere in the form, or the transaction will be rejected.