Files

Specifications

Request and response files must meet the following criteria:

  • Encrypted with PGP (mandatory for files including Credit Card transactions)

  • Formatted as .csv

  • This means, only comma (,) is accepted as separator!

    A field value must not contain a comma!
  • Linefeed: LF (Unix format) must be used as separator for the different transactions

  • Include header columns for each field

  • Encoded in UTF-8

  • The different parameters must be defined in the order given in the table Batch Processing SEPA.

Please refer to the Sample for Batch Processing.

Request

Batch processing has been designed to accept transactions for several payment methods. Field requirements vary by different payment methods.

Credit Card

The Credit Card Fields table describes the fields that must be provided for Credit Card transaction requests.

  • The fields must be defined in the .csv file in the order given in the following table to allow correct processing.

  • CSV format requires that each field must be specified. Empty fields (optional fields or fields not used by Credit Card) have to be defined as empty values separated by commas: ,,.

Example
…3.33,EUR,4012000300001003,…
Batch processing for Credit Card does not support submitting the CVV/CVC.

+ To process Credit Card transactions via batch, it is recommended to first submit an online authorization transaction via API and follow-up with a capture transaction via batch. A capture must be submitted with a parent-Transaction ID referring to a successful authorization transaction. 

+ Please refer to Credit Card for more information. The names used in the batch service may differ from the field names given in the API documentation. For details see the Batch API Field Name Mapping table.

SEPA

Batch processing has been designed to accept transactions for several payment methods. Field requirements vary by different payment methods.

The Batch API SEPA Fields Table describes the fields that must be provided for SEPA transaction requests.

  • The fields must be defined in the .csv file in the order given in the following table to allow correct processing.

  • CSV format requires that each field must be specified. Empty fields (optional fields or fields not used by SEPA) have to be defined as empty values separated by commas: ,,.

Example
 …121.22,EUR,,DE42512308000000060004,…

Please refer to SEPA DD and SEPA CT for more information. The names used in the batch service may differ from the field names given in the API documentation. For details see the Batch API Field Name Mapping table.

Request File Naming 

Request files must be given a unique batch ID using the following format:

requestbatchid.timestamp.request.csv.pgp

Example
batchsample001.201201011801.*request*.csv.pgp
  • Where timestamp is in the format of YYYYMMDDhhmm and in UTC timezone.

  • The request batch ID will be included in the response filename and within the response file content.

  • PGP encryption is optional.

If the file is encrypted, the extension .pgp must be added to the file name!
Response
Response File Naming

Response files will be named after the request file including the request batch ID, timestamp and customer number:

requestbatchid.timestamp.<foldername>.response.csv.pgp

Meaning
  • Extension .pgp will only be added if PGP encryption was requested.

  • <foldername> is the merchants’ number (SFTP User), eg: C0001

Example
  • Request file: batchsample001.201201011801.request.csv.pgp

  • Corresponding response file: batchsample001.201201011801.C0001.response.csv.pgp

Custom URL: