Principles of Batch manager

This Manual describes 

The following section Introduction offers a short introduction on how Batch Manager can be used. It the section Name of the batch files it describes how batch files must be named. The exchange of batch files with 

Batch files must be correctly structured to enable 

Introduction

Batch Manager lets you transmit payment transactions in the form of files. In this process you assemble transaction data such as the credit card number, amount and currency in a batch file which is transmitted to

Anchor
Name Name

Name of the batch files

The name of a new batch file begins with the letter T to indicate the file was originally transmitted by you. This is followed by the Date of the submission in reverse order: e.g. 20160112. This is followed by a three-figure Counter, which starts at 001 and the MerchantID issued by

The name of a batch file comprises four components.

File name for manual transmission via

Multiexcerpt include
SpaceWithExcerpt EN MultiExcerptName Backoffice-Name PageWithExcerpt Wording

File name for automated FTP transmission

Please pay attention that file name is different for 

Components of batch file names

The processing of the batch file goes through several phases which are indicated within the file name: The original file form the merchant starts with the character T. After processing, the batch file is suffixed with the letter P for Processed.

If a merchant with the MerchantID MerchantID submits two batch files on 12/01/2016 via

Notice: After you have transmitted the batch file the processing of the transactions begins. After the transmission and during the processing the file is prefixed W for Waiting. If the T batch file is submitted via FTP/sFTP for processing, the phase must be renamed W after the upload by the merchant system. The processing only starts after this step.

Once all payment transactions have been carried out, 

Anchor
Encoding Encoding

Encoding for batch files

The encoding is relevant if special characters are to be used, e.g. é or similar. In batch files such special characters can be present in the parameter OrderDesc or text fields.

In general, UTF-8 as encoding is a good choice for the delivery of batch files. UTF-8 BOM (with ByteOrderMark) is also supported.

Anchor
Manual Manual

Manual transfer of batch files

The batch interface is integrated into

To transmit a new batch file to the

Image RemovedImage Added

The batch view of

Notice: The processing of the transmitted batch file starts shortly after the transmission. Since all batch files are processed in turn, the processing of your transmitted batch file does not begin until previously transmitted batch files have been processed.

After the transmission and during the processing the file is prefixed W for Waiting. When all payments in the batch file all have been processed, the batch file is allocated the new initial P. You can click on these processed files in the 

Anchor
FTP FTP

FTP-transfer of batch files

In addition to manual batch transfer (see also Manual transfer of batch files) 

1. Save the transaction data in a formatted batch file
2. Encryption of the batch file
3. Transfer the batch file
4. Change of the phase after the upload (T -> W)
5. Retrieve the batch file after processing
6. Check status of transactions

Save transactions in the batch file

The transaction data in the batch files must correspond to the structure described in the following section Format of batch files.

Encryption of the batch file

For reasons of security, batch files must be encrypted before the FTP/sFTP transmission. To guarantee maximum security the

If several batch files are to be submitted, for example for a Merchant with the MerchantID MerchantID on the 12/01/2016, then these two files are named as follows (see also Name of the batch files):

The recognised high security of PGP-encryption is based on a process with two keys, a private key and a public key.

You can also generate public and a private key for your company.

Anchor
Format Format

Format of batch files

The content of a batch file consists of a header, several records and a footer. Each entry in the file is one row which is completed with CRLF (Enter key). The values within a line are comma-separated. The format is thus also described as the CSV format (Comma Separated Values).

The following sections describe the format of the batch file which you transmit to

Format of batch files submitted

The listing below shows the components which make up the content of a batch file.

Notice: Please note that the batch file may not include any empty rows either at the start or the end of the file. The empty rows in the listings are for ease of reading only.

Notice: It is allowed to send various payment methods within one file. 

Notice: Please note that text parameters like "Reason" or "OrderDesc" may not contain commas.

Notice: In Batch versions 2.x there is another field for <MID>. Thereby it is possible for a MasterMID to submit transactions for SubMID.

Header

Type,MerchantID,Date,Version

Record

Type,Action,<Amount>,<Currency>,<TransID>,<Data depends on Action>

Footer

Type,CountRecords,SumAmount

The following listing is an example of a batch file for the capture of three credit card transactions to the value of 1.00 and 2.00 euro’s. For the first payment the merchant system supplies the reference number 123456 but no reference numbers are supplied for the second and third:

HEAD,MerchantID,20160112,1.2
CC,Sale,100,EUR,1567890,123456,MasterCard,5490011234567890,200506,Your order from Jan. 4.
CC,Sale,100,EUR,1567891,,MasterCard,5490011234567890,200506,Your order from Jan. 4.
CC,Sale,200,EUR,10202280,,VISA,4907621234567890,200504,Your order from Jan. 4.
FOOT,3,400

The description of the individual fields and values used within the data set (Record) within the batch file you will find in the respective chapter within the manual of the individual payment method.

The general parameters for transfer within Header and Footer explains the following table:

Description of general parameters for Header and Footer of batch files

Anchor
Format2 Format2

Format of batch response files

During the processing of the transactions the Batch Manager saves the transaction status to the batch file. To this end two fields, Status and Code, are added to the transaction entries in the Record area:

Record

CC,Capture,<Amount>,<Currency>,<TransID>,<RefNr>,<PayID>,<Status>,<Code>

Notice: If using the authorisation renewal the Batch-response file can include more rows than you have submitted because the

Notice: The return of optional parameters in the response file generally occurs only if these were included in the submitted file. Generally no shipment information are given in the response file. If you need this data again, please read this data from the corresponding Notify.

The particular response parameters which Batch manager stores in the record section for each transaction you will find in the batch chapter for the respective payment method.

Anchor
Error Error

Batch error codes

From Version 3.0

The first digit describes the degree of severity of the error. All values greater than 0 indicate warnings or errors.

Notice: An error code doesn’t necessary mean that the

The 2nd to 4th digits of the error code describe the error category. The error categories relate to encryption (001) and format errors (010) and the details of payment methods, initiated in the case of credit cards (100) through direct debits (110) to Cash&Go (140).

The 5th to 8th digits of the error code give an indication of the error details. Details include instructions on configuration problems such as missing TerminalIDs (0047) and failures at the card holder's bank computing centre (121) but also standard refusals of credit card payments based on expired cards (110) or declined messages (0100).

Notice: Error-free transactions, for reasons compatibility with Version 2.1, are not characterised by eight but by a zero 0.

You can find a full list of