Standard PagoPA file - Transactions
This chapter describes the structure of the Standard PagoPA file, i.e. the transaction file to be used as an input for the batch service elaboration, the output file produced by the batch service will have the same format.
The naming convention of the file is as follows:
[service].[ABI].[filetype].[date].[time].[nnn].csv
in particular:
field
format
notes
service
Alphanumeric - 5 char
fixed value "CSTAR"
ABI
Alphanumeric - 5 char
sender ABI code or PagoPA 5 char assigned code (if ABI not available)
filetype
Alphanumeric - 6 char
Fixed value "TRNLOG"
[date].[time]
YYYYMMDD.HHMISS
file creation timestamp
nnn
Alphanumeric - 3 char
Progressive value of the file (e.g. 001)
Fields in the Standard PagoPA file
field
Type
Mandatory
Notes
sender_code
Alphanumeric - max 5 char
YES
ABI code of the sender. If not available, a 5 char code assigned by PagoPA
operation_type
Alphanumeric - regexp [0-9]{2}
YES
Operation type:
00 - payment
01 - reversal of payment
xx - future uses
circuit_type
Alphanumeric - regexp [0-9]{2}
YES
Payment circuit:
00 – Pagobancomat
- Transactions on this circuit will be sent exclusively by Bancomat.
01- Visa
02- Mastercard
03- Amex
- Transactions on this circuit will be sent exclusively by AMEX.
04- JCB
05- UnionPay
06- Diners
- Transactions on this circuit will be sent exclusively by Diners.
07- PostePay Code
08- BancomatPay
09- SatisPay
10- private circuit (onus, onwe)
xx - future uses
pan/hpan
Alphanumeric max 64 char
YES
PAN of the payment instrument used. In the case of a non-card based circuit, will be the unique identifier of the payment instrument, the same the user can register using the IO App or a touch point from the Issuer bank. In the input file the information must be provided unencrypted, in the output file the information will be hashed
date_time
ISO8601 date.
It must be compliant with the following DateTimeFormatter pattern:
yyyy-MM-dd'T'HH:mm:ss.SSS[XX][XXX]
YES
Timestamp of the payment transaction carried out with the Merchant.
Please note that the second details are not always available for all transactions. In this case, the field will be padded with all '0's
id_trx_acquirer
Alphanumeric -max 255 char
YES
Unique identifier of the transaction at the Acquirer level.
- can be populated with the ARN, or if this data is not present, with a unique id that allows to uniquely identify the transaction on the Acquirer side.
id_trx_issuer
Alphanumeric -max 255 char
YES
Authorisation code issued by the Issuer (ex: AuthCode)
correlation_id
Alphanumeric -max 255 char
NO
Correlation identifier between payment transaction and possible reversal.
The fied is mandatory if the record refers to a reversal operation (operation_type = 01)
total_amount
Numeric
YES
Valued in euro cents (ex: 10€ = 1000) and expressed in absolute value: the sign is assumed from the type of operation “00-payment, 01-reversal"
currency
Alphanumeric - max 3 char
YES
Fixed value 978 = EUR. International ISO coding is used.
acquirer_id
Alphanumeric -max 255 char
YES
Unique Acquirer ID. In the case of card transactions, it represents the homonymous value conveyed on the international circuits.
- In the Pagobancomat circuit it corresponds to the field codice_sia_abi
- Visa/Mastercard Circuit: acquirer_id
In other cases the field will be valued with fixed data depending on the reference Acquirer
merchant_id
Alphanumeric -max 255 char
YES
Unique identifier of the physical store of the Acquirer (also known to the Merchant and used by the same to register on the Automatic Billing platform).
- In the Pagobancomat circuit it can correspond to the field: merchant
terminal_id
Alphanumeric -max 255 char
YES
Identification of the Merchant's terminal/POS (Point of Sale).
- In the Pagobancomat circuit it corresponds to the field: cashier premises
- Visa/Mastercard circuit: terminal_id
bank_identificatio n_number (BIN)
Alphanumeric or - regexp [0- 9]{6}|[0-9]{8}
YES
Code containing the first 8 digits of the payment instrument.
- In the Pagobancomat circuit it corresponds to the field: codice_abi
MCC
Alphanumeric -max 5 char
YES
Merchant Category Code.
fiscal_code
Alphanumeric - max 50 char
YES
Fiscal code for legal person and for natural person (self-employed workers).
VAT
Alphanumeric - max 50 chars
NO
VAT Code, Tax Code legal person. The fied is mandatory if fiscal_code record refers to a legal person
pos_type
Alphanumeric regexp [0-9]{2}
YES
POS Type:
00 - physical POS
01 - e-commerce
PAR
Alphanumeric
NO
Payment Account reference
The field must contain the information of the PAR, which can be defined as a collector capable to associate each TokenPAN with the PAN of the physical card, thanks to the unique and immutable association between PAN and PAR and Token and PAR
Last updated