What are the requirements for a credit card batch file?

Credit card batch files require specific fields and information in order to process successfully. Understanding what the required information is, and knowing how to format the file is essential when using Batch Processing.  

Must know:

  • A Credit Card batch file will process under the currency of your Bambora account. You can not mix multiple currencies in one batch file. 
  • All banking information and customer codes are mandatory.
  • Do not mix customer codes from a Payment Profile and banking information, otherwise, transactions with banking information will not be processed.
  • A customer’s payment profile must be in active status.
  • For text files, use a comma to separate the data for each field. If there is no data for a field, make sure you still enter a comma. 
How to use the credit card batch file template?
  1. Download our template spreadsheet for a credit card batch file. 
  2. Enter your payment information in row 3 and below. 
  3. Once complete delete row 1-2 (the title and example data). 
  4. Save the spreadsheet as a CSV.
How to create your own file?
  1. Do not skip, reformat, or change the order of the fields below.. 
  2. The Column letters correspond to the columns in your spreadsheet file. 
  3. If you are using a text-file format (ex. Notepad), please use commas to separate the data.

Credit card batch field requirements:

Column Field Name Description

A

Record Type

Designates the type of transaction record. Enter C for Credit Card.

B

Transaction Type

Bambora’s Credit Card Batch service works with all six transaction types:

P – Purchase

R – Return

PA – Pre-authorization

PAC – Pre auth completion

VP – Void Purchase 

VR – Void Return


*Voids will only work if your Processor allows void transactions. Please contact Customer Care to know if your account supports Voids.

C

Adjustment Id

Reference the 8-digit Bambora transaction ID number from the original purchase or pre-authorization transaction. Adjustment ID is used only for R, PAC, VP, and VR type transactions. For P or PA transactions, leave this field blank. If an Adjustment ID is included, the card number and card expiry are optional. 


If you want to process the return using a different card, enter the new card number and expiry. This will only be successful if you have RWAP (Returns Without Associated Purchase) enabled.

D

Card Number

Enter the consumer’s credit card number. Max. 20 digits. If an Adjustment ID is included, this field is optional.

E

Card Expiry

Credit Card expiry date. 4-digits MMYY format. e.g. April 2021 = 0421. If an Adjustment ID is included, this field is optional.

F

Amount

Transaction amount. The format is in pennies, max. 9-digits. Do NOT use the decimal; e.g. $1345.62 is 134562.

G

Reference

Optional but recommended. Include an internal reference number of up to 32 alphanumeric characters. If a reference number is submitted, a duplicate transaction check is performed. If more than one transaction is attempted with the same reference number, credit card number, and amount within a one-hour period, the transaction is declined as a duplicate. If you choose not to include this information, do not skip this field, leave this entry blank.

H

Card Owner

Max. 32 characters. This can be alphanumeric.

I

Email Address

Optional. Max. 64 characters. If you want an email receipt sent to your customer, enter the card owner's email address in the batch file. Make sure you also configure the Batch Processing Receipt in your account. If you don't include this information, do not skip the field, leave it blank.

J

Recurring

Flag for the bank to indicate you do regular business with the customer—it will not create a Bambora recurring billing account.

1 – Indicates to your financial institution it is a recurring transaction.

0 – Indicates the transaction is not a recurring transaction.

K

DBA 

(Value added credit card service)

If you’re using the Dynamic Descriptor (DBA) Service for credit card processing, you can pass additional information to include on the customer credit card statement. The Dynamic DBA (Doing Business As) is a service that allows a merchant to customize the billing description that the customer sees on their credit card statement. 


Create each batch line item using the standard format. After the last field, enter a comma followed by alphanumeric data up to 25 characters. Do not use special characters, as only standard letters and numbers are used on the customer’s statement.

L

Profile Code (customer code)

If you use Bambora’s Secure Payment Profile service, merchants can replace confidential credit card billing information with the secure customer code that is stored in the payment profile. Include the customer code or token, in the last column of your file. 

Leave the card number, expiry date, card owner, and email address blank. Sample line item using the customer code value: C,P,,,,1000,,,,,,02nMl0tU3td09GMw9h1rP2

Good to know:

  • If you are using the API to process batches, please visit our Developer Docs.
Was this article helpful?
0 out of 0 found this helpful