Technical Specifications on Bankcard Interoperability

Part III File Interface

Version 23.1

October 2022
THIS PAGE IS INTENTIONALLY LEFT BLANK.
 Part III: File Interface

Copyright
UnionPay International Co. Ltd. (“UnionPay International”) retains intellectual property rights concerning this
specifications document and all other documents referenced, attached, and produced by UnionPay International,
including but not limited to copyright, patents, trademarks, and trade secrets. Any use of this specifications
document by any legal and/or natural person is limited by the rules specified in the agreement signed by UnionPay
International Institution Services Portal (https://inst.unionpayintl.com) and UnionPay International. UnionPay
International shall not be liable for any errors or omissions in this specifications document or any losses resulting
therefrom.
Without UnionPay International’s written consent, you may not use this specifications document for uses and
purposes aside from matters involving cooperation with UnionPay International. Without UnionPay International’s
written consent, you may not download, forward, or, publically or in any other form, provide this specifications
document to third parties. If any legal and/or natural person used illegal means to obtain this specifications document,
please immediately delete it and notify UnionPay International.
UnionPay International makes no representations or warranties, including but not limited to, whether or not this
specifications document or its related documents infringe upon the intellectual property rights of third parties. The
user agrees that UnionPay International shall not be liable relating to whether or not the use of this specifications
document infringes on third party rights.

© 2012-2022 UnionPay International Co. Ltd. All rights reserved.

Trademarks
UnionPay International Co. Ltd. (“UnionPay International”) and its various forms are registered trademarks of
UnionPay International Co. Ltd. and its Affiliate(s). All other company or product names mentioned herein are
trademarks of their respective companies.

© 2012-2022 UnionPay International Co. Ltd. All rights reserved.

QR Code is a registered trademark of DENSO WAVE.

UPI CONFIDENTIAL I
 Part III: File Interface

Table of Contents
ABOUT THIS DOCUMENT ...................................................................................................................................... VI
SUMMARY OF REVISIONS ...................................................................................................................................VIII
TERMS AND DEFINITIONS ...................................................................................................................................... X
1 EXPLANATIONS ON FILE ACCESS MODE .......................................................................................................... 1
1.1 FLOW TRANSMISSION MODE ................................................................................................................................2
Applicable Scope ....................................................................................................................................2
Flow Transmission Message Type ..........................................................................................................2
File Processing ........................................................................................................................................3
Message Format Description .................................................................................................................5
1.2 SFTP MODE ......................................................................................................................................................9
SFTP Introduction .................................................................................................................................10
Technical Requirements .......................................................................................................................11
SFTP Server Parameters .......................................................................................................................11
Access Control ......................................................................................................................................12
2 BASIC SPECIFICATIONS.................................................................................................................................. 14
2.1 BASIC NAMING CONVENTIONS OF UPI FILES ..........................................................................................................14
2.2 TRANSACTION CODE..........................................................................................................................................15
2.3 FILE STRUCTURE ...............................................................................................................................................15
Structure of Audit Trailer ......................................................................................................................15
Structure of Sequential File ..................................................................................................................15
2.4 RECORD FORMAT ..............................................................................................................................................15
2.5 RECORD FORMAT IN COMMON USE .....................................................................................................................16
TC 000- File Header ..............................................................................................................................17
TC 001- File Trailer................................................................................................................................18
TC 002- Reject Record ..........................................................................................................................18
TC 003- Error File Record ......................................................................................................................19
2.6 DEFINITION OF SYMBOLS ....................................................................................................................................19
2.7 DEFINITIONS OF SPECIAL DATA ITEMS....................................................................................................................20
3 AUDIT TRAILER ............................................................................................................................................. 21
3.1 OVERVIEW OF AUDIT TRAILER .............................................................................................................................21
Function of Audit Trailer.......................................................................................................................21
Naming Rules for Audit Trailer .............................................................................................................21
Audit Trailer Processing .......................................................................................................................22
File List and Access Mode of Audit Trailer ............................................................................................23
UPI CONFIDENTIAL II
 Part III: File Interface

3.2 FORMAT OF AUDIT TRAILER ................................................................................................................................24

General Format of Audit Trailer ...........................................................................................................24
Format of General Transaction Audit Trailer........................................................................................25
Format of General Transaction Audit Trailer (New) .............................................................................30
Format of General Transaction Audit Trailer for Secondary Member ..................................................33
Format of Dispute Transaction Audit Trailer ........................................................................................35
Format of Dispute Transaction Audit Trailer (New) .............................................................................40
Format of Dispute Transaction Audit Trailer for Secondary Member ..................................................43
Format of UICS IC Card E-cash Application Loading Transaction Audit Trailer ....................................44
Format of UICS IC Card Dispute Transaction Audit Trailer ...................................................................44
Format of Real-time Stand-in Authorization Transaction Audit Trailer ................................................52
Format of Stand-in Authorization Transaction Fee Audit Trailer ..........................................................57
Format of Brand Service Fee Audit Trailer (Not Used Currently) ..........................................................60
Format of Fee Collection and Fund Disbursement Transaction Audit Trailer .......................................60
Format of Fee Collection and Fund Disbursement Transaction Audit Trailer for Secondary Member .61
Format of Directly-connected POS Transaction Audit Trailer ...............................................................62
Format of UPI Institution Fee Settlement File ......................................................................................64
4 SETTLEMENT FILE ......................................................................................................................................... 69
4.1 OVERVIEW OF SETTLEMENT FILE ..........................................................................................................................69
Function of Settlement File ..................................................................................................................69
Naming Rules for Settlement File .........................................................................................................69
Settlement File Processing ...................................................................................................................70
File List and Access Mode of Settlement File ........................................................................................71
4.2 FORMAT OF SETTLEMENT FILE .............................................................................................................................71
TC 100/101/102- Transaction Record ..................................................................................................71
TC 900- Fund Settlement Record ..........................................................................................................86
TC 901/902 STF Statistics .....................................................................................................................87
Format of International Transaction Settlement File for Secondary Member .....................................88
Format of International Transaction Statistics File for Secondary Member .........................................89
5 IC CARD INFORMATION FILE ......................................................................................................................... 90
5.1 OVERVIEW OF IC CARD INFORMATION FILE ............................................................................................................90
Function of IC Card Information File ....................................................................................................90
Naming Rules for IC Card Information File ...........................................................................................90
IC Card Information File Processing .....................................................................................................90
File List and Access Mode of IC Card Information File ..........................................................................91

UPI CONFIDENTIAL III

 Part III: File Interface

5.2 FORMAT OF IC CARD INFORMATION FILE ...............................................................................................................91

TC 100/101/300/301- Transaction Record Based on Domestic UICS Debit/Credit Standards ............91
6 IC CARD OFFLINE PURCHASE FILE ................................................................................................................. 95
6.1 OVERVIEW OF IC CARD OFFLINE PURCHASE FILE .....................................................................................................95
Function of IC Card Offline Purchase File .............................................................................................95
Naming Rules for IC Card Offline Purchase File ...................................................................................95
IC Card Offline Purchase File Processing ..............................................................................................96
File List and Access Mode of IC Card Offline Purchase File ..................................................................97
6.2 FORMAT OF IC CARD OFFLINE PURCHASE FILE ........................................................................................................97
TC 300/301- Offline Transaction Record ..............................................................................................97
TC 900- Fund Settlement Record ........................................................................................................101
TC 901/902 Offline Transaction Statistics ..........................................................................................102
7 REPORT FILE ............................................................................................................................................... 104
7.1 OVERVIEW OF REPORT FILE...............................................................................................................................104
Function of Report File .......................................................................................................................104
Naming Rules for Report File .............................................................................................................104
Report File Processing ........................................................................................................................104
7.2 FORMAT OF REPORT ........................................................................................................................................105
C602DZ- UPI Institution Net Settlement Summary .............................................................................105
C603DZ- UPI Net Settlement Summary ..............................................................................................107
C603DZN- UPI Net Settlement Summary (New) – UPI Internal Use Only ...........................................107
C605DZ- Institution Dispute Resolution Detail ...................................................................................112
C606DZ- UPI Institution (UPI POS) Merchant Net Settlement Report ................................................113
C607DZ- UPI Institution (UPI POS) Merchant Reconciliation List .......................................................114
C608DZ- UPI Institution (Acquirer Side) Outgoing STF Processing Feedback .....................................115
C612DZ- UPI Institution Settlement Reconciliation Report ................................................................116
C614DZ- UPI Issuer Domestic and Cross-Border Transaction Settlement Report ...............................117
C615DZ- UPI Acquirer Domestic and Cross-Border Transaction Settlement Report ...........................119
C616DZ- UPI Institution (Acquirer) Outgoing Unsettled Transactions Reminding (Over 20 days till 29
days) Report .......................................................................................................................................................122
C618DZ- Institution Non-Dispute Fee Collection and Fund Disbursement Detail Report ...................123
C802DZ- Tax Refund Report................................................................................................................124
8 OTHER FILES ............................................................................................................................................... 126
8.1 OVERVIEW OF OTHER FILES ..............................................................................................................................126
Function of Other Files .......................................................................................................................126

UPI CONFIDENTIAL IV
 Part III: File Interface

Naming Rules for Other Files .............................................................................................................126

Other Files Processing ........................................................................................................................126
File List and Access Mode of Other Files ............................................................................................126
8.2 FORMAT OF OTHER FILES..................................................................................................................................127
Exchange Rate Update File ................................................................................................................127
BIN Update File ..................................................................................................................................127
9 STAND-IN PARAMETER SYNCHRONIZING FILE ............................................................................................. 132
9.1 OVERVIEW OF STAND-IN PARAMETER SYNCHRONIZING FILE ....................................................................................132
Structure of Stand-in Parameter Synchronizing File ...........................................................................132
Stand-in Parameter Synchronizing File Processing ............................................................................132
File List of Stand-in Parameter Synchronizing File..............................................................................133
9.2 FORMAT OF STAND-IN PARAMETER SYNCHRONIZING FILE RECORD ...........................................................................138
TC800 (PVN) .......................................................................................................................................138
TC801 (BIN) ........................................................................................................................................138
TC802 (STP) ........................................................................................................................................141
TC803 (VIP).........................................................................................................................................142
TC804 (MCT) ......................................................................................................................................144
TC805 (ARQ) .......................................................................................................................................145
TC806 (XVR) .......................................................................................................................................145
TC807 (RTP) ........................................................................................................................................146
TC808 (MTP) ......................................................................................................................................147
TC809 (ATP) ........................................................................................................................................147
10 BATCH FILE.............................................................................................................................................. 149
10.1 OVERVIEW OF BATCH FILE ................................................................................................................................149
Structure of Batch File ........................................................................................................................149
Batch File Processing ..........................................................................................................................149
File List of Batch File ...........................................................................................................................151
10.2 FORMAT OF BATCH FILE RECORD........................................................................................................................153
TC700 .................................................................................................................................................153
TC701 .................................................................................................................................................153
TC702 (Rejected Record) ....................................................................................................................153
TC703 (Error File Record) ...................................................................................................................154
TC704 (Response Record) ...................................................................................................................154
TC705 (Recurring), TC706 (Primary Credit) and TC707 (MOTO) .........................................................155

UPI CONFIDENTIAL V
 Part III: File Interface

About this Document

Purpose
The Technical Specifications on Bankcard Interoperability - Part III File Interface is one of the six parts comprising the
Technical Specifications on Bankcard Interoperability. The document specifies the file exchange relationship between
UPI and UPI Members in the inter-bank transaction network, including requirements on the file access mode, file
name, and record format.
Audience
The audience of this document are UnionPay International (UPI) staff and UPI Members and Special Participants who
have adopted message format version 2.1 (the message format version is indicated in the online message header).

Document Version
Version 23.1 replaces the previous version.

Revisions
UPI will periodically issue updates to this document, as enhancements and changes are implemented or corrections
are required. Occasionally, updates to this document will be published in an Operation Bulletin.
Please refer to the Summary of Revisions for changes in this version.

Time Expressed
UPI has operation centers in several locations, including Shanghai and Beijing. For operational purposes, the time
frame in this document, unless particularly indicated, refers to “Beijing time”. Coordinated Universal Time (UTC) is
the global standard time by which the world follows. Beijing time is 8 hours ahead of UTC. There is no Daylight Saving
Time in China.
Unless otherwise specified, the “day” mentioned in this document refers to the calendar day. The “business day”
refers to the working day subject to local regulations of the country where the processing Member is located.
Application Scope
This document applies to all UPI Members and Special Participants.

References
The terms and conditions in this document have quoted the following publications. Any later versions of these
publications will be applied in this document unless otherwise specified. Members are encouraged to study the latest
versions of such documents and decide whether to apply.
OR UPI Operating Regulations
UICS UnionPay Integrated Circuit Card Specifications
EMV 4.3 Integrated Circuit Card Specification for Payment Systems: Book 1 ~ Book 4

Support
Please address your questions to your UnionPay representatives.

UPI CONFIDENTIAL VI
 Part III: File Interface

Word Convention
Convention Tone Implication
Shall Mandatory Must be followed without exception
Should Optional but recommended Required to follow but optional
Must Mandatory Required without exception
Must not Mandatory Not required
Could Optional Hypothetical
Can Optional Stating a capability
Cannot Optional Stating an incapability
May Optional Stating a possibility

Style Convention
Convention Description
boldface Note/emphasis
italic Publications/book titles
monospace Filename/Command

UPI CONFIDENTIAL VII

 Part III: File Interface

Summary of Revisions
Description of Changes Location
Added letter “B- File for UPI internal use” in pos. 3 (file type) to the file name to 2.1 Basic Naming
clarify the naming rules of files for UPI internal use. Conventions of UPI
Files
Added the pricing scheme code “47” for domestic transactions in Cambodia in general 3.2.2 Format of
transaction audit trailers, and reserved code “24” for future use. General Transaction
Audit Trailer
Added the pricing scenario of transactions between the EEA countries and Andorra 3.2.2 Format of
under pricing scheme code “05”, and the pricing scheme code “48” for domestic General Transaction
transactions in Andorra, in general transaction audit trailers. Audit Trailer
Added a description to ECI to clarify the value used: “When ECI is different in the 3.2.2 Format of
request and response of an authorization (in scenarios like 3DS downgrading), value in General Transaction
the response shall be used.” Audit Trailer
Reserved seq.16 and added sub-merchant ID in seq.17 in the General Transaction 3.2.3 Format of
Audit Trailers (New)- Additional Part for Acquirer, and reserved this sequence in the General Transaction
General Transaction Audit Trailers (New)- Additional Part for Issuer. Audit Trailer (New)
Added the pricing scheme code “47” for domestic transactions in Cambodia in dispute 3.2.5 Format of
transaction audit trailers, and reserved code “24” for future use. Dispute Transaction
Audit Trailer
Added the pricing scenario of transactions between the EEA countries and Andorra 3.2.5 Format of
under pricing scheme code “05”, and the pricing scheme code “48” for domestic Dispute Transaction
transactions in Andorra, in dispute transaction audit trailers. Audit Trailer
Reserved settlement file name “OFBYYMMDD??C” for UPI internal use. 4.1.2 Naming Rules for
Settlement File
Added the pricing scheme code “47” for domestic transactions in Cambodia in 4.2.1.1 Block 0- Basic
settlement files block 0 of TC 100, 101, 102, and reserved code “24” for future use. Settlement
Information
Added the pricing scenario of transactions between the EEA countries and Andorra 4.2.1.1 Block 0- Basic
under pricing scheme code “05”, and the pricing scheme code “48” for domestic Settlement
transactions in Andorra, in settlement files block 0 of TC 100, 101, 102. Information
Added a note to require that file date shall be at least 1 day later than date of 4.2.1.1 Block 0- Basic
authorization: Settlement Information
“Due to discrepancy between cut-off (set as “T+1” for online messages from 11:00 pm
on T day to 11:00 pm on T+1 day) and switch of file date (set as “T+1” for submission
from 04:00 am on T day to 04:00 am on T+1 day), transactions authorized between
11:00 pm on T day to 04:00 am on T+1 day shall be submitted for settlement after
04:00 am on T+1 day, so that the transaction can be settled by cut-off of T+1 day. That
is, file date shall be at least 1 day later than date of authorization.”
Modified the submission requirement of E-commerce Indicator (ECI, Field 60.2.8) in 4.2.1.1 Block 0- Basic
Block 0 in TC 100/101/102 of settlement files, to clarify that ECI value in the response Settlement Information
shall be used when it is different in the request and response of an authorization.
Added a description: “In a file, multiple records can be present in the case of 4.2.2 TC 900- Fund

UPI CONFIDENTIAL VIII

 Part III: File Interface

Description of Changes Location

multiple settlement currencies”, and added more description of the data elements Settlement Record
clear up possible misunderstandings.
6.2.2 TC 900- Fund
Settlement Record
Added a description to pos. 24~39 “Amount, credit” and pos. 40~55 “Amount, 4.2.3 TC 901/902 STF
debit”: “The value of this field is an integer, padded with leading zeros. The unit is Statistics
1/10000 of the minor unit of currency” to clear up possible misunderstandings.
6.2.3 TC 901/902
Offline Transaction
Statistics
Added some descriptions to C603DZ: “For Issuers, the report name is 7.2.2 C603DZ- UPI Net
IFRYYMMDD01C603DZ-XXX (Billing currency code)-XXX (Settlement currency code)”, Settlement Summary
and “‘Transaction Currency’ in the report refers to billing currency for Issuers and
transaction currency for the Acquirers”.
Added a description for C603DZN: “This report is for UPI internal use only.” 7.2.3 C603DZN- UPI
Net Settlement
Summary (New) – UPI
Internal Use Only
Added a note for “Discount Amount” in C605DZ: “Note: Fee returned caused by this 7.2.4 C605DZ-
dispute transaction” to facilitate understanding. Institution Dispute
Resolution Detail

UPI CONFIDENTIAL IX
 Part III: File Interface

Terms and Definitions

Term Definition
File It refers to the party sending a file in the file receiving and sending process.
Sender
File It refers to the party receiving a file in the file receiving and sending process.
Accepter
STF It is the abbreviation of settlement file. Outgoing STFs refers to dual-message settlement files
submitted by Members to GSCS; incoming STFs refers to dual-message settlement files submitted
by GSCS to Members.

UPI CONFIDENTIAL X
 Part III: File Interface

1 Explanations on File Access Mode

File exchange happens between the UnionPay International (UPI) File Server and Members. File exchange can be
implemented through flow transmission or SFTP.
Before file transmission, additional file processing can be conducted for higher transmission efficiency, e.g. packing
and compressing.
 Packed and compressed files
UPI will pack and compress the files, and place the compressed package on the UPI File Server. Members shall
decompress and unpack the package at the Member side. Please note that files shall neither be packed nor
compressed while Members are sending them to the UPI File Server.
UPI supports files being packed and compressed in any of the following three formats. A Member shall choose an
appropriate format according to its operating system:
 Files are packed and then compressed by the standard LINUX-based Operating System command “tar” and
“gzip”. The generated files are named with a suffix of “.tar.gz”. Members using LINUX-based or Windows-based
Operating System should choose this format.
 Files are packed and then compressed by the standard Windows-based Operating System command “zip”. The
generated files are named with a suffix of “.zip”. Members using Windows-based Operating System should
choose this format.
 Files are packed and then compressed by the standard UNIX-based Operating System command “tar” and
“compress”. The generated files are named with a suffix of “.tar.Z”. Members using UNIX-based Operating
System should choose this format.
Members should choose appropriate decompressing and unpacking commands or tools to get the original files as
below.
 Using “uncompress” and “tar -xvf” on UNIX-based Operating System.
 Using “tar -xzvf” on Linux-based Operating System.
 Using tools such as “WinZip” or “WinRAR” on Windows Operating System.
File transfer between GSCS and Members is subject to the Transitory Connection mode which is different from real-
time online transaction. The two parties establish a full duplex connection over which sending, receiving requests
and responses are running through. The connection shall be closed after file transfer completes.
The processing flow is as follows:

2
Member GSCS/
/GSCS 3 Member
...

Figure 1 Normal Processing Flow of Establishing a Connection

UPI CONFIDENTIAL 1
 Part III: File Interface

1. Member (GSCS) sends a CONNECT request to GSCS (the Member).

2. GSCS (The Member) ACCEPTs the request from the Member (GSCS) and establishes the connection.
3. The Member (GSCS) initiates file receiving and sending process with GSCS (the Member).
4. The Member (GSCS) initiates disconnection.
Error handling:
In case of a communication error, the initiator of the connection shall disconnect the connection and then re-
establish the connection. For detailed information about the communication process between GSCS and Members,
please refer to the Technical Specifications on Bankcard Interoperability - Part V Communication Interface.

1.1 Flow Transmission Mode

Applicable Scope
Members can fetch and send files using the Flow Transmission Software, which can be either provided by UPI or
developed by Members according to the following specifications.
In the flow transmission mode, GSCS and Members constitute the CLIENT/SERVER structure. GSCS could either act
as the server to accept connection initiated by Members or act as the client to initiate connection with Members.
The flow transmission mode is realized through the interaction of a series of messages.

Flow Transmission Message Type

Table 1 Flow Transmission Message Type

Message Direction of Description Message Category

Type Information
File Transmission Request Messages
8000 SDRC File transmission request The sender requests the receiver to
receive files.
8010 RCSD File transmission request The receiver is ready for receiving files.
response
8100 RCSD File claim request The receiver requests the sender to
send files.
8110 SDRC File claim request response The sender can send files.
File Transmission Advice Messages
8200 SDRC File transmission advice The sender sends data files to the
receiver.
8300 SDRC File transmission end advice File transmission is finished at the
sender.
8310 RCSD File transmission end advice File receiving is finished as the receiver.
response
File Inquiry Message
8400 RCSD File inquiry request The receiver sends file inquiry request
to the sender.

UPI CONFIDENTIAL 2
 Part III: File Interface

Message Direction of Description Message Category

Type Information
8410 SDRC File inquiry request response The sender sends inquiry result files.

File Processing
File processing is for mutual transmission between GSCS and Members, and files of any types can be queried or
transmitted.
1.1.3.1 File Inquiry

2
Member GSCS
...

Figure 2 Normal Processing Flow of File Inquiry

File inquiry is for Members to send inquiry requests to GSCS to get attainable file information, and GSCS will return
inquiry results including the file name and the file length.
The file inquiry flow is as follows:
1. A Member sends an inquiry request 8400 message to GSCS.
2. GSCS returns the response 8410 message with the inquiry result to the Member.
3. There could be multiple response 8410 messages, and the transmission end is indicated by the end flag in the
message.
 Error handling:
Flow 1:
a) If no response is received from GSCS after the Member sends the inquiry request 8400 message to GSCS, the
Member will wait till timeout and exit the processing after timeout.
b) If an unexpected or wrong message is received from GSCS after the Member sends the inquiry request 8400
message to GSCS, the Member will exit the inquiry processing directly.
Flow 3:
a) When timeout occurs while Member is waiting for the response 8410 message with the end flag, the Member
will exit the processing due to timeout.
1.1.3.2 File Transmission
File transmission is the process that the sender initiates to send files to the receiver. Both Members and GSCS can
implement file transmission. The file transmission flow is as follows:

UPI CONFIDENTIAL 3
 Part III: File Interface

1
2
Sender 3 Receiver
4
5

Figure 3 Normal Processing Flow of File Transmission

1. A sender sends a file transmission request 8000 message to the receiver.

2. The receiver returns the response 8010 message to the sender.
3. The sender sends the data transmission 8200 message with the file contents to the receiver.
4. After data transmission is over, the sender sends the file end advice 8300 message to the receiver.
5. After verifying the file, the receiver sends the end response 8310 message to the sender.
 Error handling:
Flow 2:
a) When the sender receives the 8010 response with a non-zero response code after sending the 8000 message,
the transmission will be halted and the file transmitted will be invalid.
b) When the sender receives an unexpected or wrong message, the transmission will be halted and the file
transmitted will be invalid.
c) When timeout occurs while the sender is waiting for a response, and the transmission will be halted and the
file transmitted will be invalid.
Flow 5:
a) When the sender receives the 8310 response with a non-zero response code, the transmission will be halted
and the file transmitted will be invalid; meanwhile, the sender will adjust the file according to the reason of the
error.
b) When the sender receives an unexpected or wrong message, the transmission will be halted and the file
transmitted will be invalid.
c) When timeout occurs while the sender is waiting for response, the transmission will be halted and the file
transmitted will be invalid.
1.1.3.3 File Claim
File claim is the process that the receiver initiates to retrieve files from the sender. Both Members and GSCS can
implement file retrieval. GSCS can retrieve files from Members when the Members fail to upload the files.
The file retrieval flow is as follows:

UPI CONFIDENTIAL 4
 Part III: File Interface

1
2
Sender 3 Receiver
4
5

Figure 4 Normal Processing Flow of File Claim

1. A receiver sends a file retrieval request message (8100 message) to the sender.
2. After the sender finds the file based on the file name, it will send response message (8110 message) to the
receiver.
3. The sender sends the data transmission message (8200 message) containing file contents to the receiver.
4. After data transmission is finished, the sender sends the file end advice message to the receiver.
5. After verifying files, the receiver sends the end response message (8310 message) to the sender.
 Error handling:
Flow 2:
a) The sender receives the 8110 response with a non-zero response code after sending the 8100 message, and
then the transmission will be halted.
b) If the receiver receives an unexpected or wrong message, the transmission will be halted and the file
transmitted will be invalid.
c) If the timeout occurs while the receiver is waiting for a response, the transmission will be halted and the file
transmitted will be invalid.
Flow 3:
a) If the receiver receives an unexpected or wrong message, the transmission will be halted and the file
transmitted will be invalid.
b) If the timeout occurs while the receiver is waiting for a response, the transmission will be halted and the file
transmitted will be invalid.
Flow 4:
a) If the receiver receives an unexpected or wrong message, the transmission will be halted and the file
transmitted will be invalid.
b) If the timeout occurs while the receiver is waiting for a response, the transmission will be halted and the file
transmitted will be invalid.
Flow 5:
a) If errors occur in the process of file receipt, after receiving the 8300 message, the receiver will send the 8310
response with a non-zero response code, and then the file claim will be halted.

Message Format Description

UPI CONFIDENTIAL 5
 Part III: File Interface
For basic specifications on the message format, please refer to the Technical Specifications on Bankcard
Interoperability - Part II Online Message.
1.1.4.1 File Inquiry Message
 File Inquiry Request Message:
The message is used for an inquiry sender (Member) to submit a file inquiry request to an inquiry receiver (GSCS),
and the standard format is detailed as follows:
Table 2 File Inquiry Request Message

File Inquiry Request (24 Bytes in Total)

Field Format Description Presence
Message Type n4 Valid value: M
8400
Settlement an11 Settlement institution identification code for inquiry sender, left- M
Institution ID justified with trailing spaces if the length is less than 11 digits.
File Date n8 File date (YYYYMMDD) M
File Type ID an1 Valid value: M
0- inquiry of all kinds of files matching File Date.
For details, please refer to the File Type in Section 2.1 Definitions of
File Name Basic Structures.
 File Inquiry Response Message:
Table 3 File Inquiry Response Message

File Inquiry Response (Maximum 1518 Bytes in Total)

Field Format Description Presence
Message Type n4 Valid value: M
8410
Settlement an11 Settlement institution identification code for inquiry sender, left- M
Institution ID justified with trailing spaces if the length is less than 11 digits.
End Flag an1 End flag of whether inquiry is over M
Valid values:
Y- Yes
N- No
File Information n2 Number of the pieces of the file information in the message, 30 M
Number maximum.
The following two fields can appear 30 times at most.
File Length n10 File length measured in byte. M
File Name ans40 File name, left-justified with trailing spaces if the length is less than M
40 digits.

1.1.4.2 File Transmission Start Control Message

This kind of message is used, before file transmission, for the information exchange between the sender and the

UPI CONFIDENTIAL 6
 Part III: File Interface

receiver, to confirm whether the file transmission can be processed normally.

Messages of this kind are subject to the same message format. The message type and the message processing
method can be judged based on the value of the message header.
Table 4 File Transmission Start Control Message

File Transmission Start Control (114 Bytes in Total)

Field Format Description Request Response
Message Type n4 Valid value: M M
8000- Request for REMOTE receiving files and
generated by the sender
8010- Ready for REMOTE receiving files and
returned by the receiver
8100- Request for REMOTE sending files and
generated by the receiver
8110- Start REMOTE sending files and returned
by the sender
File Name a ans40 File name, left-justified with trailing spaces if the M M
length is less than 40 digits.
Settlement an11 Settlement institution identification code, left- M M
Institution ID justified with trailing spaces if the length is less
than 11 digits.
File Date n8 File date (YYYYMMDD) M M
Compress Flag b an1 Query about whether the file is compressed M M
Valid values:
Y- Yes
N- No
Response Code an2 Valid values for message type 8010: M
00- Successful
D1- IIN error
D2- Date error
D3: Invalid file type
D4: Processed files
D6: Not supported by the receiver
D7: File is locked (Reserved)
D8: Unsuccessful
DB: File name error c
DC: Unable to receive file
Valid values for message type 8110:
00- Successful
D1- IIN error
D2- Date error
D3: Invalid file type
D5: No such kind of file
D7: File is locked (Reserved)
D8: Unsuccessful

UPI CONFIDENTIAL 7
 Part III: File Interface

File Transmission Start Control (114 Bytes in Total)

Field Format Description Request Response
d
Initial Position n10 Initial position for file transmission M M
Total Length n10 Total file length e M M
File Timestamp n10 Filled with all 0s if it is not broken download M M
resumption
Current n10 Filled with all 0s if it is not broken download M M
Timestamp resumption
Self-defined Field ans8 Padded with spaces M M
Note: When broken downloads resumption occurs, the sender of the file transmission start control message
has to correctly fill in the File Timestamp and Current Timestamp, making it easier for the message receiver
to judge whether the file transmission should be resumed. If the file has been updated, transmission should
start from the initial position instead of the broken point. If the file has not been updated, transmission can
be resumed. Therefore, whether broken downloads resumption is needed depends on whether the file has
been updated or not. Details of the judgement go as follows:
1) If broken downloads resumption is initiated by a file sender (the party who has the file), the file receiver
needs to judge whether broken downloads resumption is needed. If the (Current Timestamp – File
Timestamp) filled by the file sender is greater than the (Current Timestamp – File Timestamp) recorded by
the file receiver, it indicates that the file has not been updated and broken downloads resumption can be
applied. The file receiver returns the correct values of Initial Position, File Timestamp, and Current
Timestamp to the file sender. If the value of the (Current Timestamp – File Timestamp) entered by the file
sender is less than that of the (Current Timestamp – File Timestamp) recorded by the file receiver, it indicates
that the file has been updated and the file needs to be re-sent from the initial position. The file receiver
returns the correct value of the Initial Position being all 0s to the file sender.
2) If broken downloads resumption is initiated by the file receiver, the file sender needs to judge whether
broken downloads resumption is necessary. Details of the judgement are the same as the above-stated.
Note a: A suffix will be added at the end of the File Name to indicate whether the file has been compressed
or encrypted before transmission:
1) If the file itself is compressed but not encrypted, its suffix will be “.Z”;
2) If the file itself is neither compressed nor encrypted, no suffix will be applied;
3) If the file itself is encrypted but not compressed, its suffix will be “.E”;
4) If the file itself is compressed and encrypted, its suffix will be “.Z.E”.
The real file name before transmission shall be filled in this field, no matter whether the file is re-encrypted
during transmission. The suffix “.E” acts as the indicator to distinguish whether the file is encrypted.
Note b: The Compress Flag indicates whether the file has been compressed during transmission. The value
“Y” indicates that the file will be compressed again during transmission. The receiver shall de-compress the
file and conduct following procedures according to the File Name.
Note c: The file name error refers to the case in which the file name exceeds the limit or contains invalid
characters.
Note d: When there is no broken downloads resumption, Initial Position will be filled with all 0s; otherwise,
the broken point position will be filled.
Note e: The total file length refers to the length after the file is additionally processed. If the file is
compressed, it is the length of the file compressed; if the file is encrypted, it is the length of the file
encrypted.

UPI CONFIDENTIAL 8
 Part III: File Interface

1.1.4.3 File Data Transmission Message

The message contains file contents transmitted, and the maximum size of the file contents in each transmitted
message is 1016 bytes. Therefore, data of bigger files will be transmitted in multiple messages.
Table 5 File Data Transmission Message

File Inquiry Response (Maximum 1518 Bytes in Total)

Field Format Description Transmission
Message Type n4 Valid value: M
8200
File Data Length n4 File length measured in byte M
File Data ans..1016 File Data M

1.1.4.4 File Transmission End Control Message

This kind of messages is used for information exchange after file transmission between the sender and the receiver,
to confirm whether the file transmission has been completed successfully.
Messages of this kind are in the same format. The type and processing of a message depend on the values of the
message header.
Table 6 File Transmission End Control Message

File Inquiry Response (Maximum 1518 Bytes in Total)

Field Format Description Request Response
Message Type n4 Valid value: M M
8300- File sending is over and the message is sent by the
sender
8310- File receiving is successful and the message is
returned by the receiver
File Name ans40 M M
Settlement ans11 Settlement institution identification code of the sender M M
Institution ID who asks to end file transmission, left-justified with trailing
spaces if the length is less than 11 digits
File Date n8 Format: YYYYMMDD M M
File Length n10 Actual file length M M
Response Code an2 Valid values: M
00- Successful
D9- File length unmatched
DA- File decompression error
DD- File MAC verification error
Self-defined n10 Padded with spaces M M

1.2 SFTP Mode

Members can upload or download files from the GSCS File Server through SFTP. In the SFTP mode, GSCS and
Members constitute the CLIENT/SERVER structure. The GSCS File Server is working as the server to accept

UPI CONFIDENTIAL 9
 Part III: File Interface

connections initiated by Members who are clients.

To avoid any operation failures, Members shall not use any tool or script based on SCP (SSH Command) to upload or
download files from the UPI SFTP file servers.
 Members Download Compressed File:
UPI creates folders with Members’ Institution Identification Code, e.g. 0800010344, on the UPI SFTP file server. “\in”
and “\out” subfolders are also created for uploading and downloading. UPI places compressed files under “\out” (e.g.
IFDYYMMDDCOMPRESS.tar.gz or IFDYYMMDDCOMPRESS.tar.Z or IFDYYMMDDCOMPRESS.zip). Member’s file
directory on the UPI SFTP file server is as follows..

HOME Directory \0800010344 \in IFDYYMMDDCOMPRESS.tar.gz

Or
\0802020344 \out IFDYYMMDDCOMPRESS.tar.Z
Or
\... IFDYYMMDDCOMPRESS.zip

Figure 5 Member’s Directory on SFTP File Server (Download Compressed File)

 Members Download Original Files:

UPI creates separate folders under “\out” for each date and place original files in these folders. Please note that
Members shall not select this option (Download Original Files) unless confirmed by UPI. Member’s file directory is as
follows.

HOME Directory \0800010344 \in

\0802020344 \out \YYYYMMDD

\... \YYYYMMDD

Figure 6 Member’s Directory on SFTP File Server (Download Original Files)

SFTP Introduction
As an FTP protocol standard accessible industry-wide, SFTP, which is easy to acquire, deploy and operate, has been
adopted in many areas. SFTP software packages are open and free.
1.2.1.1 Working Principles
SFTP adopts key pairs, composed of public keys and private keys, to authenticate clients who initiate connections.
The public key, which is provided by the client, is stored under the client’s directory in the SFTP server, while the
client has its private key. The client authentication procedure is as follows.

1
2
3

SFTP Server 4 Client

Figure 7 SFTP Authentication Procedure

UPI CONFIDENTIAL 10
 Part III: File Interface

1. A client initiates a connection request by its username.

2. While receiving a connection request from the client, the server will look for the client’s public key based on
the client’s username in the request. Then the server generates a random number, encrypts it with the client’s
public key, and sends it to the client. This message is called a challenge message.
3. While receiving the challenge message from the server, the client will use a private key to decrypt the
message and get the random number. Then the client sends this random number to the server in plain text.
4. While receiving the message from client, the server will compare the two random numbers. If the two
numbers are the same, it will indicate that the client has obtained the authorization, and the connection
between the server and the client will be established.
1.2.1.2 Key Generation
The SSH-2 RSA algorithm shall be used for key pair generation at the Member’s SFTP client.

Technical Requirements
1.2.2.1 User Name and Public Key Storage
UPI assigns a username to each Member requesting connection to the UPI SFTP server. The Member, acting as the
SFTP client, generates a pair of public and private keys and sends the public key to UPI. UPI stores the public key
under the corresponding user directory “/home/.ssh”. When the client initiates a connection, the server will match
the public key in corresponding user directory for authentication.
1.2.2.2 Key Length
The key length suggested by UPI is 2048 bits.
1.2.2.3 Key Life Cycle
Members should contact UPI to update the public key(s) which has been used for more than 3 years.
1.2.2.4 Account Control
Members have the access to their own directories only and shall not switch to other directory. Members shall not
make any changes to their own directories (e.g. move, add or change directory etc.). Deletion of any file is not allowed
either.

SFTP Server Parameters

The Daemon which constantly runs on the server side is called “sshd” and its configuration file “/etc/ssh/sshd_config”
describes how to manage each ssh function. “ssh_config” parameters are as follows.
Table 7 SSH Server System Wide Parameter Configurations and Explanations

Parameter Configuration Explanation

Port 9990 The port number that sshd monitors
ListenAddress 0.0.0.0 The IP address bound to the sshd server
HostKey /etc/ssh/ssh_host_key The file including the host private key
ServerKeyBits 2048 The bits of the server key
LoginGraceTime 2m The server waiting time before disconnection in case
user could not log on
KeyRegenerationInterval 1h The period of time after which a key for server is
automatically re-generated (if applicable)

UPI CONFIDENTIAL 11
 Part III: File Interface

Parameter Configuration Explanation

