Centro stella dei pagamenti elettronici
  • Centro Stella
    • Instructions for Agenzia delle Entrate Mandate
      • How to join
        • 01. Sign the Agreement
        • 02. Integrate PagoPA Environments
          • Open routes
          • Request the mutual authentication certificates
          • Obtain an API key
          • Wait for activation email
          • Check if you are enabled for PagoPA UAT environment
        • 03. Configure the Batch Service
          • Prepare the Java KeyStore
          • Install the software
            • How to install JAR version
              • Download JAR file
              • Prepare the working directories
              • Define environment variables
            • How to install Docker version
              • Download Docker image
              • Define environment variables
              • Choose working directory to mount
          • Run the software
            • Run from JAR
            • Run with Docker
        • 04. Test and monitor integration
          • Test UAT
          • Test PROD
        • 05. Go live!
      • Releases / Changelog
        • Note regarding the modifications from 2.2.0 to 2.2.3
        • Note regarding the modifications from 2.1.2 to 2.2.0
        • Note regarding the modifications of the yaml file from 2.0.0 to 2.1.0
        • Note regarding the modifications of the yaml file from 1.5.1 to 2.0.0
        • Note regarding the modifications of the yaml file from 1.4.1 to 1.5.0
        • Note regarding the modifications of the yaml file from 1.3.2 to 1.4.1
        • Note regarding the modifications of the yaml file from 1.2.5 to 1.3.2
      • Appendixes
        • Appendix 1 - Environments
        • Appendix 2 - Input file specifications
        • Appendix 3 - AdE output file specifications
          • Appendix 3 - AdE output file specifications v1.2.5
        • Appendix 4 - AdE errors file specifications
        • Appendix 5 - Logback configuration
        • Appendix 6 - Configuration properties
        • Appendix 7 - Console log overview
        • Appendix 8 - Database connection for Spring Batch
        • Appendix 9 - FAQ & Troubleshooting
        • Appendix 10 - Python and Poetry installation
        • Appendix 11 - List of output and log files
      • Api Integration
  • Glossary
  • RTD documentation
    • Input file specifications
Powered by GitBook
On this page
  1. Centro Stella
  2. Instructions for Agenzia delle Entrate Mandate
  3. Appendixes

Appendix 3 - AdE output file specifications

The following specification is referred to the latest version.

This chapter describes the structure of the output file, i.e. the file that contains the aggregates.

The naming convention of the file is as follows:

  • [service].[ABI].[filetype].[date].[time].[nnn].[nn].csv

In particular:

Field

format

notes

[service]

Alphanumeric - 5 char

fixed value ADE

[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) in the same day

[nn]

Alphanumeric - 2 char

Chunk number starting from 01 to 99 depending on the file output size

Please note that:

  • the file is in .csv type, with separator “;”

  • the csv produced by PagoPA will be encrypted with a PGP public key

  • the contents of the file do not include head and tail rows

Fields in the output file

Field number

Field name

Type

Mandatory

Note

2

Sender_Code

Alphanumeric - max 5 char

YES

ABI code of the transmitting subject or a unique code assigned to the transmitting subject by PagoPA

3

Operation_type

Alphanumeric - regexp [0-9]{2}

YES

Operation type:

  • 00 - payment

  • 01 - payment reversal

4

Transmission_date

FORMAT ISO8601 yyyy-MM-dd

YES

Date of transmission of the transactions by the acquirer

5

Operation_date

FORMAT ISO8601 yyyy-MM-dd

YES

Accounting date of operations

6

Transaction number

Entire

YES

Number of transactions

7

Total_amount

Entire

YES

Valued in euro cents (eg: € 10 = 1000) and expressed as an absolute value: the sign is deducted from the type of operation "00-payment, 01-reversal"

8

Currency

Alphanumeric - max 3 char

YES

Fixed value 978 = EUR. ISO 4217 alpha-3: 201 international encoding is used.

9

Acquirer_id

Alphanumeric - max 255 char

YES

ABI code of the subject obliged or Tax Code of the subject obliged in the case of subjects without ABI

10

Merchant_id

Alphanumeric - max 255 char

YES

Agreement code of the merchant with the acquirer

11

Terminal_id

Alphanumeric - max 255 char

YES

Terminal / POS (Point of Sale) identifier used by the person who collects the payments with POS.

Technical identification code of the terminal at the payment gateway.

12

Fiscal_code

Alphanumeric - min 11 max16 char

YES

Tax code of the person using the POS

13

VAT

Alphanumeric of 11 char

NO

VAT number of the person using the POS

14

Pos_type

Alphanumeric - regexp [0-9]{2}

YES

POS tyoe:

  • 00 – fisical pos

  • 01 - ecommerce

PreviousAppendix 2 - Input file specificationsNextAppendix 3 - AdE output file specifications v1.2.5

Last updated 1 year ago