About this Guide
This guide serves as a reference to the format and contents of the reports generated and delivered via the Smart Data product.
This document is intended for technical personnel who will be retrieving and parsing reports generated by the Smart Data system.
Alphabetic with special characters
Alphanumeric with special characters
Numeric with special characters
Boolean Expression (true or false)
Fixed length with 3 digits/characters
Variable length with maximum 3 digits/characters
Enumeration of allowed values
Please note that the terms payment and transaction are used interchangeably throughout this document. A payment respectively a transaction may encompass a number of operational activities.
During a transaction lifecycle, the state of a transaction will change, depending on the performed action. These actions may include authorization, capture, sale, cancel and refund. A transaction is thereby defined as a sequence of actions.
An action is an operation that changes the status of a payment when performed successfully.
In the context of Smart Data a job contains a set of general information about the report layout, filter options and data fields.
A task is the actual representation of a job with an assigned execution time.
Smart Data is an automated service designed to create one or more predefined reports that are made available in a merchant’s FTP account for retrieval. The service enables merchants to schedule periodic reports according to their individual needs.
Smart Data reports are delivered as delimited text files (CSV) with a standard set of data fields by default. Merchants however may customize their reports by choosing the fields from the standard set they would like have included. Data records may encompass transactions between one day and maximum one year prior to the report date. Please note that real-time data are not supported through this product.
For individual setup and configuration please contact .
The following filter options are available:
- Payment Method
- Payment Status
- Card Brand
- Successful transactions only
- Unsuccessfull transactions only
- Only transactions with specific Code/s,
- Only transactions without specific Code/s
Please note that all filter options may contain multiple values.
Smart Data reports can be setup according to the following options:
- Given time period between two dates
- Weekly (weekday of delivery at merchant’s discretion)
- Monthly (on 1st, 2nd, 3rd, ... each month)
Smart Data reports are created as plain text files in CSV format. Currently comma, tab and colon are supported delimiters to separate values (please contact for individual setup). The default delimiter is colon unless specified otherwise.
Each file will contain an initial header row and zero or more data rows. A header row will consist of a separated list of the individual field names, as defined in this document, in the specified order. The field names of the header row are currently available in English and German. The data rows will consist of a separated list of the data field values that contain characters encoded in UTF-8.
For security reasons all files are PGP encrypted and transferred via SFTP.
The file names are assigned according to the following convention: SmartData_[JobID]_[TaskID]_[YYYYMMDD_hhmmss].CSV.pgp
The individual name elements are described in the table below.
Internal job identifier
Internal task identifier
A valid file name example is: SmartData_12_789_20160320_023609.CSV.pgp
Data Records and Field Description
Each record represents an operation/action that has been performed on a payment. Regularly a payment will consist of multiple operation records. Available data fields are listed in the table below. Individual data fields can be omitted on request.
Payment identifier generated by
Merchant identifier assigned by
Timestamp of payment creation time: DD.MM.YYYY hh:mm:ss
Transaction identifier assigned by the merchant on payment level
Supplementary transaction identifier assigned by merchant on payment level
Authorized amount in its smallest unit of transaction currency
Captured amount in its smallest unit of transaction currency
Refunded amount in its smallest unit of transaction currency
ISO 4217 three-letter currency code
Transaction status with one of the following values:
Please note that the above listed status values are not exhaustive and may vary depending on the payment method.
Payment method (e.g. Barzahlen, Card, PayPal etc.)
Card scheme (e.g. Visa, MasterCard, Maestro etc.)
Country of Origin Card A2
Country of origin according to BIN/IIN (2 characters or n/a, e.g. DE)
Country of Origin Card A3
Country of origin according to BIN/IIN (3 characters or n/a, e.g. DEU)
Country of Origin Card N3
Country of origin according to BIN/IIN (3 digits or n/a, e.g. 276)
Masked card number
Card token generated by
|Expiry date||n6||Credit card's expiry date in the format yyyyMM, e.g. 202005|
|Approval code||an6||Authorisation code of the transaction|
|Cardholder Name||ans..60||Name of cardholder|
|CardType||ans..64||Card type, e.g. Credit, Debit, Prepaid,...|
|Category (Card)||ans..64||Credit card category, e.g. Standard, Business,...|
|SubBrand||a..22||CardBrand2 or Sub-Brand|
|BIN||n6..11||Bank Identification Number|
|TerminalID||an8||ID of the terminal|
|CardAcceptorID||n5..12||Contract partner number|
|Acquirer Name||an3||Acquirer shortcode|
International Bank Account Number
ISO 9362 Business Identifier Code
Custom merchant data that are included in the response and that might get conveyed to the subsequent processing host depending on the acquirer and custom arrangements
Unique action identifier assigned by
Specifies the action performed on the payment:
· AUTHENTICATE: authentication for a payment
· AUTHORIZE: authorize of a payment
· CAPTURE: capture of an authorized payment
· CREDIT: credit of a payment
· SALE: authorize and capture of a payment
· CHARGEBACK: chargeback of a previously made payment
For chargebacks it depends on acquirer whether they are notified in EPA and can be attributed to a payment process.
Timestamp of the action: DD.MM.YYYY hh:mm:ss
|Reference number (Transaction)||ans..30||Additional Transactions-ID from the merchant on action level|
|Card holder information 1 (Transaction)||ans..64||Text printed on the customer’s credit card bill alongside the payee|
|37||Card holder information 2 (Transaction)||ans..64||Text printed on the customer’s credit card bill alongside the payee|
Status received on the performed action
Operation amount in its smallest unit of transaction currency
Error code description