The re-generation is to prevent stealing the key to
decrypt captured information.
PermitRootLogin no Whether to permit the root to log on through the ssh
This option must not be set to ”yes”.
IgnoreRhosts yes Whether to use the files of “rhosts” and “shosts” while
doing authentication
IgnoreUserKnownHosts no Whether to ignore the user’s
“$HOME/.ssh/known_hosts” when the ssh daemon is
doing security authentication
StrictModes yes Whether to check the access to and the ownership of
the user directory and rhosts file before the ssh receives
the log-on request
Such mode is typically necessary because novices usually
assign everyone the write access to their directories and
files.
X11Forwarding no Whether it is permitted to forward X11
PrintMotd yes Whether the sshd will display the information in
“/etc/motd” at the time of log-on
SyslogFacility AUTH Whether to prompt “facility code” while the message
from sshd is written
LogLevel INFO The levels of sshd log messages
INFO is a good option. For more information, please
refer to the sshd help.
RhostsAuthentication no Whether it is enough to use rhosts or “/etc/hosts.equiv”
to carry out security authentication
RhostsRSAAuthentication no Whether it is permitted to use 1) rhosts plus RSA or 2)
“/etc/hosts.equiv” plus RSA to carry out seurity
authentication
RSAAuthentication yes Whether it is permitted to carry out security
authentication with RSA only
PasswordAuthentication yes Whether password authentication is permitted
PermitEmptyPasswords no Whether it is permitted to use a username without a
password to log on
TCPKeepAlive yes Whether the system should send the TCP keep alive
messages to the other side
If they are sent, a dead connection or system crash will
be properly detected.

Access Control
Users’ access should be controlled within their own “/home” directories, so it is necessary to arrange each user in a

UPI CONFIDENTIAL 12
 Part III: File Interface

