Overview

The Evo Payment clearing and settlement system generates a detail file containing all network token cryptograms from the previous calendar day's daily cutoff cycle according to the customer's specified daily cutoff time, for customers to perform automated transaction matching and reconciliation.

Note :

The file includes online transactions in all transaction statuses (including failed transactions);

If the customer generated no online transactions on the previous day, an empty file is generated, retaining only the field names and end marker END;

After the large-file splitting feature is enabled, the file name will include a BatchNum (001–999) suffix.

File location and naming rules

File levels and file codes

Evo Payment can generate details at different dimensions based on the different levels configured for the customer in the system. File codes and report names are distinguished by level as follows:

File level	File code	Report name template
Acquirer level	A-File-08	`Acquirer_Network_Token_Cryptogram_Detail_(Version No)_(Inscode)_YYYYMMDD`
Group level	G-File-08	`Group_Network_Token_Cryptogram_Detail_(Version No)_(Groupcode)_YYYYMMDD`
Merchant level	M-File-08	`Merchant_Network_Token_Cryptogram_Detail_(Version No)_(Merchantcode)_YYYYMMDD`
Store level	S-File-08	`Store_Network_Token_Cryptogram_Detail_(Version No)_(Storecode)_YYYYMMDD`

File name field descriptions

Each field is joined with an underscore (_), and the field meanings are as follows:

Field	Description
Fixed value	`Acquirer_Network_Token_Cryptogram_Detail` / `Group_Network_Token_Cryptogram_Detail` / `Merchant_Network_Token_Cryptogram_Detail` / `Store_Network_Token_Cryptogram_Detail`, corresponding to that level
Version number	The first character is the file identifier: `P` for the production environment and `T` for the test environment; the last three characters are a numeric number, from `001` to a maximum of `999` (new versions are compatible with old versions)
Inscode/Groupcode/Merchantcode/Storecode	The customer's Acquirer, Group, Merchant, or Store identifier
Date	`YYYYMMDD`, the report generation date
Batch number (optional)	Added when the Acquirer file is configured with the `Batch Generate Threshold` feature, with a value range of `001`–`999`

File name examples

Production environment (Acquirer level)

Acquirer_Network_Token_Cryptogram_Detail_P003_88888888_20230108.csv

Test environment (Acquirer level)

Acquirer_Network_Token_Cryptogram_Detail_T003_88888888_20230108.csv

With batch number (Acquirer level)

Acquirer_Network_Token_Cryptogram_Detail_P003_88888888_20230108_001.csv

Item	Description
SFTP mode	Evo Payment is the SFTP Server
Default directory	`/in/{YYYYMMDD}`
Login method	Public/private key
Transfer completion marker	Empty TXT file with the same-name `.ok` suffix (e.g. `Acquirer_Network_Token_Cryptogram_Detail_P003_88888888_20230108.csv.ok`)

Important : Before pulling and parsing the reconciliation file, the client should first check whether the same-name .ok file exists to confirm that Evo Payment has completed the file transfer.

Report structure

Basic file properties

Property	Value
File format	CSV
File encoding	UTF-8 with BOM
Line break	`\n` (`0x0A`)
Field delimiter	Double quote + comma `","`
File content end marker	`*END*` (last line)

File generation time

Generation cycle: calendar-day file, generated every Monday through Sunday

Generation time: daily 10:00–12:00 AM (Evo Payment node system time)

File data elements

This section defines the data elements of the File-08 Network_Token_Cryptogram_Detail file.

No.	Field name	Description
1	Group ID	Group number Appears only in Acquirer-level files
2	Group Name	Group name Appears only in Acquirer-level files
3	Merchant ID	Merchant number Appears only in Acquirer- and Group-level files
4	Merchant Name	Merchant name Appears only in Acquirer- and Group-level files
5	Store ID	Store number Appears only in Acquirer-, Group-, and Merchant-level files
6	Store Name	Store name Appears only in Acquirer-, Group-, and Merchant-level files
7	Merchant Txn Time	Merchant transaction time
8	API Type	API category
9	Txn Type	Transaction type
10	Payment Brand	Payment brand
11	Merchant Txn ID	Merchant transaction number
12	Merchant Order Reference	Merchant order reference information
13	Card Number	Card number (first 6******last 4)
14	Merchant Txn Curr	Merchant local currency
15	Merchant Txn Amt	Merchant transaction amount
16	Authentication Type	Authentication type
17	ECI	Authentication indicator
18	Txn Status	Transaction status
19	Token ID	Token number
20	Token Reference ID	Unique token reference number
21	Token	Token (first 6******last 4)
22	Payment Account Reference	Payment account reference
23	Metadata	Remarks

Samples

Group ID	Group Name	Merchant ID	Merchant Name	Store ID	Store Name	Merchant Txn Time	API Type	Txn Type	Payment Brand	Merchant Txn ID	Merchant Order Reference	Card Number	Merchant Txn Curr	Merchant Txn Amt	Authentication Type	ECI	Txn Status	Token ID	Token Reference ID	Token	Payment Account Reference	Metadata
A679882	Group9	M228718	Merchant31	S819947	Store49	2028-07-07T10:48:03+08:00		Cryptogram	VIS	gxt_hxerfqoj5z94794_RA_56q1444i		903207******2875					Success	6013yoa37533e41g8424939hi859b119	DNITHE260349868657627826	104717******7873	V1188181795690816544729077347

File-08 Network_Token_Cryptogram_Detail Network Token Cryptogram Detail File

Overview#

File location and naming rules#

File levels and file codes#

File name field descriptions#

File name examples#

SFTP path and login#

Report structure#

Basic file properties#

File generation time#

File data elements#

Samples#