Please wait ...

The link leads directly to this section.

Copy the link with Ctrl + C, or right-click with the mouse and choose 'Copy'.

Batch processing

Batch processing simply means that once a day you send Bambora a file containing all your transactions for the past day, instead of sending the transactions one at a time. When your system is not communicating with Bambora all the time, you reduce the pressure on both your own and Bambora's systems.

We recommend batch processing if your company completes more than 100 transactions a day.

Please note that batch files concern the processing of transactions. Use the payment window for authorising payments.

Get started

You transmit batch files to Bambora through an SFTP connection (SSH File Transfer Protocol). Bambora's batch server will process the files. When transmitting files to Bambora, connect to the SFTP server using the login information Bambora provides.

If you want to use batch processing, please contact Bambora as we need to configure your connection manually.

Files and folders

When you connect to the SFTP server, you’ll see four folders, which contain all files:

Files from the company to Bambora are stored in the folder “IN”
Files from Bambora to the company are stored in the folder “OUT”
Files containing syntax error are stored in the folder “ERROR”
Files from the “IN” folder that have been processed are stored in the folder “ARCHIVE”

Expand / Collapse

File naming

We recommend that files for Bambora are named in the following format: YYYYMMDDHH (year, month, date, hour)

Files from Bambora to the company are stored in the OUT folder in the following format: YYYYMMDDHH

Pending files

Transactions that for some reason were not processed are stored in the following format when Bambora generates the output file: YYYYMMDDHH_pending

Files are stored as pending if:

A transaction is set for capture in the future (the company governs this)
The authorisation of an instant capture is set in the future
Bambora could not process the transaction

A row in this file contains the following information:

Input	Type	Values	Description
Operation	Integer		The operation to be performed on the transaction: 1. Capture (capture amount) 2. Credit (credit amount) 3. Delete (delete transaction) 4. Authorise subscription (authorise payment on a subscription) 5. Delete subscription
Merchantnumber	Integer	7-10 digits	Your unique merchant number. Find the number on your agreement with the acquirer.
Transactionid	Long		The unique number to identify the payment. It is returned at authorisation. If operation = 4 or 5, this field is blank.
Subscriptionid	Long		The number identifying the subscription. If operation = 1, 2, or 3, this field is blank.
Amount	Long	Minor units	The amount in minor units. DKK 149.99 must be specified as 14999 in the amount field.
Date	Date	20130115 YYYYMMDD	The date when the operation is to be performed. If, for instance, you want to capture the payment on June 21st, 2013, the date is defined 20130621.

Please note that you don’t need to take action on the pending file. This is simply information from Bambora to the company about transactions to be processed in the future.

Failed transactions

Transactions that couldn’t be processed due to errors in Bambora or the acquirer’s system are stored in the following format in the OUT folder: YYYYMMDDHH_error

Please note that an email is sent to the company and Bambora's support team when such a file is generated.

A row in this file contains the following information:

Input	Type	Values	Description
Operation	Integer		The operation to be performed on the transaction: 1. Capture (capture amount) 2. Credit (credit amount) 3. Delete (delete transaction) 4. Authorise subscription (authorise payment on a subscription) 5. Delete subscription
Merchantnumber	Integer	7-10 cifre	Your unique merchant number. Find the number on your agreement with the acquirer.
Transactionid	Long		The unique number identifying the payment. It is returned at authorisation. If operation = 4 or 5, this field is blank.
Subscriptionid	Long		The number identifying the subscription. If operation = 1, 2, or 3, this field is blank.
Amount	Long	Mindste enheder	The amount in minor units. DKK 149.99 must be specified as 14999 in the amount field.
ActionCode	String	0-9 a-Z	The error code explaining why the transaction was declined.

Please note that you have to take manual action on the transactions in this file. The transactions are not processed again. Normal procedure would be to resend the transactions in a new file for Bambora.

File content

The files must be defined as CSV (comma separated values) in the format RFC 4180. Find a specification of the format here: http://tools.ietf.org/html/rfc4180

One operation is performed for each row.

Please notice:

A file can contain several different operations
The separator between each operation (row) is \r\n (0x0a 0x0d)
The separator between each field in the row is a semicolon (;)
Mandatory fields must be defined
Fields that are not mandatory must be left blank if they’re not defined

Also note that rows must be dynamic. Since Bambora might need to add more fields to each row, you cannot expect a fixed number of columns for each row. This must be dynamic.

The processing of files

Bambora processes transactions as they are received. You choose whether you want to receive one daily output file or an output file per input file.

If you receive one output file, you can schedule the generation with us. If you receive an output file per input file, we sent each output file when all rows in the input file are processed.

Files older than 30 days are deleted from the OUT folder

Files in the IN folder are deleted when they’re processed and moved to the ARCHIVE folder. Files in the ARCHIVE folder are deleted after 30 days.

Data types

The following section describes the data that are sent between your system and Bambora. For each function/service/operation you can see the input fields, which are the fields you transmit to Bambora, and the output fields, which are the fields Bambora returns.

You can make five operations on a file:

1. Capture (capture amount)
2. Credit (credit amount)
3. Delete (delete transaction and release amount)
4. Authorise subscription (authorise a capture on a subscription)
5. Delete subscription (delete subscription)