specific group to define his/her accessible “/home” directory. Please refer to following commands.
groupadd -g 2222 user (set individual user group)
useradd -u 2222 -g 2222 -c "USER sftp Account" -m -d /home/user -s
/bin/ksh user (add user to the group)
passwd user (set password)
xxxx
xxxx
chown -R user:user /home/user (set user’s “/home” to be used by user group)
chmod 500 /home/IIN; (change the access permission to the file directory /home/IIN)
chmod 500 /home/IIN/out;(change the access permission to the file directory /home/IIN/out )
chmod 500 /home/IIN/out/YYYYMMDD(change the access permission to the file directory
/home/IIN/out/YYYYMMDD )
chmod 400 /home/IIN/out/YYYYMMDD/* (change the access permission to all the files and directories under the
/home/IIN/out/YYYYMMDD/ )
chmod 400 /home/IIN/out/*.tar.Z (change the access permission to the file *.tar.Z)
chmod 400 /home/IIN/out/*.tar.gz (change the access permission to the file *.tar.gz)
chmod 400 /home/IIN/out/*.zip (change the access permission to the file *.zip)

UPI CONFIDENTIAL 13
 Part III: File Interface

2 Basic Specifications
2.1 Basic Naming Conventions of UPI Files
This section sets out standard formats of GSCS file names for the purpose of differentiating files by file name.
A file name consists of a basic name and a suffix name. The maximum length of the basic name is 34 bytes; its first
character must be a non-numeric character and all English characters must be capitalized. The suffix name should be
next to the basic name with the maximum length of 6 bytes including “.”. Therefore, the maximum length of the file
name (including the suffix name) is 34 + 6 = 40 bytes.
The basic name of files can be divided into 7 parts, and the structure is as follows:
Table 8 The Value and Sequence Information of File Name Structure

Position Definition Description

1 Direction Tag Valid values:
I- Incoming (file is sent from GSCS to Members)
O- Outgoing (The file is sent from Members to GSCS)
2 Card Transaction Valid value:
Classification Tag F- UnionPay card cross-border transaction
3 File Type Valid values:
D- Audit trailer with details
C- Dual-message settlement file
I- Information file for IC card debit/credit applications based on UICS
debit/credit standards
R- Report file
F- Settlement file for IC card debit/credit applications and e-cash applications
based on UICS standards
T- Stand-in authorization file
O- Other files
B- File for UPI internal use
4~9 File Date Format: YYMMDD
Transaction files submitted by a Member from 04:00 am on T day to 04:00 am
on T+1 day shall be filled with the date of T+1 day. The corresponding rejected
file will be filled with the same date by GSCS when it is sent back to the
Member.
If the Member does not submit any transaction file during the settlement date,
GSCS will automatically generate a rejected file where the file date is the
current date.
For other files, they will be sent by GSCS and postmarked.
10~11 Batch Number/ Valid values:
Sequence 00~99
Number a
Note a: In the following descriptions of file name, position 10~11 will be shown
as “??” to indicate the batch number or the sequence number.
12~18 Business Type File names are classified by business feature. For the files provided to
secondary institutions, B will be added in the file name of these for primary
institutions. For example, COM is for primary institutions while COMB is for
secondary institutions; ERR for primary institutions while ERRB for secondary
UPI CONFIDENTIAL 14
 Part III: File Interface

Position Definition Description

institutions.
19~34 Detailed This element is intended to display file types broken down in a more detailed
Classification way. It is optional. At present, it only applies to some report files and risk files.

2.2 Transaction Code

Transaction codes exist in dual-message settlement files and IC card offline purchase files, indicating various
transaction types. Each of the transaction codes used in this document consist of 3 digits.

2.3 File Structure

This section covers the structures of two types of files, i.e. audit trailer files and sequential files.

Structure of Audit Trailer

The structure of an audit trailer is illustrated as follows:
Transaction Record 1: Field 1 Field 2 Field 3 … Field n
Transaction Record 2: Field 1 Field 2 Field 3 … Field n
Transaction Record 3: Field 1 Field 2 Field 3 … Field n
…
Transaction Record n: Field 1 Field 2 Field 3 … Field n

Figure 8 Structure of Audit Trailer

Note 1: In the same file, the length of each row is the same.
Note 2: Each row represents a transaction record.
Note 3: An “carriage return/linefeed” (0X0D,0X0A) is added after the last field of each row.

Structure of Sequential File

The structure of a sequential file is illustrated as follows:
File Header Record Transaction Record 1 Transaction Record 2 … Transaction Record n File Trailer Record

Figure 9 Structure of Sequential File

Note 1: A sequential file consists of a file header record, a file trailer record, and one or more transaction records,
where each transaction record represents one transaction. These records are kept sequentially rather than
independently. The “carriage return/linefeed (0X0D,0X0A)” is required between each record (exceptionally, there is
no “carriage return/linefeed (0X0D,0X0A)” for Stand-in Parameter Synchronizing File);
Note 2: Each sequential file starts with a file header record and ends with one or more file trailer records;
Note 3: It is optional for sequential files to pass MAC verification. If MAC verification is needed, the file sender fills
the MAC value in the corresponding position of the file trailer, and the file receiver compares the value calculated by
a given algorithm and the MAC value in the file trailer. If the two values are the same, then the MAC verification
result will turn out to be “correct”; otherwise, the entire file will be rejected.

2.4 Record Format

Due to the complexity of business types and the abundance of transaction contents, a transaction might have
multiple features. For example, a settlement transaction involving foreign exchange contains the foreign exchange

UPI CONFIDENTIAL 15
 Part III: File Interface
rate and the currency conversion details, in addition to the information fundamentally required for settlement.
Besides, a cross-border IC card settlement transaction can also contain IC card transaction information, in addition
to the fundamental settlement information and the foreign exchange information.
As these examples indicate, a transaction has multiple features. Therefore, if we capture information of these
features and label each piece of information as a specific "block", it will be very easy to construe an entire transaction
by picking corresponding "blocks" and putting them together. Please note that such record format is not applicable
to audit trailers.
For example, the features of the following settlement transaction can be displayed in four blocks:
 Block 0: basic information of settlement transaction;
 Block 1: foreign exchange information;
 Block 2: additional information specific to IC card settlement transaction;
 Block 3: other settlement information.
Therefore, settlement transactions under different situations can be construed by different combinations of blocks
as follows:
Block 0  Magnetic stripe card settlement transaction
Block 0 Block 1  Magnetic stripe card settlement transaction with foreign exchange rate
Block 0 Block 2  Domestic IC card settlement transaction
Block 0 Block 1 Block 2  Cross-border IC card settlement transaction

Figure 10 File Record Composition

Note: If the Issuer supports Payment Token Service, Block 3 will be present in the settlement file.
For the above reasons, records are defined as follows:
 Each record in the file represents a transaction, which is made up of one or several blocks;
 For each record, Block 0 indicates the fundamental information of the transaction, which is mandatory; Block n
(n>0) indicates some additional information of the transaction, which is optional, and whether it is present
depends on the transaction requirements.
 The file header record and the file trailer record are special records in which only Block 0 will be contained.
 The block bitmap (an4) in Block 0 indicates whether Block n exists or not. The block bitmap is based on the HEX
visible character form, which could indicate 16 blocks at most.
 If a transaction record contains several blocks, these blocks should be sorted in ascending order.
For example, if a record contains Block 0, 2, 3, 4, 9, 12, 13 and 15, its corresponding block bitmap will be “B84D” as
follows:
Block Number 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Block Bitmap 1 0 1 1 1 0 0 0 0 1 0 0 1 1 0 1
Block Bitmap in Hex B 8 4 D

Figure 11 Block Bitmap

2.5 Record Format in Common Use

This section defines four kinds of record formats usually applying to the dual-message file and the IC card offline

UPI CONFIDENTIAL 16
 Part III: File Interface
transaction file, i.e. the file header record format (000), the file trailer record format (001), the reject record format
(002), and the error file record format (004).
The transaction type is indicated by the transaction code. The file header record (000) and the file trailer record (001)
locate respectively at the beginning and end of each file.
The structure of a typical sequential file is as follows:
TC(000) Block 0 … Block n TC Block 0 … Block n … TC Block 0 … Block n TC(001) Block 0 … Block n

File header First record … Last Record File trailer

Figure 12 Structure of A Typical Sequential File

It is optional for sequential files to pass MAC verification. MAC verification is not a must for sequential files without
the file header record and the file trailer record. If MAC verification is chosen, the file sender fills the MAC value in
the corresponding position of the file trailer, and the file receiver compares the value calculated by a given algorithm
and the MAC value in the file trailer. If the two values are the same, then MAC verification will be passed; otherwise,
the entire file will be rejected.
Since the file header record format (000) and the file trailer record format (001) are not contained in the audit trailer,
report file, BIN file, or foreign exchange rate file, MAC is not required for these files.

TC 000- File Header

 Block 0- Basic File Header Format
Table 9 Block 0- Basic File Header Format

Position Format Content Content Description

(Outgoing) (Incoming)
1~3 n3 Transaction Transaction Valid value:
code code 000
4~7 an4 Block bitmap Block bitmap Filled with the Hex characters of the block bitmap.
8~18 ans11 IIN IIN Filled with the forwarding IIN a in the file sent from
Members to UPI. (Exceptionally, filled with IIN of the
real Issuer in Stand-in Parameter Synchronizing File
sent from Members to UPI)
Filled with the receiving IIN in the file sent from UPI
to Members.
Left-justified with trailing spaces if the length is less
than 11 digits.
Note: The forwarding IIN/receiving IIN shall be the IIN
of the file owner.
19~26 an8 Batch date Settlement date Format: YYYYMMDD
for current batch
27~34 an8 GSCS Settlement date Format: YYYYMMDD
reserved
35~38 an4 Version tag Version tag Valid values:
TEST- Test version
PROD- Production version
Note: In the stand-in parameter synchronizing file,

UPI CONFIDENTIAL 17
 Part III: File Interface

Position Format Content Content Description

(Outgoing) (Incoming)
only PROD is permitted.
39~46 an8 Version Version number Filled with 00000001
number

TC 001- File Trailer

 Block 0- Basic File Trailer Format
Table 10 Block 0- Basic File Trailer Format

Position Format Content I/O Description

1~3 n3 Transaction I/O Valid value:
code 001
4~7 an4 Block bitmap I/O Filled with the Hex characters of the block bitmap.
8~17 n10 Transaction I/O Total number of transaction records including transaction Code
record number 000, 001.
18~33 an16 MAK I/O MAC key (consisting of sixteen HEX characters within 0-F, and A-F
should be capitalized) encrypted by MMK.
If MAC verification is not chosen, this field should be filled with
spaces.
34~49 an16 MAC I/O MAC (consisting of sixteen HEX characters within 0-F, and A-F
should be capitalized)
A secure authentication code is generated by the following
method:
1) Divide the whole file (excluding the encryption key and the
secure authentication code) into groups, with each group
containing 256 bytes; make the group up to the full length
with the binary “0” if the length is less than 256 bytes;
2) Form a 256 bytes data block by XOR operation on each
group based on bit;
3) Send the first 128 bytes into the HSM to create an MAC to
get the first 8 bytes of the secure authentication code, and
send the last 128 bytes into the HSM to create an MAC to
get the last 8 bytes of the secure authentication code.
If MAC verification is not chosen, this field shall be filled with
spaces.

TC 002- Reject Record

The reject record indicates GSCS’s rejection to a transaction record, which is different from the error file record.
The reject record is only sent by GSCS.
 Block 0- Basic Reject Format
Table 11 Block 0- Basic Reject Format

UPI CONFIDENTIAL 18
 Part III: File Interface

Position Format Length Content I/O Description

1~3 n 3 Transaction I Valid value:
code 002
4~7 an 4 Block bitmap I Filled with the Hex characters of the block bitmap
8~9 an 2 Reject reason I Please refer to the Response Code section of the
Technical Specifications on Bankcard Interoperability,
Part VI Annex.
9~ ans Variable Contents of I Contents of original transaction are returned.
length rejected
transaction

TC 003- Error File Record

GSCS will check and verify the file uploaded by Members. If any error is found in the file, an error file record will be
generated to indicate rejection to the file. GSCS sends the reject file with the error file record to inform Members
that the previously-uploaded file has been rejected.
The record in the rejection file can be used for rejection to multiple files or transactions, so a reject file may contain
reject record not only to transactions (TC002), but also to files (TC003).
 Block 0- Basic Information of Error Record
Table 12 Block 0- Basic Information of Error Format

Position Format Content I/O Description

1~3 n3 Transaction I Valid value:
code 003
4~7 an4 Block bitmap I Filled with the Hex characters of the block bitmap
8~9 an2 Reject reason I Please refer to the Response Code section of the Technical
Specifications on Bankcard Interoperability, Part VI Annex.
10~29 ans20 File Name I Name of rejected file
30~40 ans11 IIN I Institution identification code of the sender in original files, left-
justified with trailing spaces if the length is less than 11 digits
41~70 ans30 Reserved I Reserved for use

2.6 Definition of Symbols

The definitions of symbols in the file record format are as follows:
Table 13 Basic Specifications on Symbol Definition

Symbol Description
a Alphabetic a-z
n Numeric 0-9
s Special character
an Alphabetic and numeric characters

UPI CONFIDENTIAL 19
 Part III: File Interface

Symbol Description
as Alphabetic and special characters
ns Numeric and special characters
ans Alphabetic, numeric and special characters
MM Month
DD Date
YY Year
Hh Hour
mm Minute
Note 1: If not defined, the default value is 0 for any numeric field and a space for any alphabetic field.
Note 2: If the optional item in the record format is blank, it shall be filled with the default value.
Note 3: If the alphabetic field is left-justified, it shall be padded with trailing spaces.
Note 4: If the numeric field is right-justified, it shall be padded with leading zeros.
Note 5: The default value of the amount field with sign bits is “D”. For example, if the transaction fee is x+n11,
the default value of the field shall be: “D” plus eleven “0”s. If the value of this field is “0”, this field shall also be
filled with “D” plus eleven “0”s.

2.7 Definitions of Special Data Items

This section indicates the definitions of special data items (cannot fit specific message fields) in the file format:
 Fee receivable: fee that Members should obtain.
 Fee payable: fee that Members should pay.
 Interchange fee: fee collected from or paid to Members by UPI.
 Transaction fee: filled with default value if this field does not exist in the online message.
 In the following file format, “I” indicates “incoming” (GSCS to Members), and “O” indicates “outgoing”
(Members to GSCS). If a field is only filled with “I” (or “O”), it means that the field has a valid value or valid
values in the “I” (or “O”) file; the file should be filled with a default value or default values, and the institution
identification code should be filled with spaces. For example, in the basic settlement information of the block
in 4.4.1.1, from Position 205, the receiving IIN should be entered. The direction tag field is “I”, so the field of the
incoming file should be filled with a valid institution identification code while space-filled in the outgoing file.
The definitions will not be explained any more when the fields are present in the file format.

UPI CONFIDENTIAL 20
 Part III: File Interface

3 Audit Trailer
3.1 Overview of Audit Trailer
Function of Audit Trailer
Audit trailers, containing details of all kinds of online transactions, stand-in authorization, and dispute transactions,
are generated by GSCS and classified by Member type and transaction type, truthfully reflecting the key information
of all transactions. Audit trailers are mainly used by Members to conduct internal check and reconciliation. In case
of any discrepancy between the accounting statistics of UPI and Members, they can implement automatic check and
reconciliation through audit trailers to identify the transaction record with disputes. The audit trailer of stand-in
authorization is used as a supplement to make a complete transaction log of the Issuer.
With respect to special transactions like transfer-in confirmation, audit trailers only record flows of transfer-in
confirmation for settlement and reconciliation. (only applicable to Members inside Mainland China)
Audit trailers cover transactions which are approved according to the definitions of the response codes. (For the
definitions of response codes, please refer to the Technical Specifications on Bankcard Interoperability - Part VI Annex.)

Naming Rules for Audit Trailer

Table 14 Naming Rules for Audit Trailers by Transaction Type

File Name Value of Position 1~18

Cross-border Valid value for Position 1~11:
Transaction IFDYYMMDD??, where ?? stands for the file batch number/ sequence number
with Foreign
Valid values for Position 12:
Exchange
I- Issuer
Rate
A- Acquirer
Information
Valid values for Position 13~18:
COM- General transaction a audit trailer
COMN- General transaction audit trailer (New)
COMB- General transaction audit trailer for secondary Member
COMNB- General transaction audit trailer (New) for secondary Member
ERR- Dispute transaction b audit trailer
ERRN- Dispute transaction audit trailer (New)
ERRB- Dispute transaction audit trailer for secondary Member
ERRNB- Dispute transaction audit trailer (New) for secondary Member
LER- Audit trailer for UICS IC card dispute transaction c
STI- Real-time stand-in authorization audit trailer i
STIFEE- Stand-in authorization service fee audit trailer ii
LOD- Audit trailer for UICS IC card E-cash application loading transaction
FEEDTL- UPI institution fee settlement file
FEEDTLB- UPI institution fee settlement file for secondary Member
Note i: STI is used as a supplement to make a complete transaction log of the Issuer, so it is
only delivered to the Issuer. Transactions processed by stand-in authorization include all
successful and failed transactions, all general transactions, and reversals and cancellations.
Since the audit trailer is delivered to the Issuer before the settlement, the stand-in
authorization service fee therein is zero.
Note ii: STIFEE is delivered to the Issuer after the daily settlement to convey the fee
information for each stand-in authorization transaction, and it is only delivered to the Issuer.
The audit trailer contains the transaction information based on which the stand-in

UPI CONFIDENTIAL 21
 Part III: File Interface

File Name Value of Position 1~18

authorization service fee is collected for Issuer’s reconciliation.
Exceptionally, FCP/FCPB iii for the Acquirer and the Issuer are the same, there will be no A/I
indicator.
Valid value for Position 1~11:
IFDYYMMDD??, where ?? stands for the file batch number/ sequence number
Valid values for Position 12~18:
FCP- Audit trailer for fee collection and fund disbursement transaction
FCPB- Audit trailer for fee collection and fund disbursement transaction for Secondary
Member
Note iii: Detailed audit trailer for fee settlement file to participants, including details of
interchange reimbursement fee (IRF) and service fee. The computational accuracy is changed
from the minimum accuracy of the currency to 1/10000 of the minimum accuracy of the
currency.
Note a: General transactions include balance inquiry, cash withdrawal, pre-authorization completion
(request), MO/TO pre-authorization completion (request), pre-authorization completion (advice), MO/TO pre-
authorization completion (advice), manual pre-authorization completion, manual MO/TO pre-authorization
completion, purchase, MO/TO purchase, MO/TO recurring, refund (online), MO/TO refund (online),
settlement advice, MO/TO settlement advice, manual refund with original transaction (manual MO/TO
refund), manual refund without original transaction (manual MO/TO refund), remittance (online remittance
only, excluding remittance verification transaction), manual remittance, primary credit, primary credit
confirmation, account funding, and account funding refund.
Note b: Dispute transactions include debit adjustment, chargeback, credit adjustment, and special credit
adjustment.
Note c: Dispute transactions for loading transaction and offline purchase include credit adjustment for offline
purchase, credit adjustment for cash loading, credit adjustment of designated account loading, exceptional
processing, and chargeback.
Note 1: Whether manual pre-authorization completion is recorded in the general transaction audit trailer
depends on whether the Member adopts the single-message mode or the dual-message mode. For single-
message Members, this transaction is recorded in the general transaction audit trailer; for dual-message
Members, this transaction is recorded in the dual-message settlement file.
Note 2: Whether refund (manual) and refund (credit voucher) are recorded in the general transaction audit
trailer or not depends on whether the Member adopts the single-message mode or the dual-message mode.
For single-message Members, refund (manual) and refund (credit voucher) transactions are recorded in the
general transaction audit trailer; for dual-message Members, the two transaction are recorded in the dual-
message settlement file. Field 25 is used to identify different transaction types of refunds.

Audit Trailer Processing

UPI CONFIDENTIAL 22
 Part III: File Interface

GSCS Member

Figure 13 Audit Trailer Processing

GSCS sends audit trailers to the Member.

Note: If the Member does not have the transaction audit trailer, a blank audit trailer will be sent. For the real-time
stand-in authorization audit trailer and the stand-in authorization fee audit trailer, GSCS will only send them to the
Member adopting stand-in authorization.

File List and Access Mode of Audit Trailer

Table 15 File List and Access Mode of Audit Trailer

File Name Description File Access Mode

(Y: Allowed;
N: Not Allowed)
Flow SFTP
Transmission
IFDYYMMDD??ICOM/ICOMB General transaction settlement detail of the Y Y
Issuer/the secondary Issuer
IFDYYMMDD??ICOMN/ICOMNB
IFDYYMMDD??ACOM General transaction settlement detail of the Y Y
Acquirer
IFDYYMMDD??ACOMN
IFDYYMMDD??IERR/IERRB Dispute settlement detail of the Issuer/the Y Y
secondary Issuer
IFDYYMMDD??IERRN/IERRNB
IFDYYMMDD??AERR Dispute settlement detail of the Acquirer Y Y
IFDYYMMDD??AERRN
IFDYYMMDD??ALER The Acquirer’s audit trailer file of the dispute Y Y
transaction for offline purchase based on UICS
Credit/Debit Standards
IFDYYMMDD??ILER The Issuer’s audit trailer file of the dispute Y Y
transaction for offline purchase based on UICS
Credit/Debit Standards
IFDYYMMDD??ALOD E-cash loading transaction detail for the Acquirer Y Y
IFDYYMMDD??ILOD E-cash loading transaction detail for the Issuer Y Y

UPI CONFIDENTIAL 23
 Part III: File Interface

File Name Description File Access Mode

(Y: Allowed;
N: Not Allowed)
Flow SFTP
Transmission
IFDYYMMDD??ISTI Real-time stand-in authorization detail for the Y Y
Issuer
IFDYYMMDD??ISTIFEE Stand-in authorization fee for the Issuer Y Y
IFDYYMMDD??ALFEE Brand service fee detail for the Acquirer (not Y Y
used)
IFDYYMMDD??ILFEE/ILFEEB Brand service fee detail for the Issuer/the Y Y
secondary Issuer (not used)
IFDYYMMDD??FCPB Fee collection/fund disbursement detail Y Y
(secondary Member), applicable for both the
Acquirer and the Issuer
IFDYYMMDD??FCP Fee collection/fund disbursement detail, Y Y
applicable for both the Acquirer and the Issuer
IFDYYMMDD01ACOMPOS General audit trailer file for the directly- Y Y
connected Acquirer
IFDYYMMDD??IFEEDTL/IFEEDTLB UPI institution fee settlement file of the Issuer/ Y Y
the secondary Issuer
IFDYYMMDD??AFEEDTL UPI institution fee settlement file of the Acquirer Y Y

3.2 Format of Audit Trailer

General Format of Audit Trailer
The formats of audit trailers can be divided into the basic format and the supplement for specific transaction types.
Online transaction audit trailers are transmitted to Members after generated by GSCS. The basic format is specified
as follows:
 Add a space between fields. (Except for UPI Institution Fee Settlement File)
 Add a “carriage return/linefeed (0X0D,0X0A)” after the last field of each row.
In addition to the general requirements, there are also some special formats as follows:
 For the files mentioned in this chapter, the default value of a field shall be filled with spaces if the field attribute
is “a”, “an” or “ans”. When the field attribute is “n”, the default value of the field shall be filled with all zeros.
When the field attribute is “x+n”, the “x” position shall be filled with “D” followed by the default value of all
zeros.
 For the files mentioned in this chapter, the leftmost digit indicates the number of decimal digits; the segment
from the 2nd to the 8th digit from the left indicates the value of the foreign exchange rate.
 For the files mentioned in this chapter, the end of the IIN field shall be filled with three spaces.
 Fields that cannot be completed should be filled with default values.
 General transaction audit trailers only record transactions successfully settled; reversals, cancellations or their
original transactions are not included.

UPI CONFIDENTIAL 24
 Part III: File Interface

Format of General Transaction Audit Trailer

This format is applicable to audit trailers of international transactions where the 13th to 16th bytes in the file name
are COM/COMB (general transaction audit trailer).
Table 16 Format of General Transaction Audit Trailer (with space between each field)

Acquirer’s General Transaction Issuer’s General Transaction

Seq. Definition Field Format Seq. Definition Field Format
1 Acquiring institution 32 ans11 1 Acquiring institution 32 ans11
identification code identification code
2 Forwarding institution 33 ans11 2 Forwarding institution 33 ans11
identification code identification code
3 System trace audit 11 n6 3 System trace audit 11 n6
number number
4 Transmission date and 7 n10 4 Transmission date and 7 n10
time time
5 Primary account number 2 n19 5 Primary account number 2 n19
(PAN) (PAN)
6 Amount, transaction 4 n12 6 Amount, transaction 4 n12
7 Message type MTI n4 7 Message type MTI n4
8 Processing code 3 n6 8 Processing code 3 n6
9 Merchant type 18 n4 9 Merchant type 18 n4
10 Card acceptor terminal 41 ans8 10 Card acceptor terminal 41 ans8
identification identification
11 Card acceptor 42 ans15 11 Card acceptor 42 ans15
identification code identification code
12 Card acceptor 43 ans40 12 Card acceptor 43 ans40
name/location name/location
13 Retrieval reference 37 an12 13 Retrieval reference 37 an12
number number
14 Point of service condition 25 n2 14 Point of service condition 25 n2
code code
15 Authorization 38 an6 15 Authorization 38 an6
identification response identification response
16 Receiving institution 100 ans11 16 Receiving institution 100 ans11
identification code identification code
17 System trace audit 90.2 n6 17 System trace audit 90.2 n6
number of original number of original
transaction transaction
18 Response code g 39 an2 18 Response code g 39 an2
19 Currency code, 49 an3 19 Currency code, 49 an3

UPI CONFIDENTIAL 25
 Part III: File Interface

Acquirer’s General Transaction Issuer’s General Transaction

Seq. Definition Field Format Seq. Definition Field Format
transaction transaction
20 Point of service entry 22 n3 20 Point of service entry 22 n3
mode mode
21 Currency code, settlement 50 n3 21 Currency code, settlement 50 n3
22 Amount, settlement 5 n12 22 Amount, settlement 5 n12
23 Conversion rate, 9 n8 23 Conversion rate, 9 n8
settlement settlement
24 Settlement date 15 n4 24 Settlement date 15 n4
25 Exchange date h 16 n4 25 Exchange date h 16 n4
26 Cardholder billing 51 an3
currency
27 Cardholder billing amount 6 n12
28 Cardholder billing 10 n8
exchange rate
26 Fee receivable (settlement n12 29 Fee receivable (settlement n12
currency) e currency) e
27 Fee payable (settlement n12 30 Fee payable (settlement n12
currency) e currency) e
28 Additional installment x+n11 31 Additional installment x+n11
payment commission fee f payment commission fee f
29 Service fee currency a an3 32 Service fee currency a an3
30 Service fee exchange rate n8 33 Service fee exchange rate n8
a a

31 Transaction fee b x+n11 34 Transaction fee b x+n11

32 RF billing currency c an3 35 RF billing currency c an3
33 Exchange rate from RF n8 36 Exchange rate from RF n8
billing currency to billing currency to
settlement currency c settlement currency c
34 Reserved for use d ans30 37 Reserved for use d ans30
Note a: This field indicates the interchange service fee which shall be paid to UPI by the Member or returned
to the Member by UPI (This fee is not implemented currently). The currency of this service fee shall be the
settlement currency of the Member.
Note b: For the ACOM/ACOMN file that records ATM cash withdrawal transactions, the value of Transaction
Fee shall be filled with that of Field 28 with the leftmost three numbers = 000. For the ACOM file that records
other transactions or for the ICOM file, the value of Transaction Fee shall be “D00000000000”.
Note c:
1) For IRF that is collected by percentage of transaction volume (including capping and floor limits, like POS

UPI CONFIDENTIAL 26
 Part III: File Interface

Acquirer’s General Transaction Issuer’s General Transaction

Seq. Definition Field Format Seq. Definition Field Format
transactions), the currency of the IRF should be the same as the settlement currency, so currency
conversion is not necessary. Therefore, the value of “IRF Billing Currency” should be the same as that of
“Settlement Currency”. The field of “Exchange Rate from IRF Billing Currency to Settlement Currency”
should be set at the fixed value of “30001000”;
2) For fixed fee per transaction (like ATM transactions), the currency of the IRF shall be the same as the “IRF
Billing Currency”. For example, the currency of the IRF for ATM is USD and the conversion rate for
USD/HKD is 7.753. Therefore, when a Member conducts settlement in the currency of HKD, the value of
“Exchange Rate from IRF Billing Currency to Settlement Currency” should be “30007753”.
3) When IRF is not applicable to the transaction recorded, the RF billing currency will be filled with “000”.
Note d: The format of the field reserved for use is “aaabcftgggiimmddhhmmssexxyyzss” followed by carriage
returns and line feeds:
1) “aaa” stands for the card sequence number in Field 23; if Field 23 is not submitted by the Acquirer in IC
Card Transaction, GSCS will automatically fill it with the default value of “000”. If Field 23 is not submitted
by the Acquirer in Non-IC Card Transaction, GSCS will automatically fill it with blank. Issuers shall be able
to proceed correctly.
2) “b” stands for the terminal read capability in Field 60.2.2;
3) “c” stands for the IC card condition code in Field 60.2.3;
4) “f” stands for the card level in Field 60.3.9;
5) “t” is the identifier of a stand-in authorization transaction: “Y” stands for a stand-in authorization
transaction; the space stands for a non-stand-in authorization transaction. It is only valid for the Issuer
and can be filled with a space by the Acquirer;
6) “ggg” stands for the country code. GSCS will fill it with the Acquirer’s country code;
7) “ii” stands for the pricing scheme code, indicating the pricing scheme of the transaction;
Pricing Description
Scheme
Code
00 Current international pricing scheme code (default value)
01 Pricing scheme code for transactions within and between Hong Kong and Macau
02 Pricing scheme code for domestic transactions in Singapore
03 Pricing scheme code for domestic transactions in Russia
04 Pricing scheme code for domestic transactions in Malaysia
05 Pricing scheme code for intra-regional transactions across the EEA countries, between the EEA
countries and United Kingdom, and between the EEA countries and Andorra
06 Pricing scheme code for domestic transactions in Kazakhstan
07 Pricing scheme code for domestic transactions in Mauritius
08 New international pricing scheme code. This new value currently applies to cross-border
transactions with UnionPay cards issued outside of Mainland China and used inside Mainland
China, and cross-border transactions with UnionPay cards issued and used within the 16 pilot

UPI CONFIDENTIAL 27
 Part III: File Interface

Acquirer’s General Transaction Issuer’s General Transaction

Seq. Definition Field Format Seq. Definition Field Format

countries /areas (Vietnam, Laos, Cambodia, Myanmar, Malaysia, Indonesia, Brunei,

Philippines, Hong Kong, Macau, Taiwan, Korea, Japan, Singapore, Thailand, and Mainland
China).
09 Pricing scheme code for Philippine domestic transactions
10 Pricing scheme code for Seychellois domestic transactions
11 Pricing scheme code for Kenyan domestic transactions
12 Pricing scheme code for Rwandan domestic transactions
13 Pricing scheme code for Ugandan domestic transactions
14 Pricing scheme code for Tanzanian domestic transactions
15 Pricing scheme code for Belgian domestic transactions
16 Pricing scheme code for British domestic transactions
17 Pricing scheme code for French domestic transactions
18 Pricing scheme code for Dutch domestic transactions
19 Pricing scheme code for Italian domestic transactions
20 Pricing scheme code for Spanish domestic transactions
21 Pricing scheme code for Burmese domestic transactions
22 Pricing scheme code for Thai domestic transactions
23 Pricing scheme code for Vietnamese domestic transactions
24 Reserved for use
25 Pricing scheme code for domestic transactions in Japan
26 Pricing scheme code for domestic transactions in Nepal
27 Pricing scheme code for domestic transactions in Portugal
28 Pricing scheme code for domestic transactions in Bangladesh
29 Pricing scheme code for domestic transactions in Sri Lanka
30 Pricing scheme code for domestic transactions in Australia (with dual-brand debit/pre-paid
cards)
31 Pricing scheme code for domestic transactions in Australia (with other cards)
32 Pricing scheme code for domestic transactions in the US Region (Issuers subject to the Durbin
Amendment and meeting fraud-prevention standards)
33 Pricing scheme code for domestic transactions in the US Region (Issuers subject to the Durbin
Amendment and not meeting fraud-prevention standards)
34 Pricing scheme code for domestic transactions in the US Region (reserved for future use)
35 Pricing scheme code for domestic transactions in Georgia

UPI CONFIDENTIAL 28
 Part III: File Interface

Acquirer’s General Transaction Issuer’s General Transaction

Seq. Definition Field Format Seq. Definition Field Format

36 Pricing scheme code for domestic transactions in Belarus

37 Pricing scheme code for domestic transactions in Ghana
38 Pricing scheme code for domestic transactions in Pakistan (with signature-based
debit/signature-based pre-paid cards)
39 Pricing scheme code for domestic transactions in Pakistan (with credit/pin-based debit/pin-
based pre-paid cards)
40 Pricing scheme code for cross-border transactions in the Russia and Commonwealth of
Independent States and Southeast Europe (CISSEE) intraregional jurisdictions. Countries in the
CISSEE jurisdiction include Albania, Armenia, Azerbaijan, Belarus, Bosnia and Herzegovina,
Georgia, Kazakhstan, Kosovo, Kyrgyzstan, Macedonia, Moldova, Montenegro, Republic of
Serbia, Tajikistan, Turkmenistan, Ukraine and Uzbekistan.
41 Pricing scheme code for domestic transactions in United Arab Emirates
42 Pricing scheme code for domestic transactions in Madagascar
43 Pricing scheme code for domestic transactions in Ukraine
44 Pricing scheme code for domestic transactions in Uzbekistan
45 Pricing scheme code for domestic transactions in Maldives
46 Pricing scheme code for domestic transactions in Switzerland
47 Pricing scheme code for domestic transactions in Cambodia
48 Pricing scheme code for domestic transactions in Andorra
.. Reserved for future use
ZZ Reserved for future use
8) “mmddhhmmss” stands for the original transaction time. If there is no original transaction, it shall be filled
with 10 spaces;
9) “e” is the transaction initiation method, the same as the definition of Field 60.3.5;
10) “xx” stands for the transaction channel. Please refer to the definition of Field 60.2.5 in the Technical
Specifications on Bankcard Interoperability - Part II Online Message. For example, for manual transactions,
this field is filled with ‘12’;
11) “yy” stands for the ECI symbol of CUPSecure Internet payment transaction. “ECI Symbol” is only used for e-
commerce transaction. For non-ecommerce transaction, this field is filled with zeros/"00". For the value
and meaning of this field, please refer to the definition of Field 60.2.8. When ECI is different in the request
and response of the online message, value in the response will be used.
12) “z” stands for transactions in Mainland China: For the Acquirer, “M” indicates that the Issuer is in Mainland
China, and “F” indicates that the Issuer is outside Mainland of China. For the Issuer, “M” indicates that the
Acquirer is in Mainland China, and “F” indicates that the Acquirer is outside Mainland China;
13) “ss” stands for installment payment terms. For example, “03” stands for 3 terms; “06” stands for 6 terms;
“12” stands for 12 terms. For transactions other than installment payment purchase and installment
payment fixed-amount authorization, “ss” will be filled with spaces.

UPI CONFIDENTIAL 29
 Part III: File Interface

Acquirer’s General Transaction Issuer’s General Transaction

Seq. Definition Field Format Seq. Definition Field Format
Note e: The sum of all credit-entry fees (which may include interchange reimbursement fee and/or service fee
for some transactions, etc.) for the member shall be put in the field of “Fee Receivable”. The sum of all debit-
entry fees (which may include interchange reimbursement fee and/or service fee, etc.) for the member shall be
put in the field of “Fee Payable”.
Note f: The first digit is “C” for crediting and “D” for debiting the Cardholder’s account. The 2nd ~11th digits
indicate the additional installment payment commission fee which shall be paid to Issuer by the Acquirer side.
The currency of this commission fee shall be the settlement currency of the Member. If it is not installment
payment, the value should be D00000000000.
Note g: For advice transaction, GSCS uniformly fills the field with “00” and conducts settlement no matter
whether it is a reject response or there is no response. Members shall conduct settlement according to the
data provided by GSCS.
Note h: This field mandatorily exists despite its possible absence in online message, and represents the
effective date of the currency conversion rate applied in this record.

Format of General Transaction Audit Trailer (New)

This format is applicable to the audit trailer for international transactions where the value of the segment from the
13th to the 16th position in the file name is COMN (general transaction). The COMN record format is the COM record
format followed by an additional trailer. A space should be inserted between the original COM record part and the
additional trailer part.
Effective from September 7, 2016, when the Acquirer subscribes to the IFDYYMMDD??ACOMN file, it will contain
both directly-connected POS transactions and indirectly-connected ATM/Ecommerce/POS transaction under its IIN.
Table 17 Format of General Transaction Audit Trailer (New)- Additional Part for Acquirer

General Transaction Audit Trailer Additional Part for Acquirer

Seq. Definition Field Format Description
1 Order number ans40 It is only applicable to E-commerce transactions currently and
shall be filled with spaces when the transaction is submitted
through other channels.
2 Product mode an4 It is only applicable to E-Commerce Transactions currently and
should be filled with spaces when the transaction is submitted
through other channels.
Valid value:
9000- UPOP
3 Total fee a1 Valid values:
debit/credit C- Credit
identification D- Debit
If “total fee amount” is zero, either C or D works fine.
4 Total fee n16 It stands for receivable fee (Credit) or payable fee (Debit). High
amount accuracy fee, which is the sum of interchange reimbursement
fee and service fee.
The value of this field is an integer, padded with leading zeros.

UPI CONFIDENTIAL 30
 Part III: File Interface

General Transaction Audit Trailer Additional Part for Acquirer

Seq. Definition Field Format Description
The unit is 1/10000 of the minor unit of currency.
5 Industry ans60 Filled with industry information:
information
Sub- Definition Description
seq.
1 Industry ans2,
transaction
Valid values:
code
FT- Flight-related transactions
2 Industry ans2, reserved and filled with
information spaces by default
type
3 Industry ans56,
information
FT industry information consists of
an ans20 format airline ticket
number + a n8 format departure
date(YYYYMMDD).
Note: All the above formats are
left-justified with trailing spaces.

6 Card product 60.3.10 ans2 The same as the value of Field 60.3.10
7 Account 60.3.8 ans2 The same as the value of Field 60.3.8
attribute
8 Reserved ans19 Filled with spaces
9 UnionPay ans1 This field indicates whether the card is a UnionPay Standard
Standard/ Non- Card or Non-standard Card.
standard Card
Valid Values:
indicator
0- UnionPay Non-Standard Card
1- UnionPay Standard Card
10 B2B business 104(BB) n2 This field is filled with spaces by default.
type Tag01
For cross-border B2B payment and service, this field is filled
with the corresponding business type. For valid values, please
see the message field definition of Field 104 Usage BB Tag 01 in
the Technical Specifications on Bankcard Interoperability - Part
II Online Message.
11 B2B payment 104(BB) n1 This field is filled with spaces by default.
medium Tag02
For cross-border B2B payment and service, this field is filled
with the corresponding payment medium. For valid values,
please see the message field definition of Field 104 Usage BB
Tag 02 in the Technical Specifications on Bankcard
Interoperability - Part II Online Message.

UPI CONFIDENTIAL 31
 Part III: File Interface

General Transaction Audit Trailer Additional Part for Acquirer

Seq. Definition Field Format Description
12 Wallet ID ans8 This field is filled with spaces by default.
For SDWO transactions, this field is filled with the ID of the
Staged Digital Wallet Operator.
For SRC transactions, this field is filled with the DCF ID.
13 PF ID an8 This field is filled with spaces by default.
For PF transactions, this field is filled with the PF ID.
14 Special pricing an2 This field is filled with spaces by default.
indicator
For white-listed Members or Merchants offered special pricing,
this field is filled with 01.
15 Transaction an3 This field is filled with spaces by default.
scenario
For Innovative Payment transactions, this field is filled with the
indicator
value of Field 125 Usage IP Tag 01.

16 Reserved n2 Filled with spaces by default. Reserved for UPI Pilot Services.
17 Sub-merchant 48(AS) ans30 This field is filled with spaces by default.
ID TagPM
For transactions containing sub-merchant information, this
Seq.3
field is filled in with the sub-merchant ID. Left-justified with
trailing spaces.
18 Reserved ans81 Filled with spaces

Table 18 Format of General Transaction Audit Trailer (New)- Additional Part for Issuer

General Transaction Audit Trailer Additional Part for Issuer

Seq. Definition Field Format Description
1 Reserved ans40 Filled with spaces
2 Reserved an4 Filled with spaces
3 Reserved a1 Filled with spaces
4 Reserved n16 Filled with spaces
5 Reserved ans60 Filled with spaces
6 Card product 60.3.10 ans2 The same as the value of Field 60.3.10
7 Account attribute 60.3.8 ans2 The same as the value of Field 60.3.8
8 Token 63(TK) n19 Left-justified with trailing spaces.
Tag02
For Payment Token transaction, filled with the same value
of Field 63 Usage TK Tag 02.
For PAN-based transaction, filled with spaces.
9 UnionPay Standard/ ans1 This field indicates whether the card is a UnionPay

UPI CONFIDENTIAL 32
 Part III: File Interface

General Transaction Audit Trailer Additional Part for Issuer

Seq. Definition Field Format Description
Non-standard Card Standard Card or Non-standard Card.
indicator
Valid Values:
0- UnionPay Non-Standard Card
1- UnionPay Standard Card
10 B2B business type 104(BB) n2 This field is filled with spaces by default.
Tag01
For cross-border B2B payment and service, this field is
filled with the corresponding business type. For valid
values, please see the message field definition of Field
104 Usage BB Tag 01.
11 B2B payment 104(BB) n1 This field is filled with spaces by default.
medium Tag02
For cross-border B2B payment and service, this field is
filled with the corresponding payment medium. For valid
values, please see the message field definition of Field
104 Usage BB Tag 02.
12 Wallet ID ans8 This field is filled with spaces by default.
For SDWO transactions, this field is filled with the ID of
the Staged Digital Wallet Operator.
For SRC transactions, this field is filled with the DCF ID.
13 Reserved an8 Filled with spaces
14 Special pricing an2 This field is filled with spaces by default.
indicator
For white-listed Members or Merchants offered special
pricing, this field is filled with 01.
15 Transaction scenario an3 This field is filled with spaces by default.
indicator
For Innovative Payment transactions, this field is filled
with the value of Field 125 Usage IP Tag 01.
16 Reserved n2 Filled with spaces by default. Reserved for UPI Pilot
Services.
17 Reserved ans30 Filled with spaces
18 Reserved ans81 Filled with spaces
Note: For consistency of the audit trailer format for the Issuer and the Acquirer, the fields only included in the
Acquirer audit trailer files will be filled with spaces in the Issuer audit trailer files.

Format of General Transaction Audit Trailer for Secondary Member

 File Format
The file header record, the file body record, and the file tail record are separated by carriage returns/linefeeds (0X0D,
0X0A). At the end of the file tail, a carriage return/linefeed (0X0D, 0X0A) must be added as well.
Table 19 Format of General Transaction Audit Trailer for Secondary Member

UPI CONFIDENTIAL 33
 Part III: File Interface

File Header Record Format

Seq. Position Format Definition Description
1 1 ans62 Reserved field 1 Filled with spaces
2 63 ans11 IIN Left-justified with trailing spaces if the length is less
than 11.
3 74 n8 Settlement date Format: YYYYMMDD
4 82 ans300 Reserved field 2 Filled with spaces
File Body Record Format (Refer to Section 3.2.3 Format of General Transaction Audit Trailer)
File Trailer Record Format
Seq. Position Format Definition Description
1 1 ans62 Reserved field 1 Filled with all “Z”s
2 63 ans11 IIN Left-justified with trailing spaces
3 74 n8 Settlement date Format: YYYYMMDD
4 82 n6 Total number of records Total number of records (including the header and
the trailer)
5 88 n18 PAN HASH check value ∑ the absolute value of [CB PAN (digit 1~digit 10) +
(digit 11~digit 19)]
12 106 n18 Settlement amount HASH ∑ [the absolute value of (Amount, settlement) + the
check value absolute value of (Fee)]
6 124 ans258 Reserved field 2 Filled with spaces
 HASH Check Value Calculation for PAN
Encoding method for PAN:
Table 20 PAN Encoding

Original Value 9 8 7 6 5 4 3 2 1 0
Encoded Value 5 6 0 8 4 9 2 7 1 3

Table 21 Examples of PAN Encoding

If PAN is “1234567890123456”. Let’s divide it into two parts according to the calculation formula. One part is the
first 10 digits, and the other part is the last 6 digits. Both parts are right aligned and added up:
1234567890
+ 123456
-----------------
Absolute value = 1234691346
Encoded value = 1729851298
If PAN = 12345678901234567,
1234567890

UPI CONFIDENTIAL 34
 Part III: File Interface

+ 1234567
------------------------
Absolute value = 1235802457
Encoded value = 1724637940
If PAN = 1234567890123456789,
1234567890
+ 123456789
-------------------------
Absolute value = 1358024679
Encoded value = 1246379805
The final check value of the PAN is the sum of the encoded values of the PAN for all records, so is the check value of
the settlement amount.
For a file required to check the PAN and the settlement amount, if there is no file body, the check value fields for PAN
and settlement amount should all be set to 0.
Format of Dispute Transaction Audit Trailer
This format is applicable to dispute transaction audit trailers with foreign exchange rate information, in which the
segment from the 13th to the 16th position in the file name is valued as ERR/ERRB (dispute transaction audit trailer).
Dispute transaction audit trailers record transactions includes debit adjustment, chargeback, credit adjustment, and
special credit adjustment.
Table 22 Format of Dispute Transaction Audit Trailer

Acquirer’s Dispute Transaction Issuer’s Dispute Transaction

Seq. Definition Field Format Seq. Definition Field Format
1 Acquiring institution 32 ans11 1 Acquiring institution 32 ans11
identification code identification code
2 Forwarding institution 33 ans11 2 Forwarding institution 33 ans11
identification code identification code
3 System trace audit 11 n6 3 System trace audit 11 n6
number number
4 Transmission date and 7 n10 4 Transmission date and 7 n10
time time
5 Primary account number 2 n19 5 Primary account number 2 n19
(PAN) (PAN)
6 Amount, transaction 4 n12 6 Amount, transaction 4 n12
7 Message type MTI n4 7 Message type MTI n4
8 Processing code 3 n6 8 Processing code 3 n6
9 Merchant type 18 n4 9 Merchant type 18 n4
10 Card acceptor terminal 41 ans8 10 Card acceptor terminal 41 ans8

UPI CONFIDENTIAL 35
 Part III: File Interface

Acquirer’s Dispute Transaction Issuer’s Dispute Transaction

Seq. Definition Field Format Seq. Definition Field Format
identification identification
11 Card acceptor 42 ans15 11 Card acceptor 42 ans15
identification code identification code
12 Card acceptor 43 ans40 12 Card acceptor 43 ans40
name/location name/location
13 Retrieval reference 37 an12 13 Retrieval reference 37 an12
number number
14 Point of service condition 25 n2 14 Point of service condition 25 n2
code code
15 Authorization 38 an6 15 Authorization 38 an6
identification response identification response
16 Receiving institution 100 ans11 16 Receiving institution 100 ans11
identification code identification code
17 System trace audit 90.2 n6 17 System trace audit 90.2 n6
number of original number of original
transaction a transaction a
18 Response code 39 an2 18 Response code 39 an2
19 Currency code, 49 an3 19 Currency code, 49 an3
transaction transaction
20 Point of service entry 22 n3 20 Point of service entry 22 n3
mode mode
21 Currency code, 50 n3 21 Currency code, 50 n3
settlement settlement
22 Amount, settlement 5 n12 22 Amount, settlement 5 n12
23 Conversion rate, 9 n8 23 Conversion rate, 9 n8
settlement settlement
24 Settlement date 15 n4 24 Settlement date 15 n4
g g
25 Exchange date 16 n4 25 Exchange date 16 n4
26 Cardholder billing 51 an3
currency
27 Cardholder billing 6 n12
amount
28 Cardholder billing 10 n8
exchange rate
26 Fee receivable n12 29 Fee receivable n12
(settlement currency) f (settlement currency) f
27 Fee payable (settlement n12 30 Fee payable (settlement n12

UPI CONFIDENTIAL 36
 Part III: File Interface

Acquirer’s Dispute Transaction Issuer’s Dispute Transaction

Seq. Definition Field Format Seq. Definition Field Format
currency) f currency) f
28 Additional installment x+n11 31 Additional installment x+n11
payment commission fee payment commission fee
b b

29 Transaction fee c x+n11 32 Transaction fee c x+n11

30 Original transaction date 90.3 n10 33 Original transaction date 90.3 n10
and time a and time a
31 Original transaction 3 n6 34 Original transaction 3 n6
processing code e processing code e
32 Reserved for use d ans30 35 Reserved for use d ans30
Note a: The original transaction refers to the last transaction prior to this dispute transaction; it is not
necessarily the initial original transaction triggering the dispute transaction. For example, the original
transaction of a chargeback triggered by a purchase transaction may be the debit adjustment instead of the
purchase. Therefore, the system trace audit number (Field 90.2 of the dispute transaction) and the transaction
date/time (Field 90.3 of the dispute transaction) of the original transaction cannot be used to match this
dispute transaction and its initial authorization transaction. Instead, the Acquirer shall use the related system
trace audit number, the related transmission date and time, and the related transaction processing code of the
correlated transaction in the AERRN.
Note b: The first digit is “C” for crediting and “D” for debiting the Cardholder’s account. The 2nd~11th digits
indicate the additional installment payment commission fee which shall be paid to Issuer by the Acquirer side.
The currency of this commission fee shall be the settlement currency of the Member. If it is not installment
payment, the value should be D00000000000.。
Note c: This fee is yet to be implemented, and the value should be D00000000000.
Note d: The format of the field reserved for use is “AAABCGGGFHIIJ□□□□□□□□□□DEEEESS” followed by
carriage returns and line feeds. The format of the field reserved for the Issuer is
“ZAAABCGGGFHIIJ□□□□□□□□□DEEEESS” followed by carriage returns and line feeds.
In the above format,
1) “Z” is the identifier of the transaction domestically acquired or internationally acquired; Its value being
“F” means that the transaction is cross-border acquired; while its value being “M” means the transaction
is domestically acquired.
2) “AAA” stands for the card sequence number of Field 23; if the Acquirer does not submit Field 23 in IC
Card Transaction, GSCS will fill Field 23 with “000” in the settlement. If Field 23 is not submitted by the
Acquirer in Non-IC Card Transaction, GSCS will automatically fill it with blank. The Issuer shall be able to
proceed properly.
3) “B” stands for the terminal read capability in Field 60.2.2;
4) “C” stands for the IC card condition code in Field 60.2.3;
5) “GGG” stands for the country code. GSCS will fill it with the Acquirer’s country code;
6) “F” stands for the transaction initiation mode in Field 60.3.5;
7) “H” stands for the card level in Field 60.3.9;

UPI CONFIDENTIAL 37
 Part III: File Interface

Acquirer’s Dispute Transaction Issuer’s Dispute Transaction

Seq. Definition Field Format Seq. Definition Field Format
8) “II” stands for the pricing scheme code, indicating the pricing scheme of the transaction:
Pricing Description
Scheme
Code
00 Current international pricing scheme code (default value)
01 Pricing scheme code for transactions within and between Hong Kong and Macau
02 Pricing scheme code for domestic transactions in Singapore
03 Pricing scheme code for domestic transactions in Russia
04 Pricing scheme code for domestic transactions in Malaysia
05 Pricing scheme code for intra-regional transactions across the EEA countries, between the EEA
countries and United Kingdom, and between the EEA countries and Andorra
06 Pricing scheme code for domestic transactions in Kazakhstan
07 Pricing scheme code for domestic transactions in Mauritius
08 New international pricing scheme code. This new value currently applies to cross-border
transactions with UnionPay cards issued outside of Mainland China and used inside Mainland
China, and cross-border transactions with UnionPay cards issued and used within the 16 pilot
countries /areas (Vietnam, Laos, Cambodia, Myanmar, Malaysia, Indonesia, Brunei,
Philippines, Hong Kong, Macau, Taiwan, Korea, Japan, Singapore, Thailand, and Mainland
China).
09 Pricing scheme code for Philippine domestic transactions
10 Pricing scheme code for Seychellois domestic transactions
11 Pricing scheme code for Kenyan domestic transactions
12 Pricing scheme code for Rwandan domestic transactions
13 Pricing scheme code for Ugandan domestic transactions
14 Pricing scheme code for Tanzanian domestic transactions
15 Pricing scheme code for Belgian domestic transactions
16 Pricing scheme code for British domestic transactions
17 Pricing scheme code for French domestic transactions
18 Pricing scheme code for Dutch domestic transactions
19 Pricing scheme code for Italian domestic transactions
20 Pricing scheme code for Spanish domestic transactions
21 Pricing scheme code for Burmese domestic transactions
22 Pricing scheme code for Thai domestic transactions
23 Pricing scheme code for Vietnamese domestic transactions

UPI CONFIDENTIAL 38
 Part III: File Interface

Acquirer’s Dispute Transaction Issuer’s Dispute Transaction

Seq. Definition Field Format Seq. Definition Field Format

24 Reserved for use

25 Pricing scheme code for domestic transactions in Japan
26 Pricing scheme code for domestic transactions in Nepal
27 Pricing scheme code for domestic transactions in Portugal
28 Pricing scheme code for domestic transactions in Bangladesh
29 Pricing scheme code for domestic transactions in Sri Lanka
30 Pricing scheme code for domestic transactions in Australia (with dual-brand debit/pre-paid
cards)
31 Pricing scheme code for domestic transactions in Australia (with other cards)
32 Pricing scheme code for domestic transactions in the US Region (Issuers subject to the Durbin
Amendment and meeting fraud-prevention standards)
33 Pricing scheme code for domestic transactions in the US Region (Issuers subject to the Durbin
Amendment and not meeting fraud-prevention standards)
34 Pricing scheme code for domestic transactions in the US Region (reserved for future use)
35 Pricing scheme code for domestic transactions in Georgia
36 Pricing scheme code for domestic transactions in Belarus
37 Pricing scheme code for domestic transactions in Ghana
38 Pricing scheme code for domestic transactions in Pakistan (with signature-based
debit/signature-based pre-paid cards)
39 Pricing scheme code for domestic transactions in Pakistan (with credit/pin-based debit/pin-
based pre-paid cards)
40 Pricing scheme code for cross-border transactions in the Russia and Commonwealth of
Independent States and Southeast Europe (CISSEE) intraregional jurisdictions. Countries in the
CISSEE jurisdiction include Albania, Armenia, Azerbaijan, Belarus, Bosnia and Herzegovina,
Georgia, Kazakhstan, Kosovo, Kyrgyzstan, Macedonia, Moldova, Montenegro, Republic of
Serbia, Tajikistan, Turkmenistan, Ukraine and Uzbekistan.
41 Pricing scheme code for domestic transactions in United Arab Emirates
42 Pricing scheme code for domestic transactions in Madagascar
43 Pricing scheme code for domestic transactions in Ukraine
44 Pricing scheme code for domestic transactions in Uzbekistan
45 Pricing scheme code for domestic transactions in Maldives
46 Pricing scheme code for domestic transactions in Switzerland
47 Pricing scheme code for domestic transactions in Cambodia
48 Pricing scheme code for domestic transactions in Andorra

UPI CONFIDENTIAL 39
 Part III: File Interface

Acquirer’s Dispute Transaction Issuer’s Dispute Transaction

Seq. Definition Field Format Seq. Definition Field Format

.. Reserved for future use

ZZ Reserved for future use
9) “J” stands for the debit/credit code. Its value being “C” represents credit (Member will receive money based
on this dispute transaction record); while its value being “D” represents debit (Member will pay based on
this dispute transaction record);
10) “D” is the identifier of the dispute resolution initiator who initiates the dispute resolution transaction. Its
value being a space means the initiator is not defined; its value being “1” means the dispute resolution
transaction is initiated by UPI; while its value being “2” means the dispute resolution transaction is initiated
by the Member;
11) “EEEE” stands for the dispute resolution reason code;
12) “SS” stands for installment payment terms. For example, “03” stands for 3 terms; “06” stands for 6 terms;
“12” stands for 12 terms. For transactions other than installment payment purchase and installment
payment fixed-amount authorization, “SS” will be filled with spaces.
Note e: This field shall be filled with spaces by UPI when the original transaction is without the processing
code. For example, when the original transaction is a debit adjustment, the field of "Original transaction
processing code" in the dispute transaction record shall be filled with spaces by UPI.
Note f: The sum of all credit-entry fees (which may include interchange reimbursement fee and/or service fee
for some transactions, etc.) for the member shall be put in the field of “Fee Receivable”. Separately, the sum of
all debit-entry fees (which may include interchange reimbursement fee and/or service fee, etc.) for the
member shall be put in the field of “Fee Payable”.
Note g: This field mandatorily exists despite its possible absence in online message, and represents the
effective date of the currency conversion rate applied in this record.

Format of Dispute Transaction Audit Trailer (New)

This format is applicable to dispute transaction audit trailers with foreign exchange rate information, in which the
segment from the 13th to the 16th digits in the file name is valued as ERRN (dispute transaction audit trailer). The
ERRN record format is the original ERR record followed by an additional trailer, and a space should be inserted
between the original ERR record part and the additional trailer part.
Table 23 Format of Dispute Transaction Audit Trailer (New)- Additional Part for Acquirer

Dispute Transaction Audit Trailer Additional Part for Acquirer

Seq. Definition Field Format Description
1 Last transaction ans40 The order number of the last transaction, only filled when the
order number value of Field 60.2.5 is “07” for E-commerce transaction.
2 Last transaction 60.2.5 an2 The terminal type of the last transaction
terminal type
3 Total fee a1 Valid values:
debit/credit C- Credit
identification D- Debit
If “total fee amount” is zero, either C or D works fine.

UPI CONFIDENTIAL 40
 Part III: File Interface

Dispute Transaction Audit Trailer Additional Part for Acquirer

Seq. Definition Field Format Description
4 Total fee amount n16 It stands for receivable fee (Credit) or payable fee (Debit).
High accuracy fee, which is the sum of interchange
reimbursement fee and service fee.
The value of this field is an integer, padded with leading zeros.
The unit is 1/10000 of the minor unit of currency.
5 Card product 60.3.10 ans2 The same as the value of Field 60.3.10
6 Account attribute 60.3.8 ans2 The same as the value of Field 60.3.8
7 UnionPay ans1 This field indicates whether the card is a UnionPay Standard
Standard/ Non- Card or Non-standard Card.
standard Card
Valid Values:
indicator
0- UnionPay Non-Standard Card
1- UnionPay Standard Card
8 B2B business 104(BB) n2 This field is filled with spaces by default.
type Tag01
For cross-border B2B payment and service, this field is filled
with the corresponding business type. For valid values, please
see the message field definition of Field 104 Usage BB Tag 01.
9 B2B payment 104(BB) n1 This field is filled with spaces by default.
medium Tag02
For cross-border B2B payment and service, this field is filled
with the corresponding payment medium. For valid values,
please see the message field definition of Field 104 Usage BB
Tag 02.
10 Related system 11 n6 This field is filled with the value of Field 11 system trace audit
trace audit number of the initial transaction for the dispute resolution.
number
For example, if the initial authorization transaction for the
dispute resolution is initiated by a dual-message Acquirer and
forwarded to a single-message Issuer by UPI, this field is filled
with the value of Field 11 system trace audit number of the
authorization transaction. Dual-message Acquirers can use
this field along with the following related transmission date
and time and the related transaction processing code fields to
match the original authorization transaction.
11 Related 7 n10 This field is filled with the value of Field 7 Transmission Date
transaction date and Time of the initial transaction for the dispute resolution.
and time
12 Related 3 n6 This field is filled with the value of Field 3 Transaction
transaction Processing Code of the initial transaction for the dispute
processing code resolution.
13 Wallet ID ans8 This field is filled with spaces by default.
For SDWO transactions, this field is filled with the ID of the
Staged Digital Wallet Operator.

UPI CONFIDENTIAL 41
 Part III: File Interface

Dispute Transaction Audit Trailer Additional Part for Acquirer

Seq. Definition Field Format Description
For SRC transactions, this field is filled with the DCF ID.
14 PF ID an8 This field is filled with spaces by default.
For PF transactions, this field is filled with the PF ID.
15 Special pricing an2 This field is filled with spaces by default.
indicator
For white-listed Members or Merchants offered special
pricing, this field is filled with 01.
16 Transaction an3 This field is filled with spaces by default.
scenario
For Innovative Payment transactions, this field is filled with
indicator
the value of Field 125 Usage IP Tag 01.

17 Reserved ans173 Filled with spaces

Table 24 Format of Dispute Transaction Audit Trailer (New)- Additional Part for Issuer

General Transaction Audit Trailer Additional Part for Issuer

Seq. Definition Field Format Description
1 Reserved ans40 Filled with spaces
2 Reserved an2 Filled with spaces
3 Reserved a1 Filled with spaces
4 Reserved n16 Filled with spaces
5 Card product 60.3.10 ans2 The same as the value of Field 60.3.10
6 Account attribute 60.3.8 ans2 The same as the value of Field 60.3.8
7 UnionPay ans1 This field indicates whether the card is a UnionPay Standard
Standard/ Non- Card or Non-standard Card.
standard Card
Valid Values:
indicator
0- UnionPay Non-Standard Card
1- UnionPay Standard Card
8 B2B business type 104(BB) n2 This field is filled with spaces by default.
Tag01
For cross-border B2B payment and service, this field is filled
with the corresponding business type. For valid values,
please see the message field definition of Field 104 Usage BB
Tag 01.
9 B2B payment 104(BB) n1 This field is filled with spaces by default.
medium Tag02
For cross-border B2B payment and service, this field is filled
with the corresponding payment medium. For valid values,
please see the message field definition of Field 104 Usage BB
Tag 02.

UPI CONFIDENTIAL 42
 Part III: File Interface

General Transaction Audit Trailer Additional Part for Issuer

Seq. Definition Field Format Description
10 Related system 11 n6 This field is filled with the value of Field 11 system trace
trace audit audit number of the initial transaction for the dispute
number resolution.
For example, if the initial authorization transaction for the
dispute resolution is initiated by a dual-message Acquirer
and forwarded to a single-message Issuer by UPI, this field is
filled with the value of Field 11 system trace audit number of
the authorization transaction.
11 Related 7 n10 This field is filled with the value of Field 7 Transmission Date
transaction date and Time of the initial transaction for the dispute resolution.
and time
12 Related 3 n6 This field is filled with the value of Field 3 Transaction
transaction Processing Code of the initial transaction for the dispute
processing code resolution.
13 Wallet ID ans8 This field is filled with spaces by default.
For SDWO transactions, this field is filled with the ID of the
Staged Digital Wallet Operator.
For SRC transactions, this field is filled with the DCF ID.
14 Reserved an8 Filled with spaces
15 Special Pricing an2 This field is filled with spaces by default.
Indicator
For white-listed Members or Merchants offered special
pricing, this field is filled with 01.
16 Transaction an3 This field is filled with spaces by default.
Scenario Indicator
For Innovative Payment transactions, this field is filled with
the value of Field 125 Usage IP Tag 01.
17 Reserved ans173 Filled with spaces

Format of Dispute Transaction Audit Trailer for Secondary Member

The file header record, the file body record, and the file trailer record are separated by carriage return/linefeed (0X0D,
0X0A). At the end of the file trailer, a carriage return/linefeed (0X0D, 0X0A) must be added as well.
Table 25 Format of Dispute Transaction Audit Trailer for Secondary Member

File Header Record Format

Seq. Position Format Definition Description
1 1 ans62 Reserved field 1 Filled with spaces
2 63 ans11 IIN Left-justified with trailing spaces if the length is less than
11.
3 74 n8 Settlement date Format: YYYYMMDD

UPI CONFIDENTIAL 43
 Part III: File Interface

4 82 ans292 Reserved field 2 Filled with spaces

File Body Record Format (Refer to Section 3.2.5 Format of Dispute Transaction Audit Trailer)
File Trailer Record Format
Seq. Position Format Definition Description
1 1 ans62 Reserved field 1 Filled with all “Z”s
2 63 ans11 IIN Left-justified with trailing spaces
3 74 n8 Settlement date Format: YYYYMMDD
4 82 n6 Total number of Total number of records (including the header and the
records trailer)
5 88 n18 PAN HASH check value ∑ the absolute value of [CB PAN (digit 1~digit 10) + (digit
11~digit 19)], refer to Section 3.2.4 for details.
12 106 n18 Settlement amount ∑ [the absolute value of (Amount, settlement) + the
HASH check value absolute value of (Fee)], refer to Section 3.2.4 for details.
6 124 ans250 Reserved field 2 Filled with spaces

Format of UICS IC Card E-cash Application Loading Transaction Audit Trailer

The format is applicable to the transaction audit trailer with the segment from the 13 th to the 15th position of its file
name valued as “LOD”. Transaction types include designated account loading and cash loading.
The format is the same as that for the general transaction audit trailer specified in Section 3.2.2.

Format of UICS IC Card Dispute Transaction Audit Trailer

This format is applicable to the dispute transaction audit trailer where the value of the segment from the 13 th to the
15th digits in file name is “LER”.
Transaction types in this audit trailer include designated account loading, cash loading and offline purchase of E-cash
application, and offline purchase of debit/credit application.
For offline purchase transaction, credit adjustment, exceptional processing and chargeback can be performed. The
processing method for these disputes is the same as that for magnetic stripe transactions.
Credit adjustment and exceptional processing can be processed based on designated account loading and cash
loading transaction.

UPI CONFIDENTIAL 44
 Part III: File Interface

Table 26 Audit Trailer Format of Dispute Transaction for IC Card Based on UICS Debit/Credit Standards

Acquirer’s Dispute Transaction Issuer’s Dispute Transaction Explanation on Field

Seq. Definition Field Format Seq. Definition Field Format
1 Acquiring 32 ans11 1 Acquiring 32 ans11 It is the IIN of the Acquirer in the original
institution institution transaction. For exceptional processing of dispute
identification code identification code resolution, the field should be filled with the IIN of
the secondary Member to facilitate the secondary
settlement.
2 Forwarding 33 ans11 2 Forwarding 33 ans11 It is the IIN of the forwarding institution in the
institution institution original transaction. For exceptional processing of
identification code identification code dispute resolution, the field should be filled with the
IIN of the Forwarding institution which initiates the
transaction.
3 System trace audit 11 n6 3 System trace audit 11 n6 It is the trace number of the dispute. If there is no
number number original transaction, the value will be assigned by the
CDRS, which is unique within one day. And the value
will remain unchanged during transaction cycle.
4 Transmission date 7 n10 4 Transmission date 7 n10 It is the date/time when the Member initiates the
and time and time dispute. For retrieval, it is the retrieval fulfillment
date/time, and the format is “MMDDHHMMSS”. For
retrieval fulfillment, since the time is only measured
in days, the “HHMMSS” shall be filled with 6 zeros.
5 Primary account 2 n19 5 Primary account 2 n19 It is the PAN of the original transaction.
number (PAN) number (PAN)
6 Amount, 4 n12 6 Amount, 4 n12 For retrieval, the field is filled with the disputed
transaction transaction amount; for retrieval fulfillment, the field is filled
with the service fee; if there is no fee, the field will
be filled with “0”.
7 Message type MTI n4 7 Message type MTI n4 It is the message type for dispute. For retrieval
fulfillment, and manual transactions, the field is filled
with the default value.

UPI CONFIDENTIAL 45
 Part III: File Interface

Acquirer’s Dispute Transaction Issuer’s Dispute Transaction Explanation on Field

Seq. Definition Field Format Seq. Definition Field Format
8 Processing code 3 n6 8 Processing code 3 n6 It is the processing code for dispute. For retrieval
fulfillment and manual transactions, the field is filled
with the default value.
9 Merchant type 18 n4 9 Merchant type 18 n4 It is the value of the original transaction. For
exceptional processing for dispute and retrieval
fulfillment, the field is filled with the default value.
10 Card acceptor 41 ans8 10 Card acceptor 41 ans8 It is the value of the original transaction. For
terminal terminal exceptional processing for dispute and retrieval
identification identification fulfillment, the field is filled with the default value.
11 Card acceptor 42 ans15 11 Card acceptor 42 ans15 It is the value of the original transaction. For
identification code identification code exceptional processing for dispute and retrieval
fulfillment, the field is filled with the default value.
12 Card acceptor 43 ans40 12 Card acceptor 43 ans40 It is the name and address of the original transaction.
name/location name/location For exceptional processing for dispute, if the original
transaction is available, the field will be filled with
the value of the original transaction; otherwise, the
field will be filled with the default value.
13 Retrieval reference 37 an12 13 Retrieval reference 37 an12 It is the retrieval reference number of the original
number number transaction. For retrieval fulfillment and exceptional
dispute, the field should be filled with the default
value
14 Point of service 25 n2 14 Point of service 25 n2 It is the point of service condition of the dispute.
condition code condition code
15 Authorization 38 an6 15 Authorization 38 an6 It is the authorization identification response of the
identification identification original transaction. For exceptional processing for
response response dispute and retrieval fulfillment, the field is filled
with the default value.
16 Receiving 100 ans11 16 Receiving 100 ans11 It is the IIN of the receiving institution in the original
institution institution transaction. For exceptional processing, the field is

UPI CONFIDENTIAL 46
 Part III: File Interface

Acquirer’s Dispute Transaction Issuer’s Dispute Transaction Explanation on Field

Seq. Definition Field Format Seq. Definition Field Format
identification code identification code filled with the IIN that receives this transaction
17 System trace audit 90.2 n6 17 System trace audit 90.2 n6 It is the systems trace number of the original
number of original number of original transaction. For exceptional processing, the field is
transaction transaction filled with the default value.
18 Response code 39 an2 18 Response code 39 an2 It is the response code related to the dispute
transaction.
19 Currency code, 49 an3 19 Currency code, 49 an3 It is the transaction currency code related to the
transaction transaction dispute transaction. For retrieval fulfillment, the field
is filled by the default value.
20 Point of service 22 n3 20 Point of service 22 n3 It is the point of service entry mode code for the
entry mode entry mode original transaction. For retrieval fulfillment and
exceptional dispute, the field is filled by default
value.
21 Currency code, 50 n3 21 Currency code, 50 n3 It is the settlement currency code related to the
settlement settlement dispute transaction. For retrieval fulfillment, the field
is filled by default value.
22 Amount, 5 n12 22 Amount, 5 n12 It is the settlement amount related to the dispute
settlement settlement transaction. For retrieval fulfillment, the field is filled
with default value.
23 Conversion rate, 9 n8 23 Conversion rate, 9 n8 It is the settlement conversion rate related to dispute
settlement settlement transaction. For retrieval fulfillment, the field is filled
with default value
24 Settlement date 15 n4 24 Settlement date 15 n4 It is the settlement date related to dispute
transaction. For retrieval fulfillment, the field is filled
with default value.
25 Exchange date 16 n4 25 Exchange date 16 n4 It is the conversion date related to dispute
transaction. For retrieval fulfillment, the field is filled
with default value.

UPI CONFIDENTIAL 47
 Part III: File Interface

Acquirer’s Dispute Transaction Issuer’s Dispute Transaction Explanation on Field

Seq. Definition Field Format Seq. Definition Field Format
26 Cardholder billing 51 an3 It is the Cardholder account currency of the dispute.
currency For retrieval fulfillment, the field is filled with default
value.
27 Cardholder billing 6 n12 It is the Cardholder billing amount of the dispute. For
amount retrieval fulfillment, the field is filled with default
value.
28 Cardholder billing 10 n8 It is the Cardholder billing conversion rate of the
exchange rate dispute. For retrieval fulfillment, the field is filled
with default value.
26 Fee receivable n12 29 Fee receivable n12 It is the returned fee expressed in settlement
(settlement (settlement currency due to the dispute. For retrieval fulfillment,
currency) currency) the field is filled with 0.
27 Fee payable n12 30 Fee payable n12 It is the paid fee expressed in settlement currency
(settlement (settlement due to the dispute. For retrieval fulfillment, the field
currency) currency) is filled with 0.
28 Additional x+n11 31 Additional x+n11 It is filled with 0 currently.
installment installment
payment payment
commission fee commission fee
29 Transaction fee a x+n11 32 Transaction fee a x+n11 It is the service fee that should be returned to
cardholder, e.g. transfer transaction.
30 RF billing currency an3 33 RF billing currency an3
b b

31 Exchange rate n8 33 Exchange rate n8

from RF billing from RF billing
currency to currency to
settlement settlement
currency b currency b

UPI CONFIDENTIAL 48
 Part III: File Interface

Acquirer’s Dispute Transaction Issuer’s Dispute Transaction Explanation on Field

Seq. Definition Field Format Seq. Definition Field Format
32 Original 90.3 n10 34 Original 90.3 n10 Please note that it should be filled with the date of
transaction date transaction date original retrieval if it is a retrieval fulfillment. Since
and time and time the date of retrieval is in the format of “MMDD”, in
this case, “HHMMSS” is filled with zeros.
33 Original 3 n6 35 Original 3 n6
transaction transaction
processing code d processing code d
34 Issuer’s ID ans11 37 Issuer’s ID ans11 It is the Issuer’s ID of original transaction. For
exceptional dispute, the field is filled with the IIN for
the secondary settlement.
35 Receivable fee n12 38 Receivable fee n12 It is the fee caused by the dispute. It should be
(settlement (settlement received in the settlement currency.
currency) currency)
36 Payable fee n12 39 Payable fee n12 It is the fee caused by the dispute. It should be paid
(settlement (settlement in the settlement currency. It includes the fee paid to
currency) currency) UPI. For exceptional dispute, the presenter should
pay RMB 10.
37 Dispute reason n4 40 Dispute reason n4 Please refer to the Reason Code in the Technical
code code Specifications on Bankcard Interoperability - Part VI
Annex. For refund (manual), the reason code is set to
a fixed value of “9707” to make it different from
credit adjustment. For retrieval fulfillment, it is filled
with the default value.
38 Receiving 100 ans11 41 Receiving 100 ans11 It is the IIN of the receiving institution in the original
institution institution transaction.
identification code identification code
of original of original
transaction transaction
39 Card sequence 23 n3 42 Card sequence 23 n3 It is the card sequence number of the receiving
number c number c institution in the original transaction.

UPI CONFIDENTIAL 49
 Part III: File Interface

Acquirer’s Dispute Transaction Issuer’s Dispute Transaction Explanation on Field

Seq. Definition Field Format Seq. Definition Field Format
40 Settlement date of 15 n4 43 Settlement date of 15 n4 For retrieval fulfillment, it is the date of the original
original original transaction.
transaction transaction
41 Transaction 4 n12 44 Transaction 4 n12
amount of original amount of original
transaction transaction
42 Card product 9F63(tag) an24 45 Card product 9F63(tag) an24 1. There are 24 bytes in the ASCII code. The
identifier identifier segment from the 1st to the 8th bytes is the IIN,
which share the same meaning with that in the
Technical Specifications on Bankcard
Interoperability - Part II Online Message. The
segment from the 9th to the 24th bytes indicates
the card product and the benefit sharing model,
consistent with the segment from the 9th to the
16th bytes of the counterpart in the Technical
Specifications on Bankcard Interoperability -
Part II Online Message;
Note: The first 8 bytes are the same as the first
8 bytes of the 9F63 tag value in the online
message. The following 16 bytes are the results
of extending the last 8 bytes of 9F63 tag value
in the online message to characters.
2. Currently, this tag is only valid in E-cash
application, and can be filled with spaces for
debit/credit application.
43 Transaction 60.3.5 ans1 46 Transaction 60.3.5 ans1
initiation method initiation method
44 Card level 60.3.9 ans2 47 Card level 60.3.9 ans1
45 Pricing scheme ans2 48 Pricing scheme ans2 It is used by Members to calculate and check fees.
code code

UPI CONFIDENTIAL 50
 Part III: File Interface

Acquirer’s Dispute Transaction Issuer’s Dispute Transaction Explanation on Field

Seq. Definition Field Format Seq. Definition Field Format
46 Country code 19 n3 49 Country code 19 n3
47 Reserved ans20 50 Reserved ans20
Note a: The transaction fee has not been implemented yet. The value of transaction fee shall be “D00000000000”.
Note b: For the IRF collected by percentage of transaction volume (including capping and floor limits, like POS), the currency of IRF should be the same as
the settlement currency, so currency conversion is not necessary. Therefore, the field of “IRF Billing Currency” should be the same as the “settlement
currency”. The field of “Exchange Rate from IRF Billing Currency to Settlement Currency” should be filled with the fixed value ‘30001000’.
For the fixed fee per transaction (like ATM), the currency of the IRF shall be the same as the “IRF Billing Currency”. For example, suppose the currency of IRF
for ATM is USD and the conversion rate for USD/HKD is 7.753. In this example, the value of the field of “Exchange Rate from IRF Billing Currency to
Settlement Currency” should be “30007753” when the institution conducts settlement in the currency of HKD.
Note c: If Field 23 is not submitted by the Acquirer, GSCS will fill Field 23 with the default value “000” in settlement.
Note d: This field shall be filled with spaces by GSCS when the original transaction is without the processing code. For example, when the original
transaction is chargeback, the field of "Original Transaction Processing Code" in the dispute transaction shall be filled with spaces by GSCS.

UPI CONFIDENTIAL 51
 Part III: File Interface

Format of Real-time Stand-in Authorization Transaction Audit Trailer

The format is applicable to the transaction audit trailer with the segment from the 13 th to the 15th position of its file
name valued as “STI”. This audit trailer is to complete the transaction log of the Issuer if GSCS processes stand-in
authorization transactions. If a transaction is cancelled or reversed on the same day when the original transaction
occurs, the stand-in authorization transaction audit trailer should, in addition to the original transaction, also contain
its reversal transaction and cancellation transaction.
No matter whether the stand-in authorization transaction succeeds or fails, it shall be recorded.
Table 27 Format of Real-time Stand-in Authorization Transaction Audit Trailer for the Issuer

Real-time Stand-in Authorization Transaction Audit Trailer for the Issuer (ISTI)
Seq. Definition Field Description
1 Transaction ans26,
time stamp
The time stamp format in the database is “YYYY-MM-DD-
HH.mm.ss.nnnnnn”.
2 Message type n4
3 PAN 2 n19
4 Processing 3 n6
code
5 Transaction 4 n12
amount
6 Amount, 5 n12
settlement
7 Cardholder 6 n12
billing amount
8 Transmission 7 n10
date/time
9 Settlement 9 n8
conversion rate
10 Cardholder 10 n8
billing
exchange rate
11 System trace 11 n6
audit number
12 Local time of 12 n6
the acceptor
13 Local date of 13 n4
the acceptor
14 Reserved 14 It is filled with 4 spaces.
15 Settlement 15 n4
date

UPI CONFIDENTIAL 52
 Part III: File Interface

Real-time Stand-in Authorization Transaction Audit Trailer for the Issuer (ISTI)
Seq. Definition Field Description
16 Conversion 16 n4
date
17 Merchant’s 18 n4
type
18 Country code 19 n3
of the acquirer
19 Point of service 22 n3
entry mode
code
20 Point of service 25 n2
condition code
21 Point of service 26 n2
PIN obtaining
code
22 Acquiring 32 ans11
institution
identification
code
23 Forwarding 33 ans11
institution
identification
code
24 Retrieval 37 an12
reference
number
25 Authorization 38 an6
identification
response
26 Response code 39 an2
27 Card acceptor 41 ans8
terminal
identification
28 Card acceptor 42 ans15
identification
code
29 Card acceptor 43 ans40
name/location
30 Transaction 49 an3
currency code
31 Settlement 50 an3

UPI CONFIDENTIAL 53
 Part III: File Interface

Real-time Stand-in Authorization Transaction Audit Trailer for the Issuer (ISTI)
Seq. Definition Field Description
currency code
32 Cardholder 51 an3
account
currency
33 Discretionary 60 ans100
field
34 Receiving 100 ans11
institution
identification
code of
original
transaction
35 Issuer IIN ans11
36 Original 90 n42
transaction
information
37 VIP card n1,
indicator
Valid values:
1- Transaction is initiated by a VIP card
2- Transaction is not initiated by a VIP card
38 Reason for ans2,
stand-in
It indicates which stand-in checking or processing causes the failure. The
authorization
system will stop processing once a failure point is triggered, so the following
failure
reasons will not occur at the same time.
Valid values:
01- Card length checking fails
02- Card check-digit checking fails
03- Card expiration date checking fails
04- CVN (CVN2) checking fails
05- PVN checking fails
07- ARQC verification fails
08- TVR & CVR verification fails
09- ICVN verification fails
10- ARPC generation fails
11- Blacklist checking fails
12- Single transaction amount limit for a general card exceeded
13- Cumulative amount limit for a general card exceeded
14- Single transaction amount limit for a VIP card exceeded
15- Cumulative amount limit for a VIP card exceeded
16- Transaction count limit exceeded
17- Accepting region blacklist checking fails
18- Accepting merchant blacklist checking fails
96- System error

UPI CONFIDENTIAL 54
 Part III: File Interface

Real-time Stand-in Authorization Transaction Audit Trailer for the Issuer (ISTI)
Seq. Definition Field Description
It should be filled with spaces when stand-in authorization succeeds.
39 Total stand-in x+n8,
authorization
This field should be filled with valid values in stand-in authorization fee files
fee
only and be filled with spaces in real time stand-in authorization files.
This fee is a total amount of various stand-in items. The stand-in
authorization fee is subject to the following rules:
 The stand-in authorization fee will be charged for a second time if the
transaction is cancelled;
 If the stand-in authorization fee for reversal and its original transaction
is zero, the field should be filled with “D00000000”.
40 IC card data 55 ans255,
field based on
In a stand-in authorization fee file, this field shall be filled with spaces.
UICS
debit/credit In a real time stand-in authorization file, the field shall be filled with the
application value of Field 55 of the original transaction, i.e., the IC card data based on
UICS Debit/Credit Application Standards. The maximum length is 255 bytes,
and the value shall be left-justified with trailing spaces when its length is less
than 255 bytes. These contents do not need to be sent in digits, and the
original message shall be sent directly. It is not necessary to send the
contents in visible characters. It is fine to directly send the contents of the
original message.
41 Transaction 60.3.5 ans1
initiation
method
42 Token-related 63(TK) ans46,
information
The field is filled with spaces by default. If the corresponding online
transaction is a Payment Token Transaction, this field shall be filled as
follows.
Definition Format Description
Token an1 This subfield will be filled based on whether
information the track or chip information (including F23,
verification F35, F36, F45, and F55) are verified by the
indicator GSCS.
Valid Values:
0- Not verified (indicating it is a Token
transaction, but the track or chip information
are generated by the Issuer)
1- Verified
Token an19 Token generated by the TSP
Left-justified with trailing spaces if the value
length is less than 19 bytes.

UPI CONFIDENTIAL 55
 Part III: File Interface

Real-time Stand-in Authorization Transaction Audit Trailer for the Issuer (ISTI)
Seq. Definition Field Description

Token expiry an4 The expiry date of a Token that is generated by

date the TSP.
Format: YYMM
Token an2 The Token assurance level is defined by the TSP
assurance based on the risk assessment.
level
Valid values:
0~99
Left-justified with trailing spaces if the value
length is less than 2 bytes.
Token n2 The Token domain identification indicates the
domain application scenarios which are provided by
identification the TR.
Valid values:
01- SE
02- HCE
03- QR Code
04- Card-on-File (COF)
05- Digital wallet
06- Chip or magnetic stripe card
TRID an11 TRID is a unique number assigned by the TSP
during TR Registration.
Left-justified with trailing spaces if the value
length is less than 11 bytes
Product ans7 The product identification is provided by the
identification TR during Token Request. UnionPay system will
de-tokenize the transaction and forward it to
the Issuer with this value in a Payment Token
Transaction. If the TR does not provide this
information, this subfield will not be present in
the Payment Token Transaction.
The first byte of product identification
indicates the product category and the second
to seventh bytes indicate the product sub-
category:
Position Description
1 byte Filled with the product category
with ans1 attribute.
Valid value:
1- Mobile payment
2~7 Filled with the product sub-
category which is the 10th ~ 12th

UPI CONFIDENTIAL 56
 Part III: File Interface

Real-time Stand-in Authorization Transaction Audit Trailer for the Issuer (ISTI)
Seq. Definition Field Description

bytes bytes of 9F63 in Hex characters

format.
For example: “80B020”,
Byte Binary Value
of Encoded in Hex
9F63 Value
10 10000000 80
11 10110000 B0
12 00100000 20

43 Reserved ans195

Format of Stand-in Authorization Transaction Fee Audit Trailer

The format is applicable to the transaction audit trailer with the segment from the 13 th to the 18th position of its file
name valued as “STIFEE”. The stand-in authorization fee audit trailer for the Issuer (ISTIFEE) contains the fee details
of each stand-in authorization transaction, sent after day-end settlement, including details of transactions related to
stand-in authorization fee for the Issuer’s reconciliation.
Table 28 Format of Stand-in Authorization Transaction Fee Audit Trailer for the Issuer

Stand-in Authorization Transaction Fee Audit Trailer for the Issuer (ISTIFEE)
Seq. Definition Field Description
1 Transaction time ans26,
stamp
The time stamp format in the database is “YYYY-MM-DD-
HH.mm.ss.nnnnnn”.
2 Message type n4
3 PAN 2 n19
4 Processing code 3 n6
5 Transaction amount 4 n12
6 Amount, settlement 5 n12
7 Cardholder billing 6 n12
amount
8 Transmission 7 n10
date/time
9 Settlement 9 n8
conversion rate
10 Cardholder billing 10 n8
exchange rate

UPI CONFIDENTIAL 57
 Part III: File Interface

Stand-in Authorization Transaction Fee Audit Trailer for the Issuer (ISTIFEE)
Seq. Definition Field Description
11 System trace audit 11 n6
number
12 Local time of the 12 n6
acceptor
13 Local date of the 13 n4
acceptor
14 Reserved 14 It is filled with 4 spaces.
15 Settlement date 15 n4
16 Conversion date 16 n4
17 Merchant’s type 18 n4
18 Country code of the 19 n3
acquirer
19 Point of service entry 22 n3
mode code
20 Point of service 25 n2
condition code
21 Point of service PIN 26 n2
obtaining code
22 Acquiring institution 32 ans11
identification code
23 Forwarding 33 ans11
institution
identification code
24 Retrieval reference 37 an12
number
25 Authorization 38 an6
identification
response
26 Response code 39 an2
27 Card acceptor 41 ans8
terminal
identification
28 Card acceptor 42 ans15
identification code
29 Card acceptor 43 ans40
name/location
30 Transaction currency 49 an3
code

UPI CONFIDENTIAL 58
 Part III: File Interface

Stand-in Authorization Transaction Fee Audit Trailer for the Issuer (ISTIFEE)
Seq. Definition Field Description
31 Settlement currency 50 an3
code
32 Cardholder account 51 an3
currency
33 Discretionary field 60 ans100
34 Receiving institution 100 ans11
identification code of
original transaction
35 Issuer IIN ans11
36 Original transaction 90 n42
information
37 Reason for stand-in ans2,
authorization failure
It indicates which stand-in checking or processing causes the failure.
The system will stop processing once a failure point is triggered, so the
following reasons will not occur at the same time.
Valid values:
01- Card length checking fails
02- Card check-digit checking fails
03- Card expiration date checking fails
04- CVN (CVN2) checking fails
05- PVN checking fails
07- ARQC verification fails
08- TVR & CVR verification fails
09- ICVN verification fails
10- ARPC generation fails
11- Blacklist checking fails
12- Single transaction amount limit for a general card exceeded
13- Cumulative amount limit for a general card exceeded
14- Single transaction amount limit for a VIP card exceeded
15- Cumulative amount limit for a VIP card exceeded
16- Transaction count limit exceeded
17- Accepting region blacklist checking fails
18- Accepting merchant blacklist checking fails
96- System error
It should be filled with spaces when stand-in authorization succeeds.
38 Total stand-in x+n8,
authorization fee
This fee is a total amount of various stand-in items. The currency is the
same as the settlement currency.
The stand-in authorization fee is subject to the following rules:
 The stand-in authorization fee will be charged for a second time if
the transaction is cancelled;

UPI CONFIDENTIAL 59
 Part III: File Interface

Stand-in Authorization Transaction Fee Audit Trailer for the Issuer (ISTIFEE)
Seq. Definition Field Description
 If the stand-in authorization fee for reversal and its original
transaction is zero, the field should be filled with “D00000000”.
39 IC card data field 55 ans255,
based on UICS
In a stand-in authorization fee file, this field shall be filled with spaces.
debit/credit
application In a real time stand-in authorization file, the field shall be filled with
the value of Field 55 of the original transaction, i.e., the IC card data
based on UICS Debit/Credit Application Standards. The maximum
length is 255 bytes, and the value shall be left-justified with trailing
spaces when its length is less than 255 bytes. These contents do not
need to be sent in digits, and the original message shall be sent
directly. It is not necessary to send the contents in visible characters. It
is fine to directly send the contents of the original message.
40 Transaction initiation 60.3.5 ans1
method
41 Reserved ans242

Format of Brand Service Fee Audit Trailer (Not Used Currently)

Format of Fee Collection and Fund Disbursement Transaction Audit Trailer
The value of the segment from the 12th to the 14th position in the file name for UPI fee collection and fund
disbursement transaction is “FCP”. The file header record, the file body record, and the file trailer record are
separated by carriage returns/linefeeds (0X0D, 0X0A). At the end of the file trailer record, a carriage return/linefeed
(0X0D, 0X0A) must be added as well.
Table 29 Format of Fee Collection and Fund Disbursement Transaction Audit Trailer

Fee Collection and Fund Disbursement Transaction Audit Trailer

Seq. Definition Format Description
1 Transaction an3 Valid values:
code E20- Fee Collection
E30- Fund Disbursement
2 Settlement x+n12 The fee collection transaction can only be initiated by UPI. Therefore, when
amount the transaction code is “Fee Collection”, X=D, which indicates a debit to the
Member who receives this file.
When the transaction code is “Fee Disbursement”, there are two cases:
If the transaction is triggered by other Member, then X=C, which indicates a
credit to the Member who receives this file”;
If the transaction is triggered by the Member itself, then X=D, which
indicates a debit to the Member who receives this file.
3 Reason code n4 The field is filled with the message reason code of fee collection/fund
disbursement.
4 Level 1 ans11 When the transaction code is “Fee Collection”, this field will be filled with

UPI CONFIDENTIAL 60
 Part III: File Interface

Fee Collection and Fund Disbursement Transaction Audit Trailer

Seq. Definition Format Description
sender UPI’s IIN; when the transaction code is “Fund Disbursement”, this field
should be filled with the IIN of the Level 1 Sender of the fund disbursement
transaction, such as the headquarters’ IIN. If there is no Level 1 Member, this
field should be filled with the Level 2 Sender’s IIN.
5 Level 2 ans11 When the transaction code is “Fee Collection”, this field should be filled with
sender UPI’s IIN; when the transaction code is “Fund Disbursement”, this field
should be filled with the IIN of the Level 2 Sender that initiates the
transaction, for example, the branch‘s IIN. If there is no Level 2 Member, the
field should be filled with the Level 1 IIN.
6 Level 1 ans11 When the transaction code is “Fee Collection”, this field should be filled with
receiver the IIN of the Level 1 Receiver of the fee collection transaction, such as the
headquarters’ IIN; when the transaction code is “Fund Disbursement”, the
field should be filled with the IIN of the Level 1 Receiver of the fund
disbursement transaction, such as the headquarters’ IIN. If there is no Level
1 Member, the field should filled with the Level 2 IIN.
7 Level 2 ans11 When the transaction code is “Fee Collection”, this field should be filled with
receiver the IIN of the Level 2 Receiver of the fee collection transaction, e.g. the
branch‘s IIN; when the transaction code is “Fund Disbursement”, this field
should be filled with the IIN of the Level 2 Receiver of the fund disbursement
transaction. If there is no Level 2 Member, this field should be filled with the
Level 1 IIN.
8 Transaction n10
date and time
9 System trace n6
audit number
10 PAN ans19 When a fee collection/fund disbursement transaction is associated with a
PAN, this field should be filled with the related PAN information. When it is
not associated with a PAN, this field should be filled with spaces.
11 Settlement an3 The same as Field 50 defined in the Technical Specifications on Bankcard
currency Interoperability - Part II: Online Message
12 Reserved ans196

Format of Fee Collection and Fund Disbursement Transaction Audit Trailer for
Secondary Member
The value of the segment from the 12th to the 15th position in the file name for UPI fee collection and fund
disbursement transaction for Secondary Member is “FCPB”. The file header record, the file body record, and the file
trailer record are separated by carriage returns/linefeeds (0X0D, 0X0A). At the end of the file trailer record, a carriage
return/linefeed (0X0D, 0X0A) must be added as well.
Table 30 Format of Fee Collection and Fund Disbursement Transaction Audit Trailer for Secondary Member

UPI CONFIDENTIAL 61
 Part III: File Interface

File Header Record Definition

Seq. Pos. Format Definition Description
1 0 ans62 Reserved field 1 Filled with spaces currently
2 62 ans11 IIN Left-justified with trailing spaces if the length is less than 11
3 73 n8 Settlement date Format: YYYYMMDD
4 81 ans292 Reserved field 2 Filled with spaces currently
File Body Record Definition (Refer to Section 3.2.13 Format of Fee Collection and Fund Disbursement
Transaction Audit Trailer)
File Trailer Record Definition
1 0 ans62 Reserved field 1 Filled with all ‘Z’s.
2 62 ans11 IIN Left-justified with trailing spaces if the length is less than 11.
3 73 n8 Settlement date Format: YYYYMMDD
4 81 ans6 Total number of Total number of records (including the header and the
records trailer)
5 87 ans18 PAN HASH check value ∑ the absolute value of [CB PAN (digit 1~digit 10) + (digit
11~digit 19)], refer to Section 3.2.4 for details.
6 105 ans18 Settlement amount ∑ [Absolute(Settlement Amount) ]
HASH check value
7 123 ans250 Reserved field 2 Filled with spaces currently

Format of Directly-connected POS Transaction Audit Trailer

The format is applicable to the transaction audit trailer with the segment from the 12 th to the 18th position of its file
name valued as “ACOMPOS”. If the Acquirer subscribes to the ACOMN file for directly-connected POS transactions
(including QRC transactions), the Acquirer must be aware that the ACOMN will contain both directly-connected
transactions and indirectly-connected transactions under the IIN. Acquirers can identify whether the transaction is
directly-connected or not based on Field 33 Forwarding Institution Identification Code. Acquirer must be aware that
the directly-connected POS transactions will be represented in both “IFDYYMMDD01ACOMPOS” (if the Acquirer still
wants it) and “IFDYYMMDD??ACOMN”. Acquirers must avoid processing the same transaction twice.
Table 31 Format of Directly-connected POS Transaction Audit Trailer

Directly-connected POS Transaction Audit Trailer

Seq. Definition Field Format
1 Acquiring institution identification code 32 ans11
a
2 Forwarding institution identification code 33 ans11
3 System trace audit number 11 n6
4 Transmission date and time 7 n10
b
5 Primary account number (PAN) 2 n19
6 Amount, transaction 4 n12

UPI CONFIDENTIAL 62
 Part III: File Interface

Directly-connected POS Transaction Audit Trailer

Seq. Definition Field Format
7 Message type MTI n4
8 Processing code 3 n6
9 Merchant type 18 n4
10 Card acceptor terminal identification 41 ans8
11 Card acceptor identification code 42 ans15
12 Card acceptor name/location 43 ans40
13 Retrieval reference number 37 an12
14 Point of service condition code 25 n2
15 Authorization identification response 38 an6
16 Receiving institution identification code 100 ans11
17 System trace audit number of original transaction 90.2 n6
18 Response code g 39 an2
19 Currency code, transaction 49 an3
20 Point of service entry mode 22 n3
21 Currency code, settlement 50 n3
22 Amount, settlement 5 n12
23 Conversion rate, settlement 9 n8
24 Settlement date 15 n4
25 Exchange date e 16 n4
26 Fee receivable (settlement currency) c n12
27 Fee payable (settlement currency) c n12
28 Additional installment payment commission fee x+n11
29 Service fee currency an3
30 Service fee exchange rate n8
31 Transaction fee x+n11
32 RF billing currency an3
33 Exchange rate from RF billing currency to settlement currency n8
34 Reserved for use d ans30
Note a: Forwarding institution identification code will be filled with the IIN of UnionPay Front-end Processing
Systems, i.e. 00020344, and left-justified with 3 trailing spaces.
Note b: PAN is left-justified with trailing spaces if the length is less than 19 digits.
Note c: The sum of all credit-entry fees (which may include interchange reimbursement fee and/or service fee
for some transactions, etc.) for the member shall be put in the field of “Fee Receivable”. The sum of all debit-

UPI CONFIDENTIAL 63
 Part III: File Interface

Directly-connected POS Transaction Audit Trailer

Seq. Definition Field Format
entry fees (which may include interchange reimbursement fee and/or service fee, etc.) for the member shall be
put in the field of “Fee Payable”.
Note d: Format: YYYYYYYYYYYYMMDDHHMMSSFXXYYZII with carriage return/linefeed (0X0D,0X0A) added on
the right, among which:
1) “YYYYYYYYYYYY” is the fee Merchants pay to Acquirers.
2) “MMDDHHMMSS” is the transmission time of the original transaction. If there is no original transaction, it
shall be filled with 10 spaces.
3) “F” stands for the card level, i.e. the value of Field 60.3.9.
4) “XX” stands for the transaction channel. Please refer to the definition of Field 60.2.5 in the Technical
Specifications on Bankcard Interoperability - Part II Online Message. For example, for manual transactions, this
field is filled with “12”.
5) “YY” stands for the pricing scheme code. It is for Members to calculate or check the service fee.
6) “Z” stands for the transaction initiation method, i.e. the value of F60.3.5.
7) “II” stands for the number of installment payment terms. For example, “06” means 6 terms while “12”
stands for 12 terms. For transactions other than installment payment purchase and installment payment fixed-
amount authorization, “II” will be filled with spaces.
Note e: This field mandatorily exists despite its possible absence in online message, and represents the
effective date of the currency conversion rate applied in this record.

Format of UPI Institution Fee Settlement File

The format is applicable to the UPI Institution Fee Settlement File with the segment from the 12th to the 18th position
in its file name valued as “FEEDTL/FEEDTLB”. For the detailed and more accurate fee settlement file provided to
Members, the computational accuracy is changed from the minimum accuracy of the currency to 1/10000 of the
minimum accuracy of the currency. The Acquirer, the Issuer and the Secondary Issuer share the same file format.
Note: There is no space between fields in the FEEDTL/FEEDTLB file.
Table 32 Format of Fee Collection and Fund Disbursement Transaction Audit Trailer

Fee Collection and Fund Disbursement Transaction Audit Trailer

Seq. Definition Field Format Description
1 Acquiring institution 32 ans11
identification code
2 Forwarding institution 33 ans11
identification code
3 System trace audit 11 n6
number
4 Transmission date/time 7 n10
5 Primary account number 2 n19
(PAN)

UPI CONFIDENTIAL 64
 Part III: File Interface

Fee Collection and Fund Disbursement Transaction Audit Trailer

Seq. Definition Field Format Description
6 Card acceptor 42 ans15
identification code
7 Authorization 38 an6
identification response
8 Reversal identification n1 Valid values:
0- None reversal
1- Reversal
9 Transaction type n1 Valid values:
identification 0- Online transaction
1- Batch file transaction
2- Dispute and manual transaction
10 Receiving institution 100 ans11
identification code
11 Issuing institution ans11
identification code
12 Currency code, 50 an3
settlement
13 Total fee ID an4 Valid value:
TFEE
14 Total fee debit/credit a1 Valid values:
identification C- Credit
D- Debit
15 Total fee amount n16 It is the round number, right-justified with leading zeros.
The computational accuracy is 1/10000 of the minimum
computational accuracy of the currency.
16 Total reimbursement fee an4 Valid value:
ID TRMB
17 Total reimbursement fee a1 Valid values:
debit/credit C- Credit
identification D- Debit
18 Total reimbursement fee n16 It is the round number, right-justified with leading zeros.
amount The computational accuracy is 1/10000 of the minimum
computational accuracy of the currency.
19 Total service fee ID an4 Valid value:
TSVC
20 Total service fee a1 Valid values:
debit/credit C- Credit
identification D- Debit
21 Total service fee amount n16 It is the round number, right-justified with leading zeros.
The computational accuracy is 1/10000 of the minimum

UPI CONFIDENTIAL 65
 Part III: File Interface

Fee Collection and Fund Disbursement Transaction Audit Trailer

Seq. Definition Field Format Description
computational accuracy of the currency.
22 Reserved field ans50 Reserved field
23 Number of detailed fees n3 It is the number of the detailed fee fields contained in a
field record, which is determined by the number of the fees
incurred for a transaction. It might vary according to
transaction type.
24 Detailed fee 1 ID an4 Please refer to file instruction 3.
Detailed fee 1 reverse fee n1 Valid values:
identification 0- Original fee: the actual fee related to the online or
batch transaction (except refund);
1- Reverse fee: the fee returned to participants in a
dispute transaction or other circumstance.
Detailed fee 1 a1 Valid values:
debit/credit C- Credit
identification D- Debit
Detailed fee 1 amount n16 It is the round number, right-justified with leading zeros.
The computational accuracy is 1/10000 of the minimum
computational accuracy of the currency.
Detailed fee 2 ID an4 Please refer to file instruction 3.
Detailed fee 2 reverse fee n1 Valid values:
identification 0- Original fee: the actual fee related to the online or
batch transaction (except refund);
1- Reverse fee: the fee returned to participants in a
dispute transaction or other circumstance.
Detailed fee 2 a1 Valid values:
debit/credit C- Credit
identification D- Debit
Detailed fee 2 amount n16 It is the round number, right-justified with leading zeros.
The computational accuracy is 1/10000 of the minimum
computational accuracy of the currency.
……
Detailed fee n ID an4 Please refer to file instruction 3.
Detailed fee n reverse n1 Valid values:
fee identification 0- Original fee: the actual fee related to the online or
batch transaction (except refund);
1- Reverse fee: the fee returned to participants in a
dispute transaction or other circumstance.
Detailed fee n a1 Valid values:
debit/credit C- Credit
identification D- Debit

UPI CONFIDENTIAL 66
 Part III: File Interface

Fee Collection and Fund Disbursement Transaction Audit Trailer

Seq. Definition Field Format Description
Detailed fee n amount n16 It is the round number, right-justified with leading zeros.
The computational accuracy is 1/10000 of the minimum
computational accuracy of the currency.
File instruction 1: The settlement file consists of several records. Each record corresponds to a certain
transaction, and every two records are separated by carriage return/linefeed (0X0D,0X0A); transactions where
fees need to be calculated should be included in this file, such as purchase, cash withdraw, balance inquiry,
online payment, remittance, refund, MOTO, recurring, and dispute transactions; Cancellation, reversal, etc.,
are not included in this file unless otherwise required by Members.
File instruction 2:
1) The structure of the record is:
Primary transaction attribute
Settlement currency
Total fee field
Total reimbursement fee field
Number of detailed fees
Detailed fee 1 field
Detailed fee 2 field
……
Detailed fee n field
2) The structure of each fee field is:
Fee ID
Fee counter-original identification
Fee credit/debit identification
Fee amount
The number of detailed fees depends on the actual number of fees incurred for a transaction. Therefore, the
length of each record is not fixed.
File instruction 3:
The fee ID is the indicator of the fee types and is designated by UPI.
Total fee, total reimbursement fee and total service fee IDs are:
TFEE- Total fee;
TRMB- Total reimbursement fee;
TSVC- Total service fee
Detailed reimbursement fee ID is numbered as:
R001, R002, R003 …
Detailed service fee ID is numbered as:
S001, S002, S003 …
The default reimbursement fee and the default service fee are part of the detailed fees. The default
UPI CONFIDENTIAL 67
 Part III: File Interface

Fee Collection and Fund Disbursement Transaction Audit Trailer

Seq. Definition Field Format Description
reimbursement fee ID is R001; the additional installment payment commission fee ID is R002; the international
service fee ID is S001; the cross-border transaction fee ID is S002. When the cross-border transaction fee is not
applicable, S002 may be present with the amount of 0 or absent. Issuers and Acquirers must support both
forms.
File instruction 4: Transaction records are not sorted in file.
File instruction 5: For Reverse Fee Identification, the original fee represents the actual fee related to the online
and batch transaction (except refund). The reverse fee represents the refund transaction or fee which should
be returned in the dispute transaction.

UPI CONFIDENTIAL 68
 Part III: File Interface

4 Settlement File
4.1 Overview of Settlement File
Function of Settlement File
Settlement files include those submitted to GSCS by Members for settlement and those delivered to Members by
GSCS after settlement. The former are used by GSCS to settle with Members. The latter are intended for Members’
reconciliation.
Records in settlement files can be classified in the following groups by card medium:
Records in the settlement files for dual-message magnetic stripe transactions are displayed in the feature blocks of
the file format, i.e. Block 0 and Block 1.
Records in the settlement files for dual-message IC cards based on the UICS debit/credit standards are displayed in
the feature blocks of the file format, i.e. Block 0, Block 1, and Block 2.
Each file record shall be added with a carriage return/linefeed (0X0D,0X0A) on the right.

Naming Rules for Settlement File

Dual-message settlement files submitted by Members:
Table 33 Naming Rules For Dual-message Settlement File Submitted by Members

File Name Value of Position 1~11 Value of Position Record Type Included
12 in File
Outgoing Valid value for Position 1~11: Valid values for TC 000 File Header
settlement file OFCYYMMDD5?, where ? stands for the file Position 12: Record;
batch number C- Settlement file
TC 100/101/102
OFBYYMMDD??, where ? stands for the file Transaction Record;
batch number (reserved for UPI internal use)
TC 001 File Trailer
Record
Dual-message settlement files distributed by GSCS:
Table 34 Naming Rules For Dual-message Settlement File Distributed by GSCS

File Name Value of Position 1~11 Value of Position Record Type

12/12~13 Included in File
Incoming Valid value for Position 1~11: Valid values for Position TC 000 File Header;
reject file IFCYYMMDD5?, where ? stands for the 12:
TC 002 Reject
file batch number R- Reject file
Record;
TC 003 Error File
Record;
TC 001 File Trailer
Incoming Valid value for Position 1~11: Valid values for Position TC 000 File Header;
settlement file IFCYYMMDD??, where ?? stands for the 12/12~13:
TC 100/101/102
receiving member: 51 for the Acquirer C- General transaction
Transaction Record;
and 99 for the Issuer settlement file
CB- General transaction TC 001 File Trailer
settlement file for

UPI CONFIDENTIAL 69
 Part III: File Interface

File Name Value of Position 1~11 Value of Position Record Type

12/12~13 Included in File
secondary member

Incoming Valid value for Position 1~11: Valid values for Position TC 000 File Header;
statistic file IFCYYMMDD??, where ?? stands for the 12/12~13:
TC 900 Fund
receiving member: 51 for the Acquirer S- Transaction statistic
Settlement Record;
and 99 for the Issuer file;
SB- Transaction statistic TC 901 Incoming
file for secondary member STF Statistics;
TC 902 Outgoing
STF Statistics;
TC 001 File Trailer
Note: Files applied to an Acquirer may include OFCYYMMDD5?C, IFCYYMMDD51C, IFCYYMMDD5?R, and
IFCYYMMDD51S. While files applied to an Issuer may include IFCYYMMDD99C/CB, IFCYYMMDD99S/SB.

Settlement File Processing

On each settlement day, Members submit dual-message settlement files to GSCS; with respect to the dual-message
settlement files submitted by Members after GSCS completes the cut-off, though the settlement date of these
submitted files is the last business day, GSCS will still process these dual-message settlement files based on GSCS’s
current settlement date. After GSCS completes the cut-off, GSCS will deliver settlement files of the last settlement
date to each Member. If no settlement files are submitted by a Member for one business day, GSCS will generate and
deliver a feedback file with file header and file trailer but without transaction record to the Member.
If there is no rejected transactions in files submitted by the Member, GSCS will generate and deliver a feedback file
with file header and file trailer but without reject record to the Member.

Acquirer GSCS Issuer

2 3

Figure 14 Processing Flow of Dual-message Settlement Files

1. GSCS receives dual-message settlement files submitted by Acquirers and the settlement files include:
OFCYYMMDD5?C
2. After settlement, GSCS deliver dual-message settlement files to Acquirers and the settlement files include:
IFCYYMMDD51C, IFCYYMMDD51S, and IFCYYMMDD5?R
3. After settlement, GSCS deliver dual-message settlement files to Issuers and the settlement files include:
IFCYYMMDD99C/CB, IFCYYMMDD99S/SB

UPI CONFIDENTIAL 70
 Part III: File Interface

File List and Access Mode of Settlement File

Table 35 File List and Access Mode of Settlement File

File Name Description File Access Mode

(Y: Allowed;
N: Not Allowed)
Flow SFTP
Transmission
OFCYYMMDD5?C International transaction settlement files delivered from the Y Y
Member to UPI
IFCYYMMDD5?R International transaction rejection files delivered from UPI to Y Y
the Member
IFCYYMMDD51C International general transaction settlement files delivered Y Y
from UPI to the Member
IFCYYMMDD51S International transaction statistics files delivered from UPI to Y Y
the Member
IFCYYMMDD99C International transaction settlement file delivered from UPI to Y Y
the Issuer
IFCYYMMDD99S International transaction statistics files delivered from UPI to Y Y
the Issuer
IFCYYMMDD99CB International transaction settlement file delivered from UPI to Y Y
the secondary Issuer
IFCYYMMDD99SB International transaction statistics files delivered from UPI to Y Y
the secondary Issuer

4.2 Format of Settlement File

TC 100/101/102- Transaction Record
4.2.1.1 Block 0- Basic Settlement Information
Table 36 Block 0- Basic Settlement Information

Position Definition Format Field I/O Description

1~3 Transaction n3 I/O Valid values in the outgoing file (Member to
code UnionPay):
100- Settlement
101- Refund, MO/TO Refund
102- Manual cash withdrawal/POS cash withdrawal
300- Offline purchase of IC Card E-cash application
301- Offline refund of IC Card E-cash application
Valid value in the incoming file (UnionPay to
Member):
100- Settlement;
101- Refund (including online refund, manual refund,
and credit voucher refund; Field 22 and Field 60.2.5
are used to differentiate these three types of refund);

UPI CONFIDENTIAL 71
 Part III: File Interface

Position Definition Format Field I/O Description

102- Manual cash withdrawal
300- Offline purchase of IC card E-cash application
301- Offline refund of IC card E-cash application
4~7 Block bitmap an4 I/O In the outgoing file, any invalid value will cause
rejection by UnionPay with settlement file rejection
code “14”.
8~26 PAN n19 2 I/O It should be left-justified with trailing spaces if the
length is less than 19 digits. In the outgoing file
submitted by Member, the value of this field should
be equal to that of Field 2 of the original online
message.
27~38 Amount, n12 4 I/O For fixed-amount authorization, the value of this field
transaction should be equal to that of Field 4 of the original online
message. For estimated-amount authorization, the
value cannot exceed the limit specified in the UPI
Operating Regulations. For refund, the value is the
amount to be refunded, and shall not exceed the
amount of the original transaction.
39~41 Currency, an3 49 I/O It is the transaction currency. The value of this field
transaction should be equal to that of Field 49 of the original
online message.
Note: UnionPay uses numeric currency codes.
42~51 Transaction n10 7 I/O The format is “MMDDhhmmss”. In settlement files
date and time submitted by Members, for fixed-amount
authorization, the value of this field must be equal to
that of Field 7 of the original online message. For
estimated-amount authorization, the value of this
field can be re-assigned by the Acquirer. For refund
records, the value of this field should be re-assigned
by the Acquirer. Please note that Acquirers must
submit this field in the format of “MMDDhhmmss” in
all cases.
52~57 System trace n6 11 I/O It is provided by the sender. It remains unique in all
audit number batches of the processing day, like the values of Field
7, Field 32 and Field 33. It remains unchanged in a
processing cycle. In settlement files submitted by
Members, for fixed-amount authorization, the value of
this field must be equal to that of Field 11 of the
original online message. For estimated-amount
authorization, the value of this field can be re-
assigned by the Acquirer. For refund records, the value
of this field should be re-assigned by the Acquirer.
58~63 Authorization an6 38 I/O It is the authorization identification response given by
identification the Issuer when the authorization is obtained; in
response settlement files submitted by Members, the value of
this field must be equal to that of Field 38 of the

UPI CONFIDENTIAL 72
 Part III: File Interface

Position Definition Format Field I/O Description

original online message.
For offline purchase of IC card debit/credit application,
the default value of this field is filled with spaces;
For offline purchase/refund of IC card E-cash
application, this field is filled with the value of
tag9F74.
64~67 Date of n4 15 I/O It is the date when the authorization is obtained,
authorization equal to the value of Field 15 Settlement Date in the
original authorization transaction message with the
format of “MMDD”.
For refund with no original transactions, this field shall
be filled with spaces.
For offline purchase and offline refund of UICS
debit/credit application and e-cash application, the
default value of this field should be filled with spaces.
Note: Due to discrepancy between cut-off (set as
“T+1” for online messages from 11:00 pm on T day to
11:00 pm on T+1 day) and switch of file date (set as
“T+1” for submission from 04:00 am on T day to 04:00
am on T+1 day), transactions authorized between
11:00 pm on T day to 04:00 am on T+1 day shall be
submitted for settlement after 04:00 am on T+1 day,
so that the transaction can be settled by cut-off of T+1
day. That is, file date shall be at least 1 day later than
date of authorization.
68~79 Retrieval an12 37 I/O It is generated by the terminal to identify a
reference transaction.
number
80~90 Acquiring ans11 32 I/O It is left -justified with trailing spaces if the length is
institution less than 11 bytes. In settlement files submitted by
identification Members, this field value must be the same as that of
code Field 32 of original authorization transaction.
91~101 Forwarding ans11 33 I/O It is left-justified with trailing spaces if the length is
institution less than 11 bytes. In settlement files submitted by
identification Members, this field value must be the same as that of
code Field 33 of the original authorization transaction.
102~105 Merchant Type n4 18 I/O It is the acceptor’s MCC. The value of this field should
be equal to that of Field 18 of the original online
message.
106~113 Card acceptor ans8 41 I/O It is the terminal identifier of the card acceptor
terminal terminal. The value remains unchanged throughout
identification the whole transaction cycle.
114~128 Card acceptor ans15 42 I/O It is the card acceptor identification code assigned by
identification the institution in charge of POS. In settlement files

UPI CONFIDENTIAL 73
 Part III: File Interface

Position Definition Format Field I/O Description

code submitted by Members, this field value must be equal
to that of Field 42 of the original authorization
transaction.
129~168 Card acceptor ans40 43 I/O It is the card acceptor name/location. The value of this
name/location field is equal to that of Field 43 in the original
authorization transaction.
Note: Unprintable characters such as carriage
return/linefeed (0x0D,0x0A) are not allowed.
168~191 Original an23 I/O It should be filled with following details in the refund
transaction transaction record upon its original transaction
information existing:
Seq. Format Value in Hex
1 n3 Original transaction code
2 n10 Original transaction date and time
3 n6 Original transaction system trace
audit number
4 n4 Original transaction settlement
date
It should be filled with all “0”s in the record of refund
transaction without original transaction, and will be
filled with all “0”s in the settlement transaction
records as well.
192~195 Message reason n4 I/O Filled with “0000”
code
196 Single or dual n1 I/O It is filled by the sender. It should be in accordance
message with original transaction.
identifier
Valid values:
0- Single message
1- Dual message
For offline purchase of IC card including debit/credit
application and E-cash application, this field is filled
with “0”.
197~205 GSCS serial n9 I It is filled by GSCS in the Incoming Settlement File and
number shall be filled with “000000000” by Members in the
Outgoing Settlement File.
206~216 Receiving ans11 100 I It is left-justified with trailing spaces if the length is
institution less than 11 digits. It must be in accordance with the
identification original transaction.
code
217~227 Issuing ans11 I It is left-justified with trailing spaces if the length is
institution less than 11 digits. It must be in accordance with the

UPI CONFIDENTIAL 74
 Part III: File Interface

Position Definition Format Field I/O Description

identification original transaction.
code
228 Identifier of n1 I Valid value:
GSCS notice 0- normal transaction record
229~230 Transaction n2 60.2.5 I/O The value of this field is equal to that of Field 60.2.5 in
initiating the original authorization transaction.
channel
231 Identifier of a1 I/O Valid values:
transaction F- Full presentment
features P- Partial presentment
R- Refund
T- Tax refund
Filled with a space for other transactions.
232~234 Transaction an3 125(IP) I/O This field is filled with spaces by default.
scenario Tag01
For Innovative Payment transactions defined in Field
indicator
125 Usage IP:
1) In the incoming file distributed by GSCS, this field
will be filled with the value of Field 125 Usage IP Tag
01;
2) In the outgoing file submitted by Member, the
transmission requirement and valid values of this field
are subject to applicable implementation guides for
innovative payment product schemes.
235~239 Reserved an5 I Filled with spaces
240~269 Other ans30 I/O See Note a.
information a
Note a: The sequence and value information for other information are as follows.
Position Definition Format Field I/O Description
240~241 Installment n2 I/O It is the number of installment payment terms. For
payment terms example, “03” stands for 3 terms; “06” stands for
six terms and “12” stands for twelve terms.
Filled with spaces for transactions other than
installment payment purchase and installment
payment fixed-amount authorization.
242 Stand-in an1 I/O It is filled with a space by default.
authorization
For a stand-in authorization transaction record in
identifier
the file distributed to the Issuer, this field should
be filled with “Y”.
243~244 Point of service n2 25 I/O It is the point of service condition code, i.e. the
condition code value of Field 25 in original authorization.
For settlement, it could be used to define the

UPI CONFIDENTIAL 75
 Part III: File Interface

Position Definition Format Field I/O Description

transaction type, i.e., whether it is a purchase,

MO/TO or recurring transaction.
245~247 Merchant n3 19 I/O The Acquirer should submit the value of this field
country code in original authorization transactions, which is
equal to the value of Field 19.
GSCS will fill it with the Acquirer’s country code
when sending the message to the Member.
248 Transaction ans1 60.3.5 I/O The value of this field is equal to that of Field
initiation 60.3.5 in the original authorization transaction.
method
249~251 Original n3 I/O It is the type of authorization submitted by an
authorization international Acquirer.
type
Valid values:
100- Original authorization is fixed-amount
101- Original authorization is estimated-amount
Note: This position shall be filled with spaces in
TC101.
252 Card level ans1 60.3.9 I The value is the same as that of definition in Field
60.3.9.
253~254 Pricing scheme n2 I/O It is the pricing scheme for Acquirers and Issuers
code to calculate fees. This field is filled by GSCS. In the
settlement file submitted from Acquirers to GSCS,
this field shall be filled with the default value of
“00”.
Valid values:
00- Current international pricing scheme code
(default value);
01- Pricing scheme code for transactions within
and between Hong Kong and Macau;
02- Pricing scheme code for Singaporean domestic
transactions;
03- Pricing scheme code for Russian domestic
transactions;
04- Pricing scheme code for Malaysian domestic
transactions;
05- Pricing scheme code for intra-regional
transactions across the EEA countries, between
the EEA countries and United Kingdom, and
between the EEA countries and Andorra;
06 - Pricing scheme code for Kazakhstan domestic
transactions;
07- Pricing scheme code for Mauritius domestic
transactions;
08- New international pricing scheme code. This
new value currently applies to cross-border

UPI CONFIDENTIAL 76
 Part III: File Interface

Position Definition Format Field I/O Description

transactions with UnionPay cards issued outside

of Mainland China and used inside Mainland
China, and cross-border transactions with
UnionPay cards issued and used within the 16
pilot countries /areas (Vietnam, Laos, Cambodia,
Myanmar, Malaysia, Indonesia, Brunei,
Philippines, Hong Kong, Macau, Taiwan, Korea,
Japan, Singapore, Thailand, and Mainland China);
09- Pricing scheme code for Philippine domestic
transactions;
10- Pricing scheme code for Seychellois domestic
transactions;
11- Pricing scheme code for Kenyan domestic
transactions;
12- Pricing scheme code for Rwandan domestic
transactions;
13- Pricing scheme code for Ugandan domestic
transactions;
14- Pricing scheme code for Tanzanian domestic
transactions;
15- Pricing scheme code for Belgian domestic
transactions;
16- Pricing scheme code for British domestic
transactions;
17- Pricing scheme code for French domestic
transactions;
18- Pricing scheme code for Dutch domestic
transactions;
19- Pricing scheme code for Italian domestic
transactions;
20- Pricing scheme code for Spanish domestic
transactions;
21- Pricing scheme code for Burmese domestic
transactions;
22- Pricing scheme code for Thai domestic
transactions;
23- Pricing scheme code for Vietnamese domestic
transactions;
24- Reserved for use;
25- Pricing scheme code for domestic transactions
in Japan;
26- Pricing scheme code for domestic transactions
in Nepal;
27- Pricing scheme code for domestic transactions
in Portugal;
28- Pricing scheme code for domestic transactions
in Bangladesh;
29- Pricing scheme code for domestic transactions
in Sri Lanka;
30- Pricing scheme code for domestic transactions

UPI CONFIDENTIAL 77
 Part III: File Interface

Position Definition Format Field I/O Description

in Australia (with dual-brand debit/pre-paid

cards);
31- Pricing scheme code for domestic transactions
in Australia (with other cards);
32- Pricing scheme code for domestic transactions
in the US Region (Issuers subject to Durbin
Amendment and meeting fraud-prevention
standards);
33- Pricing scheme code for domestic transactions
in the US Region (Issuers subject to Durbin
Amendment and not meeting fraud-prevention
standards);
34- Pricing scheme code for domestic transactions
in the US Region (Reserved for future use);
35- Pricing scheme code for domestic transactions
in Georgia;
36- Pricing scheme code for domestic transactions
in Belarus;
37- Pricing scheme code for domestic transactions
in Ghana;
38- Pricing scheme code for domestic transactions
in Pakistan (with signature-based debit/signature-
based pre-paid cards);
39- Pricing scheme code for domestic transactions
in Pakistan (with credit/pin-based debit/pin-based
pre-paid cards);
40- Pricing scheme code for cross-border
transactions in the Russia and Commonwealth of
Independent States and Southeast Europe
(CISSEE) intraregional jurisdictions. Countries in
the CISSEE jurisdiction include Albania, Armenia,
Azerbaijan, Belarus, Bosnia and Herzegovina,
Georgia, Kazakhstan, Kosovo, Kyrgyzstan,
Macedonia, Moldova, Montenegro, Republic of
Serbia, Tajikistan, Turkmenistan, Ukraine and
Uzbekistan;
41- Pricing scheme code for domestic transactions
in United Arab Emirates;
42- Pricing scheme code for domestic transactions
in Madagascar;
43- Pricing scheme code for domestic transactions
in Ukraine;
44- Pricing scheme code for domestic transactions
in Uzbekistan;
45- Pricing scheme code for domestic transactions
in Maldives;
46- Pricing scheme code for domestic transactions
in Switzerland;

UPI CONFIDENTIAL 78
 Part III: File Interface

Position Definition Format Field I/O Description

47- Pricing scheme code for domestic transactions

in Cambodia;
48- Pricing scheme code for domestic transactions
in Andorra
255~257 Special an3 I/O It is the settlement currency. Please refer to
settlement Section A.5 of the Technical Specifications on
currency Bankcard Interoperability - Part VI Annex for
details.
The field must be filled when Members send file
to GSCS. When the file is sent by GSCS, this field
should be filled with spaces. If there is no special
settlement currency defined for UnionPay RMB
settlement service in a transaction, this field
should be filled with spaces.
258~259 E-commerce n2 60.2.8 I/O It is the ECI. ECI is only used for e-commerce
indicator transaction. When ECI is different in the request
and response of an authorization (in scenarios like
3DS downgrading), value in the response shall be
used.
For non-ecommerce transaction, this field is filled
with "00".
260~261 Card product ans2 60.3.10 I The value of this field is the same as the value of
Field 60.3.10 in original authorization
transactions.
262~263 Account ans2 60.3.8 I The value of this field is the same as the value of
attribute Field 60.3.8 in original authorization transactions.
264 UnionPay ans1 I GSCS will fill this field to indicate whether the card
standard/ non- is a UnionPay Standard Card or Non-standard
standard card Card.
indicator
Valid values:
0- UnionPay non-standard card
1- UnionPay standard card
Acquirers must fill this field with a space when
submitting the presentment file.
265~266 B2B business n2 104(BB) I/O This field is filled with spaces by default.
type Tag01
For cross-border B2B payment and service, this
field is filled with the corresponding business
type. For valid values, please see the message
field definition of Field 104 Usage BB Tag 01 in the
Technical Specifications on Bankcard
Interoperability - Part II Online Message.
267 B2B payment n1 104(BB) I/O This field is filled with a space by default.
medium Tag02
For cross-border B2B payment and service, this

UPI CONFIDENTIAL 79
 Part III: File Interface

Position Definition Format Field I/O Description

field is filled with the corresponding Payment

Medium. For valid values, please see the
definition of Field 104 Usage BB Tag 02 in the
Technical Specifications on Bankcard
Interoperability - Part II Online Message.
268~269 Special pricing ans2 I This field is filled with spaces by default.
indicator
For white-listed Members or Merchants offered
special pricing, this field is filled with 01.

4.2.1.2 Block 1- Information of Exchange Rate Features

Table 37 Block 1- Exchange Rate Features Information

Position Definition Format Field I/O Description

1~3 Point of service entry mode n3 22 I/O It is the definition of Field 22 in the
Technical Specifications on Bankcard
Interoperability - Part II Online
Message.
4 Floor limit identifier an1 I If the transaction amount is not larger
than a specific amount, online
authorization is not compulsory. When
submitting settlement files, acceptors
may use value “1” for authorization
identifier. If not applicable, it should be
filled with the default value.
Valid values:
0- online authorization;
1- authorization waived
Note: It is unused currently. In the
settlement files sent from GSCS to
Members, this field is filled with the
default value of “0”.
5~6 Type of payment service an2 I/O Valid values for the 1st byte:
requested 0- Display of card;
1- Non-display of card;
2- Not given
If not applicable, the 1st byte shall be
filled with the default value of “0” or a
space.
In the settlement files sent from GSCS
to Members, the 1st byte shall be filled
with default value of “0’”.
The 2nd byte is filled with a space.
7~18 Amount, settlement n12 5 I

UPI CONFIDENTIAL 80
 Part III: File Interface

Position Definition Format Field I/O Description

19~21 Currency code, settlement an3 50 I It refers to the currency used in
settlement.
Note: UnionPay uses numeric currency
codes.
22~29 Conversion rate, settlement n8 9 I The first digit from the left indicates the
number of decimal places (allowed
values are 0~7). The segment from the
2nd to the 8th digits indicates the value
of the conversion rate and is right
justified with no decimal point.
For example, “71212345” indicates that
the conversion rate is “0.1212345”.
30~41 Amount, cardholder billing n12 6 I
42~44 Currency code, cardholder an3 51 I It is the code of the cardholder billing
billing currency.
45~52 Conversion rate, cardholder n8 10 I The first digit from the left indicates the
billing number of decimal places (allowed
values are 0~7). The segment from the
2nd to the 8th digits indicates the value
of the conversion rate and is right
justified with no decimal point.
For example, “71212345” indicates that
the conversion rate is “0.1212345”.
53~64 Net fee amount x+n11 I It is the net payable amount of
interchange reimbursement fee,
international service fee, and cross-
border transaction fee.
65~67 IRF billing currency an3 I For IRF collected by percentage of the
transaction volume (including capping
and floor limits, like POS), the currency
of IRF should be the same as the
settlement currency. Therefore, the
field of “IRF Billing Currency” should be
filled with the “Settlement Currency”.
For the fixed fee per transaction, the
currency of the IRF shall be the “IRF
Billing Currency”.
Note: If IRF is not applicable, this field
will be filled with “000”.
68~75 Exchange rate from RF billing n8 I For IRF collected by percentage of the
currency to settlement transaction volume (including capping
currency and floor limits, like POS), the currency
conversion is not necessary. The field of
“Exchange Rate from IRF Billing

UPI CONFIDENTIAL 81
 Part III: File Interface

Position Definition Format Field I/O Description

Currency to Settlement Currency”
should be filled with the fixed value of
“30001000”.
For the fixed fee per transaction, if the
currency of reimbursement fee for ATM
is USD, the exchange rate for USD/HKD
is 7.753, and the Member settles in
HKD, then the value of the field of
“Exchange Rate from IRF Billing
Currency to Settlement Currency”
should be “30007753”.
76~78 Abbreviation of international an3 I/O Valid values:
organization/corporation and VSA- Visa
foreign institutions MST- MasterCard
JCB- JCB
AME- American Express
DNC- Dinners Club
CUP- China UnionPay
JEC- Jetco
BCC- BOC Credit Card (International)
Ltd.
For international transactions,
Members can fill this field with spaces.
In the settlement files sent from GSCS
to Members, this Field is filled with
“CUP”.
79 Mainland China transaction an1 I For the Acquirer, “M” indicates the
indicator Issuer is from Mainland China, and “F”
indicates the Issuer is outside of
Mainland China. For the Issuer, “M”
indicates the Acquirer is from Mainland
China, and “F” indicates the Acquirer is
outside of Mainland China.
80~91 Amount, transaction fee x+n11 28 I It represents additional fee collected in
every transaction.
92~111 QRC voucher number ans20 125(QR) O In the file for refund transactions
Tag02 (TC101), the QRC voucher number shall
be filled if it can be obtained from the
Merchant.
It is optional to fill the QRC voucher
number in the presentment file.
112~118 Reserved an7 I/O Reserved for use

4.2.1.3 Block 2- IC Card Characteristic Information Based on UICS Debit/Credit Standards

For dual-message Acquirers and Issuers, Block 2 will not be present for QRC-based transactions. In the presentment

UPI CONFIDENTIAL 82
 Part III: File Interface

file for Consumer-presented QRC-based transactions, it is optional for Acquirer to present the value of Block 2.
It is optional for Acquirer to send the block2 in the outgoing file. GSCS will generate block 2 to Issuer if it is a chip
transaction, but the chip data in block2 may be filled with blank space if the Acquirer does not send the chip data to
GSCS.
Table 38 Block 2- IC Card Characteristic Information Based on UICS Debit/Credit Standards

Position Definition Format Field I/O Description

1~16 Applied cryptogram an16 Tag9F26 I/O It is represented with 16 visible hex characters
(0~9,A~F): the value of TC applies.
17~19 Point of service n3 22 I/O
entry mode
20~22 Application PAN n3 23 I/O If the Acquirer does not submit Field 23, GSCS
sequence number will automatically fill the field with blank. The
Issuer shall be able to proceed correctly.
23 Terminal entry an1 60.2.2 I/O Please refer to the definition in the Technical
capability Specifications on Bankcard Interoperability -
Part II Online Message for details.
24 IC Card condition an1 60.2.3 I/O It indicates magnetic stripe card transaction is
code permitted at the IC card terminal. Please refer to
the Technical Specifications on Bankcard
Interoperability for details.
25~30 Terminal capabilities an6 Tag9F33 I/ It is represented with 6 visible hex characters
O (0~9,A~F).
31~40 Terminal verification an10 Tag95 I/ It is represented with 10 visible hex characters
results O (0~9,A~F).
41~48 Unpredictable an8 Tag9F37 I/O It is represented with 8 visible hex characters
number (0~9,A~F).
49~56 Serial number of an8 Tag9F1E I/O
interface device
57~120 Issuing bank an64 Tag9F10 I/O It is represented with 64 visible hex characters
application data (0~9,A~F); the field should be left-justified with
trailing spaces if the length is less than 64.
121~124 Application an4 Tag9F36 I/O It is represented with 4 visible hex character
transaction counter (0~9,A~F).
125~128 Application an4 Tag82 I/O It is represented with 4 visible hex character
alternation (0~9,A~F).
characteristic

129~134 Transaction date n6 Tag9A I/O It is the date of terminal authorization, with the
format of “YYMMDD”.
135~137 Country code of the n3 Tag9F1A I/O
terminal
138~179 Script result of the an42 TagDF31 I/O It is represented with 42 visible hex characters
(0~9,A~F); the field should be left-justified with

UPI CONFIDENTIAL 83
 Part III: File Interface

Position Definition Format Field I/O Description

card Issuer trailing spaces if the length is less than 42.
180~181 Authorization an2 Tag8A I/O When the transaction code is 100/101/102, the
response code value is “00”.
182~183 Transaction n2 Tag9C I/O The value is the first two digits of Field 3
category (transaction handling code)
184~195 Authorized amount n12 Tag9F02 I/O This tag value must be provided by the terminal.
If the terminal is unable to provide this
information, it must be filled with zeros. The
minor unit depends on the currency code and
transaction type in the authorization
transaction.
196~198 Currency code, n3 Tag5F2A I/O It is a 3-digit significant figure. Please refer to
transaction transaction currency used for authorization.
199~200 Cipher text an2 Tag9F27 I/O It consists of 2 visible hex characters (0~9,A~F)
information data This field should be filled with spaces if cannot
be filled.
201~212 Other amount n12 Tag9F03 I/O It is a 12-digit significant figure. The number of
decimal places depends on the authorized
currency. This field should be filled with zeros if
cannot be filled.
213~218 Authentication an6 Tag9F34 I/O It consists of a 6 visible hex characters
method and result (0~9,A~F). This field should be filled with spaces
of the cardholder if cannot be filled.
219~220 Terminal category an2 Tag9F35 I/O It is a 2-digit significant figure; this field should
be filled with spaces if cannot be filled.
221~252 Dedicated an32 Tag84 I/O It consists of 32 visible hex characters (0~9,A~F).
document name The field should be left-justified with trailing
spaces if the length is less than 32.
253~256 Application version an4 Tag9F09 I/O It consists of 2 visible hex characters (0~9,A~F).
number
257~264 Transaction serial an8 Tag9F41 I/O The field should be left-justified with trailing
counter spaces if the length is less than 8.
265~294 Reserved ans30 I/O Reserved for use

4.2.1.4 Block 3- Supplementary Settlement Information

If a dual-message Issuer receives Token-related information in an online transaction, Block 3 will be present in the
settlement file (IFCYYMMDD??C).
If a dual-message Issuer chooses to receive the wallet ID (either SDWO Wallet ID or SRC DCF ID) in settlement files,
Block 3 will be present in SDWO transactions related to back-to-back purchase or be present in SRC transactions.
If a dual-message Acquirer chooses to receive the wallet ID (either SDWO Wallet ID or SRC DCF ID) in settlement files,
Block 3 will be present in SDWO transactions related to back-to-back purchase or be present in SRC transactions.
Also, the Acquirer can choose to submit Block 3 in presentment files (OFCYYMM5?D) (currently reserved).

UPI CONFIDENTIAL 84
 Part III: File Interface
If dual-message Acquirers/ Issuers choose to receive additional installment payment commission fee information,
Block 3 will be present in the settlement file (IFCYYMMDD??C).
If dual-message Issuers/Acquirers choose to receive the installment payment fee rate and additional installment
payment fee rate, Block 3 will be present in the incoming settlement files. For installment payment refund transaction,
dual-message Acquirers shall submit Block 3 in the outgoing files.
Table 39 Block 3- Supplementary Settlement Information

Position Definition Format Field I/O Description

1~19 Token n19 63(TK) I/O The field is left-justified with trailing spaces.
Tag02
For Payment Token transaction, the field is filled with
the same value in Field 63, Usage TK Tag 02.
For PAN-based transaction, the field is filled with
spaces.
20~27 Wallet ID an8 I/O This field is filled with spaces by default.
For SDWO transactions, this field is filled with the ID
of the Staged Digital Wallet Operator.
For SRC transactions, this field is filled with the DCF ID.
28~35 PF ID an8 I/O This field is filled with spaces by default.
For a PF transaction, this field is filled with PF ID.
36~47 Additional x+n11 I The first digit is “C” for crediting and “D” for debiting
installment the Cardholder’s account. The 2nd-11th digits indicate
payment the additional installment payment commission fee
commission fee which shall be paid to Issuer by the Acquirer side. The
currency of this commission fee shall be the
settlement currency of the Member.
For installment payment, the field is filled with the
additional installment payment commission fee.
For other transaction, the field is filled with space.
48~53 Installment n6 I/O This field is filled with spaces by default.
payment fee rate
For dual-message installment payment transaction,
this field will be filled with the installment payment
commission fee rate of Field 48 in the incoming file
distributed by GSCS.
For dual-message installment payment refund
transaction, this field shall be filled with the
installment payment commission fee rate of Field 48
in the outgoing file submitted by the Acquirer.
54~59 Additional n6 I/O This field is filled with spaces by default.
installment
For dual-message installment payment transaction,
payment fee rate
this field will be filled with the additional installment
payment commission fee rate of Field 48 in the
incoming file distributed by GSCS.
For dual-message installment payment refund
UPI CONFIDENTIAL 85
 Part III: File Interface

Position Definition Format Field I/O Description

transaction, this field shall be filled with the additional
installment payment commission fee rate of Field 48
in the outgoing file submitted by the Acquirer.
60~101 Reserved an42 I/O Reserved by UPI for future use on multi-clearing
service (pilot)
102~300 Reserved ans199 I/O Reserved for use

TC 900- Fund Settlement Record

It is used for GSCS to inform Members of the net and total amounts of dual-message transactions in the transaction
statistics files sent by GSCS. In a file, multiple records can be present in the case of multiple settlement currencies.
 Block 0- Funds Settlement Basic Information
Table 40 Block 0- Funds Settlement Basic Information

Position Definition Format Description

1~3 Transaction code n3 Valid value:
900- Fund settlement record
4~7 Block bitmap an4
8 Outgoing amount an1 It is a sign of the net balance of settlement amounts in the Outgoing
sign STF switched by GSCS.
Valid values:
D- Debit
C- Credit
9~24 Outgoing amount n16 It is the net balance of settlement amounts in the Outgoing STF
submitted by the Member (as an Acquirer) and switched by GSCS.
25 Outgoing fee sign an1 It is a sign of the net balance of service fees in the Outgoing STF
submitted by the Member (as an Acquirer) and switched by GSCS.
Valid values:
D- Debit
C- Credit
26~41 Outgoing fee n16 It is the net balance of service fees in the Outgoing STF submitted by
the Member (as an Acquirer) and switched by GSCS.
42 Incoming Amount an1 It is a sign of the net balance of settlement amounts in the Incoming
Sign STF switched by GSCS and distributed to the Member (as an Issuer).
Valid values:
D- Debit
C- Credit
43~58 Incoming Amount n16 It is the net balance of settlement amounts in the Incoming STF
switched by GSCS and distributed to the Member (as an Issuer).
59 Incoming Fee Sign an1 It is a sign of the net balance of service fees in the Incoming STF
switched by GSCS and distributed to the Member (as an Issuer).
Valid values:

UPI CONFIDENTIAL 86
 Part III: File Interface

Position Definition Format Description

D- Debit
C- Credit
60~75 Incoming Fee n16 It is the net balance of service fees in the Incoming STF switched by
GSCS.
The value of this field is an integer, padded with leading zeros. The
unit is 1/10000 of the minor unit of currency.
76 STF Amount Sign an1 It is a sign of the net balance of the settlement amounts in the STF
(including outgoing and incoming STFs) switched by GSCS.
Valid values:
D- Debit
C- Credit
77~92 STF Amount n16 It is the net balance of the settlement amounts in the STF (including
outgoing and incoming STFs) switched by GSCS.
The value of this field is an integer, padded with leading zeros. The
unit is 1/10000 of the minor unit of currency.
93 STF Fee Sign an1 It is a sign of the net balance of service fees in the STF (including
outgoing and incoming amounts) switched by GSCS.
Valid values:
D- Debit
C- Credit
94~109 STF Fee n16 It is the net balance of service fees in the STF switched by GSCS.
The value of this field is an integer, padded with leading zeros. The
unit is 1/10000 of the minor unit of currency.
110~119 Outgoing n10 Total number of transactions in the Outgoing STF submitted by the
Summary Member (as an Acquirer)
120~129 Incoming n10 Total number of transactions in the Incoming STF distributed to the
Summary Member (as an Issuer)
130~132 Currency code, an3 It is a 3-digit number, indicating the currency type in fund
settlement settlement
133~162 Reserved ans30 Reserved for use

TC 901/902 STF Statistics

It is used to inform Members of the volume and amount of transaction received or initiated by Members in the
transaction statistics files sent by GSCS. The statistics transaction code in the record format is used to indicate the
transaction category related to the statistics. The statistics record format (901, 902) in the transaction statistics file
may be present several times to indicate the statistics for multiple kinds of transactions.
 Block 0- Basic Statistic Information
Table 41 Block 0- Basic Statistic Information

UPI CONFIDENTIAL 87
 Part III: File Interface

Position Definition Format Description

1~3 Transaction code n3 Valid values:
901- Incoming STF statistics
902- Outgoing STF statistics
4~7 Block bitmap an4
8~10 Currency code, an3 It is a 3-digit number, indicating the currency type in fund
settlement settlement
11~13 Statistic transaction n3 Valid values:
code 100- Settlement
101- Online refund/ manual refund
102- Cash withdrawal through bank counter
14~23 Incoming/ outgoing n10 It is the number of transactions in the Outgoing STF or Incoming
summary STF switched by GSCS.
24~39 Amount, credit n16 It is the aggregated credit amount of this transaction.
The value of this field is an integer, padded with leading zeros.
The unit is 1/10000 of the minor unit of currency.
40~55 Amount, debit n16 It is the aggregated debit amount of this transaction.
The value of this field is an integer, padded with leading zeros.
The unit is 1/10000 of the minor unit of currency.
56~85 Reserved ans30 Reserved for use

Format of International Transaction Settlement File for Secondary Member

The following format applies to files named as “IFCYYMMDD99CB”. The file header record, the file body record, and
the file trailer record should be separated by carriage return/linefeed (0X0D,0X0A).
Table 42 Format of International Transaction Settlement File for Secondary Member

File Header Record Format

Seq. Position Format Definition Description
1 1~7 ans7 Reserved field 1 Filled with spaces
2 8~18 ans11 IIN Left-justified with trailing spaces if the length is less than
11.
3 19~26 n8 Settlement date Format: YYYYMMDD
4 27~269 ans243 Reserved field 2 Filled with spaces
File Body Record Format (Refer to Section 4.2.1 TC 100/101/102- Transaction Record)
File Trailer Record Format
Seq. Position Format Definition Description
1 1~7 ans7 Reserved field 1 Filled with all “Z”s
2 8~18 ans11 IIN Left-justified with trailing spaces
3 19~26 n8 Settlement date Format: YYYYMMDD

UPI CONFIDENTIAL 88
 Part III: File Interface

4 27~32 n6 Total number of Total number of records (including the header and the
records trailer)
5 33~50 n18 PAN HASH check value ∑ the absolute value of [CB PAN (digit 1~digit 10) + (digit
11~digit 19)]
12 51~68 n18 Settlement amount ∑ [the absolute value of (Amount, settlement) + the
HASH check value absolute value of (Fee)]
Note: The Amount, settlement and the Fee are recorded
in Block 1 Information of Exchange Rate Features.
6 69~269 ans201 Reserved field 2 Filled with spaces

Format of International Transaction Statistics File for Secondary Member

The following format applies to files named as “IFCYYMMDD99SB”. The file header record, the file body record, and
the file trailer record should be separated by carriage return/linefeed (0X0D,0X0A).
Table 43 Format of International Transaction Statistics File for Secondary Member

File Header Record Format

Seq. Position Format Definition Description
1 1~7 ans7 Reserved field 1 Filled with spaces
2 8~18 ans11 IIN Left-justified with trailing spaces if the length is less than
11.
3 19~26 n8 Settlement date Format: YYYYMMDD
4 27~162 ans136 Reserved field 2 Filled with spaces
File Body Record Format (Refer to Section 4.2.2 TC 900 and Section 4.2.3 TC 901)
File Trailer Record Format
Seq. Position Format Definition Description
1 1~7 ans7 Reserved field 1 Filled with all “Z”s
2 8~18 ans11 IIN Left-justified with trailing spaces
3 19~26 n8 Settlement date Format: YYYYMMDD
4 27~32 n6 Total number of Total number of records (including the header and the
records trailer)
5 33~50 n18 Reserved Filled with spaces
12 51~68 n18 Reserved Filled with spaces
6 69~162 ans94 Reserved field 2 Filled with spaces

UPI CONFIDENTIAL 89
 Part III: File Interface

5 IC Card Information File

5.1 Overview of IC Card Information File
Function of IC Card Information File
Data recorded in IC card information files include:
 Data of failed offline IC card transactions based on UICS Debit/Credit standards, recorded in information files
which are represented by Block 0, Block 1, and Block 2 characteristic segment in the file format;
 Data of IC card transactions based on UICS Debit/Credit standards, recorded in information files represented by
Block 0, Block 1, and Block 2 characteristic segment in the file format; and the transactions are successful but
the ARPC verification result is wrong.
Each file record shall be completed with a carriage return/linefeed.
IC card information files are only used for reference of risk information and independent of settlement.

Naming Rules for IC Card Information File

IC card information files submitted by Members:
Table 44 Naming Rules For IC Card Information File Submitted by Members

File Name Value of Position 1~11 Value of Position 12 Record Type Included in File
Outgoing IC card Valid value for Position Valid values for TC 000 File Header Record;
information file 1~11: Position 12:
TC 100/101/300/301 Transaction
OFIYYMMDD??, where ?? E- Information files
Record Based on Domestic UICS
stands for the file batch supporting UICS
Debit/Credit Standards;
number debit/credit standards
TC 001 File Trailer Record
IC card information files distributed by GSCS:
Table 45 Naming Rules For IC Card Information File Distributed by GSCS

File Name Value of Position 1~11 Value of Position Record Type Included in File
12/12~13
Incoming IC card Valid value for Position Valid values for TC 000 File Header Record;
information file 1~11: Position 12:
TC 100/101/300/301 Transaction
IFIYYMMDD??, where ?? E- Information files
Record Based on Domestic UICS
stands for the file batch supporting UICS
Debit/Credit Standards;
number debit/credit standards
TC 001 File Trailer Record

IC Card Information File Processing

UPI CONFIDENTIAL 90
 Part III: File Interface

Acquirer 1 GSCS 2 Issuer

Figure 15 IC Card Information File Processing

1. GSCS receives directly-forwarded files sent by Acquirer, including: OFIYYMMDD??E.

2. GSCS sends the received files to the corresponding Issuer, including: IFIYYMMDD??E.

File List and Access Mode of IC Card Information File

Table 46 File List and Access Mode of IC Card Information File

File Name Description File Access Mode

(Y: Allowed;
N: Not Allowed)
Flow SFTP
Transmission
OFIYYMMDD??E Information files for domestic IC cards based on UICS Y Y
Debit/Credit Standards sent to UPI by the Member
IFIYYMMDD??E Information files for domestic IC cards based on UICS Y Y
Debit/Credit Standards sent to the Member by UPI

5.2 Format of IC Card Information File

TC 100/101/300/301- Transaction Record Based on Domestic UICS Debit/Credit
Standards
5.2.1.1 Block 0- Basic Characteristic Information
Please refer to Section 4.2.1.1 Block 0- Basic Settlement Information for details.
5.2.1.2 Block 1- Exchange Rate Characteristic Information
Please refer to Section 4.2.1.2 Block 1- Information of Exchange Rate Features for details.
5.2.1.3 Block 2- Advice Characteristic Information of IC Card Based on UICS Debit/Credit Standards
This characteristics segment is only used:
1. To inform the Issuer of UICS Debit/Credit characteristics information in the failed offline transaction;
2. To inform the Issuer of UICS Debit/Credit characteristics information in the offline transaction, which are
successful but the ARPC verification result is wrong.
Table 47 Block 2- Advice Characteristic Information of IC Card Based on UICS Debit/Credit Standards

UPI CONFIDENTIAL 91
 Part III: File Interface

Position Definition Format Field I/O Description

1 Applied cryptogram n1 I/O Valid values:
type 1- AAC, indicating the application authentication
cryptogram generated when offline transaction
fails;
2- ARPC, only indicating the situation where the
ARPC is wrong but the transaction is still
approved
2~17 Applied cryptogram an16 Tag9F26 I/O It only indicates the value of ACC, represented
with 16 visible hex characters (0-9, A-F).
The field is filled with spaces if the Applied
Cryptogram Type is 2.
18~20 Point of service n3 22 I/O
entry mode
21~23 Application PAN n3 23 I/O If the Acquirer does not submit Field 23, GSCS
sequence number will automatically fill the field with blank. The
Issuer shall be able to proceed correctly.
24~25 Authorization an2 Tag8A I/O Valid values for applied cryptogram type being
response code 1:
Z1- The offline transaction fails;
Z3- The transaction is unable to be processed
online, and the offline transaction fails.
Valid values for applied cryptogram type being
2:
05- The ARPC verification result is wrong but the
transaction is still approved.
26~41 Authorization an16 Tag91 I/O If the Applied Cryptogram Type is 1, this field
Response shall be filled with spaces.
Cryptogram (ARPC)
If the Applied Cryptogram Type is 2 (indicating
that the ARPC verification result is wrong but the
transaction is still approved), this field shall be
filled with 16 visible hex (0-9, A-F), indicating the
Authorization Response Cryptogram calculated
by the Issuer and received by card.
42 Card ARPC an1 I/O Valid value for the applied cryptogram type
verification result being 2:
2- Failure
Filled with a space for the Applied Cryptogram
Type being 1
43 Terminal entry an1 60.2.2 I/O Please refer to the definition in the Technical
capability Specifications on Bankcard Interoperability - Part
II Online Message for details.
44 IC Card condition an1 60.2.3 I/O It indicates magnetic stripe card transaction is
code permitted at the IC card terminal. Please refer to
the Technical Specifications on Bankcard

UPI CONFIDENTIAL 92
 Part III: File Interface

Position Definition Format Field I/O Description

Interoperability for details.
45~50 Terminal an6 Tag9F33 I/O If the Applied Cryptogram Type is 1(means offline
capabilities transaction), this field shall be filled with 6 visible
hex characters (0~9,A~F).
If the Applied Cryptogram Type is 2, this field
shall be filled with spaces
51~60 Terminal an10 Tag95 I/O If the Applied Cryptogram Type is 1(means offline
verification results transaction), this field shall be filled with 10
visible hex characters (0~9,A~F)
If the Applied Cryptogram Type is 2, this field
shall be filled with spaces
61~69 Unpredictable an8 Tag9F37 I/O If the Applied Cryptogram Type is 1(means offline
number transaction) this field shall be filled with 8 visible
hex characters (0~9,A~F).
If the Applied Cryptogram Type is 2, this field
shall be filled with spaces.
69~76 Serial number of an8 Tag9F1E I/O If the Applied Cryptogram Type is 2, this field
interface device shall be filled with spaces.
77~140 Issuing bank an64 Tag9F10 I/O This field is filled with 64 visible hex characters
application data (0~9,A~F); the field shall be left-justified with
trailing spaces if the length is less than 64 digits.
141~144 Application an4 Tag9F36 I/O If the Applied Cryptogram Type is 1(means offline
transaction counter transaction), this field shall be filled with 4 visible
hex characters (0~9,A~F);
If the Applied Cryptogram Type is 2, this field
shall be filled with spaces.
145~148 Application an4 Tag82 I/O If the Applied Cryptogram Type is 1(means offline
alternation transaction), this field shall be filled with 4 visible
characteristic hex characters (0~9,A~F);
If the Applied Cryptogram Type is 2, this field
shall be filled with spaces.
149~160 Other amount n12 Tag9F03 I/O If the Applied Cryptogram Type is 2, this field
shall be filled with zeros.
161~166 Transaction date n6 Tag9A I/O It is the date of terminal authorization, with the
format of “YYMMDD”.
167~169 Country code of n3 Tag9F1A I/O
the terminal
170~171 Transaction n2 Tag9C I/O The value is the first two digits of Field 3
category (transaction handling code)
172~183 Authorized amount n12 Tag9F02 I/O This tag value must be provided by the terminal.
If the terminal is unable to provide this

UPI CONFIDENTIAL 93
 Part III: File Interface

Position Definition Format Field I/O Description

information, it must be filled with zeros. The
minor unit depends on the currency code and
transaction type in the authorization transaction.
184~186 Currency code, n3 Tag5F2A I/O It is a 3-digit significant figure. Please refer to
transaction transaction currency used for authorization.
187~188 Cipher text an2 Tag9F27 I/O It consists of 2 visible hex characters (0~9,A~F).
information data This field should be filled with spaces if cannot be
filled.
189~194 Authentication an6 Tag9F34 I/O It consists of a 6 visible hex characters (0~9,A~F).
method and result This field should be filled with spaces if cannot be
of the cardholder filled.
195~196 Terminal category an2 Tag9F35 I/O It is a 2-digit significant figure; this field should be
filled with spaces if cannot be filled.
197~228 Dedicated an32 Tag84 I/O It consists of 32 visible hex characters (0~9,A~F).
document name The field should be left-justified with trailing
spaces if the length is less than 32.
229~232 Application version an4 Tag9F09 I/O It consists of 2 visible hex characters (0~9,A~F).
number
233~240 Transaction serial an8 Tag9F41 I/O The field should be left-justified with trailing
counter spaces if the length is less than 8.
241~270 Reserved ans30 I/O Reserved for use

UPI CONFIDENTIAL 94
 Part III: File Interface

6 IC Card Offline Purchase File

6.1 Overview of IC Card Offline Purchase File
Function of IC Card Offline Purchase File
IC card offline purchase files (the abbreviation of offline purchase file for IC Card Based on Debit/Credit Application
and E-cash Application of UICS Debit/Credit Standards) include those sent by Members to GSCS and those sent by
GSCS after settlement to Members, covering offline purchase transactions based on debit/credit application and E-
cash application. Among the two types of files, the former is used for settlement between GSCS and the Member,
and the latter is used for Member reconciliation.
International IC card offline purchase file consists of Block 0, Block 1, and Block 2.

Naming Rules for IC Card Offline Purchase File

IC card offline purchase files submitted by Members:
Table 48 Naming Rules For IC Card Offline Purchase File Submitted by Members

File Name Value of Position 1~11 Value of Position 12 Record Type

Included in File
Outgoing IC card Valid value for Position 1~11: Valid values for Position TC 000 File Header
offline purchase OFFYYMMDD??, where ?? stands 12: Record;
file for the sending member: 51 for the C- Information files
TC 300/301 Offline
Acquirer. supporting UICS
Transaction Record;
debit/credit standards
TC 001 File Trailer
Record
IC card offline purchase files distributed by GSCS:
Table 49 Naming Rules For IC Card Offline Purchase File Distributed by GSCS

File Name Value of Position 1~11 Value of Position 12/12~13 Record Type
Included in File
Incoming IC card Valid value for Position 1~11: Valid values for Position TC 000 File Header;
offline purchase IFFYYMMDD??, where ?? stands 12:
TC 002 Reject
reject file for the receiving member: 51 for R- Reject file
Record;
the Acquirer and 99 for the Issuer
TC 003 Error File
Record;
TC 001 File Trailer
Incoming IC card Valid value for Position 1~11: Valid values for Position TC 000 File Header
offline purchase IFFYYMMDD??, where ?? stands 12/12~13/12~15: Record;
settlement file for the receiving member: 51 for C- Offline transaction
TC 300/301 Offline
the Acquirer and 99 for the Issuer settlement file
Transaction
CB- Offline transaction
Record;
settlement file for
secondary member TC 001 File Trailer
CPOS- Direct-connected Record
POS offline transaction
settlement file

UPI CONFIDENTIAL 95
 Part III: File Interface

File Name Value of Position 1~11 Value of Position 12/12~13 Record Type
Included in File
Incoming IC card Valid value for Position 1~11: Valid values for Position TC 000 File Header;
offline purchase IFFYYMMDD??, where ?? stands 12/12~13/12~15:
TC 900 Fund
statistic file for the receiving member: 51 for S- Offline transaction
Settlement Record;
the Acquirer and 99 for the Issuer statistic file
SB- Offline transaction TC 901 Incoming
statistic file for secondary Offline Transaction
member Statistics;
SPOS- Direct-connected
TC 902 Outgoing
POS offline transaction
Offline Transaction
statistic file
Statistics;
TC 001 File Trailer

IC Card Offline Purchase File Processing

Within a settlement day, Members could send IC card offline purchase files to GSCS in multiple batches. For files sent
after GSCS cutoff, even if the settlement date is the last business day, GSCS will do settlement for the Member
according to its current settlement date. After cutoff, GSCS generates IC card offline purchase files of the last
settlement day and sends the files to each Member.
For dual message files in multiple clearing batches, Members could submit one or more IC card offline settlement
files in each batch; the batch number in the file name is the file sequence number, and such files submitted by
Members within one settlement day cannot share the same file name. No matter how many IC card offline purchase
files are sent by Members in a batch, GSCS only generates one reject file for each batch. If there is no rejection record
in the file, a reject file with a file head and a file end but without any file record will be sent. If no IC card offline
purchase file is submitted by the Member on the day when its IC card offline purchase business goes live, GSCS will
generate and send a feedback file with a file head and a file end but without any file record to the Member.
IC card offline transactions could be accepted and approved on terminals since they are special. If the terminal fails
to send the transaction information, neither the Acquirer nor the Issuer will have the transaction record. In order to
keep accounts in balance (no deficit or surplus), both the Acquirer and the Issuer shall provide transaction details.
Therefore, Acquirers and Issuers shall support this kind of IC card offline purchase file, regardless of the single
message system or the dual message system.

Acquirer GSCS Issuer

2 3

Figure 16 IC Card Offline Purchase File Processing

1. GSCS receives the IC card offline purchase file sent by the Acquirer, including the international transaction
settlement file (OFFYYMMDD51C).

UPI CONFIDENTIAL 96
 Part III: File Interface
2. After settlement, GSCS sends the generated IC card offline purchase file of international transactions to the
Acquirer, including the international reject file (IFFYYMMDD51R), the successful settlement file
(IFFYYMMDD51C/CPOS for directly-connected Acquirers only), and the statistics file (IFFYYMMDD51S/SPOS for
directly-connected Acquirers only).
3. After settlement, GSCS sends the generated IC card offline purchase file of international transactions to Issuer,
including the general transaction settlement file (IFFYYMMDD99C/CB) and the transaction statistics file
(IFFYYMMDD99S/SB).

File List and Access Mode of IC Card Offline Purchase File

Table 50 File List and Access Mode of IC Card Offline Purchase File

File Name Description File Access Mode

(Y: Allowed;
N: Not Allowed)
Flow SFTP
Transmission
OFFYYMMDD51C International IC card offline purchase file sent by the Acquirer Y Y
to UPI
IFFYYMMDD51R International IC card offline transaction reject file sent by UPI Y Y
to the Acquirer
IFFYYMMDD51C International IC card offline transaction settlement file sent Y Y
by UPI to the Acquirer
IFFYYMMDD51CPOS International IC card offline transaction settlement file sent Y Y
by UPI to the directly-connected Acquirer
IFFYYMMDD51S International IC card offline transaction statistics file sent by Y Y
UPI to the Acquirer
IFFYYMMDD51SPOS International IC card offline transaction statistics file sent by
UPI to the directly-connected Acquirer
IFFYYMMDD99C International IC card offline transaction settlement file sent Y Y
by UPI to the Issuer
IFFYYMMDD99S International IC card offline transaction settlement file sent Y Y
by UPI to the Issuer
IFFYYMMDD99CB International IC card offline transaction settlement file sent Y Y
by UPI to the secondary Issuer
IFFYYMMDD99SB International IC card offline transaction settlement file sent Y Y
by UPI to the secondary Issuer

6.2 Format of IC Card Offline Purchase File

TC 300/301- Offline Transaction Record
6.2.1.1 Block 0- Basic Settlement Information
Please refer to the format definition in Section 4.2.1.1. Please note that only Transaction Code 300 and 301 are
included in this file.

UPI CONFIDENTIAL 97
 Part III: File Interface

6.2.1.2 Block 1- Exchange Rate Feature Information

Please refer to format definition in Section 4.2.1.2. Please note that only Transaction Code 300 and 301 are included
in this file.
6.2.1.3 Block 2- Feature Information of IC Card based on UICS Debit/Credit Standards
The block shall be present for e-cash offline purchase and offline refund. Otherwise, the transaction will be rejected
for clearing with the response code of F1 in the rejection file. The terminal shall send the information obtained based
on the following requirements for the block and use the default value for the other information that cannot be
captured.
The terminal must send the data used to generate the TC (authorization amount, other amount, terminal country
code, terminal verification result (TVR), transaction currency code, transaction date, transaction type, random
number, application interchange profile (AIP), application transaction counter (ATC), card verification result (CVR),
card expiration date, and card sequence number).
Table 51 Block 2- Feature Information of IC Card based on UICS Debit/Credit Standards

Position Definition Format Field I/O Description

1~16 Applied cryptogram an16 Tag9F26 I/O It is represented with 16 visible hex characters
(0~9,A~F): the value of TC applies.
17~19 Point of service n3 22 I/O The value of this field, together with the values
entry mode of Field 60.2.2 and Field 60.2.3, is used to
indicate the transaction medium. Block 2 can
only be present when the transaction medium is
an IC card. It shall not be present in other cases.
If Block 2 is present but the transaction medium
is not an IC card, this transaction will not be
settled and the response code in the reject file
will be “F4”.
20~22 Application PAN n3 23 I/O If the Acquirer does not submit Field 23, GSCS
sequence number will automatically fill the field with blank. The
Issuer shall be able to proceed correctly.
23 Terminal entry an1 60.2.2 I/O Please refer to the definition in the Technical
capability Specifications on Bankcard Interoperability - Part
II Online Message for details.
For offline transactions, when the first two digits
of Field 22 are “05” or “95”, the value of Field
60.2.2 shall be “5” or “6”. Otherwise, this record
will be rejected with the code of “F4”. When the
first two digits of Field 22 are “07” or “98”, the
value of Field 60.2.2 shall be “6”. Otherwise, this
record will be rejected with the code of “F4”.
24 IC Card condition an1 60.2.3 I/O It indicates magnetic stripe card transaction is
code permitted at the IC card terminal. Please refer to
the Technical Specifications on Bankcard
Interoperability for details.
25~30 Terminal an6 Tag9F33 I/ It is represented with 6 visible hex characters
capabilities O (0~9,A~F).

UPI CONFIDENTIAL 98
 Part III: File Interface

Position Definition Format Field I/O Description

31~40 Terminal an10 Tag95 I/ It is represented with 10 visible hex characters
verification results O (0~9,A~F).
41~48 Unpredictable an8 Tag9F37 I/O It is represented with 8 visible hex characters
number (0~9,A~F).
49~56 Serial number of an8 Tag9F1E I/O
interface device
57~120 Issuing bank an64 Tag9F10 I/O It is represented with 64 visible hex characters
application data (0~9,A~F); the field should be left-justified with
trailing spaces if the length is less than 64.
121~124 Application an4 Tag9F36 I/O It is represented with 4 visible hex character
transaction counter (0~9,A~F).
125~128 Application an4 Tag82 I/O It is represented with 4 visible hex character
alternation (0~9,A~F).
characteristic

129~134 Transaction date n6 Tag9A I/O It is the date of terminal authorization, with the
format of “YYMMDD”.
135~137 Country code of the n3 Tag9F1A I/O
terminal
138~139 Authorization an2 Tag8A I/O Valid values:
response code Y1- Successful offline transaction
Y3- Cannot be processed online, successful
offline transaction
140~141 Transaction n2 Tag9C I/O The value is the first two digits of Field 3
category (transaction handling code)
142~153 Authorized amount n12 Tag9F02 I/O This tag value must be provided by the terminal.
If the terminal is unable to provide this
information, it must be filled with zeros. The
minor unit depends on the currency code and
transaction type in the authorization transaction.
154~156 Currency code, n3 Tag5F2A I/O It is a 3-digit significant figure. Please refer to
transaction transaction currency used for authorization.
157 Account an1 I This field will be filled with the following values
cryptogram when the file receiver has no ability to verify the
verification result applied cryptogram (only for TC) or asks the
switching center to verify the applied cryptogram
(only for TC).
Valid values:
1- Successful
2- Failed
3- Unauthorized
158~161 Reserved ans4 I/O Filled with spaces

UPI CONFIDENTIAL 99
 Part III: File Interface

Position Definition Format Field I/O Description

162~163 Cryptogram an2 Tag9F27 I/O It consists of 2 visible hex characters (0~9,A~F)
information data This field should be filled with spaces if cannot be
filled.
164~175 Other amount n12 Tag9F03 I/O It is a 12-digit significant figure. The number of
decimal places depends on the authorized
currency. This field should be filled with zeros if
cannot be filled.
176~181 Cardholder an6 Tag9F34 I/O It consists of a 6 visible hex characters (0~9,A~F).
verification method This field should be filled with spaces if cannot be
result filled.
182~183 Terminal category an2 Tag9F35 I/O It is a 2-digit significant figure; this field should
be filled with spaces if cannot be filled.
184~215 Dedicated an32 Tag84 I/O It consists of 32 visible hex characters (0~9,A~F).
document name The field should be left-justified with trailing
spaces if the length is less than 32.
216~219 Application version an4 Tag9F09 I/O It consists of 2 visible hex characters (0~9,A~F).
number
220~227 Transaction serial an8 Tag9F41 I/O The field should be left-justified with trailing
counter spaces if the length is less than 8.
228~251 Card product an24 Tag9F63 I/O ASCII code has 24 bytes.
identifier
The segment from the 1st to 8th bytes in ASCII
represents for IIN, while the 9th to 24th bytes,
corresponding to the 9th and 16th byte of the
tag value, represents for the card type and the
fee distribution mode.
Note: The first 8 bytes are the same as the first 8
bytes of the 9F63 tag value in the online
message. The following 16 bytes are the results
of extending the last 8 bytes of the 9F63 tag
value in the online message to characters.
Currently, this tag is only valid in E-cash
application. It shall be filled with spaces in
debit/credit application.
252~254 Original transaction n3 I/O For single currency e-cash, the currency
currency of e-cash conversion between the billing currency and the
cross-border offline transaction currency is implemented like this: the
transactions currency conversion is conducted at the terminal;
the transaction amount (Field 49) will be based
on the e-cash billing currency; the actual
transaction currency will depend on this field.
255~266 Original transaction n12 I/O For single currency e-cash, the currency
amount of e-cash conversion between the billing currency and the
cross-border offline transaction currency is implemented like this: the
currency conversion is conducted at the terminal;

UPI CONFIDENTIAL 100

 Part III: File Interface

Position Definition Format Field I/O Description

transactions the transaction amount (Field 49) is based on the
e-cash billing currency; the actual transaction
currency depends on this field.
267~274 Exchange rate used n8 I/O It is the exchange rate used at the terminal for
at terminal for currency conversion in single currency e-cash
cross-currency e- cross-border transactions.
cash offline
transactions
275~324 Reserved ans50 I/O Filled with spaces

TC 900- Fund Settlement Record

In transaction statistics files sent by GSCS, it is used to inform Member of net and total amounts of IC card offline
purchase transactions. In a file, multiple records can be present in the case of multiple settlement currencies.
 Block 0- Funds Settlement Basic Information
Table 52 Block 0- Funds Settlement Basic Information

Position Definition Format Description

1~3 Transaction code n3 Valid value:
900- Fund settlement record
4~7 Block bitmap an4
8 Outgoing amount an1 It is a sign of the net balance of settlement amounts in the outgoing
sign IC card offline transactions submitted by the Member (as an
Acquirer) and switched by GSCS.
Valid values:
D- Debit
C- Credit
9~24 Outgoing amount n16 It is the net balance of settlement amounts in the outgoing IC card
offline transactions submitted by the Member (as an Acquirer) and
switched by GSCS.
25 Outgoing fee sign an1 It is a sign of the net balance of service fees in the outgoing IC card
offline transactions submitted by the Member (as an Acquirer) and
switched by GSCS.
Valid values:
D- Debit
C- Credit
26~41 Outgoing fee n16 It is the net balance of service fees in the outgoing IC card offline
transactions submitted by the Member (as an Acquirer) and
switched by GSCS.
42 Incoming amount an1 It is a sign of the net balance of settlement amounts in the
sign Incoming IC card offline transactions switched by GSCS and
distributed to the Member (as an Issuer).
Valid values:

UPI CONFIDENTIAL 101

 Part III: File Interface

Position Definition Format Description

D- Debit
C- Credit
43~58 Incoming amount n16 It is the net balance of settlement amounts in the incoming IC card
offline transactions switched by GSCS and distributed to the
Member (as an Issuer).
59 Incoming fee sign an1 It is a sign of the net balance of service fees in the incoming IC card
offline transactions switched by GSCS and distributed to the
Member (as an Issuer).
Valid values:
D- Debit
C- Credit
60~75 Incoming fee n16 It is the net balance of service fees in the incoming IC card offline
transactions switched by GSCS and distributed to the Member (as
an Issuer).
76 Offline transaction an1 It is a sign of the net settlement amount of IC card offline
amount sign transactions (including incoming and outgoing) switched by GSCS.
Valid values:
D- Debit
C- Credit
77~92 Offline transaction n16 Value of net settlement amount in IC card offline transactions
amount (including incoming and outgoing) switched by GSCS
93 Offline transaction an1 Sign of net service fee in IC card offline transactions (including
fee sign incoming and outgoing) switched by GSCS.
Valid values:
D- Debit
C- Credit
94~109 Offline transaction n16 It is the net balance of service fee in IC card offline transaction
fee (including incoming and outgoing) switched by GSCS.
110~119 Outgoing n10 Total number of transactions in the outgoing IC card offline
summary transactions.
120~129 Incoming n10 Total number of transactions in the incoming IC card offline
summary transactions.
130~132 Currency code, an3 It is a 3-digit number, indicating the currency type in fund
settlement settlement
133~162 Reserved ans30 Reserved for use

TC 901/902 Offline Transaction Statistics

In transaction statistics files sent by GSCS, it is used to inform a Member of the count and amount of transaction
received or initiated by the Member. The statistics transaction code in the record format is used to indicate the
transaction type used in this statistics. In transaction statistics files, statistics record formats (901, 902) could appear
multiple times, which is applicable to statistics for multiple types of transactions.

UPI CONFIDENTIAL 102

 Part III: File Interface

 Block 0- Basic Statistic Information

Table 53 Block 0- Basic Statistic Information

Position Definition Format Description

1~3 Transaction code n3 Valid values:
901- Incoming offline transaction statistics
902- Outgoing offline transaction statistics
4~7 Block bitmap an4
8~10 Currency code, an3 It is a 3-digit number, indicating the currency type in fund
settlement settlement
11~13 Statistic transaction n3 Valid values:
code 300- Offline purchase with IC cards based on UICS Debit/Credit
Standards (including offline purchase of small amount)
301- Offline refund of UICS debit/credit application
14~23 Incoming/ outgoing n10 Count of outgoing or incoming IC card offline transactions
summary switched by GSCS
24~39 Amount, credit n16 It is the aggregated credit amount of this transaction.
The value of this field is an integer, padded with leading zeros. The
unit is 1/10000 of the minor unit of currency.
40~55 Amount, debit n16 It is the aggregated debit amount of this transaction.
The value of this field is an integer, padded with leading zeros. The
unit is 1/10000 of the minor unit of currency.
56~85 Reserved ans30 Reserved for use

UPI CONFIDENTIAL 103

 Part III: File Interface

7 Report File
7.1 Overview of Report File
Function of Report File
All types of reports are used for UPI and Members to evaluate and analyze the operation situations. Every report file
only contains one report. The format and content of the report are defined as follows.

Naming Rules for Report File

Table 54 Naming Rules for Report File

Position Definition Description

1 Direction tag Valid values:
I- Incoming, the file is sent from GSCS to Members
O- Outgoing, the file is sent from Members to GSCS
2 Card classifying tag Valid value:
F- RMB cross-border transaction
3 File type Valid values:
D- Audit trailer (detail)
C- Dual-message settlement file
R- Report file
4~9 File date Format: YYMMDD
10~11 Batch number/ Valid values:
sequence number 00~99
12 Business type Valid value:
C- Settlement
13~15 Report serial It is used to distinguish the details of each file. It could be present or absent,
number depending on the features of each file. Currently it is used just in some of
report files and risk files.
16 Frequency tag Valid values:
D- Daily
M- Monthly
17 Receiving Valid value:
institution tag Z- Member
18 Secondary member Valid values:
tag B- Report for secondary member
Not present if the file is not for secondary member.

Report File Processing

UPI CONFIDENTIAL 104

 Part III: File Interface

GSCS Member

Figure 17 Report File Processing

After creating the report files, GSCS distributes them to Members.

7.2 Format of Report

C602DZ- UPI Institution Net Settlement Summary
This report is a daily report. For Issuers, the report name is IFRYYMMDD01C602DZ-XXX (Billing currency code)-XXX
(Settlement currency code), For Acquirers, the report name is IFRYYMMDD01C602DZ-XXX (Transaction currency
code)-XXX (Settlement currency code).
For the purpose of reconciliation and calculation, the computational accuracy is changed from the minimum accuracy
of the currency to 1/10000 of the minimum accuracy of the currency (the computational accuracy applicable to the
Stand-in Fee Daily Report remains the same as the accuracy of the currency).
 Report Header
The report header includes the following information:
 IIN
 Institution Name
 Transaction Settlement Date
 Report Date
 Transaction Currency (billing currency for issuer and transaction currency for the acquirer)
 Settlement Currency
 Daily Sub-reports
UPI Institution Net Settlement Summary Reports include four daily sub-reports:
Table 55 C602DZ Classifications

Report ID Definition Description

C602DZ-001 UPI Institution Settlement The sum of the settlement amount, reimbursement fee, service
(mandatory) Summary Report (Daily fee, additional fee and net settlement amount,
Report)
Debit amount, credit amount, and total amount
C602DZ-002 UPI Institution Settlement Transaction count, transaction amount, settlement amount,
(mandatory) Fee Report (Daily Report) interchange reimbursement fee, service fee, net settlement
amount, and information summarized by transaction type.

UPI CONFIDENTIAL 105

 Part III: File Interface

Report ID Definition Description

Note: Acquirers are classified as directly-connected and indirectly-
connected types.
C602DZ-003 UPI Institution Settlement Transaction count, transaction amount, settlement amount,
(mandatory) Dispute Fee Report (Daily interchange reimbursement fee, service fee, net settlement
Report) amount, and information summarized by dispute transaction type.
C602DZ-004 UPI Institution Settlement It contains the transaction count and the additional fee
(optional) Stand-in Fee Report information summarized by stand-in transaction type. The
(Daily Report) settlement count of the stand-in fee report is involved in C602-DZ-
001.
These reports include all fees that are settled in a given settlement service. Fees are reported by the following
categories:
 Business mode
 Transaction type
Note: The service fees in the report refer to the total service fee including international service fee and cross-border
transaction fee.
 Machine-readable Formats
Table 56 C602DZ-001/002/003 Report Format

Position Format Alignment Definition

1-13 an13 Left-alignment Institution Role
14-49 an36 Left-alignment Transaction Type
50-66 un17 Right-alignment Settlement Count
67-90 an24 Right-alignment Transaction Amount
91-111 an21 Right-alignment Settlement Amount
112-132 an21 Right-alignment Reimbursement Fee
133-153 an21 Right-alignment Service Fee
154-174 an21 Right-alignment Additional Fee
175-197 an23 Right-alignment Net Settlement Amount
Note: Format “an” stands for alphanumeric, while format “un” stands for unpacked numeric.

Table 57 C602DZ-004 Report Format

Position Format Alignment Definition

1-36 an36 Left-alignment Transaction Type
37-49 an13 Left-alignment Institution Role
50-66 un17 Right-alignment Settlement Count
67-89 an21 Right-alignment Additional Fee
Note: Format “an” stands for alphanumeric, while format “un” stands for unpacked numeric.

UPI CONFIDENTIAL 106

 Part III: File Interface

 Sample
For report samples, please refer to Section C.1 of the Technical Specifications on Bankcard Interoperability - Part VI
Annex.

C603DZ- UPI Net Settlement Summary

This report is a daily report, For Issuers, the report name is IFRYYMMDD01C603DZ-XXX (Billing currency code)-XXX
(Settlement currency code), For Acquirers, the report name is IFRYYMMDD01C603DZ-XXX (Transaction currency
code)-XXX (Settlement currency code). “Transaction Currency” in the report refers to billing currency for Issuers and
transaction currency for the Acquirers.

C603DZN- UPI Net Settlement Summary (New) – UPI Internal Use Only
This report is for UPI internal use only.
Table 58 Net Settlement Files Report (New)
SECT1
Note: Details of “SECT” will be specified in the following “Section Illustration” part.
STAC1
Note: Details of “SECT” will be specified in the following “Block Illustration” part.
TROL MSTP PCOD PSCC AMOT SCOD TRAF
Note: It will be given based on real transactions. Only real transactions will be represented in random
sequence. Please refer to “Role Clarification” and “Statistic Items” for “TROL” and details of each item.
STAC2
……
STAC3
……
----20-----**********-----) Every SECT shall end with this stop legend. It belongs to the same level of SECT, format fixed.

 Section Illustration
Each section is in the TVL form, with “SECT” tag. The value of its length depends on the tag length, ranging from 01
to 99. The value of each section shall be determined on a case-by-case basis. Altogether 99 statistic items from 01 to
99 could be defined with their values present in the following format:
Table 59 Section Illustration

Tag Name Tag Definition Length Value /V

/Acronym Name /L
/T
SECT(section) Card It indicates the items 01-99 Valid value:
Type that should be 01 Bank Card.
calculated.
Note: Every value shall be ended by full
stop mark “.”, every two words shall be
separated by a space.
 Block Illustration
Within the same section, each statistic item corresponds to several statistic blocks, and statistic blocks appear one

UPI CONFIDENTIAL 107

 Part III: File Interface
after another by serial number. Namely, all the statistics files received by all Members consist of the same statistic
blocks; some need to be analyzed, some don't. Members decide which statistic block need to be analyzed according
to the serial number.
Each block is in the TVL form, with “STAC” tag. The value of its length is calculated by the tag length, ranging from 01
to 99. The value of each section shall be determined on a case-by-case basis. Altogether 99 statistic items from 01 to
99 could be defined with their values present in the following format:
Table 60 Block Illustration

Tag Name Tag Name Definition Length Value /V

/Acronym /T /L
STAC(statistics) Statistic It indicates the item 01-99 Valid values:
Content that shall be 01 Common Transaction Stat.
calculated. 02 Offline Transaction Stat.
03 Dispute Transaction Stat.
04 Dual Massage Transaction Stat.
05 Standin Transaction Stat.
06 Logo Fee Stat.
……
98 Other Stat.
99 Total Stat.
Note: Every value shall be ended by full
stop mark “.”, every two words shall be
separated by a space.
 Role Clarification
Every range indicates the role(s) of a Member in a transaction. A Member can perform single or multiple roles, which
is represented in the TLV form, with TROL tag (“transaction role”). Its length is 02. All the roles are represented in a
two-letter acronym. The value of a transaction role is its acronym. For details, please see the below.
Table 61 Role Clarification

Tag Name Tag Name /T Definition Length Value /V

/Acronym /L
TROL(transaction Transaction It means the role of 02 Valid values:
role) Role Member in a AC- Acquirer
transaction IS- Issuer
TL- Total, without role clarification. It
should only appear on the last row of
the report.
Note: There is no full stop mark “.” At
the end of every value.
 Statistic Items
Different statistic items shall be tagged with different values in the form of TLV. Every two items shall be separated
by a space. But the length of the space shall not be taken into account for calculation of the total length.
Table 62 Statistic Items

UPI CONFIDENTIAL 108

 Part III: File Interface

Tag Name Tag Name /T Definition Length Value /V

/Acronym /L
MSTP Message Message Type 04 Its value corresponds to transactions whose
(massage type) Type types can be judged by these fields. Refer to
Appendix F for details.
PCOD Processing Processing 02
(processing For unidentified transactions or transactions
code) without Field 3 and Field 25, these fields shall
be filled with default values according to their
PSCC (point of Point of Point of service 02
attributes. For example, if the attribute is n,
service service condition code
the field shall be filled with 0; if there is an “a”
condition condition
in the attribute, it shall be filled with spaces.
code) code
Note: There is no full stop mark “.” At the end
of every value.
SCOD (system System code System code 03 For dual message settlement transaction and
code) offline settlement transaction, its value is equal
to the TC value, e.g., 300, 301, 362, etc.
For dispute transaction, it shall be filled with
Transaction ID.
For Fee Collection and Fund Disbursement
transaction, it shall be filled with Transaction ID.
For other transactions than dual message
settlement transaction and offline settlement
transaction, the field shall be filled with three
spaces by default.
Note: There is no full stop mark “.” at the end of
each value.
CPRO (card Card property Card property 02 Valid values:
property) 01- Debit card
02- Credit card
03- Quasi-credit card
Note: There is no full stop mark “.” at the end
of each value.
AMOT Amount Transaction 31 X+n30
(amount) amount
TRAF Transaction Transaction fee 31 X+n30
(transaction fee to be settled.
fee)
LOGF (logo fee) Logo fee Logo fee to be 31 X+n30
settled
ERTF (err Dispute fees Dispute 31 X+n30
transact fee) transaction fee
to be settled.
PODF (period Service fee of Amount of 31 X+n30

UPI CONFIDENTIAL 109

 Part III: File Interface

Tag Name Tag Name /T Definition Length Value /V

/Acronym /L
fee) period fee period fee
STIF (stand in Stand in fee Stand in 31 X+n30
fee) authorization
fee
NETA (net Net amount Netted 31 It is the net amount of all transaction amounts
amount) transaction which only appears at the last line of the
volume summary file.
---- Separator Separate 20 -----**********-----
different
regions
 Report Structure
This reports consolidates all reports into a summary file, currently including general transactions initiated with
bankcards, offline transactions, dispute transactions, dual message transactions, stand-in authorization transactions,
branding fee, regular fee, subtotal of small-amount fees, and interchange fee. All transactions are categorized by card
product.
For reader’s convenience, every two layers shall be separated by carriage return/linefeed (0X0D,0X0A), and so shall
every two records. But the length of the carriage return/linefeed shall not be taken into account for calculation of
the tag value. For example, the value of SECT1301 Bank Card shall be 13 instead of 15 though there is a carriage
return/linefeed (0X0D,0X0A).
This report is composed of three layers.
The first layer is for the product type, currently specific to bank cards. For example, if a participant only want to have
transactions based on UnionPay cards, then it should fill the first layer in the following format (the second layer and
the third layer shall be omitted).
SECT1301 Bank Card.
×××××××××××××
×××××××××××××
×××××××××××××
×××××××××××××
----20-----**********-----
The second layer is for the statistic range. Even if there is no offline transaction or stand-in authorization, the tag
name and content should still be present. If there is no value in that tag, the tag will be redirected to the next range.
If there is only general transaction and offline transaction, the second layer shall be filled in the following format (the
first and the third layer shall be omitted).
STAC2701 Common Transaction Stat.
×××××××××××××
×××××××××××××
STAC2802 Offline Transaction Stat.
×××××××××××××

UPI CONFIDENTIAL 110

 Part III: File Interface

×××××××××××××
STAC2603 Error Transaction Stat.
STAC3304 Dual Massage Transaction Stat.
STAC2805 Standin Transaction Stat.
STAC1706 Logo Fee Stat.
STAC1498 Other Stat.
STAC1499 Total Stat.
The third layer is for the statistic items involved in role classification. If the statistic item is not included in the second
layer, it does not need to appear; if the statistic item is included in the second layer, it must appear. Generally, all role
tag should appear. Details are listed here:
1)For Common Transaction Stat., TROL, MSTP, PCOD, PSCC, SCOD, AMOT, and TRAF shall be calculated.
2)For Offline Transaction Stat., TROL, MSTP, PCOD, PSCC, SCOD, AMOT, and TRAF shall be calculated.
3)For Error Transaction Stat., TROL, MSTP, PCOD, PSCC, SCOD, AMOT, and TRAF shall be calculated.
4)For Dual Massage Transaction Stat., TROL, MSTP, PCOD, PSCC, SCOD, AMOT, and TRAF shall be calculated.
5) For Stand-in Transaction Stat., TROL, MSTP, PCOD, PSCC, SCOD, AMOT, and STIF shall be calculated
6)For Logo Fee Stat., TROL, CPRO, and LOGF shall be calculated.
7)For Other Stat., AMOT and TRAF shall be calculated.
8)For Total Stat., TROL and NETA shall be calculated.
Requirements:
1) For Common Transaction Stat, Offline Transaction Stat., Error Transaction Stat., Dual Massage Transaction Stat.,
and Stand-in Transaction Stat., if there is only one role (Issuer or Acquirer) of the Member, there should be one record.
If there are two roles, there should be two records.
2) The Logo Fee Stat shall be presented in the following format. If there is no value for a role, the LOGF shall also
appear, and its value is a space plus thirty “0”s.
STAC1706 Logo Fee Stat.
TROL02AC CPRO0202 LOGF31XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
TROL02AC CPRO0203 LOGF31XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
TROL02IS CPRO0202 LOGF31XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
TROL02IS CPRO0203 LOGF31XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
If there is no role in that range, then only TLV content of the third layer shall appear.
3)For Other Stat. where there is a value, there is a record. If there is no value, only TVL content of the second layer
shall appear.
4) For Total Stat., the total value shall appear.
 Sample File
SECT1301 Bank Card.
STAC2701 Common Transaction Stat.
TROL02AC MSTP040200 PCOD0200 PSCC0200 SCOD03S22 AMOT31C000000000000200003000000000000

UPI CONFIDENTIAL 111

 Part III: File Interface

TRAF31C000000000000000000000000000300
TROL02IS MSTP040200 PCOD0200 PSCC0200 SCOD03S22 AMOT31D000000000000500003004500000000
TRAF31D000000000000000000000000000360
STAC2802 Offline Transaction Stat.
TROL02AC MSTP040000 PCOD0200 PSCC0200 SCOD03300 AMOT31C000000000000200003000000000000
TRAF31D000000000000000000000024000000
TROL02IS MSTP040000 PCOD0200 PSCC0200 SCOD03300 AMOT31D000000000000200003000000000000
TRAF31C000000000000000000000024000000
STAC2603 Error Transaction Stat.
TROL02AC MSTP040422 PCOD0200 PSCC0200 SCOD03E23 AMOT31C000000000000000000000000201200
TRAF31D000000000000000000000000002060 ERTF31C000000000000000000000000000140
TROL02IS MSTP040422 PCOD0200 PSCC0200 SCOD03E23 AMOT31C000000000000000000000000201200
TRAF31D000000000000000000000000002060 ERTF31C000000000000000000000000000140
STAC3304 Dual Massage Transaction Stat.
TROL02AC MSTP040000 PCOD0200 PSCC0200 SCOD03100 AMOT31C000000000000200003000000000000
TRAF31D000000000000000000000024000000
TROL02IS MSTP040000 PCOD0200 PSCC0200 SCOD03100 AMOT31D000000000000200003000000000000
TRAF31C000000000000000000000024000000
STAC2805 Standin Transaction Stat.
TROL02AC MSTP040200 PCOD0200 PSCC0200 SCOD03S22 AMOT31C000000000000000000000000201200
STIF31D000000000000000000000000002060
TROL02IS MSTP040200 PCOD0200 PSCC0200 SCOD03S22 MOT31C000000000000000000000000201200
STIF31D000000000000000000000000002060
STAC1706 Logo Fee Stat.
TROL02AC CPRO0202 LOGF31D000000000000000000000000201200
TROL02AC CPRO0203 LOGF31D000000000000000000000000002800
TROL02IS CPRO0202 LOGF31D000000000000000000000000203700
TROL02IS CPRO0203 LOGF31D000000000000000000000000001201
STAC1498 Other Stat.
AMOT31C000000000000200003000000000000 TRAF31C000000000000000000000000000300
AMOT31D000000000000500003004500000000 TRAF31D000000000000000000000000000360
STAC1499 Total Stat.
TROL02TL NETA31C000000000000005838000003400006
----20-----**********-----

C605DZ- Institution Dispute Resolution Detail

Institution Dispute Resolution Detail C605DZ demonstrates the transactions processed by Cross-border Dispute
Resolution System (CDRS). This report is a daily report, and the report name is IFRYYMMDD01C605DZ.
 Report Header

UPI CONFIDENTIAL 112

 Part III: File Interface

The report header includes the following information:

 IIN
 Institution Name
 Settlement Date
 Original Currency
 Machine-readable Format
Table 63 C605DZ Report Format

Position Format Alignment Definition

1-8 an8 Left-alignment IIN of Acquirer
10-17 an8 Left-alignment IIN of Issuer
19-26 un8 Right-alignment Dispute Settlement Date
28-46 an19 Left-alignment Primary Account Number
48-53 an6 Left-alignment Original Transaction Sequence Number a
56-65 un10 Right-alignment Original Transaction Date a
67-77 un11 Right-alignment Dispute Amount in Original Currency
79-88 un10 Right-alignment Dispute Exchange Rate
90-97 un8 Right-alignment Discount Amount b
99-113 an15 Left-alignment Merchant Code
115-136 an22 Left-alignment Merchant Name
138-167 an30 Left-alignment Dispute Description
169-172 an4 Left-alignment Reason Code
Note: Format “an” stands for alphanumeric, while format “un” stands for unpacked numeric.
Note a: The original transaction refers to the last transaction prior to this dispute transaction; it is not
necessarily the initial original transaction triggering the dispute transaction. For example, the original
transaction of a chargeback triggered by a purchase transaction may be the debit adjustment instead of the
purchase.
Note b: Fee returned caused by this dispute transaction.
 Sample
For report samples, please refer to Section C.2 of the Technical Specifications on Bankcard Interoperability - Part VI
Annex.
C606DZ- UPI Institution (UPI POS) Merchant Net Settlement Report
This report is provided to Acquirers whose Merchants initiating directly-connected transactions, and it is a daily
report. The report name is IFRYYMMDD01C606DZ.
 Report Header
The report header includes the following information:
 Report Date

UPI CONFIDENTIAL 113

 Part III: File Interface

 Institution Name
 Transaction Settlement Date
 Report Date
 Transaction Currency (billing currency for issuer and transaction currency for the acquirer)
 Settlement Currency
 Machine-readable Format
Table 64 C606DZ Report Format

Position Field Length Format Alignment Definition

1-15 15 UN Left-alignment Merchant ID
17-55 39 AN Left-alignment Merchant Name
57-95 39 AN Left-alignment Account Name
97-127 31 AN Left-alignment Account No.
129-148 20 AN Left-alignment Name of Beneficiary
150-164 15 UN Right-alignment Transfer Amount
Note: Format “an” stands for alphanumeric, while format “un” stands for unpacked
numeric.
 Sample
For report samples, please refer to Section C.3 of the Technical Specifications on Bankcard Interoperability - Part VI
Annex.

C607DZ- UPI Institution (UPI POS) Merchant Reconciliation List

This report is used as the basis for reconciliation by Merchants initiating directly-connected transactions, and it is a
daily report. The report name is IFRYYMMDD01C607DZ.
 Report Header
The report header includes the following information:
 Report Code
 Report Date
 Merchant ID
 Account Name
 Account Number
 Settlement Date
 Settlement Currency
 Transaction Currency
 Machine-readable Format
Table 65 C607DZ Report Format (Summary)

UPI CONFIDENTIAL 114

 Part III: File Interface

Position Field Length Format Alignment Definition

1-16 16 AN Left-alignment Card Type
18-34 17 UN Right-alignment Transaction Count
38-55 18 UN Right-alignment Transaction Amount (Transaction Currency)
62-79 18 UN Right-alignment Transaction Amount (Settlement Currency)
81-97 17 UN Right-alignment Interchange Fee
99-121 23 UN Right-alignment Net Settlement Amount
Note: Format “an” stands for alphanumeric, while format “un” stands for unpacked numeric.

Table 66 C607DZ Report Format (Details)

Position Field Length Format Alignment Definition

1-23 23 UN Left-alignment Card No.
25-42 18 UN Right-alignment Transaction Amount
46-73 28 UN Left-alignment Transaction Date and Time
75-96 22 UN Left-alignment Authorization Number
98-113 16 UN Left-alignment Voucher Number
115-138 24 UN Right-alignment Merchant Discount Amount
142-152 11 UN Left-alignment Term Number
154-169 16 UN Left-alignment Reference Number
Note: Format “un” stands for unpacked numeric.
 Sample
For report samples, please refer to Section C.4 of the Technical Specifications on Bankcard Interoperability - Part VI
Annex.

C608DZ- UPI Institution (Acquirer Side) Outgoing STF Processing Feedback

This report is provided to Members adopting the dual-message mode, and it is a daily report. The report name is
IFRYYMMDD01C608DZ.
 Report Header
The report header includes the following information:
 Institution Identification Code
 Institution Name
 Transaction Settlement Date
 Report Date
 Transaction Currency
 Machine-readable Format
The information of outgoing STF, net settlement, and rejected transactions is summarized by transaction count as
well as total amount. The details of rejected transactions, including Primary Account Number, Reject Code,
UPI CONFIDENTIAL 115
 Part III: File Interface

Transaction Time, Transaction Amount, Authorization Number, Merchant ID and Terminal ID, are listed one by one.
Table 67 C608DZ Report Format (Summary)

Position Field Length Format Alignment Definition

26-42 17 UN Right-alignment Transaction Count
46-62 17 UN Right-alignment Total Amount
Note: Format “un” stands for unpacked numeric.

Table 68 C608DZ Report Format (Details of Rejected Transaction)

Position Field Length Format Alignment Definition

1-34 34 AN Left-alignment Primary Account Number
36-46 11 AN Right-alignment Reject Code a
48-66 19 UN Right-alignment Transaction Time b
68-86 19 UN Right-alignment Transaction Amount
88-112 25 AN Left-alignment Authorization Number
114-132 19 AN Left-alignment Merchant ID
134-152 19 AN Left-alignment Terminal ID
Note: Format “an” stands for alphanumeric, while format “un” stands for unpacked numeric.
Note a: Please refer to Table A.35 of the Technical Specifications on Bankcard Interoperability - Part VI Annex to
see the valid values of Reject Code.
Note b: The format of Transaction Time is “MMDDhhmmss”.
 Sample
For report samples, please refer to Section C.5 of the Technical Specifications on Bankcard Interoperability - Part VI
Annex.

C612DZ- UPI Institution Settlement Reconciliation Report

This report is a daily report. For Members who need reconciliation, this report serves as the evidence of the fund
transfer between institutions. The report name is IFRYYMMDD01C612DZ.
 Report Header
The report header includes the following information:
 Institution Identification Code
 Institution Name
 Transaction Settlement Date
 Report Date
 Transaction Currency
 Machine-readable Format
Table 69 C612DZ Report Format

UPI CONFIDENTIAL 116

 Part III: File Interface

Position Field Length Format Alignment Definition

1-19 19 AN Left-alignment Settlement Currency
20-57 38 AN Right-alignment Acquirer Net Settlement Amount
58-93 36 AN Right-alignment Issuer Net Settlement Amount
94-126 33 AN Right-alignment All Net Settlement Amount
Note: Format “an” stands for alphanumeric.
 Sample
For report samples, please refer to Section C.4 of the Technical Specifications on Bankcard Interoperability - Part VI
Annex.

C614DZ- UPI Issuer Domestic and Cross-Border Transaction Settlement Report

This is a daily report. The report name is IFRYYMMDD01C614DZ-XX-(PAN length)-XXXXXXXXXXXX (12 digits BIN)-XXX
(Settlement currency code). When the BIN length is less than 12 digits, letters “x” will be added to the right of the
BIN to align all report names to a fixed length. Below please see examples of some valid formats:
IFRYYMMDD01C614DZ-16-624304xxxxxx-458
IFRYYMMDD01C614DZ-16-6233770xxxxx-458
IFRYYMMDD01C614DZ-16-62338253xxxx-156
IFRYYMMDD01C614DZ-19-623382534567-156
The report is sent from UPI to Issuers.
 Report Header
The report header includes the following information:
 Institution Identification Code
 Institution Name
 Settlement Date
 PAN Length
 BIN
 Settlement Currency
 Daily Sub-reports
UPI Issuer Domestic and Cross-Border Transaction Settlement Reports include 3 daily sub-reports:
 C614-DZ-001 UPI Issuer Domestic Transaction Settlement Report (Daily Report)
 C614-DZ-002 UPI Issuer Cross-Border Transaction Settlement Report (Daily Report)
 C614-DZ-003 UPI Issuer Domestic and Cross-Border Stand-In Transaction Settlement Report (Daily Report)
These reports include all fees that are that are settled in a given settlement service. Fees are reported by the following
categories:
 Business mode
 Transaction type
Note 1: The report sample shows all transaction types which may be present in the report. The transaction types

UPI CONFIDENTIAL 117

 Part III: File Interface

listed in the report for each Issuer may vary according to the transaction types that the Issuer actually supports.
Note 2: Fee Collection/Fund Disbursement transactions are not included in the report, as they cannot be categorized
by BIN. Issuers may subscribe to the C602DZ report if they need to collect data of Fee Collection/Disbursement
transactions.
Note 3: The C614DZ report is only used for statistics and reconciliation. It cannot replace C602DZ report.
Table 70 Sub-Report Details

Report ID Report Title Report Description

C614-DZ-001 UPI Issuer Domestic The report is prepared in aspects of dispute and non-dispute
(mandatory) Transaction transactions which are further broken down into different
Settlement Report transaction types. The settlement count, the settlement amount,
(Daily Report) the interchange reimbursement fee, the service fee, and the net
settlement amount are presented for each settlement category.
Subtotals by business mode, subtotals by dispute transaction and
non-dispute transaction, and totals for all transactions are included
in the report.
C614-DZ-002 UPI Issuer Cross- The report is prepared in aspects of dispute and non-dispute
(mandatory) Border Transaction transactions which are further broken down into different
Settlement Report transaction types. The settlement count, the settlement amount,
(Daily Report) the interchange reimbursement fee, the international service fee,
the cross-border transaction fee, and the net settlement amount
are presented for each category. Subtotals by business mode,
subtotals by dispute transaction and non-dispute transaction, and
totals for all transactions are included in the report.
C614-DZ-003 UPI Issuer Domestic The report is broken down into domestic and cross-border stand-in
(optional) and Cross-Border transactions. The settlement count and the stand-in service fee are
Stand-In Transaction summarized for each category. A total of all stand-in transactions
Settlement Report are given in the report.
(Daily Report)
 Machine-readable Format
Table 71 C614DZ-001 Report Format

Position Field Length Format Alignment Definition Note

1-11 11 AN Left-alignment Institution Role Issuer
13-48 36 AN Left-alignment Transaction Type
50-59 10 UN Right-alignment Settlement Count
61-81 21 AN Right-alignment Settlement Amount High accuracy
83-101 19 AN Right-alignment Interchange Reimbursement Fee High accuracy
103-121 19 AN Right-alignment Service Fee High accuracy
123-141 19 AN Right-alignment Reserved
143-161 19 AN Right-alignment Reserved
163-183 21 AN Right-alignment Net Settlement Amount High accuracy

UPI CONFIDENTIAL 118

 Part III: File Interface

Position Field Length Format Alignment Definition Note

Note: Format “an” stands for alphanumeric, while format “un” stands for unpacked numeric.

Table 72 C614DZ-002 Report Format

Position Field Length Format Alignment Definition Note

1-11 11 AN Left-alignment Institution Role Issuer
13-48 36 AN Left-alignment Transaction Type
50-59 10 UN Right-alignment Settlement Count
61-81 21 AN Right-alignment Settlement Amount High accuracy
83-101 19 AN Right-alignment Interchange Reimbursement Fee High accuracy
103-121 19 AN Right-alignment International Service Fee High accuracy
123-141 19 AN Right-alignment Cross-border Transaction Fee High accuracy
143-161 19 AN Right-alignment Reserved
163-183 21 AN Right-alignment Net Settlement Amount High accuracy
Note: Format “an” stands for alphanumeric, while format “un” stands for unpacked numeric.

Table 73 C614DZ-003 Report Format

Position Field Length Format Alignment Definition Note

1-11 11 AN Left-alignment Institution Role Issuer
13-48 36 AN Left-alignment Transaction Type
50-59 10 UN Right-alignment Settlement Count
61-81 21 AN Right-alignment Stand-In Service Fee High accuracy
Note: Format “an” stands for alphanumeric, while format “un” stands for unpacked
numeric.
 Sample
For report samples, please refer to Section C.7 of the Technical Specifications on Bankcard Interoperability - Part VI
Annex.

C615DZ- UPI Acquirer Domestic and Cross-Border Transaction Settlement Report

This is a daily report. The report name is IFRYYMMDD01C615DZ-XXX (Settlement currency code). The report is sent
from UPI to Acquirers.
 Report Header
The report header includes the following information:
 Institution Identification Code
 Institution Name
 Settlement Date
 Settlement Currency

UPI CONFIDENTIAL 119

 Part III: File Interface

 Daily Sub-reports
UPI Acquirer Domestic and Cross-Border Transaction Settlement Reports include 6 daily sub-reports:
C615-DZ-001 UPI Acquirer Credit Card Domestic Transaction Settlement Report (Daily Report)
 C615-DZ-002 UPI Acquirer Credit Card Cross-Border Transaction Settlement Report (Daily Report)
 C615-DZ-003 UPI Acquirer Debit Card Domestic Transaction Settlement Report (Daily Report)
 C615-DZ-004 UPI Acquirer Debit Card Cross-Border Transaction Settlement Report (Daily Report)
 C615-DZ-005 UPI Acquirer Prepaid Card Domestic Transaction Settlement Report (Daily Report)
 C615-DZ-006 UPI Acquirer Prepaid Card Cross-Border Transaction Settlement Report (Daily Report)
These reports include all fees that are settled in a given settlement service. Fees are reported by the following
categories:
 Business mode
 Transaction type
Note 1: The report sample shows all transaction types which may be present in the report. The transaction types
listed in the report for each Acquirer may vary according to the transaction types that the Acquirer actually supports.
Note 2: Fee Collection/Fund Disbursement transactions are not included in the report, as they cannot be categorized
by card types. Acquirers may subscribe to the C602DZ report if they need to collect data of Fee Collection/Fund
Disbursement transactions.
Note 3: The principles of card type judgement (debit card, credit card or prepaid card) are consistent with the BIN
files. For example, currently signature-based debit cards and signature-based prepaid cards are categorized as credit
cards in accordance with BIN files.
Note 4: The C615DZ report is only used for statistics and reconciliation. It cannot replace C602DZ report.
Table 74 Sub-Report Details

Report ID Report Title Report Description

C615-DZ-001 UPI Acquirer Credit The report is prepared in aspects of dispute and non-dispute
(mandatory) Card Domestic transactions which are further broken down into different
Transaction transaction types. The settlement count, the settlement amount, the
Settlement Report interchange reimbursement fee, the service fee, and the net
(Daily Report) settlement amount are presented for each category. Subtotals by
business mode, subtotals by dispute transaction and non-dispute
transaction, and totals for all transactions are included in the report.
C615-DZ-002 UPI Acquirer Credit The report is prepared in aspects of dispute and non-dispute
(mandatory) Card Cross-Border transactions which are further broken down into different
Transaction transaction types. The settlement count, the settlement amount, the
Settlement Report interchange reimbursement fee, the international service fee, the
(Daily Report) cross-border transaction fee, and the net settlement amount are
presented for each category. Subtotals by business mode, subtotals
by dispute transaction and non-dispute transaction, and totals for all
transactions are included in the report.
C615-DZ-003 UPI Acquirer Debit The report is prepared in aspects of dispute and non-dispute
(mandatory) Card Domestic transactions which are further broken down into different
Transaction transaction types. The settlement count, the settlement amount, the
Settlement Report interchange reimbursement fee, the service fee, and the net

UPI CONFIDENTIAL 120

 Part III: File Interface

Report ID Report Title Report Description

(Daily Report) settlement amount are presented for each category. Subtotals by
business mode, subtotals by dispute transaction and non-dispute
transaction, and totals for all transactions are given.
C615-DZ-004 UPI Acquirer Debit The report is prepared in aspects of dispute and non-dispute
(mandatory) Card Cross-Border transactions which are further broken down into different
Transaction transaction types. The settlement count, the settlement amount, the
Settlement Report interchange reimbursement fee, the international service fee, the
(Daily Report) cross-border transaction fee, and the net settlement amount are
presented for each category. Subtotals by business mode, subtotals
by dispute transaction and non-dispute transaction, and totals for all
transactions are included in the report.
C615-DZ-005 UPI Acquirer Prepaid The report is prepared in aspects of dispute and non-dispute
(mandatory) Card Domestic transactions which are further broken down into different
Transaction transaction types. The settlement count, the settlement amount, the
Settlement Report interchange reimbursement fee, the service fee, and the net
(Daily Report) settlement amount are presented for each category. Subtotals by
business mode, subtotals by dispute transaction and non-dispute
transaction, and totals for all transactions are included in the report.
C615-DZ-006 UPI Acquirer Prepaid The report is prepared in aspects of dispute and non-dispute
(mandatory) Card Cross-Border transactions which are further broken down into different
Transaction transaction types. The settlement count, the settlement amount, the
Settlement Report interchange reimbursement fee, the international service fee, the
(Daily Report) cross-border transaction fee, and the net settlement amount are
presented for each category. Subtotals by business mode, subtotals
by dispute transaction and non-dispute transaction, and totals for all
transactions are included in the report.
 Machine-readable Format
Table 75 C615DZ-001, C615DZ-003 and C615DZ-005 Report Format

Position Field Length Format Alignment Definition Note

1-11 11 AN Left-alignment Institution Role Acquirer
13-48 36 AN Left-alignment Transaction Type
50-59 10 UN Right-alignment Settlement Count
61-81 21 AN Right-alignment Settlement Amount High accuracy
83-101 19 AN Right-alignment Interchange Reimbursement Fee High accuracy
103-121 19 AN Right-alignment Service Fee High accuracy
123-141 19 AN Right-alignment Reserved
143-161 19 AN Right-alignment Reserved
163-183 21 AN Right-alignment Net Settlement Amount High accuracy
Note: Format “an” stands for alphanumeric, while format “un” stands for unpacked numeric.

Table 76 C615DZ-002, C615DZ-004 and C615DZ-006 Report Format

UPI CONFIDENTIAL 121

 Part III: File Interface

Position Field Length Format Alignment Definition Note

1-11 11 AN Left-alignment Institution Role Issuer
1-11 11 AN Left-alignment Institution Role Acquirer
13-48 36 AN Left-alignment Transaction Type
50-59 10 UN Right-alignment Settlement Count
61-81 21 AN Right-alignment Settlement Amount High accuracy
83-101 19 AN Right-alignment Interchange Reimbursement Fee High accuracy
103-121 19 AN Right-alignment International Service Fee High accuracy
123-141 19 AN Right-alignment Cross-border Transaction Fee High accuracy
143-161 19 AN Right-alignment Reserved
163-183 21 AN Right-alignment Net Settlement Amount High accuracy
Note: Format “an” stands for alphanumeric, while format “un” stands for unpacked numeric.
 Sample
For report samples, please refer to Section C.8 of the Technical Specifications on Bankcard Interoperability - Part VI
Annex.

C616DZ- UPI Institution (Acquirer) Outgoing Unsettled Transactions Reminding (Over

20 days till 29 days) Report
This is a daily report. The report name is IFRYYMMDD01C616DZ. The report is sent from UPI to dual message
Acquirers. The report is broken down by Original Authorization Date, and transactions of each day are summarized
by each ‘transaction currency - settlement currency’ pair.
 Report Header
The report header includes the following information:
 Institution Identification Code
 Institution Name
 Report Date
 Original Authorization Period
 Machine-readable Format
Table 77 C616DZ Report Format (Transaction Details)

Position Field Length Format Alignment Definition

1-31 31 AN Left-alignment Original Authorization Date
33-47 15 AN Left-alignment Acquirer IIN
49-61 13 AN Left-alignment Sender IIN
63-81 19 UN Left-alignment Transaction Time
83-97 15 UN Left-alignment Trace Number
99-130 32 UN Left-alignment Primary Account Number

UPI CONFIDENTIAL 122

 Part III: File Interface

Position Field Length Format Alignment Definition

132-149 16 UN Right-alignment Transaction Amount
151-173 23 UN Right-alignment Transaction Currency
175-200 26 UN Right-alignment Settlement Amount
202-223 22 UN Right-alignment Settlement Currency
225-239 15 AN Left-alignment Merchant ID
241-248 8 AN Left-alignment Terminal ID
Note: Format “an” stands for alphanumeric, while format “un” stands for unpacked
numeric.

Table 78 C616DZ Report Format (Summaries of each original transaction date)

Position Field Length Format Alignment Definition

1-31 31 AN Left-alignment Original Authorization Date
33-47 15 AN Left-alignment Acquirer IIN
49-61 13 AN Left-alignment Sender IIN
63-79 17 UN Right-alignment Transaction Count
81-149 69 UN Right-alignment Total Transaction Amount
151-173 23 UN Right-alignment Transaction Currency
175-200 26 UN Right-alignment Total Settlement Amount
202-223 22 UN Right-alignment Settlement Currency
Note: Format “an” stands for alphanumeric, while format “un” stands for unpacked
numeric.
 Sample
For report samples, please refer to Section C.9 of the Technical Specifications on Bankcard Interoperability - Part VI
Annex.

C618DZ- Institution Non-Dispute Fee Collection and Fund Disbursement Detail Report
Institution Non-dispute Fee Collection and Fund Disbursement Detail C618DZ demonstrates the non-dispute Fee
Collection and Fund Disbursement transactions processed by Cross-border Dispute Resolution System (CDRS). Please
refer to Technical Specifications on Bankcard Interoperability - Part VI Annex for detailed message reason codes. This
report is a daily report, and the report name is IFRYYMMDD01C618DZ.
 Report Header
The report header includes the following information:
 Settlement Date
 Report Code
 Institution Identification Code
 Institution Name
 Original Currency

UPI CONFIDENTIAL 123

 Part III: File Interface

 Machine-readable Format
Table 79 C618DZ Report Format

Position Field Length Format Alignment Definition

1-8 8 AN Left-alignment IIN of Acquirer
10-17 8 AN Left-alignment IIN of Issuer
19-26 8 UN Right-alignment Settlement Date
28-38 11 UN Right-alignment Settlement Amount in Original Currency
40-99 60 AN Left-alignment Detail Description
101-104 4 AN Left-alignment Reason Code
Note: Format “an” stands for alphanumeric, while format “un” stands for unpacked numeric.
 Sample
For report samples, please refer to Section C.10 of the Technical Specifications on Bankcard Interoperability - Part VI
Annex.

C802DZ- Tax Refund Report

This is a daily report. The report name is IFRYYMMDD01C802DZ-XXX (Transaction Currency Code)-XXX (Settlement
Currency Code). The report is sent from UPI to Acquirers. The following two types of transactions are included in this
report:
 Refund transactions for tax refund purpose; and
 Primary Credit Transactions initiated by Merchants classified under MCC 9311 - Tax payments.
Note: The C802DZ report is only used for statistics and reconciliation. It cannot substitute for the C602DZ report in
function.
 Report Header
The report header includes the following information:
 Institution Identification Code
 Institution Name
 Transaction Settlement Date
 Report Date
 Transaction Currency
 Settlement Currency
 Machine-readable Format
Table 80 C802DZ Report Format

Position Field Length Format Alignment Definition

1-13 13 AN Left-alignment Institution Role
14-49 36 AN Left-alignment Transaction Type
50-66 17 UN Right-alignment Settlement Count

UPI CONFIDENTIAL 124

 Part III: File Interface

Position Field Length Format Alignment Definition

67-90 24 AN Right-alignment Transaction Amount
91-111 21 AN Right-alignment Settlement Amount
112-132 21 AN Right-alignment Interchange Reimbursement Fee
133-153 21 AN Right-alignment Service Fee
154-174 21 AN Right-alignment Additional Fee
175-197 23 AN Right-alignment Net Settlement Amount
Note: Format “an” stands for alphanumeric, while format “un” stands for unpacked
numeric.
 Sample
For report samples, please refer to Section C.11 of the Technical Specifications on Bankcard Interoperability - Part VI
Annex.

UPI CONFIDENTIAL 125

 Part III: File Interface

8 Other Files
8.1 Overview of Other Files
Function of Other Files
Other files mainly refer to exchange rate update files and BIN update files.
GSCS prompts Members to update exchange rate information in their systems by sending the whole-library exchange
rate file. And the Members substitute their local original files for the whole-library exchange rate file. GSCS prompts
Members to update BIN information in their systems by sending the whole-library BIN file. And the Members
substitute their local original files by the whole-library BIN file.
After receiving BIN files from Members, GSCS updates the whole-library file with the BIN information in the BIN files.

Naming Rules for Other Files

Table 81 Naming Rules for Other Files

File Name Value of Position 1~11 Value of Position 12~14

Transaction with Exchange Rate Information Valid value for Position Valid values for Position
outgoing IC card offline purchase file 1~11: 12~14:
IFOYYMMDD?? RAT- Exchange Rate Update
Record File
BIN- Update Records of BIN
assigned by UPI a
Valid value for Position Valid values for Position
1~11: 12~14:
OFOYYMMDD51 BIN- Update Records of BIN
sent by Members
Note a: There are various UPI BIN files, mainly consistent with the format specified in section 8.2.2, but
IFOYYMMDD04 is special, not consistent with the basic format and not specified in this document.

Other Files Processing

GSCS 1 Member

Figure 18 Other Files Processing

1. Once these files are generated, GSCS will send them to each Member or receive files from Members.
File List and Access Mode of Other Files

UPI CONFIDENTIAL 126

 Part III: File Interface

Table 82 File List and Access Mode of Other Files

File Name Description File Access Mode

(Y: Allowed;
N: Not Allowed)
Flow Transmission SFTP
IFOYYMMDD??RAT Exchange rate update file from UPI Y Y
IFOYYMMDD??BIN BIN update file from GSCS Y Y

8.2 Format of Other Files

Exchange Rate Update File
Table 83 File Head Format of Exchange Rate Update

Seq. Field Name Type and Length I/O Explanation

1 File Head Tag a4 I Fixed value: HHHH
2 File Generation Time n14 I
3 Reserved Field ans71 I

Table 84 File Record Format of Exchange Rate Update

Seq. Field Name Type and Length I/O Explanation

1 Effective Date of Exchange n8 I/O
Rate Version
2 Original Currency n3 I/O
3 Target Currency N3 I/O
4 Buying Rate ans15 I/O 7 positions on the left of the decimal point
and 7 on the right
5 Middle Rate ans15 I/O 7 positions on the left of the decimal point
and 7 on the right
6 Selling Rate ans15 I/O 7 positions on the left of the decimal point
and 7 on the right
7 Reserved Field ans30 I

Table 85 File Trailer Format of Exchange Rate Update

Seq. Field Name Type and Length I/O Explanation

1 File Trailer Tag a4 I/O Fixed value: TTTT
2 Total Number n10 I/O
3 Reserved Field ans75 I/O
4 End Tag s2 I/O Return and shift sign

BIN Update File

UPI CONFIDENTIAL 127

 Part III: File Interface

Table 86 File Head Format of BIN Update

Seq. Field Name Type and Length I/O Explanation

1 File Head Tag a4 I/O Fixed value: “HHHH”
2 File Generation n14 I/O
Time
3 IIN an11 I/O It is filled by spaces if BIN file is from UPI
The Member’s IIN is provided here, and the value is left-
aligned. The field shall be left-justified with trailing
spaces if the length is less than 11 digits.
4 Reserved Field ans129 I/O It is not used currently and filled with spaces.
5 End Tag s2 I/O Return and shift sign

Table 87 File Record Format of BIN Update

Seq. Field Name Type and Length I/O Explanation

1 Issuer IIN an11 I/O It is left-justified with trailing spaces if the
length is less than 11 digits.
2 Issuer Name ans60 I/O It is left-justified with trailing spaces if the
length is less than 60 characters.
3 Card Level ans1 I/O The value is the same as that of Field 60.3.9 in
the Technical Specifications on Bankcard
Interoperability - Part II Online Message.
4 Issuing Region ans4 I/O Format: 0 + 3 digits country code. Mainland
China is represented by 0156.
5 Card Product ans2 I/O The value is the same as that of Field 60.3.10 in
the Technical Specifications on Bankcard
Interoperability - Part II Online Message.
6 PCT Business Type an16 I/O It is filled with spaces if the BIN file is not
IFOYYMMDD27BIN.
It is filled with the specific PCT business type by
UPI if the BIN file is IFOYYMMDD27BIN.
7 Billing Currency 2 n3 I/O It is filled with spaces if the BIN file is from UPI
but is not IFOYYMMDD27BIN.
It is filled with Billing Currency 2 by UPI if the
BIN file is IFOYYMMDD27BIN.
It is filled with Billing Currency 2 by the
Member if the BIN file is from Members.
8 Billing Currency 3 n3 I/O It is filled with spaces if the BIN file is from UPI
but is not IFOYYMMDD27BIN.
It is filled with Billing Currency 3 by UPI if the
BIN file is IFOYYMMDD27BIN.

UPI CONFIDENTIAL 128

 Part III: File Interface

Seq. Field Name Type and Length I/O Explanation

It is filled with Billing Currency 3 by the
Member if the BIN file is from Members.
9 Prepaid Card Real ans1 I/O Valid values:
name/anonymous flag Space- Not applicable
1- Anonymous prepaid card
0- Real name registered prepaid card
10 Reserved ans10 I/O It is reserved for future use, and filled with
spaces.
11 BIN Length n2 I/O
12 BIN an12 I/O It is left-justified with trailing spaces if the
length is less than 12 digits.
13 PAN Length n2 I/O
14 Card Type a1 I/O Valid values:
C- credit card;
D- debit card;
P - prepaid card;
15 Single/Dual Message n1 I/O It is filled with a space if the BIN file is from UPI
Valid values:
0- single message;
1- dual message
16 Billing Currency 1 n3 I/O It is filled with spaces if the BIN file is from UPI
but is not IFOYYMMDD27BIN.
It is filled with Billing Currency 1 by UPI if the
BIN file is IFOYYMMDD27BIN.
It is filled with Billing Currency 1 by the
Member if the BIN file is from Members.
17 Transaction Type n13 I/O It is filled with spaces if the BIN file is from UPI
Supported
It is filled by the Member if the BIN file is from
Members, and the value is filled with
transaction type supported.
18 Transaction Channel n12 I/O It is filled with spaces if the BIN file is from UPI
Supported
It is filled by the Member if the BIN file is from
Members, and the value is filled with
transaction channel supported.
19 Network Opened n1 I/O It is filled with spaces if the BIN file is from UPI
It is filled by the Member if the BIN file is from
Members, and the value is filled with network
opened.
20 End Tag s2 I/O Return and shift sign
Note 1: Definition of PCT business type

UPI CONFIDENTIAL 129

 Part III: File Interface

Seq. Field Name Type and Length I/O Explanation

1st byte: Cross-border remittance
2nd byte: Domestic P2P transfer outside of Mainland China
3rd byte: Reserved
4th byte: Payout
5th~16th bytes: Reserved
For each byte, value “1” indicates support for the corresponding PCT business type, whereas value “0”
indicates no support. The reserved bytes are filled with spaces by default.
Note 2: Definition of transaction type supported
1st byte: ATM Inquiry
2nd byte: ATM Disbursement
3rd byte: Purchase
4th byte: Purchase Cancellation
5th byte: Authorization/Pre-authorization
6th byte: Authorization/Pre-authorization Cancellation
7th byte: Pre-authorization Completion
8th byte: Pre-authorization Completion Cancellation
9th byte: Refund
10th byte: Settlement Advice (or Pre-authorization Completion (Offline))
11th byte: POS Inquiry
12th byte: Reserved for use
13th byte: Reserved for use
For each byte, value “1” indicates support for the corresponding transaction type, whereas value “0” indicates
no support. For example, if ATM inquiry, ATM disbursement, purchase and purchase cancellation are supported
by the BIN, this field will be filled with 1111000000000.
Note 3: Definition of transaction channel supported
1st byte: ATM
2nd byte: CDM
3rd byte: POS
4th byte: EDC
5th byte: Self-terminal
6th byte: Bank counter and terminal
7th byte: Internet
8th byte: Wireless device, like mobile phone
9th byte: Telephone bank

UPI CONFIDENTIAL 130

 Part III: File Interface

Seq. Field Name Type and Length I/O Explanation

10th byte: reserved
11th byte: Mobile POS
12th byte: CDRA
For each byte, value “1” indicates support for the corresponding transaction channel, whereas value “0”
indicates no support.
For example, if ATM and POS channels are supported by the BIN, this field is filled with 101000000000.
Note 4: Definition of network opened
0: whole UPI network；
1: UPI network for UnionPay card and foreign card；
2: UPI network for UnionPay card and foreign card, and UPI overseas network；
3: UPI overseas network.
Note 5: Definition of Card Product
For BIN Update File other than IFOYYMMDD24BIN and IFOYYMMDD28BIN, this field can be filled with spaces;
For IFOYYMMDD24BIN and IFOYYMMDD28BIN, the value of this field is the same as that of Field 60.3.10 in the
Technical Specifications on Bankcard Interoperability - Part II Online Message;
Note 6: Definition of Card Type
The value of ‘P’ can only apply to IFOYYMMDD24BIN and IFOYYMMDD28BIN;
Note 7: For IFOYYMMDD07BIN & IFOYYMMDD08BIN BIN Update Files,
the value of "Card Type" could be - "N";
the value of "Single/Dual Message" could be - "2";
Note 8: For BIN Update Files other than IFOYYMMDD27BIN, PCT Business Type, Billing Currency 1, Billing
Currency 2, and Billing Currency 3 will be filled with spaces if the BIN file is from UPI.

Table 88 File Trailer Format of BIN Update

Seq. Field Name Type and Length I/O Explanation

1 File Head Tag a4 I Fixed value: “TTTT”
2 BIN Count n10 I
3 Reserved Field ans144 I Not used at this stage, and filled with spaces
4 End Tag s2 I Return and shift sign

UPI CONFIDENTIAL 131

 Part III: File Interface

9 Stand-in Parameter Synchronizing File

9.1 Overview of Stand-in Parameter Synchronizing File
Structure of Stand-in Parameter Synchronizing File
Stand-in authorization parameter synchronizing files are subject to the sequential file structure. Please refer to 2.3.2
Structure of Sequential File for the detailed description of the sequential file structure. Please see the detailed
description in 2.4 Record Format for stand-in authorization parameter synchronizing file format and file header
record format (000), rejection record format (002), error file record format (003) and file end record format (001).

Stand-in Parameter Synchronizing File Processing

Parameter files from Members, such as the PVN information file, the BIN file, the blacklist information file, and the
VIP card information file, are required by the UPI stand-in authorization system. Parameter synchronizing files
submitted by Members can be used for full card parameter updating and increment updating, and files for full
updating and increment updating can be differentiated by file names.
The UPI stand-in authorization system will check and load the parameter synchronizing files upon receipt of the files
from Members. For an invalid file, the system will generate a rejection file and sent it to the Member. For a valid file,
the system will also general a rejection file only including a file header and a file trailer and send it to the Member.
For a full updating file, the system will replace the related information in one time. For an increment file, the system
will conduct related revision, increase or deletion based on the requirements of the file.
Once stand-in authorization is processed, GSCS will send a real-time stand-in authorization file to the Member to
complete its transaction log. After daily settlement, GSCS will send a stand-in authorization fee file to the Member
for notification. For the detailed definition of real-time stand-in authorization file and stand-in authorization fee file,
please refer to stand-in authorization file format in Section 3.2.11.
The file processing flow for stand-in authorization is depicted as follows:

2
Issuer GSCS
3

Figure 19 Stand-in Parameter Synchronizing File Processing

1. GSCS receives the parameter synchronizing file submitted by the Issuer. (e.g. OFTYYMMDD??PVN);
2. GSCS checks if the files are valid. If invalid, rejection file (e.g. IFYYMMDD??PVNR) will be generated; if valid,
rejection file (e.g. IFTYYMMDD??PVNR) will be generated as well;
3. After completing stand-in authorization, GSCS sends the real-time stand-in authorization file
(IFDTYYMMDD??ISTI to the Issuer;
4. After daily settlement, GSCS sends the stand-in authorization fee file (IFDTYYMMDD??ISTIFEE) to the Issuer.

UPI CONFIDENTIAL 132

 Part III: File Interface

File List of Stand-in Parameter Synchronizing File

Table 89 File List of Stand-in Parameter Synchronizing File
File Definition File Name Sender Receiver Explanation Transaction Type Record Format Content
Code

Stand-in PVN OFTYYMMDD??PVN**** Member GSCS It contains full PVN TC800: PVN File header TC000;
Full File information the Issuer Record Format record format
sends to GSCS for initial (000), PVN TC001;
parameter information TC800
synchronization. Upon (800), and file
receipt of this file, GSCS trailer record
will fully update the PVN format (001)
information based on this
file. The batch number is
constantly 00.

Rejection File for IFTYYMMDD??PVNR**** GSCS Member It is the rejection file TC002: Record File header TC000;
Stand-in PVN GSCS sends to the Issuer Decline record format
Full File to notify the Issuer of the (000), record TC001;
reason for failure. The TC003: Error File decline format
Record TC002;
batch number is (002), error file
constantly 00. record format TC003
(003), and file
trailer record
format (001)

Stand-in OFTYYMMDD??APVN**** Member GSCS 1. It contains the TC800:PVN File header TC000;
Authorization incremental PVN Record Format record format
Increment File information the Issuer (000), PVN TC001;
sends to GSCS, used to information
TC800
record revisions. Upon (800), and file
receipt of this file, GSCS trailer record
will make additions, format (001)
deletions, or revisions
based on the identifier in
this file.

2. The file submitted by

the Issuer shall be written
as follows: I-increment;
U-update; D-delete.

The batch number is

constantly 00.

Rejection File of IFTYYMMDD??APVNR**** GSCS Member It is the rejection file TC002: Record File header TC000;
Stand-in GSCS sends to the Issuer Decline record format
Authorization to notify the Issuer of the (000), record TC001;
Increment File reason for error. The TC003: Error File decline format
Record TC002;
batch number is (002), error file
constantly 00. record format TC003
(003), and file
trailer record
format (001)

BIN File for OFTYYMMDD??BIN**** Member GSCS It is the full BIN TC801: BIN File header TC000;
Stand-in information the Issuer Record Format record format
Authorization sends to GSCS for (000), PVN TC001;
synchronization. The information TC801
batch number is (801), and file
constantly 00. trailer record
format (001)

Rejection File of IFTYYMMDD??BINR**** GSCS Member It is the rejection file TC002: Record File header TC000;
BIN File for GSCS sends to the Issuer Decline record format
Stand-in to notify the Issuer of the (000), record TC001;
Authorization reason for error. The TC003: Error File decline format
Record TC002;
(002), error file
record format

UPI CONFIDENTIAL 133

 Part III: File Interface
File Definition File Name Sender Receiver Explanation Transaction Type Record Format Content
Code

batch number is (003), and file TC003

constantly 00. trailer record
format (001)

Stand-in OFTYYMMDD??STP**** Member GSCS It is the black list TC802: STP File header TC000;
Authorization information the Issuer Record Format record format
Blacklist Full File sends to GSCS for (000), STP TC001;
synchronization. information
TC802
Negative/Positive file (802), and file
checking is supported. trailer record
Details are in conformity format (001)
with the consensus
reached by both parties.
The batch number is
constantly 00.

Rejection File for IFTYYMMDD??STPR**** GSCS Member It is the rejection file TC002: Record File header TC000;
Stand-in GSCS sends to the Issuer Decline record format
Authorization to notify the Issuer of the (000), record TC001;
Blacklist Full File reason for error. The TC003: Error File decline format
Record TC002;
batch number is (002), error file
constantly 00. record format TC003
(003), and file
trailer record
format (001)

Stand-in OFTYYMMDD??ASTP**** Member GSCS It is the incremental TC802: STP File header TC000;
Authorization blacklist information the Record Format record format
Blacklist Issuer sends to GSCS for (000), STP TC001;
Increment File synchronization. The information
TC802
batch number is (802), and file
constantly 00. trailer record
format (001)

Rejection File for IFTYYMMDD??ASTPR**** GSCS Member It is the rejection file TC002: Record File header TC000;
Stand-in GSCS sends to the Issuer Decline record format
Authorization to notify the Issuer of the (000), record TC001;
Blacklist reason for error. The TC003: Error File decline format
Record TC002;
Increment File batch number is (002), error file
constantly 00. record format TC003
(003), and file
trailer record
format (001)

Suspended Card IFTYYMMDD??RTP**** GSCS Member It is the response file TC807: RTP File header TC000;
Return GSCS sends to the Issuer Record Format record format
Information File after collecting the (000), RTP TC001;
suspended card information
TC807
information from the (807), and file
Issuer. trailer record
format (001)
Note: When the value
of ?? is 01, it means that
the file is sent after daily
cutoff; when the value
of ?? is 02, it means that
the file is sent after
authorization completion,

Stand-in OFTYYMMDD??VIP**** Member GSCS 1. It contains the full PVN TC803: VIP File header TC000;
Authorization information the Issuer Record Format record format
VIP Full File sends to GSCS for initial (000), VIP TC001;
parameter information
TC803
synchronization. Upon (803), and file
receipt of this file, GSCS trailer record
will fully update the VIP format (001)

UPI CONFIDENTIAL 134

 Part III: File Interface
File Definition File Name Sender Receiver Explanation Transaction Type Record Format Content
Code

information based on this

file.

2. It is the increment file

submitted by the Issuer
shall be written as
follows: I-increment; U-
update; D-delete. The
batch number is
constantly 00.

Rejection File of IFTYYMMDD??VIPR**** GSCS Member It is the rejection file TC002: Record File header TC000;
Stand-in GSCS sends to the Issuer Decline record format
Authorization to notify the Issuer of the (000), record TC001;
VIP Full File reason for error. The TC003: Error File decline format
Record TC002;
batch number is (002), error file
constantly 00. record format TC003
(003), and file
trailer record
format (001)

Stand-in OFTYYMMDD??AVIP**** Member GSCS 1. It contains the TC803: VIP File header TC000;
Authorization incremental VIP Record Format record format
VIP Increment information the Issuer (000), VIP TC001;
File sends to GSCS, used to information
TC803
record revisions. Upon (803), and file
receipt of this file, GSCS trailer record
will make additions, format (001)
deletions, or revisions
based on the identifier in
this file.

2. It is the increment file

submitted by the Issuer.
The file shall be written
as follows: I-increment;
U-update; D-delete. The
batch number is
constantly 00.

Rejection File of IFTYYMMDD??AVIPR**** GSCS Member It is the rejection file TC002: Record File header TC000;
Stand-in GSCS sends to the Issuer Decline record format
Authorization to notify the Issuer of the (000), record TC001;
VIP Increment reason for error. The TC003: Error File decline format
Record TC002;
File batch number is (002), error file
constantly 00. record format TC003
(003), and file
trailer record
format (001)

Stand-in OFTYYMMDD??MCT Member GSCS It is the full merchant TC804:Merchant File header TC000;
Authorization category information the Category File record format
merchant Issuer sends to GSCS for Record Format (000), Merchant TC001;
category full file original parameter Category
TC804
synchronization. GSCS will information
update the corresponding (804), and File
information based on this trailer record
file. format (001)

Stand-in IFTYYMMDD??MCTR GSCS Member It is the rejection file TC002: reject File header TC000;
Authorization GSCS sends to the Issuer record record format
merchant to notify the Issuer of the (000), reject TC001;
category full reason for error. The TC003: error file record format
record TC002;
reject file batch number is (002), error file
constantly 00. record format TC003
(003), and file
trailer record
format (001)

UPI CONFIDENTIAL 135

 Part III: File Interface
File Definition File Name Sender Receiver Explanation Transaction Type Record Format Content
Code

Stand-in OFTYYMMDD??AMCT Member GSCS 1. It is the increment file TC804:Merchant File header TC000;
Authorization of the merchant category Category Record record format
Merchant information the Issuer Format (000), merchant TC001;
Category sends to GSCS, used to category TC804
Increment File record revisions. Upon information
receipt of the file, GSCS (804), and file
will make additions, trailer record
deletions, or revisions format (001)
based on the identifier in
this file.

2. It is the increment file

submitted by the Issuer
shall be written as
follows: I-increment; U-
update; D-delete.

Reject file of IFTYYMMDD??AMCTR GSCS Member It is the rejection file TC002: reject File header TC000;
Stand-in GSCS sends to the Issuer record record format
Authorization to notify the Issuer of the (000), reject TC001;
Merchant reason for error TC003: error file record format
record TC002;
Category (002), error file
Increment File record format TC003
(003), and file
trailer record
format (001)

Stand-in OFTYYMMDD??ARQ Member GSCS It is the data source TC805:ARQC File header TC000;
authorization parameter file for ARQC verification data record format
ARQC verification the Issuer source record (000), format of TC001;
Verification Data sends to GSCS. GSCS will format data source TC805
source update the corresponding parameter
parameter full information based on this record for ARQC
file file. verification
(805), and file
trailer record
format (001)

Reject file of IFTYYMMDD??ARQR GSCS Member It is the rejection file TC002: reject File header TC000;
Stand-in GSCS sends to the Issuer record record format
authorization to notify the Issuer of the (000), reject TC001;
ARQC reason for error. TC003:error file record format
record TC002;
verification data (002), error file
source record format TC003
parameter (003), and file
information full trailer record
file. format (001)

Stand-in OFTYYMMDD??XVR Member GSCS It is the data source TC806:TVR/CVR File header TC000;
Authorization parameter file for record format
TVR/CVR TVR/CVR verification the Verification (000), format of TC001;
verification Issuer sends to GSCS. parameter record TVR/CVR
format TC806
parameter full GSCS will update the verification
file corresponding parameter
information based on this record (806),
file. and file trailer
record format
(001)

Reject file of IFTYYMMDD??XVRR GSCS Member It is the rejection file TC002:reject File header TC000;
Stand-in GSCS sends to the Issuer record record format
Authorization to notify the Issuer of the (000), reject TC001;
TVR/CVR reason for error. TC003:error file record format
record TC002;
Verification (002), error file
Parameter record format TC003
(003), and file

UPI CONFIDENTIAL 136

 Part III: File Interface
File Definition File Name Sender Receiver Explanation Transaction Type Record Format Content
Code

trailer record
format (001)

Stand-in OFTYYMMDD??MTP**** Member GSCS It is the full merchant TC808: MTP File header TC000;
Authorization blacklist sent by the record format record format
merchant Issuer to implement (000), MTP TC001;
blacklist full file transaction blacklist Information TC808
control from acceptance (808), and file
merchant side. The batch tail record
number is 00 constantly. format (001)

Reject file of IFTYYMMDD??MTPR**** GSCS Member It is the returned file TC002: Reject File header TC000;
stand-in GSCS sends to the Issuer record record format
authorization to inform the reason for (000), Reject TC001;
merchant error. The batch number TC003: Error file record format
record TC002;
blacklist full file is constantly 00. (002), Error file
record format TC003
(003), and file
tail record
format (001)

Stand-in OFTYYMMDD??AMTP**** Member GSCS It is the increment file of TC808: MTP File header TC000;
merchant the merchant blacklist the Record format record format
blacklist Issuer sends to GSCS. The (000), MTP TC001;
increment file batch number is Information
TC808
constantly 00. (808), File tail
record format
(001)

Reject file of IFTYYMMDD??AMTPR**** GSCS Member It is the rejection file TC002: Reject File header TC000;
stand-in GSCS sends to the Issuer record record format
merchant to notify the Issuer of the (000), Reject TC001;
blacklist reason for error. The TC003: Error file record format
record TC002;
increment file batch number is (002), Error file
constantly 00. record format TC003
(003), and file
tail record
format (001)

Stand-in OFTYYMMDD??ATP Member GSCS It is the full acquiring TC809: ATP File header TC000;
authorization region blacklist the Issuer record format record format
acquiring region sends to GSCS, intended (000), ATP TC001;
blacklist full file to control transactions Information
TC809
from acquiring region (809), and file
perspective. The batch tail record
number is constantly 00. format (001)

Reject file for IFTYYMMDD??ATPR**** GSCS Member The rejection file GSCS TC002: Reject File header TC000;
stand-in sends to the Issuer to record record format
authorization inform the reason for (000), Reject TC001;
acquiring region error. The batch number TC003: Error file record format
record TC002;
blacklist full file is constantly 00. (002), Error file
record format TC003
(003), and file
tail record
format (001)

Stand-in OFTYYMMDD??AATP**** Members GSCS The increment file for TC809: ATP File header TC000;
authorization acquiring region blacklist, record format record format
acquiring region which the Issuer sends to (000), ATP TC001;
blacklist GSCS. The batch number Information
TC809
increment file is constantly 00. (809), and file
tail record
format (001)

Reject file for IFTYYMMDD??AATPR**** GSCS Member The rejection file GSCS TC002: Reject File header TC000;
stand-in sends to the Issuer to record record format
authorization (000), Reject TC001;

UPI CONFIDENTIAL 137

 Part III: File Interface
File Definition File Name Sender Receiver Explanation Transaction Type Record Format Content
Code

acquiring region notify the Issuer of the TC003: Error file record format TC002;
blacklist reason for error. record (002), Error file
increment file record format TC003
(003), and file
tail record
format (001)

Note: “****”is the sequence number, and its value varies from 0000 to 9999. If the Member submits multiple files in a batch, sequence numbers shall be
assigned to the files for differentiation, For a batch with a single file, the value shall be “0000”.

9.2 Format of Stand-in Parameter Synchronizing File Record

TC800 (PVN)
Table 90 Block 0- Basic PVN Information

Position Length Format Content Description

0 3 n Transaction Code 800: PVN synchronizing file record
3 4 an4 Block Bitmap
7 1 a Operation Identifier The fixed value I should be taken as the Identifier bit in
the full file;
The value of this Identifier is as follows in the increment
files:
I: This record is newly added.
U: The corresponding record is updated.
D: The corresponding record is deleted.
8 2 n Length of Primary It is the length of "Primary Account Number" field.
Account Number
10 19 n Primary Account
Number
29 4 n PVN Value
33 1 an Index of Key The value ranges from 1 to 6, representing one to six
kinds of key indexes; the value 0 is a reserved value,
which should not be used.
34 100 ans Reserved for Use

TC801 (BIN)
Table 91 Block 0- Basic BIN Information

Position Length Format Content Description

0 3 n Transaction code 801: BIN synchronizing file record
3 4 an4 Block Bitmap

UPI CONFIDENTIAL 138

 Part III: File Interface

Position Length Format Content Description

7 1 a Operation Identifier The fixed value I should be taken as the Identifier bit
in the full file;
The value of this Identifier in the increment file is as
follows:
I: This record is newly added.
U: The corresponding record is updated.
D: The corresponding record is deleted.
8 14 n Card BIN It is a “2-bit length bit + maximum 12-digit” character.
The length bit refers to the length of card number but
not that of the card BIN; when the length of the card
BIN is less than 12 digits, the field shall be left-
justified with trailing spaces.
22 1 a If it is a standard Y: Standard UnionPay card; N: Non-standard
UnionPay card UnionPay card.
23 3 n Currency Limit For every card BIN, the currency limit is stipulated for
the stand-in verification item to calculate the billing
amount.
26 30 ans Stand-in verification The Issuer should indicate which items shall be
item bit-map processed with stand-in verification for each BIN. For
the items requiring stand-in verification, the value is
"1"; for the items not requiring the stand-in
verification, the value is "0".
The existing stand-in verification sequence is: card
number length, card number check-digit, card
expiration date, CVN and PVN, stand-in ARQC
verification for IC cards and ARPC generation, TVR
verification for IC cards, CVR verification for IC cards,
and iCVN verification for IC cards.
The undefined verification bit is filled with spaces.
56 2 n Storage position of CVN It is the position to store CVN value in additional data
of Track 2, which is the offset of CVN in additional
data field. The value starts from 1.
58 10 n Daily total
authorization limit
68 10 n Single transaction limit It is the single transaction limit corresponding to this
corresponding to the merchant group
first merchant group
78 10 n Daily cumulative It is the daily transaction limit value corresponding to
transaction limit this merchant group
corresponding to the
first merchant group
88 10 n Single transaction limit

UPI CONFIDENTIAL 139

 Part III: File Interface

Position Length Format Content Description

corresponding to the
second merchant group
98 10 n Daily cumulative
transaction limit
corresponding to the
second merchant group
108 10 n Single transaction limit
corresponding to the
third merchant group
118 10 n Daily cumulative
transaction limit
corresponding to the
third merchant group
128 10 n Single transaction limit
corresponding to the
fourth merchant group
138 10 n Daily cumulative
transaction limit
corresponding to the
fourth merchant group
148 10 n Single transaction limit
corresponding to the
fifth merchant group
158 10 n Daily cumulative
transaction limit
corresponding to the
fifth merchant group
168 10 n Single transaction limit
corresponding to the
sixth merchant group
178 10 n Daily cumulative
transaction limit
corresponding to the
sixth merchant group
188 10 n Single transaction limit
corresponding to the
seventh merchant
group
198 10 n Daily cumulative
transaction limit
corresponding to the
seventh merchant
group

UPI CONFIDENTIAL 140

 Part III: File Interface

Position Length Format Content Description

208 10 n Single transaction limit
corresponding to the
eighth merchant group
218 10 n Daily cumulative
transaction limit
corresponding to the
eighth merchant group
228 10 n Single transaction limit
corresponding to the
ninth merchant group
238 10 n Daily cumulative
transaction limit
corresponding to the
ninth merchant group
248 10 n Single transaction limit
corresponding to the
tenth merchant group
258 10 n Daily cumulative
transaction limit
corresponding to the
tenth merchant group
268 10 n Single limit on Fallback
transaction
278 10 n Accumulative limit on
Fallback transaction
288 2 n CVK Index It starts from 01 and increases successively.
290 2 n ARQC/ARPC Security It starts from 01 and increases successively.
Key (AC-MDK) Index
292 2 n dCVN Key Index It starts from 01 and increases successively.
294 2 n iCVN Key Index It starts from 01 and increases successively.
296 3 n Daily total transaction It is the maximum number of transactions that the
limit card BIN can perform on one settlement day
299 69 ans Reserved
Note 1: If a Member does not define the merchant group of an MCC, GSCS will classify the MCC under the 10th
merchant group by default.
Note 2: The currency limit is the billing currency. If one BIN corresponds to multiple billing currencies, multiple
records shall be submitted.

TC802 (STP)
Table 92 Block 0- Basic STP Information

UPI CONFIDENTIAL 141

 Part III: File Interface

Position Length Format Content Description

0 3 n Transaction code 802: STP synchronizing file record
3 4 an4 Block Bitmap
7 1 a Operation Identifier The fixed value “I” should be taken as the Identifier bit in
the full file.
The value of this Identifier in the increment file is as
follows:
I: This record is newly added.
U: The corresponding record is updated.
D: The corresponding record is deleted.
8 2 n Length of primary It is the length of "primary account number" field.
account number
10 19 n Primary account It is the card number in blacklist provided by the Issuer.
number
29 20 ans Description It is the Issuer’s reserved field
information
49 8 n Record valid date Format: YYYYMMDD;
It stands for the end date of the record valid period.
When the system time exceeds this date, the card record
shall be treated as expired.
57 72 ans Reserved

TC803 (VIP)
Table 93 Block 0- Basic VIP Information

Position Length Format Content Description

0 3 n Transaction code 803: VIP synchronous file record
3 4 an Block Bitmap
7 1 a Operation Identifier The fixed value “I” should be taken as the
Identifier bit in the full files;
The value of this Identifier is as follows in the
increment file:
I: This record is newly added.
U: The corresponding record is updated.
D: The corresponding record is deleted.
8 2 n Length of primary account It is the length of "primary account number"
number field.
10 19 n Primary account number It is the VIP card number provided by the
Issuer

UPI CONFIDENTIAL 142

 Part III: File Interface

Position Length Format Content Description

29 1 a If it is a standard UnionPay card Y: Standard UnionPay card; N: Non-standard
UnionPay card;
30 3 n Currency limit For every card BIN, the currency limit is
stipulated for the stand-in verification item to
calculate the billing amount.
33 10 n Daily total authorization limit
43 10 n Single transaction limit It is the single transaction limit corresponding
corresponding to the first to this merchant group
merchant group
53 10 n Daily transaction limit It is the daily transaction limit corresponding
corresponding to the first to this merchant group.
merchant group
63 10 n Single transaction limit
corresponding to the second
merchant group
73 10 n Daily transaction limit
corresponding to the second
merchant group
83 10 n Single transaction limit
corresponding to the third
merchant group
93 10 n Daily transaction limit
corresponding to the third
merchant group
103 10 n Single transaction limit
corresponding to the fourth
merchant group
113 10 n Daily transaction limit
corresponding to the fourth
merchant group
123 10 n Single transaction limit
corresponding to the fifth
merchant group
133 10 n Daily transaction limit
corresponding to the fifth
merchant group
143 10 n Single transaction limit
corresponding to the sixth
merchant group
153 10 n Daily transaction limit
corresponding to the sixth
merchant group

UPI CONFIDENTIAL 143

 Part III: File Interface

Position Length Format Content Description

163 10 n Single transaction limit
corresponding to the seventh
merchant group
173 10 n Daily transaction limit
corresponding to the seventh
merchant group
183 10 n Single transaction limit
corresponding to the eighth
merchant group
193 10 n Daily transaction limit
corresponding to the eighth
merchant group
203 10 n Single transaction limit
corresponding to the ninth
merchant group
213 10 n Daily transaction limit
corresponding to the ninth
merchant group
223 10 n Single transaction limit
corresponding to the tenth
merchant group
233 10 n Daily transaction limit
corresponding to the tenth
merchant group
243 10 n Single limit on Fallback
transaction
253 10 n Cumulative limit on Fallback
transaction
263 3 n Daily total transaction limit The maximum number of transactions that
can be performed in one settlement day
266 77 ans Reserved
Note 1: If Member does not define the merchant group of an MCC, GSCS will classify the MCC under the 10th
merchant group by default.
Note 2: The currency limit is the billing currency. If one BIN corresponds to multiple billing currencies, multiple
records shall be submitted.

TC804 (MCT)
Table 94 Block 0- Basic MCT Information

Position Length Format Content Description

0 3 n Transaction code 804: MCT merchant category synchronizing file

UPI CONFIDENTIAL 144

 Part III: File Interface

Position Length Format Content Description

3 4 an4 Block Bitmap
7 1 a Operation Identifier The fixed value I should be taken as the Identifier bit in
the full file;
The value of this Identifier is as follows in the increment
file:
I: This record is newly added.
U: This record is updated
D: This Record is deleted
8 4 n Merchant Category MCC
Code
12 4 ans Merchant Category It is the merchant group corresponding to the Merchant
Type Category Type, maximum 10 groups, valued from gp01
to gp10
16 256 Ans Name of Merchant
Category Type
272 100 ans Reserved for use
Note: If Member does not define the merchant group of an MCC, GSCS will classify the MCC under the 10th
merchant group by default.

TC805 (ARQ)
Table 95 Block 0- Basic ARQ Information

Position Length Format Content Description

0 3 n Transaction 805: Data source parameter file for ARQC verification
Code
3 4 an Block
Bitmap
7 1 a Processing The value shall be “I” constantly.
Code
8 2 n Serial It is the serial number of data source.
Number
10 4 ans Tag It is the tag of data source
14 2 n Start It is the start position of data from tag value (It starts from 1
Position instead of 0. For the subfield whose attribute is cn, the start
position is the first letter from the right. For the rest, with the
start position is the first letter on the left.)
16 2 n Truncated It is the length of data truncated from start position.
length

TC806 (XVR)

UPI CONFIDENTIAL 145

 Part III: File Interface

Table 96 Block 0- Basic XVR Information

Position Length Format Content Description

0 3 n Transaction 806: TVR/CVR verification parameter information
Code
3 4 an4 Block bitmap
7 1 a Action Its value is constantly “I” in full file.
Identifier
8 1 a Verification 1 byte
Object
T-TVR verification
C-CVR verification
9 1 n Byte number It is the byte number of the verification data element in the
verification object (TVR or CVR). TVR contains 5 bytes and CVR
contains 4 bytes, both starting from 1.
10 1 n Binary bit It is the bit number of the verification data element in byte,
number starting from 1.
11 1 n Invalid Value It is the invalid value that defines the data element;
The value is given by Issuers. For example, 0 means success,
and 1 means failure
If the verification object in online transaction corresponds to an
invalid value, the verification fails.
12 100 ans Reserved

TC807 (RTP)
Table 97 Block 0- Basic RTP Information

Position Length Format Content Description

0 3 n Transaction 807: Suspended Card Information Return
Code
3 4 an Block Bitmap
7 1 a Manual I: This record is newly added
Processing
U: This record is updated
D: This record is deleted
8 2 n Length of PAN It is used to indicate the length of “PAN”.
10 19 n PAN
29 20 ans Description It is the Issuer’s reserved field.
49 8 n Record valid Format: YYYYMMDD;
date
It stands for the end date of the record valid period. When the
system time exceeds this date, the card record shall be treated
as expired.

UPI CONFIDENTIAL 146

 Part III: File Interface

Position Length Format Content Description

57 72 ans Reserved

TC808 (MTP)
Table 98 Block 0- Basic MTP Information

Position Length Format Content Description

0 3 n Transaction Code 808: Merchant Blacklist
3 4 an Bitmap
7 1 a Operation The fixed value I should be taken as the Identifier bit in the
Identifier full file;
The value of this Identifier in the increment file is as
follows:
I: This record is newly added.
U: The corresponding record is updated.
D: The corresponding record is deleted.
8 11 an Acquirer IIN
19 15 ans Merchant code
34 8 n Valid date of Format: YYYYMMDD;
merchant blacklist
It stands for the end date of the record valid period. When
the system time exceeds this date, the card record shall be
treated as expired
42 100 ans Reserved

TC809 (ATP)
Table 99 Block 0- Basic ATP Information

Position Length Format Content Description

0 3 n Transaction Code 809: acquiring region blacklist information
3 4 an Bitmap
7 1 a Operation The fixed value I should be taken as the Identifier bit in the
Identifier full file;
The value of this Identifier in the increment file is as
follows:
I: This record is newly added.
U: The corresponding record is updated.
D: The corresponding record is deleted.
8 14 n BIN It is a “2-digit length field + maximum 12-digit” number. The
length field refers to the PAN length instead of the BIN
length. If a BIN is less than 12 digits in length, the field shall

UPI CONFIDENTIAL 147

 Part III: File Interface

Position Length Format Content Description

be left-justified with trailing spaces.
22 4 n Acquiring region
code
26 4 ans Merchant type **** stands for all types of merchants.
30 8 n Valid date of Format: YYYYMMDD;
acquiring region
It stands for the end date of the record valid period. When
blacklist
the system time exceeds this date, the card record shall be
treated as expired

UPI CONFIDENTIAL 148

 Part III: File Interface

10 Batch File
10.1 Overview of Batch File
Structure of Batch File
A batch transaction file is recorded in the form of a file header, a file body and a file tail. Each record consists of
multiple blocks. For details, please refer to Section 2.3

Batch File Processing

The settlement methods for batch recurring and batch order transactions differ in the message type that
Acquirers/Issuers adopt. For batch recurring Acquirers and Issuers, it is mandatory for them to support single
message only. The recurring transaction is taken as an example to illustrate the process. The processing flows for
primary credit transaction and recurring are the same, except that primary credit transaction exceptions are
processed by primary credit confirmation while recurring exceptions are processed by reversal.
 Both Acquirer and Issuer adopt single message:
The processing and settlement flow for single-message batch recurring transaction is as follows:

1 3

2 4
Acquirer GSCS Issuer
5

6 7

Figure 20 Batch File Processing for Acquirer and Issuer Both Adopt Single Message

Step 1-5: Batch recurring transactions are converted to online transactions. Details are illustrated in transaction
processing descriptions.
Step 6: For single message Acquirers, GSCS put batch recurring transactions in the audit trailer for the Acquirers
(ACOM/ACOMPOS).
Step 7: For single message Issuers, GSCS will put batch recurring transactions in the audit trailer for the Issuers (ICOM).
Suppose an Acquirer submitted 100 transactions, among which 80 of them had been successfully downloaded by
GSCS and 60 of them had been approved by Issuers. The details are illustrated here below:
Table 100 Detailed Processing of Batch File for Acquirer and Issuer Both Adopt Single Message

Step File Name Purpose Successful Failed

Transaction Count Transaction
Count
1 Batch Recurring To accept submitted transactions 100
Request File
2 Batch Recurring For GSCS to update the Acquirer 80 20
Response File on the file uploading result

UPI CONFIDENTIAL 149

 Part III: File Interface

Step File Name Purpose Successful Failed

Transaction Count Transaction
Count
3 Online Request File To send the request online 80
4 Online Response File For the Issuer to give response 60 20
online
5 Batch Recurring For GSCS to give response to the 60 20
Response File Acquirer
6 Audit Trailer For GSCS to send the settlement 60
trailer to the Acquirer
7 Audit Trailer For GSCS to send the settlement 60
trailer to the Issuer
 Acquirers adopt single message while Issuer adopts dual message:
The processing and settlement flow is the same as that in Figure 20 except for this difference: in step 7, the Issuer
adopts the dual message system, so GSCS sends the settlement file IFCYYMMDD??C instead of ICOM.
 Both Acquirer and Issuer adopt dual message:
If the Acquirer adopts the single message system, the transaction flow of batch recurring and settlement is as follows:

1 3

2 4
Acquirer GSCS Issuer
5

6 7

Figure 21 Batch File Processing for Acquirer and Issuer Both Adopt Dual Message

Step 1-5: In batch recurring transactions, the files submitted in batch will be converted to online files. Please refer to
the transaction processing for details. (For general transactions of dual message Acquirers, the presentment file is
required after the online authorization request. In order to simplify the transaction procedure, in batch recurring
transaction, the presentment file needed is incorporated into transaction request file. For example, in Step 1, request
and presentment will be submitted together through a batch recurring request file.)
Step 6: For the dual message Acquirer, GSCS will send it the dual message settlement file IFCYYMMDD??B.
Step 7: For the dual message Acquirer, GSCS will send it the dual message settlement file IFCYYMMDD??C.
Suppose an Acquirer submitted 100 transactions, among which 80 of them had been successfully downloaded by
GSCS and 60 of them had been approved by Issuers. The transaction processing and settlement procedure is detailed
as follows:
Table 101 Detailed Processing of Batch File for Acquirer and Issuer Both Adopt Dual Message

UPI CONFIDENTIAL 150

 Part III: File Interface

Step File Name Purpose Successful Failed

Transaction Count Transaction
Count
1 Batch Recurring For the Acquirer to submit the 100
Request File transaction and settlement
information
2 Batch Recurring For GSCS to send the upload 80 20
Response File response to the Acquirer
3 Online Request To send the online request 80
Message
4 Online Response For the Issuer to give response 60 20
Message online
5 Batch Recurring For GSCS to send the response to 60 20
Response File the Acquirer
6 Dual Message For GSCS to send successfully settled 60
Settlement File transactions to the Acquirer
7 Dual Message For GSCS to send successfully settled 60
Settlement File transactions to the Issuer
 Acquirer adopts dual message while Issuer adopts single message:
The transaction processing and settlement flow is the same as described in Figure 21 except for this difference: in
Step 7, the Issuer adopts single message and thus GSCS sends the audit trailer (ICOM) instead of the dual message
settlement file IFCYYMMDD??C.

File List of Batch File

Table 102 File List of Batch File
File File Name Sender Receiver Explanation Transaction Type Record Format Code Content
Definition

Batch OFTYYMMDD??ATBIE Acquirer GSCS The Acquirer sends TC705:Recurring File head record format TC700 (File
Recurring the batch recurring (000) head
Request File request to GSCS. record)
File tail record format
001 TC701 (File
tail record)
Recurring record format
705 TC705
(Primary
credit)

Batch IFTYYMMDD??ATBIRS GSCS Acquirer GSCS updates the TC702:Reject File head record format TC700 (File
Recurring Acquirer on file record (700) head
Feedback uploading result record)
File based on file TC703:Error File Reject record format
checking. Record (702) TC701 (File
tail record)
Error file record format
(703) TC702
(Reject
File tail record format record)
(701)
TC702
(Reject

UPI CONFIDENTIAL 151

 Part III: File Interface
File File Name Sender Receiver Explanation Transaction Type Record Format Code Content
Definition

record)

Batch IFTYYMMDD??ATBIRE GSCS Acquirer GSCS sends a TC704:Response File head record format TC700 (File
Recurring response file to the Message 700 head
Response Acquirer based on record)
File the response file File tail record format
given by Issuer. 701 TC701 (File
tail record)
Response record format
704 TC704
(Response
Record)

Batch OFTYYMMDD??ATBOE Acquirer GSCS The Acquirer sends TC706:Primary File head record format TC000
Primary batch primary credit credit 700
credit request to GSCS. TC001
Request File File tail record format
701 TC706
(Primary
Primary credit Record credit)
Format 06

Batch IFTYYMMDD??ATBORS GSCS Acquirer GSCS updates the TC002:Reject File head record format TC700 (File
Primary Acquirer on file record (700), Reject record head
credit uploading result format (702) record)
Feedback based on file TC003:Error File
File checking. Record Error file record format TC701 (File
(703) tail record)

File tail record format TC702

(701) (Reject
record)

TC702
(Reject
record)

Batch IFTYYMMDD??ATBORE GSCS Acquirer GSCS sends a TC704:Response File head record format TC700 (File
Primary response file to the Record 700 head
credit Acquirer based on record)
Response the response file File tail record format
File given by Issuer. 701 TC701 (File
tail record)
Response record format
704 TC704
(Response
record)

Batch OFTYYMMDD??AMOTO Acquirer GSCS The Acquirer sends TC707 order File header record TC700
MO/TO batch order request format 000 (Header
request file to GSCS. record)
File tail record format
001 TC701 (Tail
record)
Recurring record format
707 TC707
(Order)

Batch IFTYYMMDD??AMOTORS GSCS Acquirer GSCS updates the TC702: Reject File header record TC700
MO/TO Acquirer on file Record format (700), Reject (Header
feedback file uploading result record format(702), record)
based on file TC703:Error File Error file record format
checking. Record (703), file tail record TC701 (Tail
format (701) record)

TC702
(Reject
Record)

TC703
(Reject

UPI CONFIDENTIAL 152

 Part III: File Interface
File File Name Sender Receiver Explanation Transaction Type Record Format Code Content
Definition

Record)

Batch IFTYYMMDD??AMOTORE GSCS Acquirer GSCS sends a TC704: Response File header record TC700 (File
MO/TO response file to the Information format 700 head
response file Acquirer based on record)
the response file File tail record format
given by Issuer. 701 TC701 (File
tail record)
Response record format
704 TC704
(Response
record)

10.2 Format of Batch File Record

TC700
Table 103 Block 0- Batch File Head Format

Position Length Format Content I/O Description

0 3 n Transaction Code I/O 700:Batch File Head
3 4 an Block Bitmap I/O
7 10 n Total Transaction I/O All the transactions
Count
17 16 n Total Transaction I/O The total amount of all transactions
Amount
33 11 an IIN of Initiator I/O IIN of the institution that initiated the transaction
44 8 n File submitted date I/O It is filled by the Member or Merchant in the
format of YYYYMMDD
52 8 n Replied transaction I/O It is filled with spaces in the request file; GSCS shall
settlement date define the value in the response file in the format
of YYYYMMDD.
60 40 ans Reserved I/O

TC701
Table 104 Block 0- Batch File Tail Format

Position Length Format Content I/O Description

0 3 n Transaction Code I/O 701:Batch File tail
3 4 an Block Bitmap I/O
7 16 an Reserved I/O Reserved field
23 16 b Reserved I/O Reserved field

TC702 (Rejected Record)

UPI CONFIDENTIAL 153

 Part III: File Interface

Feedback on file initiation in case of error was detected in batch transaction file.
Table 105 Block 0- Batch File Rejected Record

Position Length Format Content I/O Description

0 3 n Transaction I 702: Reject record
Code
3 4 an Block Bitmap I
7 2 an Reject Reason I Please refer to the Technical Specifications on
Bankcard Interoperability - Part VI Annex for
details.
9 40 ans File name I It is the file name where error was recorded. The
file name shall be left-justified with trailing spaces
if the length is less than 40 bytes.
49 Variable ans Rejected I The original transaction content is returned
length Transaction without being changed. It should be in the format
Content of “length + content”. The length is 3 digits.

TC703 (Error File Record)

It is the reject file for the batch file, usually used in case of failed download, incorrect statistics, MAC verification
failure, and excessive error records, etc.
Table 106 Block 0- Batch File Error File Record

Position Length Format Content I/O Description

0 3 n Transaction Code I 703:Error file record
3 4 an Block bitmap I
7 2 an Reject Reason I 01-Cannot download file
02- Statistics do not match
03-MAC verification error
04- Error number exceeds limit
99-Others
9 40 ans File Name I Name of Error File
49 11 an IIN of the sender of original I The IIN of the institution that sends error
file file
60 40 ans Reserved I

TC704 (Response Record)

It is used by GSCS to respond to Acquirers.
Table 107 Block 0- Batch File Response Record

Position Length Format Content Field I/O Description

0 3 n Transaction I 704: Response Record

UPI CONFIDENTIAL 154

 Part III: File Interface

Position Length Format Content Field I/O Description

Code
3 4 an Block bitmap I
7 2 an Response Code 39 I Please refer to the Technical Specifications on
Bankcard Interoperability - Part VI Annex for
details.
9 40 ans Transaction File I It is the name of the file where the original
Name request is recorded. The file name shall be left-
justified with trailing spaces if the length is less
than 40 bytes.
49 10 n Transaction 7 I The same as the transaction date in the
transmission original request transaction
time
59 6 n System trace 11 I The same as the system trace audit number in
audit number the original request file
65 11 an Receiving IIN 100 I
76 40 ans Reserved I

TC705 (Recurring), TC706 (Primary Credit) and TC707 (MOTO)

Table 108 Block 0- Batch File Basic Transaction Record

Position Length Format Content Field I/O Description

0 3 n Transaction O 705:Recurring
Code
706:Primary credit
707:MOTO
3 4 an Block Bitmap O It is used to indicate blocks that are included in
the record.
1. TC705 recurring transaction contains Block 0
and Block 1.
2. TC706 primary credit transaction contains
Block 0 and Block 2
3. TC707 MOTO transaction contains Block 0
and Block 3
7 19 n Primary 2 O
Account
Number
26 15 n Merchant 42 O Merchant code
code
41 4 n Merchant’s 18 O Merchant type
type
45 40 ans Merchant 43 O

UPI CONFIDENTIAL 155

 Part III: File Interface

Position Length Format Content Field I/O Description

Name and
address
85 10 n Transaction 7 O
transmission
time
95 6 n System trace 11 O Its combination with the transaction
audit number transmission time, the Acquirer IIN, and the
sender IIN shall be unique.
101 12 an Retrieval 37 O It should be kept unchanged in the whole
reference transaction lifecycle.
number
113 3 an Transaction 49 O
currency
116 12 n Transaction 4 O
amount
128 11 an Acquirer IIN 32 O
139 11 an Sender IIN 33 O It should be the same with the sender IIN in
TC700.
150 1 n Transaction 60.3.5 O Set value 4 – batch agent
initiation
method
151 2 n Point of 25 O It should be the same with the Field 25 value
Service used in online recurring, primary credit,
condition ordering, which is used to define the
code corresponding online message type after
conversion. For detailed value, please refer to
the definition of Field 25 in recurring
transaction, primary credit transaction and
MOTO transaction in Appendix B of the
Technical Specifications on Bankcard
Interoperability - Part VI Annex.
153 40 ans Reserved O

Table 109 Block 1- Batch File Additional Information for Recurring

Position Length Format Content Field I/O Description

0 2 ans User ID 48 O Optional. Please refer to the usage of PZ in Field 48
category defined in “Online Message”. If not used, it should
be filled with the default value.
2 40 ans User ID 48 O Optional. Please refer to the usage of PZ in Field 48
defined in “Online Message”. If not used, it should
be filled with the default value.
42 17 ans Payment 48 O Optional. Please refer to the start/end date of this

UPI CONFIDENTIAL 156

 Part III: File Interface

Position Length Format Content Field I/O Description

Range payment and the usage of PZ in Field 48 defined in
“Online Message”. If not used, it should be filled
with the default value.
59 40 ans Name 61.6 O Optional. If not used, it shall be filled with the
default value.
99 2 n ID type 61.1 O Optional. If not used, it shall be filled with the
default value.
101 20 ans ID number 61.1 O Optional. Please use the last six digits of the ID.
Please refer to the usage of AM in field 61.6
defined in “online message”. If not used, it shall be
filled with the default value.
121 20 ans Mobile 48 O Optional. If not used, it shall be filled with the
phone default value.
number
141 4 n Card valid 14 O Optional. The format is YYMM. If not used, it shall
date be filled with the default value.
145 36 ans Reserved O

Table 110 Block 2- Batch File Additional Information for Primary Credit

Position Length Format Content Field I/O Description

0 40 ans Payment 48 O Optional. It is the payment item of primary credit
Item filled with the default value if not used.
40 17 ans Payment 48 O Optional. It is the start/end date of this payment.
Range Please refer to the usage of PZ in Field 48 defined in
“Online Message”. If not used, it should be filled with
the default value.
57 40 ans Name 61.6 O Optional. It should be filled with the default value if
not used.
97 2 n ID Type 61.1 O Optional. It should be filled with the default value if
not used.
99 20 ans ID 61.1 O Optional. It is the last six digits of the ID. Please refer
Number to the usage of AM in Field 61.6 defined in the
“online message”. If not used, it should be filled with
the default value.
119 40 ans Reserved O

Table 111 Block 3- Batch File Additional Information for MO/TO

Position Length Format Content Field I/O Description

0 4 n Message 0 O Ordering transaction includes MOTO purchase,
Type MOTO pre-authorization, MOTO authorization and
related transactions. The values for “message type”,

UPI CONFIDENTIAL 157

 Part III: File Interface

Position Length Format Content Field I/O Description

“processing code” and “point of service condition
code” in Block 0 are the same as those of Field 0,
Field 3, and Field 25 in the online message
respectively. The converted online message type
can be determined by the value of these fields.
0 6 n Processing 3 O It is the same as Field 3 in the online message.
Code Please refer to the definition of Field 3 in Appendix
B for MOTO transactions.
6 4 n Valid date 14 O Card valid period, optional, filled with default value
if not used.
10 40 ans Name 61.6 O Optional. It shall be filled with the default value if
not used.
50 2 n ID type 61.1 O Optional. It shall be filled with the default value if
not used.
52 20 ans ID number 61.1 O Optional. It is the last six digits of the ID. Please
refer to the usage of AM in Field 61.6 defined in the
online message. If not used, it shall be filled with
the default value/
72 20 ans Mobile 48 O Optional. It shall be filled with the default value if
phone not used.
number
92 40 ans Reserved O

UPI CONFIDENTIAL 158