0% found this document useful (0 votes)

132 views355 pages

Network Specifications - Instructions October 2019

Network Specifications_Instructions October 2019

Uploaded by

Natalie Gnoza

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

132 views355 pages

Network Specifications - Instructions October 2019

Network Specifications_Instructions October 2019

Uploaded by

Natalie Gnoza

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

AXgjbe^FcXV\Y\VTg\baf

<afgehVg\baf
BVgbUXe%#$,

GLOBAL NETWORK SERVICES

Confidential and Trade Secret Materials
This document contains sensitive, confidential, and trade secret information and
may not be disclosed to third parties without the prior written consent of American Express
Travel Related Services Company, Inc.

To the maximum extent permitted by law, American Express does not make and hereby disclaims any
and all representations, warranties, and liabilities, whether express or implied, or arising by law or
from a course of dealing or usage of trade, including implied warranties of merchantability or fitness
for a particular purpose or any warranty of title or non-infringement. Each Participant must comply
with laws and regulations applicable to the subject matter of this document. These laws and
regulations can differ from country to country, and each Participant is solely responsible for being
aware and adhering to them in all countries where applicable.

The policies, procedures, and rules in this manual are subject to change from time to time by
American Express Global Network Services.

© 2019 American Express Travel Related Services Co., Inc.

Network Specifications - Instructions

Table of Contents
Summary of Changes ...................................................................... xi
Chapter 1 Introduction ................................................................. 1-1
In This Introduction ......................................................................................... 1-1
About This Document ....................................................................................... 1-2
Chapter 2 American Express Global Network Services (AEGNS) ... 2-1
History ........................................................................................................... 2-1
Participant Roles .............................................................................................. 2-2
The Network ................................................................................................... 2-3
The Transaction Life Cycle ................................................................................. 2-4
Network Functionality..................................................................................... 2-12
Mandatory Network Functionality ..................................................................... 2-26
Feature-based Network Functionality ................................................................ 2-27
Contract Agreement Types .............................................................................. 2-28
Participant Profiles ......................................................................................... 2-29
Chapter 3 How To Use This Manual ............................................... 3-1
Document Layout ............................................................................................ 3-1
Formatting Standards Used in This Manual .......................................................... 3-2
How Message Fields are Defined ........................................................................ 3-3
How to Use Messages ....................................................................................... 3-9
Participant Responsibility ................................................................................ 3-16
Chapter 4 Network Cards .............................................................. 4-1
Issuer Responsibilities ...................................................................................... 4-1
Acquirer Responsibilities ................................................................................... 4-2
ISO 7813 Track 1 and 2 Formatting .................................................................... 4-3
ISO 7813 Standard Track 1 Layout ..................................................................... 4-4
ISO 7813 Standard Track 2 Layout ................................................................... 4-10
ISO 4909 Track 3 Formatting........................................................................... 4-14
ANSI X4.16 Track 1 and 2 Format .................................................................... 4-15
ANSI X4.16 Track 1 Layout.............................................................................. 4-16
ANSI X4.16 Track 2 Layout.............................................................................. 4-21
Test Cards .................................................................................................... 4-24
Primary Account Numbers (PAN)...................................................................... 4-25
Identifying Card Usage Parameters .................................................................. 4-27
Creating Personal Identification Numbers .......................................................... 4-28
Key Management ........................................................................................... 4-30
Zone Master Key............................................................................................ 4-38
Card Security Code Key (CSCK) ....................................................................... 4-39
CSC Generation ............................................................................................. 4-40
Personal Identification Number Key (PIN Key).................................................... 4-42
Card Identification Number File........................................................................ 4-44
Card Identification Number Header Record ........................................................ 4-46
Card Identification Number Detail Record .......................................................... 4-51
Card Identification Number Trailer Record ......................................................... 4-55
Emergency Card Replacements ........................................................................ 4-59
Chapter 5 Technical Certification .................................................. 5-1
What Is Certification? ....................................................................................... 5-1
Certification Phases Overview ............................................................................ 5-3

October 2019 Page i

Phase I: Unattended Testing.............................................................................. 5-6

Phase II: Telecommunication Connectivity Testing ................................................ 5-8
Phase III: Testing with AEGNS ........................................................................... 5-9
Certifying Issuers .......................................................................................... 5-11
Certifying Acquirers........................................................................................ 5-12
Feature Certification....................................................................................... 5-13
Role of the Network Test Simulator (NTS) in Certification .................................... 5-14
Chapter 6 Reporting Fraudulent Transactions ............................... 6-1
GNS Fraud Repository (GFR) ............................................................................. 6-1
Submitting Fraud Updates to the GFR ................................................................. 6-2
Network Response to Fraud Updates................................................................... 6-6
Fraud Reports ................................................................................................. 6-9
Fraud Reports Received Through the GLOBE ...................................................... 6-10
Submitting High Risk Indicators ....................................................................... 6-13
Accessing the High Risk S/E List ...................................................................... 6-14
Fraud Mitigation Tools..................................................................................... 6-15
Chapter 7 Reports ......................................................................... 7-1
Reports Delivery .............................................................................................. 7-1
Section 1 Program Progress Reports ................................................................ 7-4
Program Progress Reports................................................................................. 7-4
Card Statistics by Product ................................................................................. 7-6
Billings and Fees by Industry and Card Product .................................................... 7-9
Account Balances Outstanding, Write-offs, and Recoveries................................... 7-14
Membership Rewards Statistics by Product ........................................................ 7-17
Merchant Statistics by Industry........................................................................ 7-20
Local and Inbound Discount Business and Transactions by Industry ...................... 7-23
Section 2 Authorization Reports ..................................................................... 7-26
Authorization Reports ..................................................................................... 7-26
CAS Activity Summary – Authorizations Activity ................................................. 7-27
CAS Activity Summary by Point of Sale ............................................................. 7-33
CAS Activity Summary by S/E Type .................................................................. 7-35
CAS Activity Summary – Entry Activity ............................................................. 7-37
Authorization Transaction Edit Error Detail......................................................... 7-43
Unacknowledged Voids, Refunds, and Reversals Report ....................................... 7-45
Authorization Transaction Stand-In Detail.......................................................... 7-47
Authorization Deferred Payment Plan (DPP) Transaction Detail Report ................... 7-49
Authorization Transaction Detail ....................................................................... 7-51
Acquirer Detail .............................................................................................. 7-54
Exception Detail Report .................................................................................. 7-56
Authorization Decline Transaction Stand-In Detail Report..................................... 7-57
Authorization Referred Stand-In Detail Report.................................................... 7-59
Recurring Billing Cancellation Records Reports ................................................... 7-61
Section 3 Clearing and Settlement Reports .................................................... 7-63
Clearing and Settlement Reports...................................................................... 7-63
Daily Settlement Advisement........................................................................... 7-64
Daily Activity Report (DAR) ............................................................................. 7-65
External File Tracking Report ........................................................................... 7-71
Net Settlement Summary Report ..................................................................... 7-74
Gross Settlement Summary Report .................................................................. 7-77

Page ii October 2019

Network Fee Summary Report ......................................................................... 7-80

Issuer’s/Network Rate Amount Summary Report ................................................ 7-81
Current Day Activity - Warehoused Transactions................................................. 7-83
Accumulated Activity - Warehoused Transactions................................................ 7-84
Non-Financial Summary Report........................................................................ 7-85
Issuer’s/Network Rate Amount by Industry Segment Report ................................ 7-86
Non-Cleared Transaction Summary................................................................... 7-88
Returned Transaction Summary Report ............................................................. 7-89
Network Fee Summary by VBU Report .............................................................. 7-90
External Network Fee Detail Report .................................................................. 7-91
Pending Transaction Summary Report............................................................... 7-93
Section 4 Fraud Reports ................................................................................. 7-94
Fraud Reports ............................................................................................... 7-94
Fraud by Issuer and S/E Market ....................................................................... 7-96
Fraud by Issuer and Industry ......................................................................... 7-97
Fraud by Issuer, S/E Market, and Fraud Type ..................................................... 7-98
Issuer Gross Fraud Update .............................................................................. 7-99
Issuer Fraud Summary .................................................................................. 7-100
Non-Actioned Rejected Transaction Reports ...................................................... 7-102
Fraud by Acquirer and Cardmember Market ...................................................... 7-106
Fraud by Acquirer and Industry....................................................................... 7-107
Fraud by Acquirer, Cardmember Market, and Fraud Type .................................... 7-108
Acquirer S/E Fraud Summary Report ............................................................... 7-109
Acquirer S/E Fraud Detail Report..................................................................... 7-111
Top 40 S/Es 6 Month Summary Report............................................................. 7-113
Top 40 S/Es 6 Month Detail Report .................................................................. 7-114
Section 5 OpsNet Reports ............................................................................. 7-115
OpsNet Reports ............................................................................................ 7-115
Chapter 8 Instruction Documents ................................................. 8-1
More Instruction .............................................................................................. 8-1
Chapter 9 Acronyms ..................................................................... 9-1
Acronyms ....................................................................................................... 9-1
Chapter 10 Definitions ................................................................ 10-1
Definitions .................................................................................................... 10-1
Chapter 11 Index ........................................................................ 11-1

October 2019 Page iii

Page iv October 2019

List of Figures
Figure 1-1. Change Bar Example ............................................................................. 1-2
Figure 4-1. The Key Creation and Exchange Illustration ........................................... 4-34
Figure 6-1. Fraud Repository Update File Structure .................................................... 6-5
Figure 6-2. Fraud Repository Response File Structure ................................................ 6-7

October 2019 Page v

Page vi October 2019

List of Tables
Table [Link]...................................................................................... 2-5
Table [Link]............................................................................................. 2-6
Table [Link]......................................................................................... 2-7
Table [Link] ................................................................................................ 2-9
Table [Link] Authorization Messages for Acquirers ..................................... 2-13
Table [Link] Clearing and Settlement Messages for Acquirers ...................... 2-14
Table [Link] Reports for Acquirers ........................................................... 2-18
Table [Link] Authorization Messages for Issuers ........................................ 2-19
Table [Link] Clearing and Settlement Messages for Issuers ......................... 2-21
Table 2-10.
Available Reports for Issuers .............................................................. 2-24
Table 2-11.
Network Mandatory Functionality Requirements .................................... 2-26
Table 2-12.
AEGNS Contract Agreement Types ...................................................... 2-28
Table [Link] Lengths...................................................................................... 3-4
Table [Link] Optionality.................................................................................. 3-5
Table [Link] Formats ..................................................................................... 3-6
Table [Link] Path ..................................................................................... 3-8
Table [Link] to Use Messages .......................................................................... 3-9
Table [Link] Approval Process ....................................................................... 4-24
Table [Link] Check Digit Computation ............................................................. 4-26
Table [Link] Code Position Definitions......................................................... 4-27
Table [Link] Keys................................................................................ 4-30
Table [Link] Key Management Life Cycle ............................................. 4-31
Table [Link] Creation and Exchange Procedure (Exporting Participant)................. 4-34
Table [Link] Receiving and Loading Procedure (Receiving Participant).................. 4-36
Table [Link]/Working Key Exchange Procedure........................................ 4-37
Table [Link] Express CSC Supported Algorithms ....................................... 4-40
Table [Link] Certification Responsibilities.................................................. 5-2
Table [Link] Type Fields and Locations............................................................ 6-4
Table [Link] Identifier in Fraud Transactions............................................ 6-6
Table [Link] of Available Reports .............................................................. 7-1
Table [Link] Statistics by Product .................................................................... 7-7
Table [Link] and Fees by Industry and Card Product: Definitions ...................... 7-9
Table [Link] Balances Outstanding, Write-offs and Recoveries: Definitions...... 7-14
Table [Link] Rewards Statistics by Product: Definitions .......................... 7-17
Table [Link] Statistics by Industry: Definitions .......................................... 7-20
Table [Link] and Inbound Discount Business and Transactions by Industry:
Definitions....................................................................................... 7-23
Table 7-8. CAS Activity Summary – Authorizations Activity: Definitions ................... 7-27
Table 7-9. CAS Activity Summary by Point of Sale: Definitions ............................... 7-33
Table 7-10. CAS Activity Summary by S/E Type: Definitions .................................... 7-35
Table 7-11. CAS Activity Summary – Entry Activity: Definitions................................ 7-37
Table 7-12. Authorization Transaction Edit Error Detail: Definitions........................... 7-43

October 2019 Page vii

Table 7-13. Unacknowledged Voids, Refunds, and Reversals Report: Definitions ......... 7-45
Table 7-14. Authorization Transaction Stand-In Detail: Definitions............................ 7-47
Table 7-15. Authorization Deferred Payment Plan (DPP) Transaction Detail Report:
Definitions....................................................................................... 7-49
Table 7-16. Authorization Transaction Detail: Definitions ......................................... 7-51
Table 7-17. Acquirer Detail: Definitions................................................................. 7-54
Table 7-18. Exception Detail Report: Definitions..................................................... 7-56
Table 7-19. Authorization Decline Transaction Stand-In Detail: Definitions................. 7-57
Table 7-20. Authorization Referred Stand-In Detail: Definitions................................ 7-59
Table 7-21. Recurring Billing Cancellation Records Reports: Definitions ..................... 7-61
Table 7-22. Reports for Settlement/Reconciliation .................................................. 7-67
Table 7-23. Signage Reference ............................................................................ 7-67
Table 7-24. External File Tracking Report: Definitions ............................................. 7-71
Table 7-25. Net Settlement Summary Report: Definitions........................................ 7-74
Table 7-26. Net Settlement Summary Report: Definitions........................................ 7-75
Table 7-27. Net Settlement Summary Report: Definitions........................................ 7-75
Table 7-28. Gross Settlement Summary Report: Definitions..................................... 7-77
Table 7-29. Gross Settlement Summary Report: Definitions..................................... 7-78
Table 7-30. Gross Settlement Summary Report: Definitions..................................... 7-79
Table 7-31. Network Fee Summary Report: Definitions ........................................... 7-80
Table 7-32. Organization Division - Issuer’s/Network Rate Amount Summary Report:
Definitions....................................................................................... 7-81
Table 7-33. Issuer Division - Issuer’s Rate Amount Summary Report: Definitions ....... 7-82
Table 7-34. Acquirer Division - Network Rate Amount Summary Report: Definitions.... 7-82
Table 7-35. Current Day Activity - Warehoused Transactions: Definitions .................. 7-83
Table 7-36. Accumulated Activity - Warehoused Transactions: Definitions ................. 7-84
Table 7-37. Non-Financial Summary Report: Definitions .......................................... 7-85
Table 7-38. Organization Division - Issuer’s/Network Rate Amount by Industry
Segment Report: Definitions .............................................................. 7-86
Table 7-39. Issuer Division - Issuer’s Rate Amount by Industry Segment Report:
Definitions....................................................................................... 7-87
Table 7-40. Acquirer Division - Network Rate Amount by Industry Segment Report:
Definitions....................................................................................... 7-87
Table 7-41. Non-Cleared Transaction Summary: Definitions..................................... 7-88
Table 7-42. Returned Transaction Summary Report: Definitions ............................... 7-89
Table 7-43. Network Fee Summary by VBU Report: Definitions ................................ 7-90
Table 7-44. External Network Fee Detail Report: Definitions .................................... 7-91
Table 7-45. Pending Transactions Summary Report: Definitions ............................... 7-93
Table 7-46. Industry Categories........................................................................... 7-95
Table 7-47. Fraud by Issuer and S/E Market: Definitions ......................................... 7-96
Table 7-48. Fraud by Issuer and Industry: Definitions............................................. 7-97
Table 7-49. Fraud by Issuer, S/E Market, and Fraud Type: Definitions....................... 7-98
Table 7-50. Issuer Gross Fraud Update: Definitions ................................................ 7-99
Table 7-51. Issuer Fraud Summary: Definitions .................................................... 7-100

Page viii October 2019

Table 7-52. Non-Actioned Rejected Transaction Reports: Definitions ........................ 7-103

Table 7-53. Non-Actioned Rejected Transaction Reports: Definitions ........................ 7-104
Table 7-54. Fraud by Acquirer and Cardmember Market: Definitions ........................ 7-106
Table 7-55. Fraud by Acquirer and Industry: Definitions......................................... 7-107
Table 7-56. Fraud by Acquirer, Cardmember Market, and Fraud Type: Definitions...... 7-108
Table 7-57. Acquirer S/E Fraud Summary Report: Definitions ................................. 7-109
Table 7-58. Acquirer S/E Fraud Detail Report: Definitions ....................................... 7-111
Table 7-59. Top 40 S/Es 6 Month Summary Report: Definitions............................... 7-113
Table 7-60. Top 40 S/Es 6 Month Detail Report: Definitions .................................... 7-114

October 2019 Page ix

Page x October 2019

Summary of Changes
This table shows the changes to the Network Specifications -
Instructions manual.
Summary of Changes for Network Specifications - Instructions
Subject Revision First Publication Date
• Programming Notes The definition for Format Code has October 2019 Network Specification
for ISO 7813 Track 1 been updated to better reflect the - Instructions
on page 4-5 meaning as it applies to Track 1.
• Programming Notes
for ANSI X4.16 Track
1 on page 4-17
Chapter 9. Acronyms A new Acronyms chapter has been
on page 9-1 added.
Chapter 10. Definitions A new Definitions chapter has been
on page 10-1 added.

October 2019 xi

xii October 2019

Chapter 1 Introduction

In This Introduction

Overview The Network Specifications - Instructions manual contains:

• American Express Global Network Services (AEGNS) History
• How To Use This Manual
• Network Cards
• Global Online Business Exchange (GLOBE)
• Technical Certification
• Reporting Fraudulent Transactions
• Reports
• Instruction Documents

Who Must Use This Participants (Acquirers, Issuers) and Authorized Processors must
Manual know the function of each message, format, and data element
definition used on the Network.

October 2019 Page 1-1

About This Document

Publication Cycle The Network Specifications manuals and Codes Reference Guide will
be published two times each year, in April and October.
The Network Participant Updates (NPU) will be published on the
second Friday of each month and will include technical and code
changes.

Summary of Important changes are in the Summary of Changes on page xi.

Changes

Change Bars Change bars show new or changed text. Change bars are on the left
side of the page, adjacent to the new or changed text.

Figure 1-1. Change Bar Example

continued on next page

Page 1-2 October 2019

Trash Can Icon A trash can icon shows erased text.

Technical Change GNS Participants are told about technical changes at different times.
Notification
Type of Change When Participants are Told
Mandatory system/technical Six (6) months before the April or
change October effective date
Optional system/technical As necessary
change
Necessary legal change The notification and effective dates
are aligned with the legal and regu-
latory requirements
Reminders/information only When necessary

October 2019 Page 1-3

Page 1-4 October 2019

Chapter 2 American Express Global Network

Services (AEGNS)

History

AEGNS Since 1996, American Express has been pursuing a strategy of

opening its Service Establishment (S/E) network and card product
portfolio to financial institutions around the world. Through these
partnerships, AEGNS has more American Express Cards in the
market, more S/E coverage, and new products around the world.
AEGNS is a Network that includes financial service institutions
worldwide. These include:
• Banks or financial institutions that issue “Blue Box” Line Cards
that include the American Express logo and are accepted on the
American Express S/E Network
• Banks or financial institutions that have an exclusive license to
issue the Centurion Line of American Express Cards in a special
market where American Express does not offer a proprietary
local-currency card
• Institutions that acquire S/Es onto the American Express
Network

Goals AEGNS’ goals are to develop new and innovative products, features,
and services, assist in building new partnerships, and help
Participants increase their business.

October 2019 Page 2-1

Participant Roles

What is a Institutions that send or receive messages through the Network are
Participant? Participants. Participants can be:
• Acquirers
• Issuers
• Acquirers and Issuers

Acquirer Role Acquirers are entities who contract with S/Es, (also called
Merchants or Card Acceptors) to accept American Express-branded
Cards for goods and services, by agreement with AEGNS. ATM
Acquirers are entities that acquire Transactions from Cardmembers
at ATMs.
Acquirers have these responsibilities:
• Manage S/E risks
• Make sure S/Es are compliant
• Send Cardmember charges from the S/E to the Network
• Make payments to S/Es for Cardmember charges

Issuer Role The Network accepts Transactions from Issuers authorized by

AEGNS to issue Cards. Issuers are third parties who issue American
Express-branded Cards.
When an Issuer follows the minimum Card product quality and
standards of American Express, the Issuer can target defined
customer segments. Issuers can include their design on the Card.
Issuers have these responsibilities:
• Decide the criterion to issue Cards
• Manage the related credit risks
• Hold the receivables of the Cards

Page 2-2 October 2019

The Network

Overview The Network is a global communication system that transmits

authorization messages, clearing and settlement batch files, and
fraud repository update files.

AEGNS Services AEGNS has these services:

• Authorization support
• Clearing and Settlement
• Dispute procedures
• Fraud operations
• Value-added Network services

How Participants Participants send messages to the Network. The Network sends the
Use the Network messages to the correct recipient.

How the Network The Network uses these components to send and receive
Processes Data messages:
• The Acquirer system
• Acquirer Global Online Business Exchange (GLOBE)
• The Network
• Issuer GLOBE
• The Issuer system

October 2019 Page 2-3

The Transaction Life Cycle

Overview The Transaction life cycle shows the steps the Network and
Participants use to send Transactions.

Steps in the The Transaction life cycle has these steps:

Transaction Life 1. Authorization
Cycle
2. Clearing
3. Settlement
4. Fraud1
Refer to these sections for more instruction:
• Table 2-1 Authorization on page 2-5
• Table 2-2 Clearing on page 2-6
• Table 2-3 Settlement on page 2-7
• Table 2-4 Fraud on page 2-9
• Figure 2-1 Authorization and Clearing and Settlement
Transaction Life Cycle on page 2-8
• Figure 2-2 Fraud Transaction Life Cycle on page 2-11

Authorization Table 2-1 Authorization on page 2-5 describes step 1 of a

Transaction life cycle.
Refer to Authorization Processing and Authorization Messages in the
Network Specifications - Authorization manual for instructions.

continued on next page

[Link] fraud step only applies to Transactions where fraud is confirmed and
reported by the Issuer.

Page 2-4 October 2019

Table 2-1. Authorization

Step Description
1 Swipe an American Express-branded Card in a Point of Sale
(POS) device to purchase goods or services at an S/E or to
get cash at an Automated Teller Machine (ATM).
2 The POS device connects to its acquiring bank (Acquirer) and
sends an Authorization Request.
3 The Acquirer makes a POS Authorization Request (1100)
message and sends it to the Network.
4 The Network sends the POS Authorization Request (1100)
message to the Issuer.
5 The Issuer’s system uses internal authorization rules and
Cardmember data to make a POS Authorization Response
(1110) message.
Note: The Network can respond to the POS Authorization
Request (1100) message if it is standing in for the
Issuer.
6 The Issuer sends the POS Authorization Response (1110)
message to the Network.
7 The Network sends the POS Authorization Response (1110)
message to the Acquirer.
8 The Acquirer sends the POS Authorization Response (1110)
message to the S/E.
9 The Transaction is completed.

Refer to Clearing on page 2-6 and Settlement on page 2-7 for the
Clearing and Settlement life cycle.

Authorization Exceptions to the Transaction life cycle in Table 2-1 are:

Exceptions • Stand-In - The Network can respond to a POS Authorization
Request (1100) for an Issuer if a Stand-In situation occurs.
Stand-In is a set of parameters to approve Transactions when
the Network cannot contact the Issuer. For more instruction, see
Authorization Stand-In in the Network Specifications -
Authorization manual.

continued on next page

October 2019 Page 2-5

• Below Floor Limit Transactions - An Authorization Response

to the S/E from the Issuer or Network (during Stand-In) is not
required for Transactions with amounts below the Network Floor
Limit. The first time the Transaction goes across the Network is
the Acquirer’s First Presentment. For more instruction on Floor
Limits, refer to the Business and Operational Policies manual.

Clearing Table 2-2 describes step 2 of the Transaction Life Cycle. This
includes the Presentment and the Chargeback and Dispute
procedures.
Refer to the Clearing and Settlement and Financial Messages
chapters in the Network Specifications - Financial/Non-Financial
manual for instructions.

Table 2-2. Clearing

Step Description
1 After the POS Transaction is complete, the S/E submits the
Transaction data to their Acquirer for payment.
For an ATM Transaction, the Network makes the First Present-
ment message.
2 The Acquirer makes a POS First Presentment (1240) message
with the data from the S/E.
3 The Outclear Process
• The Acquirer collects all First Presentment messages, other
financial messages for American Express-branded Cards,
and these messages for Chargebacks and disputes:
• Retrieval Request
• Fulfillment Notification
• First Chargeback
• Second Presentment
• Final Chargeback
• The Acquirer makes a batch (Outclear) file.
• The Acquirer sends the batch file to the Network.
• The Network sends back a Network File Acknowledgment
(1844) message to the Acquirer to show that the batch file
was accepted.
Refer to the Clearing and Settlement chapter in the Network
Specifications - Financial/Non-Financial manual for more
instruction on Chargeback processing. Refer to Fraud on page
2-9 for instruction on the Transaction life cycle where fraud
has been confirmed and reported by the Issuer.

Page 2-6 October 2019

Table 2-2. Clearing (continued)

Step Description
4 The Inclear Process
• The Network makes cleared Transaction detail and sum-
mary records for each Issuer Institution Number (IIN).
• The Network puts records into a batch file for each IIN.
• The Network sends the batch (Inclear) file to each IIN.
• The institution that receives the batch file sends back a
Participant File Acknowledgment (1824) message to the
Network.
Rejected records and files are described in the Clearing and
Settlement chapter in the Network Specifications - Finan-
cial/Non-Financial manual.
5 The Issuer receives the batch file and continues with their
internal procedure and bills Cardmembers.
6 The Network makes the last Participant Inclear file for the
day.
7 The Network makes the Daily Activity Report.

Settlement Step 3 of the Transaction life cycle is Settlement.

Table 2-3. Settlement

Step Description
1 The Network sends the Daily Activity Report.
2 The Participant and the Network settle amounts owed.

Refer to the Clearing and Settlement and Financial Messages

chapters in the Network Specifications - Financial/Non-Financial
manual for instructions.

continued on next page

October 2019 Page 2-7

C L E A R I N G & S E T T L E M E N T
1. Cardmember
presents card at
Service Establishment
(S/E).
Establishment

2. Salesperson 3. Device connects

Service

9. S/E receives 10. After sale, S/E

tallies sale, swipes to its acquiring bank message from
Cardmember’s card and sends the submits transaction to
Acquirer Acquirer for payment
in POS device request.
Acquirer

4. The Acquirer formats 8. Acquirer receives 11. Using this information, Acquirer composes
A U TH O R I Z A T I O N

Authorization message a First Presentment message, adds to batch

an authorization request
(1100) and sends it to from Network and file and sends batch file for payment
forwards response to S/E (Outclear process).
the Network.

13. The Network opens batch file, sorts

12. Network receives batch records by Issuer Institution Identifier (IIN),
Network
AEGNS

file (First Presentment) and and combines records that pertain to each
5. Network forwards 7. Network forwards
returns an recipient into new batch files. The AEGN
message to Issuer response to Acquirer
acknowledgement file to the creates cleared transaction detail and
Acquirer, indicating its summary records, adds them to the file, and
acceptance of file. submits file to Issuers (Inclear process).

6. Issuer’s system checks

Issuer

Cardmember’s information and

formats authorization response Issuers
(1110) and sends response
back through the Network

Figure 2-1. Authorization and Clearing and Settlement Transaction Life Cycle

continued on next page

October 2019 Page 2-8

Fraud Table 2-4 Fraud describes step 4 of a Transaction life cycle.

Refer to Chapter 6 Reporting Fraudulent Transactions on page 6-1
and the Data Collection Messages chapter in the Network
Specifications - Financial/Non-Financial manual for instructions.

Table 2-4. Fraud

Step Description
1 After an Issuer bills a Cardmember, the Cardmember can dis-
pute the Transaction as fraudulent and report it to the Issuer.
The Issuer sends the data to the Network in the Fraud Repos-
itory Update Record (9324) message. The Network sends
back a Fraud Repository Response (9334) message to the
Issuer.
2 The Issuer sends a Retrieval Request Notification (1642) to
the Network to get first presentment Transaction data from
the Acquirer, if necessary.
3 The Acquirer sends back a Fulfillment Notification (1640)
message with Transaction documentation.
4 The Issuer receives the fulfillment and sends a First Charge-
back (1442) message to the Network. The Network sends the
First Chargeback (1442) message to the Acquirer.
The Network examines the GNS Fraud Repository for a fraud
Transaction with the same Transaction Identifier (TID) as the
Chargeback record. The Network updates the liability status.
5 The Acquirer can send a Second Presentment (1240) to the
Issuer through the Network, to try to receive payment for the
Transaction.
Note: If the Acquirer does not send a Second Presentment,
the Fraud Transaction Life Cycle ends.
The Network examines the GNS Fraud Repository for a fraud
Transaction with the same TID as the Second Presentment
record. The Network updates the liability status.
6 The Issuer receives the Second Presentment (1240) and can
send a Final Chargeback (1442) to the Network. The Network
sends the Final Chargeback to the Acquirer.
The Network examines the GNS Fraud Repository for a fraud
Transaction with the same TID as the Final Chargeback
record. The Network updates the liability status.
7 If the S/E disagrees with the Chargeback, a Dispute Resolu-
tion (written filing) can be started.
An Arbitration Case goes through the Network to the Issuer
for possible resolution.
The GNS Fraud Repository is updated with the Arbitration
Results.

continued on next page

October 2019 Page 2-9

Reference Material Refer to the Business and Operational Policies manual for more
instruction on the Dispute process.

continued on next page

Page 2-10 October 2019

5. Acquirer receives
3. Upon receipt of 7. Acquirer can either
chargeback and may send a
request, Acquirer accept Chargeback or
Second Presentment (1240) to
submits Fulfillment submit an arbitration
the Issuer. (If not , the Fraud
Notification (1640) (written filing)
Transaction Lifecycle ends.)
NETWORK

6.1 Network
AEGNS

3.1 Network
2.1 Network forwards 4.1 Network forwards 5.1 Network forwards forwards 7.1. Arbitration goes
forwards Fulfillment
Retrieval Request First Chargeback Second Presentment Chargeback through
Notification (1640)
(1642 ) to Acquirer (1442) to Acquirer (1240) to Issuer Notification record Network to Issuer
to Issuer
(1442) to Acquirer
REPOSITORY (GFR)

1.1 Fraud Repository 5.1.1 Fraud

4.1.1 Fraud 6.1.1 Fraud 7.1.1 Fraud
FRAUD

updated (9324). Sends Repository

Repository Repository Repository
Fraud Repository is updated to reflect
is updated to reflect is updated to is updated with
Response message to Second
chargeback reflect final Arbitration results
Issuer (9334). Presentment chargeback
ISSUER

1. Issuer bills Cardmember 4. Issuer receives 6. Issuer receives 1240 7.2 Issuer
(CM) and receives CM 2. Issuer outclears Fulfillment and raises a Second Presentment Receives a copy
dispute. Populates Fraud Retrieval request to chargeback. Issuer and raises Final Fraud of the arbitration
Repository Update Record Network (1642). outclears First Chargeback (1442) case
(9324) with information. Chargeback (1442) to the
Network .

Figure 2-2. Fraud Transaction Life Cycle

October 2019 Page 2-11

Network Functionality

Overview This section shows the Network messages (and optionality) and
message functionality available on the Network. Certification
requirements are listed, if applicable. Refer to Field Optionality on
page 3-5 for optionality definitions.

Acquirer This section lists messages and associated functionality for

Functionality Acquirers.

continued on next page

Page 2-12 October 2019

Table 2-5. Available Authorization Messages for Acquirers

Acquirer Certification
Message Functionality Notes
POS | ATM Required
1100/1110 POS Authorization and M N/A Yes
Response Message
Cash Disbursement M N/A Yes Only Issuers who are new to the Acquirer role must certify.
All other Participants must only test for the feature.
Chip Card Processing C N/A Yes
Printed Card Security Code (PCSC) C N/A Yes Acquirers must be certified to send 3 and/or 4 byte lengths.
Market Specific Data C N/A Yes
DPP During Stand-In C N/A No
Deferred Payment Plan (DPP) O N/A Yes
Automated Address Verification O N/A Yes
Transaction Identifier (TID) M N/A Yes
Online PIN Cardholder Verification O N/A Yes Acquirers certified for Online PIN must be able to accept and
Method send the PIN data when captured at the Card Acceptor’s ter-
minal.
1120/1130 POS Authorization O N/A Yes
Advice and Response
Market Specific Data C N/A Yes
Transaction Identifier (TID) M N/A Yes
1220/1230 POS Authorization Authorization Adjustment Capability O N/A Yes
Adjustment Financial Advice
1200/1210 ATM Financial N/A M Yes
Transaction Request and Response
Global PIN Management N/A C Yes
Market Specific Data N/A C Yes
Chip Card Processing N/A O Yes
1420/1430 Reversal Advice and M M Yes
Response
Global Pin Management N/A O Yes
Market Specific Data C C Yes
Transaction Identifier (TID) M C Yes
ATM Reconciliation N/A M Yes

October 2019 Page 2-13

Table 2-5. Available Authorization Messages for Acquirers (continued)

Acquirer Certification
Message Functionality Notes
POS | ATM Required
1804/1814 Network Management M M Yes
Request/ Response

Table 2-6. Available Clearing and Settlement Messages for Acquirers

Acquirer Certificatio
Message Functionality Notes
POS | ATM n Required
9824/9825 File Header/Trailer M M Yes
1824 Participant Acknowledgment M M Yes
File
1844 Network File M M Yes
Acknowledgment
1240 First and Second FP - M FP - N/A* Yes * ATM First Presentments are not outcleared by Acquirers to
Presentment SP - M SP - M the Network. ATM Second Presentments outclear from the
Acquirer to the Network and Inclear from the Network to the
Issuer.
Zip Code Verification (ZCV) C N/A No This feature is limited to the USA and Puerto Rico only if
received from a participating S/E.
PCSC Validation C N/A No This feature is limited to the USA, Canada, and Puerto Rico
only if received from a participating S/E
Transaction Identifier (TID) FP - M FP - N/A* Yes *A unique number given by the Network to identify a
SP - ME SP - ME Cardmember Transaction throughout its life cycle.

Promotional Program Transactions C N/A No The Network will submit POS First Presentment (1240)
messages with Processing Codes 027908 Debit Promotional
Program Transaction and 227908 Credit Promotional Program
Transaction on behalf of the Acquirer in designated markets.
1244 Promotional Program Debit Promotional Program Transactions C N/A Yes Acquirers receive the Promotional Program Debit File (1244)
File message from the Network. The message shows that a POS
First Presentment (1240) message with award Transactions
was sent to an Issuer.
1642 Retrieval Request Notification M M Yes
Zip Code Verification (ZCV) C N/A No This feature is limited to the USA and Puerto Rico only if
received from a participating S/E.

October 2019 Page 2-14

Table 2-6. Available Clearing and Settlement Messages for Acquirers (continued)
Acquirer Certificatio
Message Functionality Notes
POS | ATM n Required
PCSC Validation C N/A No This feature is limited to the USA, Canada, and Puerto Rico
only if received from a participating S/E
1640 Fulfillment Notification M M Yes
Zip Code Verification (ZCV) C N/A No This feature is limited to the USA and Puerto Rico only if
received from a participating S/E.
PCSC Validation C N/A No This feature is limited to the USA, Canada, and Puerto Rico
only if received from a participating S/E
1442 First and Final Chargeback M M Yes
Zip Code Verification (ZCV) C N/A No This feature is limited to the USA and Puerto Rico only if
received from a participating S/E.
PCSC Validation C N/A No This feature is limited to the USA, Canada, and Puerto Rico
only if received from a participating S/E
1644 Daily Activity File O O Yes
1744 Fee Collection M M Yes
1740/1742 ATM Fees N/A C Yes
9240 Industry Specific Addenda Yes
Airline M N/A Yes
Auto Rental M N/A Yes
Communication Services M N/A Yes
Retail M N/A Yes
Entertainment/Ticketing M N/A Yes
General Format M N/A Yes
Insurance M N/A Yes
Lodging M N/A Yes
Rail M N/A Yes
Restaurant M N/A Yes
Travel/Cruise M N/A Yes
9240 Double Byte Character C N/A Yes
9240 Market Specific Data C N/A Yes
Addendum
9240 Deferred Payment Plan C N/A Yes
Addendum
9240 Chip Card Addendum C C Yes

October 2019 Page 2-15

Table 2-6. Available Clearing and Settlement Messages for Acquirers (continued)
Acquirer Certificatio
Message Functionality Notes
POS | ATM n Required
9240 Corporate Purchasing Card O N/A Yes
Transaction Detail
9844/9845 Data Collection M N/A Yes
Header/Trailer
9640 S/E Demographics M N/A Yes
1340 On Us POS First and Second M (FP) N/A Yes (FP) Certification is required for the On Us POS First Presentment
Presentment O (SP) No (SP) (1340) message for Participants that own the Cardmember
and S/E relationships or process On Us Transactions, including
Transactions of Multinational Accounts service by the
Participants.
Certification is recommended for the On Us POS Second
Presentment (1340) message for Participants that own the
Cardmember and S/E relationships or process On Us
Transactions, and Transactions of Multinational Accounts
serviced by the Participant.
Note: AEGNS will tell Acquirers if they must certify for and
send the On Us POS Second Presentment (1340)
message.
1340 On Us ATM First and Second N/A M Yes Certification required for Participants that own the
Presentment Cardmember and Service Establishment relationships or
process On Us Transactions.
1340 On Us First and Final O M No Certification is recommended for Participants that own the
Chargeback Notification Cardmember and Service Establishment relationships or
process On Us Transactions.
Note: AEGNS will tell Acquirers if they must certify for and
send this message.
9340 Industry Specific Addenda O N/A Yes
Airline O N/A Yes
Auto Rental O N/A Yes
Communication Services O N/A Yes
Retail O N/A Yes
Entertainment/Ticketing O N/A Yes
General Format O N/A Yes
Insurance O N/A Yes
Lodging O N/A Yes

October 2019 Page 2-16

Table 2-6. Available Clearing and Settlement Messages for Acquirers (continued)
Acquirer Certificatio
Message Functionality Notes
POS | ATM n Required
Rail O N/A Yes
Restaurant O N/A Yes
Travel/Cruise O N/A Yes
9340 Deferred Payment Plan O N/A Yes
Addendum
9344 Program Specific O O Yes
ATM Location List N/A O Yes
Acquirer S/E Fraud Detail O O No

continued on next page

October 2019 Page 2-17

Table 2-7. Available Reports for Acquirers

Acquirer Certification
Message Functionality
POS | ATM Required
Clearing & Settlement Reports
Daily Settlement Advisement M M Yes
Daily Activity Report M M Yes
Authorizations Reports Yes
Acquirer Detail Report (daily) M N/A Yes
Fraud Reports 9644 Fraud Report M M Yes
Fraud by Issuer and S/E Market
(monthly)
Fraud by Issuer and Industry
(monthly)
Fraud by Issuer, S/E Market and
Fraud Type (monthly)
Issuer Gross Fraud Update
(monthly)
Issuer Fraud Summary (monthly)
Non-Actioned Rejected Transaction
Reports (monthly)
Fraud by Acquirer and Cardmember
Market (monthly)
Fraud by Acquirer and Industry
(monthly)
Fraud by Acquirer, Cardmember
Market, and Fraud Type (monthly)
Acquirer S/E Fraud Summary
Report (semimonthly)
Acquirer S/E Fraud Detail Report
(semimonthly)
Top 40 S/Es 6 Month Summary
Report (semiannually)
Top 40 S/Es 6 Month Detail Report
(semiannually)

Issuer This section lists the messages and functionality for Issuers.
Functionality
continued on next page

Page 2-18 October 2019

Table 2-8. Available Authorization Messages for Issuers

Issuer Certification Notes
Message Functionality
POS ATM Required
1100/1110 POS Authorization and M N/A Yes
Response Message
Host Stand-In M N/A No
Remote Stand-In O N/A No
Deferred Payment Plan (DPP) O N/A Yes
DPP During Host Stand-In C N/A No
Voice Referral Handling O N/A Yes
Automated Address Verification O N/A Yes
Chip Card Processing C N/A Yes
Cash Disbursement M N/A Yes
Printed Card Security Code (PCSC) C N/A Yes Issuers must be certified to receive 3 and/or 4 byte length.
Market Specific Data C N/A Yes
Fraud Probability Score O N/A Yes
Recommendation Code O N/A Yes
5CSC Validation of POS Financial O N/A Yes
Transactions
Transaction Identifier (TID) O N/A Yes
Online PIN Cardholder Verification O N/A Yes Issuers certified for this feature must be able to receive, ver-
Method ify, and reply to a POS Authorization Request (1100) mes-
sage when the PIN data is sent from an Acquirer through the
Network.
1120/1130 POS Authorization M N/A Yes
Advice and Response
Market Specific Data C N/A Yes
Fraud Probability Score O N/A Yes
Recommendation Code O N/A Yes
5CSC Validation of POS Financial O N/A Yes
Transactions
Transaction Identifier (TID) O N/A Yes
1200/1210 ATM Financial N/A M Yes
Transaction Request and Response
Multiple ATM Settlement Currency N/A O Yes

October 2019 Page 2-19

Table 2-8. Available Authorization Messages for Issuers (continued)

Issuer Certification Notes
Message Functionality
POS ATM Required
Global PIN Management N/A C Yes
5CSC Validation of ATM Financial N/A O Yes
Transactions
Chip Card Processing N/A C Yes
Market Specific Data N/A C Yes
1220/1230 POS Authorization Authorization Adjustment Capability O N/A Yes
Adjustment Financial Advice
1420/1430 Reversal Advise and M M Yes
Response
Market Specific Data C C Yes
Transaction Identifier (TID) C O Yes
Global Pin Management N/A O Yes
Multiple ATM Settlement Currency N/A O Yes
1804/1814 Network Management M M Yes
Request/ Response
1304/1314 Real Time Exception O N/A Yes
Updates
Exception File M M Yes This feature is for Stand-In or Issuers that use GNSAS to
authorize their Transactions.

continued on next page

October 2019 Page 2-20

Table 2-9. Available Clearing and Settlement Messages for Issuers

Issuer Certification
Message Functionality Notes
POS ATM Required
9824/9825 File Header/Trailer M M Yes
1824 Participant Acknowledgment M M Yes
File
1844 Network File Acknowledge- M M Yes
ment
1240 First and Second Presentment M M Yes
Zip Code Verification (ZCV) C N/A No This feature is limited to the USA and Puerto Rico only if
received from a participating S/E.
PCSC Validation C N/A No This feature is limited to the USA, Canada, and Puerto Rico
only if received from a participating S/E.
Transaction Identifier (TID) M M Yes
Promotional Program Transactions M N/A Yes Issuers who choose to participate in designated markets
must receive POS First Presentment (1240) messages with
Processing Codes 027908 Debit Promotional Program
Transaction and 227908 Credit Promotional Program
Transaction.
If the Issuer is not certified for the feature, a Cardmember
cannot enroll for a Promotional Program campaign.
1642 Retrieval Request Notification M M Yes
Zip Code Verification (ZCV) C N/A No This feature is limited to the USA and Puerto Rico only if
received from a participating S/E.
PCSC Validation C N/A No This feature is limited to the USA, Canada, and Puerto Rico
only if received from a participating S/E.
Transaction Identifier (TID) M M Yes
1640 Fulfillment Notification M M Yes
Zip Code Verification (ZCV) C N/A No This feature is limited to the USA and Puerto Rico only if
received from a participating S/E.
PCSC Validation C N/A No This feature is limited to the USA, Canada, and Puerto Rico
only if received from a participating S/E.
Transaction Identifier (TID) M M Yes
1442 First and Final Chargeback M M Yes
Zip Code Verification (ZCV) C N/A No This feature is limited to the USA and Puerto Rico only if
received from a participating S/E.

October 2019 Page 2-21

Table 2-9. Available Clearing and Settlement Messages for Issuers (continued)
Issuer Certification
Message Functionality Notes
POS ATM Required
PCSC Validation C N/A No This feature is limited to the USA, Canada, and Puerto Rico
only if received from a participating S/E.
Transaction Identifier (TID) M M Yes
Daily Activity File (1644) O O Yes
1744 Fee Collection M M Yes
1740/1742 ATM Fees N/A C Yes
9240 Industry Specific Addenda Yes
Airline M N/A Yes
Auto Rental M N/A Yes
Communication Services M N/A Yes
Retail M N/A Yes
Entertainment/Ticketing M N/A Yes
General Format M N/A Yes
Insurance M N/A Yes
Lodging M N/A Yes
Rail M N/A Yes
Restaurant M N/A Yes
Travel/Cruise M N/A Yes
9240 Extended Financial Addendum C N/A Yes
9240 Double Byte Character C N/A Yes
9240 Market Specific Data C N/A Yes
Addendum
9240 Deferred Payment Plan C N/A Yes
Addendum
9240 Chip Card Addendum C C Yes
9240 Corporate Purchasing Card C N/A Yes
Transaction Detail
9844/9845 Data Collection M M Yes
Header/Trailer
9324 Fraud Update/9334 Fraud M M Yes
Response Record
Transaction Identifier (TID) O O Yes

October 2019 Page 2-22

Table 2-9. Available Clearing and Settlement Messages for Issuers (continued)
Issuer Certification
Message Functionality Notes
POS ATM Required
1340 On Us POS First and Second N/A M No Certification is required for the On Us POS First Presentment
Presentment (1340) message for Participants that own the Cardmember
and S/E relationships or process On Us Transactions,
including Transactions of Multinational Accounts service by
the Participants.
Certification is recommended for the On Us POS Second
Presentment (1340) message for Participants that own the
Cardmember and S/E relationships or process On Us
Transactions, and Transactions of Multinational Accounts
serviced by the Participant.
Note: AEGNS will tell Acquirers if they must certify for and
send the On Us POS Second Presentment (1340)
message.
1340 On Us ATM First and Second N/A M Yes Certification required for Participants that own the
Presentment Cardmember and Service Establishment relationships or
process On Us Transactions.
1340 On Us First and Final O M No Certification recommended for Participants that own the
Chargeback Cardmember and Service Establishment relationships or
process On Us Transactions.
Note: AEGNS will tell Acquirers if they must certify for and
send this message.
9344 Program Specific O O Yes
Batch Exception Update and M M Yes
Response
Chip Card Request C C Yes

continued on next page

October 2019 Page 2-23

Table 2-10. Available Reports for Issuers

Issuer Certification
Message Functionality
POS ATM Required
Clearing & Settlement Reports
Daily Settlement Advisement M M Yes
Daily Activity Report M M Yes
Authorizations Reports Yes
CAS Activity Summary Report M N/A Yes
(monthly) (4)
Authorization Transaction Edit Error M N/A Yes
Detail (daily)
Unacknowledged Voids, Refunds M N/A Yes
and Reversals Report (daily)
Authorization Transaction Detail M N/A Yes
Report (daily)
Authorization Transaction Stand-In M N/A Yes
Detail Report (daily)
Authorization DPP Transaction M N/A Yes
Detail Report (daily) (for DPP
only)
Exception Detail Report (monthly) O N/A Yes
Acquirer Detail Report (daily) N/A N/A Yes
Authorization Decline Transaction O N/A No
Stand-in Detail Report (monthly)
Authorization Referred Stand-In O N/A No
Detail Report (monthly)
Recurring Billing Cancellation M N/A No
Records Report (monthly) - Active (for Issuers
certified for
the Recur-
ring Billing
Cancella-
tion Ser-
vice)
Recurring Billing Cancellation M N/A No
Records Report (monthly) - (for Issuers
Changed and Deleted certified for
the Recur-
ring Billing
Cancella-
tion Ser-
vice)
Preferred Delinquent File M N/A Yes
Fraud Reports 9644 Fraud Report M M Yes
Fraud by Issuer and S/E Market
(monthly)
Fraud by Issuer and Industry
(monthly)
Fraud by Issuer, S/E Market and
Fraud Type (monthly)

Page 2-24 October 2019

Table 2-10. Available Reports for Issuers (continued)

Issuer Certification
Message Functionality
POS ATM Required
Issuer Gross Fraud Update
(monthly)
Issuer Fraud Summary (monthly)
Non-Actioned Rejected Transaction
Reports (monthly)
Fraud by Acquirer and Cardmember
Market (monthly)
Fraud by Acquirer and Industry
(monthly)
Fraud by Acquirer, Cardmember
Market, and Fraud Type (monthly)
Acquirer S/E Fraud Summary
Report (semimonthly)
Acquirer S/E Fraud Detail Report
(semimonthly)
Top 40 S/Es 6 Month Summary
Report (semiannually)
Top 40 S/Es 6 Month Detail Report
(semiannually)

Page 2-25 October 2019

Mandatory Network Functionality

Participant Participants must implement and support all mandatory (core)

Responsibilities functionality requirements of the Network.
Mandatory functionality is defined for each Participant during the
implementation, certification, and feature certification processes.

Mandatory Refer to Table 2-11 for a description of the mandatory

Functionality requirements.

Table 2-11. Network Mandatory Functionality Requirements

Process Description
Authorization Process- The process to get an online approval for a
ing chapter in the Net- POS or ATM Request. Participants send single
work Specifications - online/real time messages to request authori-
Authorization manual zation and respond to Authorization Requests.
The Network routes each message to the cor-
rect recipient and sends the response back to
the Acquirer.
Clearing and Settlement The process of sending Transaction data to get
chapter in the Network payment or establish billing for Cardmembers.
Specifications - Finan- • The clearing process routes, edits, and
cial/Non-Financial man- summarizes Transactions.
ual
• The settlement process calculates the
amounts owed to and from AEGNS. These
amounts are exchanged.
Chapter 6 Reporting The process of exchanging data about fraudu-
Fraudulent Transactions lent Transactions on the Network. The Net-
on page 6-1 work stores these messages and uses the
data to create fraud reporting.

Page 2-26 October 2019

Feature-based Network Functionality

Overview Feature-based functionality lets Participants select system features

that are necessary for their business.

What Is Included? Feature-based Network functionality includes infrastructure

developments such as new products and services, changes to
existing messages, and hardware or application changes.

Optionality Features described in this manual can be mandatory or optional.

Mandatory certification dates for features are communicated six
months in advance of the feature.
Optional features can become mandatory if they are necessary for
important business functions. AEGNS tells Participants about
necessary certification dates, if a feature becomes mandatory.

Complete List For a list of mandatory and feature-based Network functionality,

refer to Network Functionality on page 2-12.

October 2019 Page 2-27

Contract Agreement Types

Overview AEGNS does business with these entities.

Table 2-12. AEGNS Contract Agreement Types

Contract Type Description

Independent Opera- A Participant who not only issues American
tor Express Card products but is also an S/E Acquirer
and processor.
Joint Venture A third party institution that works with American
Express to set up a separate business to acquire
S/Es and/or issue cards.
NCL (Network Card American Express gives an institution a license to
License) issue cards accepted on the American Express S/E
network.
Acquirer Acquires S/Es to let Cardmembers purchase
goods and services with the American Express
Card

Page 2-28 October 2019

Participant Profiles

Participant Profile The Participant Profile contains the features the Participant supports
and the operational parameters (such as preferred currency). The
Participant Profile has this data:
• Institution IDs necessary for routing
• How a Participant receives reports
• Timing of reports
• Presentment and settlement currencies
• Issuer’s/Network rates
• Foreign Currency Factors

Participant Profile The Network uses the Participant Profile to make a decision to send
Use Transactions to a Participant.
Example: The Network sends Authorization Requests that have
Deferred Payment Plan (DPP) data only to Issuers certified to use
DPP.

Participant Profile AEGNS updates the Participant Profile when a Participant certifies
Updates for a new feature.

October 2019 Page 2-29

Page 2-30 October 2019

Chapter 3 How To Use This Manual

Document Layout

Document Naming Network Specifications manuals consist of three separate,

content-specific manual:
• Network Specifications - Authorization
• Network Specifications - Financial/Non-Financial
• Network Specifications - Instructions

Use of Italics Italics are used when the complete title of the manual is referenced.
For example: Network Specifications - Authorization, Network
Specifications - Financial/Non-Financial, or Network Specifications -
Instructions.
Note: References to Network Specifications manuals is inclusive of
all three manuals and is not italicized.

October 2019 Page 3-1

Formatting Standards Used in This Manual

Date A date value is stored in the format CCYYMMDD, where:

• CC = Century, 00 through 99
• YY = Year, 00 through 99
• MM = Month, 01 through 12
• DD = Day, 01 through 31
Note: For optional fields the initialization value is “00010101.”

Time A time value is stored in the format HHMMSS, where:

• HH = Hour, 00 through 23
• MM = Minute, 00 through 59
• SS = Second, 00 through 59
Note: The default value is six zeros.

Amount Each amount field has a related currency code and currency
decimalization field. Do not keep decimals in amount fields. If
decimals must be kept in amount fields, it is specified in the
description of a field.

Hash Amount A hash amount field stores an accumulation of all numbers. There
are no signs or decimals.

Debit/Credit The amount that is a debit or credit to the Participant’s account,

Amount based on the Processing Code in the message.

Page 3-2 October 2019

How Message Fields are Defined

Overview Network messages are based on International Organization for

Standardization (ISO) 8583 Financial Transaction Card Originated
Message – Interchange Message Specifications.

Binary Binary data is used in special circumstances, such as storing data

about the Transaction in Integrated Circuit Card (ICC) System
Related Data (e.g., Bit 55 in Authorization messages and Field 4 in
Chip Card Addenda messages).
• Eight bit blocks
• Right justified
• Left zero-filled

Binary Numeric Data items with numeric formats have 2 digits for each byte (00 to
99). Each digit is stored on 4 bits (1 nibble) resulting in each byte
storing 2 digits.
Example: A date field containing the numerics representing the
date November 30, 2006 in YYMMDD format is a three byte field
holding the six digits “061130.” A numeric field with an odd number
of digits is always padded with a leading zero (0) before packing.

Binary Data items with Binary formats have 8 bits for each byte. The value
(Hexadecimal) for binary bytes of data can change from hexadecimal “0” to
hexadecimal “F.”

continued on next page

October 2019 Page 3-3

Field Lengths Table 3-1 shows the types of field lengths used by the Network
messages. The descriptions apply to all fields unless specified
differently.

Table 3-1. Field Lengths

Length Description
Fixed Fixed Length fields contain data that is always the
same number of bytes.
Variable Variable Length fields contain data of different
lengths up to the maximum length. These fields
are shown by:
• LLVAR with a 2-digit variable length indicator
(00 to 99), preceding the field and identifying
the field length.
• LLLVAR with a 3-digit length indicator (000 to
999) preceding the field and identifying the field
length.
Note: The variable length indicator is not
included in the field length unless shown in
the message layout.

Variable Length Variable length subfields in Bit 55 of the Authorization messages

Subfields have the length (LL or LLL) encoded in binary. There is one more
byte in Bit 55 for LLVAR and LLLVAR fields.
Examples:
1. Data Subfield 2 in the POS Authorization Request (1100) mes-
sage: Issuer Application Data: LLVAR. The length byte occu-
pies 1 byte of storage, (for example, length 7 in binary is
00000111).
2. Data Subfield 1 in the POS Authorization Response (1110)
message: Issuer Authentication Data: LLVAR. The length byte
occupies 1 byte of storage, (for example, length 10 in binary
is 00001010).
3. Data Subfield 2 in the POS Authorization Response (1110)
message: Issuer Script Data: LLVAR. The length byte occupies
1 byte of storage, (for example, length 128 in binary is
10000000).
Participants should include length bytes to format or process Bit 55.

continued on next page

Page 3-4 October 2019

Field Optionality Each field (data element) includes optionality to show if it must be
present. The types of optionality are described in this table.

Table 3-2. Field Optionality

Optionality Description
Mandatory (M) Data is required to process this message. The
field must contain the applicable text or numeric
data.
Mandatory Echo Data is echoed from a message before.
(ME)
Conditional (C) Data must be present if the condition described is
true.
Conditional Echo Data is echoed, if it was in the message that was
(CE) received.
Optional (O) Data is not mandatory for processing the mes-
sage, but should be supplied if available. For
Financial messages and Data Collection mes-
sages, the default characters for a text field is
spaces and for a numeric field, zeros. For Authori-
zation messages, if the field is optional and the
data is not available, the bitmap position should
be set to zero and the field should not be sent.
Optional Echo (OE) Data is echoed if included in a previous message.
Filler (F) Filler fields show positions in a message that are
not used, but must contain default values
described in the programming notes section.
Numeric fields must contain zero(s).
Alphanumeric fields must contain spaces.
Reserved Field A field reserved by AEGNS for internal use.
Numeric fields must contain zeros. Alphanumeric
fields must contain spaces.
Not Applicable Do not send this field.
(N/A)

continued on next page

October 2019 Page 3-5

Data Formats Table 3-3 shows the data formats used in Network messages.

Table 3-3. Data Formats

Data Formats Description
Numeric - (9(X) or • Numeric digits 0 through 9
N(X): • Right justified
• 9 or N = numeric • Default is zeros
• (X) = number of • Filler fields must be initialized to zeros
positions
Implied decimal A decimal point is implied, but not stored, in a
specific location in a field. The location of the
implied decimal is described with a “v”.
Example: 9(6)v9(8). This example shows 6
digits, a decimal point, then 8 digits.
Alphanumeric - X(X) Note: All alphanumeric data must be sent in
or AN(X): EBCDIC 500 format unless specified
• X or AN = alphanu- differently.
meric • Alphabetical characters A through Z and a
through z, numeric, and special characters
• (X) = number of
positions • Left justified
• Space-filled
• Default is spaces
• Filler fields must be initialized to spaces
Note: English alphabet characters are the
only alphabetical characters that can be
used, as the diacritical marks
commonly used in the addresses of
non-English speaking countries are not
recognized.
Binary (B) Binary data is used in special circumstances, to
store data about the Transaction in ICC System
Related Data (Bit 55)
• Base 2 (0 and 1)
• Eight bit blocks
• Right justified
• Left zero-filled
Hexadecimal • Base 16 (numeric digits 0 through 9 and the
Hexadecimal or Hex letters A through F)
• Two bit blocks
Special Character • Special characters (for example:%,?, ^, #)
ANS in the message • Left justified
layouts for alphanu- • Space-filled
meric fields that have
special characters • Default is spaces
• Filler fields must be initialized to spaces

Page 3-6 October 2019

Table 3-3. Data Formats (continued)

Data Formats Description
Tilde (~) • This symbol is used in a numeric or
alpha-numeric format to show a space (for
example: XX~)
Graphic (G) A graphic field has two bytes of data that rep-
resent each graphic character, or double byte
character, used for specific languages (e.g.,
Japanese Kanji).
Group A group field contains two or more subfields,
each of which have a separate meaning (e.g.,
Interest Rate and Number of Installments can
be kept in a Deferred Payment Plan group
field).

Bit 55 Subfield Data present in subfields in Bit 55 that originate from the Chip Card
Format or Terminal must be translated into binary data to agree with the
format of the data in the Card or terminal as follows:
• Data items with a format defined as Numeric are translated as
packed decimal, with 2 digits for each byte (“00” to “99”). A
numeric field with an odd number of digits is always padded with
leading zero(s).
• Data items with a format defined as Binary are mapped directly
as 8 bits for each byte with the value for binary bytes of data
varying from hexadecimal “0” to hexadecimal “F.”
Note: These Card or terminal data formats are defined in the
AEIPS Chip Card Specification and the AEIPS Terminal
Technical Manual on Knowledge Base. Use the Search
function to locate these documents.

Informational Informational Reject Reason Codes are used for Transactions that
Reject Reason do not reject but need extra explanation regarding the processing.
Codes A Transaction with an Informational Reject Reason Code is
processed and settled by the Network.

continued on next page

October 2019 Page 3-7

Message Paths Some messages reference a message path as shown in Table 3-4.
These paths can have different optionality. The optionality is
displayed in all appropriate message layout tables and
programming notes that use the path. Refer to Field Optionality on
page 3-5 for optionality definitions.

Table 3-4. Message Path

Path Description
A to N The Acquirer sends a message to the Network.
N to I The Network sends a message to the Issuer.
I to N The Issuer returns a message to the Network.
N to A The Network send the message to the Acquirer

Page 3-8 October 2019

How to Use Messages

How to Use Table 3-5 shows each Network message and how the Network and Participants use it.
Messages

Table 3-5. How to Use Messages

Message How Acquirers Use It How the Network Uses It How Issuers Use It
Authorization Messages
POS Authorization Request Requests Authorization for a POS
(1100) Transaction
POS Authorization Response Responds to 1100 POS Authorization
(1110) Request
POS Authorization Advice (1120) • Responds to Acquirer Authorization
Request with decline due to canceled
S/E status
• Responds to Acquirer Authorization
Request during Stand-In
• Tells Issuers of Authorization
Requests declined due to canceled
S/E status
• Tells Issuers of Authorization voice
referrals resolved by the Acquirer
• Tells Issuers of Transactions deci-
sioned during Stand-In
• Tells Issuers of online processing of
refunds
• Tells certified Issuers when Global
Network Services Authorization Sys-
tem (GNSAS) declines a Transaction
on their behalf based on Fraud Prob-
ability Score and Recommendation
Code

October 2019 Page 3-9

Table 3-5. How to Use Messages (continued)

Message How Acquirers Use It How the Network Uses It How Issuers Use It
POS Authorization Advice Acknowledges the 1120 POS Authoriza-
Response (1130) tion Advice
POS Authorization Reversal Generates POS online reversals and
Advice (1420) voids
POS Authorization Reversal D Acknowledges the receipt of 1420 POS
Advice Response (1430) Authorization Reversal Advice
ATM Financial Transaction • Requests Authorization to dispense
Request (1200) funds from an ATM
• Transports and request verification of
PIN change on Chip Cards (if certi-
fied)
ATM Financial Transaction • Responds to a 1200 ATM Financial
Response (1210) Transaction Request
• Acknowledges and encrypts PIN to
chip (if certified)
Promotional Program Debit File After receiving a Promotional Program Sends this message to Acquirer to tell
(1244) Debit File (1244) message from the them that a POS First Presentment
Network, an Acquirer must respond (1240) has been sent to an Issuer con-
with a Participant File Acknowledgment taining award Transaction
(1824).
ATM Reversal Advice (1420) Tells Issuers of a change in disposition
of an ATM Transaction
ATM Reversal Advice Response Acknowledges receipt of 1420 POS
(1430) Authorization Reversal Advice
Network Management Request Sends a sign-on/off to show can/cannot
(1804) accept Authorization traffic
Network Management Response Responds to an 1804 Network Manage- Receives an 1814 Network Manage-
(1814) ment Request to show can/cannot ment Response to an 1804 Network
accept Authorization traffic Management Request
Real Time Exception Request Requests 1 update done immediately to
(1304) the Network Exception File for:
Real Time VIP Indicator Updates
Add/delete/update Cardmember
Account data

October 2019 Page 3-10

Table 3-5. How to Use Messages (continued)

Message How Acquirers Use It How the Network Uses It How Issuers Use It
Real Time Exception Response Responds to 1304 Real Time Exception
(1314) Request
Exception File Requests update to the Card status
Preferred/Delinquent File Requests update to preferred or delin-
quent data for Cardmembers in the
batch Preferred/Delinquent File
Payment Token Provisioning Passed by the Network to an Issuer to
Request (1100) request that a Card be provisioned by
the Issuer in support of Payment Token
provisioning.
Payment Token Provisioning Responds to the Payment Token Provi-
Response (1110) sioning Request (1100) message sent
by the Network
Payment Token Post Provisioning Not sent directly from the requestor to Notifies Issuers of the result of a Pay-
Notification (1120) the Issuer. The Network responds to ment Token Provisioning Request
the requestor, keeps the Transaction in (1100)
the Store and Forward queue, and
sends the message along to the Issuer
from the queue.
Payment Token Post Provisioning Responds to the Payment Token Post
Notification Response (1130) Provisioning Notification (1120) mes-
sage
Financial Messages
File Header (9824) Creates as the first data record for the Creates as the first data record for the Creates as the first data record for the
files containing Financial messages files containing Financial messages files containing Financial messages
File Trailer (9825) Creates as the last data record for the Creates as the last data record for the Creates as the last data record for the
files containing Financial messages files containing Financial messages files containing Financial messages
Network File Acknowledgment Shows acceptance or rejection of files
(1844) and returns rejected Transactions
Participant File Acknowledgment Acknowledges receipt of an incleared Acknowledges receipt of an incleared
(1824) file file
POS First and Second Present- Presents Cardmember POS Transac-
ment (1240) tions for payment

October 2019 Page 3-11

Table 3-5. How to Use Messages (continued)

Message How Acquirers Use It How the Network Uses It How Issuers Use It
ATM First and Second Present- Presents Cardmember ATM Transac- Generates ATM First Presentment
ment (1240) tions for payment (Second Present- (1240) from the ATM Authorization
ment) Request (1200)
POS Authorization Adjustment Acquirers (and their S/Es) send this
Financial Advice (1220) message to release funds held when
the last Transaction amount is less than
the first authorized amount. This mes-
sage supplies the last amount of the
Transaction to the Issuer when the sale
is complete.
POS Authorization Adjustment Returns this message after receiving a
Financial Advice Response (1230) POS Authorization Adjustment Financial
Advice (1220) from an Acquirer.
Fee Collection (1744) Generates contractual fee amount and
descriptions of Network fees
ATM Fees (1740/1742) Generates contractual ATM fee amount
to debit Issuer (1740) and credit
Acquirer (1742) for Cardmember 1240
ATM First Presentment Transactions.
For some contracts, this includes
unsuccessful (declined) ATM Transac-
tions, in which the 1740/1742 message
will not be accompanied by a Card-
member 1240 ATM First Presentment
Transaction.
Retrieval Request Notification Requests POS or ATM Presentment data
(1642)
Fulfillment Notification (1640) Responds to a Retrieval Request Notifi-
cation for supporting documentation for
a POS or ATM Transaction
First and Final Chargeback Notifi- Processes chargeback to transfer liabil-
cation (1442) ity back to Acquirer for a POS or ATM
Transaction
Addenda Messages

October 2019 Page 3-12

Table 3-5. How to Use Messages (continued)

Message How Acquirers Use It How the Network Uses It How Issuers Use It
Industry Specific Detail Addenda
(9240/9340)
Airline Industry Specific Detail Supplies more data for an airline Trans-
(9240/9340) action
Auto Rental Industry Specific Supplies more data for an auto rental
Detail (9240/9340) Transaction
Communication Services Industry Supplies more data for a communica-
Specific Detail (9240/9320) tion services Transaction
Entertainment/Ticketing Indus- Supplies more data for an entertain-
try Specific Detail (9240/9340) ment/ticketing Transaction
General Format Industry Specific Supplies more data for a general retail
Detail (9240/9340) or oil Transaction
Insurance Industry Specific Detail Supplies more data for an insurance
(9240/9340) Transaction
Lodging Industry Specific Detail Supplies more data for a lodging Trans-
(9240/9340) action
Rail Industry Specific Detail Supplies more data for a rail Transac-
(9240/9340) tion
Restaurant Industry Specific Supplies more data for a restaurant
Detail (9240/9340) Transaction
Retail Industry Specific Detail Supplies more data for a department
(9240/9340) store or other retail Transaction
Travel/Cruise Industry Specific Supplies more data for a travel/cruise
Detail (9240/9340) Transaction
Deferred Payment Plan Supplies more data for a deferred pay-
(9240/9340) ment plan Transaction
Double Byte Character (9240) Supplies more data for a double byte
character format
Market Specific Data (9240) Supplies more market specific data in a
double byte character format

October 2019 Page 3-13

Table 3-5. How to Use Messages (continued)

Message How Acquirers Use It How the Network Uses It How Issuers Use It
Chip Card (9240) Supplies more data necessary to pro-
cess a Chip Card Transaction
Note: The Chip Card Addendum can
only be appended to a First
Presentment (1240) message.
Corporate Purchasing Card Trans- Supplies more Transaction data for use
action Detail (9240) in the report of CPC Transactions
Extended Financial Addendum Supplies more data for a Transaction Receives more data if contractually eli-
(9240) gible
Data Collection Messages
Data Collection File Header Creates as the first data record for the Creates as the first data record for the Creates as the first data record for the
(9844) Data Collection files Data Collection files Data Collection files
Data Collection File Trailer (9845) Creates as the last data record for the Creates as the last data record for the Creates as the last data record for the
Data Collection files Data Collection files Data Collection files
On Us POS First and Second Pre- Supplies data on 1 Cardmember POS
sentment (1340) Transaction when the acquiring and
issuing business belongs to an Inde-
pendent Operator
On Us ATM First and Second Pre- Supplies data on 1 Cardmember ATM
sentment (1340) Transaction when the acquiring and
issuing business belongs to an Inde-
pendent Operator
On Us First and Final Chargeback Supplies data on 1 Cardmember
Notification (1340) Chargeback Transaction when the
acquiring and issuing business belongs
to Independent Operator
S/E Demographics Detail Data Supplies demographic characteristics of
(9640) new and existing Service Establish-
ments (S/E)
Program Specific Data Collection Supplies data to an administrator of a Supplies data to an administrator of a
(9344) specific program specific program

October 2019 Page 3-14

Table 3-5. How to Use Messages (continued)

Message How Acquirers Use It How the Network Uses It How Issuers Use It
Acquirer S/E Fraud Detail (9344) Gives Acquirers a list of the S/Es in
their market with fraudulent Transac-
tions, as reported by Issuers on the
Network
ATM Location List (9344) Supplies ATM location information in
positions 209-1400
Fusion Membership Rewards Lets Cardmembers transfer points to
(9344) American Express contracted Member-
ship Rewards (MR) partners through an
automatic capability between the Par-
ticipant and the MR partners through
American Express using the Partici-
pant’s GLOBE
Chip Card Request and Response Requests personalization of a Chip Card
(9344) in positions 209-1400
Batch Exception Update Request Informs the Network of Cardmembers
(9344) to be denied or receive special handling
(VIP during host Stand-In)
Batch Exception Update Replies to Issuer with count and detail
Response Count and Detail of the total number of records received,
(9344) processed, and rejected
Fraud Repository Update and Returns to Issuer when the file is fully Reports fraudulent Transactions to the
Response (9324/9334) or not fully accepted into the GNS GNS Fraud Repository
Fraud Repository (9334)
Fraud Report Record (9644) Supplies monthly fraud reports to Par-
ticipants

October 2019 Page 3-15

Participant Responsibility

Data Standards All computer systems and software used by Participants will:
• Manage and configure data involving all valid dates without
functional or data abnormality related to such dates
• Manage and configure data involving all valid dates without
inaccurate results related to such dates
• Have user interfaces and data fields formatted to accept all valid
dates
• Represent all data to include indications of the millennium,
century, decade, and the year

Page 3-16 October 2019

Chapter 4 Network Cards

Issuer Responsibilities

Issuer Issuers must:

Responsibilities
• Contract with a certified Card Manufacturer to make, emboss,
and code Network Card plastic
• Make sure their Cards agree with the ISO and Network
technical, security, and visual identity standards as described in:
• Network Specifications manuals
• The Business and Operational Policies manual
• All related American Express Global Network Services
(AEGNS) manuals
• The Marketing Resources pages on
[Link]/knowledgebase
• Send test Cards to AEGNS, as described in Test Cards on page
4-24

Certified Card Certified Card Manufacturers must align with the Network Card
Manufacturers standards. These standards include technical analysis of the Card
magnetic stripe such as jitter testing. Issuers must contract with
certified Card Manufacturers to make Network Cards. For a list of
certified Card Manufacturers, refer to the Certified Card
Manufacturers List on
[Link]/knowledgebase. Use the Search
function to locate these documents.

Non-certified Card Card Issuers that use the services of Card Manufacturers that are
Manufacturers not certified by AEGNS must contact their AEGNS Representative
about the Card Manufacturer certification process.

How To Order Contact your local AEGNS Representative for information about
Plastic plastic orders.

More Instruction Refer to ISO/IEC 7811-2, Identification Cards - Recording

Technique - Part 2: Magnetic Stripe for more embossing standards.

October 2019 Page 4-1

Acquirer Responsibilities

Acquirer Acquirers must:

Responsibilities
• Make sure that their Service Establishments (S/Es) accept and
process Network Card Transactions correctly for Cards that have
been encoded in accordance with the specifications in this
manual. This includes all Point of Sale equipment that supports
ISO 7813 Track 1 and 2 formats and ANSI X4.16 Track 1 and 2
formats.
• Get all magnetic stripe data from the Start Sentinel to the End
Sentinel, and include it in the Authorization Request, as
captured.
• Identify the technical capability of the Card (ISO or ANSI).

Important POS equipment used by an S/E should not:

• Validate the Card Expiration Date or Card Effective Date and
reject Transactions
• Read one track from the Card’s magnetic stripe and send the
other (for example, read Track 1 and send Track 2)
• Assume a fixed length for Track 1 or Track 2

Card Acceptance S/Es and Acquirers can validate the Cardmember account number
Procedures check digit at the point of sale (refer to Computing PAN Check Digits
on page 4-26 for instructions).

More Instruction For more instruction on S/E Card Acceptance Procedures, refer to
Chapter 4 – S/E and ATM Standards in the Business and Operational
Policies manual.

Page 4-2 October 2019

ISO 7813 Track 1 and 2 Formatting

Overview The magnetic stripe on AEGNS Cards must use the ISO 7813
format.
Refer to ISO 7813 Standard Track 1 Layout on page 4-4 and ISO
7813 Standard Track 2 Layout on page 4-10 for layout instructions.

Important Participants must support ISO 7813 Track 1 and 2 formats and ANSI
X4.16 Track 1 and 2 Format to make Authorization decisions.
Track data must be sent as captured. When Track 1 and Track 2
data are received by the Network, the Network sends only Track 2
data to the Issuer.

Issuers Cards must align with the ISO 7813 format before implementation.

Acquirers Magnetic stripe data on Track 1 or Track 2 must pass parity and
Longitudinal Redundancy Check (LRC) tests before the data is sent
to the Network.
Network Card account numbers must pass the check digit test,
when received by the Network, as described in Computing PAN
Check Digits on page 4-26.

Discretionary Data The Discretionary Data field in ISO 7813 Track 1 is a variable length
field. It shows the balance of the digits available on the track. The
Discretionary Data field is not padded with zeros or spaces. The
Discretionary Data is used in Track 1 for the Card Effective Date and
Card Security Code field. The Discretionary Data is in Track 2 for the
Language Code field.
Note: AEGNS reserves the definition and use of the Discretionary
Data field. Participants must get written approval from
AEGNS, and must comply with future defined usage, before
they use the Discretionary Data field.

October 2019 Page 4-3

ISO 7813 Standard Track 1 Layout

Description The ISO 7813 Standard Track 1 layout is used to encode Track 1 on
AEGNS Cards.
POS applications remove the Start Sentinel, the End Sentinel, and
the Longitudinal Redundancy Check (LRC) fields. Only the 76 bytes
of data between the sentinels is sent.
Other messages send the data between the sentinels (76 bytes)
and the Variable Length Indicator (LLVAR) (2 bytes).
Special Track 1 Data format definitions are found in each message
that has a Track 1 Data field.

Important Participants must use the Network Positions value for encoding
Track 1 on all AEGNS Cards.

Message Layout This table shows the layout for ISO 7813 Track 1. Refer to the
Programming Notes for ISO 7813 Track 1 on page 4-5 for more
instruction.

ISO 7813 Standard Track 1 Layout

Field Network Field Field
Optionality Field Name
Number Positions Type Length
1 1 M Special Character 1 Start Sentinel
2 2 M Alphanumeric 1 Format Code
3 3-17 M Numeric 15 Primary Account Number
(PAN)
4 18 M Special Character 1 Field Separator
5 19-44 M Alphanumeric 26 Cardmember Name
6 45 M Special Character 1 Field Separator
7 46-49 M Numeric 4 Card Expiration Date
8 50-52 M Numeric 3 Service Code
9 53-56 M Numeric 4 Card Effective Date
10 57-61 M Alphanumeric 5 Card Security Code
11 62-65 M Alphanumeric 4 Reserved
12 66-77 M Alphanumeric 12 Partner Defined Data
13 78 M Special Character 1 End Sentinel
14 79 M Binary Coded Digit 1 Longitudinal Redundancy
Check (LRC)

Page 4-4 October 2019

Programming Notes for ISO 7813 Track 1

Field 1 Start Sentinel
Definition Identifies the beginning of a magnetic stripe.

The Start Sentinel is not sent in the Authorization Request message. This field uses a
6-bit character set with odd parity. Refer to ISO/IEC 7811-2, Identification Cards -
Recording Technique - Part 2: Magnetic Stripe for instructions.
Network Position 1
Optionality Mandatory
Field Type Special Character
Field Length 1
Notes Required Value: %

Field 2 Format Code

Definition ANSI/ISO track data protocol defines two (2) Format Codes. Code A = name first,
Code B = account number first. Code B is the standard format and is the Format
Code utilized by American Express.
Network Position 2
Optionality Mandatory
Field Type Alphanumeric
Field Length 1
Notes Required Value: B

This field shows which of 2 possible formats is used on the track.

Field 3 Primary Account Number (PAN)

Definition A series of digits encoded into the magnetic stripe, stored on the chip of a Chip Card,
and printed on the Card; used to identify the Card Issuer and the Cardmember (CM)
account or relationship. Valid American Express Card account numbers begin with 34
or 37 and end in a valid check digit.
Network Position 3-17
Optionality Mandatory
Field Type Numeric
Field Length 15

October 2019 Page 4-5

This document contains sensitive, confidential and trade secret information, and may not be disclosed
to third parties without written consent of American Express Travel Related Services Company, Inc.
Network Specifications - Instructions
ISO 7813 Standard Track 1 Layout
Field 4 Field Separator
Field 4 Field Separator
Definition This field divides track data. This field uses a 6-bit character set with odd parity.
Refer to ISO/IEC 7811-2, Identification Cards - Recording Technique - Part 2-
Magnetic Stripe for instruction.
Network Position 18
Optionality Mandatory
Field Type Special Character
Field Length 1
Notes Required Value: ^

Field 5 Cardmember Name

Definition This field contains the Cardmember’s Name.
Network Position 19-44
Optionality Mandatory
Field Type Alphanumeric
Field Length 26
Notes There is a limit of 21 characters on the front of the Card.

Magnetic Stripe: While the length of the Cardmember Name can vary, the number
of characters on the magnetic stripe must be 26 characters. Unused bytes must be
filled with spaces.

The following characters are used to separate the elements of a Cardmember’s

Name:
“/” (forward slash) = surname/first name separator

“-” (space) = first name/middle name or first name/middle initial separator (as
required)

“.” (period) = name/title separator (as required)

Magnetic Stripe Examples:

Surname only: FROST/

Surname and first name: FROST/CHARLES

Surname, first name, and middle initial: FROST/CHARLES F

Surname, first initial, and middle initial: FROST/C F

Surname, first name, middle name, and title: FROST/CHARLES [Link]

The minimum encoded data shall be a single alpha character (as surname) and the
surname separator.

Card Face: The maximum number of characters that can be embossed on the Card
face is 21 characters. Refer to the ISO 7811-3 standard for more instruction on
embossing the card face.

continued on next page

Page 4-6 October 2019

Surname only: FROST

Surname and first name: CHARLES FROST

Surname, first name, and middle initial: CHARLES F FROST

Surname, first initial, and middle initial: C F FROST

Surname, first name, middle name, and title: CHARLES FRANCIS FROST JR (This
Cardmember Name exceeds 21 characters and, therefore, cannot be used for the
card face).

Field 6 Field Separator

Definition This field divides track data. This field uses a 6-bit character set with odd parity.
Refer to ISO/IEC 7811-2, Identification Cards - Recording Technique - Part 2-
Magnetic Stripe for instruction.
Network Position 45
Optionality Mandatory
Field Type Special Character
Field Length 1
Notes Required Value: ^

Field 7 Card Expiration Date

Definition This is the Card Expiration Date embossed on the face of the Card.
Network Position 46-49
Optionality Mandatory
Field Type Numeric
Field Length 4
Notes Format: YYMM

Field 8 Service Code

Definition A 3-digit number used in magnetic stripe mode Transactions that specifies
acceptance requirements and limitations for a magnetic stripe-read Transaction.
Network Position 50-52
Optionality Mandatory
Field Type Numeric
Field Length 3
Notes Refer to the Codes Reference Guide for a list of Service Codes.

October 2019 Page 4-7

Field 10 Card Security Code

Definition Any of several values printed or encoded on the Card and used for fraud prevention
in Authorizations, including: the Printed Card Security Code (PCSC), the 5-digit Card
Security Code encoded within the magnetic stripe (5CSC), and the 5-digit Card
Security Code encoded within the magnetic stripe equivalent on Chip Cards (iCSC).
Network Position 57-61
Optionality Mandatory
Field Type Alphanumeric
Field Length 5

Field 11 Reserved
Definition This field is for AEGNS internal use.
Network Position 62-65
Optionality Mandatory
Field Type Alphanumeric
Field Length 4
Notes Alphanumeric Reserved Fields must contain spaces.

Field 12 Partner Defined Data

Definition A free form text field for Participant use.
Network Position 66-77
Optionality Mandatory
Field Type Alphanumeric
Field Length 12
Notes If this field is not used, it must contain spaces.

Page 4-8 October 2019

The End Sentinel is not sent in an Authorization Request message. This field uses a
6-bit character set with odd parity. Refer to ISO/IEC 7811-2, Identification Cards -
Recording Technique - Part 2: Magnetic Stripe for instructions.
Network Position 78
Optionality Mandatory
Field Type Special Character
Field Length 1
Notes Required Value: ?

Field 14 Longitudinal Redundancy Check (LRC)

Definition This unique character is in each magnetic stripe. The LRC immediately follows the
End Sentinel, when the Card is read from the Start Sentinel. The LRC is automatically
generated by the embossing/encoding machine.
Network Position 79
Optionality Mandatory
Field Type Binary Coded Digit
Field Length 1

October 2019 Page 4-9

ISO 7813 Standard Track 2 Layout

Description This layout is used for encoding Track 2 on all Network Cards.
POS applications strip these fields and send only the 37 bytes of
data between the sentinels.
Other messages send the data between the sentinels (37 bytes)
plus the 2-digit variable length indicator to make a total of 39 bytes
of data.
Special Track 2 Data format definitions are in each message that
has a Track 2 Data field.

Message Layout This table shows the layout for ISO 7813 Track 2. Refer to
Programming Notes for ISO 7813 Track 2 on page 4-11 for more
instruction.

ISO 7813 Standard Track 2 Layout

Field Field Field
Positions Optionality Field Name
Number Type Length
1 1 M Special Character 1 Start Sentinel
2 2-16 M Numeric 15 Primary Account Number
(PAN)
3 17 M Special Character 1 Field Separator
4 18-21 M Numeric 4 Card Expiration Date
5 22-24 M Numeric 3 Service Code
6 25-28 M Numeric 4 Card Effective Date
7 29-33 M Numeric 5 Card Security Code
8 34-36 M Numeric 3 Reserved Field
9 37-38 M Numeric 2 Language Code
10 39 M Special Character 1 End Sentinel
11 40 M Binary 1 Longitudinal Redundancy
Check (LRC)

Page 4-10 October 2019

Programming Notes for ISO 7813 Track 2

Field 1 Start Sentinel
Definition Identifies the beginning of a magnetic stripe.

The Start Sentinel is not sent in the Authorization Request message. This field uses a
6-bit character set with odd parity. Refer to ISO/IEC 7811-2, Identification Cards -
Recording Technique - Part 2: Magnetic Stripe for instructions.
Position 1
Optionality Mandatory
Field Type Special Character
Field Length 1
Notes Required Value: ;

Field 2 Primary Account Number (PAN)

Definition A series of digits encoded into the magnetic stripe, stored on the chip of a Chip Card,
and printed on the Card; used to identify the Card Issuer and the Cardmember (CM)
account or relationship. Valid American Express Card account numbers begin with 34
or 37 and end in a valid check digit.
Position 2-16
Optionality Mandatory
Field Type Numeric
Field Length 15

Field 3 Field Separator

Definition This field divides track data. This field uses a 6-bit character set with odd parity.
Refer to ISO/IEC 7811-2, Identification Cards - Recording Technique - Part 2-
Magnetic Stripe for instruction.
Position 17
Optionality Mandatory
Field Type Special Character
Field Length 1
Notes Valid Values: = or D

Field 4 Card Expiration Date

Definition This is the Card Expiration Date embossed on the face of the Card.
Position 18-21
Optionality Mandatory
Field Type Numeric
Field Length 4
Notes Format: YYMM

October 2019 Page 4-11

This document contains sensitive, confidential and trade secret information, and may not be disclosed
to third parties without written consent of American Express Travel Related Services Company, Inc.
Network Specifications - Instructions
ISO 7813 Standard Track 2 Layout
Field 5 Service Code
Field 5 Service Code
Definition A 3-digit number used in magnetic stripe mode Transactions that specifies
acceptance requirements and limitations for a magnetic stripe-read Transaction.
Position 22-24
Optionality Mandatory
Field Type Numeric
Field Length 3
Notes Refer to the Codes Reference Guide for a list of Service Codes.

Field 6 Card Effective Date

Definition This is the Card Effective Date embossed on the face of the Card.
Position 25-28
Optionality Mandatory
Field Type Numeric
Field Length 4
Notes Format: YYMM

Field 7 Card Security Code

Definition Any of several values printed or encoded on the Card and used for fraud prevention
in Authorizations, including: the Printed Card Security Code (PCSC), the 5-digit Card
Security Code encoded within the magnetic stripe (5CSC), and the 5-digit Card
Security Code encoded within the magnetic stripe equivalent on Chip Cards (iCSC).
Position 29-33
Optionality Mandatory
Field Type Numeric
Field Length 5

Field 8 Reserved
Definition This field is for AEGNS internal use.
Position 34-36
Optionality Mandatory
Field Type Numeric
Field Length 3
Notes Required Value: 000

Numeric Reserved Fields must contain zeros.

Page 4-12 October 2019

This document contains sensitive, confidential and trade secret information, and may not be disclosed
to third parties without written consent of American Express Travel Related Services Company, Inc.
Network Specifications - Instructions
ISO 7813 Standard Track 2 Layout
Field 9 Language Code
Field 9 Language Code
Definition Used to define the specific language or Double Byte Character language.
Position 37-38
Optionality Mandatory
Field Type Numeric
Field Length 2
Notes Valid Values:
• 00 = Non-Canadian Cardmembers
• 01 = Canadian Cardmembers - English language
• 02 = Canadian Cardmembers - French language

Field 10 End Sentinel

Definition This field identifies the end of the magnetic stripe.

The End Sentinel is not sent in an Authorization Request message. This field uses a
6-bit character set with odd parity. Refer to ISO/IEC 7811-2, Identification Cards -
Recording Technique - Part 2: Magnetic Stripe for instructions.
Position 39
Optionality Mandatory
Field Type Special Character
Field Length 1
Notes Required Value: ?

Field 11 Longitudinal Redundancy Check (LRC)

Definition This unique character is in each magnetic stripe. The LRC immediately follows the
End Sentinel, when the Card is read from the Start Sentinel. The LRC is automatically
generated by the embossing/encoding machine.
Position 40
Optionality Mandatory
Field Type Binary
Field Length 1

October 2019 Page 4-13

ISO 4909 Track 3 Formatting

Overview The Network does not use the Track 3 format at this time. Issuers
who use Track 3 must get approval from AEGNS before Card
issuance. Brand image and Card usage must agree. The Issuer
must give a description and the format of their Track 3 encoding to
AEGNS.

Page 4-14 October 2019

ANSI X4.16 Track 1 and 2 Format

Overview ANSI X4.16 formats are still encoded on some American Express
branded Cards and Emergency Replacement Cards. To assist
Acquirers, the format used on these Cards is described in this
section.
Refer to ANSI X4.16 Track 1 Layout on page 4-16 and ANSI X4.16
Track 2 Layout on page 4-21 for layout instructions.

Important Participants must support ISO 7813 Standard Track 1 Layout and
ANSI X4.16 Track 1 and 2 Formatting to make Authorization
decisions.
Track data must be sent as captured.

October 2019 Page 4-15

ANSI X4.16 Track 1 Layout

Important Issuers are not permitted to use this format for Card encoding.
Issuers must accept an Authorization Request with this format.

Description ANSI X4.16 Track 1 holds a maximum of 61 bytes. Two bytes are:
• Start Sentinel
• End Sentinel
POS applications strip these 2 fields and send only the 59 bytes of
data between the sentinels.
Other messages send the data between the sentinels (59 bytes)
plus the 2-digit variable length indicator (LLVAR) to make a total of
61 bytes of data.
Special ANSI X4.16 Track 1 Data format definitions are in each
message that has an ANSI X4.16 Track 1 Data field.

Layout This table shows the layout for ANSI X4.16 Track 1. Refer to the
Programming Notes for ANSI X4.16 Track 1 on page 4-17 for more
instruction.

ANSI X4.16 Track 1 Layout

Field Field Field
Positions Optionality Field Name
Number Type Length
1 1 M Special Character 1 Start Sentinel
2 2 M Alphanumeric 1 Format Code
3 3-19 M Alphanumeric 17 Primary Account Number
(PAN)
4 20 M Special Character 1 Field Separator
5 21-46 M Alphanumeric 26 Cardmember Name
6 47 M Special Character 1 Field Separator
7 48-51 M Numeric 4 Card Expiration Date
8 52-55 M Numeric 4 Card Effective Date
9 56-60 M Numeric 5 Card Security Code or Card
Identification Code
10 61 M Special Character 1 End Sentinel

Page 4-16 October 2019

Programming Notes for ANSI X4.16 Track 1

Field 1 Start Sentinel
Definition Identifies the beginning of a magnetic stripe.

The Start Sentinel is not sent in the Authorization Request message. This field uses a
6-bit character set with odd parity. Refer to ISO/IEC 7811-2, Identification Cards -
Recording Technique - Part 2: Magnetic Stripe for instructions.
Position 1
Optionality Mandatory
Field Type Special Character
Field Length 1
Notes Required Value: %

Field 2 Format Code

Definition ANSI/ISO track data protocol defines two (2) Format Codes. Code A = name first,
Code B = account number first. Code B is the standard format and is the Format
Code utilized by American Express.
Position 2
Optionality Mandatory
Field Type Alphanumeric
Field Length 1
Notes Required Value: B

This field shows which of 2 possible formats is used on the track.

Field 3 Primary Account Number (PAN)

Definition A series of digits encoded into the magnetic stripe, stored on the chip of a Chip Card,
and printed on the Card; used to identify the Card Issuer and the Cardmember (CM)
account or relationship. Valid American Express Card account numbers begin with 34
or 37 and end in a valid check digit.
Position 3-19
Optionality Mandatory
Field Type Alphanumeric
Field Length 17
Notes The Primary Account Number (PAN) numeric format includes spaces in the 17-digit
field parameter; for example: 3759 876543 21001.

October 2019 Page 4-17

This document contains sensitive, confidential and trade secret information, and may not be disclosed
to third parties without written consent of American Express Travel Related Services Company, Inc.
Network Specifications - Instructions
ANSI X4.16 Track 1 Layout
Field 4 Field Separator
Field 4 Field Separator
Definition This field divides track data. This field uses a 6-bit character set with odd parity.
Refer to ISO/IEC 7811-2, Identification Cards - Recording Technique - Part 2-
Magnetic Stripe for instruction.
Position 20
Optionality Mandatory
Field Type Special Character
Field Length 1
Notes Required Value: ^

Field 5 Cardmember Name

Definition This field contains the Cardmember’s Name.
Position 21-46
Optionality Mandatory
Field Type Alphanumeric
Field Length 26
Notes Magnetic Stripe: While the length of the Cardmember Name can vary, the number
of characters on the magnetic stripe must be 26 characters. Unused bytes must be
filled with spaces.
The following characters are used to separate the elements of a Cardmember’s
Name:

“/” (forward slash) = surname/first name separator

“-” (space) = first name/middle name or first name/middle initial separator (as
required)

“.” (period) = name/title separator (as required)

Magnetic Stripe Examples:

Surname only: FROST/

Surname and first name: FROST/CHARLES

Surname, first name, and middle initial: FROST/CHARLES F

Surname, first initial, and middle initial: FROST/C F

Surname, first name, middle name, and title: FROST/CHARLES [Link]

The minimum encoded data shall be a single alpha character (as surname) and the
surname separator.

Card Face: The maximum number of characters that can be embossed on the Card
face is 21 characters. Refer to the ISO 7811-3 standard for more instruction on
embossing the card face.

continued on next page

Page 4-18 October 2019

Surname only: FROST

Surname and first name: CHARLES FROST

Surname, first name, and middle initial: CHARLES F FROST

Surname, first initial, and middle initial: C F FROST

Surname, first name, middle name, and title: CHARLES FRANCIS FROST JR (This
Cardmember Name exceeds 21 characters and, therefore, cannot be used for the
card face).

Field 6 Field Separator

Definition This field divides track data. This field uses a 6-bit character set with odd parity.
Refer to ISO/IEC 7811-2, Identification Cards - Recording Technique - Part 2-
Magnetic Stripe for instruction.
Position 47
Optionality Mandatory
Field Type Special Character
Field Length 1
Notes Required Value: ^

Field 7 Card Expiration Date

Definition This is the Card Expiration Date embossed on the face of the Card.
Position 48-51
Optionality Mandatory
Field Type Numeric
Field Length 4
Notes Format: YYMM

Field 8 Card Effective Date

Definition This is the Card Effective Date embossed on the face of the Card.
Position 52-55
Optionality Mandatory
Field Type Numeric
Field Length 4
Notes Format: YYMM

October 2019 Page 4-19

This document contains sensitive, confidential and trade secret information, and may not be disclosed
to third parties without written consent of American Express Travel Related Services Company, Inc.
Network Specifications - Instructions
ANSI X4.16 Track 1 Layout
Field 9 Card Security Code or Card Identification Code
Field 9 Card Security Code or Card Identification Code
Definition Any of several values printed or encoded on the Card and used for fraud prevention
in Authorizations, including: the Printed Card Security Code (PCSC), the 5-digit Card
Security Code encoded within the magnetic stripe (5CSC), and the 5-digit Card
Security Code encoded within the magnetic stripe equivalent on Chip Cards (iCSC).
Position 56-60
Optionality Mandatory
Field Type Numeric
Field Length 5

Field 10 End Sentinel

Definition This field identifies the end of the magnetic stripe.

The End Sentinel is not sent in an Authorization Request message. This field uses a
6-bit character set with odd parity. Refer to ISO/IEC 7811-2, Identification Cards -
Recording Technique - Part 2: Magnetic Stripe for instructions.
Position 61
Optionality Mandatory
Field Type Special Character
Field Length 1
Notes Required Value: ?

Page 4-20 October 2019

ANSI X4.16 Track 2 Layout

Important Issuers cannot use this format for Card encoding. Issuers must
accept an Authorization Request with this format.

Description ANSI X4.16 Track 2 holds a maximum of 31 bytes. Two bytes are:
• Start Sentinel
• End Sentinel
POS applications strip these 2 fields and send only the 29 bytes of
data between the sentinels.
Other messages send the data between the sentinels (29 bytes)
plus the two-digit variable length indicator (LLVAR) to make a total
of 31 bytes of data.
Special ANSI X4.16 Track 2 Data format definitions are in each
message that has an ANSI X4.16 Track 2 Data field.

Layout This table shows the layout for ANSI X4.16 Track 2. Refer to the
Programming Notes for ANSI X4.16 Track 2 on page 4-22 for more
instruction.

ANSI X4.16 Track 2 Layout

Field Field
Positions Optionality Field Type Field Name
Number Length
1 1 M Special Character 1 Start Sentinel
2 2-16 M Numeric 15 Primary Account Number
(PAN)
3 17 M Special Character 1 Field Separator
4 18-21 M Numeric 4 Card Expiration Date
5 22-25 M Numeric 4 Card Effective Date
6 26-30 M Numeric 5 Card Security Code or Card
Identification Code
7 31 M Special Character 1 End Sentinel

October 2019 Page 4-21

Programming Notes for ANSI X4.16 Track 2

Field 1 Start Sentinel
Definition Identifies the beginning of a magnetic stripe.

The Start Sentinel is not sent in the Authorization Request message. This field uses a
6-bit character set with odd parity. Refer to ISO/IEC 7811-2, Identification Cards -
Recording Technique - Part 2: Magnetic Stripe for instructions.
Position 1
Optionality Mandatory
Field Type Special Character
Field Length 1
Notes Required Value: ;

Field 2 Primary Account Number (PAN)

Definition A series of digits encoded into the magnetic stripe, stored on the chip of a Chip Card,
and printed on the Card; used to identify the Card Issuer and the Cardmember (CM)
account or relationship. Valid American Express Card account numbers begin with 34
or 37 and end in a valid check digit.
Position 2-16
Optionality Mandatory
Field Type Numeric
Field Length 15

Field 3 Field Separator

Definition This field divides track data. This field uses a 6-bit character set with odd parity.
Refer to ISO/IEC 7811-2, Identification Cards - Recording Technique - Part 2-
Magnetic Stripe for instruction.
Position 17
Optionality Mandatory
Field Type Special Character
Field Length 1
Notes Required Value: =

Field 4 Card Expiration Date

Definition This is the Card Expiration Date embossed on the face of the Card.
Position 18-21
Optionality Mandatory
Field Type Numeric
Field Length 4
Notes Format: YYMM

Page 4-22 October 2019

Field 6 Card Security Code or Card Identification Code

Definition Any of several values printed or encoded on the Card and used for fraud prevention
in Authorizations, including: the Printed Card Security Code (PCSC), the 5-digit Card
Security Code encoded within the magnetic stripe (5CSC), and the 5-digit Card
Security Code encoded within the magnetic stripe equivalent on Chip Cards (iCSC).
Position 26-30
Optionality Mandatory
Field Type Numeric
Field Length 5

Field 7 End Sentinel

Definition This field identifies the end of the magnetic stripe.

The End Sentinel is not sent in an Authorization Request message. This field uses a
6-bit character set with odd parity. Refer to ISO/IEC 7811-2, Identification Cards -
Recording Technique - Part 2: Magnetic Stripe for instructions.
Position 31
Optionality Mandatory
Field Type Special Character
Field Length 1
Notes Required Value: ?

October 2019 Page 4-23

Test Cards

Test Card Creation The Issuer must emboss and encode a minimum of three test Cards
for each Card product (white plastic can be used). These test Cards
must follow the guidelines found by searching Marketing Resources
on Knowledge Base
([Link]/knowledgebase).

Card Approval This table shows the Card approval process.

Table 4-1. Card Approval Process

Step Who Does What
1 Issuer Sends a minimum of three test Cards for each
Card product to AEGNS for magnetic stripe
encoding certification along with the account
numbers, expiration dates, Card Security
Codes, PIN values, and other Issuer-specific
encoding specifications (e.g., Service Code
Value) that were used to encode the test Cards
Refer to the Codes Reference Guide for a list of
Service Codes.
2 AEGNS Reviews the encoding of the test Cards and
certifies the Issuer for Card issuance

Marketing The GNS Global Marketing group reviews all Card products. Issuers
Approval must comply with the instructions found by searching Marketing
Resources on Knowledge Base at
[Link]/knowledgebase.

Network Exception At least one Card must be listed on the Network Exception File to
File fulfill Network Exception Database testing during the Certification
process. Refer to the Network Specifications - Authorizations
manual for more information.

Page 4-24 October 2019

Primary Account Numbers (PAN)

Field Separators Field separators in Track 1 and Track 2 can be changed due to
EBCDIC and ASCII conversion algorithms.
To find the field separator in a track, AEGNS recommends the
algorithm below. As the track is parsed, keep all numeric
characters. The first non-numeric character is the field separator. At
that point, you have Primary Account Number.

Formatting This table shows the formatting of the Primary Account Number
(PAN).

3 7 X X X X X X X X X X X X X
A B C D

A Company: 34 or 37 shows that the card is an American Express Card.

Part of the BIN Range.
B BIN range: Bank Identifier Number. Includes the first two digits (A).
Shows the BIN range that the Card belongs to, and thus the Issuer of
the Card.
C Card number: A unique number assigned by the Issuer.
D Check digit: Use Computing PAN Check Digits on page 4-26 to calcu-
late. The function of the check digit is to find errors in when the card
number is manually typed.

continued on next page

October 2019 Page 4-25

Computing PAN The Check Digit finds errors when the card number is manually
Check Digits typed. The Check Digit is the last position of the Primary Account
Number. The steps to compute the Check Digit are described in
Table 4-2 along with an example.

Table 4-2. PAN Check Digit Computation

Step Result
Example: PAN = 37387218601100?
1. Start with the last digit, go right to left, and • 0x2=0
multiply every other digit by two. • 1x2=2
• 0x2=0
• 8 x 2 = 16
• 2x2=4
• 8 x 2 = 16
• 7 x 2 = 14
2. If the product of Step 1 is a two-digit number, • 0 0
add the two digits together.
• 22
• 00
• 1+6  7
• 44
• 1+6 7
• 1+4 5
3. Add the results of Step 2. 25
4. Add all the digits not used in Step 1. 3+3+7+1+6+1+0 = 21
5. Add the results of Steps 3 and 4. 25 + 21 = 46
6. If the result of Step 5 is a multiple of 10, the 50 - 46 = 4
check digit is zero. If the result of Step 5 is not
a multiple of 10, subtract the result from the
next higher multiple of 10. The new result is
the calculated check digit.

Page 4-26 October 2019

Identifying Card Usage Parameters

Service Codes Issuers use the Service Code field in Track 1 and Track 2 to identify
the Card’s usage parameters (how the Card can be used). The
Service Code field is 3 bytes containing digits 1 through 9. Table 4-3
shows the Service Code values when used in each of the 3 bytes.
Refer to the Business and Operational Policies manual for more
instruction.
Refer to the Codes Reference Guide for a list of Service Codes.

Table 4-3. Service Code Position Definitions

Position 1 Position 2 Position 3
Values Authorization Range of PIN
Interchange Technology
Processing Services Requirements
0 N/A N/A Normal No restrictions PIN required
1 International N/A N/A No restrictions N/A
2 International Integrated By Issuer Goods and ser- N/A
Circuit Cards vices only
3 N/A N/A N/A ATM only PIN required
4 N/A N/A By Issuer unless Cash only N/A
bilateral agree-
ment applies
5 National N/A N/A Goods and ser- PIN required
vices only
6 National Integrated N/A No restrictions Prompt for PIN if
Circuit Cards PIN pad present
7 Private N/A N/A Goods and ser- Prompt for PIN if
vices only PIN pad present
8 N/A N/A N/A N/A N/A
9 Test N/A N/A N/A N/A

Service Code Refer to the Codes Reference Guide for a list of Service Codes.
Values Used by the
Network

October 2019 Page 4-27

Creating Personal Identification Numbers

Overview Issuers can supply their Cardmembers with Personal Identification

Numbers (PINs).
Note: To use American Express ATMs for cash access, Issuers
must supply their Cardmembers with PINs.

PIN Limitations The Network accepts PINs with a minimum of 4 digits to a

maximum of 12 digits. The Network passes as many digits as it
receives from the Acquirer (within the 4 to 12 digit limit).

PIN Transmission The Network requires the PIN to be a 16-digit PIN block in the
Requirements American National Standards Institute (ANSI X9.8) format (also
known as ISO 9564-1 format 0).

PIN Transmission The ANSI X9.8 format combines the Cardmember PIN and account
Block Creation number as follows:
1. A 16-digit block is assembled from the digit 0, the length of the
PIN, the PIN itself and 10 pad characters (hexadecimal F).
Example: A 4-digit PIN 9238 will have a block of 0492 38FF FFFF
FFFF.
2. Another 16-digit block is assembled from four zeros and the
right-most 12 digits of the account number, excluding the check
digit.
Example: For the 13-digit account number 4000 0012 3456 2,
where the check digit is 2, the block is 0000 4000 0012 3456.
3. The two blocks are exclusive OR added:
04 92 38 FF FF FF FF FF

00 00 40 00 00 12 34 56

04 92 78 FF FF ED CB A9 = PIN Block

PIN Offset The encoding of a PIN offset is not offered on Network Cards at this
time.

continued on next page

Page 4-28 October 2019

Important Although positions are available on the track to encode the PIN
offset 3 bytes, not all ATMs or other PIN-based terminals accessible
by American Express Cards can validate that type of PIN.

October 2019 Page 4-29

Key Management

Overview American Express Global Network Services requires the Card

Security Code(s) and PIN data to be secured. For the protection of
data and mitigation of fraud, encryption keys are used for the
secure generation, storage, and transport of this data. These keys
include, but are not limited to:
Table 4-4. Encryption Keys

Key Length Requirements

Common Keys Generated Keys Generated on
Key Type Purpose
Acronyms before or after
September 5, 2007 September 5, 2007

Local Master LMK1 The master key used to Double-length, Double-length,

Key protect all other keys in the triple-DES, with ANSI triple-DES, with ANSI
Participant’s environment X9.24 standards, and X9.24 standards, and
Master File MFK
odd parity odd parity
Key

Master Key MK

Zone Mas- ZMK1 Keys used to encrypt other Double-length, Double-length,

ter Key keys for transport: triple-DES, with ANSI triple-DES, with ANSI
• ZMKs are exchanged X9.24 standards, and X9.24 standards, and
Zone ZCMK odd parity odd parity
Control between the Participant and
AEGNS as clear compo-
Master Key
nents.
Key KEK • CSCKs and/or ZPKs are
Encryption encrypted under a ZMK
Key when exchanged between
the Participants to AEGNS.
• Refer to Zone Master Key
on page 4-38 for more
instruction.

Card CSCK1 The CSCK is used to generate Single or Double-length,

Security and validate Card Security Double-length triple-DES, with ANSI
Code Key Codes. X9.24 standards, and
Note: The use of
Refer to Card Security Code odd parity
single-length
Key (CSCK) on page 4-39 for keys has a
more instruction. higher
security risk.
Zone PIN ZPK1 The Zone PIN Key (ZPK) used Can be single-length Double-length,
Key for Card Authorization triple-DES, with ANSI
Note: The use of
single-length X9.24 standards, and
odd parity
keys has a
higher
security risk.

1. American Express preferred key naming convention.

continued on next page

Page 4-30 October 2019

The encryption keys shared with AEGNS, or used to protect keys

shared with AEGNS, are to be securely managed by the Participant
through a defined and documented key management life cycle
(including, but not limited to, generation, usage, storage,
personnel, etc.), in alignment with the following industry standards
and current AEGNS policies:
Table 4-5. Documented Key Management Life Cycle

Document Name Location/Reference Description

Payment Card Industry Data [Link] This document defines detailed
Security Standard (PCI DSS) requirements for the protection
of Cardholder Data.
Payment Card Industry PIN [Link] This document defines detailed
Security Requirements (PCI requirements for the protection
PIN) of PIN data, as well as detailed
key management requirements.

AEGNS recommends the use of a Key Check Value to validate that

the correct cryptographic key has been exchanged and successfully
installed for production.

Important These are the current forms used in the Key Management process:
• Key Exchange Readiness Checklist
• Key Exchange Transmittal for American Express Cards
• Key Exchange Transmittal for Chip Cards
Note: Contact your AEGNS Representative to get and complete the
forms.

Encryption Room Physical access to cryptographic keying materials, including, but not
Requirements limited to, HSMs, physical encryption keys, smart cards, paper
components, and other generic storage mediums used by key
management personnel are subject, at a minimum, to the following
requirements:
• Physical access to any cryptographic keying material must be
maintained with dual control at all times, such that it shall not
be possible for a single individual to gain access without the
assistance and knowledge of another duly appointed individual
• Physical access to any cryptographic keying material shall be
restricted for need to know access, demonstrable with
appropriate job functions

continued on next page

October 2019 Page 4-31

• Physical access to any cryptographic keying material must be

logged to include the following:
• Date
• Time
• Person
• Purpose
• Signature
The logs should be protected from modification, reviewed on a
monthly basis, and retained for a minimum of 12 months given the
level of risk associated with the information.

Key Component Key components must be kept separate from other components of
Requirements the same key at all times. They must be stored in separate
tamper-evident envelopes and two or more components must never
be under the control of one person. An independent observer should
be present for key generation or loading to attest that the
procedures have been followed correctly.

Hardware The use of hardware encryption is designed to reduce the chance of

Encryption key compromise, which helps to decrease the possible exposure to
fraud. Participants must utilize hardware cryptographic modules for
all cryptographic operations, including key generation and storage.
Issuers are responsible and liable for all losses that occur from
fraudulent use of CSCs and PINs. Issuers will indemnify and hold
harmless American Express and American Express Entities against
all such losses.
Thales is the preferred hardware supplier.
• Participants should contact their local Thales representative for
Thales HSM interface specifications.
• For other hardware suppliers, contact your HSM system supplier
for instructions on how to interface between the HSM and the
Network.
• Participants who use Atalla equipment must inform American
Express if variants used during key exchange will have a value
other than “no” or “zero.”
• If the Participant is not sure their current technology supports
the use of double-length ZMKs, the Participant should contact
their Hardware Security Module (HSM) vendor.

continued on next page

Page 4-32 October 2019

Key Compromise In the event encryption keys are compromised or suspected of

being compromised, American Express is to be notified in
accordance with the “Requirements for Notification of Data
Compromise” and “Participant Responsibilities Following Discovery
of Data Compromise” sections in Chapter 2 of the Business and
Operational Policies manual.
Examples of known or suspected encryption key compromise
scenarios include, but are not limited to:
• Missing/unaccounted for encryption keys or keying materials
• Missing/unaccounted for encryption devices (for example,
HSMs)
• Signs of unauthorized access to or tampering of encryption
devices, stored encryption keys or keying materials, tamper
evident envelopes, key storage safes and/or secure areas where
these items are located
• Compromise of any key under which the key was encrypted or
derived
In such cases, a new ZMK should be exchanged with AEGNS and the
affected CSCK and/or ZPK should be replaced.
Issuers are responsible and liable for all losses that occur from
compromised keys and fraudulent use of CSCs and PINs. Issuers
will indemnify and hold harmless American Express and American
Express Entities against all such losses.

Equipment Used to During cryptographic key exchanges with American Express,

Protect Participants may be requested to tell AEGNS of the cryptographic
Cryptographic equipment they use to minimize disruptions (for example, Atalla).
Keys
continued on next page

October 2019 Page 4-33

Generating and The Key Creation and Exchange process is illustrated in Figure 4-1.
Shipping Keys

Figure 4-1. The Key Creation and Exchange Illustration

Key Creation and The steps involved in key creation and exchange are shown in
Exchange Table 4-6.
Procedures
Table 4-6. Key Creation and Exchange Procedure (Exporting Participant)

Step Who Does What More Instruction

1 Each Key • Generates 1 of the 3 clear ZMK components and Important: At no time should a
Signing Offi- records the component check value KSO observe a ZMK component
cer (KSO) • Enters their clear components into the HSM to generated by another KSO.
form a double-length, TDEA (3DES) encryption
key (also known as the overall ZMK) to protect
the Zone PIN Key during transportation to Ameri-
can Express. The overall ZMK check value should
be recorded.
2 Each KSO Makes a copy of the ZMK component and check Important: If there is indica-
value for temporary storage, which is destroyed tion of a compromise of a key
when the Key Exchange process has been success- component, all new key compo-
fully completed. nents must be generated.

Page 4-34 October 2019

Table 4-6. Key Creation and Exchange Procedure (Exporting Participant)

(continued)
Step Who Does What More Instruction
3 Each KSO Immediately puts the ZMK component in tam- • Each envelope must have a
per-evident envelopes pre-printed serial number
• One for storage These envelopes are recom-
• One for transportation mended:

Note: All key components must be shipped Sentry Superior Bag Manu-
separately in a tamper-evident envelope II Bag facturing Corp.
through a secure courier service. The ZMK 759 E Lincoln Ave.
components must be shipped separately Rahway, NJ 07065
and at different times. AEGNS Telephone:
recommends that the ZMK-3 be shipped 5 908-815-9870
days after the first mailing of other key
1-800-522-1236
parts.
(Toll-free in United
The ZPK must be sent in a separate envelope.
States only)
Working keys can accompany ZMK-1.
Item # Staple Office Supply,
609145 [Link]
Model:
MMF2362010N06

4 All KSOs and Must sign the KSO and Independent Observer/Audi-
the indepen- tor Agreement included in the Key Exchange Readi-
dent ness Checklist.
observer (if AEGNS reserves the right to request from Partici-
applicable) pants, at its own discretion, documentation to vali-
date that the correct key exchange has been
performed.

5 Each KSO Seals the tamper-evident envelope; it cannot be

re-opened without destroying it
6 Each KSO Records this information on the face of each tam- Identify the envelope correctly.
per-evident envelope: You must be able to read data
• Receiving KSO # (for example, KSO #1) on the envelope.
• Receiving KSO name Problems with the key compo-
• Description and component sequence (for exam- nent envelopes can delay the
ple, ZMK 1 of 3) key exchange process by requir-
ing the keys in the envelope to
• Sending Institution
be destroyed and requested
• Key generation date and time again from the Participant.
• Sending KSO #
• Sending KSO name
• Name of the Participant
• Deal or Deal Code Name (if applicable)
• The KSO printed name and signature
7 Secure Cou- The KSO provides an envelope to the courier. The
rier (for courier delivers the envelope to the American
example, Express KSOs as detailed on the shipping label.
DHL or
FedEx)

October 2019 Page 4-35

Table 4-6. Key Creation and Exchange Procedure (Exporting Participant)

(continued)
Step Who Does What More Instruction
8 Participant Complete the Key Mailing Log form obtained from All numbers must be submitted
an AEGNS Representative. This form must include at one time.
courier(s) used and an envelope tracking numbers An AEGNS Representative
should attach the completed Key
Mailing Log form to the IT Ser-
vice Catalog request for this key
exchange. Questions or con-
cerns can be sent to [Link]-
[Link]@aex
[Link].

9 All KSOs When the Zone PIN Key has been successfully
exchanged, the ZPK and ZMK components can be
securely stored through the end of each key life
span before final destruction.

Receiving and The steps involved in receiving and loading keys are shown in
Loading Keys Table 4-7.

Table 4-7. Key Receiving and Loading Procedure (Receiving Participant)

Step Who Does What More Instruction

1 A trusted Receives the Key Mailing Log attached to the IT The Key Mailing is completed and is
employee Service Catalog request available to compare with the cou-
rier envelopes as they are received.
This is a required form and it assists
in matching courier envelopes
received to the correct key
exchange request.
2 Receiving Securely store the clear key components and/or The mailing envelopes must not be
KSOs encrypted keys when they are received. opened until it is time to load the
Refer to the current PCI Logical Security key components.
Requirements, Section 8.8 Key Storage on
[Link].
3 All 3 KSOs Must be present at the loading of the ZMK com-
ponents
4 All 3 KSOs Must do an inspection of each courier envelope If there is indication of tampering
and tamper-evident envelope for signs of tam- then the keys are compromised and
pering the Participant must regenerate and
ship the keys again.
5 Each KSO Opens their envelope and loads the ZMK com- At no time should a KSO have pos-
ponent into the HSM session of, or be in a position to
observe the ZMK component of
another KSO. The ZMK components
show as asterisks on the screen.
6 The KSO Compares the check values generated during ZMK components and check values
loading to those received from the generating should be supplied and compared
institution for each ZMK, CSC key, and PIN
key.

Page 4-36 October 2019

Table 4-7. Key Receiving and Loading Procedure (Receiving Participant)

(continued)
Step Who Does What More Instruction
7 Each KSO Puts the components into a new, separate tam- When the CSCK and/or PIN key is
per-evident envelope for secure storage (for exchanged successfully, the ZMK
example, in a safe) components must be destroyed.
8 All 3 KSOs Must sign the Auditor Agreement attesting that
and an inde- the procedures have been followed. This is an
pendent internal form used for recording and auditing
observer, if purposes.
applicable
Note: Contact your AEGNS Representative to
get the Auditor Agreement.

Exchanging A copy of the subsidiary/working key is made for back up and

Subsidiary/ recovery. The steps involved in the subsidiary/working key
Working Keys exchange are shown in Table 4-8.

Table 4-8. Subsidiary/Working Key Exchange Procedure

Step Who Does What More Instruction
1 Participant • Generates subsidiary/working keys using These subsidiary/working keys are
their Local Master Key (LMK) double length keys. Examples
• Encrypts subsidiary/working keys using the include CSCKs and ZPKs.
ZMK
2 Generating Makes a copy of the subsidiary/working key for The subsidiary/working key copy
institution back up and recovery should be stored by the generating
institution.
3 Generating Seals the subsidiary/working key in a pre-seri-
Institution alized tamper-evident envelope and transports
the subsidiary/working key encrypted under the
shared ZMK through a secure courier service
(for example, DHL or FedEx)
4 Receiving Imports the subsidiary/working key into the When the subsidiary/working key
institution HSM. It is changed from the Zone Master Key has been successfully imported, the
(ZMK) encryption to the Local Master Key (LMK) ZMK components and working keys
encryption for use must be destroyed.
5 KSOs at the Must sign the Auditor Agreement attesting that
receiving the procedures have been followed. This is an
institution internal form used for recording and auditing
purposes

October 2019 Page 4-37

Zone Master Key

Overview The Zone Master Key (ZMK) is used to protect the Card Security
Code Key (CSCK) and the Personal Identification Number Key (PIN
Key) during transportation to American Express.
In the key exchange, the ZMK is conveyed from the Participant to
AEGNS in three clear (deciphered) components. The ZMK
components must be sent to and handled by separate Key Signing
Officers (KSOs). The components must be securely stored and
follow the logical requirements as specified in the current version of
the PCI Logical Security Requirements on
[Link].

Length The American Express Encryption Key Management Standard

requires Zone Master Keys (ZMKs) to be double-length with ANSI
X9.24 and odd parity.

Important If the Participant is not sure their current technology supports the
use of double-length ZMKs, the Participant should contact their
Hardware Security Module (HSM) vendor.

Page 4-38 October 2019

Card Security Code Key (CSCK)

Overview Card Security Codes (CSCs) are values that Issuers or their
Authorized Processors can use during Authorization to validate the
Card. Issuers are solely responsible and liable for establishing and
protecting the Cards they issue from use in fraudulent Transactions.
Issuers are responsible and liable for all losses that occur from
fraudulent use of CSCs and PINs. Issuers shall indemnify and hold
harmless American Express Entities against all such losses.

Triple Data The Triple Data Encryption Algorithm (TDEA) algorithm is used to
Encryption generate the CSC. Refer to Key Management on page 4-30 for
Algorithm (TDEA) instructions on managing Card Security Code Keys (CSCKs).
TDEA encryption and decryption is supplied through an HSM.
The TDEA implementation is hardware-dependent and is not
described in this manual. TDEA is used to generate the CSCK.

Important The CSCK is unique between the Network and the Participant.

Preferred Thales is the preferred supplier of the hardware. For interface

Hardware Supplier specifications, the Participant should contact the local Thales
representative.

Other Hardware Contact your HSM system supplier for instructions on how to
Suppliers interface between the HSM and the Network.

CSCs on the Card The Card format can use three types of CSCs. They are:
• 3-digit (3CSC)—On the signature panel
• 4-digit (4CSC or 4DBC)—On the front of the Card
• 5-digit (5CSC or 5CID)—In the magnetic stripe

October 2019 Page 4-39

CSC Generation

Overview American Express supports two algorithms for generation of Card

Security Code (CSC) values:
• CSC Version 1.0 (classic)
• CSC Version 2.0 (enhanced)
The American Express Transaction validation defines card security
codes that are 5, 4, and 3 digits in length:

Table 4-9. American Express CSC Supported Algorithms

CSC CSC Location Algorithm Used

iCSC Contact 5-digit CSC value is in the Track 2 equivalent CSC Version 2.0
(AEIPS) data of the chip

iCSC Contactless 5-digit CSC value is in the Expresspay appli- CSC Version 2.0
(Expresspay) cation on the chip

CSC CSC Location Algorithm Used

5CSC 5-digit CSC value is on the magnetic stripe CSC Version 1.0 or 2.0

4CSC 4-digit CSC value is on the front of the card CSC Version 1.0 or 2.0

3CSC 3-digit CSC value is on the signature panel CSC Version 1.0 or 2.0

Issuers can use the CSC Version 1.0 or CSC Version 2.0 algorithm
to generate 5CSC, 4CSC, and 3CSC values.
Issuers can use CSC Version 2.0 to generate AEIPS (contact),
Expresspay (contactless), or both iCSC values. Issuers who use CSC
Version 2.0 to calculate the iCSC can also use it to generate 5CSC,
4CSC, and 3CSC values.
Issuers who choose to use only CSC Version 1.0 to generate CSC
values cannot differentiate the 5CSC on the magnetic stripe from
the 5CSC in the Track 2 equivalent data on the AEIPS (contact)
chip.
Issuers that use American Express SafeKeySM must use the CSC
Version 2.0 algorithm to generate the applicable value in the AEVV.
American Express SafeKey is based on the 3D-Secure protocol,
used for online, card not present payments.

continued on next page

Page 4-40 October 2019

For Dual Interface Chip Cards, Issuers who choose to use iCSC for
their contact application must also use iCSC for their contactless
application.
Issuers are required to validate the 5CSC or the iCSC generated by
CSC Version 1.0 or CSC Version 2.0 in the Authorization Request
and use the result for decisioning.
Refer to the American Express Hardware Security Module (HSM)
Vendor Documentation Function Requirements for more instruction.

October 2019 Page 4-41

Personal Identification Number Key (PIN Key)

Overview The Network supports separate keys for the acquiring and issuing
businesses. The decision to use single or separate keys is optional.
It is good to have two PIN keys in case one is compromised.

Managing PIN Refer to Creating Personal Identification Numbers on page 4-28,

Keys Generating and Shipping Keys on page 4-34, and Receiving and
Loading Keys on page 4-36 for instructions.

ATM Standard Test AEGNS uses standard test key parts to expedite testing and to tell
Keys Participants of the hardware encryption key requirements.

Example The example below shows the AEGNS ATM standard double-length,
triple-DES Zone Master Test Key parts that are used for hardware
encryption and the hexadecimal procedures that make the key
components, with the test Zone Master Key (ZMK) and Zone PIN
Key (ZPK).

98 16 70 83 19 C1 5E B3 A1 45 2A 9E 83 C7 19 34 = Part 1 Zone Master Key (ZMK1)

1A E6 46 BF 5D 8F D0 73 23 6E 5B 98 B3 8F 97 37 = Part 2 Zone Master Key (ZMK2)
23 7F A1 31 49 3E 2A 5B 1A 70 FD 5B 16 70 C1 5B = Part 3 Zone Master Key (ZMK3)
5E 08 97 04 F6 84 4B C2 = Verify Code
A1 8F 97 0D 0D 70 A4 9B 98 5B 8C 5D 26 38 4F 58 = Clear ZMK
75 FE C1 65 CF 18 1D 86 12 93 50 F8 E7 C4 A1 61 = ZMK Encrypted under LMK

Note: In the above example, the first six digits of the Verify Code
are highlighted to show that key check value matching is
frequently done on only the first six digits (for example, with
the Network Test Simulator).

continued on next page

Page 4-42 October 2019

Creating Encrypted This example shows the creation of encrypted ZMKs.

ZMKs
Component One and Component Two of the ZMK are Xor’d (exclusively or’d) together to give
an intermediate value.
98 16 70 83 19 C1 5E B3 98 16 70 83 19 C1 5E B3 = Part 1 Zone Master Key (ZMK1)
1A E6 46 BF 5D 8F D0 73 1A E6 46 BF 5D 8F D0 73 = Part 2 Zone Master Key (ZMK2)
82 F0 36 3C 44 4E 8E C0 82 F0 36 3C 44 4E 8E C0 = Intermediate Value

The intermediate value and Component Three ZMK are Xor’d (exclusively or’d) together to
yield the Clear ZMK that is used to encrypt the PIN Key under the ZMK.
82 F0 36 3C 44 4E 8E C0 82 F0 36 3C 44 4E 8E C0 = Intermediate Value
23 7F A1 31 49 3E 2A 5B 23 7F A1 31 49 3E 2A 5B = Part 3 Zone Master Key (ZMK3)
A1 8F 97 0D 0D 70 A4 9B A1 8F 97 0D 0D 70 A4 9B = Clear ZMK

The Clear Zone PIN Key (ZPK) is encrypted using the Clear Zone Master Key (ZMK) to yield
the encrypted Zone PIN Key (ZPK) for transmission from the Participant to American
Express.
U - CF AC AD 93 F2 72 4F 40 D6 05 3E ED 7A 0D = ZPK Encrypted under ZMK
DC F1
5F 81 DB 9E D4 60 F3 E9 = ZPK Verify Code
U - 16 15 11 1F E7 EB 7B 6B 68 09 60 FE 4F 30 2C = ZPK Encrypted under LMK
E6 (Odd parity)
F0 F1 F2 F3 F4 F5 F6 F7 F1 F2 F3 F4 F5 F6 F7 F8 = Clear PIN Key

October 2019 Page 4-43

Card Identification Number File

Overview Issuers who receive authorization decisioning services from AEGNS

will send the Card Identification Number (CID) File to the Network.
This shows that Cards have been issued.

What Is The CID The CID file is used during authorization to validate the four-digit
File Used For? batch code (4DBC) on the face of the Card when it is supplied in the
authorization message, or five-digit CID if it has been encoded in
the magnetic stripe.

CID File Structure Each file can contain multiple batches. A batch has:
• A header (refer to Card Identification Number Header Record on
page 4-46 for layout instructions)
• Zero, one, or more detail records (refer to Card Identification
Number Detail Record on page 4-51 for layout instructions)
• A trailer (refer to Card Identification Number Trailer Record on
page 4-55 for layout instructions)

Scrambling Issuers must scramble the Primary Account Numbers transmitted in

Primary Account the CID file with this Primary Account Number Scrambling Routine.
Numbers
• Digit 1 moves to digit 9
• Digit 2 moves to digit 3
• Digit 3 moves to digit 4
• Digit 4 moves to digit 5
• Digit 5 moves to digit 6
• Digit 6 moves to digit 7
• Digit 7 moves to digit 8
• Digit 8 moves to digit 1
• Digit 9 moves to digit 2
• Digit 10 moves to digit 12
• Digit 11 moves to digit 13
• Digit 12 moves to digit 14
• Digit 13 moves to digit 10
• Digit 14 moves to digit 11
• Digit 15 stays digit 15

continued on next page

Page 4-44 October 2019

Scramble Example Account “ABCDEFGHIJKLMNO” is scrambled as

“HIBCDEFGAMNJKLO.”
Account “375987654321001” is scrambled as “547598763003211.”

October 2019 Page 4-45

Card Identification Number Header Record

Description The Card Identification Number Header must be the first data
record of the Card Identification Number Detail file. It designates
date, time, and file identification that uniquely identify the file from
the other files processed through the Network. The forwarding
institution for the file creates the Card Identification Number Header
Record.

Message Layout This is the message layout for the file’s Header Record. Refer to the
Programming Notes for Card Identification Number Header Record
on page 4-47 for more instruction.

Card Identification Number Header Record Message Layout

Field
Format Positions Optionality Field Name
Number
1 X(1) 1 M Record Type
2 9(5) 2-6 M Record Sequence Number
3 X(5) 7-11 M Header Indicator
4 X(1) 12 M Status Indicator
5 9(3) 13-15 M Embossing Center Number
6 9(5) 16-20 M Creation Julian Date
7 X(1) 21 M Embossing Machine ID
8 9(3) 22-24 M Batch Control Number
9 9(2) 25-26 M Creation Time - Hour
10 9(2) 27-28 M Creation Time - Minute
11 X(1) 29 M Copy Indicator
12 X(1) 30 M Change Indicator
13 X(2) 31-32 M Embossing Software Version
14 X(2) 33-34 M Support Software Version
15 X(3) 35-37 F Filler
16 X(3) 38-40 M File ID

Page 4-46 October 2019

Programming Notes for Card Identification Number Header

Record
Field 1 Record Type
Definition A unique code that identifies a type of record.
Format X(1)
Positions 1
Optionality Mandatory
Notes Required Value: H Header

Field 2 Record Sequence Number

Definition A sequential number assigned to each record by the file originator. This ascending
number starts at 00001 for the first record and is incremented by one for each record
in the file.
Format 9(5)
Positions 2-6
Optionality Mandatory
Notes Required Value: 00001

Field 3 Header Indicator

Definition Indicates the file is a Card Identification Number File update.
Format X(5)
Positions 7-11
Optionality Mandatory
Notes Required Value: 11111

Field 4 Status Indicator

Definition Indicates the status of the data of this batch.
Format X(1)
Positions 12
Optionality Mandatory
Notes Required Value: 0 (zero)

Field 5 Embossing Center Number

Definition The unique number assigned to the embossing location by AEGNS.
Format 9(3)
Positions 13-15
Optionality Mandatory

October 2019 Page 4-47

Field 7 Embossing Machine ID

Definition A unique character to identify each embossing machine at an embossing center,
starting with one. This will always be 1 for a center with only one embossing
machine.
Format X(1)
Positions 21
Optionality Mandatory

Field 8 Batch Control Number

Definition A sequential control number that starts at 001 for the first batch in the first file. The
batch control number increments through 999 for each batch in a file or across files.
Batch Control Number rolls to 001.
Format 9(3)
Positions 22-24
Optionality Mandatory
Notes Not Valid: 000

Field 9 Creation Time - Hour

Definition Indicates the hour the plastic was embossed.
Format 9(2)
Positions 25-26
Optionality Mandatory
Notes Valid Values: 00 through 23

Field 10 Creation Time - Minute

Definition Indicates the minute the plastic was embossed.
Format 9(2)
Positions 27-28
Optionality Mandatory
Notes Valid Values: 00 through 59

Page 4-48 October 2019

This document contains sensitive, confidential and trade secret information, and may not be disclosed
to third parties without written consent of American Express Travel Related Services Company, Inc.
Network Specifications - Instructions
Card Identification Number Header Record
Field 11 Copy Indicator
Field 11 Copy Indicator
Definition Shows if the batch was sent before.
Format X(1)
Positions 29
Optionality Mandatory
Notes Valid Values:
• 0 = original (first time sent)
• 1 = duplicate (batch corrected and returned)

Field 12 Change Indicator

Definition Shows if the batch contains changes to a previously sent record.
Format X(1)
Positions 30
Optionality Mandatory
Notes Valid Values:
• space = default
• C = change

Field 13 Embossing Software Version

Definition Reserved for use by AEGNS.
Format X(2)
Positions 31-32
Optionality Mandatory

Field 14 Support Software Version

Definition The embossing software version auto populated by the machine.
Format X(2)
Positions 33-34
Optionality Mandatory

Field 15 Filler
Definition Filler fields show positions in a message that are not used, but must contain default
values described in the Notes section.
Format X(3)
Positions 35-37
Optionality Filler
Notes Alphanumeric Filler fields must contain spaces.

October 2019 Page 4-49

This document contains sensitive, confidential and trade secret information, and may not be disclosed
to third parties without written consent of American Express Travel Related Services Company, Inc.
Network Specifications - Instructions
Card Identification Number Header Record
Field 16 File ID
Field 16 File ID
Definition This field indicates the file is a Card Identification Number File update file.
Format X(3)
Positions 38-40
Optionality Mandatory
Notes Required Value: CID (Card Security Code)

Page 4-50 October 2019

Card Identification Number Detail Record

Description The Card Identification Number Detail file is sent by the Issuer to
the Network to update the Network on Cards that have been issued.
The file is used during Authorization to validate the four-digit batch
code on the face of the Card when it is supplied in the Authorization
message, or if the five-digit security code has been encoded in the
magnetic stripe.

Message Layout This is the message layout for the file’s Detail Record. Refer to the
Programming Notes for Card Identification Number Detail Record on
page 4-52 for more instruction.

Card Identification Number Detail Record Message Layout

Field
Format Positions Optionality Field Name
Number
1 X(1) 1 M Record Type
2 9(5) 2-6 M Record Sequence Number
3 9(15) 7-21 M Primary Account Number (PAN)
4 X(4) 22-25 M Four Digit Batch Code
5 9(2) 26-27 M Card Effective Date
6 9(2) 28-29 M Card Effective Year
7 9(2) 30-31 M Card Expiration Month
8 9(2) 32-33 M Card Effective Year
9 X(1) 34 M Change Flag
10 X(5) 35-39 F Filler
11 X(1) 40 M Card Activation Code

October 2019 Page 4-51

Programming Notes for Card Identification Number Detail

Record
Field 1 Record Type
Definition A unique code that identifies a type of record.
Format X(1)
Positions 1
Optionality Mandatory
Notes Required Value: C

Field 2 Record Sequence Number

Field 3 Primary Account Number (PAN)

Field 4 Four Digit Batch Code

Definition The number printed on a Card that identifies the production batch of the Card.
Format X(4)
Positions 22-25
Optionality Mandatory

Field 5 Card Effective Date

Definition This is the Card Effective Date embossed on the face of the Card.
Format 9(2)
Positions 26-27
Optionality Mandatory
Notes Valid Values: 01-12

Page 4-52 October 2019

Field 7 Card Expiration Month

Definition The month in which the Card is no longer valid.
Format 9(2)
Positions 30-31
Optionality Mandatory
Notes Valid Values: 01-12

Field 8 Card Expiration Year

Definition The year in which the Card is no longer invalid.
Format 9(2)
Positions 32-33
Optionality Mandatory
Notes Valid Values: 00-99

Field 9 Change Flag

Definition Indicates the action taken on this record by the embossing center.
Format X(1)
Positions 34
Optionality Mandatory
Notes Valid Values:
• space = default
• C = change

Field 10 Filler
Definition Filler fields show positions in a message that are not used, but must contain default
values described in the Notes section.
Format X(5)
Positions 35-39
Optionality Filler
Notes Alphanumeric Filler fields must contain spaces.

October 2019 Page 4-53

Page 4-54 October 2019

Card Identification Number Trailer Record

Description The Card Identification Number Trailer Record is the last record in
the file. The trailer record echoes data from the Card Identification
Number Header Record. The forwarding institution creates the
trailer record.

Message Layout This is the message layout for the file’s Trailer Record. Refer to the
Programming Notes for Card Identification Number Trailer Record
on page 4-56 for more instruction.

Card Identification Number Trailer Record Message Layout

Field
Format Positions Optionality Field Name
Number
1 X(1) 1 M Record Type
2 9(5) 2-6 M Record Sequence Number
3 9(5) 7-11 M Trailer Indicator
4 X(1) 12 F Filler
5 9(3) 13-15 M Embossing Center Number
6 9(5) 16-20 M Creation Julian Date
7 X(1) 21 M Embossing Machine ID
8 9(3) 22-24 M Batch Control Number
9 9(6) 25-30 M Record Count
10 X(7) 31-37 F Filler
11 X(3) 38-40 M File ID

October 2019 Page 4-55

Programming Notes for Card Identification Number Trailer

Record
Field 1 Record Type
Definition A unique code that identifies a type of record.
Format X(1)
Positions 1
Optionality Mandatory
Notes Required Value: T Trailer

Field 2 Record Sequence Number

Field 3 Trailer Indicator

Definition Indicates the type of record.
Format 9(5)
Positions 7-11
Optionality Mandatory
Notes Required Value: 99999 Trailer

Field 4 Filler
Definition Filler fields show positions in a message that are not used, but must contain default
values described in the Notes section.
Format

X(1)
Positions 12
Optionality Filler
Notes Alphanumeric Filler fields must contain spaces.

Field 5 Embossing Center Number

Definition The unique number assigned to the embossing location by AEGNS.
Format 9(3)
Positions 13-15
Optionality Mandatory
Notes AEGNS assigns the same value as in the header record.

Page 4-56 October 2019

Field 7 Embossing Machine ID

Field 8 Batch Control Number

Field 9 Record Count

Definition Indicates the total number of detail records in the file.
Format 9(6)
Positions 25-30
Optionality Mandatory

Field 10 Filler
Definition Filler fields show positions in a message that are not used, but must contain default
values described in the Notes section.
Format X(7)
Positions 31-37
Optionality Filler
Notes Alphanumeric Filler fields must contain spaces.

October 2019 Page 4-57

This document contains sensitive, confidential and trade secret information, and may not be disclosed
to third parties without written consent of American Express Travel Related Services Company, Inc.
Network Specifications - Instructions
Card Identification Number Trailer Record
Field 11 File ID
Field 11 File ID
Definition This field indicates the file is a Card Identification Number File update file.
Format X(3)
Positions 38-40
Optionality Mandatory
Notes Required Value: CID (Card Security Code)

Page 4-58 October 2019

Emergency Card Replacements

Overview Emergency Card Replacement (ECR) replaces a Card for a

Cardmember when it is lost or stolen.

Who Assigns Card Issuers assign the Primary Account Number.

Numbers?

Current ECR Current ECRs use ANSI X4.16 standards for magnetic stripes.
Standards Issuers must recognize and support this format. Refer to ANSI
X4.16 Track 1 and 2 Format on page 4-15 for instructions.

Card Security Code Currently, ECR does not support Card Security Code (CSC) or an
Support encryption key exchange process between Participants.
The CSC on Track 1 or Track 2 is created without using the Issuers
encryption. The Issuer should not deny a request that comes in with
an ANSI X4.16 standard format Track 1 or Track 2 due to failing CSC
validation.
Participants that use a DES-based encryption to make CSC values in
the magnetic stripe cannot create ECR plastic for other Participants.

ATM Usage A Cardmember cannot get cash access at an ATM with an

Emergency Card Replacement Card.

ECR Validity Refer to the Business and Operational Policies manual - Product
Features and Specifications - Emergency Card Replacement section
for the number of days the ECR is valid.

October 2019 Page 4-59

Page 4-60 October 2019

Chapter 5 Technical Certification

What Is Certification?

Overview Participants go through the technical certification process to make

sure they can send and receive all files and messages before they
get access to the Network.
AEGNS tells Participants the necessary level of certification, which
can include Phase I, Phase II, Phase III, or all phases. It can also
include Beta (Phase IV). Refer to Certification Phases Overview on
page 5-3 for instructions.
AEGNS and Participants work together to plan and schedule
certification. A Participant must contact their AEGNS Representative
to start the procedure.
Refer to Feature Certification on page 5-13 for information on
certifying for more features.

What Must Be Technical certification is necessary for these systems:

Tested?
• Authorizations
• Clearing and Settlement
• Telecommunications Connectivity, with Global Online Business
Exchange (GLOBE)
• GNS Fraud Repository (GFR)
• Data Collection
• Other interfaces (as necessary)
Technical certification is done with the Network using the Global
Online Business Exchange (GLOBE).

continued on next page

October 2019 Page 5-1

Participant Roles This table describes the Participant resources and responsibilities
and necessary for successful certification.
Responsibilities
Table 5-1. Participant Certification Responsibilities
Participant Owner Responsibilities
Coordinator/Project • Participant test coordination
Manager • Assist in scenario preparation where necessary
• Review Test Cases
Interface Owners Manage overall flow of test files over the Network
for the Participant

Page 5-2 October 2019

Certification Phases Overview

Self-Validation Self-Validation Testing allows Participants to confirm changes which

Testing do not require AEGNS verification or certification.

Phase I Phase I is unattended testing with the Network Test Simulator. Refer
to Role of the Network Test Simulator (NTS) in Certification on page
5-14 for more instruction about the NTS.
In this phase, Participants send and receive a sample of messages
with no Network connection. For Phase I, AEGNS supplies the test
scripts. Refer to Phase I: Unattended Testing on page 5-6 for
instruction about Phase I.

Important Acquirers and Issuers must complete unattended testing for

Authorizations, Clearing and Settlement, Fraud, and Data Collection
messages, as applicable for the installation.
When the Participant can send and receive messages with the
correct technical specification bit format, then Phase I is complete.
Phase I must be verified by AEGNS before the Participant starts
Phase II and Phase III.

Phase II During Phase II, the telecommunication connectivity is validated

(that is, can the Participant test host communicate with the AEGNS
test host). Phase II can also include echo message testing and POS
Issuer Sign On and Sign Off messages.
AEGNS and the Participant are responsible for Phase II testing.
Refer to Phase II: Telecommunication Connectivity Testing on page
5-8 for more information regarding Phase II.
Note: Participants cannot continue to Phase III until Phases I and
II are completed.

continued on next page

October 2019 Page 5-3

Phase III Phase III interfaces with the Network test environment.
The Participant will pass a set of messages and file types to the
Network through the GLOBE (test host to test host) to verify the file
and message formats and processing capability.
The AEGNS Coordinator and the Participant’s Test Coordinator
schedule this testing. AEGNS verifies a Participant’s compliance with
all AEGNS message standards and process flows and makes sure
the Participant can send and receive messages and files in the
correct format. Refer to Phase III: Testing with AEGNS on page 5-9
for more information regarding Phase III.
Note: Before the Participants start Beta Testing, they must
complete Phase III testing for Authorizations, Clearing and
Settlement, and Data Collection as applicable for the
installation.

Important New AEGNS Participants

A Participant has 60 calendar days to start production traffic of
authorization features when the certification procedure is complete.
After the 60 calendar day period, if the Participant has not put the
feature into production, the Participant must certify again.
Existing AEGNS Participants Adding Authorization Features
A Participant has 30 calendar days to start production traffic of new
authorization features when the certification procedure is complete.
After the 30 calendar day period, if the Participant has not put the
feature into production, Participants must complete a regression
test.

Beta Testing Beta Testing is a “controlled test” in a production environment for

operational and technical functionality. It encompasses a small
number of Transactions run end-to-end through the Network.
Components must be reconfigured to function in a production
environment. For example, ports and other settings on the
Participant host and the GLOBE that have been set for the test
system must be reconfigured to connect to the production system.
Beta Testing makes sure that the reconfiguration of the components
was completed correctly.

continued on next page

Page 5-4 October 2019

Beta Testing is coordinated and occurs between AEGNS and Issuer

resources using Participant-issued, live test Cards. A Beta test script
is created, and a pre-determined number of Transactions are run
end-to-end through the production systems for AEGNS and the
Issuer.
Note: A Beta Test is not usually necessary for feature certifications.
It can be necessary for business purposes.

Completion On the successful completion of Beta Testing, the Participant is

certified and can do business on the Network.

October 2019 Page 5-5

Phase I: Unattended Testing

Overview Participants on the Network must receive and respond to all:

• Authorization messages that are being certified
• Clearing and Settlement messages that are being certified
• Data Collection messages that are being certified
• GFR messages that are being certified
Messages have been pre-loaded on the Network Test Simulator to
complete the supplied test scripts.

Important Phase I testing must be completed and verified by AEGNS before

Phase II and Phase III testing starts.

Authorizations The pre-loaded messages include POS and ATM Transactions that
support the Phase I requirements:
• Can an Issuer format approval and denial Authorization
Responses to requests from the Network
• Can an Acquirer format and send requests and receive
Authorization Responses from the Network
AEGNS supplies a test script for the Participants to use during
Phase I (unattended) and Phase III (attended) testing.

Clearing and The Network Test Simulator uses the results of Authorization testing
Settlement to make files for a life cycle test. These are two procedures to make
files:
• Run a set of prescribed Authorization tests
• Create an off-line file
Participants can use these files to create First Presentments and all
associated messages of the Transaction life cycle. This process
fulfills the Phase I requirement to Inclear and Outclear files to and
from the Network.

continued on next page

Page 5-6 October 2019

Data Collection The Network Test Simulator is a testing environment that supports
the Participant’s Phase I requirement to submit and receive Data
Collection Files to/from the Network.

GFR The Network Test Simulator is a testing environment that supports

the Participant’s Phase I requirement to submit and receive GFR
files to/from the Network.

October 2019 Page 5-7

Phase II: Telecommunication Connectivity Testing

Overview A GLOBE is installed at the Participant site to connect to the

Network. After the GLOBE is set up, telecommunication connectivity
testing occurs. This testing verifies file formats and complete
connectivity between the Participant host, the GLOBE, and
telecommunications lines through to the Network.

Important Phase II testing must be completed and verified by AEGNS before

Phase III testing starts.

Responsible AEGNS and the Participant are responsible for this testing.
Parties

Phase II Activities During the Phase II test call, AEGNS and the Participant work
together to establish the communication between the Participant’s
test host and the Network test host, to make sure that:
• Participants can send and receive files across the Network
• Participants can send and receive messages across the Network
Note: AEGNS supplies the specific activities to make sure
communication has been established.

Page 5-8 October 2019

Phase III: Testing with AEGNS

Overview Phase III certification is a live test between the AEGNS test host
and the Participant’s test host.

Authorization The Participant must successfully execute the required

Authorizations online test scripts through the GLOBE to the Global
Network Services Authorization System (GNSAS)—test host to test
host. Successful execution is the completion of the necessary test
cases with no errors.

Clearing and The Participant must successfully send and receive multiple batch
Settlement Clearing and Settlement files, based on the Phase III Clearing and
Settlement test scripts, through the GLOBE to the Network (test
host to test host). Execution of these life cycle iterations occur over
several days (feature certification, refer to Feature Certification on
page 5-13 for more information) to several weeks (new Participant
certification).

Data Collection The Participant must successfully send and receive Data Collection
files.

GFR The Participant must successfully send and receive GFR files. Refer
to Clearing and Settlement to Fraud Mapping in the Network
Specifications - Financial/Non-Financial manual for a table that
maps First Presentment (1240) message fields to Fraud Report
Record (9324) fields.

Test Scripts Data Collection files do not have test scripts. To complete testing,
refer to the Data Collection Messages chapter in the Network
Specifications - Financial/Non-Financial manual for the correct
values of each field.

Card Magnetic After Cards are made, and before implementation, AEGNS certifies
Stripe the magnetic stripe encoding on the Cards as part of Phase III
certification. Issuers are responsible for sending test Cards to
AEGNS for certification as described in Test Cards on page 4-24.
Contact your AEGNS Representative to schedule certification of
Cards.

continued on next page

October 2019 Page 5-9

Chip Cards The AEGNS Smart Solutions team directly supports all Chip Card
implementations and special requirements. If embarking on a Chip
Card implementation, contact your AEGNS Representative to
arrange an introduction to the AEGNS Smart Solutions team.

Page 5-10 October 2019

Certifying Issuers

Issuer Issuers on the Network must be certified to:

Requirements
• Receive and respond to Network-compliant, online Authorization
messages as specified in the Authorization Messages chapter in
the Network Specifications - Authorization manual
• Receive and submit Network-compliant, batch Clearing and
Settlement files containing financial and administrative
Transactions as specified in the Financial Messages chapter in
the Network Specifications - Financial/Non-Financial manual
• Receive and submit Network-compliant, batch Data Collection
files as specified in the Data Collection Messages chapter in the
Network Specifications - Financial/Non-Financial manual
• Send and/or receive other file and message types and reports

October 2019 Page 5-11

Certifying Acquirers

Acquirer Acquirers on the Network must be certified to:

Requirements
• Send and receive Network-compliant, online Authorization
messages as specified in the Authorization Messages chapter in
the Network Specifications - Authorization manual
• Submit and receive Network-compliant, batch Clearing and
Settlement files containing financial Transactions as specified in
the Financial Messages and Addenda Messages chapters in the
Network Specifications - Financial/Non-Financial manual
• Submit Network-compliant, batch Data Collection files as
specified in the Data Collection Messages chapter in the Network
Specifications - Financial/Non-Financial manual

Page 5-12 October 2019

Feature Certification

What Is It? Feature certification lets Participants and Authorized Processors stay
current with the Network file and record formats and/or select
functionality that is necessary for their business.
Note: Participants should not implement new coding for Network
functionality into their systems until AEGNS finds their
certification to be complete.

Certifying for AEGNS releases functionality two times each year. The functionality
Release has changes that can be mandatory or optional:
Functionality
• Mandatory feature - All Participants are required to certify in
AEGNS time frames.
• Optional feature - Certification can be necessary for Participants
who use the functionality.
Note: Contact your AEGNS Representative to schedule feature
certification.

Phases AEGNS tells Participants the necessary level of certification, which

can range from Phase I only to Phase I through Phase III.

Important After Feature certification is complete for Authorization-related

features, the Participant has thirty calendar days to implement. If
the feature(s) are not implemented within thirty days of Phase III
certification completion, Participants must complete regression
testing for that feature.

Schedule and The schedule and scope of a feature certification is communicated

Scope to the Participant in a separate Participant communication
document sent by AEGNS.

October 2019 Page 5-13

Role of the Network Test Simulator (NTS) in Certification

What is the The NTS is a web-based testing tool that simulates the Network
Network Test processing of authorization, financial, and data collection messages.
Simulator? All Participants must use the NTS to complete Phase I testing
without requiring a direct connection to the Network.

When is the NTS The NTS is updated when changes are published in the monthly
Updated? Network Participant Update.

More Instruction Refer to the Fees chapter in the Business and Operational Policies
manual for information on the fees associated with the Network Test
Simulator.

Page 5-14 October 2019

Chapter 6 Reporting Fraudulent Transactions

GNS Fraud Repository (GFR)

What Is It? The GFR stores fraud Transaction data sent to the Network by
Issuers.

Fraud Prevention As part of the Network fraud prevention service, Issuers must
Services supply data about known fraud Transactions. The Network uses this
fraud data for risk services with, but not limited to:
• Fraud MIS Reporting
• High Risk Service Establishment (HRSE) Identification
• Recurrent Cardmember Loss Identification
• S/E Submission Monitoring
• Points of Compromise Identification
• Risk Decisioning Tool Development
• Audit Reporting

More Fraud Contact your AEGNS Representative with fraud services requests.
Services

How Is Fraud Data The Network uses data from the GFR to create MIS Fraud reports.
Used? The Network uses the Fraud Report Record (9644) message to
inclear fraud reports. It also displays the report on GNS FraudNet on
Knowledge Base ([Link]/knowledgebase).
All Issuers who submit fraud Transactions to the GFR receive fraud
reports. Acquirers receive similar fraud reports. These reports track
and monitor the types of fraud submitted to the Network. The
reports show summary gross and net fraud loss data.
Refer to the Security and Fraud chapter of the Business and
Operational Policies manual for policies regarding the reporting of
fraud Transactions.

October 2019 Page 6-1

Submitting Fraud Updates to the GFR

Fraud Repository Fraud data is sent from the Issuer to the GFR in the Fraud
Update (9324) Repository Update (9324) message. Each Fraud Repository Update
(9324) message contains data from one fraud Transaction.
Issuers can use the Fraud Repository Update (9324) message and
the appropriate Function Code to:
• Add a new fraud Transaction
• Update an existing fraud Transaction
• Delete an existing fraud Transaction
Refer to the Fraud Repository Update and Response (9324/9334)
message in the Network Specifications - Financial/Non-Financial
manual for message layout instructions.

Certification Issuers must be certified to send the Fraud Repository Update

(9324) message to the GFR. Contact your AEGNS Representative to
schedule certification.

Submission Each Issuer sends Fraud Repository Update (9324) records in a

Frequency fraud update file as frequently as necessary. Refer to Fraud
Repository Update File Structure on page 6-5.
AEGNS’ policy requires Issuers to send fraud Transactions within
one business day after the Transaction is confirmed as fraud.

Fraud Chargeback An Issuer can send a First and Final Chargeback Notification (1442)
Process message, with an appropriate Message Reason Code, only when a
fraud record exists in the GFR.
If a fraud record does not exist, the 1442 message rejects with a
Reject Reason Code 5022 - Issuer Fraud Chargeback Reason Code
Invalid.
Note: Refer to Chapter 7 in the Business and Operational Policies
manual for Message Reason Code Chargeback instruction.

continued on next page

Page 6-2 October 2019

No Fraud If a Participant does not send fraud Transactions for a month, the
Participant must send an empty data file by the third business day
of the next month to show that no fraud occurred. An empty
dataset is defined as a header record and trailer record with zero
hash count. Refer to the Business and Operational Policies manual
for instruction.
Note: There are no 9324 update records in an empty data file, so
the response file sends a 9844 file header and a 9845 file
trailer. Field 18 - Systems Trace Audit Number in the Fraud
Repository Response (9334) message echoes the File
Sequence Number from the outcleared Data Collection File
Header (9844) message.

Submission Issuers report fraud Transactions to the GFR using the Issuer’s
Currency settlement currency with the Network. This currency can be the
same as or different from the Cardmember billing currency or the
currency of the first Transaction. The Network converts the fraud
Transaction amount into the currency of the Network (U.S. Dollars)
on the date the Network receives the Transaction.
Note: The Cardmember Billing Amount is reported in the currency
defined in the Issuer’s agreement with the Cardmember and
must be supplied by the Issuer.
The Issuer must report these amounts and currencies to the Fraud
Repository Update (9324).
• Fraud Transaction Amount as it is in the Issuer Gross Settlement
Amount on the First Presentment (1240)
• First Presentment Transaction Amount as it is in the Transaction
Amount on the First Presentment (1240)
• First Presentment Presentment Amount as it is in the First
Presentment Presentment Amount on the First Presentment
(1240)

continued on next page

October 2019 Page 6-3

Automatic Fraud All Issuers are automatically certified for automatic fraud update
Update when they certify for GNS Fraud Repository Update/Response
(9324/9334) messages.
• All Issuers must submit fraud Transactions to the GFR using the
GNS Fraud Repository Update (9324) message with a Fraud
Chargeback Status Indicator of 10 (Initial Fraud Report) and
Function Code 301 (Add Record).
• When Issuers submit First and Final Chargebacks and when
Acquirers submit Second Presentments, the Network
automatically updates the status of the existing fraud
Transaction in the GFR. Issuers must not update the Fraud
Chargeback Status Indicator after the first reporting, since the
Network automatically updates this field.
Example: If a Chargeback is submitted, the Network searches
the GFR to locate an existing fraud Transaction with the same
Transaction Identification Number (TID) as the Chargeback
record. If a match is found, the Network automatically updates
the liability status (Field 28) of the existing fraud record.
Issuers can submit Fraud Repository Update records to change data
(except Field 28) during the life cycle of a Transaction. This is done
using a Function Code of 302 (Change Record) or 303 (Delete
Record).
Exception: Issuers on Network releases before 2001 must submit
GNS Fraud Repository Updates (9324) using Fraud Chargeback
Status Indicators 20, 30, 40, or 50 to show a financial liability
change for an existing fraud Transaction.

Fraud Types Issuers must categorize each fraud Transaction into a specific fraud
type. Throughout the fraud Transaction life cycle, the Issuer must
report changes to the fraud type for each fraud Transaction. Table
6-1 Fraud Type Fields and Locations shows the fraud type data fields
in the Fraud Repository Update (9324).

Table 6-1. Fraud Type Fields and Locations

Fraud Type Field Name Fraud Type Field Positions
Fraud Type Code 262-263

Issuer Fraud Chargeback Status 264-265

Indicator
Issuer Fraud Chargeback Reason Code 266-269

continued on next page

Page 6-4 October 2019

Changing Fraud After the Issuer reports the initial fraud Transaction to the GFR, the
Types Issuer can change the fraud type, if necessary, after more
investigation. To change the fraud type of an existing fraud
Transaction, the Issuer resubmits the fraud Transaction using the
Fraud Repository Update Record (9324) with Function Code 302, to
show the correct fraud type in the Fraud Type Code field. The
Network matches the record with the existing fraud Transaction
using the Transaction Identifier (TID) and automatically updates the
GFR.

Fraud Repository Figure 6-1 illustrates the composition of a fraud repository update
Update File file.
Structure
Fraud update file outcleared from a
Participant to the GNS Fraud
Repository

Data Collection GNS Fraud Repository Data Collection

File Header Update Messages File Trailer
(9844) (9324) (9845)

Figure 6-1. Fraud Repository Update File Structure

The Fraud Repository Update (9324) file has these records:

• A Data Collection File Header (9844) record
• One or more Fraud Repository Update (9324) records
• A Data Collection File Trailer (9845) record
Refer to the Data Collection File Header (9844) and the Data
Collection File Trailer (9845) messages in the Network Specifications
- Financial/Non-Financial manual for message layout instructions.

Fraud Transaction The Network can require Issuers to do a reconciliation to validate

Precision the precision of the fraud Transaction data in the GFR.1 Issuers are
responsible for data precision and consequential action of loss as a
result of errors.

[Link] can validate the precision of fraud Transaction data through the
Cardmember Detail Search on GNS FraudNet on
([Link]/knowledgebase). Use the Search function to
locate the GNS FraudNet User Guide for more instruction.

October 2019 Page 6-5

Network Response to Fraud Updates

Fraud Repository When an Issuer submits a fraud update file to the GFR, the Network
Response (9334) responds with a Fraud Repository Response (9334) message to
show how the file was processed. This response message echoes
the data supplied in the outclear file with some exceptions, (for
example, the File Sequence Number (positions 5-10)) is replaced
with the sequence number generated out of the GFR and the
population of error codes, if applicable. Data can be supplied in
selected fields, with Reject Reason Codes and Transaction Identifier
(TID). Refer to the Fraud Repository Update and Response
(9324/9334) message in the Network Specifications -
Financial/Non-Financial manual for message layout instructions.

Transaction A unique TID tracks each fraud Transaction through the GFR. The
Identifier (TID) Issuer must use the TID assigned to the Transaction in the First
Presentment record to provide the initial Fraud Repository Update
(9324). This TID then follows the fraud Transaction throughout the
fraud life cycle.

Table 6-2. Transaction Identifier in Fraud Transactions

If... Then...
The Issuer has the TID • The Issuer supplies that TID in the first
assigned to the Transaction Fraud Repository Update Record (9324)
in the First Presentment • That TID follows the fraud Transaction
throughout the fraud life cycle
Important: It is critical to use the Transaction Identifier from the Fraud
Repository Update (9324) message to identify the fraud Transaction in all
future Fraud Repository updates.

Fraud Response After the Fraud Repository Update (9324) message is processed,
File Structure the Network updates the GFR and echoes a Fraud Repository
Response (9334) message to the Issuer, identifying the processing
done on the update file. The Fraud Repository Response contains all
Issuer-submitted records with the modifications to each data
collection message.

continued on next page

Page 6-6 October 2019

Figure 6-2 depicts the various combinations possible for the

response file. The contents of the Fraud Repository Response file
depend on the acceptance status of the associated Fraud Repository
Update file.

Fraud Response File From Fraud Response File From Fraud Response File From
the Network to the Issuer the Network to the Issuer the Network to the Issuer
or Processor or Processor or Processor

ALL RECORDS ACCEPTED PARTIAL RECORDS FILE IS REJECTED

ACCEPTED

Data Collection Data Collection File

Data Collection Header (9844)
File Header File Header (In rejected files,
(9844) (9844) positions 97-136
updated with Reject
Reason Code(s) for the
entire file)

All message(s) with

All message (s) with updated Message Type All message(s) from the
updated Message Identifier (9334), and original file (9324) as
Type Identifier Action Code. In rejected outcleared to the
(9334) and Action records, positions 97-136 Network (including the
Code updated with Reject original header and
Reason Code(s) trailer)

Data Collection Data Collection Data Collection

File Trailer File Trailer File Trailer
(9845) (9845) (9845)

Figure 6-2. Fraud Repository Response File Structure

continued on next page

October 2019 Page 6-7

Accepted and When the Fraud Repository Update file has been accepted and
Processed Fraud processed, the Fraud Repository Response file has these records:
Repository Update • A Data Collection File Header (9844) record
File Structure
• One or more Fraud Repository Response (9334) records
• A Data Collection File Trailer (9845) record

Rejected Fraud When the entire fraud update file has been rejected, the first file,
Update File with a new header and trailer, is returned as shown below:
Structure
• New Data Collection File Header (9844)
• The first fraud update file, with the Data Collection File Header
(9844), each of the Fraud Repository Update (9324) records as
they were submitted to the Network, and the Data Collection
File Trailer (9845)
• New Data Collection File Trailer (9845)

Response The Network can echo more than one Fraud Repository Response
Frequency file to an Issuer or an Issuer Authorized Processor in one day.
Issuers must make sure that they or their Authorized Processor can
receive multiple Fraud Repository Response files without overwriting
existing files. The Network makes sure this is part of the
certification procedure.

Page 6-8 October 2019

Fraud Reports

Fraud Report Participants get Fraud reports from:

Delivery
• GNS FraudNet on
[Link]/knowledgebase. Use the Search
function to locate the GNS FraudNet User Guide for instructions
about receiving fraud reports online.
• The Fraud Report Record (9644) through the GLOBE.
Note: Participants receive reports in U.S. Dollars.

October 2019 Page 6-9

Fraud Reports Received Through the GLOBE

Overview These sections describe the report delivery process for Issuers and
Acquirers receiving fraud reports through the GLOBE.
Fraud reports supply summaries of fraud data to each Issuer who
sent fraud Transactions to the GFR and each Acquirer that has S/Es
with fraud Transactions.

Fraud Report Refer to Fraud Reports on page 7-94 for report frequency.
Frequency

Report The fraud reports summarize fraud activity by fraud type, industry,
Summarization and reporting district.
A Fraud to Gross Ratio can be calculated and reported to Acquirers
on a monthly basis. This ratio is derived from S/E sales volume data
reported to the GFR.

Business Use These sections give instructions about the business use of the fraud
reports. Most reports show this data about the fraud activity of an
Issuer or Acquirer during the last 24 months:
• Fraud type
• Monthly totals
• Year-to-date totals
• Year-over-year comparison (available when data has been
submitted for 24 months)
• Variance percentages
• Gross fraud, Chargebacks, and net fraud

continued on next page

Page 6-10 October 2019

GLOBE Delivery The Network delivers fraud reports to Participants in an electronic

format in the Fraud Report Record (9644). Fraud Report Records
contain data about the fraud report, with the report name and the
contents of each report line. The report file contains the data from
several reports that the Participant is certified to receive.
The fraud report file has:
• A Data Collection File Header (9844)
• One or more Fraud Report Records (9644)
• A Data Collection File Trailer (9845)
Refer to the Fraud Report Record (9644) message in the Network
Specifications - Financial/Non-Financial manual for message layout
instructions.

The Importance of The Fraud Transaction Date determines which month’s fraud activity
Fraud Transaction receives the new or updated fraud data outcleared by Participants
Date to the Network. The GFR uses the date of the fraud Transaction, not
the fraud report date, to show accurate fraud activity.
Each month, the Network calculates Issuer and Acquirer fraud
measurements based on the available fraud data supplied by the
Issuer. Because of the time delay in fraud discovery, fraud cannot
be reported to the GFR until one or more months after the fraud
Transaction date. Therefore, the monthly fraud totals for recent
months can change each month as new fraud Transactions are
discovered and confirmed by Issuers.
The fraud Transaction date effects the fraud reports as follows:
• The fraud amount reported for the prior month can change as
fraud Transactions are reported and financial responsibility is
determined. An Issuer’s reported gross fraud amount typically
stabilizes after the fraud lag time.
• The fraud amounts reported for a given month accurately show
the fraud that occurred in that calendar month. These amounts
show accurate monthly fraud ratios when compared against
sales volume for the same month.

continued on next page

October 2019 Page 6-11

Financial As fraud Transactions change financial responsibility through the

Responsibility chargeback process, the Network updates the monthly fraud totals
accordingly.

9644 Structure More than one line of a report can be captured in a single Fraud
Report Record (9644) record. Each 9644 record contains nine fields
(Report Line numbers 1-9) which are used to store each report line
in the order they appear on the report. The Participant reads each
9644 record to identify the number of report lines in the record, and
then prints them.
Example: A fraud report that has 25 printed report lines is made up
of 25 report line fields. Since the Fraud Report Record can only
contain nine report line fields, it takes three Fraud Report Records
to hold the 25 lines. There are nine on the first record, nine on the
second record, and seven on the third record.

Creating Reports Use these fields in the Fraud Report Record (9644) to assemble the
from the 9644 report from each report line:
• Message Transaction Sequence Number - This identifies the
number of records that go together to create one report. The
records are numbered sequentially for each report. Numbering
starts over for each Participant’s report in the file.
• Number of Report Lines Present - This identifies how many of
the nine report line fields in the Fraud Report Record contain
report lines. Typically, all of the records in a single report
(identified by the Message Transaction Sequence Number field)
use all nine fields except for the last record, which uses only as
many fields as required to complete the report.

Page 6-12 October 2019

Submitting High Risk Indicators

High Risk Indicator High Risk Indicators are submitted to the Network by Acquirers
Submission using GNS FraudNet on
[Link]/knowledgebase.

Financial Liability Acquirers are subject to Fraud Full Recourse Chargebacks and
accept liability for fraud Transactions at S/Es that are on the GNS
High Risk List. Refer to the Business and Operational Policies
manual for chargeback policies.

October 2019 Page 6-13

Accessing the High Risk S/E List

Overview The High Risk S/E (HRSE) List supplies all eligible1 GNS FraudNet
Participants with a list of S/Es that are categorized as high risk.

Where To Find the Participants can see and download the High Risk S/E List from GNS
HRSE FraudNet on [Link]/knowledgebase.

[Link] GNS FraudNet Participants refers to personnel who are responsible

for disputes or fraud-related issues in a Participant organization.

Page 6-14 October 2019

Fraud Mitigation Tools

Dynamic Fraud Dynamic Fraud Management Network Services (DFMNS) utilizes

Management real-time fraud mitigation tools to detect fraudulent charges during
Network Services POS credit Authorizations.
Global Network Services Authorization System (GNSAS) helps
determine the fraud risk associated with each Transaction by
providing real-time:
• Fraud Probability Scoring - This is a 5 byte, numeric value from
0 to 1, where a higher value means a greater potential risk.
• Recommendation Code - This is a 3 byte, numeric value which
corresponds to a description of the fraud risk associated with the
Transaction. Refer to the Codes Reference Guide Fraud Indicator
section for a list of DFMNS Recommendation Codes.
AEGNS recommends that Issuers certify to receive both the
Probability Score and the Recommendation Code in Bit 62 - Fraud
Indicators to help in their Authorization decisioning.

October 2019 Page 6-15

Page 6-16 October 2019

Chapter 7 Reports

Reports Delivery

Report Delivery The Network-generated reports described in this chapter are sent to
Participants through the Global Online Business Exchange (GLOBE)
report delivery function.
The GLOBE links the Participant’s host to the Network and supports
the electronic transfer of reports from the Network to Participants.
The Program Progress Reports sent to AEGNS by the Participants
are delivered by signing onto Knowledge Base and accessing the
reports directly.

Printing The Participant users can print the reports or see the reports in their
own report viewing software.
The Program Progress Reports can only be printed through the
Internet Explorer print option.

More Instruction Refer to Chapter 5 Global Online Business Exchange (GLOBE) or

contact your AEGNS Representative for more instruction regarding
the GLOBE.

Available Reports Table 7-1 Overview of Available Reports lists available reports with
the report types, names, IDs, generating systems, and frequency of
delivery. Refer to the report section for more instruction.

Table 7-1. Overview of Available Reports

Generating
Report Type Report Name Report ID Frequency
System
Program Progress Card Statistics by Product Issuer Monthly
Reports
Billings and Fees by Industry and Issuer Monthly
Card Product
Account Balances Outstanding, Issuer Monthly
Write-offs, and Recoveries
Membership Rewards Statistics by Issuer Monthly
Product
Merchant Statistics by Industry Acquirer Monthly
Local and Inbound Discount Acquirer Monthly
Business and Transactions by
Industry

October 2019 Page 7-1

Table 7-1. Overview of Available Reports (continued)

Generating
Report Type Report Name Report ID Frequency
System
Authorization CAS Activity Summary – BC050AA0 Network Monthly
Reports Authorizations Activity
CAS Activity Summary by Point of BC056AA0 Network Monthly
Sale
CAS Activity Summary by S/E Type BC057AA0 Network Monthly
CAS Activity Summary – Entry BC055AA0 Network Monthly
Activity
Authorization Transaction Edit BC043AA0 Network Daily
Error Detail
Unacknowledged Voids, Refunds, BC045AA0 Network Daily
and Reversals Report
Authorization Transaction Stand-In BC040AA0 Network Daily
Detail
Authorization Deferred Payment BC044AA0 Network Daily
Plan (DPP) Transaction Detail
Report
Authorization Transaction Detail BC041AA0 Network Daily
Acquirer Detail BC042AA0 Network Daily
Exception Detail Report BC059AA0 Network Monthly
Authorization Decline Transaction BC053AA0 Network Monthly
Stand-In Detail Report
Authorization Referred Stand-In BC053AA0 Network Monthly
Detail Report
Recurring Billing Cancellation
Records Reports
• Active Records Reports BC059AA1-A Network Monthly
• Changed and Deleted Records BC059AA1-C Network Monthly
Report
Clearing and Daily Settlement Advisement Network Daily
Settlement Reports
Daily Activity Report (DAR)
External File Tracking Report NUDAD816-01 Network Daily
Net Settlement Summary Report NUDAD816-01 Network Daily
Gross Settlement Summary Report NUDAD816-01 Network Daily
Network Fee Summary Report NUDAD816-01, Network Daily
Part 1.C
Issuer’s/Network Rate Amount NUDAD816-01 Network Daily
Summary Report
Current Day Activity - Warehoused NUDAD816-01, Network Daily
Transactions Part 1.E
Accumulated Activity - NUDAD816-01, Network Daily
Warehoused Transactions Part 1.F
Non-Financial Summary Report NUDAD816-01, Network Daily
Part 1.G

Page 7-2 October 2019

Table 7-1. Overview of Available Reports (continued)

Generating
Report Type Report Name Report ID Frequency
System
Issuer’s/Network Rate Amount by NUDAD816-01, Network Daily
Industry Segment Report Part 1.H
Non-Cleared Transaction Summary NUDAD816-01, Network Daily
Part 1.I
Returned Transaction Summary NUDAD816-01, Network Daily
Report Part 1.J
Network Fee Summary by VBU NUDAD816-01, Network Daily
Report Part 1.K
External Network Fee Detail Report NUDAD816-01 Network Daily
Fraud Reports Fraud by Issuer and S/E Market FSG019 Fraud Reposi- Monthly
tory
Fraud by Issuer and Industry FSG020 Fraud Reposi- Monthly
tory
Fraud by Issuer, S/E Market, and FSG021 Fraud Reposi- Monthly
Fraud Type tory
Issuer Gross Fraud Update FSG002 Fraud Reposi- Monthly
tory
Issuer Fraud Summary FSG003 Fraud Reposi- Monthly
tory
Non-Actioned Rejected Transaction Fraud Reposi- Monthly
Reports tory
Fraud by Acquirer and FSG022 Fraud Reposi- Monthly
Cardmember Market tory
Fraud by Acquirer and Industry FSG023 Fraud Reposi- Monthly
tory
Fraud by Acquirer, Cardmember FSG024 Fraud Reposi- Monthly
Market, and Fraud Type tory
Acquirer S/E Fraud Summary FSG11A Fraud Reposi- Semimonthly
Report tory
Acquirer S/E Fraud Detail Report FSG11B Fraud Reposi- Semimonthly
tory
Top 40 S/Es 6 Month Summary FSG11C Fraud Reposi- Semiannually
Report tory
Top 40 S/Es 6 Month Detail Report FSG11D Fraud Reposi- Semiannually
tory

October 2019 Page 7-3

Section 1 Program Progress Reports

Program Progress Reports

Overview AEGNS Participants must compile and submit reports to:

• Enable AEGNS to fulfill its shareholder and regulatory reporting
obligations
• Enable some commercial terms such as contractual royalties,
commission fees to be calculated and settled

Reporting Activity The Program Progress Reports have 5 components, each of which
displays actual activity for a reporting period. The reports are
specific to Card issuing and Service Establishment (S/E) acquiring
and have these data elements, which are agreed to between the
Participant and the AEGNS Finance Representative:
• Mandatory (M)
• Conditional (C) (dependent on contract)
• Calculated (CAL)

Policy Refer to the Business and Operational Policies manual for the policy
for the Program Progress reports.

Submission More instruction regarding the reporting submission process can be

Process found on [Link]/knowledgebase.

Issuer’s Reports Issuers must supply 3 reports to AEGNS using the web-based
submission tool supplied by AEGNS. All Issuers must supply Card
Statistics by Product, Billings and Fees by Industry and Card
Product, and the Account Balances Outstanding, Write-offs, and
Recoveries reports for POS and ATM Transactions.
If the Participant participates in the Membership Rewards Program,
the Issuer must also submit the Membership Rewards Statistics by
Product report.

continued on next page

Page 7-4 October 2019

Acquirer’s Reports Acquirers must supply two reports to AEGNS using the web-based
submission tool supplied by AEGNS. All Acquirers must supply
Merchant Statistics by Industry and Local and Inbound Discount
Business and Transactions by Industry reports for POS and ATM
Transactions.

Independent Participants who have the issuing and acquiring business must
Operator Reports submit Issuer and Acquirer reports. If the Participant supports a
revolve product, the Issuer must submit account balances
outstanding, write-offs, and recoveries detail by product.
If the Participant participates in the Membership Rewards Program,
the MR Statistics by Product report must also be submitted.

Frequency Participants must, at their own expense, supply these reports on a

monthly basis for all businesses they operate: specifically, all Card
issuing businesses for Issuers and all acquisition of S/Es for
Acquirers.

Report Deadlines These reports must be sent to AEGNS by the 15th of each month.

How to Report AEGNS supplies Participants with the necessary web-based

submission tool and instructions for the submissions of the reports.

Certification No certification is required.

Definitions The reports, usage, and definitions for all reports are in this chapter.
Definitions in a Participant contract with AEGNS takes precedence
over definitions in this document.

October 2019 Page 7-5

Card Statistics by Product

What is Card The Card Statistics shows the issuance of Cards and devices and
Statistics? their status (for example, active and canceled) on the Network.

Report Usage The Issuer Card Statistics by Product reports:

• Total quantity of basic and supplementary Cards issued per
product, organized by issued Card-in-force (CIF) components
• Number of active basic and supplementary Cards in circulation
at the end of the reporting period
• Number of new Cards
• Number of Cards canceled and the cancellation reason
• Number of Cards converted from one Card type to another

Role Type Report Issuer

Product Type All Issuer products

Frequency Monthly

Product Lines Refer to the Business and Operational Policies manual for a listing of
available Card products.

Definitions This table shows the definitions and optionality for terms used in
the Card Statistics by Product report for all Issuers. Definition in the
Issuer’s contract takes precedence over the definitions in this
document.

continued on next page

Page 7-6 October 2019

Table 7-2. Card Statistics by Product

Data Element Name Optionality Definition
Beginning Cards M The total number of basic and supplementary Cards
(separated by product type) in circulation at the start
of the reporting period.
This total must agree with the Ending Cards reported
by product in the previous reporting period.
New Cards Acquired M The number of new basic and supplementary Cards
issued (separated by product type) in the reporting
period (excluding conversions/transfers in).
Transfers In/Out M The total number of basic and supplementary Cards
(transferred from/to the AEGNS portfolio to/from a
non-AEGNS portfolio).
For example, transfer of Visa/MC Cardmembers to an
AEGNS portfolio will be received as a transfer-in under
the product type, with more Ending Cards.
American Express Cards transferred to other
non-American Express products show as a transfer-out
under the product type, decreasing the overall Ending
Cards.
Conversions In/Out M The number of basic and supplementary Cards con-
verted from one American Express product to another
American Express product issued by the Participant.
For example, if the Cardmember replaces a personal
Card with a Gold Card, the personal Card shows in the
Conversion Out section and the Gold Card shows in the
Conversion In section.
(Conversions In) must equal (Conversions Out) prod-
ucts in this reporting period.
Attrition – Voluntary M The total number of basic and supplementary Cards
canceled by Cardmembers.
For example, Cardmember requests cancellation or
refuses to pay the annual fee.
Attrition – Involuntary M The total number of basic and supplementary Cards
canceled by the Issuer.
For example, non-payment of the amounts billed, the
Cardmember is deceased, or all other reasons.
Attrition - Total Cal Auto-filled total number of basic and supplementary
Cards canceled separated by product type.
Calculation = (Attrition - Voluntary) + (Attrition - Invol-
untary)
Ending Cards Cal Auto-filled number of basic and supplementary Cards
(separated by product type) in circulation at the end of
the reporting period.
Calculation = (Beginning Cards) + (New Cards
Acquired) + (Transfers In) - (Transfers Out) + (Conver-
sions In) - (Conversions Out) - (Attrition - Total)

October 2019 Page 7-7

Table 7-2. Card Statistics by Product (continued)

Data Element Name Optionality Definition
Active Cards Over Previous C The year to date number of new Cards acquired that
Month have one or more Transactions (excluding the annual
Card fee) in the last month separated by product type.
Active Cards Over Three C The year to date number of new Cards acquired that
Months have 1 or more Transactions (excluding the annual
Card fee) in the last 3 months separated by product
type.
Active Cards Over 12 C The year to date number of new Cards acquired that
Months have 1 or more Transactions (excluding the annual
Card fee) in the last 12 months separated by product
type.
Inactive Cards Over 12 C The year to date number of new Cards acquired do not
Months have 1 or more Transactions (excluding the annual
Card fee) in the last 12 months separated by product
type.
Cards Reaching Anniversary M The number of Cards that are at their anniversary of
issuance. This does not include attrition.
The anniversary date is the date on which the Card
completes each year of issuance and is not necessarily
the expiry date of the Card.
Card Fees - Annual Card C Number of Cardmembers charged an annual fee
Fee (waived or not waived).
Card Fees - Renewed C The number of Cards that are at their anniversary and
the Cardmember has renewed.
EMV Contact Cards (AEIPS) M The number of Basic and Supplementary Cards in the
Ending Cards total which are enabled for EMV (AEIPS).
Magnetic Stripe Contact- C The number of Basic and Supplementary Cards in the
less Cards (Expresspay) Ending Cards total which are enabled for Magnetic
Stripe Contactless (Expresspay).
EMV Contactless Cards M The number of Basic and Supplementary Cards in the
(AEIPS and Expresspay) Ending Cards total which are enabled for EMV Contact-
less (Expresspay).
Contactless Devices C The number of non-Card devices (FOBs, stickers and
(Expresspay) mobile phones) enabled for Contactless (Expresspay).
Basic Card Definition A Card issued as the primary Card for an Account.
Only
Supplementary Card Definition A Card issued to a Cardmember based on an Account
Only established by another Cardmember, at the request of
the other Cardmember. Supplementary Card can also
be “additional Cardmember.”

Page 7-8 October 2019

Billings and Fees by Industry and Card Product

What is Billing and The POS, ATM, and Cash Disbursement Transactions by the Issuer’s
Fees? Cardmembers and the fees associated with the Card, such as
balance transfers, cash advances, delinquency charges, annual fees
and interest, depending on the Participant’s functionality and
contractual agreement.

Report Usage The Billings and Fees by Industry and Card Product reports:
• Billed volume and number of Transactions of local and other
billed business by Card product
• Total number of local/foreign ATM Transactions
• Total volume of local/foreign non-ATM cash Transactions (in the
local billing currency)

Role Type Issuer

Product Type All Issuer products

Frequency Monthly

Definitions This table gives the definitions and optionality for terms used in
each of the fields of the Billings and Fees by Industry and Card
Product report.

Table 7-3. Billings and Fees by Industry and Card Product: Definitions
Data Element Option-
Definition
Name ality
Point of Sale Volume
Total POS On Us M Total POS Transaction count and amount. The Transaction is con-
sidered On Us when a Participant owns the Cardmember and S/E
relationships and the Transactions are not passed through the
Network.
Total POS AEGN M Total POS Transaction count and amount. The Transaction is local
Local when the Acquirer and Issuer are in the same geographic area.
The total includes all local Participant Cardmember Charges at
Merchants acquired by other Participant Acquirers in the same
geographic area, including spend at American Express Multina-
tional Accounts which may or may not be serviced by the Partici-
pant.

October 2019 Page 7-9

Table 7-3. Billings and Fees by Industry and Card Product: Definitions (continued)
Data Element Option-
Definition
Name ality
Total POS AEGN M Total POS Transaction count and amount submitted to the Network
Foreign from outside of the Issuer's country.
The Transaction is foreign when the Acquirer and Issuer are not in
the same geographic area.
Industry Split C The type of business (for example, goods and services) of the
S/Es covered in the report.
Refer to the Report Category Codes section of the Codes Refer-
ence Guide for valid codes and their descriptions.
Participants must submit data if required by their contract.
Total POS Cal Auto-filled total of the Point of Sale volumes
Calculation = Sum of all POS volumes
ATM Volumes
Total ATM On Us M Total ATM Transaction count and amount started by the Issuer's
Cardmember at Issuer owned ATMs and not passed through the
Network. The total includes the fees and commissions applied by
the Issuer.
Transactions are On Us when a Participant owns the Cardmember
and Acquirer ATM relationships.
Total ATM Local C Total ATM Transaction count and amount at ATMs in the Issuer's
Bilaterals country. These Transactions occur at ATMs where the Issuer and
another entity have an agreement for the ATM Transactions. The
Transactions are not passed through the Network.
Total ATM AEGN M Total ATM Transaction count and amount sent to the Network
Local started by the Issuer's Cardmember at an ATM in the Issuer's
country. The total includes the fees and commissions applied by
the Issuer.
The Transaction is local when the Acquirer and Issuer are in the
same geographic area.
Total ATM AEGN M Total ATM Transaction count and amount submitted to the Network
Foreign started by the Issuer's Cardmember at an ATM not in the Issuer's
country. The total includes the fees and commissions applied by
the Issuer.
The Transaction is foreign when the Acquirer and Issuer are not in
the same geographic area.
Total ATM Cal Auto-filled total of the ATM volumes
Calculation = Sum of the above
ATM Denied Transaction Volume
Total ATM On Us C Total count of On Us ATM Transactions denied. On Us Participants
Denials own the Cardmember and ATM relationships and the Transactions
are not passed through the Network.
Total ATM Local C Total count of ATM Transaction denied at ATMs in the Issuer's
Bilaterals Denials country. These Transactions occur at ATMs where the Issuer and
another entity have an agreement for the ATM Transactions. The
Transactions are not passed through the Network.

Page 7-10 October 2019

Table 7-3. Billings and Fees by Industry and Card Product: Definitions (continued)
Data Element Option-
Definition
Name ality
Total ATM AEGN C Total ATM Transaction count submitted to the Network in the
Local Denials Issuer's country and denied.
The Transaction is local when the Acquirer and Issuer are in the
same geographic area.
Total ATM AEGN C Total ATM Transaction count submitted to the Network outside the
Foreign Denials Issuer's country and denied.
The Transaction is foreign when the Acquirer and Issuer are not in
the same geographic area.
Total ATM Denials Cal Auto-filled total count of ATM denied requests.
Calculation = Sum of the above
Cash Disbursement Transaction Volumes
Total Cash Dis- C Total Cash Disbursement Transaction count and amount (MCC
bursement On Us 6010 only).
On Us Participants own the Cardmember and S/E relationships
and the Transactions are not passed through the Network.
Total Cash Dis- C Total Cash Disbursement Transaction count and amount (MCC
bursement AEGN 6010 only) submitted to the Network in the Issuer's country. The
Local total includes the fees and commissions applied by the Issuer.
The Transaction is local when the Acquirer and Issuer are in the
same geographic area.
Total Cash Dis- C Total Cash Disbursement Transaction count and amount (MCC
bursement AEGN 6010 only) submitted to the Network outside the Issuer's country.
Foreign The total includes the fees and commissions applied by the Issuer.
The Transaction is foreign when the Acquirer and Issuer are not in
the same geographic area.
Total Cash Dis- Cal Auto-filled total of the Cash Disbursement volumes.
bursement Calculation = Sum of the above
Not include in Financial Calculations
Total Reward C Total count and amount of applicable Cardmember Reward
Redemption Trans- Redemption Transactions, if applicable.
actions
Total Promotional C Total count and amount of applicable Cardmember Promotional
Program Transac- Program Transactions, if applicable.
tions
Other C Total count and amount of applicable Cardmember Transaction as
requested by the AEGNS Representative.
Total Excluded from Cal Auto-filled total of the volumes not included in the financial calcu-
Financial Calcula- lations.
tions Calculation = Sum of the above
Fees and Charges
Card Fees
Published Annual C The Card fee amount published in the product terms and condi-
Card Fee tions for Basic and Supplementary Cards.

October 2019 Page 7-11

Table 7-3. Billings and Fees by Industry and Card Product: Definitions (continued)
Data Element Option-
Definition
Name ality
Card Fees Billable M Total count and amount of billable Card fees (rebated or waived)
for Basic and Supplementary Cards.
Fee free promotions are included here.
Card Fee Rebates M Total count and amount of Card fees (rebated or reversed).
Goodwill gesture or fee reimbursement on cancellation is included
for Basic and Supplementary Cards.
Card Fee Waivers M Total count and amount of Card fees waived (not billed) for Basic
and Supplementary Cards.
Promotional waivers are included here.
Total Card Fees Cal Auto-filled total of the Card fee volumes
Billed Calculation = Card Fees Billable - Card Fee Rebates - Card Fee
Waivers
Finance Charges
Gross Interest M Total amount of the interest amount applied / collected from
Income on Revolve accounts with revolving or outstanding balances
Delinquency M Total amount of the finance charges assessed by the Issuer due to
Charges outstanding balances, late payment and other delinquency
charges.
Other Charges M Total amount of other finance charges assessed to the Cardmem-
ber - to be discussed and agreed with your AEGNS Representative
Total Finance Cal Auto-filled total of the Finance charges volumes
Charges Calculation = Sum of the above
Other Fees
FX Commission on M Total foreign exchange commissions on Transactions applied by
AEGN Foreign the Issuer. This includes Foreign Currency Factor.
Transactions
Insurance M Total insurance premiums for insurance billed to the Card on poli-
cies sold by the Issuer.
Loyalty Fees M Total loyalty program fees billed on the Card regardless of the type
of loyalty program.
Other Fees C Other fees not identified above – to be discussed and agreed with
your AEGNS Representative.
Total Other Fees Cal Auto-filled of the other fee volumes
Calculation = Sum of the above
Total Billed Busi- Cal Auto-filled total value of all Transactions presented.
ness Calculation = (Point of sale Volumes) + (ATM Volumes) + (Cash
Disbursement Transaction Volumes) + (Total Card Fees Billed) +
(Finance Charges) + (Other Fees).

Page 7-12 October 2019

Table 7-3. Billings and Fees by Industry and Card Product: Definitions (continued)
Data Element Option-
Definition
Name ality
POS Billing Detail By Industry
Industry Split C Transaction count and amount excluding MCC 6010 Transactions
separated by industry. The totals of the industry split should total
the summarized count and amount above.
Refer to the Report Category Codes section of the Codes Refer-
ence Guide for valid codes and their descriptions.
Participant must submit data if required by their contract.

October 2019 Page 7-13

Account Balances Outstanding, Write-offs, and Recoveries

What is Account The Account Balance Outstanding is the amount owed on a debt as
Balance of a particular date.
Outstanding?

Report Usage The Issuer Account Balances Outstanding, Write-offs, and

Recoveries report is used to report:
• Total balances and average days outstanding
• Average total outstanding balances
• Total payments received
• Losses (credit losses, CM fraud, counterfeit losses, etc.)
• Recoveries

Role Type Issuer

Product Type All Issuer products

Frequency Monthly

Definitions This table gives the definitions and optionality for terms used in each of the
fields of the Account Balances Outstanding, Write-offs, and Recoveries
report.

Table 7-4. Account Balances Outstanding, Write-offs and Recoveries: Definitions

Data Element Option-

Definition
Name ality
Account Balance Summary
Current Credit Out- M The total count and amount of monetary value of current balances
standing Balance by Product Type where no finance or interest charges are
assessed.
Revolving Credit M The total count and amount of monetary value of revolving out-
Outstanding Bal- standing balances by Product Type where finance or interest
ance charges are assessed.
Credit Outstanding Cal Auto-filled total value of outstanding balances
Balance Total Calculation = Sum of the above

Page 7-14 October 2019

Table 7-4. Account Balances Outstanding, Write-offs and Recoveries: Definitions

(continued)
Data Element Option-
Definition
Name ality
Account Balances C Total monetary value of outstanding balances by Product Type for
Detail the specific delinquency time periods:
• Less than 30 days
• Between 30-59 days
• Between 60-89 days
• Between 90-119 days
• Between 120-179 days
• Between 180-269 days
• Between 270-359 days
• More than 360 days
The total balance outstanding is calculated at the end of the Pro-
gram Progress reporting period.
Average Revolved C The calculation total of the Total Revolved Balances Amount
Balance divided by Total Revolved Balances Transaction Count.
Billings Split
AEGNS Percentage C Percentage of billings across product portfolio related to
of Billings non-AEGNS card portfolios. This is when the Cardmember has an
American Express Card and a different Card product with the
Issuer.
Interest Rates
Minimum Interest C The minimum Annual Percentage Rate (APR) of finance charges
Rate Charged to applied to revolving balances.
Cardmember
Maximum Interest C The maximum Annual Percentage Rate (APR) of finance charges
Rate Charged to applied to revolving balances.
Cardmember
Introductory Inter- C The introductory interest rate charged to the Cardmember as part
est Rate Charged of the Issuer’s promotion.
to Cardmembers
Bad Debt Write-offs C Total balance on the accounts written off as bad debt during
reporting period.
Bankruptcy C Total balance on the accounts written off as Cardmember declared
Write-offs bankruptcy.
Credit Losses Total Cal Auto-filled total values of credit losses which include bad debt and
bankruptcy write-offs.
Calculation = (Bad Debt Write-offs) + (Bankruptcy Write-offs)
Cardmember Fraud C The total amount attributable to Cardmember fraud during the
Losses reporting period.
Counterfeit Losses C The total loss amount attributable to counterfeiting during the
reporting period.

October 2019 Page 7-15

Table 7-4. Account Balances Outstanding, Write-offs and Recoveries: Definitions

(continued)
Data Element Option-
Definition
Name ality
Chargeback C The amount of the chargeback write-offs during the reporting
Write-offs period.
Lost Checks C The amount of the lost checks during the reporting period.
Other C The amount of other losses not specifically categorized during the
reporting period.
Other Losses Total Cal Auto-filled total amount of losses which include Chargeback
Write-offs, Lost Checks, and Other during the reporting period.
Calculation = (Chargeback Write-offs) + (Lost Checks) + (Other)
Recoveries C The total amount of recoveries during the reporting period.
Gross Interest M The interest amount applied and collected from accounts with
Income on Revolve revolving or outstanding balances.
Cost of Funds M The cost of funding total receivables.
Net Interest Cal Auto-filled total net interest income
Income Calculation = (Gross Interest Income on Revolve - Cost of Funds)

Page 7-16 October 2019

Membership Rewards Statistics by Product

What is The Membership Rewards (MR) program lets enrolled Cardmembers

Membership earn points that can be redeemed for rewards for travel,
Rewards? entertainment, retail certificates, and merchandise.

Report Usage All Participants licensed to participate in the Membership Rewards

(MR) program must complete and submit the Issuer MR Statistics
by Product report that shows the:
• Total number of CM eligible for MR
• Total number of CM enrolled in MR
• Total billing of MR enrollees
• Average spend enrolled/non enrolled Card
• MR Partners

Role Type Issuer

Product Type All Issuer products with MR program associated with it

Frequency Monthly

Definitions This table gives the definitions and optionality for terms used in
each of the fields of the MR Statistics by Product report.

Table 7-5. Membership Rewards Statistics by Product: Definitions

Data Element Option-
Definition
Name ality
Eligible Cards in Cal Auto-filled total number of Cardmembers eligible for Membership
Force (Basic) Rewards. This is the calculation from the Card Statistics by Prod-
uct report.
Membership C The total number of Cardmembers enrolled in Membership
Rewards Enrollees Rewards.
Non MR Enrollees C The total number of Cardmembers not enrolled in Membership
Rewards.
% of Eligible Cal Auto-filled calculation of (MR Enrollees) / (Non-MR Enrollees).
Enrolled
Count of Attrited C The total number of Membership Rewards enrollee who attrited.
MR Enrollees

October 2019 Page 7-17

Table 7-5. Membership Rewards Statistics by Product: Definitions (continued)

Data Element Option-
Definition
Name ality
Percentage Attri- Cal Auto-filled calculation of (Count of MR Attrited Enrollees) / (MR
tion of Non-MR Enrollees).
Enrollees
Count of Attrited C The total number of Cardmembers eligible for Membership
Non Enrollees Rewards, but are non enrollees and attrite.
Percentage Attri- Cal Auto-filled calculation (Count of Attrited Non Enrollees) / (Non MR
tion of MR Enroll- Enrollees).
ees
Total Eligible MR Cal Auto-filled from the Total Billed Business field of the Billings and
Billings Fees by Industry report.
Total MR Enrollees C The total billing of Membership Rewards enrollees.
Billings
Total Non MR C The total billing of Cardmembers eligible for Membership Rewards
Enrollees Billings but are not enrolled.
Percentage of Bill- Cal Auto-filled calculation of (Total MR Enrollees Billings) / (Total Eligi-
ings From Enrollees ble MR Billings).
Average Spend Per Cal Auto-filled calculation of (Total MR Enrollees Billings) / (MR Enroll-
MR Enrolled Card ees).
Average Spend Per Cal Auto-filled calculation of (Total Non MR Enrollees Billings) / (Non
Non MR Enrolled MR Enrollees).
Card
Number of Points Redeemed
Airline Partners C The total number of points redeemed and items redeemed with
Airline MR Partners.
For example, points redeemed is the number of Membership
Rewards points used for the redemption, whereas items redeemed
is the number of redemptions made which will include a block of
points.
• Transfer 20000 points to airline frequent flyer program
This is reported as one item redeemed and 20000 points
redeemed.
Hotel Partners C The total number of points redeemed and items redeemed with
Hotel MR Partners.
For example, points redeemed is the number of Membership
Rewards points used for the redemption, whereas items redeemed
is the number of redemptions made which will include a block of
points.
• one free night of lodging for 1000 points
This is reported as one item redeemed and 1000 points redeemed.

Page 7-18 October 2019

Table 7-5. Membership Rewards Statistics by Product: Definitions (continued)

Data Element Option-
Definition
Name ality
Retail Partners C The total number of points redeemed and items redeemed with
Retail MR Partners.
For example, points redeemed is the number of Membership
Rewards points used for the redemption, whereas items redeemed
is the number of redemptions made which will include a block of
points.
• one bottle of wine for 1000 points
This is reported as one item redeemed and 1000 points redeemed.
All Other Partners C The total number of points redeemed and items redeemed with all
other MR Partners.
For example, points redeemed is the number of Membership
Rewards points used for the redemption, whereas items redeemed
is the number of redemptions made which will include a block of
points.
• one bottle of wine for 1000 points
• one car rental for 16000 points
• Transfer 20000 points to airline frequent flyer program
This is reported as three items redeemed and37000 points
redeemed.

October 2019 Page 7-19

Merchant Statistics by Industry

What is Merchant Many establishments have more than one location. When a
Statistics by contracted S/E has more than one location, the number of locations
Industry? should be listed to give an accurate count of S/Es accepting the
Card.

Report Usage The Acquirer Service Establishments and Locations in Force by

Industry report is used to report:
• Total number of S/Es and ATMs at the start and end of the
reporting period
• S/Es and ATMs with new contracts signed during the reporting
period
• S/Es and ATMs canceled during the reporting period
• Total number of active S/Es during the reporting period
• Total number of Service Establishment locations contracted to
accept the Card during the reporting period

Role Type Acquirer

Product Type Not applicable

Locations in Force When a contracted S/E has more than one location, the number of
locations should be listed to give an accurate count of S/Es
accepting the Card.

Frequency Monthly

Definitions This table gives the definitions and optionality for terms used in
each of the fields of the Merchant Statistics by Industry report.

Table 7-6. Merchant Statistics by Industry: Definitions

Data Element Option-
Definition
Name ality
Beginning Loca- M The number of Service Establishments locations accepting the
tions in Force Card at the start of the reporting period.
New Locations M The total count of new locations added during the reporting
period. For example, an existing S/E has added new locations to
the existing contract.

Page 7-20 October 2019

Table 7-6. Merchant Statistics by Industry: Definitions (continued)

Data Element Option-
Definition
Name ality
Canceled Locations M The total count of locations canceled during the reporting period.
Ending Locations in Cal Auto-filled with the number of Service Establishments contracted
Force to accept the Card at the end of the reporting period.
Calculation = (Beginning Locations in Force) + (New Locations) -
(Canceled Locations)
Active Locations C The number of locations at which spending was recorded during
the reporting period.
Percentage of Cal Auto-filled with the percentage of S/E locations at which spending
Active Locations was recorded during the reporting period.
Calculation = (Active Locations) / (Ending Locations in Force)
Active Locations in M The number of S/E locations at which spending was recorded
Force in the Last during a rolling 12 month period.
Rolling 12 Months
Percentage of Cal Auto-filled with the percentage of S/E locations at which spending
Active Locations in was recorded during a rolling 12 month period.
Force in the Last Calculation = (Active Locations) / (Ending Locations in Force) for
Rolling 12 Months the reporting period.
Industry C The type of business (e.g., goods and services) of the Card Accep-
tors covered in the report. Refer to the Report Category Codes
section of the Codes Reference Guide for valid codes and their
descriptions. Participant must submit data if required by their con-
tract.
POS Terminal Statistics
Standalone Termi- C The number of POS terminals that contain all of the functionality
nals required for processing a Card-based payment Transaction in the
POS unit (e.g., printer, PIN pad, display, and modem) owned by
the Acquirer.
Integrated Termi- C The number of POS terminals that integrate the functionality
nals required for processing a Card-based payment Transaction with
the functions for an electronic cash register owned by the
Acquirer.
Online Acceptors C The number of online businesses that accept Cards as payment. If
an S/E has a physical and online presence, online presence is
reported separately in this field.
Other C The number of other terminal types or acceptors that are not in
the categories listed above.
Total Terminals Cal Auto-filled with the number of terminals, Online Acceptors and
other.
Calculation = Sum of all terminals and acceptors above.
EMV Level 1 Com- C The number of terminals with Level 1 EMV compliant hardware.
pliant Terminals
EMV Level 2 Com- C The number of terminals with Level 2 EMV compliant software.
pliant Terminals

October 2019 Page 7-21

Table 7-6. Merchant Statistics by Industry: Definitions (continued)

Data Element Option-
Definition
Name ality
EMV Level 2 Active C The number of active terminals with AEIPS software and can sup-
Terminals ply end-to-end EMV Transactions.
Expresspay Certi- C The number of readers/terminals that can start Expresspay con-
fied Readers/Termi- tactless Transactions.
nals
ATM Statistics
Total ATM M The number of ATMs accepting the Card owned or accessible by
the Acquirer.
Total EMV Compli- M The number of ATMs accepting the Card owned or accessible by
ant ATM the Acquirer.

Page 7-22 October 2019

Local and Inbound Discount Business and Transactions by

Industry

What Is Discount The total spend by Cardmembers at an S/E is considered Discount

Business? Business.

Report Usage The Acquirer Local and Inbound Discount Business and Transactions
by Industry report is used to report:
• Total amount of S/E discount business in local currency
• Total amount of charges
• Average Transaction amount
• Average discount rates

Role Type Acquirer

Product Type Not applicable

Frequency Monthly

Definitions This table gives the definitions and optionality for terms used in
each of the fields of the Local and Inbound Discount Business and
Transactions by Industry report.

Table 7-7. Local and Inbound Discount Business and Transactions by Industry:
Definitions
Data Element Option-
Definition
Name ality
POS Volume
Total On Us M Total On Us POS Transaction count and amount excluding MCC
6010 Cash Disbursement Transactions. On Us Participants own the
Cardmember and S/E relationships and the Transactions are not
passed through the Network.
Total On Us Multi- C Total count and amount at S/Es American Express has designated
national Accounts as Multinational Accounts (MNA) (e.g., Giorgio Armani and Gucci)
as designated in the agreement. On Us Participants own the Card-
member and S/E relationships and the Transactions are not
passed through the Network.

October 2019 Page 7-23

Table 7-7. Local and Inbound Discount Business and Transactions by Industry:
Definitions (continued)
Data Element Option-
Definition
Name ality
Total POS AEGN M Total POS Transaction count and amount generated by a Card-
Local member in the Acquirer's country submitted to the Network.
The Transaction is local when the Acquirer and Issuer are in the
same geographic area.
Total AEGN Local C Total Transaction count and amount of volume at S/Es American
Multinational Express has designated as Multinational Accounts (MNA) (e.g.,
Accounts Giorgio Armani and Gucci) in the agreement.
The Transaction is local when the Acquirer and Issuer are in the
same geographic area.
Total POS AEGN M Total Transaction count and amount made at Participant’s S/E's
Inbound POS by a Network Cardmember from outside of the Acquirer’s
country presented by the Network
Total AEGN For- C Total POS Transaction count and amount made at Participant’s
eign Multinational S/E's POS generated by a Network Cardmember from outside of
Accounts the Acquirer’s country presented by the Network at S/Es American
Express has designated as Multi National Accounts (MNA) (e.g.,
Giorgio Armani and Gucci) in the agreement. If the S/E is not a
MNKA, this field is blank.
Total POS Discount Cal Auto-filled value of all POS Discount Business
Business Calculation = Sum of the above
ATM Volume
Total On Us M Total On Us ATM Transaction count and amount. On Us Participants
own the Cardmember and ATM relationships and the Transactions
are not passed through the Network.
Total AEGN Local M Total ATM Transaction count and amount generated by a Card-
member in the Acquirer's country submitted to the Network.
The Transaction is local when the Acquirer and Issuer are in the
same geographic area.
Total AEGN M Total Transaction count and amount at the Acquirer's ATM gener-
Inbound ated by an American Express Cardmember in the Acquirer's coun-
try and presented to the Network.
Inbound is defined as a Cardmember from outside the country is
transacting at a local ATM.
Total ATM Volume Cal Auto-filled value of all ATM volume
Calculation = Sum of the above
Cash Disbursement Business
Total On Us M Total Transaction count and amount of Cash Disbursement vol-
ume. On Us Participants own the Cardmember and S/E relation-
ships and the Transactions are not passed through the Network.
Total AEGN Local M Total Transaction count and amount of Cash Disbursement volume
in the country of the Acquirer and sent to the Network.
The Transaction is local when the Acquirer and Issuer are in the
same geographic area.

Page 7-24 October 2019

Table 7-7. Local and Inbound Discount Business and Transactions by Industry:
Definitions (continued)
Data Element Option-
Definition
Name ality
Total AEGN M Total Transaction count and amount of Cash Disbursement volume
Inbound presented to the Network.
Inbound is defined as a Cardmember from outside the country is
transacting at a local ATM.
Total Cash Dis- Cal Auto-filled value of all Cash Disbursement volume
bursement Volume Calculation = Sum of the above
Not included in Financial Calculations
Total Reward C Total count and amount of applicable Cardmember Reward
Redemption Trans- Redemption Transactions.
actions
Total Promotional C Total count and amount of applicable Cardmember Promotional
Program Transac- Program Transactions.
tions
Other C Total count and amount of applicable Cardmember Transaction as
requested by the AEGNS Representative.
Total Excluded from Cal Auto-filled total of the volumes not included in the financial calcu-
Financial Calcula- lations.
tions Calculation = Sum of the above
POS Billing Detail By Industry
Industry Split C Transaction count and amount excluding MCC 6010 Transactions
separated by industry. The totals of the industry split should total
the summarized count and amount above.
Refer to the Report Category Codes section of the Codes Refer-
ence Guide for valid codes and their descriptions.
Participant must submit data if required by their contract.
Average Merchant Discount Rate by Industry
Industry Split C If Service Establishment discount rate is different for local cards
and inbound cards in your market then supply the two rates.
Refer to the Report Category Codes section of the Codes Refer-
ence Guide for valid codes and their descriptions.
Participant must submit data if required by their contract.

October 2019 Page 7-25

Section 2 Authorization Reports

Authorization Reports

Overview The Transaction Authorization Requests and responses are reported

by the Global Network Services Authorization System (GNSAS) and
distributed to Participants through the Global Online Business
Exchange (GLOBE).

More Instruction Contact your AEGNS Representative for instruction about the
delivery of authorization reports.
Refer to the Authorization Processing chapter in the Network
Specifications - Authorization manual for more instruction.

Page 7-26 October 2019

CAS Activity Summary – Authorizations Activity

Report Usage The CAS Activity Summary – Authorizations Activity report (Report
ID Number BC050AA0) gives totals for Authorization Requests and
approved, denied, and pending Transactions.

Request Resolved The authorizations are resolved with one of these two procedures:
By
• Through an authorization system
• Manually by an authorizer.

Frequency Monthly

Report Contents This report is separated into two parts, “counts,” and “amounts.”
The first two pages of the example report represent the counts
section. The report then uses the same fields for the amounts
section.

Printing The report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the CAS Activity Summary –
Authorizations Activity report are below. These definitions apply to
the “counts” and the “amounts” sections of the report.

Table 7-8. CAS Activity Summary – Authorizations Activity: Definitions

Data Element Name Definition

Total Authorizations The total Authorization Requests. The value is the result of adding AEGN
Systems Resolved count/amount, Authorizer Resolved count/amount,
Issuer Resolved count/amount, and Post Authorizations count/amount,
added together.
Issuer Resolved The number and amount of Authorization Requests switched by AEGNS to
the Issuer or Issuer Authorized Processor.
AEGNS Systems Total Authorization Requests resolved by GNSAS. The number is the result
Resolved of adding GNSAS Resolved and AA Resolved together (for counts and
amounts).
CAS Resolved Authorization Requests resolved by GNSAS, for counts and amounts.
AA Resolved Authorization Requests resolved by GNSAS Authorizer Assist system, for
counts and amounts.
Authorizer Resolved Authorization Requests resolved by an Authorizer, for counts and amounts.

October 2019 Page 7-27

Table 7-8. CAS Activity Summary – Authorizations Activity: Definitions

(continued)
Data Element Name Definition
Post Authorizations Total of all post-authorization advice messages sent after Stand-In. This
field should match the combined total of Systems + Manual counts and/or
amounts listed below.
Systems: Transactions decided by GNSAS remote system during Stand-In.
Manual: Transactions decided by an Authorizer.
Authorizer Resolved Data about Transactions resolved by an authorizer. This detail total should
Detail always match Authorizer Resolved count/amount. The subtotal for each
Authorizer Resolved count/amount combined should match this total. See
the note at the end of this table.1 This field should also match the Autho-
rizer Resolved field count/amount.
Negative A subtotal count/amount that is part of Authorizer Resolved Detail. The
Negative referral reason counts and amounts below should equal this
amount. See the note at the end of this table.1
Lost Transactions that occur after the Cardmember lost possession of the Card.
Inspector Fraudulent activity that occurred on the Card or the Card number since it
was reported lost, stolen, or non-received.
Stolen Transactions that occur with Cards that were reported stolen.
Deceased Transactions that occur with Cards belonging to basic Cardmembers who
were reported deceased.
Bank Suspended Transactions that occur with Cards that the Issuer had suspended.
Non Received Card Transactions that occur with recently-issued Cards that the Cardmember
had reported as not received.
Left Company Transactions that occur with Cards after the Issuer was notified that a
Cardmember no longer worked for the company or had changed positions.
Collection Transactions that occur with Cards after the maximum time period for
delinquency and are canceled by the Issuer.
Gold Card W/ No Line Transactions that occur with a Gold Card with no line of credit associated
Of Cr with it.
Authorizer Status A subtotal count/amount. The Authorizer Status referral reason counts and
amounts listed below should equal this amount. See the note at the end of
this table.1
PIN Warning Possible Transactions that occur with an ATM PIN that is not correct.
Fraud
Known Fraud Warning Transactions that occur with a Card with a history of fraud.
Air Warning Transactions attempted on Cards on which this warning was issued. This
warning stops auto-approvals and shows possible fraudulent activity
and/or derogatory data on the account. Also known as AIRWARN status.
S&T Travelwarn Transactions attempted after a referral was created because of credit prob-
lems on the Cardmember’s Sign and Travel piece of the Card account.
ACTWARN – New And Transactions attempted with Cards in which the Cardmember has not called
Replacement in to activate their new or replacement Card.

Page 7-28 October 2019

Table 7-8. CAS Activity Summary – Authorizations Activity: Definitions

(continued)
Data Element Name Definition
GRCC Generated Air- Global Revolve Credit Card Generated Airwarn. This field is used with nega-
warn tive reasons, which causes the Card to refer/decline.
Ng Check Cash support for no more charges. When the Card account has a check
returned for derogatory reasons, such as insufficient funds, Ng Check dis-
plays as an alternative to AIRWARN. Simultaneous with other No Further
Charges (NFC) cash supports/negatives.
Undeliverable Card Transactions in which the Card was not delivered to the Cardmember (sim-
ilar to non-received).
Cardmember Transactions that occur after the Cardmember requested the Card be can-
Requested Cancel celed.
Returned Mail Transactions in which mail sent to the Cardmember by the Issuer was
returned by the Post Office (usually the billing statement or plastic Card).
Retail Warn Transactions for referrals from retail S/Es. The primary use of this field is
with Corporate Cards. It helps to prevent retail and/or personal charges on
a Corporate Card.
Cardmember’s Transactions in which the Cardmember’s Card was replaced with another
Account Trans Card (e.g., a Personal Card replaced with a Gold Card).
B3 Mega S/E Strategy Transactions in which the Card is identified as a bottom three mega S/E
Card. This is a positive status code.
Cash Warn These S/E types cannot dispense cash, site draft, or Travelers Cheque:
E = check cashing
F = gift checks
G = counter check cashing or cash on the Card
K = cash dispensing
L = Travelers Cheque dispensing
Company Requested The company associated with the Cardmember’s Card requested that the
Cancel Card be canceled.
Restricted Cardmem- The Cardmember’s Card is valid only in some countries/markets.
ber
Credit Balance Referral The Cardmember paid more than the account balance on the Card.
Worldwide Cash Policy A subtotal count/amount that is part of the Authorizer Resolved Detail. The
Worldwide Cash Policy referral reason counts and amounts listed below
should equal this amount. See the note at the end of this table.1
WWCP Not Used Error Transactions in which the Worldwide Cash Policy was not used. Possible
reasons include a retrieval error or S/E exemption from WWCP.
WWCP Trans Not Eligi- Transactions in which an ineligible account was used (e.g., a Corporate
ble Card was attempted for a sight draft).
WWCP Member Not Transactions in which a Cardmember was not eligible for the Transaction
Eligible (e.g., a Corporate Gold Card was attempted for a sight draft).
WWCP Above Policy Transactions that are more than the maximum number of Worldwide Cash
NBR Char Policy Transactions.

October 2019 Page 7-29

Table 7-8. CAS Activity Summary – Authorizations Activity: Definitions

(continued)
Data Element Name Definition
WWCP Above Policy Transactions that are more than the amount limit for Worldwide Cash Pol-
Amount icy.
WWCP Minimum Sight Transactions in which the amount requested was less than the minimum
Draft amount on the WWCP table for sight draft.
WWCP Above Policy Transactions in which the amount is more than a specific combined limit
Amount2 (e.g., the total combined amount of cash dispensing and Travelers Cheque
dispensing).
WWCP Above Policy Transactions in which the amount is more than a specific combined limit
Amount3 (e.g., the total combined amount of cash dispensing, Travelers Cheque dis-
pensing, emergency check cashing, sight draft, and check cashing).
WWCP Draft Amount Transactions in which the amount requested was less than the minimum
Less Min amount on the WWCP table.
Ineligible Sight Draft Transactions in which the Card was not eligible for sight draft Transactions.
CID The Card Identification number. This subtotal count/amount is part of the
Authorizer Resolved Detail. The CID referral reason counts and amounts
listed below should equal this amount. See the note at the end of this
table.1
Invalid CID C Transactions in which the CID/CSC on the magnetic stripe of the Card was
incorrect (e.g., stripe contained alphanumeric data).
Unmatched CID Transactions in which the CID/CSC on the magnetic stripe of the Card did
not match the GNSAS database or the key supplied by the Participant. The
message *UNMCID* can be in conjunction with CIDWARN if the CSC num-
ber on the Card does not match AEGNS records.
First Time Use Transactions that represented the first time use for the Card.
Mail Fraud Transactions in which Cards intercepted in the mail and not received by the
Cardmember were presented.
Missing CID Transactions in which GNSAS does not have a complete record of the CID.
Valid only for Participants with Cards authorized by GNSAS.
Unmatched Dates Transactions in which the Card Expiration Date read on the magnetic stripe
of the Card does not match the Issuer’s Card Expiration Date on the
GNSAS Database. Valid only for Participants with Cards authorized by
GNSAS.
Expired Card DB Transactions in which the Card presented had expired.
Magstripe Data Error Transactions in which the Card magnetic stripe was not correct.
ACTWARN Renewal Transactions in which the Cardmember had not called to activate the
renewal Card before using the Card.
Stripe Expired Card Transactions in which the Card Expiration Date on the magnetic stripe on
the back of the Card had passed.
GRCC Global Revolve Credit Card. This subtotal count/amount is part of Autho-
rizer Resolved Detail. The GRCC referral reason counts and amounts listed
below should equal this amount. See the note at the end of this table.1

Page 7-30 October 2019

Table 7-8. CAS Activity Summary – Authorizations Activity: Definitions

(continued)
Data Element Name Definition
No GRCC Line Of Transactions for GRCC Cards with no associated line of credit.
Credit
RCP Negative Transactions for GRCC Cards with a negative indicator.
RCP 60 Day Delin- Transactions for GRCC accounts 60 days past due.
quent
Master GRCC No Card Transactions for the basic GRCC accounts with no associated Cards.
GRCC Max Cash Transactions for GRCC Cards that are at the maximum cash limit.
GRCC No Check Cash GRCC Cards that are not eligible for check cashing Transactions.
Global Limits A subtotal count/amount that is part of Authorizer Resolved Detail. The
Global Limit referral reason counts and amounts listed below should equal
this amount. See the note at the end of this table.1
G/L Over S/E Limit Transactions that are more than the Global Limits amount for this type of
S/E.
G/L Over Monthly Limit Transactions that are more than the Global Limits monthly limit.
G/L Over Daily Limit Transactions that are more than the Global Limits daily limit.
G/L ATM Monthly Transactions that are more than the Global Limits monthly ATM limit.
G/L Restricted S/E Transactions attempted at S/Es that are not on the Preferred Supplier List
(e.g., Corporate Purchasing accounts).
G/L ATM Minimum Transactions with amounts that are less than the minimum Global Limits
ATM amount.
Global Limit-Credit Transactions for Accounts with a credit balance because the Global Limits
Balance account balance due was overpaid.
Global Limit-Past Due Transactions for Accounts with a Global Limit with a past due balance.
G/L Exceed Group Transactions with an amount that is more than a specific combined Global
Limit Limits amount (e.g., the combined total of cash dispensing, TC dispensing,
emergency check cashing, sight draft, and check cashing).
CRIT Tables Criteria Tables. This subtotal count/amount is part of Authorizer Resolved
Detail. The CRIT table referral reason counts and amounts listed below
should equal this amount. See the note at the end of this table.1
Delinquent Transactions for accounts with a delinquent status.
Accum Transactions with amounts that are more than the permitted maximum.
Accum All Charges Transactions with amounts that are more than the permitted maximum for
all types of charges.
Governor $Amount Transactions that are more than the permitted maximum for a Card.
Accum Max $Charges Transactions that are more than the permitted maximum dollar amount.
Accum Test 1 Transactions that are more than the limits set for the Accum 1 Crit value
test.
Other Transactions categorized as exceptions for other reasons.
Canceled S/E Transactions that originated from a canceled S/E.
Deactivated Card Transactions in which a Cardmember’s Card was deactivated.

October 2019 Page 7-31

Table 7-8. CAS Activity Summary – Authorizations Activity: Definitions

(continued)
Data Element Name Definition
Restricted Cardmem- Transactions in which the Cardmember can only use the Card in specific
ber countries or markets.
Par Init Transactions in which an override occurs on the account (e.g., the account
can be approved for charges up to some amount).
ARM Relayer Transactions which were processed by GNSAS Authorization System risk
system. The Transactions were referred from the CAS queue or were forced
referrals.
Invalid Date Transactions in which the GNSAS risk system encountered an invalid date.
Test Account Transactions for Card accounts defined as a test Card.
CPC CM Restricted S/E Transactions in which the Cardmember’s Purchasing Card is valid only at
specific S/Es.
Business Travel Acct Transactions in which the Cardmember’s Card has a negative restriction for
Negat business travel.
1. The fields that refer to this should match the combined total of all the fields grouped below it. The actual
fields listed in each group can change from report to report, depending on the activity for the current
reporting period.
Each field, with the total fields, has counts that show the number of requests, the number of approved
Transactions, the number of declined Transactions, and the number of referred Transactions. There is
also a percentage column for each of the counts displayed.
The Total Authorization field should equal a combined total of AEGNS Systems Resolved + Authorizer
Resolved + Post Authorizations + Issuer Resolved.

Page 7-32 October 2019

CAS Activity Summary by Point of Sale

Report Usage The CAS Activity Summary – Summary by Point of Sale report
(Report ID Number BC056AA0) gives a list of the locations where
Cards were accepted during the last month. For each location, the
report gives the number and dollar amount for each approved,
declined, and referred Transaction.

Frequency Monthly

Printing This report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the CAS Activity Summary –
Summary by Point of Sale report are below.

Table 7-9. CAS Activity Summary by Point of Sale: Definitions

Data Element Name Definition
Network ID The Network ID is the Participant’s name.
Point of Sale Sources The origin of each Point of Sale Transaction.
Requests The total number of Transactions from each Point of Sale source.1
% of Total The percentage of requests from each Point of Sale source, based on
the total amount of requests.1
Approved The total of approved Transactions.1
Number: number of approved Transactions.
Dollars: U.S. Dollar amount of approved Transactions.
Declined The total of declined Transactions.1
Number: number of declined Transactions.
Dollars: U.S. Dollar amount of declined Transactions.
Number Pending Total number of pending Transactions (counts only).1
Referrals Total number and percentage of referred Transactions.1
Number: number of referred Transactions.
Dollars: U.S. dollar value of referred Transactions.
%: percentage of referred Transactions.
Superphone Transactions originating from a phone/authorizer/ relayer.1
POS Terminals Point of Sale Terminal: Transactions originating from a source that has a
POS device.1
Airline Links Transactions originating from an airline.1

October 2019 Page 7-33

Table 7-9. CAS Activity Summary by Point of Sale: Definitions (continued)

Data Element Name Definition
Department Store Links Transactions originating from a source that is defined as a department
store.1
3rd Party Links Transactions originating from a source with a primary Authorized Pro-
cessor that is not GNSAS. The source has a direct line to GNSAS to
route Transactions.1
Other S/E Links Transactions originating from a source that is defined as a leased line
type of access.
Dial Batch Auth Transactions originating from a source that has a dial terminal. Transac-
tions are bundled up and sent in a batch.1
Total The total number of Transactions and activity for those Transactions for
all Point of Sale sources.
1. These categories contain breakouts for each source origination (source center) of Transactions. Source
centers are on the report only when there have been Transactions.
The total numbers for the approved, declined, and pending Transactions are equal to the total requests
count for each source center. The referral counts are not included in the request counts.

Page 7-34 October 2019

CAS Activity Summary by S/E Type

Report Usage The CAS Activity Summary – Summary by S/E Type report (Report
ID Number BC057AA0) gives data regarding the various industries
in which Cardmembers used their Cards. This report is categorized
by the type of industry and displays the number of Transactions and
the related dollar value for those Transactions.

Frequency Monthly

Printing The report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the CAS Activity Summary –
Summary by S/E Type report are below.

Table 7-10. CAS Activity Summary by S/E Type: Definitions

Data Element Name Definition
Industry Type The type of business of the Card Acceptors covered in the report.
Refer to the Merchant Category Codes section of the Codes Reference
Guide for more instruction.
Requests Total number of Transactions the Industry Type count represents.
% of POS Percentage of the total Transactions the count represents.
Approved Total approved Transactions, divided into numbers and dollars.
Number: Total number of approved Transactions.
Dollars: Total U.S. Dollar amount of approved Transactions.
Declined Total declined Transactions, divided into numbers and dollars.
Number: Total number of declined Transactions.
Dollars: Total U.S. Dollar amount of declined Transactions.
Number Pending Total number of pending Transactions (counts only).
Referrals Total number and percentage of referred Transactions.
Number: Total number of referred Transactions.
%: Percentage of referred Transactions.
Shops Counts for the total number of Transactions/requests at retail S/Es.1
Hotels/Motels Counts for the total number of Transactions/requests at lodging S/Es.1
Restaurants Counts for the total number of Transactions/requests at restaurant-type
S/Es.1
Travel Counts for the total number of Transactions/requests at travel S/Es (e.g.,
airlines).1

October 2019 Page 7-35

Table 7-10. CAS Activity Summary by S/E Type: Definitions (continued)

Data Element Name Definition
Department Stores Counts for the total number of Transactions/requests at department
stores.1
Car Rentals Counts for the total number of Transactions/requests at car rental-type
S/Es.1
Mail Order Counts for the total number of Transactions/requests for mail and phone
orders.1
Check Cashing Counts for the total number of Transactions/requests for S/Es that supply
check cashing functions.1
Sight Drafts Counts for the total number of Transactions/requests for S/Es that supply
sight draft functions. See the note at the end of this table.
T/C Dispensing Counts for the total number of Transactions/requests for Travelers Cheque
dispensing.1
Oil Companies Counts for the total number of Transactions/requests at petrol S/Es.1
Cash Dispensing Counts for the total number of Transactions/requests for Transactions at
ATM machines.1
Bank Check Cashing Counts for the total number of Transactions/requests for check cashing
Transactions at banking institutions.1
Others Counts for the total number of Transactions/requests that are not in one of
the categories listed above.1
S/E Type E Counts for the total number of Emergency Check Cashing Transactions.
S/E Type G Counts for the total number of Check Cashing/Cash on the Card.
Counter Checks Counts for the total number of Counter Checks.
Emergency Checks Counts for the total number of Emergency Checks.
Cash on the Card Counts for the total number of Cash on the Card.
Optima Money Gram Counts for the total number of Optima (GRCC) Money Gram.
Inv. Service Code Counts for the total number of Inv. Service Code.
1. There are also percentages for the number of requests and referrals. There are amounts for approved
and declined counts. The approved, declined and pended Transaction counts equal the request count.
The referral count is not included in the request count.

Page 7-36 October 2019

CAS Activity Summary – Entry Activity

Report Usage The CAS Activity Summary – Entry Activity report (Report ID
Number BC055AA0) contains data about updates to GNSAS for
Issuers’ Cardmember accounts.

Frequency Monthly

Printing This report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the CAS Activity Summary –
Entry Activity report are below.

Table 7-11. CAS Activity Summary – Entry Activity: Definitions

Data Element Name Definition
Number of Entries The total number of entries in each category.
Percent of Entries The percentage of the total number of entries.
Percent in Category The percentage of entries in each category.
Total System Entries Total count of system entries (e.g., negative, status updates).
Total Credit Request Total number of credit/Authorization Request entries.
Entries
Total Downtime Entries Total count of downtime entries.
Total Credit Reversal Total count of credit reversal entries.
Entries
Total Negative Add Total number of negative add entries. Online updates only; no batch
Entries updates are on this report.
Purchase Card Updates to Corporate Purchasing Cards.
Promotional/ Altered/ Updates to advertising Card numbers or test account numbers.
Invalid Acct Num On Bul-
letin
Inspector Updates to Cards with fraudulent activity on the Card or Card number
after the Card is reported lost, stolen or non-received. No charges will be
approved for this Card, regardless of overrides (e.g., preferred Cardmem-
ber).
CIDALRT Updates for Cards with missing, unmatched, or invalid Card Identification
(CSC).
Stolen Updates for Cards reported stolen. There will be no approvals on this
Card.
Lost Updates for Cards reported lost and out of the Cardmember’s possession.
There will be no approvals on these Cards.

October 2019 Page 7-37

Table 7-11. CAS Activity Summary – Entry Activity: Definitions (continued)

Data Element Name Definition
Non-Received Card Updates from Cards reported not received. There will be no approvals on
these Cards.
Deceased Updates for deceased basic Cardmembers.
Collection Updates in which the Card has passed the maximum time period for delin-
quency and was canceled by the Issuer.
Counterfeit Updates in which the Card is thought to be fraudulent.
Left Company Updates in which notification was received that the Cardmember no lon-
ger works for the company.
CANC 93 Updates for U.S. Government Card products that were canceled. This is a
negative referral.
Bank Suspended Updates for bank suspended accounts (not the 91 bank negative).
Gold Card W/No Line of Updates for Gold Cards with no associated line of credit.
Credit
Total Authorizer Add Total count of the number of authorizer status Transactions added by
Entries authorizers.
Credit Balance Referral Updates for Cardmember paid more than the account balance on the
Card.
Chipcard Updates for Cards containing a chip.
Cardmember Requested Updates for Cards canceled at Cardmember request.
Cancel
Company Requested Updates for Cards canceled at the company’s request.
Cancel
Company Requested Updates for Cards where the company has requested the charging privi-
Suspend leges to be suspended.
Cardmember’s Account Updates for Cards replaced with another Card (e.g., a Personal Card
Transferred replaced with a Gold Card).
Restricted Cardmember Updates for Cards valid only in some countries/markets.
Cash Warn These S/E types cannot make updates for dispensed cash, site draft or
Travelers Cheque:
E = Check Cashing
F = Gift Checks
G = Counter Check Cashing or Cash on the Card
K = Cash Dispensing
L = Travelers Cheque Dispensing
MAN4DBC - Add Manual Updates by an authorizer to add a record to supply the Network with the
Path correct 4DBC value for a Card (used for Insourced Cards only).
MAN4DBC - Add Swipe Updates to add a record to supply the Network with the correct 4DBC
4DBC Path value for a Card (used for Insourced cards only).
Plastic Auth Swipe With Updates where the Card was swiped and the 4DBC was manually typed.
4DBC
Optima Cash Susp Updates to suspend Optima (GRCC) Card cash functionality privileges.

Page 7-38 October 2019

Table 7-11. CAS Activity Summary – Entry Activity: Definitions (continued)

Data Element Name Definition
S&T Travelwarn Updates in which a referral was created because of credit problems on the
Cardmember’s Sign and Travel piece of the Card account.
Known Fraud Updates for Cards with a history of fraud.
Miscellaneous Updates for risk reasons that are not defined categories for this report
I3 Mega S/E Strategy Updates for Cards identified as a bottom 3% mega S/E Card for Interna-
tional. This is a positive status code.
Undelivered Card Updates for Cards not delivered to the Cardmember (similar to
non-received).
Remote Negative Updates for negatives applied by the Distributed CAS Platform (DCP).
Inhibit Travelers Cheque Updates to prevent automatic dispensing of Travelers Cheques from an
American Express dispenser.
Inhibit Cash Dispensing Updates to prevent automatic dispensing of cash from American Express
dispensers.
ATMWARN Updates for ATM referral reasons.
Retail Warn Updates for Transactions referred from retail S/Es. This warning helps to
prevent retail and/or personal charging on a Corporate Card.
Firstwarn Updates for first time use of the Card.
Mailwarn Updates for Cards intercepted in the mail.
Optima Generated Air- Updates for Global Revolve Credit Card with negative reasons causing
warn referrals or declines.
Rev I – Card Level Updates at the Card level for preferred Cardmembers.
Deaf Cardmember Updates for deaf Cardmembers.
Quadriplegic Cardmem- Updates for quadriplegic Cardmembers.
ber
Blind Cardmember Updates for blind Cardmembers.
Membership Miles Updates for Cards enrolled in membership miles.
Purchase Card Override Updates for Purchasing Cards with an override that lets it be approved up
to a specified amount.
Purchase Card Mid Mkt Updates for Purchasing Cards that falls into a range defined as mid-mar-
ket level.
Franchise Bank Card Authorizer declined Authorization Request for a GNS Card with the code
Decline 91 franchise bank negative
Check Warning - Optima Update for returned check for Optima (GRCC) Card.
Checkbook
Express Pay Inactive Card is not eligible for Express Pay Services.
Others Updates for all statuses not listed above.
Total Account Status Add The combined total number of all status counts.
Entries
Rev I – Account Level Updates for Rev I status added at the account level.

October 2019 Page 7-39

Table 7-11. CAS Activity Summary – Entry Activity: Definitions (continued)

Data Element Name Definition
Business Travel Account Updates for Business Travel Account Card identification added at the
Level account level.
Total Account Status Total number of account status (8001) Transactions.
Lookups
Total Support Data Add Total number of support add Transactions.
Entries
Authorizer Name & ID Total number of log ins for Authorizers. This data shows who added the
support on an account.
System Decline NFC No updates for more charges for Card accounts.
Card Picked Up At Updates for S/Es requesting that the Card be picked up.
Request Of S/E
NFC Until Returned No more charges until a returned payment becomes good (e.g., a direct
debit or an ATM draft was returned for insufficient funds).
NFC Free Form No more charges. AIRWARN does not need to be associated with this
code.
NFC Please Refer CM To No more charges. Cardmember should contact Credit Department.
Credit Dept
NFC Until Ng Check Paid No more charges until returned check is paid.
NFC Until Payment No more charges until a payment is received.
Received
NFC Until Balance Paid In No more charges until balance is paid in full.
Full
NFC Until Card Product No more charges until the Card product balance is current.
Current
NFC Until S&T Current No more charges for Sign and Travel until Sign and Travel is current.
NFC Until Returned No more direct debit charges, until a direct debit payment that was
Direct Debit Paid returned has been paid.
Pick Up Card For Reeval- Updates for Cards that should be picked up for reevaluation to find out if
uation they should be returned to Cardmembers.
Deny Charge If CAS Updates for decline Transactions if Credit Authorizations System (CAS)
Exposure Exceeds exposure is more than a specified amount.
NFC Until Phone Num- No more charges until phone numbers are obtained from the Cardmem-
bers Are Obtained ber.
NFC Until Cross Refer- No more charges until the cross-reference number for this account is cur-
ence # Is Current rent.
NFC Until Paid To XXX No more authorizations on the Card until the account is paid for a specific
Days number of days.
NFC Under CRAT Review No more charges allowed. Card is under review of credit authorizations.
NFC Until Under Optima Updates to disallow charges until the over-the-limit Optima Card balance
Line Of Credit is below the limit.
Cardmember Payment Updates in which Cardmember payment data is available to the autho-
Information rizer. This is a positive status.

Page 7-40 October 2019

Table 7-11. CAS Activity Summary – Entry Activity: Definitions (continued)

Data Element Name Definition
Cardmember Banking Updates in which Cardmember banking data is available to the authorizer.
Information This is a positive status.
Unauthorized Use By Updates for Cards used without approval.
Monitor For Possible Fac- Updates for Cardmembers believed to be factoring. A record of charge
toring (ROC) is put through, but the Cardmember receives cash as an alterna-
tive to merchandise.
NFC Basic Rescinds Lia- Updates to disallow charges. The Basic Card rescinds the liability.
bility
NFC Possible Counterfeit Update to stop more charges for a Card that is thought to be fraudulent.
Card
Possible Fraud Plus Free Updates to free form field. Authorizers can add text that is pertinent to
Form Text the suspected fraud for a Card.
NFC Canceled By No more charges allowed. Card is canceled.
NFC Establish Positive No more charges allowed, unless positive identification has been estab-
Identification lished.
No Phone/Mail Order Per Updates to disallow charges for Transactions without a Card present due
CM-IPC In Pr to issues with plastic Cards. The Cardmember reports that the Card is
used without their approval.
NFC Until Positive Updates to disallow charges without establishing positive identification.
ID-Fraud Suspected This Card has suspected fraud.
Unformatted Support Updates to free form field. Authorizers can add text that is pertinent to
the account. This is a positive status.
OK To Authorize Normal Updates for Cards that can be authorized for normal charges.
Charges
One Time Charge Sup- Updates for Cards authorized for a one-time charge of a specified amount.
port Authorized
One Emergency Cash Updates for Cards authorized for a one-time cash dispensing Transaction
Disp Authorized for a specified amount.
Unidentified Updates for unidentified status reasons that are not in the statuses above.
Total Delete Entries Total count of deleted online entries.
Negative Count of negative deletes.
Authorizer Status Count of status updates deleted by authorizers.
Account Status Count of status updates deleted by authorizers, at the account level.
Support Count of Transactions where an authorizer deleted a support on a Card.
Others Count for other delete Transactions, which were not in one of the defined
deletion types
Total Referrals Received Total number of referral Transactions.
Interactive Referrals Updates for referral Transactions from the queue, forced-referral, or credit
request. These Transactions start with post-authorization advices. The
negative reason code is greater than zero.

October 2019 Page 7-41

Table 7-11. CAS Activity Summary – Entry Activity: Definitions (continued)

Data Element Name Definition
Condensed Referrals Updates for referral Transactions from the queue, forced referral, or credit
requests. These Transactions are started by an authorizer or GNSAS, have
a valid approve or deny code, and the negative reason code is greater
than zero.
System Pending Count of Transactions referred by GNSAS.
Post Authorization Number of post-authorization advice Transactions.
Advices

Page 7-42 October 2019

Authorization Transaction Edit Error Detail

Report Usage The Authorization Transaction Edit Error Detail report (Report ID
Number BC043AA0) lists Transactions and the reasons for
authorization denials or errors detected when the Issuer responded
with an edit error reason code. This report is sorted by the Card
number, S/E number, and MST Time In (i.e., the time the
Authorization Request was received by GNSAS).

Frequency Daily

Printing This report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the Authorization Transaction

Edit Error Detail report are below.

Table 7-12. Authorization Transaction Edit Error Detail: Definitions

Data Element Name Definitions
Cardmember Number The Cardmember’s valid American Express Card number.
S/E Number The Service Establishment (S/E) number for the Transaction originating
from an S/E location.
MST Time In The Mountain Standard Time (Mountain Standard Time (MST)) GNSAS
received the Transaction/request.
MST Time Out The Mountain Standard Time (Mountain Standard Time (MST)) GNSAS
responded to the Transaction/request.
USD Dollar Amount United States Dollar Amount: the amount requested (expressed in U.S.
Dollars).
Original Transaction The first Transaction amount in the currency used by the S/E.
Amount
Orig Curr Original Currency: the currency type that was used to display the Original
Transaction Amount.
Action Code The type of action taken for the Authorization Request. Each code is fol-
lowed by a description of that code in the Action Code Description field.
Action Code Description A description of the code used to show the type of action of the Transac-
tions.
Approval Code The approval code given by GNSAS or by the primary Authorized Proces-
sor. This field is blank for this report because it supplies data for errors
only.
Input Mode The mode of input for the Transaction: swiped, non swiped or voice. This
field is blank for 8001 TRANS and non-credit request Transactions.

October 2019 Page 7-43

Table 7-12. Authorization Transaction Edit Error Detail: Definitions (continued)

Data Element Name Definitions
BIN Bank Identification Number; in this report, a five-digit prefix of the num-
ber identifying the Issuer Institution. Also used as the first five digits of a
Card Account number, issued by the Issuer.
Total Number Caslog The total number of Transactions/requests reported for that BIN.
Records
For Total $ Total dollar amount of all Transactions/requests reported in U.S. Dollars
for the BIN.
Grand Total Number The grand total of all Transactions/requests reported for the Issuer.
CASLOG Records
For Total $ The grand total dollar amount of all Transaction/requests reported in U.S.
Dollars for the Issuer.

Page 7-44 October 2019

Unacknowledged Voids, Refunds, and Reversals Report

Report Usage The Unacknowledged Voids, Refunds, and Reversals Report (Report
ID Number BC045AA0) lists data for unacknowledged Transactions
if the Network does not receive a correct response after the third
delivery attempt. This report is sorted by the Card number, S/E
number, and MST Time In (i.e., the time the Authorization Request
was received by GNSAS).

More Instruction The Unacknowledged Voids, Refunds, and Reversals Report was
created to accompany the Online Processing of Voids, Refunds, and
Reversals feature. Refer to the Authorization Processing chapter in
the Network Specifications - Authorization manual for instructions.

Frequency Daily

Printing This report is designed to be printed in landscape orientation.

Definitions Definitions for each of the fields on the Unacknowledged Voids,

Refunds, and Reversals Report are below.

Table 7-13. Unacknowledged Voids, Refunds, and Reversals Report: Definitions

Data Element Name Definitions
Run Date The date the report was created.
For “Participant's Displays the Participant's name.
Name”
For Process Date The date the Transaction/request came to GNSAS.
Cardmember Number The Cardmember’s valid American Express Card number.
S/E Number The Service Establishment (S/E) number for the Transaction originating
from an S/E location.
MST Time In The Mountain Standard Time (Mountain Standard Time (MST)) GNSAS
received the Transaction/request.
MST Time Out The Mountain Standard Time (Mountain Standard Time (MST)) GNSAS
responded to the Transaction/request.
USD Dollar Amount United States Dollar Amount: the amount requested (expressed in U.S.
Dollars).
Original Transaction The first Transaction amount in the currency used by the S/E.
Amount
Orig Curr Original Currency: the currency type that was used to display the Original
Transaction Amount.
Action Code The type of action taken for the Authorization Request.

October 2019 Page 7-45

Table 7-13. Unacknowledged Voids, Refunds, and Reversals Report: Definitions

Data Element Name Definitions
Approval Code The approval code given by GNSAS or by the primary Authorized Proces-
sor.
Input Mode The mode of input for the Transaction: swiped, non swiped or voice.
BIN Bank Identification Number; in this report, a five-digit prefix of the num-
ber identifying the Issuer Institution. Also used as the first five digits of a
Card Account number, issued by the Issuer.
Total Number Records The total number of Transactions/requests reported for that BIN.

Page 7-46 October 2019

Authorization Transaction Stand-In Detail

Report Usage The Authorization Transaction Stand-In Detail report (Report ID

Number BC040AA0) lists Transaction data for authorizations made
when the Network authorizes charges for a Issuer’s Cardmembers
during Stand-In. This report is sorted by the Participant’s BIN
range, S/E number, and MST Time In (i.e., the time the
Authorization Request was received by GNSAS).

Frequency Daily

Printing This report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the Authorization Transaction

Stand-In Detail report are below.

Table 7-14. Authorization Transaction Stand-In Detail: Definitions

Data Element Name Definition
Run Date The date the report was created.
For “Participant's Displays the Participant's name.
Name”
For Process Date The date the Transaction/request came to GNSAS.
Cardmember Number The Cardmember’s valid American Express Card number.
S/E Number The identifying number assigned to Service Establishments. This value is
listed for all Transactions originating from an S/E location. Only the Card-
member number, Transaction code and Transaction times are displayed.
For example:
• 8001 TRANS = Account status lookup.
• 75 TRANS = Used to apply the ‘91’ reason code. Participants using
GNSAS to decision Transactions can also apply other statuses.
• 77 TRANS = Account negative update.
MST Time In The Mountain Standard Time (Mountain Standard Time (MST)) GNSAS
received the Transaction/request.
MST Time Out Mountain Standard Time (Mountain Standard Time (MST)) the Network
responded to the Transaction/request.
USD Dollar Amount Amount requested in U.S. Dollars only.
Original Transaction The first Transaction amount in the currency used by the S/E.
Amount
Orig Curr The currency type that was used to display the Original Transaction
Amount.

October 2019 Page 7-47

Table 7-14. Authorization Transaction Stand-In Detail: Definitions (continued)

Data Element Name Definition
Action Code The type of action taken for the Authorization Request. Refer to the Action
Codes section of the Codes Reference Guide for valid codes and their
descriptions.
Approval Code The approval code given by the Network. If the S/E can receive six digit
approval codes, this field shows six digits, if not, it shows two digits. For
declined, pended, 8001 TRANS, and non-credit request Transactions, this
field is blank.
Resolution Transaction resolution:
• Approved
• Declined
• Pended
• Reversal
• AAV Appr
• AAV Decl
• AAV Pend
• AAV Only
• Regsw Appr
• Regsw Decl
• Regsw Pend
• Regsw
• PIN Appr
• PIN Decl
• PIN Pend
This field applies only to credit requests. For account status
updates (e.g., negative, VIP, etc.), the field is blank.
Input Mode The mode of input for the Transaction: swiped, non swiped or voice. This
field is blank for 8001 TRANS and non-credit request Transactions.
BIN Bank Identification Number; in this report, a five-digit prefix of the num-
ber identifying the Issuer Institution. Also used as the first five digits of a
Card Account number, issued by the Issuer.
Total Number CASLOG Total number of Transactions/requests reported for a BIN.
Records
For Total $ Total dollar amount of all Transactions/requests reported in U.S. Dollars
for that BIN.
Grand Total Number Grand total of all Transactions/requests reported for the Participant.
CASLOG Records
For Total $ Grand total dollar amount of all Transaction/requests reported in U.S. Dol-
lars for the Participant.

Page 7-48 October 2019

Authorization Deferred Payment Plan (DPP) Transaction

Detail Report

Report Usage The Authorization Deferred Payment Plan (DPP) Transaction Detail
Report (Report ID BC044AA0) lists DPP requests decisioned by the
Issuer or the Network. This report is appended to the file containing
the Daily Authorization Report and sorted by the Participant’s BIN
range, S/E number, and MST Time In (i.e., the time the
Authorization Request was received by GNSAS).

Frequency Daily

Printing This report is designed to be printed in a landscape orientation.

Definitions This table gives the definitions for terms used in each of the fields of
the Authorization DPP Transaction Detail Report.

Table 7-15. Authorization Deferred Payment Plan (DPP) Transaction Detail Report:
Definitions
Data Element Name Definition
Run Date The date the report was created.
For “Participant’s Displays the Participant’s name
Name”
For Process Date The date the Transaction/request came to GNSAS.
Cardmember Number The Cardmember’s valid American Express Card number.
S/E Number The Service Establishment number for Transactions originating from an
S/E location.
MST Time In The Mountain Standard Time (Mountain Standard Time (MST)) GNSAS
received the Transaction/request.
MST Time Out The time the Network responded to the Transaction/request in Mountain
Standard Time (Mountain Standard Time (MST)).
USD Dollar Amount Amount requested in U.S. Dollars only
Original Transaction The first Transaction amount in the currency used by the S/E.
Amount
Orig Curr The currency type that was used to display the Original Transaction
Amount.
Plan Type Type of DPP plan:
03 = Acquirer-based
05 = Issuer-based
Number Install The number of installments for the Transaction

October 2019 Page 7-49

Table 7-15. Authorization Deferred Payment Plan (DPP) Transaction Detail Report:
Definitions (continued)
Data Element Name Definition
Approval Code The Approval Code given by the Network or by the primary Authorized
Processor. If the S/E can receive six-digit Approval Codes, this field shows
six digits, if not, it shows two digits.
Resolution Shows if the Transaction was approved, declined or pended. This field
applies only to credit requests.
Auth By Source of decision (Issuer or the Network)
Input Mode The mode of input for the Transaction: swiped, non swiped or voice. This
field is blank for 8001 TRANS and non-credit request Transactions.
BIN Bank Identification Number; in this report, a five-digit prefix of the num-
ber identifying the Issuer Institution. Also used as the first five digits of a
Card Account number, issued by the Issuer.
Total Number CASLOG Total number of Transactions/requests reported for this BIN.
Records
For Total $ Total dollar amount of all Transactions/requests reported in U.S. Dollars
for this BIN.
Total Number Reversal Total number of reversal Transactions/requests reported for this BIN.
Records
For Total $ Total dollar amount of all reversal Transactions/requests reported in U.S.
Dollars for this BIN.
Grand Total Number Grand total of all Transactions/requests reported for the Participant for all
CASLOG Records BINs.
For Total $ Grand total dollar amount of all Transaction/requests reported in U.S. Dol-
lars for the Participant for all BINs.
Grand Total Number Grand total of all reversal Transactions or requests reported for the Partic-
Reversal Records ipant.
For Total $ Grand total dollar amount of all reversal Transactions or requests reported
in U.S. Dollars for the Participant.

Page 7-50 October 2019

Authorization Transaction Detail

Report Usage The Authorization Transaction Detail report (Report ID Number

BC041AA0) lists Transaction data for an Issuer’s Cardmember
authorization activity and is supplied to the Issuer or routed to a
Network Issuer’s Authorized Processor to show non-edit error
Transactions and/or requests processed by the Network. This report
is sorted by the Participant’s BIN range, S/E number, and MST Time
In (i.e., the time the Authorization Request was received by
GNSAS).

Frequency Daily

Printing This report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the Authorization Transaction

Detail report are below.

Table 7-16. Authorization Transaction Detail: Definitions

Data Element Name Definition
Run Date The date the report was created.
For “Participant’s Displays the Participant’s name.
Name”
For Process Date The date the Transaction/request came to GNSAS.
Cardmember Number The Cardmember’s valid American Express Card number.
S/E Number The identifying number assigned to Service Establishments. This value is
listed for all Transactions originating from an S/E location. For Transactions
without an S/E number, the Transaction type code is reported. Only the
Cardmember number, Transaction code and Transaction times are dis-
played. For example:
8001 TRANS = Account status lookup
75 TRANS = Used to apply the ‘91’ reason code. Participants using GNSAS
to decision Transactions apply other statuses.
77 TRANS = Account negative update.
MST Time In The Mountain Standard Time (Mountain Standard Time (MST)) GNSAS
received the Transaction/request.
MST Time Out Mountain Standard Time (Mountain Standard Time (MST)) the Network
responded to the Transaction/request.
USD Dollar Amount Amount requested in U.S. Dollars only.
Original Transaction The first Transaction amount in the currency used by the S/E.
Amount

October 2019 Page 7-51

Table 7-16. Authorization Transaction Detail: Definitions (continued)

Data Element Name Definition
Orig Curr The currency type that was used to display the Original Transaction
Amount.
Action Code The type of action taken for the Authorization Request. Refer to the Action
Codes section of the Codes Reference Guide for valid codes and their
descriptions.
Approval Code The Approval Code given by the Network or by the primary Authorized
Processor. If the S/E can receive six digit Approval Codes, this field shows
six digits, if not, it shows two digits. For declined, pended, 8001 TRANS,
and non-credit request Transactions, this field is blank.
Resolution Transaction resolution:
• Approved
• Declined
• Pended
• Reversal
• AAV Appr
• AAV Decl
• AAV Pend
• AAV Only
• Regsw Appr
• Regsw Decl
• Regsw Pend
• Regsw
• PIN Appr
• PIN Decl
• PIN Pend
This field applies only to credit requests. For account status
updates (e.g., negative, VIP, etc.), the field is blank.
Auth By The party who resolved the Transaction/request. For example:
• AMEX = the Network, where the Network is the primary Authorized Pro-
cessor.
• ISSR = Participant’s Authorized Processor, when the Network is not the
primary Authorized Processor.
• STND = the Network stood in on behalf of the Network Participant
• DCP = Network Remote Stand-In on behalf of the Participant
• S/E = The authorization decision was made by the Service Establish-
ment (limited use only)
When the Network switches a Transaction/request to the Participant’s pri-
mary Authorized Processor, if there is no response in eight seconds from
the time GNSAS ‘switched’ the Transaction, the Network stands in.
Input Mode The mode of input for the Transaction: swiped, non swiped or voice. This
field is blank for 8001 TRANS and non-credit request Transactions.

Page 7-52 October 2019

Table 7-16. Authorization Transaction Detail: Definitions (continued)

Data Element Name Definition
Bin Bank Identification Number; in this report, a five-digit prefix of the num-
ber identifying the Issuer Institution. Also used as the first five digits of a
Card Account number, issued by the Issuer.
Total Number CASLOG Total number of Transactions/requests reported for a BIN.
Records
Grand Total Number Grand total of all Transactions/requests reported for the Participant.
CASLOG Records
For Total $ Grand total dollar amount of all Transaction/requests reported in U.S. Dol-
lars for the Participant.

October 2019 Page 7-53

Acquirer Detail

Report Usage The Acquirer Detail report (Report ID Number BC042AA0) lists
acquiring Transaction data of inbound traffic for a specific AEGNS
acquiring center and enables Acquirers to research customer
inquiries and forecast authorization traffic volume. This report is
sorted by Card number, BIN range, S/E number, and MST Time In
(i.e., the time the Authorization Request was received by GNSAS).

Frequency Daily

Printing This report is designed to be printed in landscape orientation.

Definitions Definitions for each of the fields on the Acquirer Detail report are
below.

Table 7-17. Acquirer Detail: Definitions

Data Element Name Definition
Run Date The date the report was created.
For “Participant’s Displays the Participant’s name
Name”
For Process Date The date the Transaction/request came to GNSAS.
Cardmember Number The Cardmember’s valid American Express Card number.
S/E Number The Service Establishment number for Transactions originating from an
S/E location. If there is no S/E number, the Transaction type code is
reported. Only the Cardmember number, Transaction code and Transaction
times are displayed. For example:
8001 TRANS = Account status lookup
75 TRANS = Used to apply the ‘91’ reason code. Participants using GNSAS
to decision Transactions apply other statuses.
77 TRANS = Account negative update
MST Time In The Mountain Standard Time (Mountain Standard Time (MST)) GNSAS
received the Transaction/request.
MST Time Out Mountain Standard Time (Mountain Standard Time (MST)) the Network
responded to the Transaction/request.
USD Dollar Amount Amount requested in U.S. Dollars only
Original Transaction The first Transaction amount in the currency used by the S/E.
Amount
Orig Curr The currency type that was used to display the Original Transaction
Amount.

Page 7-54 October 2019

Table 7-17. Acquirer Detail: Definitions (continued)

Data Element Name Definition
Action Code The type of action taken for the Authorization Request. Refer to the Action
Codes section of the Codes Reference Guide for valid codes and their
descriptions.
Approval Code The Approval Code given by the Network or by the primary Authorized
Processor. If the S/E can receive six-digit Approval Codes, this field shows
six digits; if not, it shows two digits. For declined, pended, 8001 TRANS,
and non-credit request Transactions, this field is blank.
Resolution Transaction resolution:
• Approved
• Declined
• Pended
• Reversal
• AAV Appr
• AAV Decl
• AAV Pend
• AAV Only
• Regsw Appr
• Regsw Decl
• Regsw Pend
• Regsw
• PIN Appr
• PIN Decl
• PIN Pend
This field applies only to credit requests. For account status
updates (e.g., negative, VIP, etc.), the field is blank.
Auth By The party who resolved the Transaction/request. For example:
AMEX = The Network, where the Network is the primary Authorized Pro-
cessor.
ISSR = Participant’s Authorized Processor, when the Network is not the
primary Authorized Processor.
STND = The Network stood in on behalf of the Issuer
When the Network switches a Transaction/request to the Participant’s pri-
mary Authorized Processor, if there is no response in eight seconds from
the time GNSAS ‘switched’ the Transaction, the Network stands in.
Input Mode The mode of input for the Transaction: swiped, non swiped or voice. This
field is blank for 8001 TRANS and non-credit request Transactions.
Total Number CASLOG The total number of Transactions/requests reported for a BIN.
Records
For Total $ The total dollar amount of all Transactions/requests reported in U.S. Dol-
lars for a BIN.

October 2019 Page 7-55

Exception Detail Report

Report Usage The Exception Detail Report (Report ID Number BC059AA0) gives a
list of the current data in the Network Exception Database. The
report must be requested through your AEGNS Representative.

Frequency This report is made on the first day of each month and is part of the
existing standard Authorization reports.

Printing This report is designed to be printed in landscape orientation. Detail

data for two Cards on the Exception Database are on each report
line.

Definitions Definitions for each of the fields on the Exception Detail report are
below.

Table 7-18. Exception Detail Report: Definitions

Data Element Name Definition
Run Date The date the report was created.
For “Participant's Displays the Participant's name.
Name”
For Process Date The date the data is retrieved from the database. This date is the same as
the run date.
Cardmember Number The Cardmember’s valid American Express Card number.
Update Date The date on which the Exception Database was updated.
Exception Reason The reason why this Cardmember Number is an exception.

Page 7-56 October 2019

Authorization Decline Transaction Stand-In Detail Report

Report Usage The Authorization Decline Transaction Stand-In Detail report

(Report ID Number BC053AA0) lists Transaction data for
authorizations that were declined by the Network during Stand-In
processing. This report is sorted by the Participant’s BIN range, S/E
number, and MST Time In (i.e., the time the Authorization Request
was received by GNSAS).

Frequency Monthly

Printing This report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the Authorization Transaction

Detail report are below.

Table 7-19. Authorization Decline Transaction Stand-In Detail: Definitions

Data Element Name Definition
Run Date The date the report was created.
For “Participant’s Displays the Participant’s name.
Name”
For Process Month The month and year the Transactions are reported.
Cardmember Number The Cardmember’s valid American Express Card number.
S/E Number The identifying number assigned to Service Establishments. This value is
listed for all Transactions originating from an S/E location. For Transactions
without an S/E number, the Transaction type code is reported. Only the
Cardmember number, Transaction code and Transaction times are dis-
played. For example: 8001 TRANS=Account status lookup 75
TRANS=Used to apply the ‘91’ reason code. Participants using GNSAS to
decision Transactions apply other statuses. 77 TRANS =Account negative
update.
S/E Type The type of S/E that the Transaction was authorized for. Refer to the
Exhibits chapter of the Business and Operational Policies manual for more
instruction.
MST Time In The Mountain Standard Time (Mountain Standard Time (MST)) GNSAS
received the Transaction/request.
MST Time Out Mountain Standard Time (Mountain Standard Time (MST)) the Network
responded to the Transaction/request.
USD Dollar Amount Amount requested in U.S. Dollars only.
Original Transaction The first Transaction amount in the currency used by the S/E.
Amount

October 2019 Page 7-57

Table 7-19. Authorization Decline Transaction Stand-In Detail: Definitions

Data Element Name Definition
Orig Curr The currency type that was used to display the Original Transaction
Amount.
Decline Reason The reason that the Authorization Request was declined, during stand-in
processing.
Bin Bank Identification Number; in this report, a five-digit prefix of the num-
ber identifying the Issuer Institution. Also used as the first five digits of a
Card Account number, issued by the Issuer.
Total Number CASLOG Total number of Transactions/requests reported for a BIN.
Records
Grand Total Number Grand total of all Transactions/requests reported for the Participant.
CASLOG Records
For Total $ Grand total dollar amount of all Transaction/requests reported in U.S. Dol-
lars for the Participant.

Page 7-58 October 2019

Authorization Referred Stand-In Detail Report

Report Usage The Authorization Referred Stand-In Detail report (Report ID

Number BC053AA0) lists Transaction data for authorizations that
were referred by the Network, during Stand-In processing. This
report is sorted by the Participant’s BIN range, S/E number, and
MST Time In (i.e., the time the Authorization Request was received
by GNSAS).

Frequency Monthly

Printing This report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the Authorization Transaction

Detail report are below.

Table 7-20. Authorization Referred Stand-In Detail: Definitions

Data Element Name Definition
Run Date The date the report was created.
For “Participant’s Displays the Participant’s name.
Name”
For Process Month The month and year the Transactions are reported.
Cardmember Number The Cardmember’s valid American Express Card number.
S/E Number The identifying number assigned to Service Establishments. This value is
listed for all Transactions originating from an S/E location. For Transactions
without an S/E number, the Transaction type code is reported. Only the
Cardmember number, Transaction code and Transaction times are dis-
played. For example: 8001 TRANS=Account status lookup 75
TRANS=Used to apply the ‘91’ reason code. Participants using GNSAS to
decision Transactions apply other statuses. 77 TRANS=Account negative
update.
S/E Type The type of S/E that the Transaction was authorized for. Refer to the
Exhibits chapter of the Business and Operational Policies manual for more
instruction.
MST Time In The Mountain Standard Time (Mountain Standard Time (MST)) GNSAS
received the Transaction/request.
MST Time Out Mountain Standard Time (Mountain Standard Time (MST)) the Network
responded to the Transaction/request.
USD Dollar Amount Amount requested in U.S. Dollars only.
Original Transaction The first Transaction amount in the currency used by the S/E.
Amount
Orig Curr The currency type that was used to display the Original Transaction
Amount.

October 2019 Page 7-59

Table 7-20. Authorization Referred Stand-In Detail: Definitions (continued)

Data Element Name Definition
Decline Reason The reason that the Authorization Request was referred, during Stand-In
processing.
Bin Bank Identification Number; in this report, a five-digit prefix of the num-
ber identifying the Issuer Institution. Also used as the first five digits of a
Card Account number, issued by the Issuer.
Total Number CASLOG Total number of Transactions/requests reported for a BIN.
Records
Grand Total Number Grand total of all Transactions/requests reported for the Participant.
CASLOG Records
For Total $ Grand total dollar amount of all Transaction/requests reported in U.S. Dol-
lars for the Participant.

Page 7-60 October 2019

Recurring Billing Cancellation Records Reports

Report Usage The Recurring Billing Cancellation Records Reports are provided to
an Issuer and show the the Recurring Billing Cancellation data that
the Issuer has supplied to the Network.
The reports help Issuers in the management of their Recurring
Billing Cancellation records.
The 2 reports available to Issuers that have certified for the
Recurring Billing Cancellation Service are:
• Active Records Report
• Changed and Deleted Records Report
These reports are delivered as part of a certified Issuer’s Monthly
Authorization Reporting.

Active Records The Active Records Report is a list of the Recurring Billing
Report Cancellation data in the Network Exception Database.

Changed and The Changed and Deleted Records Report is a list of the Recurring
Deleted Records Billing Cancellation data that was erased from the Network
Report Exception Database the month before. The records may have
expired or been deleted by the Issuer.

Frequency Monthly

Printing These reports are designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the Recurring Billing

Cancellation Records Reports are below.

Table 7-21. Recurring Billing Cancellation Records Reports: Definitions

Data Element Name Definition

Active Records Reports
Run Date The date the report was created.
Cardmember Number The Cardmember’s valid American Express Card number.
S/E Number The Service Establishment (S/E) number given to one or more locations of
the Card Acceptor. The number is ten digits.

October 2019 Page 7-61

Table 7-21. Recurring Billing Cancellation Records Reports: Definitions

(continued)
Data Element Name Definition
RB Blocking Code This code identifies a Recurring Billing Cancellation in the Exception File
from the Issuer.
If Issuers uses the Enhanced Exception File, this code must be Exception
Code BZ = Recurring Billing Cancellation.
If Issuers use the Batch Exception Update Request (9344) message, this
code must be Message Reason Code 3704 = Recurring Billing Cancellation.
Minimum Amount The minimum Transaction amount that the Network will block as part of
the Recurring Billing Cancellation Service.
Maximum Amount The maximum Transaction amount that the Network will block as part of
the Recurring Billing Cancellation Service.
Transaction Currency The numeric code for the currency used in the Transaction.
Code
Date Reported The date when the Issuer reported the Recurring Billing Cancellation block.
Record Expiration Date The date when the Exception Record expires on the Network.
Changed and Deleted Records Report
Run Date The date the report was created.
Cardmember Number The Cardmember’s valid American Express Card number.
S/E Number The Service Establishment (S/E) number given to one or more locations of
the Card Acceptor. The number is ten digits.
Minimum Amount The minimum Transaction amount that the Network will block as part of
the Recurring Billing Cancellation Service.
Maximum Amount The maximum Transaction amount that the Network will block as part of
the Recurring Billing Cancellation Service.
Transaction Currency The numeric code for the currency used in the Transaction.
Code
Original Reported Date The date when the Issuer reported the Recurring Billing Cancellation
record.
Original Expiry Date The expiration date, set by the Issuer, in the first Exception Record.
Modify Date The Date when the Recurring Billing Cancellation record was erased from
the Network Exception Database.
Change/Delete Reason The reason why the Recurring Billing Cancellation record was erased from
the Network Exception Database. This could be:
• Changed by the Issuer
• Deleted by the Issuer
• Expired when the Record Expiration date was reached

Page 7-62 October 2019

Section 3 Clearing and Settlement Reports

Clearing and Settlement Reports

Overview Clearing and Settlement reports show all accepted and cleared
Transactions by the Network and give the settlement for each
Participant in the Daily Activity Report (DAR).

Report Delivery The Global Online Business Exchange (GLOBE) sends the cleared
Transaction summary reports to the Participants.

More Instruction Contact your AEGNS Representative for more instruction about the
delivery of reports.
Refer to the Clearing and Settlement chapter in the Network
Specifications - Authorization manual for instruction on clearing and
settlement.

October 2019 Page 7-63

Daily Settlement Advisement

Report Usage The Daily Settlement Advisement report is a document created by

the Network for specific Participants. It increases the Daily Activity
File to give Participant more calculations on settlements not
automatically done by the Network.

Page 7-64 October 2019

Daily Activity Report (DAR)

Report Usage The Daily Activity Report (DAR) delivers a single report of daily
activity that can decrease and simplify the time the Participant
spends on reconciliation and settlement. The last inclear of the day
starts the Daily Activity Process and the creation of the Daily
Activity Report and the Daily Activity File.
Monthly reports are generated when fees are applied.

The DAR includes these:

• External File Tracking
• Net Settlement Summary
• Gross Settlement Summary
• Network Fee Summary Report (monthly)
• Issuer’s/Network Rate Amount Summary
• Current Day Activity - Warehoused Transactions
• Accumulated Activity - Warehoused Transactions
• Non-Financial Summary
• Issuer’s/Network Rate Amount by Industry Segment
• Non-Cleared Transaction Summary
• Returned Transaction Summary
• Network Fee Summary By VBU (monthly)
• External Network Fee Detail Report (monthly)
• Pending Transaction Summary

Divisions The DAR reports all daily activities in a summarized format for all
Issuer IINs and Acquirer AINs associated with one organization
(Organization ID) for one reporting period.
The report is organized into three divisions.

continued on next page

October 2019 Page 7-65

Organization Summarizes the organizations’ daily activity by accumulating the

Division total for all Issuer IINs and Acquirer AINs activity for the reporting
period. There is only one organization division per report. The
reporting period is the time between the last completed DAR and
the currently scheduled DAR. This time frame is usually a 24 hour
time period.
Each division receives their specific report data. The report data
includes components used for settlement or reconciliation. The
format and order are the same for each of the three divisions.

Issuer Division Summarizes the daily activity for each Issuer (IIN) associated with
the organization that is reported.

Acquirer Division Summarizes the daily activity for each Acquirer (AIN) associated
with the organization that is reported.

Section Types There are two sections for each division. The sections are based on
the primary function of the section.

Settlement The primary function of the settlement section is to derive the daily
Net Settlement Amount.

Reconciliation The primary function of the reconciliation section is to give data

about the Transactions included or not included in the settlement
calculation.

continued on next page

Page 7-66 October 2019

Reports In Each This is a list of reports in the applicable section:

Section
Table 7-22. Reports for Settlement/Reconciliation
Settlement Reconciliation
• Net Settlement Summary • External File Tracking
• Gross Settlement Summary • Current Day Activity-Warehoused
• Network Fee Summary • Accumulated Activity-Warehoused
• Issuer’s/Network Rate • Non-Financial Summary
Amount Summary • Issuer’s/Network Rate Amount Sum-
mary by Industry Segment
• Non-Cleared Transaction Summary
• Returned Transaction Summary
• Network Fee Summary by VBU
• External Network Fee Detail
• Pending Transaction Summary

Reporting A Credit has the characters “CR” after the numeric amount.
Standards
A Debit has blanks after the numeric amount. The figures in the
Presentment Amount column on the DAR do not display a sign.

Signage Reference The Signage Reference is the debit or credit that is applicable for
Transactions that are on the Daily Activity Report.

Table 7-23. Signage Reference

Issuer’s/Net
Message
Function Processing work Rate
Transaction Type Type Signage
Code Code Amount
Identifier
Signage Only
POS First Present- 1240 200 000000 Debit Credit Acquirer Debit Acquirer
ment Debit Issuer Credit Issuer
POS First Present- 1240 200 200000 Credit Debit Acquirer Credit Acquirer
ment Credit Issuer Debit Issuer
POS First Present- 1240 200 000090 Debit Credit Acquirer Debit Acquirer
ment Bonus Plan Debit Issuer Credit Issuer
POS First Present- 1240 200 200090 Credit Debit Acquirer Credit Acquirer
ment Bonus Plan Credit Issuer Debit Issuer
POS First Present- 1240 200 014008 Debit Credit Acquirer Debit Acquirer
ment Cash Dis- Debit Issuer Credit Issuer
bursement

October 2019 Page 7-67

Table 7-23. Signage Reference (continued)

Issuer’s/Net
Message
Function Processing work Rate
Transaction Type Type Signage
Code Code Amount
Identifier
Signage Only
POS First Present- 1240 200 220000 Credit Debit Acquirer Credit Acquirer
ment Cash Dis- Credit Issuer Debit Issuer
bursement
POS First Present- 1240 200 027908 Debit Credit Acquirer Debit Acquirer
ment Promotional Debit Issuer Credit Issuer
Program Transaction
POS First Present- 1240 200 227908 Credit Debit Acquirer Credit Acquirer
ment Promotional Credit Issuer Debit Issuer
Program Transaction

POS First Charge- 1442 450 000000 Debit Debit Acquirer Credit Acquirer
back Credit Issuer Debit Issuer
POS First Charge- 1442 450 200000 Credit Credit Acquirer Debit Acquirer
back Debit Issuer Credit Issuer
POS First Charge- 1442 450 014008 Debit Debit Acquirer Credit Acquirer
back Cash Disburse- Credit Issuer Debit Issuer
ment
POS First Charge- 1442 450 220000 Credit Credit Acquirer Debit Acquirer
back Cash Disburse- Debit Issuer Credit Issuer
ment

POS Second Pre- 1240 205 000000 Debit Credit Acquirer Debit Acquirer
sentment Debit Issuer Credit Issuer
POS Second Pre- 1240 205 200000 Credit Debit Acquirer Credit Acquirer
sentment Credit Issuer Debit Issuer
POS Second Pre- 1240 205 014008 Debit Credit Acquirer Debit Acquirer
sentment Cash Dis- Debit Issuer Credit Issuer
bursement
POS Second Pre- 1240 205 220000 Credit Debit Acquirer Credit Acquirer
sentment Cash Dis- Credit Issuer Debit Issuer
bursement

POS Final Charge- 1442 451 000000 Debit Debit Acquirer Credit Acquirer
back Credit Issuer Debit Issuer
POS Final Charge- 1442 451 200000 Credit Credit Acquirer Debit Acquirer
back Debit Issuer Credit Issuer
POS Final Charge- 1442 451 014008 Debit Debit Acquirer Credit Acquirer
back Cash Disburse- Credit Issuer Debit Issuer
ment

Page 7-68 October 2019

Table 7-23. Signage Reference (continued)

Issuer’s/Net
Message
Function Processing work Rate
Transaction Type Type Signage
Code Code Amount
Identifier
Signage Only
POS Final Charge- 1442 451 220000 Credit Credit Acquirer Debit Acquirer
back Cash Disburse- Debit Issuer Credit Issuer
ment

ATM First Present- 1240 200 010000 Debit Credit Acquirer Debit Acquirer
ment Cash Debit Issuer Credit Issuer
ATM First Present- 1240 200 170920 Debit Credit Acquirer Debit Acquirer
ment Virtual Debit Issuer Credit Issuer
ATM First Present- 1240 200 060000 Debit Credit Acquirer Debit Acquirer
ment Travelers Debit Issuer Credit Issuer
Cheques
ATM First Present- 1240 200 170808 Debit Credit Acquirer Debit Acquirer
ment Cash Debit Issuer Credit Issuer

ATM First Charge- 1442 450 010000 Debit Debit Acquirer Credit Acquirer
back Credit Issuer Debit Issuer
ATM First Charge- 1442 450 170920 Debit Debit Acquirer Credit Acquirer
back Credit Issuer Debit Issuer
ATM First Charge- 1442 450 060000 Debit Debit Acquirer Credit Acquirer
back Credit Issuer Debit Issuer
ATM First Charge- 1442 450 170808 Debit Debit Acquirer Credit Acquirer
back Credit Issuer Debit Issuer

ATM Second Pre- 1240 205 010000 Debit Credit Acquirer Debit Acquirer
sentment Cash Debit Issuer Credit Issuer
ATM Second Pre- 1240 205 170920 Debit Credit Acquirer Debit Acquirer
sentment Virtual Debit Issuer Credit Issuer
ATM Second Pre- 1240 205 060000 Debit Credit Acquirer Debit Acquirer
sentment Travelers Debit Issuer Credit Issuer
Cheques
ATM Second Pre- 1240 205 170808 Debit Credit Acquirer Debit Acquirer
sentment Cash Debit Issuer Credit Issuer

ATM Final Charge- 1442 451 010000 Debit Debit Acquirer Credit Acquirer
back Credit Issuer Debit Issuer
ATM Final Charge- 1442 451 170920 Debit Debit Acquirer Credit Acquirer
back Credit Issuer Debit Issuer

October 2019 Page 7-69

Table 7-23. Signage Reference (continued)

Issuer’s/Net
Message
Function Processing work Rate
Transaction Type Type Signage
Code Code Amount
Identifier
Signage Only
ATM Final Charge- 1442 451 060000 Debit Debit Acquirer Credit Acquirer
back Credit Issuer Debit Issuer
ATM Final Charge- 1442 451 170808 Debit Debit Acquirer Credit Acquirer
back Credit Issuer Debit Issuer

Page 7-70 October 2019

External File Tracking Report

Report Usage The External File Tracking Report lists the Outclear and Inclear files
and their status as processed by the Network for an organization
during the time period covered by its Daily Activity Report (DAR).
This includes:
• A list of Outclear files received from the organization during the
reporting period and their processing status.
• A list of Inclear files sent to the organization during the
reporting period with a status of complete.
The report identifies the files and status included in the Daily
Activity Process (DAP).

Frequency Daily

Report Placement The External File Tracking data is always the first page of the Daily
Activity Report.

Definitions Definitions for each of the fields on the External File Tracking
Summary (Organization level) report are below.

Table 7-24. External File Tracking Report: Definitions

Data Element Name Definition
Organization ID/Name The Organization ID and Name to whom the Transactions belong.
Processor ID The Acquiring Institution Identifier or Issuer Processor Identifier of the
institution which submitted the Transaction.
Seq A file sequential number assigned to each file by the file originator.
Date The date the originator created the file.

October 2019 Page 7-71

Table 7-24. External File Tracking Report: Definitions (continued)

Data Element Name Definition
Status The File and/or Transaction statuses reported are:
In Process
• File is suspended (pending disposition)
• File is sent only through the Capture phase (accepted)
Complete
• File is sent through the Settlement phase (settled), or
• File is sent through the Capture phase but is returned because the num-
ber of errors is more than the threshold level (full file reject), or
• File is sent through the Settlement phase, the file contains errors but is
not more than the error threshold level (partial file accept), or
• File is sent through the Inclear phase
In the file status of Completed is a Transaction level status Returned. It is
possible for a file to be in a Completed status but have some or all of the
Transactions returned. Refer to Transaction Count (below) for more instruc-
tion. Refer to Financial Messages Process Flow in the Network Specifica-
tions - Financial/Non-Financial manual for more instruction.

Page 7-72 October 2019

Table 7-24. External File Tracking Report: Definitions (continued)

Data Element Name Definition
Transaction Count The total number of Transactions in process, completed, and returned are
reported for each file. The “Returned” line only displays when there are
returned Transactions. The number of “In Process” or “Complete” Transac-
tions plus the “Returned” Transactions equals the total of the Transactions
in the file for the organization that is reported. The totals displayed are
based on the last status of the file.
Note: If the Transaction status is “DAF File returned”, the Transactions will
not be contributed to DAF Hash total amount, whereas the “DAF
Non-Cleared” will be contributed to DAF Hash total amount.
Retrieval Request and Fulfillment messages are not considered in
the calculation of the DAF Hash total amount.
Listed below are examples of how the Transaction counts are listed based
on the status of the file:
• File completes Capture with no returned Transactions; total number of
accepted Transactions displayed and a status of “In Process”.
• File completes Capture with returned Transactions below threshold; total
number of accepted Transactions displayed for the “In Process” status
and the total number of returned Transactions with a status of
“Returned”.
• File completes Capture with returned Transactions above the threshold or
with header and/or trailer errors (full file reject); total number of Trans-
actions with a “Returned” status.
• File completes Settlement with no returned Transactions; total number of
settled Transactions and a status of “Complete”.
• File completes Settlement but there were returned Transactions when it
completed Capture (partial file accept); total number of settled Transac-
tions with a “Complete” status and total number of Transactions that
were returned by Capture with a status of “Returned”.
• File completes Inclear; total number of Incleared Transactions and a sta-
tus of “Complete”.
Note: Non-financial Transactions (Retrieval Requests and Fulfillment
Notifications) are not in the Transactions Count column but are in
the status on this report (i.e., Status Complete Transactions Count
0 shows all Transactions in the file are non-financial.) See the
Non-Financial Summary Report.
Outclear Files Files sent from the Participant to the Network.
Inclear Files Files sent from the Network to the Participant.

October 2019 Page 7-73

Net Settlement Summary Report

Report Usage The Net Settlement Summary Report summarizes the Total Net
Settlement by Settlement Currency.

Frequency Daily

Report The total lines displayed on this page (Net Settlement) correspond
Components with the total lines throughout the report divisions for each
Currency Code reported.
Total lines in a Currency Code group are not split across pages. A
page break occurs at the end of this section.

Report If a Participant is an Issuer and Acquirer, the Organization - Net

Presentation Settlement Summary Report shows the net amount for the Issuer
and Acquirer activity.
Issuer activity is reported in the Issuer - Net Settlement Summary.
Acquirer activity is reported in the Acquirer - Net Settlement
Summary.

Definitions Definitions for each of the fields on the Organization Division - Net
Settlement Summary Report are below.

Table 7-25. Net Settlement Summary Report: Definitions

Data Element Name Definition
Organization ID/Name The Organization ID and Name to whom the Transactions belong.
Settlement Currency The ISO numeric and alpha currency codes of the Settlement Amount.
Code
Total Gross Settlement The total of all POS and ATM Transactions to be paid in the Settlement Cur-
rency by currency. This is the settlement amount for Acquirers or Issuers
before the Acquirer or Issuer Amount is deducted.
Total Pass Through Reserved for future use. Total entry will display a zero amount.
Fees
Total Network Fees The amount Participants pay for marketing, operational and other services
supplied directly or indirectly by AEGNS by currency. If there are no Net-
work Fees, zero is displayed.
Total Issuer’s/Network The sum of all Issuer’s/Network Rate Amounts.
Rate Amount
Total Net Settlement The Total Net Settlement amount is equal to the sum of the Total Gross
Settlement, Total Network Fees minus Total For Issuer’s/Network Rate
Amount by currency. This is the amount settled with the Participant.

Page 7-74 October 2019

Definitions Definitions for each of the fields on the Issuer Division - Net
Settlement Summary report are below.

Table 7-26. Net Settlement Summary Report: Definitions

Data Element Name Definition
Issuer ID/Name The Issuer Identification Number (IIN) and Name to whom the Transactions
belong.
Settlement Currency The ISO numeric and alpha currency codes of the Settlement Amount.
Code
Total Gross Settlement The total of all POS and ATM Transactions to be paid in the Settlement Cur-
rency by currency. This is the settlement amount for Acquirers or Issuers
before the Acquirer or Issuer Amount is deducted.
Total Pass Through Reserved for future use. Total entry will display a zero amount.
Fees
Total Network Fees The amount Participants pay for marketing, operational and other services
supplied directly or indirectly by AEGNS by currency. If there are no Net-
work Fees, zero is displayed.
Total For Issuer’s Rate The sum of all Issuer’s Rate Amounts.
Amount
Total Net Settlement The Total Net Settlement amount is equal to the sum of the Total Gross
Settlement, Total Network Fees minus Total Issuer Rate Amount by cur-
rency. This is the amount settled with the Participant.

Definitions Definitions for each of the fields on the Acquirer Division - Net
Settlement Summary report are below.

Table 7-27. Net Settlement Summary Report: Definitions

Data Element Name Definition
Acquirer ID/Name The Acquirer Identification Number (AIN) and Name to whom the Transac-
tions belong.
Settlement Currency The ISO numeric and alpha currency codes of the Settlement Amount.
Code
Total Gross Settlement The total of all POS and ATM Transactions to be paid in the Settlement Cur-
rency by currency. This is the settlement amount for Acquirers or Issuers
before the Acquirer or Issuer Amount is deducted.
Total Pass Through Reserved for future use. Total entry will display a zero amount.
Fees
Total Network Fees The amount Participants pay for marketing, operational and other services
supplied directly or indirectly by AEGNS by currency. If there are no Net-
work Fees, zero is displayed.
Total Network Rate The sum of all Network Rate Amounts.
Amount

October 2019 Page 7-75

Table 7-27. Net Settlement Summary Report: Definitions (continued)

Data Element Name Definition
Total Net Settlement The Total Net Settlement amount is equal to the sum of the Total Gross
Settlement, Total Network Fees minus Total Network Rate Amount by cur-
rency. This is the amount settled with the Participant.

Page 7-76 October 2019

Gross Settlement Summary Report

Report Usage The Gross Settlement Summary Report displays gross Transaction
totals for Presentments, Chargebacks, and ATM Fees (Issuer and/or
Acquirer).
Presentments include Warehoused (First Presentments for Bonus
Plan) Transactions from the Warehouse for settlement.

Frequency Daily

Report If a Participant is an Issuer and Acquirer, the Organization - Gross

Presentation Settlement Summary Report shows the gross amount for the Issuer
and Acquirer activity.
Issuer activity is reported in the Issuer - Gross Settlement
Summary. Acquirer activity is reported in the Acquirer - Gross
Settlement Summary.

Definitions Definitions for each of the fields on the Organization Division -

Gross Settlement Summary report are below.

Table 7-28. Gross Settlement Summary Report: Definitions

Data Element Name Definition
Organization ID/Name The Organization ID and Name to whom the Transactions belong.
Settlement Currency The ISO numeric and alpha currency codes of the Settlement Amount.
Code
Transaction Type The literals (e.g., POS, ATM, or Cash) that show the type of Transactions.
Presentment Currency The ISO numeric currency code of the Presentment currency in which the
Code (Pres Curr Code) First Presentment Transaction Amount was executed.
Transaction Count The total number of Transactions that have been settled per message type.
If Transaction count is zero, this section will not be on the report.
Presentment Amount The sale or credit amount of the first Cardmember Transaction in the Trans-
action currency presented to the Network.
Outclear Gross Settle- The total of all charges sent from the Participant to the Network to be paid
ment in the Settlement Currency. This is the settlement amount for Acquirers or
Issuers before the Acquirer or Issuer Amount is deducted.
Inclear Gross Settle- The total of all charges sent from the Network to the Participant to be paid
ment in the Settlement Currency. This is the settlement amount for Acquirers or
Issuers before the Acquirer or Issuer Amount is deducted.
Net Difference The sum of the Outclear Gross Settlement amount plus the Inclear Gross
Settlement amounts.

October 2019 Page 7-77

Table 7-28. Gross Settlement Summary Report: Definitions (continued)

Data Element Name Definition
Processing Code The literal of Debit or Credit that shows the processing code of the Transac-
tion.
Message Type The literal display of the Message Type (e.g., First Presentment) for the
Transaction.

Definitions Definitions for each of the fields on the Issuer Division - Gross
Settlement Summary report are below.

Table 7-29. Gross Settlement Summary Report: Definitions

Data Element Name Definition
Issuer ID/Name The Issuer Identification Number (IIN) and Name to whom the Transac-
tions belong.
Settlement Currency The ISO numeric and alpha currency codes of the Settlement Amount.
Code
Transaction Type The literals (e.g., POS or ATM) that show the type of Transactions.
Presentment Currency The ISO numeric currency code of the Presentment currency in which the
Code (Pres Curr Code) First Presentment Transaction Amount was executed.
Transaction Count The total number of Transactions that have been settled per message
type. If Transaction count is zero, this section will not be on the report.
Presentment Amount The sale or credit amount of the first Cardmember Transaction in the
Transaction currency presented to the Network.
Outclear Gross Settle- The total of all charges sent from the Participant to the Network to be
ment paid in the Settlement Currency. This is the settlement amount for
Acquirers or Issuers before the Acquirer or Issuer Amount is deducted.
Inclear Gross Settle- The total of all charges sent from the Network to the Participant to be
ment paid in the Settlement Currency. This is the settlement amount for
Acquirers or Issuers before the Acquirer or Issuer Amount is deducted.
Net Difference The sum of the Outclear Gross Settlement amount plus the Inclear Gross
Settlement amounts.
Processing Code The literal of Debit or Credit that show the processing code of the Trans-
action.
Message Type The literal display of the Message Type (e.g., First Presentment) for the
Transaction.

continued on next page

Page 7-78 October 2019

Definitions Definitions for each of the fields on the Acquirer Division - Gross
Settlement Summary report are below.

Table 7-30. Gross Settlement Summary Report: Definitions

Data Element Name Definition
Acquirer ID/Name The Acquirer Identification Number (AIN) and Name to whom the Transac-
tions belong.
Settlement Currency The ISO numeric and alpha currency codes of the Settlement Amount.
Code
Transaction Type The literals (e.g., POS or ATM) that show the type of Transactions.
Presentment Currency The ISO numeric currency code of the Presentment currency in which the
Code (Pres Curr Code) First Presentment Transaction Amount was executed.
Transaction Count The total number of Transactions that have been settled per message type.
If Transaction count is zero, this section will not be on the report.
Presentment Amount The sale or credit amount of the first Cardmember Transaction in the Trans-
action currency presented to the Network.
Outclear Gross Settle- The total of all charges sent from the Participant to the Network to be paid
ment in the Settlement Currency. This is the settlement amount for Acquirers or
Issuers before the Acquirer or Issuer Amount is deducted.
Inclear Gross Settle- The total of all charges sent from the Network to the Participant to be paid
ment in the Settlement Currency. This is the settlement amount for Acquirers or
Issuers before the Acquirer or Issuer Amount is deducted.
Net Difference The sum of the Outclear Gross Settlement amount plus the Inclear Gross
Settlement amounts.
Processing Code The literal of Debit or Credit that shows the processing code of the Transac-
tion.
Message Type The literal display of the Message Type (e.g., First Presentment) for the
Transaction.

October 2019 Page 7-79

Network Fee Summary Report

Report Usage The Network Fee Summary Report displays the totals for the
Network Fees (1744) assessed during the reporting period.

Frequency Monthly

Report There is no report when there are no fees.

Presentation

Definitions Definitions for each of the fields on in the Organization Division -

Network Fee Summary Report are below.

Table 7-31. Network Fee Summary Report: Definitions

Data Element Name Definition
Organization ID/Name The Organization ID and Name to whom the Transactions belong.
Presentment Currency The ISO numeric currency code of the Presentment currency in which the
Code (Pres Curr Code) First Presentment Transaction Amount was executed.
Transaction Count The total number of Transactions that have been settled. If Transaction
count is zero, this section will not be on the report.
Presentment Amount The sale or credit amount of the first Cardmember Transaction in the Trans-
action currency presented to the Network.
Settlement Amount The total of all charges sent to and from the Participant to the Network to
be paid in the Settlement Currency. This is the settlement amount for
Acquirers or Issuers before the Acquirer or Issuer Amount is deducted.

Page 7-80 October 2019

Issuer’s/Network Rate Amount Summary Report

Report Usage The Issuer’s/Network Rate Amount Summary Report displays

summarized Issuer’s/Network Rate Amounts for Presentments and
Chargebacks by settlement currency presented during the reporting
period.

Frequency Daily

Report Local, regional and foreign Transactions are summarized into one
Components total for each settlement currency code.

Report If a Participant is an Issuer and Acquirer, the Organization -

Presentation Issuer’s/Network Rate Amount Summary Report shows the
Issuer’s/Network Rate Amounts for the Issuer and Acquirer activity.
Issuer activity is reported in the Issuer’s Rate Amount Summary
Report. Acquirer activity is reported in the Acquirer - Network Rate
Amount Summary Report.

Definitions Definitions for each of the fields on the Organization Division -

Issuer’s Rate Amount Summary report are below.

Table 7-32. Organization Division - Issuer’s/Network Rate Amount Summary

Report: Definitions
Data Element Name Definition
Organization ID/Name The Organization ID and Name to whom the Transactions belong.
Settlement Currency The ISO numeric and alpha currency codes of the Settlement Amount.
Code
Total Issuer’s/Network The total Issuer’s/Network Rate Amount for a given Settlement Currency.
Rate Amount
Transaction Count The total number of Transactions that have been settled. If Transaction
count is zero, this section will not be on the report.
Issuer’s/Network Rate The Issuer’s/Network Rate Amount calculated for a Transaction using the
Amount Issuer’s rate.

continued on next page

October 2019 Page 7-81

Definitions Definitions for each of the fields on the Issuer Division - Issuer’s
Rate Amount Summary report are below.

Table 7-33. Issuer Division - Issuer’s Rate Amount Summary Report: Definitions

Data Element Name Definition

Issuer ID/Name The Issuer Identification Number (IIN) and Name to whom the Transactions
belong.
Settlement Currency The ISO numeric and alpha currency codes of the Settlement Amount.
Code
Total Issuer’s Rate The total Network Rate Amount for a given Settlement Currency.
Amount
Transaction Count The total number of Transactions that have been settled. If Transaction
count is zero, this section will not be on the report.
Issuer’s Rate Amount The Issuer’s Rate Amount calculated for a Transaction using the Issuer’s
Rate.

Definitions Definitions for each of the fields on the Acquirer Division - Network
Rate Amount Summary report are below.

Table 7-34. Acquirer Division - Network Rate Amount Summary Report: Definitions

Data Element Name Definition

Acquirer ID/Name The Acquirer Identification Number (AIN) and Name to whom the Transac-
tions belong.
Settlement Currency The ISO numeric and alpha currency codes of the Settlement Amount.
Code
Total Network Rate The total Network Rate Amount for a given Settlement Currency.
Amount
Transaction Count The total number of Transactions that have been settled. If Transaction
count is zero, this section will not be on the report.
Network Rate Amount The per Transaction amount, based on a standard Network rate that the
Acquirer negotiated with AEGNS.

Page 7-82 October 2019

Current Day Activity - Warehoused Transactions

Report Usage The Current Day Activity Report displays the gross settlement
amounts for First Presentment Bonus Plan Transactions processed
during the reporting period. Processing encompasses the receipt of
Transaction and warehousing (deferred) of Bonus Plan Transactions.
Note: The Bonus Plan is a DPP available in the Japan local market.

Frequency Daily

Report There is no report if there is no Bonus Plan activity.

Presentation

Definitions Definitions for each of the fields on the Organization Division

Current Day Activity - Warehoused Transactions report are below.

Table 7-35. Current Day Activity - Warehoused Transactions: Definitions

Data Element Name Definition
Organization ID/Name The Organization ID and Name to whom the Transactions belong.
Settlement Currency The ISO numeric and alpha currency codes of the Settlement Amount.
Code
Transaction Type The literals (e.g., POS, Debit, or Credit) that show the type of Transactions.
Presentment Currency The ISO numeric currency code of the Presentment currency in which the
Code (Pres Curr Code) First Presentment Transaction Amount was executed.
Transaction Count The total number of Transactions that have been settled by Transaction and
currency type. If Transaction count is zero, this section will not be on
report.
Presentment Amount The sale or credit amount of the first Cardmember Transaction in the Trans-
action currency presented to the Network.
Outclear Gross Settle- The total of all charges sent from the Participant to the Network to be paid
ment in the Settlement Currency. This is the settlement amount for Acquirers or
Issuers before the Acquirer or Issuer Amount is deducted.
Inclear Gross Settle- The total of all charges sent from the Network to the Participant to be paid
ment in the Settlement Currency. This is the settlement amount for Acquirers or
Issuers before the Acquirer or Issuer Amount is deducted.
Net Difference The sum of the Outclear Gross Settlement amount and the Inclear Gross
Settlement amounts.
Message Type The literal display of the Message Type (e.g., First Presentment) for the
Transaction.

October 2019 Page 7-83

Accumulated Activity - Warehoused Transactions

Report Usage The Accumulated Activity Report displays the accumulated deferred,
deferred next and extracted from counts and settlement amounts
for warehoused (Bonus Plan) Transactions for the reporting period.

Frequency Daily

Report There is no report if there is no Bonus Plan activity.

Presentation

Definitions Definitions for each of the fields on the Organization Division

Accumulated Activity - Warehoused Transactions report are below.

Table 7-36. Accumulated Activity - Warehoused Transactions: Definitions

Data Element Name Definition
Organization ID/Name The Organization ID and Name to whom the Transactions belong.
Settlement Currency The ISO numeric and alpha currency codes of the Settlement Amount.
Code
Transaction Type The literals (e.g., POS, Debit, or Credit) that show the type of Transactions.
Deferred Settlement This column reports all data currently warehoused that will be settled at
Date, Transaction the next scheduled settlement date for the Participant.
Count, Net Settlement
Amount
Deferred Next Settle- This column reports all data currently warehoused that will be settled at
ment Date, Transac- the Participant’s settlement date that occurs immediately after the next
tion Count, Net scheduled Participant settlement date.
Settlement Amount
Extracted from Ware- This column reports all data extracted from the warehouse to be settled on
house Settlement Date, the report for the current Business Date. Bonus Plan Transactions are set-
Transaction Count, Net tled 2 times a year. All Bonus Plan Transactions are warehoused on the day
Settlement Amount they are processed by the Network as Bonus Plan Transactions.
Message Type The literal display of the Message Type (e.g., First Presentment) for the
Transaction.

Page 7-84 October 2019

Non-Financial Summary Report

Report Usage The Non-Financial Summary Report displays the counts for the
non-financial Transactions (Retrieval Request and Fulfillment
Notifications) that flowed through the Network during the reporting
period.

Frequency Daily

Report There is no report if there is no Retrieval Request or Fulfillment

Presentation Notification message.

Definitions Definitions for each of the fields on the Organization Division

Non-Financial Summary report are below.

Table 7-37. Non-Financial Summary Report: Definitions

Data Element Name Definition
Organization ID/Name The Organization ID and Name the Transactions belong to.
Outclear Transaction The total of all non-financial (Retrieval Request and Fulfillment Notification)
Count Transactions sent from the Participant to the Network.
Inclear Transaction The total of all non-financial (Retrieval Request and Fulfillment Notification)
Count Transactions sent from the Network to the Participant.
Message Type Literal that shows Retrieval Request or Fulfillment Notification message
types.

October 2019 Page 7-85

Issuer’s/Network Rate Amount by Industry Segment

Report

Report Usage The Issuer’s/Network Rate Amount by Industry Segment Report

displays summarized Issuer’s/Network Rate Amount for First and
Second Presentments and First and Final Chargebacks by Industry
Description (except foreign) presented during the reporting period.

Frequency Daily

Report If a Participant is an Issuer and Acquirer, the Organization -

Presentation Issuer’s/Network Rate Amount by Industry Segment Report shows
the Issuer’s/Network Rate Amounts for the Issuer and Acquirer
activity.
Issuer activity is reported in the Issuer’s/Network Rate Amount by
Industry Segment Report. Acquirer activity is reported in the
Acquirer - Network Rate Amount by Industry Segment Report. The
report presents local, regional, and foreign Transactions.

Definitions Definitions for each of the fields on the Organization Division

Issuer’s/Network Rate Amount by Industry Segment report are
below.

Table 7-38. Organization Division - Issuer’s/Network Rate Amount by Industry

Segment Report: Definitions
Data Element Name Definition
Organization ID/Name The Organization ID and Name to whom the Transactions belong.
Settlement Currency The ISO numeric and alpha currency codes of the Settlement Amount.
Code
Transaction Type The literals (e.g., Local, Credit) that show demographic area and type of
Transactions.
Industry Description Text description of the high level industry type of the Transaction.
Transaction Count The total number of Transactions that have been settled per industry. If
Transaction count is zero, this section will not be on the report.
Issuer’s/Network Rate The Issuer’s/Network Rate Amount calculated for a Transaction using the
Amount Issuer’s/Network rate.
Message Type The literal display of the Message Type (e.g., 2nd Presentment) for the
Transaction.

continued on next page

Page 7-86 October 2019

Definitions Definitions for each of the fields on the Issuer Division - Issuer’s
Rate Amount by Industry Segment report are below.

Table 7-39. Issuer Division - Issuer’s Rate Amount by Industry Segment Report:
Definitions
Data Element Name Definition
Issuer ID/Name The Issuer ID and Name to whom the Transactions belong.
Settlement Currency The ISO numeric and alpha currency codes of the Settlement Amount.
Code
Transaction Type The literals (e.g., Local, Credit) that show demographic area and type of
Transactions.
Industry Description Text description of the high level industry type of the Transaction.
Transaction Count The total number of Transactions that have been settled per industry. If
Transaction count is zero, this section will not be on the report.
Issuer’s Rate Amount The Issuer’s Rate Amount calculated for a Transaction using the Issuer’s
Rate.
Message Type The literal display of the Message Type (e.g., 2nd Presentment) for the
Transaction.

Definitions Definitions for each of the fields on the Acquirer Division - Network
Rate Amount by Industry Segment report are below.

Table 7-40. Acquirer Division - Network Rate Amount by Industry Segment Report:
Definitions
Data Element Name Definition
Acquirer ID/Name The Acquirer ID and Name to whom the Transactions belong.
Settlement Currency The ISO numeric and alpha currency codes of the Settlement Amount.
Code
Transaction Type The literals (e.g., Local, Credit) that show demographic area and type of
Transactions.
Industry Description Text description of the high level industry type of the Transaction.
Transaction Count The total number of Transactions that have been settled per industry. If
Transaction count is zero, this section will not be on the report.
Network Rate Amount The Network Rate Amount calculated for a Transaction using the Network
Rate.
Message Type The literal display of the Message Type (e.g., 2nd Presentment) for the
Transaction.

October 2019 Page 7-87

Non-Cleared Transaction Summary

Report Usage The Non-Cleared Transaction Summary Report displays summarized

Transaction Counts and Amounts for Presentments, Chargebacks,
Retrieval Requests, Fulfillment Notifications and ATM Fees presented
during the reporting period that have been received by the Network
and have completed capture but not the settlement calculation
process.

Frequency Daily

Report The report shows POS and ATM Transactions which the Network
Presentation cannot process. If Transaction type is not known (i.e., POS or ATM),
the Transaction shows as POS.

Definitions Definitions for each of the fields on the Organization Division

Non-Cleared Transaction Summary report are below.

Table 7-41. Non-Cleared Transaction Summary: Definitions

Data Element Name Definition
Organization ID/Name The Organization ID and Name to whom the Transactions belong.
Transaction Type The literals (e.g., POS, ATM, and Cash) that show the type of Transactions
(Debit and Credit).
Transaction Currency The ISO numeric currency code of the Transaction currency in which the
Code Transaction occurred.
Transaction Count The total number of Transactions that have been settled for each message
type. If Transaction count is zero, this section will not be on the report.
Transaction Amount The sale or credit amount of the first Cardmember Transaction in the Trans-
action currency presented to the Network. This is the sales invoice amount
and taxes. It does not include fees.
Totals Total Transaction count is displayed for each Transaction type grouping.
Message Type The literal display of the Message Type (e.g., 1st Presentment) for the
Transaction.

Page 7-88 October 2019

Returned Transaction Summary Report

Report Usage The Returned Transaction Summary Report displays summarized

Transaction Amounts for Presentments, Chargebacks, Retrieval
Requests, Fulfillment Notifications and ATM Fees presented during
the reporting period that have been returned to the Participants.

Frequency Daily

Report The report presents POS and ATM Transactions returned to the
Presentation Participant.

Definitions Definitions for each of the fields on the Organization Division

Returned Transaction Summary report are below.

Table 7-42. Returned Transaction Summary Report: Definitions

Data Element Name Definition
Organization ID/Name The Organization ID and Name to whom the Transactions belong.
Tracking ID An identification number assigned to each file for tracking and sorting.
Also includes the Julian Date of the day that the originator created the file.
Transaction Type The literals (e.g., POS, ATM, and Cash) that show the type of Transactions
(Debit and Credit).
Transaction Currency The ISO numeric currency code of the Transaction currency in which the
Code (Tran Curr Code) Transaction occurred.
Transaction Count The total number of Transactions that have been settled per message
type. If Transaction count is zero, this section will not be on the report.
Transaction Amount The sale or credit amount of the first Cardmember Transaction in the
Transaction currency presented to the Network. This is the sales invoice
amount and taxes. It does not include fees.
Totals Total Transaction count is displayed for each Transaction type grouping.
Message Type The literal display of the Message Type (e.g., 1st Presentment) for the
Transaction.

October 2019 Page 7-89

Network Fee Summary by VBU Report

Report Usage The Network Fee Summary by VBU Report displays the totals for
each Valid Billing Unit (VBU) category of Network Fees assessed
during the reporting period.

Frequency Monthly

Report There is no report if there are no fees.

Presentation

Definitions Definitions for each of the fields on the Organization Division

Network Fee Summary by VBU report are below.

Table 7-43. Network Fee Summary by VBU Report: Definitions

Data Element Name Definition
Organization ID/Name The Organization ID and Name to whom the Transactions belong.
Settlement Currency The ISO numeric and alpha currency codes of the Settlement Amount.
Code
VBU Code Valid Billing Unit Code
Refer to the Codes Reference Guide for a list of Valid Billing Unit Codes.
Valid Billing Unit The description of the Valid Billing Unit Code shows the cause for the fee.
Description
Transaction Count The total number of Transactions that have been settled per valid billing
unit. If Transaction count is zero, this section will not be on the report.
Settlement Amount The amount of the fees in the settlement currency of the Participant.
VBU Totals The total of the Transaction count and the total settlement amount for
Network fees for all VBUs.

Page 7-90 October 2019

External Network Fee Detail Report

Report Usage The External Network Fee Detail Report aggregates the Transaction
based Valid Billing Unit (VBU) 001-999 and gives a 95 byte
description for the ad hoc and miscellaneous VBUs for Participants
assessed fees during the report period.

Frequency Monthly

Report There is no report if there are no fees.

Presentation

Definitions Definitions for each of the fields on the Organization Division

Network Fee Summary by VBU report are below.

Table 7-44. External Network Fee Detail Report: Definitions

Data Element Name Definition
Organization ID/Name The Organization ID and Name to whom the Transactions belong.
Institution ID/Name The Institution ID and Name to whom the Transactions belong.
Settlement Currency The ISO numeric and alpha currency codes of the Settlement Amount.
Code
Fee Description The description associated with the ad hoc or miscellaneous fee assessed.
TID The Transaction Identifier assigned to the fee assessment.
Calculation Method A brief description of the calculation formula used to assess the fee repre-
sented by the Valid Billing Unit (VBU). The three types of calculation are:
• Price x Quantity
• Percent x Amount
• Flat Fee
Calculation Factor The value used to calculate a VBU fee. When the Calculation Method is
defined as Price x Quantity, the Calculation Factor is a pre-defined VBU
price. When the Calculation Method is defined as Percent x Amount, the
Calculation Factor is a pre-defined percentage set for the given VBU. For
the Flat fee procedure, the factor is zero as the fee amount is not calcu-
lated. A lump sum VBU fee amount is specified.
Quantity The number of charges for the VBU assessed when the Price x Quantity
calculation is used.
Fee Basis Amount The amount of the fee when the Flat Fee and Percent x Amount calcula-
tions are used.
Calculated Fee Cur- The code which identifies the currency in which the fee was assessed.
rency
Calculated Fee Amount The amount of the fee assessed in the calculated currency.

October 2019 Page 7-91

Table 7-44. External Network Fee Detail Report: Definitions (continued)

Data Element Name Definition
Fee Settlement Amount The value of the calculated fee amount in the Participants settlement cur-
rency. If the total debits and total credits net to zero, each VBU and
amount will be displayed.
Note: A ‘CR’ is adjacent to the amount when the amount is a credit.

Page 7-92 October 2019

Pending Transaction Summary Report

Report Usage The Pending Transaction Summary Report displays summarized

Transaction counts and amounts for Presentments presented during
the reporting period that have been received by the Network and
have completed capture but have not completed the settlement
process.

Frequency Daily

Report The report provides Presentment Transactions that have not been
Presentation settled.

Definitions Definitions for each of the fields on the Acquirer Division Pending
Transaction Summary report are below.

Table 7-45. Pending Transactions Summary Report: Definitions

Data Element Name Definition
Acquirer ID/Name The Acquirer ID and Name to whom the Transactions belong.
Tracking ID An identification number assigned to each file for tracking and sorting Also
includes the Julian Date of the day that the originator created the file.
Presentment Currency The ISO numeric and alpha currency codes of the Presentments Amounts
Code for a specific currency group.
Transaction Type The literals (e.g., 1st Presentment, 2nd Presentment) that show the type
of Transactions (Debit and Credit).
Presentment Currency The ISO numeric currency code of the Presentment currency in which the
Code (Pres Curr Code) Presentment occurred.
Transaction Count The total number of Transactions that have been reported per message
type. If Transaction count is zero, this section will not be on the report.
Presentment Amount The sale or credit amount of the first Cardmember Transaction in the
Transaction currency presented to the Network. This is the sales invoice
amount and taxes. It does not include fees.
Total for Presentment Total Transaction count and Presentment Amount is displayed for each
Currency (Curr) Code Transaction currency type grouping.

October 2019 Page 7-93

Section 4 Fraud Reports

Fraud Reports

Overview The Network supplies several fraud reports to Acquirers and Issuers
to assist in the understanding and prevention of fraud.

Important Effective February 2014, the reports in this section will not be
available on FraudNet.
Note: After February 2014, Participants will still receive all 13
Fraud Reports in this section through the GLOBE.
Existing reports in this section have been consolidated from thirteen
(13) reports delivered through the GLOBE to nine (9) User Driven
Reports on FraudNet as follows:

Existing Reports Report# User Driven Reports

Issuer Gross Fraud Update FSG002 Issuer Gross Fraud Summary

Issuer Fraud Summary FSG003

Fraud by Issuer and SE Market FSG019 Issuer Fraud Details Combined

Fraud by Issuer and Industry FSG020

Fraud by Issuer and E Market FSG021

and Fraud Type

Fraud by Acquirer and FSG022 Acquirer Fraud Details

Cardmember Market Combined

Fraud by Acquirer and Industry FSG023

Fraud by Acquirer and FSG024
Cardmember Market and Fraud
Type

Acquirer Report Bi Weekly FSG11A Acquirer Report Bi Weekly

Summary Summary

Acquirer Report Monthly Detail FSG11B Acquirer Report Monthly Detail

Top 40 SEs 6 Month Summary FSG11C Top 40 SEs 6 Month Summary

Top 40 SEs 6 Month Detail FSG11D Top 40 SEs 6 Month Detail

Issuer Non Actioned Rejected FSG040 Issuer Non Actioned Rejected

Transaction Details Transaction Details
Issuer Non Actioned Rejected
Transaction Summary

continued on next page

Page 7-94 October 2019

Report Delivery The fraud reports are distributed to Participants through the Global
Online Business Exchange (GLOBE) or FraudNet.

Industry Fraud reports use these industry categories to help Participants

Categories analyze and understand the industry segments in which the fraud
was reported. All categories (except Mail/Phone order), exclude
mail, telephone, or Internet fraud.

Table 7-46. Industry Categories

Industry Category Description
Hotels & Motels Lodging, hotels, motels, and resorts
Restaurants & Bars Eating or drinking establishments, including fast
food
Financial Services Financial services, including insurance and tax
preparation
Airlines Airlines and air carriers
Car Rentals Vehicle rental, including utility trailer, motor
home, and recreational vehicles
Department Stores Department stores
Clothing Shops Clothing shops including shoes, furs, miscella-
neous apparel and accessories, and clothing
rental
Flower/Candy/Book Florists, candy, dairy product, or book sales
Gift/Luggage/ Jew- Boutiques, luggage and leather sales, or jewelers
elry
Gourmet & Liquor Specialty items and liquor sales
Mail/Phone Order Items purchased over the phone, by mail, or by
Internet where merchandise is shipped to the
customer
Petrol Companies Petrol (gasoline) purchases or service stations
Other Shops Items that do not fall into other categories as
specified in this table
Other Travel All other travel related sales not already specified
in this table
Travel Agents Travel agencies including tour operators
Legal Services Legal services, including fines, bail and bonds
All Other S/Es Remaining types of purchases not already
included in this table

October 2019 Page 7-95

Fraud by Issuer and S/E Market

Report Usage The Fraud by Issuer and S/E Market report (Report ID FSG019)
gives an overview of the total value of fraudulent Transactions
reported by an Issuer, categorized by S/E Market. This report lets
Participants monitor Fraud trends by market. Fraud can take several
months to identify and report. Because the Network reports by
Transaction date, Fraud totals can change from month to month.
This report includes three months of data because of late reporting
and changing Fraud totals.

Frequency Monthly

Printing This report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the Fraud by Issuer and S/E
Market report are below.

Table 7-47. Fraud by Issuer and S/E Market: Definitions

Data Element Name Definition
IIN A unique number assigned to an Issuer by AEGNS.
IPN A unique number assigned to an Issuer processor by AEGNS.
S/E Market Service Establishment Market: the market in which the Fraud Transaction
occurred.
Fraud Amount Total amount of fraud (USD) reported by Issuers.
Number of Frauds Total number of fraud Transactions reported by Issuers.
Pct of Total The percentage this fraud amount represents for Cards issued by the
Issuer for the S/Es in this S/E market.
Totals The total of amounts for the entire report.

Page 7-96 October 2019

Fraud by Issuer and Industry

Report Usage The Fraud by Issuer and Industry report (Report ID FSG020) gives
an overview of the total value of fraudulent Transactions reported
by an Issuer, categorized and totaled by industry.
This report includes three months of data because of late reporting
and changing Fraud totals.

Frequency Monthly

Printing This report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the Fraud by Issuer and Industry
report are below.

Table 7-48. Fraud by Issuer and Industry: Definitions

Data Element Name Definition
IIN A unique number assigned to an Issuer by AEGNS.
IPN A unique number assigned to an Issuer Processor by AEGNS.
Industry The industry segment in which the fraud was reported. The Industry Cat-
egories on page 7-95 gives a list of these categories.
Fraud Amount Total amount of fraud (USD) reported by Issuer.
Number of Frauds Total number of fraud Transactions reported by Issuer.
Pct of Total The percentage this industry fraud amount represents for this industry,
included under this Issuer.
Totals The total of amounts for the entire report.

October 2019 Page 7-97

Fraud by Issuer, S/E Market, and Fraud Type

Report Usage The Fraud by Issuer, S/E Market, and Fraud Type report (Report ID
FSG021) gives an overview of the total value of fraudulent
Transactions reported by an Issuer, categorized and totaled by S/E
market and fraud type.
This report shows Fraud trends by market. Fraud can take several
months to identify and report. The reports are by Transaction date,
so fraud totals can change from month to month. This report
includes three months of data because of late reporting and
changing Fraud totals.

Frequency Monthly

Printing This report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the Fraud by Issuer, S/E Market
and Fraud Type report are below.

Table 7-49. Fraud by Issuer, S/E Market, and Fraud Type: Definitions
Data Element Name Definition
IIN A unique number assigned to an Issuer by AEGNS.
IPN A unique number assigned to an Issuer Processor by AEGNS.
S/E Market Service Establishment Market: the market in which the Fraud Transaction
occurred.
Fraud Type Type of fraud committed, categorized by the Issuer, based on fraud type
categories listed in the Fraud Type Codes section of the Codes Reference
Guide.
Fraud Amount Total amount of fraud (USD) reported by Issuer.
Number of Frauds Total number of fraud Transactions reported by Issuer.
Pct of Total The percentage this fraud amount represents for this fraud type, in this
S/E market, for Cards issued by the Issuer.
Totals The total of amounts for the entire report.

Page 7-98 October 2019

Issuer Gross Fraud Update

Report Usage The Issuer Gross Fraud Update report (Report ID Number FSG002)
displays fraud by type for each month, and compares figures
between the current year and the year before. Amount and
percentage variance columns are included, and the report is
sub-categorized by Issuer Identification Number (IIN) and
accumulated by issuing Participant.

Frequency Monthly

Printing This report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the Issuer Gross Fraud Update
report are below.

Table 7-50. Issuer Gross Fraud Update: Definitions

Data Element Name Definition
Participant’s Name / IIN The Participant name and the Issuer Identification Number of the report
recipient.
Month The total gross fraud amount in U.S. Dollars as reported for each month.
Current Year The total gross fraud amount in U.S. Dollars, listed by month as reported
for the current year.
Previous Year The total gross fraud amount in U.S. Dollars, listed by month as reported
for the year before.
$Variance Amount of variance between the current year and the year before during
the period of time represented in the sub-categories of fraud type.
% Variance Percent of variance between the current year and the year before during
the period of time represented in the sub-categories of fraud type.
YTD Year-to-date. Shows year-to-date data for the current year and the year
before.
Full Year Displays total of the year-to-date data for the current year and the full
year data for the year before.
All Fraud Types The total of all fraud classifications listed in the report.
S/E Fraud All fraud due to fraudulent S/E set-ups (also called fictitious S/Es) and
employees who committed fraud at the location of their employers.
Lost Card All fraud due to the use of a lost Card.

October 2019 Page 7-99

Issuer Fraud Summary

Report Usage The Issuer Fraud Summary report (Report ID Number FSG003)
displays the gross fraud, chargebacks, net fraud and
chargeback-to-gross fraud for the reported month and the
year-to-date. This report is sorted by fraud type and year.
Participants can compare overall fraud trends and net losses by
fraud type.

Frequency Monthly

Printing This report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the Issuer Fraud Summary
report are below.

Table 7-51. Issuer Fraud Summary: Definitions

Data Element Name Definition
Participant’s Name/ IIN The name and Issuer Identification Number of the report recipient.
Fraud Type The fraud classifications listed in the report (e.g., lost, stolen, MO/PO,
CNP, S/E, etc.).
Year Displays the previous and current reporting years.
Gross Fraud Total fraud reported by this Issuer.
Chargebacks Total chargebacks reported by this Issuer.
Net Fraud Total of gross fraud less chargebacks
Chargebacks to Gross Chargebacks divided by the total gross fraud
Fraud
MTD Month-to-date. Includes all data from the first day of the month through
the last day of the month, as shown in the report header, for the current
year and the year before.
YTD Year-to-date. Includes all data from January 1 through the last day of the
current month, as shown in the report header, for the current year and the
year before.
% Var Percent of variance between the current year and the year before for the
period of time shown in the sub-categories.
Lost Card All fraud due to the use of a lost Card.
MO/PO Mail Order/Phone Order. All fraud due to the use of mail, phone or Internet
orders in which merchandise was shipped.
CNP Card Not Present. All fraud when the Card is not present during an in-per-
son Transaction.

Page 7-100 October 2019

Table 7-51. Issuer Fraud Summary: Definitions (continued)

Data Element Name Definition
Non-Rcvd Non-Received. All fraud due to the use of a new or replacement Card
never received by the Cardmember.
S/E Fraud All fraud due to fraudulent S/E set-ups (also called fictitious S/Es) and
employees who committed fraud at the location of their employers.
Stolen All fraud due to the use of a stolen Card.
Altered Card All fraud due to physically or electronically changed Cards and counterfeit
Cards.
Fraud App All fraud because of a false Cardmember application. This includes stolen
or false identities and applicants that are not approved for more Cards.
Skimmed All data that was electronically captured from the magnetic stripe of a
valid Card and electronically encoded onto a Card that is not valid.

October 2019 Page 7-101

Non-Actioned Rejected Transaction Reports

Report Usage There are two monthly Non-Actioned Rejected Transaction Reports:
• Issuer Non-Actioned Rejected Transaction Report
• Acquirer Non-Actioned Rejected Transaction Report

Report The reports show rejected files and/or Transactions and are sorted
Components by message type Fraud Repository Update (9324) and S/E
Demographics Detail Data (9640).

Response File No response messages are used in the reporting. These rejected
files/Transactions are from the month before where no correcting
message has been received by the GNS Fraud Repository from the
Participant.
If all rejected files/records have been corrected and returned to the
GNS Fraud Repository, the report will display “No rejects pending
correction.”

Frequency The report is generated on the 10th of each month for the returned
files/records from the month before where no correcting file has
been submitted.

Optionality Mandatory

Certification No certification is required. Participants should test to make sure

they can receive and open the report.

Policy Impacts Issuers are required to resubmit rejected Transactions from the
Fraud Repository Update (9324).
To prevent possible penalties, the Non-Actioned Rejected
Transaction Report shows outstanding Transactions.

Report Delivery The applicable report is sent to the Participant through the Global
Online Business Exchange (GLOBE) report delivery function (9644).
It is also accessible through FraudNet in the Report View.

continued on next page

Page 7-102 October 2019

Definitions Definitions for each of the fields on the Issuer Non-Actioned

Rejected Transaction report are below.

Table 7-52. Non-Actioned Rejected Transaction Reports: Definitions

Data Element Name Definition
Month The month the Transactions were returned to the Participant. The
report is generated on the 10th of the month for the rejects from
the calendar month before.
IIN The unique number assigned by AEGNS to uniquely identify the
Card Issuer.
Name The name of the Issuer Participant as known to the public.
IPN The unique identification number assigned by the Network to the
designated Authorized Processor for an Issuer.
Name The name of the Issuer Authorized Processor as known to the pub-
lic.
File Seq # A sequential number given to each file by the file originator. This
ascending number starts at 000001 for the first file and increments
by one for all other files. When the number is 899999, the number
starts at 000001 for rejected files from the Clearing and Settle-
ment system.
This is the file sequence number from the first file that rejected or
contained rejected Transactions.
Network Processing Date The date that the Transaction was received and rejected/accepted
by the GNS Fraud Repository (GFR).
File Level Reject Yes (Y) or No (N) that shows if the reject was at the file level or if
the file was accepted but contained rejected Transactions.
Reject Code Reason(s) Up to ten four-byte fields that show the reason(s) for which a mes-
sage is rejected. Displayed is the four-digit reject reason code and
up to 40 bytes of description.
Refer to the Reject Reason Codes section of the Codes Reference
Guide for valid codes and their descriptions.
Reject Count Count corresponding with the File Level Reject indicator. If the indi-
cator is (Y) yes, and the file rejected, then the Reject Count is one
as the Transactions were not processed. If the File Level Reject is
(N) no, then the Reject Count contains the number of Transactions
that rejected in the accepted file.
Total Number of Rejected Files The number of files that rejected during the reporting period. The
Network cannot determine if the files have been corrected and
resubmitted at the file level.
Total Number of Rejected The total number of Transactions that rejected during the reporting
Transactions Pending Correc- period which have not been corrected and resubmitted.
tions

continued on next page

October 2019 Page 7-103

Definitions Definitions for each of the fields on the Acquirer Non-Actioned

Rejected Transaction report are below.

Table 7-53. Non-Actioned Rejected Transaction Reports: Definitions

Data Element Name Definition
Month The month the Transactions were returned to the Participant. The
report is generated on the 10th of the month for the rejects from
the month before.
AIN The unique identification number assigned to an Acquirer by
AEGNS.
Name The name of the Acquirer as known to the public.
APN The unique identification number assigned by AEGNS to the desig-
nated Authorized Processor for an Acquirer.
Name The name of the Acquirer Authorized Processor as known to the
public.
File Type Text representing the message type received. For example,
SEDEMO displays when the 9640 S/E Demographics Details mes-
sage was received.
File Seq # A sequential number assigned to each file by the file originator.
This ascending number starts at 000001 for the first file and incre-
ments by one for all other files. When the number is 899999, the
number starts at 000001 for rejected files from the Clearing and
Settlement system.
This is the file sequence number from the first file that rejected or
contained rejected Transactions.
Network Processing Date The date that the Transaction was received and rejected/accepted
by the GNS Fraud Repository (GFR).
File Level Reject Yes (Y) or No (N) that shows if the reject was at the file level or if
the file was accepted but contained rejected Transactions.
Reject Code Reason(s) Up to ten four-byte fields that show the reason(s) for which a mes-
sage is rejected. Displayed is the four-digit reject reason code and
up to 40 bytes of description.
Refer to the Reject Reason Codes section of the Codes Reference
Guide for valid codes and their descriptions.
Reject Count Count corresponding with the File Level Reject indicator. If the indi-
cator is (Y) yes, and the file rejected, then the Reject Count is one
as the Transactions were not processed. If the File Level Reject is
(N) no, then the Reject Count contains the number of Transactions
that rejected in the accepted file.

Page 7-104 October 2019

Table 7-53. Non-Actioned Rejected Transaction Reports: Definitions (continued)

Data Element Name Definition
Total Number of Rejected Files The number of files that rejected during the reporting period. The
Network cannot determine if the files have been corrected and
resubmitted at the file level.
Total Number of Rejected The total number of Transactions that rejected during the reporting
Transactions Pending Correc- period which have not been corrected and resubmitted.
tions

October 2019 Page 7-105

Fraud by Acquirer and Cardmember Market

Report Usage The Fraud by Acquirer and Cardmember Market report (Report ID
FSG022) gives an overview of the total value of fraudulent
Transactions reported at an Acquirer’s S/Es, categorized and totaled
by Cardmember market, enabling monitoring of Fraud trends by
market.

Fraud Monthly Fraud can take several months to identify and report. Fraud is
Totals reported by Transaction date and fraud totals can change from
month to month. This report includes three months of data because
of late reporting and changing Fraud totals.

Frequency Monthly

Printing This report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the Fraud by Acquirer and
Cardmember Market report are below.

Table 7-54. Fraud by Acquirer and Cardmember Market: Definitions

Data Element Name Definition
AIN A unique number assigned to an Acquirer by AEGNS.
APN A unique number assigned to an Acquirer Processor by AEGNS.
CM Market Cardmember Market: the market in which the Cardmember’s Issuer is
located.
Fraud Amount Total amount of fraud (USD) reported by Issuer.
Number of Frauds Total number of fraud Transactions reported by Issuer.
Pct of Total The percentage this fraud amount represents for Cards issued in this
Cardmember market, at the Acquirer’s S/E.
Total The total of amounts for the entire report.

Page 7-106 October 2019

Fraud by Acquirer and Industry

Report Usage The Fraud by Acquirer and Industry report (Report ID FSG023)
gives an overview of the total value of fraudulent Transactions
reported at an Acquirer’s S/Es, categorized and totaled by Industry.
This report enables monitoring of Fraud trends by market.

Frequency Monthly

Printing The report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the Fraud by Acquirer and
Industry report are below.

Table 7-55. Fraud by Acquirer and Industry: Definitions

Data Element Name Definition
AIN A unique number assigned to an Acquirer by AEGNS.
APN A unique number assigned to an Acquirer Processor by AEGNS.
Industry The industry segment in which the fraud was reported. Refer to the
Industry Categories on page 7-95.
Fraud Amount Total amount of fraud (USD) reported by Issuer.
Number of Frauds Total number of fraud Transactions reported by Issuer.
Pct of Total Percent of Total: the percentage this fraud amount represents for this
industry at the Acquirer’s S/Es.
Totals The total of amounts for the entire report.

October 2019 Page 7-107

Fraud by Acquirer, Cardmember Market, and Fraud Type

Report Usage The Fraud by Acquirer, Cardmember Market and Fraud Type report
(Report ID FSG024) gives an overview of the total value of
fraudulent Transactions reported at an Acquirer’s S/Es, categorized
and totaled by Cardmember market and fraud type. This report
enables monitoring of Fraud trends by market.

Frequency Monthly

Printing The report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the Fraud by Acquirer,

Cardmember Market and Fraud Type report are below.

Table 7-56. Fraud by Acquirer, Cardmember Market, and Fraud Type: Definitions

Data Element Name Definition

AIN A unique number assigned to an Acquirer by AEGNS.
APN A unique number assigned to an Acquirer Processor by AEGNS.
CM Market Cardmember Market: the market in which the Cardmember’s Issuer is
located.
Fraud Type Type of fraud committed based on fraud type categories. Reported fraud
is categorized by the Issuer.
Fraud Amount Total amount of fraud (USD) reported by Issuer.
Number of Frauds Total number of fraud Transactions reported by Issuer, categorized by
Acquirer, Cardmember market and fraud type.
Pct of Total Percent of Total: the percentage this fraud amount represents for this
fraud type, for Cards issued in this Cardmember market, at the
Acquirer’s S/Es.
Total The total of amounts for the entire report.

Page 7-108 October 2019

Acquirer S/E Fraud Summary Report

Report Usage The Acquirer S/E Fraud Summary Report gives Acquirers a list of
the S/Es in their market that have fraudulent Transactions, as
reported by Issuers on the Network. This report is sorted by
Acquirer Identification Number (AIN) and then by S/E Number.

Frequency The report is sent 2 times a month:

• On the first of the month, the report shows the volume from the
prior calendar month.
• On the 16th of the month, the report shows the volume from the
first 15 days of the current month.

Printing The report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the Acquirer S/E Fraud
Summary Report are below.

Table 7-57. Acquirer S/E Fraud Summary Report: Definitions

Data Element Name Definition
S/E Number The identification number of a person that has a contract with an Acquirer
where such entity lets a Cardmember charge Goods and Services at or
from such entity with the Card and transfer such Charges to an Acquirer.
S/E Name The name of the S/E as it is reported by the Acquirer.
S/E Country The name of the Card Acceptor’s country.
Gross Fraud Count The number of fraud Transactions reported for an S/E by Network Issuers.
Gross Fraud Amount The dollar amount in U.S. Dollars of the fraud Transactions reported by all
Network Issuers for an S/E.
Gross Fraud Average The average amount of gross fraud based on the Gross Fraud Amount
divided by the Gross Fraud Count.
Chargebacks Count The number of Transactions (from the Transactions included in the report)
that were charged back by Issuers.
Chargebacks Average The average amount of Chargebacks based on the chargeback amount
divided by the Chargeback Count.
Net Fraud Count The number of fraud Transactions reported by all Issuers, based on Gross
Fraud Count minus Chargeback Count.
Net Fraud Amount The dollar amount for fraud Transactions reported by all Issuers, based on
Gross Fraud Amount minus chargeback amount.
Net Fraud Average The average fraud dollar amount, based on Gross Fraud Average minus
Chargeback Average.

October 2019 Page 7-109

Table 7-57. Acquirer S/E Fraud Summary Report: Definitions (continued)

Data Element Name Definition
Fraud to Gross Percentage representing the total fraud for the sales during a specific time
frame.

Page 7-110 October 2019

Acquirer S/E Fraud Detail Report

Report Usage The Acquirer S/E Fraud Detail Report supplies Acquirers with each
fraud Transaction reported for a specific time frame for an S/E. This
report is sorted by Acquirer Identification Number (AIN) and then
by S/E Number. Total Amount, Total Record Of Charge (ROCs), and
Avg. Amount for the same time frame are shown at the end of each
S/E listing.

9344 Message The data from the Acquirer S/E Fraud Detail Report is also available
from the Acquirer S/E Fraud Detail (9344) message automatically
sent to an Acquirer through the use of the Program Specific
message (9344) 2 times a month. The Acquirer can import the data
into their fraud prevention system(s). Refer to the Program Specific
Data Collection (9344) and the Acquirer S/E Fraud Detail (9344)
messages for more instruction.

Frequency The report and Acquirer S/E Fraud Detail (9344) message are sent
2 times a month:
• On the first of the month, the report and message show the
volume from the prior calendar month.
• On the 16th of the month, the report and message show the
volume from the first 15 days of the current month.
Acquirers must receive these reports and messages.
Note: If there is no fraud reported for an S/E, the S/E is not
included in the report and message.

Printing The report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the Acquirer S/E Fraud Detail
Report are below.

Table 7-58. Acquirer S/E Fraud Detail Report: Definitions

Data Element Name Definition
S/E Number The identification number of a person that has a contract with an Acquirer
where such entity lets a Cardmember charge Goods and Services at or
from such entity with the Card and transfer such Charges to an Acquirer.
S/E Name Card Acceptor Name. The name of the S/E as it is reported by the
Acquirer.
S/E Country The name of the Card Acceptor’s country.

October 2019 Page 7-111

Table 7-58. Acquirer S/E Fraud Detail Report: Definitions (continued)

Data Element Name Definition
Account Number (Pri- A series of digits used to identify a customer Account or relationship. The
mary Account Number) assigned number identifies the Issuer and Cardmember and is composed
of an Issuer identifier and an accompanying check digit. The account num-
ber can be embossed onto the plastic, is encoded into the magnetic stripe,
and printed on the back of a Card.
USD Amount Total Amount of the fraud Transaction in U.S. Dollars.
Frd Rpt Dt The date when the fraud Transaction was reported to the GNS Fraud
Repository by the Network Issuer.
Charge Date The local date when the fraud Transaction was executed at a Card Accep-
tor location. If mail order or telephone order, it is the date the goods were
shipped.
Fraud Type The type of fraud reported and put into the GNS Fraud Repository. Refer to
the “Fraud Types Codes” section in the Codes Reference Guide for valid
codes, associated names and abbreviations, and their descriptions.
S/E Total Amount The total reported fraud for an S/E in U.S. Dollars.
S/E Total ROCs The total ROCs (Record Of Charge) for an S/E that make up the fraud on
this report.
S/E Avg Amount The average fraud amount for an S/E, based on the S/E Total Amount
divided by the S/E Total ROCs.
AIN Total Amount The total reported fraud for an AIN in U.S. Dollars.
AIN Total ROCs The total ROCs for an AIN that make up the fraud on this report.
AIN Avg Amount The total reported fraud for an AIN in U.S. Dollars.

Page 7-112 October 2019

Top 40 S/Es 6 Month Summary Report

Report Usage The Top 40 S/Es 6 Month Summary Report shows Acquirers the 40
S/Es in their market that have the highest gross fraud, as reported
by Issuers on the Network. The Top 40 S/Es 6 Month Summary
Report is sorted by Acquirer Identification Number (AIN) and then
by S/E Number.

Frequency The report is sent every six months.

Printing The report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields on the Top 40 S/Es 6 Month
Summary Report are below.

Table 7-59. Top 40 S/Es 6 Month Summary Report: Definitions

Data Element Name Definition
S/E Number The identification number of a person that has a contract with an Acquirer
where such entity lets a Cardmember charge Goods and Services at or
from such entity with the Card and transfer such Charges to an Acquirer.
S/E Name The name of the S/E as it is reported by the Acquirer.
Gross Fraud Count The number of fraud Transactions reported for an S/E by Network Issuers.
Gross Fraud Amount The dollar amount in U.S. Dollars of the fraud Transactions reported by all
Network Issuers for an S/E.
Gross Fraud Average The average amount of gross fraud based on the Gross Fraud Amount
divided by the Gross Fraud Count.
Chargebacks Count The number of Transactions (from the Transactions included in the report)
that were charged back by Issuers.
Chargebacks Average The average amount of Chargebacks based on the chargeback amount
divided by the Chargeback Count.
Net Fraud Count The number of fraud Transactions reported by all Issuers, based on Gross
Fraud Count minus Chargeback Count.
Net Fraud Amount The dollar amount for fraud Transactions reported by all Issuers, based on
Gross Fraud Amount minus chargeback amount.
Net Fraud Average The average fraud dollar amount, based on Gross Fraud Average minus
Chargeback Average.

October 2019 Page 7-113

Top 40 S/Es 6 Month Detail Report

Report Usage The Top 40 S/Es 6 Month Detail Report supplies Acquirers with each
fraud Transaction reported for a six month timeframe of the 40 S/Es
in their market that have the highest gross fraud, as reported by
Issuers on the Network. This report is sorted by Acquirer
Identification Number (AIN) and then by S/E Number. Total Amount,
Total Record Of Charge (ROCs), and Avg. Amount are shown at the
end of each S/E listing.

Amount Totals All amount and totals on the report come from the Transactions that
are in the six month timeframe of the report.

Frequency The report is sent every six months.

Printing The report is designed to be printed in a landscape orientation.

Definitions Definitions for each of the fields in the Top 40 S/Es 6 Month Detail
Report are below.

Table 7-60. Top 40 S/Es 6 Month Detail Report: Definitions

Data Element Name Definition
S/E Number The identification number of a person that has a contract with an Acquirer
where such entity lets a Cardmember charge Goods and Services at or
from such entity with the Card and transfer such Charges to an Acquirer.
Account Number (Pri- A series of digits used to identify a customer Account or relationship. The
mary Account Number) assigned number identifies the Issuer and Cardmember and is composed
of an Issuer identifier and an accompanying check digit. The account num-
ber can be embossed onto the plastic, is encoded into the magnetic stripe,
and printed on the back of a Card.
USD Amount Total Amount of the fraud Transaction in U.S. Dollars.
Frd Rpt Dt The date when the fraud Transaction was reported to the GNS Fraud
Repository by the Network Issuer.
Charge Date The local date when the fraud Transaction was executed at a Card Accep-
tor location. If mail order or telephone order, it is the date the goods were
shipped.
Fraud Type A description that identifies the type of fraud assigned by the Issuer.
S/E Total Amount The total reported fraud for an S/E in U.S. Dollars.
S/E Total ROCs The total ROCs (Record Of Charge) for an S/E that make up the fraud on
this report.
S/E Avg Amount The average fraud amount for an S/E, based on the S/E Total Amount
divided by the S/E Total ROCs.

Page 7-114 October 2019

Section 5 OpsNet Reports

OpsNet Reports

Overview Please refer to the OpsNet Users Guide for instruction about OpsNet
report.

October 2019 Page 7-115

Page 7-116 October 2019

Chapter 8 Instruction Documents

More Instruction

Overview These resources are referenced in this document:

1. The American Express Acquirer Chip Card Implementation
Guide
2. The American Express Expresspay Card Specification
3. The American Express Expresspay Card Specification Dual Interface
Addendum
4. The American Express Expresspay Communication Layer
5. The American Express Expresspay Terminal Specification
6. The American Express Issuer Chip Card Implementation Guide
7. The American Express Global Network Services AEIPS Chip
Card Specification manual
8. The American Express Global Network Services AEIPS Terminal
Technical Manual
9. The American Express Hardware Security Module (HSM) Func-
tion Requirements
10. The Business and Operational Policies manual
11. The American Express Global Network Services Codes Refer-
ence Guide
12. The International Organization for Standardization (ISO), ISO
8583, Financial Transaction card originated message –- Inter-
change message specifications
13. The International Organization for Standardization (ISO),
ISO/IEC 7811-2, Identification cards -- Recording technique --
Part 2: Magnetic stripe
14. The International Organization for Standardization (ISO),
ISO/IEC 7811-3, Identification cards -- Recording technique --
Part 3: Location of embossed characters on ID-1 cards, Second
Edition 1995
15. The International Organization for Standardization (ISO),
ISO/IEC 7813, Information technology -- Identification cards
-- Financial Transaction cards
16. International Air Transport Association, IATA Airline Coding
Directory, Forty-Seventh Edition, Effective August 1, 1998

continued on next page

October 2019 Page 8-1

17. American Express SafeKey Protocol Specification

18. American Express SafeKey MPI Functional Requirements
19. American Express SafeKey ACS Functional Requirements
20. American Express SafeKey Acquirer - Merchant Implementa-
tion Guide
21. American Express SafeKey Issuer Implementation Guide
22. American Express SafeKey 2.0 Protocol Specification
23. American Express SafeKey 2.0 Acquirer-Merchant Implemen-
tation Guide
24. American Express SafeKey 2.0 Issuer Implementation Guide
25. Online PIN Processing Implementation Guide
Knowledge Base ([Link]/knowledgebase)
contains all Participant documentation. Use the Search function to
locate these documents.

Page 8-2 October 2019

Chapter 9 Acronyms

Acronyms
Acronyms

Acronym Meaning

3CSC 3-digit Card Security Code

4CSC 4-digit Card Security Code

4DBC 4-Digit Batch Code

5CSC 5-digit Card Security Code

AAV Automated Address Verification

ACS Access Control Server

AEGN American Express Global Network

AEGNS American Express Global Network Services

AEIPS American Express Integrated Circuit Card Payment Specifications

AEVV American Express Verification Value

AIN Acquiring Institution Number (Acquiring Institution Identification)

AIP Application Interchange Profile

AMEX American Express

AML Anti-Money Laundering

AN Alphanumeric

APN Acquiring Institution Processor

APR Annual Percentage Rate

ARN Acquirer Reference Number

ARPC Authorization Response Cryptogram

ARQC Authorization Request Cryptogram

ASCII American Standard Code Information Interchange

ATC Application Transaction Counter

ATM Automated Teller Machines

BIN Bank Identification Number

CAD Card Acceptor Device

CAS Credit Authorizations System

CAT Customer Activated Terminals

CID Card Identification Number

October 2019 Page 9-1

Acronyms (continued)

Acronym Meaning

CM Card Member

CNP Card Not Present

CPC Corporate Purchasing Card

CRIT Criteria Table

CSC Card Security Code

CSCK Card Security Code Key

CVM Cardholder Verification Methods

CVR Cardholder Verification Results

DAF Daily Activity File

DAP Daily Activity Process

DAR Daily Activity Report

DBA Doing Business As

DFMNS Dynamic Fraud Management Network Services

DPP Differred Payment Plan

EBCDIC Extended Binary Coded Decimal Interchange Code

ECI Electronic Commerce Indicator

ECR Emergency Card Replacement

EEA European Economic Area

EMV Europay, MasterCard/Visa and American Express

EU European Union

FAS Funds Access System

FLS Fraud Liability Shift

FP First Presentment

FSN File Sequence Number

GAN AR Gobal Authorization Nework Alternate Routing

GFR GNS Fraud Repository

GLOBE Global Online Business Exchange

GNS Global Network Services

GNSAS Global Network Services Authorization System

HRSE High Risk Service Establishment

HSM Hardware Security Module/Host Security Module

IAD Issuer Application Data

IATA International Air Transportation Association

Page 9-2 October 2019

Acronyms (continued)

Acronym Meaning

ICC Integrated Circuit Card

iCSC Integrated Printed Card Security Code

ID Identification / Identifier

IIN Issuer Identification Number

IP Internet Protocol

IPN Issuer Processor Number

ISO International Organization for Standardization

KSO Key Signing Officer

LLLVAR Three-Digit Variable Length Indicator

LLVAR Two-Digit Variable Length Indicator

LRC Longitudinal Redundancy Check

MCC Merchant Category Codes

MNA Multinational Account

MR Membership Rewards

MST Magnetic Secure Transmission

NTS Network Test Simulator

OTP One-Time Password

PAN Primary Account Number

PCI Payment Card Industry

PCSC Printed Card Security Code

PIN Personal Identification Number

POS Point Of Sale

ROC Record Of Change

SE (S/E) Service Establishment

TAT Transit Access Terminal

TID Transaction Identifier

TRID Token Requestor ID

TVR Terminal Verification Results

VIP Very Important Person

VLI Variable Length Indicator

ZCV ZIP Code Verification

October 2019 Page 9-3

Page 9-4 October 2019

Chapter 10 Definitions

Definitions

Overview The definitions in this chapter apply to the Network Specifications -

Authorization, Network Specifications - Financial/Non-Financial, Network
Specifications - Instructions, and the Codes Reference Guide.

Definitions

30 Day Balance Transactions billed to the Cardmember that are 30 days past due.

4 Digit Batch Code (4DBC) A 4-digit number printed on the Card (4DBC/4CSC).

60 Day Balance Transactions billed to the Cardmember that are 60-89 days past due.

90 Day Balance Transactions billed to the Cardmember that are 90 or more days past due.

AAV Response Code See, Automated Address Verification (AAV) Response Code (for future use).

Accepted Hash Total Amount Hash Transaction amount from all Presentments and Chargebacks accepted
by the Network.

Accepted Total Count Total number of messages accepted by the Network including File Header,
File Trailer, Presentments, Addenda Records, Chargebacks, and Retrieval
Request Notification messages.

Access Control Server The Access Control Server is a component of SafeKey that operates in the
Issuer domain. It verifies whether authentication is available for a Card
number and performs Payer Authentication for given Transactions.

Account An account established by an Issuer with a Person upon the issuance of one
(1) or more Cards.

Account Status Check A message sent by an Acquirer to verify the account status of the
Cardholder number.

Acquirer Any entity (including, without limitation, American Express and American
Express Entities) authorized by American Express or an American Express
Entity to engage in the Merchant Acquiring Business.

October 2019 Page 10-1

Definitions (continued)

Acquirer DPP Authorization This is the deferred payment plan data for the Acquirer Deferred Payment
Plan.

Acquirer Reference Data, This unique number is given by the Network and follows a Transaction
Transaction Identifier (TID) during its life cycle.

Acquirer Reference Number A unique number assigned by the Acquirer. It contains data supplied by an
(ARN) Acquirer and used by an Acquirer to match Transactions.

Acquirer S/E Fraud Detail The Acquirer S/E Fraud Detail (9344) message gives Acquirers a list of the
(9344) S/Es in their market with fraudulent Transactions, as reported by Issuers on
the Network. This allows Acquirers to see fraud trends that start in their S/E
Base.

Acquirer Settlement Amount The settlement amount calculated for an individual Transaction, net of the
Network rate, in the currency defined by the Acquirer’s contractual
agreement.

Acquirer Settlement Currency The numeric currency code of the Settlement Amount.
Code

Acquirer Settlement The number of places the decimal must be moved to the left to correctly
Decimalization represent the Acquirer Settlement Amount.

Acquirer/Issuer Amount The per Transaction amount, based on a standard rate that the Acquirer and
Issuer negotiate with AEGNS.

Note: Debit and credit amounts can net to zero; therefore, zeros can be a
valid value for this field.

Acquiring Institution This is a unique identification code given to an Acquirer by the Network.
Identification (AIN) Code

Acquiring Institution The unique identification number assigned by AEGNS to the designated
Processor Identifier (APN) Authorized Processor for an Acquirer.

Action Code The type of action done or the type of action to do for a Transaction.

Active Effective Date The date the Service Establishment was placed in an active status.

Actual Total Amount Hash Transaction amount from all accepted and rejected Presentments and
Chargebacks received by the Network.

Page 10-2 October 2019

Definitions (continued)

Actual Total Count The total number of all financial messages, including Presentments and
Chargebacks, accepted by the Network.

Automated Address A message option that allows an S/E to verify the Cardmember address
Verification information.

Addenda Type Code A specific type of addendum message.

Additional AEVV Information More data that Issuer or ACS operators may be required to supply for
problem tracking and dispute resolution. The field includes the ACS Version,
Authentication Action, and Cardmember IP Address.

Additional Amount 1-5 The amount for which a specific data element has not been defined on the
Presentment message due to the amount being specific to a particular
market or region, or specific to a type of Transaction addendum.

Additional Amount Accounting A code that indicates the accounting effect of the corresponding additional
Effect Type Code 1-5 amount field on a Presentment message or Transaction.

Additional Amount Type 1-5 A code that classifies the type of another amount in the Additional Amount
fields of the Presentment Message. Examples of amount types include
No-Show Reservation Transactions, meal, beverage, and tip amounts from
a restaurant charge addendum, or local tax on a First Presentment
message.

Additional Insurance Policy An insurance policy number that is associated with another policy number.
Number

Additional Reference Number A number assigned by the Acquirer to assist in locating/retrieving source
data and documentation.

Additional Response Data This field contains the Issuer response to address verification requests or
PCSC validation requests in the POS Authorization Request (1100)
message.

AEGNS Issuer BIN Number A number assigned by AEGNS to uniquely identify the Issuer of American
Express cards.

The first six bytes of the Cardmember’s for their American Express Card are
the Bank Identifier Number (BIN) for the Issuer. During the Participant
Setup process, specific Card products can be differentiated using bytes 7
and 8 of this field.

October 2019 Page 10-3

Definitions (continued)

AEVV Authentication Results From the ACS authentication decision, adapted from the SafeKey Payer
Code Authentication Response.

AEVV ID A constant literal = AEVV

AEVV Key Indicator An indicator as determined by keys loaded by the ACS. Permissible values
for a standard ACS are 01 and 02. Attempts ACS may use values 01-99.

AEVV Validation Result Supplied by the Authorization process to identify that the Issuer has
validated the AEVV.

Airline Document Number The form number of an airline document (e.g., a ticket, refund receipt,
etc.).

Airline Document Parts The number of parts in an airline document (e.g., a multi-part document
has two or more parts).

Airline Industry Specific Detail The Airline Industry Specific Detail Addendum message fields contain more
(9240/9340) data for an Airline Transaction. If the Format Code included in the 1240
Presentment message is 01, the Airline addendum must be submitted with
the Presentment.

Each First and Second Presentment can have multiple addenda records, but
can have only one Industry Specific Detail Addendum record.

Airline Invoice Number The invoice number for an airline ticket Transaction.

Airport Code The IATA Travel Point code of the airport in which the device (ATM) is
located.

Alternate Card Acceptor A Card Acceptor identification number used internally by a Participant.
Identification Code

Alternate Card Acceptor The number of positions or length of the Alternate Card Acceptor
Identification Code Length Identification Code.

American Express Global The aggregate of S/Es that accept Cards and the operational, service
Network (AEGN) or Network delivery, systems, and marketing infrastructure that supports them and the
American Express Brand.

American Express Global The business division of American Express responsible for managing the
Network Services (AEGNS) business relationship with Acquirers and Issuers which operate pursuant to
a license from an American Express Entity.

Page 10-4 October 2019

Definitions (continued)

American Express MNA Y (yes) or N (no) flag that indicates if this Service Establishment (S/E) is an
Indicator American Express Multinational Account (MNA).

American Express SafeKey® See SafeKey.

American Express Verification Contains a cryptographic value derived by the Issuer during authentication.
Value (AEVV) It can give evidence of the results of payment authentication during an
online purchase.

Amount Authorized The authorized Transaction amount sent from the terminal to the Card.

Amount Indicator Shows the Participant Net Settlement Amount for a transaction or group of
Transactions as a debit, credit, or zero.

Amount of Installment The amount of the installment in the currency and decimalization of the
Transaction Amount. It is the base installment amount including prorated
tax and tips plus applicable finance charge.

Amount Other A secondary amount associated with the Transaction. It represents a cash
back amount.

Amount Plus Finance Charges The total amount plus finance charge to be paid for the purchase.

Amount Requested The requested amount of the ATM Transaction in the local currency.

Amount, Additional The available amount of funds in the Card currency remaining on a Prepaid
Card for a Transaction executed by an S/E participating in the Prepaid
Authorization feature.

Amount, Original The original Transaction amount requested when a partial amount is
approved in a Prepaid Authorization request on a Prepaid Card.

Amount, Original (1120, 1220, The original Transaction amount from the POS Authorization Response
1230 Messages) (1110).

Amount, Original (ATM) The original authorization amount on the ATM Transaction Request (1200)
message. This field is used with the ATM Reversal Advice (1420) message.

October 2019 Page 10-5

Definitions (continued)

Amount, Reconciliation This is the total amount of the Transaction after the Network changes the
Amount, Transaction (Bit 4) to the Issuer’s currency (Bit 50). The Network
sends this amount to the Issuer.

Amount, Reconciliation This is the total amount of the provisioning request after the Network
(Provisioning) changes the Amount, Transaction (Bit 4) to the Issuer’s currency (Bit 50).

Amount, Transaction The POS sale or credit amount of the Transaction in the currency used at
the Card Acceptor location.

Amount, Transaction (ATM) The cash amount at an ATM terminal.

Amount, Transaction The sale or credit amount of the provisioning request.

(Provisioning)

ANSI X4.16 Track 1 Layout ANSI X4.16 Track 1 holds a maximum of 61 bytes. Two bytes are:
• Start Sentinel
• End Sentinel

POS applications strip these 2 fields and send only the 59 bytes of data
between the sentinels.

Other messages send the data between the sentinels (59 bytes) plus the
2-digit variable length indicator (LLVAR) to make a total of 61 bytes of data.

Special ANSI X4.16 Track 1 Data format definitions are in each message
that has an ANSI X4.16 Track 1 Data field.

ANSI X4.16 Track 2 Layout ANSI X4.16 Track 2 holds a maximum of 31 bytes. Two bytes are:
• Start Sentinel
• End Sentinel

POS applications strip these 2 fields and send only the 29 bytes of data
between the sentinels.

Other messages send the data between the sentinels (29 bytes) plus the
two-digit variable length indicator (LLVAR) to make a total of 31 bytes of
data.

Special ANSI X4.16 Track 2 Data format definitions are in each message
that has an ANSI X4.16 Track 2 Data field.

Anticipated Transaction The anticipated date of settlement for a deferred Transaction. This
Settlement Date Transaction has been warehoused for a future settlement date.

Application Cryptogram This is the cryptogram generated by the ICC in response to the GENERATE
AC Command.

Page 10-6 October 2019

Definitions (continued)

Application Interchange Indicates the capabilities of the Chip Card to support specific functions of
Profile (AIP) the application to be taken into consideration by the Terminal when
determining how to process the Transaction.

Application PAN Sequence This value identifies and differentiates a Card application with the same
Number (PAN).

Application Transaction The counter maintained by the application in the Card.

Counter (ATC)

Approval Code A unique code assigned by the card Transaction authorizing institution to
indicate the disposition for the Transaction.

Approval Code (Provisioning) A unique code assigned by the card provisioning request authorizing
institution to indicate the disposition for the provisioning request.

Approval Code Length The length of the approval code (Field 29) for a Transaction.

Arbitration The procedure used to resolve issues between Acquirers and Issuers
regarding Network policies and determine responsibility for the disputed
item.

ARPC Response Code The Authorization Response Cryptogram (ARPC) code used during ARPC
computation and used by the Chip Card to validate the ARPC during Issuer
Authentication (External Authentication Command), EMV Tag “8A.”

Arrival Class of Service 1-4 Assigned by the Carrier that corresponds to the fare class (e.g. A, B, etc.) in
the class of service (e.g., First Class) applicable to this travel segment.

Arrival Rail Station Name 1-4 The name of the rail station’s location associated with a rail ticket purchase.

ATM Acquirer An American Express Entity or other Person authorized by an American

Express Entity to acquire Transactions by Cardmembers at ATMs.

ATM Additional Amouint Type A code that classifies the type of another amount in the Additional Amount
1-5 fields of the Presentment Message.

ATM Fees (1740/1742) The Network assesses and settles ATM Fees. The fees are sent to the
Participant in the ATM Fees (1740-1742) message.

The 1740 message is sent to an Issuer.

The 1742 message is sent to an Acquirer.

October 2019 Page 10-7

Definitions (continued)

ATM Financial Transaction Use this message to request authorization to dispense funds from an
Request (1200) Automated Teller Machine (ATM).

ATM Financial Transaction Use this message to respond to an ATM Financial Transaction Request
Response (1210) (1200) message.

ATM First and Second The American Express Funds Access System (FAS) creates the ATM First
Presentment (1240) Presentments from the data of one Cardmember Transaction in the ATM
Financial Transaction Request (1200). The ATM First Presentment is sent to
the Network. The Network sends the ATM First Presentment (1240)
message to the Issuer.
ATM First Presentments are not outcleared by Acquirers to the Network.
ATM Second Presentments outclear from the Acquirer to the Network and
Inclear from the Network to the Issuer. In the outclear and inclear columns,
the optionality is defined for the outclear and inclear files.

ATM Location List (9344) Participants use the ATM Location List message to tell Cardmembers of the
physical location of a Participant’s ATM device.

ATM Reconciliation Header The File Header is the first data record in the file and serves as the highest
Record level of control in a file. Each file can have only one File Header Record.

ATM Reconciliation Trailer The file trailer is the last data record in the file. It includes control totals
Record used to evaluate the integrity of the file. The forwarding institution creates
the file trailer for the file.

ATM Record Message The ATM record contains data pertaining to a single Cardmember
Transaction. This includes the account number, reference code, amount,
and more data required by the Acquirer to reconcile the account.

ATM Reversal Advice (1420) Acquirers can use the ATM Reversal Advice (1420) message to advise
Issuers of a disposition change for a Transaction.

ATM Reversal Advice Response The Network uses this message to acknowledge the receipt of the ATM
(1430) Reversal Advice (1420) message. It does not mean that exposure on the
account has been reversed.

ATM Transaction A Transaction conducted at an ATM, initiated with a PIN, for any financial
transaction, account inquiry, or PIN management.

Authentication Results Code The result of the American Express SafeKey authentication from the ACS in
the AEVV.

Authentication Tracking A 16-digit number generated by the ACS to identify the Transaction.
Number

Page 10-8 October 2019

Definitions (continued)

Authorization Response The cryptogram computed by the Issuer that is returned to the Chip Card to
Cryptogram (ARPC) enable the Card to perform Issuer Authentication.

Authorization Status Indicates if the Issuer approved the authorization request for the
Transaction.

Authorization An S/E seeking approval for a Transaction.

Authorized Processor A third-party company to the extent that it has been engaged by an
Acquirer or Issuer, and certified by AEGNS to perform processing services
on behalf of the Acquirer or Issuer.

Auto Rental Agency Name Rental agency or automobile rental chain name that is on the storefront
and/or customer receipt. Must be easily recognized by the Cardmember.

Auto Rental Agreement Invoice number of the rental agreement (issued by the rental agency) that
Number is signed by the Cardmember.

Auto Rental Audit Adjustment The amount of charge adjustments related to a rental automobile contract
Amount after the vehicle was checked in.

Auto Rental Audit Adjustment Indicates an adjustment was made to a rental automobile charge. The
Indicator Cardmember was notified of the adjustment (e.g., for damage, mileage,
gas, etc.). Refer to the Auto Rental Audit Adjustment Indicator section of
the Codes Reference Guide for a complete list of codes and descriptions.

Auto Rental City Name The city, town, or village where an automobile was rented.

Auto Rental Class Code Indicates the classification of the rental vehicle. Refer to the Auto Rental
Class Code section of the Codes Reference Guide for a complete list of
codes and descriptions.

Auto Rental Country Code The Country Code of the country where an automobile was rented. Refer to
the Country Codes section of the Codes Reference Guide for a complete list
of codes and descriptions.

Auto Rental Distance The distance traveled during the rental period.

Auto Rental Distance Unit of The unit measure of the distance driven during the rental period.
Measure

October 2019 Page 10-9

Definitions (continued)

Auto Rental Industry Specific The Auto Rental Industry Specific Detail message fields contain more data
Detail (9240/9340) for an auto rental Transaction. If the Format Code included in the 1240
Presentment message is 05, the Auto Rental addendum must be submitted
with the Presentment.
Each First and Second Presentment can have multiple addenda records, but
can have only one Industry Specific Detail Addendum record.

Auto Rental Pickup City Name The city, town or village from where a rental automobile was picked up.

Auto Rental Pickup Country The Country Code of the country where a rental automobile was picked up.
Code Refer to the Country Codes section of the Codes Reference Guide for a
complete list of codes and descriptions.

Auto Rental Pickup Date The date a rental automobile was picked up.

Auto Rental Pickup Region A code identifying the state, province or region where a rental automobile
Code was picked up. Refer to the Region Codes section of the Codes Reference
Guide for a complete list of codes and descriptions.

Auto Rental Pickup Time The time a rental automobile was picked up.

Auto Rental Region Code A code identifying the state, province or region where the automobile was
rented. Refer to the Region Codes section of the Codes Reference Guide for
a complete list of codes and descriptions.

Auto Rental Renter Name The name of the person who rented the automobile. This is usually the
Cardmember name, but it could be different.

Auto Rental Return City Name The city, town, or village where a rental automobile was returned.

Auto Rental Return Country The Country Code of the Country where a rental automobile was returned.
Code Refer to the Country Codes section of the Codes Reference Guide for a
complete list of codes and descriptions.

Auto Rental Return Date The date a rental automobile was returned.

Auto Rental Return Region Identifies the state, province or region where a rental automobile was
Code returned. Refer to the Region Codes section of the Codes Reference Guide
for a complete list of codes and descriptions.

Auto Rental Return Time The time a rental automobile was returned.

Page 10-10 October 2019

Definitions (continued)

Automated Address A message option that allows an S/E to verify the Cardmember address
Verification information.

Automated Teller Machine An unattended terminal where an ATM Transaction takes place. Refer to
(ATM) ATM Transaction.

Bank Identification Number The first six (6) digits of a Cardmember account number or Token that
(BIN) identifies an Issuer Institutions.

Base Discount Rate The S/E’s base discount rate, not including fees or incentives. This has
three implied decimal places.
For example, a Base Discount Rate of 3.250 would be populated as 3250 for
the field value.

Batch Control Number A sequential control number that starts at 001 for the first batch in the first
file. The batch control number increments through 999 for each batch in a
file or across files. Batch Control Number rolls to 001.

Batch Exception Update This Program Specific Data Collection message is used to transmit batch
Request (9344) Authorization exception update messages from the Issuer to the Network.
The Network uses this data to update the Network Exception Database.

The Network responds with the Batch Exception Update Response Count
and Detail message.

Batch Exception Update The Network returns the Batch Exception Update Response Count and
Response Count and Detail Detail message to supply the count of the total number of records received
(9344) and detail about the rejected records.

Beginning Hours of Operation The local time the device (ATM) location begins hours of operation (i.e., the
time the business opens and is available for Cardmember use). If the device
is available 24 hours a day, default to 000001.

Beta Test A live operational and systems test.

Billing Period The billing period for this recurring charge.

Billing(s) The aggregate of amounts on all Cardmember statements with inclusions

and exclusions as defined in the Participant Agreement.

Bitmap Primary Each bit in this data element identifies the presence (value 1) or absence
(value 0) of a field.

October 2019 Page 10-11

Definitions (continued)

Brand Protection Policies and procedures designed to protect the American Express Brand
and Participants against exposure to regulatory, financial, and brand risks
associated with Illegal or Brand Damaging Activity.

Business Day A day on which all parties to a transaction and/or an event are open to do
business.

Business Ownership Indicates the category of the business owner as may be needed by special
Classification Code interest groups in specific regions.

Call Date The date a communication (e.g., a phone call) was initiated.

Call Duration Time The length or duration of a communication (e.g., a phone call).

Call From City Name The city, town or village where a communication originated.

Call From Country Code The Country Code of the country where a communication originated. Refer
to the Country Codes section of the Codes Reference Guide for a complete
list of codes and descriptions.

Call From Phone Number The phone number where a call or fax originated.

Call From Region Code The state, province or region code where a communication originated. Refer
to the Region Codes section of the Codes Reference Guide for a complete
list of codes and descriptions.

Call Time The time a communication (e.g., a phone call) was initiated.

Call To City Name The destination city, town, or village of a communication.

Call To Country Code The destination Country Code of the country of a communication. Refer to
the Country Codes section of the Codes Reference Guide for a complete list
of codes and descriptions.

Call To Phone Number The destination phone number of the communication.

Call To Region Code The destination state, province or region code of a communication. Refer to
the Region Codes section of the Codes Reference Guide for a complete list
of codes and descriptions.

Page 10-12 October 2019

Definitions (continued)

Campaign Country Name The country in which the campaign is sponsored.

Cancelled Effective Date The date the Service Establishment was placed in a cancelled status if the
Status Code indicates cancelled or reinstated.

Capture Date The Capture Date on which Transaction data was processed.

Capture Time The Capture Time on which Transaction data was processed.

Card A payment Card bearing an American Express trademark or logo and issued
by an Issuer or an Account number issued by an Issuer, which can be used
to purchase Goods and Services from S/Es on the Network and/or to obtain
financial services at ATMs.

Card Acceptor Address Line The Card Acceptor (also known as Service Establishment (S/E)) location
1-4 address.

Card Acceptor Business Code Also called the Merchant Category Code (MCC), this code classifies the
business product or service for a Card Acceptor (S/E).

Card Acceptor City The city name of the Card Acceptor location.

Card Acceptor Country Code The Country Code of the Card Acceptor location.

Card Acceptor Country Name The name of the country in which the Card Acceptor is located.

Card Acceptor Full Recourse A Y (Yes) or N (no) indicator that shows if the Card Acceptor is on a Full
Status Recourse Agreement with the Acquirer.

Card Acceptor Headquarters If the supplier is part of a corporation, the location name may be different
Name than the headquarters. This is the name of the corporation.

Card Acceptor Headquarters If the supplier is part of a corporation, this is the Card Acceptor number
Number assigned to the headquarters of the corporation.

Card Acceptor High Risk Designates the current High Risk Status of the Card Acceptor (S/E).
Indicator
Note: S/E Volume Summary Messages must be submitted for all S/Es, not
just those with High Risk Indicators. Refer to the Card Acceptor High Risk
Indicators section of the Codes Reference Guide for a complete list of codes
and descriptions.

October 2019 Page 10-13

Definitions (continued)

Card Acceptor Identification The routing transit number in an ATM Transaction. This value is a 10-digit
Code (ATM) number.

Card Acceptor Identification The Service Establishment (S/E) number given to one or more locations of
Code (POS) the Card Acceptor. The number is ten digits, followed by five spaces for a
total of 15 bytes.

Card Acceptor Identification The Service Establishment (S/E) number given to the provisioning
Code (Provisioning) requestor. The number is ten (10) digits, followed by five (5) spaces for a
total of 15 bytes.

Card Acceptor Invoice Number A unique number assigned by the S/E to track a Transaction. The invoice
number is assigned to the Transaction by the supplier.

Card Acceptor Location Text The free form text location of the Card Acceptor.

Card Acceptor Multinational A Y (Yes) or N (no) indicator that shows if a particular Transaction relates to
Indicator an AEGNS Multinational Account (MNA).

Card Acceptor Name (ATM) The ATM location as it is known to Cardmembers.

Card Acceptor Name (POS) The name of the Card Acceptor, also know as Service Establishment (S/E).

Card Acceptor Name and The name of the Card Acceptor as it is known to Cardmembers.
Location

Card Acceptor Name and For a digital wallet Payment Token Provisioning Request, this is the name of
Location (Digital Wallet) the digital wallet as it is known to the Cardmember.

Card Acceptor Original Invoice The original invoice number assigned to the Transaction by the supplier.
Number Required for refund Transactions.

Card Acceptor Postal Code The postal code of the Card Acceptor location.

Card Acceptor Region Code A code for the state, province, or region of the Card Acceptor location.

Card Acceptor Telephone The telephone number used to contact the Card Acceptor.
Number

Card Acceptor Terminal This code identifies a POS terminal at a Card Acceptor location.
Identification

Page 10-14 October 2019

Definitions (continued)

Card Acceptor Terminal A unique code that identifies an ATM terminal at a Card Acceptor location
Identification (ATM) (i.e., where the Transaction took place).

Card Account Name The name embossed on the front of the Card. This could be different from
the Primary Account holder’s name.

Card Activation Code This field shows if the Card uses a Card Activation Service. For future use.

Card Capability This field indicates the highest form of technology present in the Card.

Card Effective Date This is the Card Effective Date embossed on the face of the Card.

Card Effective Month The month in which the Card becomes valid.

Card Effective Year The year in which the Card becomes valid.

Card Expiration Date This is the Card Expiration Date embossed on the face of the Card.

Card Expiration Month The month in which the Card is no longer valid.

Card Expiration Year The year in which the Card is no longer invalid.

Card Not Present Any Transaction in which the Cardmember and Card are not present at the
Point of Sale (e.g., Internet, mail order).

Card Phone Number The number associated with the Customer’s calling card.

Card Present Any Transaction in which the Cardmember and Card or Mobile Proximity
Payment Device (MPPD) are present at the Point of Sale (e.g., a retail
store).

Card Security Code (CSC) Any of several values printed or encoded on the Card and used for fraud
prevention in Authorizations, including: the Printed Card Security Code
(PCSC), the 5-digit Card Security Code encoded within the magnetic stripe
(5CSC), and the 5-digit Card Security Code encoded within the magnetic
stripe equivalent on Chip Cards (iCSC).

Card Security Code Key (CSCK) A Cryptographic Key used to create Card Security Codes that are placed on
the magnetic stripe, chip, or Card.

October 2019 Page 10-15

Definitions (continued)

Card Type Indicator When populated with the value of “C” by an Issuer, the Card Type Indicator
identifies the account as an Expresspay-enabled Card.

Card Verification Result (CVR) Proprietary data element indicating the exception conditions that occurred
during Card risk management.

Card-on-file The storage of a Cardmember’s PAN and associated data by or on behalf of

an S/E in support of Billing Services, including, but not limited to, Recurring
Billing Transactions.

Cardholder Data Cardholder Data has the meaning contained in the current Payment Card
Industry Data Security Standard Glossary, Abbreviations and Acronyms
(refer to [Link]), and, as of the date of this
publication, it includes the following elements:
• The full Primary Account Number (PAN) by itself, or
• The full PAN plus any of the following:
• Cardholder Name
• Expiration Date
• Service Code

Cardholder Verification The method by which Cardmember verification is performed to make sure
Method (CVM) that the person presenting the Card or Mobile Device is the person to whom
the Account was issued.

Cardmember A Person who has entered into an agreement and established a Card
Account with any Issuer, or whose name appears on a Card.

Cardmember Account Number Digits 3 through 11 from the original Cardmember (CM) Account Number
and a calculated check digit.

Cardmember Address Line 1-4 A line used for the Cardmember address.

Cardmember Billing Amount The Cardmember billing amount calculated for an individual Transaction,
inclusive of fees, in the currency defined by the Issuer’s contractual
agreement with the Cardmember identified in the Cardmember Billing
Currency Code.

Cardmember Billing City The city associated with the Cardmember’s billing address.

Cardmember Billing Country The Country Code of the Cardmember based on the issuing BIN.
Code

Page 10-16 October 2019

Definitions (continued)

Cardmember Billing Currency The numeric currency code of the Cardmember Billing Amount.
Code

Cardmember Billing Date The local date when the Issuer billed the Cardmember account.

Cardmember Billing The number of places the decimal must be moved to the left to correctly
Decimalization represent the Cardmember Billing Amount. (Monetary amounts are stored
without decimal places.)

Cardmember Billing Postal The postal code of the Cardmember’s billing address.
Code

Cardmember Billing Region The Region code of the Cardmember based on the issuing BIN.
Code

Cardmember First Name The first name of the Cardmember.

Cardmember Last Name The last name of the Cardmember.

Cardmember Name This field contains the Cardmember’s Name.

Cardmember Reference A Cardmember designated reference number that corresponds with the
Number Transaction.

Cards in Force (CIF) Total number of non-cancelled Cards issued by a particular Issuer as of the
end (or beginning, when stated) of a given period.

Carrier Code Segment 1-4 The IATA Carrier Code of the transportation provider for each segment of
travel or a three-digit code of “YY” and a space for a non-IATA carrier.

Cash Advance The receipt of cash from an ATM displaying the American Express logo, by a
Cardmember using his/her Card.

Cash Disbursement The receipt of cash from an ATM displaying the American Express logo, by a
Cardmember using his/her Card.

Cash Disbursement Provider Branch locations of Participants that have been certified to process Cash
Disbursements.

Centurion Line A Card which is identical in appearance, positioning, and core benefits to a
Card issued by American Express or an American Express Entity. Also
referred to as an “American Express Format Card” or “Centurion Line Card.”

October 2019 Page 10-17

Definitions (continued)

Certification The verification of a Participant’s connectivity, message format, and

message content.

Change Flag Indicates the action taken on this record by the embossing center.

Change Indicator Shows if the batch contains changes to a previously sent record.

Charge Item Amount 1-4 The unit cost of the item which corresponds to the items described in the
Charge Item Description and Charge Item Quantity fields.

Charge Item Description 1-4 A concise description of the goods or services purchased which corresponds
to the items described in the Charge Item Amount and Charge Item
Quantity fields.

Charge Item Quantity 1-4 The quantity of items purchased that corresponds to the Charge Item
Amount and Charge Item Description fields.

Chargeback An amount which an Issuer is entitled to collect from an Acquirer in

accordance with the Network Chargeback policy.

Chargeback Message Reason An ISO code subset of the Message Reason Code values, indicating the
Code reason a Transaction was charged back.

Chargeback Reason Text More formatted text to further qualify the Message Reason Code for a
Chargeback.

Check Digit Routine A calculation that is performed on the Cardmember Account number to
determine if the Account Number may be valid.

Chip Card A Card with an embedded chip containing AEIPS and/or Expresspay
Applications that, when used at a Chip Card-enabled terminal, interacts
with the terminal to initiate AEIPS or Expresspay Transactions.

Page 10-18 October 2019

Definitions (continued)

Chip Card (9240) The Chip Card Addendum transmits Transaction data containing data on the
Cardmember’s Chip Card Transaction. The Point of Service Data Code in the
Presentment message is used to show the Transaction was made with a
Chip Card.

First Presentment Chip Card Transactions can be sent with Industry

Specific, Deferred Payment Plan, Double Byte Character, and/or Market
Specific Data addenda messages in addition to a Chip Card Addendum.

This addendum is only used with the First Presentment (1240) message
and should not accompany Data Collection messages sent through the
Network.

The Chip Card Addendum must accompany the 1240 First Presentment
when the Transaction is an AEIPS or Expresspay EMV mode Transaction
identified by the Point of Service Data Code Position 7 value of 5 in the 1240
First Presentment.

Chip Card Request and The Chip Card Request message is used to transmit data from the Issuer to
Response (9344) the vendor for creation and personalization of a chip card. The Chip Card
Response message is sent from the vendor to the Issuer and contains data
on all cards that have been successfully personalized and dispatched.

City Name in Katakana The Katakana name of the city in which the Service Establishment, or
outlet, is located.

Class of Service Code 1-4 Assigned by the Carrier that corresponds to the fare class (e.g. A, B, etc.) in
the class of service (e.g., First Class) applicable to this travel segment.
Refer to the Class of Service Codes section of the Codes Reference Guide
for a complete list of codes and descriptions.

Clearing The process of routing, editing, and summarizing Transaction data between
an Acquirer, an Issuer, and the Network for Participant reconciliation and
Settlement.

Communication Call Type Code A code indicating the type of communication or call. Refer to the
Communication Call Type Codes section of the Codes Reference Guide for a
complete list of codes and descriptions.

Communication Rate Class A code that indicates the rate class used to price a communication (e.g., a
Code phone call or fax). Refer to the Communication Rate Class Codes section of
the Codes Reference Guide for a complete list of codes and descriptions.

Communication Services The Communication Services Industry Specific Detail message fields
Industry Specific Detail contain more data for a Communication Services Transaction. If the Format
(9240/9340) Code included in the 1240 Presentment message is 13, the Communication
Services addendum must be submitted with the Presentment.

Each First and Second Presentment can have multiple addenda records, but
can have only one Industry Specific Detail Addendum record.

October 2019 Page 10-19

Definitions (continued)

Compliance The procedure used to resolve issues between Acquirers and Issuers
regarding a violation of the policies in the Business and Operational Policies
manual.

Conjunction Ticket Y (yes) or N (no) code shows if the itinerary contains more than four
segments of travel.

Contact Email Address The email address of the contact for shipping questions.

Contactless A Transaction environment using a Near-Field Communication (NFC)

enabled card or mobile device to initiate a Transaction.

Contactless Payment Acceptor A Y (Yes) or N (No) indicator that shows if the Card Acceptor is enabled to
process payments initiated with an Expresspay (Contactless) device.

Contract Number The contract number of this installment agreement.

Copy Indicator Shows if the batch was sent before.

Corporate Purchasing Card Companies review their internal processing to decrease costs and increase
Transaction Detail (9240) employee productivity. To do this, many companies use the Corporate
Purchasing Card (CPC).

The CPC is a charge card designed to:

• Purchase some types of goods and services
• Decrease the cost of purchases and the administrative purchasing
process
• Supply more Transaction data to the Issuer for reporting CPC
Transactions to CPC clients

If sent, a POS First or Second Presentment (1240) message must come

before the Corporate Purchasing Card Transaction Detail Addendum
Message.

The fields in the Message Layout have more data for a Corporate
Purchasing Card Transaction, representing fields that pertain to the entire
Transaction.

In the outclear and inclear columns, the optionality is defined for the
outclear and inclear files. Although many of the fields are optional, the
Corporate Client will determine which S/Es must collect and report the
enhanced data, and what data is necessary.

Cost of Funds Interest or associated costs (as a rate) paid by a financial institution to
continue servicing the business function following late or non-settlement.

Country Code, Acquiring This is the Country Code of the acquiring institution.
Institution

Page 10-20 October 2019

Definitions (continued)

Create Timestamp The time the Transaction was entered into the Global Fraud Repository.

Creation Julian Date Indicates the date the batch was created.

Creation Time - Hour Indicates the hour the plastic was embossed.

Creation Time - Minute Indicates the minute the plastic was embossed.

Credit An amount to be credited to a Cardmember's Card Account.

Credit Card A Card for which only a predetermined percentage or minimum amount,
rather than the full amount, of the outstanding balance is required to be
paid by the Cardmember each month, with interest being charged on the
unpaid balance on such Card Account.

Credit Code Preferred A code that represents a set of changes to the CRIT Table’s Cardmember
charging thresholds. Each code maps to a unique set of indexes.

Credit Count Contains the total number of credits for financial messages in the file. When
the Credit Count exceeds the number of bytes available for the field, the
Credit Count will be truncated on the left side. For example, a Credit Count
of 111,900,000 credit transactions will populate 11900000 as the field
value.

Credit Count (for DAF 1325 Contains the total number of credits for financial and non-financial
Field 4) (Retrieval Requests and Fulfillment Notifications) messages in the file.
When the Credit Count exceeds the number of bytes for the field, the Credit
Count will be truncated on the left side. For example, a Credit Count of
119,900,000 credit transactions will populate 19900000 as the field value.

Credit Count (for File Trailer Contains the total number of credits for financial messages in the file. When
(9825)) the Credit Count exceeds the number of bytes available for the field, the
Credit Count will be truncated on the left side. For example, a Credit Count
of 1,900,000 credit transactions will populate 900000 as the field value.

Credits Total Amount A total of the values in the Transaction Amount field (byte positions 32-46)
for all financial credit messages.

Credits Total Amount (DAF A total of the values in the Transaction Amount field (byte positions
1325) 196-210) for all financial credit messages. This excludes non-financial
messages in the Daily Activity File.

October 2019 Page 10-21

Definitions (continued)

Cryptogram Information Data Indicates the type of cryptogram (TC, ARQC, or AAC) returned by the Card
and the steps the terminal must perform. Use the AEIPS Chip Card
Specifications for format instructions.

Cryptogram Version Number Version of the algorithm used to define the cryptogram generation as
defined in the AEIPS specifications.

Cryptographic Key A secret value to Encipher or Decipher the Ciphertext.

Currency Code, Reconciliation This is the numeric code of the Issuer’s currency.

Currency Code, Transaction This is the numeric code for the currency used in the Transaction or
Payment Token Provisioning Request.

Current Status Code Identifies the status of the fraud transaction at this reporting period.

Customer Activated Terminal An unattended POS device that dispenses a product or provides a service
(CAT) paid for with a Card (e.g., gasoline pump upon activation by a valid Card).

Customer Service Number The telephone number to contact a customer service representative for help
at the device (ATM) location (the owner or service of the machine).

DAF ATM Fees (1644) The Network assesses and settles ATM Fees. The Network sends the ATM
Fee Message to the Participant.
The 1740 message is sent to an Issuer, and the 1742 message is sent to an
Acquirer. For ATM Fees, debit Processing Codes are used in the 1740
message, and credit Processing Codes in the 1742 message.

DAF ATM First and Second The American Express Funds Access System (FAS) creates the ATM First
Presentments (1644) Presentments (1240) from the ATM Financial Transaction Request (1200).
These messages contain data from one Cardmember Transaction.

Page 10-22 October 2019

Definitions (continued)

DAF File Returned (1644) The DAF File Returned summarizes activity for Transactions presented
during the reporting period that have been returned to the sending
Participant.
This file only contains Transactions returned.
• For returned files due to the error threshold that is met or a full file
reject for counts or amount, the reject reasons are blank since the
Transaction itself is not rejected.
• Returned Transactions that contain the reject reasons.
• For returned Transactions, most fields are specified as alphanumeric to
let the Network send the field back with the same data as received. For
example, if the Transaction was returned because the Transaction
amount field contained spaces, the DAF record will contain spaces in
the Transaction amount field.

DAF First and Final The First and Final Chargeback Notification is outcleared from the Issuer to
Chargebacks (1644) the Network and incleared from the Network to the Acquirer to process a
Transaction Chargeback. This record contains Original Transaction,
Presentment data, and Chargeback and supporting documentation.

DAF Fulfillment Notification The Acquirer sends the Fulfillment Notification (1640) message to the
(1644) Issuer through the Network in response to a Retrieval Request Notification
for a Record Of Charge (ROC) or Transaction documentation.

DAF Network Fees (1644) The Network sends Automated Fee Collection messages for
Network-generated fees to Participants. The Network generates the Fee
Collection Message (1744) and sends it to an Acquirer or Issuer.
This message contains the fee amount and a description. The fees assessed
are driven by contractual data captured in the Participant Profile during the
Participant Setup process.

DAF Non-Cleared (1644) Non-Cleared shows the Network does not recognize the Transaction type, or
the Network cannot determine what layout to use to map fields from the
first outcleared record into the DAF record. The Network uses the POS
Presentment layout to map fields and define most fields as alphanumeric,
allowing the Network to send the field back with the same data as received.

DAF Retrieval Request The Issuer sends the Retrieval Request Notification message (1642) to the
Notification (1644) Acquirer through the Network to request Transaction data. This record
contains the first Presentment data.

Daily Activity File A flat file with transaction level activity for an organization’s settlement and
transaction reconciliation process.

Daily Activity File (DAF) File The fields of the Daily Activity File (DAF) File Header (1324) are used for
Header (1324) routing and file integrity verification. The DAF File Header (1324) message
comes before all DAF (1644) messages.

October 2019 Page 10-23

Definitions (continued)

Daily Activity File (DAF) File The fields of the Daily Activity File (DAF) File Trailer (1325) are used for
Trailer (1325) routing and file integrity verification. The DAF File Trailer (1325) can only be
used with the DAF File Header (1324). The DAF File Trailer (1325) is the last
message on the Daily Activity File (1644).

Daily Activity File (DAF) POS First and Second Presentments contain data from one Cardmember
First and Second Presentments Transaction. First and Second Presentments outclear from the Acquirer to
(1644) the Network and Inclear from the Network to the Issuer.

Daily Activity Process It provides Participants with a consolidated source of data to use during the
auto-reconciliation or settlement process.

Daily Activity Report A report that summarizes daily activities for Issuer IINs and Acquirer AINs
associated with one (1) organization for one (1) reporting period.

Daily Settlement Advisement A Network report that augments the Daily Activity File to give Participants
more calculations on settlements not automatically done by the Network.

Data Collection File Header The Data Collection File Header (9844) message comes before all Data
(9844) Collection messages and is the first data record on the file and serves as the
highest level of control in a file. Each file can have only one Data Collection
File Header message. It designates date, time, and file identification fields
that uniquely distinguish the file from the other files transmitted by a
Participant. The Data Collection File Header message is created by the
forwarding institution for the file.

The fields of the Data Collection File Header (9844) are used for routing and
file integrity verification. A Data Collection File Header must come before all
Data Collection Messages.

Data Collection File Trailer The Data Collection File Trailer (9845) message comes after the Data
(9845) Collection messages. It is the last data record in the Data Collection
message file. Each file has only one Data Collection File Trailer message. It
echoes data from the file header and includes control totals used to make
an analysis of the integrity of the file after transmission. The Data Collection
File Trailer message is created by the forwarding institution for the file.

The fields of the Data Collection File Trailer (9845) are used for routing and
file integrity verification. The Data Collection File Trailer (9845) can only be
used with the Data Collection File Header (9844).

Data Compromise Unauthorized use of or unauthorized access to Cardholder Data and/or

Sensitive Authentication Data, including payment-related Cryptographic
Keys, that results in the misuse of such information or the reasonable
possibility that the misuse of such information will occur.

Date and Time, Local This is the local date and time when a Transaction occurred.
Transaction

Page 10-24 October 2019

Definitions (continued)

Date and Time, Local This is the current date and time supplied by the Network at the time of the
Transaction (Provisioning) provisioning request.

Date and Time, Transmission This is the local date and time when the Acquirer transmits the request to
the Network.

Date of First Installment The date the first installment is due for a deferred payment plan purchase.
Payment

Debit Count Contains the total number of debits for financial messages in the file. When
the Debit Count exceeds the number of bytes available for the field, the
Debit Count will be truncated on the left side. For example, a Debit Count of
111,900,000 debit Transactions will populate 11900000 as the field value.

Debit Count (DAF 1325) Contains the total number of debits for financial and non-financial (Retrieval
Requests and Fulfillment Notifications) messages in the file. When the Debit
Count exceeds the number of bytes for the field the Debit Count will be
truncated on the left side. For example, a Debit Count of 119,900,000 debit
Transactions will populate 19900000 as the field value.

Debit Count (for File Trailer Contains the total number of debits for financial messages in the file. When
9825) the Debit Count exceeds the number of bytes available for the field, the
Debit Count will be truncated on the left side. For example, a Debit Count of
1,900,000 debit Transactions will populate 900000 as the field value.

Debits Total Amount A total of values in the Transaction Amount field (byte positions 32-46) for
all financial debit messages.

Debits Total Amount (DAF A total of the values in the Transaction Amount field (byte positions
1325) 196-210) for all financial debit messages. This excludes non-financial
messages in the Daily Activity File.

Deferred Payment Plan The Deferred Payment Plan (DPP) addendum is used when the Issuer has a
(9240/9340) deferred payment plan for their Cardmembers. Field 112, Extended
Payment Data positions 1021-1022 of the POS First Presentment (1240)
message must contain a value greater than 01.

The fields in the Deferred Payment Plan Addendum message contain more
data for a Deferred Payment Plan Transaction.

Deferred Payment Plan (DPP) This is the Deferred Payment Plan data, permitting charges to be billed in
equal installments rather than in one (1) total billing.

Deny List An S/E-maintained list of Card Account numbers used to deny access to the
transit service following a declined Authorization and to reinstate access
following a subsequent Authorization approval.

October 2019 Page 10-25

Definitions (continued)

Departure Date 1-4 The departure date for a segment of a trip.

Departure Location Code 1-4 The IATA Travel Point Code of the departure location (e.g., airport, rail
terminal, or city), or a three-digit code of “ZZZ” for a non-IATA travel point.

Departure Rail Station Name The location name of the departure rail station associated with a rail ticket
1-4 purchase.

Derivation Key Index Proprietary data element associated with the Chip Card and transmitted in
the Card Verification Results during Chip Card Transactions. This data
element may be used by the Issuer of the Chip Card to select the applicable
keys to use to perform online Card Authentication (or, cryptogram
validation) and Issuer Script Processing.

Destination Institution A unique number that identifies the final destination institution receiving
Identification Code the data record.

Destination Location Code 1-4 The IATA Travel Point Code of the destination location (e.g., airport, rail
terminal, or city), or a three-digit code of “ZZZ” for a non-IATA travel point.

Device Location Code A unique code identifying the type of device (ATM) location (e.g., shopping
center, airport, business district).

Device Network Name The name of the device (ATM) Network used by the owner of the ATM (i.e.,
Bank One).

Device Network A unique routing/transit number assigned by AEGNS to the device to

Routing/Transit Number identify the ATM Participant.

Device Properties Code Up to four unique codes that describe the properties of the functions of the
device (ATM) at this location (e.g., deposits accepted, restricted access,
security camera on site, surcharge, etc.).

Digital Wallet A type of Digital Wallet Payment where a Transaction is initiated by a digital
Application-initiated wallet utilizing a merchant application within a Mobile Device, and not
Transaction through the contactless interface.

Digital Wallet A Type of Digital Wallet Payment where a Transaction is initiated by a digital
Contactless-initiated wallet within a Mobile Device through the contactless interface at an
Transaction Expresspay-enabled POS Device.

Page 10-26 October 2019

Definitions (continued)

Digital Wallet Magnetic Secure A type of Digital Wallet Payment where a Transaction is initiated by a digital
Transmission (MST) wallet within a Mobile Device through MST.
Transaction

Digital Wallet Payment A Digital Wallet Contactless-initiated Transaction, Digital Wallet

Application-initiated Transaction, or Digital Wallet Magnetic Secure
Transmission (MST) Transaction conducted through a digital wallet,
operated by an AEGNS-recognized Digital Wallet Program Provider that
resides on a Mobile Device.

Digital Wallet Program An AEGNS-recognized digital wallet program that supports enablement of
Digital Wallet Payments or Expresspay Mobile Transactions initiated from
Mobile Devices.

Discount Amount The total discount amount for all items purchased, stated in the Transaction
currency as it was executed at the Card Acceptor location.

Discount Rate The rate used to calculate the decrease from the list price of the item. Two
decimal places are implied.

Dispensed Currency The currency code of the currency in which the First Presentment
Transaction Amount was executed at the ATM.

District Location of Service The Katakana name of the region or district in which the Service
Establishment Establishment, or outlet, where the Transaction occurred is located.

Documentation Any supporting information provided by a Cardmember, Acquirer, Issuer, or

S/E such as a Cardmember letter, copy, itemized Documentation, Original
ROC, ROC, Substitute ROC, or Transaction Log.

Double Byte Character A single character requiring two (2) bytes of data.

Double Byte Character (9240) The Double Byte Character (DBC) addendum is sent with First and Second
Presentments in countries where Cardmember statements must be in the
local language. Acquirers in some countries send the Card Acceptor name
and address in the local language character set to the Issuers in the same
country who have contracted to receive it. The Network sends the DBC
addenda to certified Issuers when the Transaction occurred in the Issuer’s
domicile country.

Double Byte Character Card Lines used to indicate the Card Acceptor location address represented in the
Acceptor Address Lines 1-4 local language and character set where the Transaction occurred.

October 2019 Page 10-27

Definitions (continued)

Double Byte Character Card The name of the Card Acceptor/Service Establishment as it is known to the
Acceptor Name Cardmember represented in the local language and character set where the
Transaction occurred.

Double Byte Data Line 1-4 A free-form entry in the local language and character set where the
Transaction occurred.

Duty Amount The total duty amount for all items purchased, stated in the Transaction
currency as it was executed at the Card Acceptor location.

Dynamic Fraud Management A set of fraud Authorization tools including a Fraud Probability Score and
Network Services (DFMNS) Recommendation Code assessed for each Eligible Transaction. The results of
the evaluation (i.e., Eligible Transactions that have a higher fraud risk) are
displayed to Issuers through WINTER and, for certified Issuers, through the
Authorization message.

E-Ticket Indicator Y (yes) or N (no) code to indicate if an electronic ticket was issued.

Electronic Commerce Indicator An indicator that is related to American Express SafeKey and shows the
(ECI) results of SafeKey Authentication.

Embossing Center Number The unique number assigned to the embossing location by AEGNS.

Embossing Machine ID A unique character to identify each embossing machine at an embossing

center, starting with one. This will always be 1 for a center with only one
embossing machine.

Embossing Software Version Reserved for use by AEGNS.

Emergency Card Replacement The process of replacing a Card for a Cardmember when he or she has
(ECR) reported that the original Card has been lost or stolen and a replacement is
needed on an emergency basis.

EMV A term that is used to refer to the specifications developed by Europay,

MasterCard, Visa, and American Express.

EMV Mode An Expresspay Transaction mode using EMV-compliant processes between

the Card, Terminal, and Acquirer.

Page 10-28 October 2019

Definitions (continued)

Encryption Encryption has the meaning contained in the current International

Organization of Standards (ISO) (refer to [Link]), and, as of the date
of this publication, includes the act of enciphering, i.e., rendering of text
(Plaintext) unintelligible (Ciphertext), by means of an encoding mechanism.
Plaintext can be understood by any entity (e.g., a person, a computer, or a
process). Once transformed into Ciphertext, no entity can process or
understand the data until the Ciphertext is correctly deciphered.

End Sentinel This field identifies the end of the magnetic stripe.

Ending Hours of Operation The local time that the device (ATM) location ends hours of operation (i.e.,
the time the business closes and is no longer available for Cardmember
use). If the device is available 24 hours a day, default to 000001.

Enhanced Exception File Use the Enhanced Exception File to send exception data from the Issuer to
the Network. The Network uses this data to update the Network Exception
Database, which contains data about Card accounts that get special
handling.
The Enhanced Exception File contains fields that are specific to the
Recurring Billing Cancellation Service.

Entertainment/Ticketing The Entertainment/Ticketing Industry Specific Detail message fields contain

Industry Specific Detail more data for an entertainment/ticketing Transaction. If the Format Code
(9240/9340) included in the 1240 Presentment message is 22, the
Entertainment/Ticketing addendum must be sent with the Presentment.

Each First and Second Presentment can have multiple addenda records, but
can have only one Industry Specific Detail Addendum record.

European Economic Area European Economic Area combines the countries of the European Union
(EEA) (EU) and member countries of the European Trade Association.

Event Country Code The Country Code where the event is to be or was held. Refer to the
Country Codes section of the Codes Reference Guide for a complete list of
codes and descriptions.

Event Date The date of an entertainment or ticketing event. The default is the
Transaction date.

Event Individual Ticket Price The price of an individual ticket for an entertainment or ticketing event
Amount represented in First Presentment Presentment Currency and
Decimalization.

October 2019 Page 10-29

Definitions (continued)

Event Location The name of the city or the venue name for an entertainment or ticketing
event.

Event Name The name of an entertainment or ticketing event.

Event Region Code A code indicating the state, province, or region where the event is to be or
was held. Refer to the Region Codes section of the Codes Reference Guide
for a complete list of codes and descriptions.

Event Ticket Quantity The number of tickets purchased for an entertainment or ticketing event.

Exception Code The disposition for the Card Account.

When the Network receives a Real Time Exception Update message, it

applies the change only if the code is of the same or higher importance.

Exception File Use the Exception File to send exception updates from the Issuer to the
Network. The Network uses this data to update the Network Exception
Database, which stores data on Card accounts that should receive special
handling.

Exchanged Ticket Number The number associated with the exchanged ticket; used to link the new and
exchanged tickets. Cardmember can monitor the Transaction.

Expiration Date The year and month on which a Card expires.

Expired Card A Card for which the Expiration Date appearing on the front of the Card or
encoded on the magnetic stripe has passed.

Expiry Month A value from 01 to 12 that indicates the month the Exception File record will
expire.

Expiry Year The last digit of the year that the negative should expire; for example,
5=2005.

Expresspay Expresspay is a program within American Express for facilitating

Contactless Transactions between a Chip Card or Mobile Device containing
an Expresspay Application and an Expresspay-enabled POS Device.

Expresspay Application An application residing on a Chip Card or Mobile Device that is used in the
initiation of an Expresspay Transaction at an Expresspay-enabled POS
Device.

Page 10-30 October 2019

Definitions (continued)

Expresspay Mobile An AEGNS-approved service that is enabled by an Issuer and its Mobile
Entities, including, as applicable, Service Providers. A mobile version of
Expresspay where the Expresspay application is hosted in a secure element
of a Mobile Device, or a software-based version of Expresspay Mobile where
an Expresspay Mobile Host Card Emulation (HCE) Application resides in the
operating system of a Mobile Device and is capable of transacting over a
contactless interface.

Expresspay Mobile Transaction An Expresspay Transaction initiated by a Mobile Device as a method of

payment.

Expresspay Transaction An Expresspay Transaction is a Contactless Transaction initiated by the use

of an Expresspay-enabled Card or Mobile Device at an Expresspay-enabled
POS Device.

Extended Financial Addendum The Extended Financial Addendum (9240) contains more financial data for
(9240) POS and ATM Transactions, and additional data supporting a Transaction
using payment tokenization.

The Extended Financial Addendum (9240) is used for multiple financial

features that align with regulatory or contractual requirements in which
Issuers must disclose financial data to their Cardmembers.

European Union (EU) and European Economic Area (EEA) Issuers should
refer to the Payment Service Directive (PSD) for instruction on foreign
exchange data disclosure. Look on Knowledge Base and use the Search
function to locate the Payment Services Directive (PSD) document.

If the Participant elects to receive more financial data, the Extended

Financial Addendum will accompany the First and Second Presentment
(1240) and directly follow the 1240 message.

Extended Payment Data The number of extended payment installments requested for a card
transaction (e.g., 16 = 16 months).

Fallback When an AEIPS Transaction cannot be completed in a Chip-Enabled Device

utilizing chip technology, the Chip-Enabled Device must then utilize the
magnetic card stripe to continue the Transaction.

Fare Segment 1-4 The total fare for a segment of travel including taxes and fees.

Fee Amount The amount assessed to specific Issuers who are contractually obligated to
receive the 9240 Extended Financial Addendum.

Fee Amount Currency Code The currency code of the Fee Amount. Refer to the Currency Codes section
of the Codes Reference Guide for a complete list of codes and descriptions.

October 2019 Page 10-31

Definitions (continued)

Fee Amount Decimalization The number of places the decimal must be moved to the left to correctly
represent the Fee Amount. Refer to the Currency Codes section of the
Codes Reference Guide for a complete list of codes and descriptions.

Fee Collection (1744) The Network creates the Fee Collection (1744) message and sends it to an
Acquirer or Issuer.
This message contains the fee amount and a description. The fees are
calculated from contractual data in the Participant Profile.

Fee Reason Text Textual description of the fee being assessed.

Fee Type Code A code that describes the type of fee.

Fictitious S/E An S/E whose sole purpose of accepting American Express Cards is to
defraud the Acquirer or Issuer.

Field Separator This field divides track data. This field uses a 6-bit character set with odd
parity. Refer to ISO/IEC 7811-2, Identification Cards - Recording Technique
- Part 2- Magnetic Stripe for instruction.

File Header (9824) The File Header is the first data record in the file created by the forwarding
institution. The File Header is the highest level of control in a file. Each file
can have only one (1) File Header. The File Header contains the date, time,
and file identification fields that uniquely identify the file from other files
processed through the Network.

File ID This field indicates the file is a Card Identification Number File update file.

File Name Code Used to identify the contents of the file.

File Receipt Date The date the Participant received the file from the Network.

File Receipt Time The time the Participant received the file from the Network.

File Sequence Number A sequential number given to each file by the file originator. This number
starts at 000001 for the first file and increments by one for all other files.
The number starts at 000001 after it gets to 899999.

Note: File Sequence Number 900000-999999 are reserved for test files.

File Tracking Identifier An identification number assigned to individual files for tracking and
sorting. This field is spaces for organization and role level records.

Page 10-32 October 2019

Definitions (continued)

File Trailer (9825) The File Trailer is the last data record in the file created by the forwarding
institution. The File Trailer echoes data from the File Header. The File Trailer
contains control totals used to analyze the quality of the file after it is sent.

Filler Filler fields show positions in a message that are not used, but must contain
default values described in the Notes section.

Filler/Special Payment Type A multi-use field, which can have a space value or a Special Payment Type
Indicator which is only available to Acquirers supporting and Issuers
certified to receive the Special Payment Type Indicator.

The Special Payment Type Indicator provides additional information in

support of the Deferred Payment Plan Addendum by identifying if a
Transaction includes multiple installment payments.
The Special Payment Type Indicator is conditional as follows:
• Amount of installment (Transaction Amount) includes multiple
installment payments
• Acquirer provides Special Payment Type Indicator
• Issuer certified to receive Special Payment Type Indicator

Final Chargeback A second Chargeback, by the Issuer to the Acquirer, of the original
Transaction, in response to a Second Presentment.

Finance Charges The amount of finance charges for deferring payments on the purchase.
The position of the implied decimal point is determined by the Currency
Code, Transaction (Bit 49). Refer to the Currency Codes section of the
Codes Reference Guide for a complete list of codes and descriptions.

Financial Transaction A Transaction clearing through the Network that has a direct Settlement
impact associated with the Transaction.

First and Final Chargeback The Chargeback notification record is outcleared from the Issuer to the
Notification (1442) Network and incleared from the Network to the Acquirer to process a
Chargeback for a Transaction.
When an Issuer believes a Transaction does not comply with AEGNS
policies, the Issuer can file a Chargeback and move the financial liability to
the Acquirer. After a Second Presentment is received, the Issuer decides if
there is enough justification to dispute the Second Presentment. Process a
Final Chargeback in the same way that the First Chargeback was processed.
Refer to the Business and Operational Policies manual for instruction about
the Chargeback process and policy requirements.
Chargeback messages are specific to the type of Presentment sent.

First Chargeback The process an Issuer initiates to move financial liability from itself to an
Acquirer on a previously submitted Presentment.

October 2019 Page 10-33

Definitions (continued)

First Presentment The first time an Acquirer submits a Transaction to the Issuer through the
Network in a 1240 message.

First Presentment Network The date the First Presentment Transaction was accepted by the Network.
Processing Date

First Presentment Network The time the First Presentment Transaction was accepted by the Network.
Processing Time

First Presentment The dispensed amount of the original Cardmember Transaction as it was
Presentment Amount (ATM) executed by the Card Acceptor represented in the Transaction Currency.

First Presentment The sale or credit amount of the original Cardmember Transaction as it was
Presentment Amount (POS) executed by the Card Acceptor represented in the Transaction currency.

First Presentment The currency code of the First Presentment Presentment Amount submitted
Presentment Currency Code to the Network.

First Presentment The number of places the decimal must be moved to the left to correctly
Presentment Decimalization represent a First Presentment Presentment Amount.

First Presentment Transaction The sale or credit amount of the original Cardmember Transaction in the
Amount Transaction currency as it was executed at the Card Acceptor location. This
is the exact sales invoice amount, including taxes, and does not include
fees.

First Presentment Transaction The currency code of the local currency in which the First Presentment
Currency Code Transaction Amount was executed at the Card Acceptor location.

First Presentment Transaction The local date when a Cardmember Transaction was executed at a Card
Date Acceptor location. If mail order or telephone order, the Transaction Date is
the date the goods were shipped.

First Presentment Transaction The number of places the decimal must be moved to the left to correctly
Decimalization represent the First Presentment Transaction Amount.

First Presentment Transaction The local time when a Cardmember Transaction was executed at a Card
Time Acceptor location.

First Presentment Transaction The rate used to convert the Transaction Amount to the First Presentment
To Presentment Conversion Presentment Amount in an applicable presentment currency, when the card
Rate Transaction is not in a valid presentment currency.

Page 10-34 October 2019

Definitions (continued)

Flight Number 1-4 The flight number, as defined by the carrier for each segment of travel.

Floor Limit, Network The amount of a Transaction requiring Authorization set for specific industry
categories and geographic regions by AEGNS and to be used by Acquirers
when setting S/E Floor Limits.

Floor Limit, S/E A maximum monetary amount for a single Transaction, at or above which
the S/E must obtain an Authorization before completing the Transaction. At
their own financial risk, Acquirers may set individual S/E Floor Limits to
amounts different from those specified by AEGNS.

Foreign Currency Factor A percentage, as set out in the Participant Agreement, assessed by AEGNS
on the processing of a Transaction made in a currency different from the
currency in which the Cardmember’s Card is denominated.

Foreign Currency Factor An amount assessed by AEGNS for the processing of Charges and cash
Amount withdrawals made in a currency different from the currency in which the
Card is denominated.

Foreign Currency Factor The currency used for the Foreign Currency Factor Amount. Refer to the
Amount Currency Code Currency Codes section of the Codes Reference Guide for a complete list of
codes and descriptions.

Foreign Currency Factor The currency decimalization of the Foreign Currency Factor Amount. Refer
Amount Decimalization to the Currency Codes section of the Codes Reference Guide for a complete
list of codes and descriptions.

Format Code The type of industry specific detail to be supplied in the addendum and
amount fields for a Presentment message. More data is kept for certain
types of spending (e.g., for airline, hotel, restaurant, and retail store
purchases).

Forwarding Institution The institution identifier assigned to the processing institution that is
Identification Code sending the file.

Four Digit Batch Code The number printed on a Card that identifies the production batch of the
Card.

Fraud Chargeback Reason The chargeback reason as reported on the 9324 Fraud Repository Update
Code message.

October 2019 Page 10-35

Definitions (continued)

Fraud Disposition Code The current status of a fraud transaction reported to the GNS Fraud
Repository. Refer to the Fraud Chargeback Status Indicators section of the
Codes Reference Guide for a complete list of codes and descriptions.

Fraud Full Recourse The right of the Issuer to send a Chargeback to the Acquirer without a
Retrieval Request Notification for Transactions incurred at an S/E which is a
High Risk S/E according to the risk indicator in accordance with the Network
Chargeback policy.

Fraud Indicators The Fraud Indicator field is used to provide fraud mitigation indicators for a
variety of situations.

Fraud Liability Shift (FLS) A shift in financial liability for fraudulent Transactions that occurs if certain
requirements are met.

Fraud Probability Score A 5-byte numeric value on an Eligible Transaction that indicates to the
Issuer the probability of fraud.

Fraud Report Record (9644) The Fraud Report Record (9644) message delivers monthly fraud reports
from the GNS Fraud Repository in an electronic format. The Fraud Report
File is Network to Participant and no response is necessary.

Fraud Repository A Network fraud reporting database used by Participants to electronically

enter S/E and Cardmember fraudulent Transaction data.

Fraud Repository Update and The Fraud Repository Update (9324) message reports fraud Transaction
Response (9324/9334) data from the Issuer to the GNS Fraud Repository.

The Fraud Repository Update Record is returned to the Issuer as a Fraud

Repository Response (9334) message when the file is not fully or fully
accepted into the GNS Fraud Repository. Data elements are echoed back to
the Issuer.

Fraud to Gross (FTG) The ratio of fraudulent Transactions as compared to total Charge volume,
provided that both volume amounts are in the same currency.

Fraud Transaction Amount The total amount of the fraud Transaction in the Issuer’s settlement
currency identified as the Fraud Transaction Currency Code. The Fraud
Transaction Amount value also displays as the Record Hash Total.

Fraud Transaction Amount A + or - sign indicating the accounting effect of the Fraud Transaction
Accounting Effect Type Code Amount.

Page 10-36 October 2019

Definitions (continued)

Fraud Transaction Currency The currency code of the Fraud Transaction Amount.
Code

Fraud Transaction Currency The number of places the decimal must be moved to the left to correctly
Decimalization represent the Fraud Transaction Amount. (Monetary amounts are stored
without decimal places).

Fraud Transaction Date The local date when the fraud Transaction was executed at a Card Acceptor
location. If mail order or telephone order, the Fraud Transaction Date is the
date the goods were shipped.

Fraud Transaction Time The local time when the fraud Transaction was executed at a Card Acceptor
location.

Fraud Type Code A code identifying the type of fraud reported. Must be a valid Fraud Type
Code.

Fraud Type Description A description of the type of fraud reported. Descriptions include:
• Fraudulent Application
• Altered/Counterfeit Card
• Account Takeover
• S/E Fraud
• Lost
• Non Received - Including Returned Plastic
• Stolen - Including Stolen And Returned
• Mail/Phone Order - Including Internet Orders
• Card Not Present - Excluding Mail/Phone Order
• Convenience Check
• Other
• Skimming
• Unknown Fraud Type

Fraudulent Application An application for a Card Account submitted by an individual with the intent
to defraud an Issuer using another individual’s personal information in such
application.

October 2019 Page 10-37

Definitions (continued)

Fraudulent S/E An S/E that provides fraudulent information during the set up process with
the intent of defrauding American Express or the Acquirer, or a Merchant
whose S/E volume is comprised, or mostly comprised, of unauthorized or
fraudulent Transactions including, but not limited to:
• Billing Cardmembers for unauthorized Charges
• Imprinting, swiping, or keying additional Transactions for unauthorized
Charges before returning the Card to the Cardmember, or using stolen
Account information while the Cardmember retains possession of their
Card
• Keying in an unauthorized Transaction after being given a stolen
Account number by a collusive Participant.

Fulfillment The Documentation supplied by the Acquirer to support a Retrieval Request

from the Issuer.

Fulfillment Notification (1640) Acquirers can use the Fulfillment Notification (1640) message to:
• Send an automated fulfillment notification to an Issuer in response to a
Retrieval Request Notification (1642) for a Record of Charge (ROC) or
other documentation of a Transaction
• Supply the Issuer with a response to the Retrieval Request Notification
to show the action taken by the Acquirer

Full Transaction Amount This field contains the total sale amount plus applicable taxes and tips.

Function Code This code shows the reason for a message in its Message Type.

Funds Exchange The process where Participants transfer funds based on the net value of the
financial Transactions cleared for a given day or period.

Fusion Membership Rewards The Fusion Membership Rewards (9344) message contains data enabling
(9344) Cardmembers to redeem points with American Express contracted
Membership Rewards (MR) Partners through an automatic transfer
capability between the Participant and the MR partners through American
Express Network.

The Fusion Membership Rewards (9344) message is used to:

• Transmit the request to redeem points
• Acknowledge the receipt and processing of the file
• Return the file with a list of reject response codes
• Acknowledge the transfer request was completed by the MR partner

After the points transfer is complete, the response file returned to the
Participant verifies the points total and file sequence numbers.

Messages can pass through the Global Clearing and Settlement system or
can be routed to other systems.

Page 10-38 October 2019

Definitions (continued)

General Format Industry If the Format Code included in the 1240 Presentment message is 20 or 21,
Specific Detail (9240/9340) the General Format addendum must be sent with the Presentment.

Each First and Second Presentment can have multiple addenda records, but
can have only one Industry Specific Detail Addendum record.

Goods The process where Participants transfer funds based on the net value of the
financial Transactions cleared for a given day or period.

Gross Settlement Amount The Issuer or Acquirer Gross Settlement Amount calculated for an individual
Transaction. The currency is defined by the Issuer or Acquirer’s contractual
agreement.

Hash Total Amount A hash total of values in the Transaction Amount field (byte positions
32-46) for all financial messages (i.e., 1240, 1442, 1740, 1742, 1744).

Hash Total Amount (DAF A hash total of the values in the Transaction Amount field (byte positions
1325) 196-210) for all financial messages (i.e., 1240, 1442, 1740, 1742, 1744).
This excludes non-financial messages in the Daily Activity File.

Header Indicator Indicates the file is a Card Identification Number File update.

Hierarchy Level Number The hierarchy level of the S/E.

Level 02 is the lowest level and level 08 is the highest. This data is
mandatory for all S/Es that are members of a hierarchy (chain or group);
i.e., where the supplied New Hierarchy Participant Code is 02 or 03. How
hierarchy levels are reported in the S/E Demographic Message change
based on the functionality in the Participant's systems.

High Risk S/E An S/E designation assigned by AEGNS indicating that certain Transactions
conducted at the S/E may be charged back to the Acquirer under Fraud Full
Recourse Chargeback rights.

Host Stand-In A Network service that provides Authorization services on behalf of the
Issuer, based on Issuer parameters, when the Issuer is unavailable to the
host.

IAD Data Length The length of the discretionary data in the Issuer Application Data (IAD).

IATA Carrier Code The International Air Transportation Association (IATA) Carrier Code of the
agency that sold and ticketed the travel. It may, but does not necessarily,
indicate the transportation provider that travel was completed on.

October 2019 Page 10-39

Definitions (continued)

ICC Chip/PIN Indicator A code assigned by the Network to show if a Chip or a Chip and PIN
Transaction has occurred.

ICC Header Version Name The version header for the bit contents of the chip.

ICC Header Version Number The version number for the bit contents of the chip.

ICC System Related Data This is the data sent to and from the Integrated Circuit Card and used in an
AEIPS or Expresspay Transaction.

iCSC-3 Output A cryptographic value generated by the ACS/HSM for American Express
SafeKey.

Imprint Cardmember data transferred from a Card to a Transaction receipt to

complete a Transaction. An Imprint may be an electronic Imprint or a
manual Imprint. A manual Imprint is the imprint of the embossed data
taken with a manual imprinter. A pencil rubbing or photocopy of the Card is
not considered proof of a valid Imprint.

Industry Specific Detail The Industry Specific Detail Addenda messages supply more data about a
Addenda (9240/9340) First or Second Presentment for Transactions in special industries.

Installment Number The number of this installment (e.g., the third installment payment).

Insurance Coverage Date The start and end date of an insurance policy.
Range

Insurance Industry Specific The Insurance Industry Specific Detail message fields contain more data for
Detail (9240/9340) an insurance Transaction. If the Format Code included in the 1240
Presentment message is 04, the Insurance addendum must be submitted
with the Presentment.

Each First and Second Presentment can have multiple addenda records, but
can have only one Industry Specific Detail Addendum record.

Insurance Policy Number The number assigned to an insurance policy.

Insurance Policy Premium The frequency of an insurance premium (e.g., monthly, annual).
Frequency

Interest Rate The monthly and annual interest rates are expressed as a percentage (i.e.,
5% rather than 0.05).

Page 10-40 October 2019

Definitions (continued)

International Organization for The international body that develops and publishes standards for industry.
Standardization (ISO)

Internet The global system of interconnected computer networks that use the
Internet protocol suite to link billions of devices worldwide.

Internet Electronic Delivery Delivery, to the Cardmember, via Internet download or another file transfer
process, of Goods or Services purchased on the Internet.

Invoice Number A unique number assigned by the S/E to track a Transaction.

ISO 7813 Standard Track 1 The ISO 7813 Standard Track 1 layout is used to encode Track 1 on AEGNS
Layout Cards.

POS applications remove the Start Sentinel, the End Sentinel, and the
Longitudinal Redundancy Check (LRC) fields. Only the 76 bytes of data
between the sentinels is sent.

Other messages send the data between the sentinels (76 bytes) and the
Variable Length Indicator (LLVAR) (2 bytes).

Special Track 1 Data format definitions are found in each message that has
a Track 1 Data field.

ISO 7813 Standard Track 2 This layout is used for encoding Track 2 on all Network Cards.
Layout
POS applications strip these fields and send only the 37 bytes of data
between the sentinels.
Other messages send the data between the sentinels (37 bytes) plus the
2-digit variable length indicator to make a total of 39 bytes of data.

Special Track 2 Data format definitions are in each message that has a
Track 2 Data field.

Issuer Any entity (including, without limitation, American Express and American
Express Entities) authorized by American Express or an American Express
Entity to issue a Card and to engage in the Card Issuing Business

Issuer Application Data (IAD) Issuer defined application data. Refer to the AEIPS Chip Card Specification
manual for format instruction. This subfield may contain other data
depending on changes to the standards described in the AEIPS Chip Card
Specification manual.

Issuer Authentication Data Contains data sent from the Issuer to be retuned to the Chip Card for
Online Authentication.

October 2019 Page 10-41

Definitions (continued)

Issuer Authorized Amount The amount authorized by the Issuer stated in the respective settlement
currency.

Issuer DPP Authorization The deferred payment plan data for the Issuer Deferred Payment Plan.

Issuer DPP Pre-Authorization This is a pre-authorization request for deferred or extended payments,
including the plan code data.

Issuer Final Disposition Date The date when the Issuer revised the fraud Transaction data.

Issuer Fraud Chargeback The Message Reason Code is used when a Chargeback has been submitted
Reason Code for the fraud Transaction.

Issuer Fraud Chargeback Identifies the current financial responsibility status of a fraud Transaction.
Status Indicator

Issuer Gross Settlement The Network calculates this amount for a Transaction and uses the currency
Amount of the Issuer’s contractual agreement.
A Foreign Currency Factor mark-up by the Network is added to the value of
the final settlement currency.

Issuer Institution Identifier A unique 11-digit number assigned by AEGNS to an Issuer to identify
(IIN) Transactions belonging to that Issuer.

The first 6 digits of the IIN is the Bank Identifier Number (BIN).

Issuer Last Revision Date The local date when the Issuer revised the fraud Transaction data.

Issuer Last Revision Time The local time when the Issuer revised the fraud Transaction data.

Issuer Net Settlement Amount The Network calculates this amount for a Transaction, net of the Issuer’s
Rate Amount, in the currency defined by the Issuer's contractual
agreement.

Issuer Original Fraud The local date when the Cardmember reported the fraud to the Issuer, or
Disposition Date the Issuer discovered the fraud.

Issuer Original Fraud The local time when the Cardmember reported the fraud to the Issuer, or
Disposition Time the Issuer discovered the fraud.

Page 10-42 October 2019

Definitions (continued)

Issuer Override Request A feature available to Issuers through FraudNet that enables an Issuer to
submit a request to suspend Dynamic Fraud Management decline
Authorization Responses for specific Card Account Numbers during a period
defined by the Issuer.

Issuer Processor Identifier The unique identification number assigned by the Network to the
(IPN) designated Authorized Processor of an Issuer.

Issuer Script Data Contains Issuer Script Template(s) and Command(s) to be communicated
to the ICC in the Chip Card.

Issuer Settlement Currency The currency code of the Settlement Amount. The Network puts the value
Code in this field.

Issuer Settlement Date The date when the Network calculates the Issuer Settlement Amount for
the Transaction.

Issuer Settlement The number of places the decimal must be moved to the left to correctly
Decimalization represent the Issuer Settlement Amount. The Network puts the value in this
field.

Issuer Settlement Time The time when the Issuer Settlement Amount is calculated for one
Cardmember Transaction. The Network puts the same time on all
Transactions sent together (e.g., in the same file).

Issuer's Rate The difference, which may be expressed as a percentage, between the face
amount of a Charge and the price which the Issuer pays upon presentment
of a Charge to such Issuer.

Issuer’s/Network Rate The Issuer’s Rate is a rate, per Transaction amount, negotiated between
AEGNS and the Issuer. The Network Rate is a rate, per Transaction amount,
negotiated between AEGNS and the Acquirer, for settlement of inbound
Charges.

Issuer’s/Network Rate The Network calculates the total value of the Issuer’s/Network rate to be
Amount paid to or from the Network against Transactions.

Itemized Document Code The type of itemized documentation required for a message type.

Itemized Document Reference The reference number of the Transaction that transmitted supporting or
Number itemized documentation.

October 2019 Page 10-43

Definitions (continued)

Katakana Data Line A free form text entry in Katakana that further defines the Transaction.

Language Code Used to define the specific language or Double Byte Character language.

Legacy DPP An optional Network service that lets Charges to be billed in equal
installments as an alternative to 1 total billing.

Life Cycle Management Activities related to the ongoing management of Cardmember Account
information, including updates and changes, that may have a direct impact
on Transactions and digital capabilities.

Line Item Detail Key 1-2 A number used by the S/E to tell the Issuer of Line Item Detail data sent
outside of the Network.

Local or Foreign The location of the Acquirer and Issuer market regions. If the Acquirer and
Issuer are located in the same market region, then the Transaction is
considered local (for example, a Japanese Cardmember purchases goods in
Japan). If they are not in the same market region, it is considered to be
foreign (for example, a Japanese Cardmember purchases goods in France).

Lodging Charge Type Code Classifies the type of lodging charges on a Cardmember Transaction. Refer
to the Lodging Charge Type Codes section of the Codes Reference Guide for
a complete list of codes and descriptions.

Lodging Check In Date Lodging Addendum

The actual date the guest checked into the lodging establishment.

Travel/Cruise Addendum

This is the cruise departure date, also known as the sail date.

Lodging Check In Time The time a guest checked into a lodging establishment.

Lodging Check Out Date The time a guest checked out of a lodging establishment.

Lodging Check Out Time The time a guest checked out of a lodging establishment.

Lodging Folio Number The itemized statement of charges/credits incurred during a lodging stay.

Page 10-44 October 2019

Definitions (continued)

Lodging Industry Specific The Lodging Industry Specific Detail message fields contain more data for a
Detail (9240/9340) lodging Transaction. If the Format Code included in the 1240 Presentment
message is 11, the Lodging addendum must be submitted with the
Presentment.
Each First and Second Presentment can have multiple addenda records, but
can have only one Industry Specific Detail Addendum record.

Lodging Renter Name The name of the person who leased the lodging space.

Lodging Room Rate 1-3 Lodging Addendum

The nightly rate for one room, also known as the per diem rate, charged for
a stay in a lodging establishment.

Travel/Cruise Addendum

This is the total cost of the cruise.

Lodging Special Program Code More services, related to a lodging charge, offered by the S/E .

Lodging Stay Duration The number of nights a guest stayed at a lodging establishment.

Longitudinal Redundancy This unique character is in each magnetic stripe. The LRC immediately
Check (LRC) follows the End Sentinel, when the Card is read from the Start Sentinel. The
LRC is automatically generated by the embossing/encoding machine.

Market Specific Data This bit provides additional authorization data.

(Authorizations)

Market Specific Data (9240) The Market Specific Data Addendum message lets Participants in some
markets send market specific descriptive billing data (e.g., free form text
describing the Transaction in Kanji) between Participants through the
Network as double byte character sets.

The descriptive data passed through the Network from the Acquirer to the
Issuer with this addendum stays the same. This feature is only available for
Cardmember Transactions that occur in an Issuer’s local market.

Market Specific Data This is the provisioning-specific data unique to and supplied by the digital
(Provisioning) wallet provider.

Master Key A Cryptographic Key used to derive all other Encryption keys or a group of
keys.

October 2019 Page 10-45

Definitions (continued)

Matching Key An alphanumeric code that serves as a unique identifier through which
Issuers can match a First Presentment to corresponding detail data (such
as Purchasing Card Line Item Detail) that may have been supplied to the
Issuer through paths outside of the Network.

Matching Key Type Identifies the type of data referenced by the matching key.

Media Code The media used to initiate a Cardmember transaction processed by the
Network.

Member Type The type of member.

Merchant Refer to Service Establishment (S/E) (aka Merchant or Card Acceptor).

Merchant Category Code A code that identifies the industry in which the S/E does business.

Message Number A sequential number assigned by the message originator to each message
in a file. This number is used to monitor the integrity and continuity of the
data being exchanged.

Message Reason Code This code gives the cause of a First and Final Chargeback, Retrieval Request
Notification, File Acknowledgment, ATM and POS, and Reversal requests.

Message Transaction A number that associates and sequences all components of a primary
Sequence Number message type.

Message Type Identifier This code identifies the type of message sent by the forwarding institution.

Mobile Device An Issuer-approved and AEGNS-recognized electronic device (including, but

not limited to, a mobile telephone, tablet, or wearable device) that is
enabled to initiate Digital Wallet Program Transactions. Mobile Device is also
referred to as a “Mobile Proximity Payment Device (MPPD)” in some related
AEGNS manuals, guidelines, and resources.

MR Partner Code A unique code assigned by AEGNS to the Membership Rewards (MR)
partner (e.g., DL for Delta Airlines).

MR Partner Program ID The identification number associated with a particular Fusion Membership
Number Rewards program.

Page 10-46 October 2019

Definitions (continued)

MR Partner Response Code A Membership Rewards (MR) Partner specific code that indicates the MR
Partner response to a points transfer request.

MR Points Transfer The number of points the Cardmember is transferring to a Membership

Rewards (MR) Partner.

Multinational Accounts (MNAs) Service Establishments (S/Es) that have locations both inside and outside
the Territory, requiring American Express to coordinate servicing and other
customer relationship matters on a regional or global basis and being any
S/Es designated as such in writing by American Express.

Name of Insured The name of the insured. This could be different from the Cardmember
name.

Name of Service Establishment The phonetic spelling of the Katakana name of the Service Establishment,
in Katakana or outlet, at which the transaction took place.

National Use Data This is an ISO field that supplies Cardmember authentication data during
Authorization.

Net Settlement Amount The Issuer or Acquirer Gross Settlement Amount calculated for an individual
Transaction, net of the Issuer’s/Network Rate Amount, in the currency
defined by the Issuer or Acquirer’s contractual agreement.

Net Transaction Amount Euro The total transaction amount for all items purchased, excluding amounts
such as tax, shipping, duty, etc., stated in Euro.

Net Weight A freeform text field that describes the net weight of the shipment.

Network Refer to American Express Global Network (AEGN) or Network.

Network Fees The amount of commission and fees Participants pay for marketing,
operational, and other services provided directly or indirectly by AEGNS.

Network File Acknowledgment A Network message to the Participant to validate acceptance or rejection of
(1844) an outcleared file after edits and validation are complete.

Network Management Request The Network uses this message to manage the flow of messages and to
(1804) advise the Network of the availability of the Participant after scheduled or
unscheduled outages.

Network Management Use this message to respond to the Network Management Request (1804).
Response (1814)

October 2019 Page 10-47

Definitions (continued)

Network Processing Date The date the Network accepted or processed the transaction.

Network Processing Time The time the Network accepted or processed the Transaction.

Network Rate The difference, which may be expressed as a percentage, between the face
amount of a Charge and the amount that the Acquirer receives from the
Network for the Presentment.

Network Test Simulator A Web-based, on-demand tool used to facilitate Phase I (unattended)
testing/Certification, performed by Participants prior to obtaining full access
to the Network.

New Charges Transactions presented to the Issuer but not yet billed to the Cardmember.

New Hierarchy Effective Date The date the new hierarchy link went into effect.

New Hierarchy End Date The date the new hierarchy link ceased to exist.

New Hierarchy Participant Shows if the S/E is in a hierarchy (chain or group) of S/Es. If so, it shows if
Code the S/E is at the top of the hierarchy or a dependent in that hierarchy.

New Hierarchy Superior The S/E number of this Service Establishment’s new superior in the
Merchant hierarchy.

New Relationship Effective The date the new relationship link went into effect.
Date

New Relationship End Date The date the new relationship link ceased to exist.

New Relationship Superior The S/E number of the superior to this S/E in the relationship.
Merchant

No Show Reservation Charges which an S/E is permitted to submit in accordance with its contract
Transactions with an Acquirer which allow an S/E to recover some or all of the revenue
lost when reserving facilities or Services for a Cardmember who makes
advance commitment for their use but who does not utilize them. These
Transactions may also be referred to as “Assured Reservation Program”
Transactions.

Non-Financial Transaction A Transaction clearing through the Network that does not have a direct
impact to Settlement associated with the Transaction.

Page 10-48 October 2019

Definitions (continued)

Number in Party The number of people traveling together as a group.

Number of Installments The total number of installments requested or agreed to between the
Acquirer/Issuer and the Cardmember.

Number of Nights at Room Lodging Addendum

Rate 1-3
The number of nights lodging at a specified room rate.

Travel/Cruise Addendum

This is the length of the cruise in days.

Number of Report Lines Each Fraud report contains up to 9 report lines. This field identifies how
Present many of the 9 report line fields contains report data.

Offer ID The number of an offer in a marketing program.

Offer Type The applicable type for the offer in a marketing program.

Offline An operating mode in which no real-time connection is made to the

American Express Network.

Offline PIN A form of CVM where the PIN entry is validated by the AEIPS chip offline
and the validation results are returned to the terminal.

On Us ATM First and Second On Us ATM First and Second Presentments contain data related to one
Presentment (1340) Cardmember Transaction.

The On Us ATM 1340 messages must be submitted on a daily basis by those

Participants that own the Cardmember and S/E relationships or process On
Us Transactions.

On Us First and Final The On Us First and Final Chargeback Notification message is used to
Chargeback Notification process a Chargeback for a previous Transaction.
(1340)
The On Us 1340 messages must be sent daily by Participants that own the
Cardmember and S/E relationships or process On Us Transactions.

October 2019 Page 10-49

Definitions (continued)

On Us POS First and Second The On Us POS (1340) messages apply to Participants that own the
Presentment (1340) Cardmember and S/E relationships, and Multinational Accounts serviced by
the Participant. These messages are used to collect data on Transactions
that were not processed through the Network.
On Us First Presentment and Second Presentment (1340) messages contain
data related to a single Cardmember Transaction that occurred outside the
Network on a Participant’s card network. This data includes account
number, reference codes, debit or credit amount, and purchase description.
Participants must include, in their On Us First and Second Presentment
(1340) messages, their own Cardmembers’ Transactions that occur at
Multinational Accounts in the Participants’ markets.

The On Us POS messages are modeled after the Clearing and Settlement
financial messages but, like all Data Collection messages, must be
outcleared daily to the Network in a separate file. On Us Presentment
messages can be sent alone or with On Us Addenda (9340) messages.
These messages must have a Data Collection Header (9844) message
before and a Data Collection Trailer (9845) message after.

The On Us 1340 messages must be submitted on a daily basis.

On-Us Transaction A Transaction where the Issuer and the Acquirer are the same entity. For
ATM Transactions only, also a Transaction by an Issuer's Cardmember at an
ATM in such Issuer’s Participant ATM Network or Participant Shared ATM
Network.

One-Time Password (OTP) A dynamic code provided by the Issuer to the Cardmember as an added
source of fraud protection.

Online Authorization An Authorization where a real-time connection to the American Express

Network is made and an Authorization Request is submitted for decision.

Online PIN A form of CVM where the Acquirer sends an encrypted PIN value in the
online Authorization Request for validation by the Issuer.

Organization Identifier The unique identifier assigned, by AEGNS, to the Participant organization
that is sending or receiving Outclear/Inclear files to/from the Network.

Original Action Code A code that echoes the Action Code supplied on the Participant’s original file
transmission. Refer to the Action Codes section of the Codes Reference
Guide for a complete list of codes and descriptions.

Original Data Elements Data from the Authorization Request (1100 or 1200) or POS/ATM
Authorization Reversal Advice (1420) message.

Page 10-50 October 2019

Definitions (continued)

Original File Sequence Number The File Sequence Number reported on the File Header and File Trailer. The
File Sequence Number is sequential and assigned to each file by the file
originator. This ascending number starts at 000001 for the first file and
increments by one for all other files. The number rolls over after it has
reached 899999.

The Network echoes the field on the Network File Acknowledgment (1844)
as it is received. The Participant echoes the field on the Participant File
Acknowledgment (1824) as it is received.

Original Hash Total Amount The Hash Total Amount originally reported on the File Trailer. When the field
is not supplied, the Network will default to zeros.

Original Message Number The message number reported on the File Trailer of the original file. This
Count number is used to monitor the integrity and continuity of the data being
exchanged.

Original Total Count The total count of financial records originally reported on the File Trailer.

Original Transmittal Date The original transmittal date for the file transmitted to the Network.

Original Transmittal Time The original transmittal time for the file transmitted to the Network.

Originating Institution A unique identification number that identifies the original source of the data
Identification Code sent in the data record for one or more institutions.

Other Charges Amount The amount of miscellaneous charges.

Package Indicator The type of package the agent is booking.

PAN Expiration Date This is the Card Expiration Date embossed on the face of the Card.

PAN Sequence Number A number distinguishing between separate Cards with the same Primary
Account Number.

Partial Authorization An Authorization requested by an S/E and approved by an Issuer for a

partial amount - less than the total amount of the purchase.

Participant An entity which is an Issuer, Acquirer, or both.

October 2019 Page 10-51

Definitions (continued)

Participant File Participants must send the Participant File Acknowledgment (1824)
Acknowledgment (1824) message to the Network to acknowledge receipt of the Clearing and
Settlement Inclear File and the Daily Activity File. This message must follow
the File Header (9824) and come before the File Trailer (9825). The
Forwarding Institution ID In the File Header (9824) must match the
Receiving Institution ID from the Inclear file.

Participant Role Type Identifies the role of the organization for the reported activity.

Partner Defined Data A free form text field for Participant use.

Pass Through Fee Reason Text A freeform text description of the reason for the Pass Through Fee. The
(For Future Use) Pass Through Fee Reason Text field is mandatory for transaction based and
non-transaction based Pass Through Fee messages, but filler initialized to
spaces for outcleared ATM Fee messages.

Passenger Name The name of the passenger. This could be different from the Cardmember
name.

Payment Aggregator A provider of Payment Services. A Payment Aggregator is an entity that

contracts with an Acquirer to provide Payment Services to other Merchants
who may or may not have a direct relationship with Acquirers of American
Express Global Network Services (AEGNS).

Payment Token A surrogate PAN value that may be used to initiate payment Transactions.

Payment Token Post This message notifies Issuers of the result of a Provisioning Request.
Provisioning Notification The Network does not pass this message directly from the Token Requestor
(1120) to the Issuer. Instead, the Network responds to the Token Requestor, stores
the Transaction in the Store and Forward queue, and sends the message to
the Issuer from the queue.

Payment Token Post The Payment Token Post Provisioning Notification Response (1130) is sent
Provisioning Notification in response to a Payment Token Post Provisioning Notification (1120)
Response (1130) message.
The Network does not send this message from the Issuer to the Token
Requestor. The Network responds to the Token Requestor, sends the advice
to the Issuer, and accepts the Payment Token Post Provisioning Notification
Response (1130) response from the Issuer.

Payment Token Provisioning This message is passed by the Network to an Issuer to request that a Card
Request (1100) be provisioned a Token by the Network.

Page 10-52 October 2019

Definitions (continued)

Payment Token Provisioning This message is used by the Issuer to respond to a Payment Token
Response (1110) Provisioning Request (1100) sent by the Network.

Payment Type Amount 1-5 The installment payment amount.

Payment Type Code 1-5 The type of charge included in the First Presentment transaction amount
and the installment amount.

Personal Identification A four (4) to twelve (12) personal code that lets an Issuer identify the
Number (PIN) Cardmember for approval of an ATM or POS Transaction.

Pickup Location The location where a taxi passenger was picked up or where an auto rental
vehicle was picked up.

PIN Key Cryptographic Keys used to protect PINs.

Plan Description A description of the deferred payment plan.

Plan Type Shows if the Cardmember requests an Acquirer or Issuer sponsored

deferred payment plan.

Point of Sale (POS) Point of Sale (POS) device has the meaning contained in the current
Payment Card Industry Data Security Standard Glossary, Abbreviations and
Acronyms (refer to [Link]), and, as of the date of
this publication, it includes the following elements: hardware and/or
software used to process payment Card Transactions at S/E locations.

Point of Service Data Code This is a series of codes that shows the capability, security data, and
conditions of a terminal (or wallet) when a Transaction occurs at the point
of service (or during provisioning).

POS Authorization Adjustment Acquirers send the POS Authorization Adjustment Financial Advice (1220)
Financial Advice (1220) message when the last Transaction amount is less than the first authorized
amount. Issuers can then release funds that are greater than the last
Transaction amount.

POS Authorization Adjustment Issuers send the POS Authorization Adjustment Financial Advice Response
Financial Advice Response (1230) message to Acquirers to acknowledge the Issuer’s receipt of the
(1230) POS Authorization Adjustment Financial Advice (1220).

October 2019 Page 10-53

Definitions (continued)

POS Authorization Advice This message informs Issuers of an Authorization Request that is approved
(1120) or declined due to:
• Canceled status of the S/E
• Voice authorization referrals that the Acquirer resolves
• Transactions decisioned during Stand-In processing
• Online processing of refunds
• Fraud Probability Score and Recommendation Code (declined by Global
Network Services Authorization System (GNSAS) on behalf of a
certified Issuer)

POS Authorization Advice The POS Authorization Advice Response (1130) is sent in response to a POS
Response (1130) Authorization Advice (1120) message.
The Network does not send this message from the Issuer to the Acquirer.
The Network responds to the Acquirer, sends the advice to the Issuer, and
accepts the POS Authorization Advice Response (1130) response from the
Issuer.

POS Authorization Request This message is used to request Transaction authorization to purchase
(1100) goods or services at an S/E.

POS Authorization Response This message is used to respond to a Transaction Authorization Request to
(1110) purchase goods or services at an S/E.

POS Authorization Reversal Acquirers can generate online reversals and voids with this message.
Advice (1420) The 1420 is only an advice message. The POS Reversal Advice Response
(1430) is required.

POS Authorization Reversal This message is used to acknowledge the receipt of the POS Authorization
Advice Response (1430) Reversal Advice (1420).
The generation of the 1430 response confirms that the Network received
the 1420. It does not mean that exposure on the account is reversed.

POS First and Second First and Second Presentments contain data from one Cardmember
Presentment (1240) Transaction.
First and Second Presentments outclear from the Acquirer to the Network
and Inclear from the Network to the Issuer. Optionality is defined for the
outclear and inclear files.
All Presentment messages can be sent with one or more addenda
messages.

Page 10-54 October 2019

Definitions (continued)

Preferred/Delinquent File Use the Preferred/Delinquent File message to update the Network with
delinquency and preferred Cardmember status. The Preferred/Delinquent
File is a 51-byte fixed block record length format with a block size of 15453
bytes. If a record is in the file in one transmission, and not the next, the
Cardmember status returns to normal. There are no header and trailer
records in this file. If the Issuer does not send a new file, the file from the
day before is used to update the Network Preferred/Delinquent File.

Prepaid Card A Card for which the balance amount is pre-loaded onto the Card and will
be reduced as the Card is used by the Cardmember.

Prepaid Card Balance Inquiry A request for the available balance on a Prepaid Card, submitted on behalf
of a Cardmember by an S/E, as part of an Authorization Request sent to an
Issuer.

Prepaid Card Balance Return The available balance remaining on a prepaid card, returned following the
Prepaid Card Balance Inquiry.

Prepaid Card Partial An approval response with a partial authorization that also provides the
Authorization with Balance available balance on a prepaid card.
Return

Presentment The submission of Transaction data to the Network by Acquirers.

Presentment Amount The fee amount stated in the Presentment Currency.

Presentment Currency Code The numeric currency code of the Presentment amount.

Presentment Decimalization The number of places the decimal must be moved to the left to correctly
represent a Presentment Amount.

Primary Account Number A series of digits encoded into the magnetic stripe, stored on the chip of a
(PAN) Chip Card, and printed on the Card; used to identify the Card Issuer and
the Cardmember (CM) account or relationship. Valid American Express Card
account numbers begin with 34 or 37 and end in a valid check digit.

Primary Account Number The number of positions or length of the Primary Account Number.
Length

Primary Account Number, This field is a multipurpose field which provides the Primary Account
Extended Number or associated data.

Printed Card Security Code A 3-digit number printed on the back of the Card (3CSC) or a 4-digit
(PCSC) number printed on the front of the Card (4DBC/4CSC).

October 2019 Page 10-55

Definitions (continued)

Processing Code This is the service being requested.

Product Code Indicates the type of Card product used to accrue and redeem the Fusion
Membership Rewards points.

Program Code Represents the name of message data contained in the Program Specific
Data field.

Program Indicator Contains the code that tells Issuers that the Transaction qualifies for special
S/E programs or other types of programs that can have a liability shift or
special operating rules. If the Program Indicator is not provided, this field
must contain spaces.

Program Name The name of the marketing program. A marketing program can contain
more than one offer.

Program Progress Reports Reports required to be submitted by Participants on a regular basis,

containing information related to their GNS Issuer and/or Acquirer
Business.

Program Specific Data Contains data specifically required by the administrator of the specific
program for which the Program Specific Data Collection (9344) message is
used. The program’s administrator will supply data regarding the program
specific data to Participants during program setup and contract negotiation.

All Program Specific Data Collection Messages must contain the fields 1-20
of this message (bytes 1-208) and must be preceded by a Data Collection
File Header (9844) and followed by a Data Collection File Trailer (9845).

Contact your AEGNS Representative for more instruction regarding specific

programs available to Participants.

Page 10-56 October 2019

Definitions (continued)

Program Specific Data The Program Specific Data Collection (9344) message lets Participants send
Collection (9344) and receive data to and from program administrators or third party vendors
of special programs and services outside of the Network. Some of these
program administrators use American Express systems, but others use
vendor systems not affiliated with American Express. The Program Specific
Data Collection message is a standard procedure to send data necessary for
value-added programs available to Participants.

Program specific data collections messages include these:

• Acquirer S/E Fraud Detail
• ATM Location List
• Fusion Membership Rewards
• Chip Card Request and Response
• Batch Exception Update Request
• Batch Exception Update Response Count and Detail

Promotional Program An optional Network feature that facilitates marketing campaigns that drive
spend and loyalty by closing the redemption loop in local S/E commerce.

Promotional Program Debit Acquirers in designated markets receive the Promotional Program Debit File
File (1244) (1244) message from the Network. The message shows that a POS First
Presentment (1240) message with award Transactions was sent to an
Issuer.
Acquirers must send a Participant File Acknowledgment (1824) Message to
the Network to show they received the Promotional Program Debit File
(1244) message.
Acquirers can use the Promotional Program Debit File (1244) message to
debit Service Establishments (S/Es) for Promotional Program offers that are
funded by the S/Es.

Proof of Delivery A receipt of delivery that is signed by the Cardmember or an authorized

recipient at the valid address of the Cardmember.

Rail Industry Specific Detail The Rail Industry Specific Detail message fields contain more data for a rail
(9240/9340) Transaction. If the Format Code included in the 1240 Presentment message
is 06, the Rail addendum must be sent with the Presentment.

Each First and Second Presentment can have multiple addenda records, but
can have only one Industry Specific Detail Addendum record.

Real Time Exception Request The Real Time Exception Request (1304) message is used by Issuers for
(1304) one update done immediately to the status of the Card Account, as opposed
to updating data in a batch.

October 2019 Page 10-57

Definitions (continued)

Real Time Exception Response The Real Time Exception Response (1314) message is an online message
(1314) used by the Network to respond to the 1304 Real Time Exception Request
to add, update, or delete Cardmember Account status data. The response
message includes an Action Code to show the Network’s disposition for the
request.

Receiving Institution The unique institution identifier assigned to the Participant who received the
Identifier Transaction.

Receiving Organization The unique organization identifier assigned to the Participant who received
Identifier the Transaction.

Receiving Processor The unique institution identifier assigned to the Authorized Processor who
Institution Identifier received the Transaction from the Network.

Receiving Processor The unique organization identifier assigned to the Authorized Processor who
Organization Identifier received the Transaction from the Network.

Recommendation Code A 3-byte numeric value on an Eligible Transaction that corresponds to a

description of the fraud risk associated with the Transaction. Refer to the
Codes Reference Guide Fraud Indicator section for a complete list.

Record Count Indicates the total number of detail records in the file.

Record Expiration Date The date that the exception record is set to expire on the Network
Exception Database. This date often coincides with the date of the Card
expiration.

Record Hash Value This field is calculated when financial balancing is required for a given Data
Collection Message type.

Record Number in Original File A sequential number assigned to each record in a file by physical
occurrence. This number indicates the position of returned Transactions in a
file.

Page 10-58 October 2019

Definitions (continued)

Record of Charge (ROC) The receipt for a Cardmember's Charge, Credit, or ATM Transaction
containing the details of any Transaction carried out at an ATM or at the
POS. The form the ROC may take depends upon the method and equipment
used to capture the details of the Card and Transaction and may differ from
the following examples.

It may be an imprinted form, which carries an Imprint of the raised letter

and numbers on a Card, plus the handwritten Transaction information
recorded by the S/E. It may include the signature of the Cardmember.

It may be a paper receipt printed by a POS device printer and may be

signed by the Cardmember.

It may be the log entries made when an ATM dispenses cash.

AEGNS uses the following terms to refer to a ROC:

Original ROC, Substitute ROC, Transaction Log, and Copy.

Record Sequence Number A sequential number assigned to each record by the file originator. This
ascending number starts at 00001 for the first record and is incremented by
one for each record in the file.

Record Type A unique code that identifies a type of record.

Recurring Billing The billing method for periodic Transactions for a product or service agreed
to in writing by the Cardmember (e.g., membership fees to health clubs,
magazine subscriptions, insurance premiums).

Referral During an Authorization Request, the message relayed to the S/E via a POS
terminal advising the S/E to contact the Acquirer's service center.

Referral Response An Authorization Response that provides a final resolution to an

Authorization Request that initially resulted in a “please call” or “refer to
Issuer.”

Regional Specific Data Data used by the Issuer to enhance the Cardmember billing. The data is
specific to the Japan region and is populated from Bit 60 Market Specific
Data from either a POS Authorization Request (1100) or an ATM
Authorization Request (1200).

Reinstated Effective Date The date the Service Establishment was placed in a reinstated status if the
Status Code indicates reinstated.

Reject Reason Codes 1-10 Up to ten 4-byte fields that show the reason(s) for a message reject or
informational Reject Reason Code.

October 2019 Page 10-59

Definitions (continued)

Rejected Hash Total Amount Hash Transaction amount from all Presentments and Chargebacks rejected
by the Network.

Rejected Total Count Total number of messages rejected by the Network including File Header,
File Trailer, Presentments, Addenda Records, Chargebacks and Retrieval
Notification messages.

Remote Stand-In (RSI) This is an optional Issuer feature that lets a Remote Host do Stand-In if the
Acquirer cannot transmit to the Host.

Repl Code Digit 12 of the original Cardmember Account Number. This value represents
the number of replacement Cards issued (e.g., a “4” in the twelfth position
indicates four Cards have been issued to the Cardmember).

Report Batch Number A unique number assigned to the daily ATM Reconciliation report.

Report Category Code A code indicating the high level description of the goods or services of a
Transaction (i.e., retail, lodging, etc.).

Report Line 1-9 Lines 1-9 of the report data in the Fraud Report. The first byte of each line
contains a control character.

Report Name The name of the Fraud Report as it is printed on the report.

Requested Plan Details Contains the following data for the requested plan:
• Interest Rate
• Number of Installments
• Amount of Installment
• Finance Charges
• Amount Plus Finance Charges
• One Installment Above Requested Plan Details
• Two Installments Above Requested Plan Details
• One Installment Below Requested Plan Details
Two Installments Below Requested Plan Details

Requester Address Line 1-2 The two lines used to indicate the address of the person requesting the
Transaction.

Requester City The city name of the person requesting the Transaction.

Page 10-60 October 2019

Definitions (continued)

Requester Country Code The Country Code of the Country of the person requesting the Transaction.
Refer to the Country Codes section of the Codes Reference Guide for a
complete list of codes and descriptions.

Requester Email The email address of the person ordering the product or making the
purchase, if the requestor is not the Cardmember. Otherwise, this field
must be space-filled.

Requester Name The name of the person ordering the product or making the purchase, if the
requestor is not the Cardmember. Otherwise, this field must be space-filled.

Requester Postal Code The postal code of the person requesting the Transaction.

Requester Region Code The code representing the region (or equivalent, such as state or province)
for the requester of the purchase. Refer to the Region Codes section of the
Codes Reference Guide for a complete list of codes and descriptions.

Reserved Field This field is for AEGNS internal use.

Restaurant Industry Specific The Restaurant Industry Specific Detail message fields contain more data
Detail (9240/9340) for a restaurant Transaction. If the Format Code included in the 1240
Presentment message is 12, the Restaurant addendum must be submitted
with the Presentment.

Each First and Second Presentment can have multiple addenda records, but
can have only one Industry Specific Detail Addendum record.

Restaurant Item Amount 1-4 The amount of a restaurant item represented in First Presentment
Presentment Currency and Decimalization.

Restaurant Item Description The description that corresponds to a restaurant charge item.
1-4

Retail Department Name The retail store sales department name where the Transaction occurred.

Retail Industry Specific Detail The Retail Industry Specific Detail message fields contain more data for a
(9240/9340) department store or other retail Transaction. If the Format Code included in
the 1240 Presentment message is 02, the Retail addendum must be
submitted with the Presentment.

Each First and Second Presentment can have multiple addenda records, but
can have only one Industry Specific Detail Addendum record.

October 2019 Page 10-61

Definitions (continued)

Retail Item Amount 1-6 The unit cost of one retail item in First Presentment Presentment Currency
and Decimalization.

Retail Item Description 1-6 The description of the retail item purchased.

Retail Item Quantity 1-6 The number of retail items purchased in the Transaction.

Retrieval Request The request for either an Original ROC or a legible reproduction of the ROC
or other Documentation as identified in the Transaction data of the original
Presentment of the Transaction.

Retrieval Request Notification The Issuer sends a Retrieval Request Notification (1642) message to the
(1642) Acquirer through the Network to request data on a Transaction. The
Retrieval Request Notification (1642) must supply enough data for the
Acquirer to identify the Transaction. The Retrieval Request Notification
(1642) contains data from the First Presentment.

Role Type Code A code that uniquely identifies the Service Establishment’s business role.

Run Date The local date on which the Network creates the ATM Reconciliation file.

Run Time The local time when the Network creates the ATM Reconciliation file.

S/E Demographics Detail Data The required S/E Demographics Detail Data (9640) message contains
(9640) demographic data about new S/Es, updated data about existing S/Es, and
Multinational Accounts serviced by the Participant.

Acquirers must submit an initial file containing S/E demographics data for
all S/Es.

After the initial file submission, the S/E Demographics Detail Data (9640)
message must be submitted when these occur:
• An S/E becomes part of the Acquirer’s network
• The relationship between the Acquirer and S/E ends
• The S/E has a change in demographic data (e.g., address, etc.)
• AEGNS requests additions or changes to Multinational Accounts
serviced by the Participant

These messages must have a Data Collection Header (9844) message

before and a Data Collection Trailer (9845) message after. Authorized
Processors submitting for multiple Acquirers must submit files for each
Acquirer.

The Acquirer must submit an empty dataset (only 9844 Data Collection File
Header and 9845 Data Collection File Trailer) by the 5th of the next month
to show no changes in an Acquirer’s portfolio.

Page 10-62 October 2019

Definitions (continued)

S/E Floor Limit Amount The floor limit amount set by the Acquirer for this S/E. If no S/E floor limit is
set, the Network floor limit for S/Es in the S/E’s country is used. There is no
implied decimal point.

S/E Floor Limit Currency The currency used for the S/E Floor Limit Amount.

SafeKey American Express SafeKey is a security solution that leverages global

industry standards to detect and reduce online fraud, adding an extra layer
of security when Cardmembers shop online or on their mobile devices.

SafeKey Transaction ID The American Express SafeKey Transaction ID.

A constant literal = XID

SafeKey Transaction ID Value A unique number supplied by the SafeKey authentication process that
identifies the SafeKey Transaction.

Second Factor Authentication A value in the AEVV obtained from the ACS to supply second factor
Code authentication.

Second Presentment The second time a Transaction is presented from an Acquirer to the Issuer
after a First Chargeback.

Secondary ID A Data Type Code.

Security Related Control This field contains a variable length indicator and the Card Security Code
Information (CSC) or One-Time Password (OTP) supplied by the Acquirer.

Card Security Code includes the 5CSC or the Printed Card Security Code
(PCSC), which includes 3CSC and 4CSC (4DBC).

OTP is a dynamic 4-digit code provided by the Issuer to the Cardmember.

Security Related Control This field contains a variable length indicator and the Card Security Code
Information (Provisioning) (CSC) supplied by the digital wallet.

Card Security Code includes the 3CSC and 4CSC (4DBC).

Segment Fare Basis 1-4 The fare level of a segment of travel that the passenger is entitled to.

Sending Institution Identifier The unique institution identification number assigned to the sender of the
message. For ATM Fee messages, the Network uses the ATM Acquirer
Identifier assigned to the ATM Processor.

October 2019 Page 10-63

Definitions (continued)

Sending Organization The unique organization identifier assigned to the Participant who sent the
Identifier transaction to the Network.

Sending Processor Institution The unique institution identification number of the processing institution
Identifier sending this message. For ATM Fee messages, the Network uses the ATM
Acquirer Processor Identifier assigned to the ATM Processor.

Sending Processor The unique organization identifier assigned to the Authorized Processor or
Organization Identifier forwarding institution who sent the transaction to the Network.

Service Code A 3-digit number used in magnetic stripe mode Transactions that specifies
acceptance requirements and limitations for a magnetic stripe-read
Transaction.

Service Description Describes the current service being supplied.

Service Establishment (S/E) Any entity that has entered into a contract with an Acquirer wherein such
(aka Merchant or Card Acceptor) entity agrees to:

Permit any Cardmember to charge purchases of Goods and Services at or

from such entity by means of the Card, and Transfer such Charges to an
Acquirer.

Service Provider Any entity to which Cardholder Data and/or Sensitive Authentication Data is
provided, including those involved in the processing, storage, transmission,
and/or switching of Transaction data, Cardholder Data, and/or Sensitive
Authentication Data, such as Authorized Processors, third-party processors,
vendors, Mobile Entities, or their agents, representatives, or
subcontractors.

Settlement The process by which the Network computes the net totals that will be used
for Funds Exchange between Acquirers and Issuers.

Settlement Amount The amount of the fees in the settlement currency of the Participant.

Settlement Amount Approved The amount the Issuer approved for the Cardmember ATM Transaction in
the Acquirer’s settlement currency.

Settlement Amount Dispensed The actual amount dispensed to the Cardmember for the ATM Transaction.

Settlement Amount Requested The amount requested by the Cardmember at the ATM in the Acquirer’s
settlement currency.

Page 10-64 October 2019

Definitions (continued)

Settlement Calculation Date The Network date that the Transaction settlement is calculated for Acquirer
and Issuer settlement amounts for each financial Transaction message.

Settlement Conversion Rate The rate used to convert the dispensed amount to the settlement amount.
If no conversion is required, this value will be “000010000000”.

Settlement Currency Code The currency code of the Settlement Amount.

Settlement Date The date when the Network calculates the Settlement Amount for one
Cardmember transaction or for one fee. All Transactions transmitted
together (e.g., in the same file) by a Participant or all fees from the Network
have the same date.

Settlement Day A day on which the Settlement Bank of either the Acquirer or the Issuer and
AEGNS are open for business.

Settlement Decimalization The number of places the decimal must be moved to the left to correctly
represent the Settlement Amount.

Settlement Fee Other A fee charged by the Network for performing the foreign exchange
conversion.

Settlement Network Fee A fee paid to the Acquirer by the Network for the use of the ATM.

Settlement Time The time when the Settlement Amount is calculated for one fee. All fees
transmitted together are assigned the same time regardless of when
Network processing is completed.

Ship From Address Line 1-2 The two lines used to indicate the shipping address from where the goods
were shipped.

Ship From City The shipping address’s city name from where the goods were shipped.

Ship From Company Name The name of the company from which the goods were shipped. Please
check local tax authority requirements for all shipping-related fields.

Ship From Country Code The code representing the country from where the goods were shipped.

Ship From EU Country An indicator to specify if the country from where goods were shipped is a
member of the European Union.

October 2019 Page 10-65

Definitions (continued)

Ship From Postal Code The shipping address’s postal code from where the goods were shipped.

Ship From Region Code A code representing the region (or equivalent, such as state or province)
from which the goods were shipped. If there is no shipping, this field must
be space-filled.

Ship to Address Line 1-2 The two lines of the shipping address where the goods were shipped.

Ship to City The shipping address’s city name where the goods were shipped.

Ship to Country Code The code representing the country where the goods were shipped.

Ship to EU Country An indicator to specify if the country where goods were shipped is a
member of the European Union.

Ship to Name The name of the person or company where the goods were shipped.

Ship to Postal Code The shipping address’s postal code where the goods were shipped.

Ship to Region Code A code representing the region (or equivalent, such as State or Province)
where the goods were shipped.

Shipping Carrier The name of the carrier transporting the goods.

Shipping Charge The total shipping charge for all items purchased, including insurance if
applicable, stated in the Transaction currency as it was executed at the Card
Acceptor location.

Shipping Date The date the order was shipped.

Shipping Rate The rate used to calculate the charge for transporting goods by common
carrier. Two decimal places are implied.

Source Identification The operating center servicing the Card.

Operating Center

Sponsored Merchant An S/E that enters into a Sponsored Merchant Agreement with a Payment
Aggregator.

Page 10-66 October 2019

Definitions (continued)

Stand-In Authorization Stand-In occurs when an Issuer is offline, does not respond before timeout
(an 8 second timeframe), experiences a communications failure, or when
there are scheduled Issuer outages. In the above instances, the Network
uses Stand-In parameters supplied by the Issuer to approve or deny POS
Transactions.

Stand-In Parameter Issuer to Network: Stand-In parameter data if the Issuer signs off and
Information requests Stand-In by the Network. This field is 3 bytes, plus 350 bytes of
private use data.

Stand-In Parameter This field is present for advice messages when the Network supplied a
Information for DPP Requests Stand-In decision for a request that contains DPP data. For more instruction
regarding Stand-In, refer to the Exhibits Chapter of the Business and
Operational Policies manual.

Stand-In Parameter Acquirer to Network:

Information for Non-DPP
This field is present for advice messages when the Acquirer or S/E supplied
Requests a Stand-In decision.

Network to Issuer:

This field is present for advice messages when the Network supplied a
Stand-In decision for a request that does not contain DPP data.

For more instruction regarding Stand-In, refer to the Exhibits Chapter of the
Business and Operational Policies manual.

Start Sentinel Identifies the beginning of a magnetic stripe.

Status Code Defines the Service Establishment’s status (i.e., active, cancelled, etc.).
Refer to the Status Reason Codes section of the Codes Reference Guide for
a complete list of codes and descriptions.

Status Indicator Indicates the status of the data of this batch.

Status Reason Code Defines the reason the Service Establishment was cancelled or reinstated, if
the Status Code indicates cancelled or reinstated.

Stop Over Indicator 1-5 Indicates when a traveler spends more than four (4) hours at a destination
before the next leg of travel begins.

October 2019 Page 10-67

Definitions (continued)

Sub Product Code A Participant specific, AEGNS defined code that further defines the Card
product used to accrue and redeem the Fusion Membership Rewards points.

Support Software Version The embossing software version auto populated by the machine.

System Date The date the Funds Access System (FAS) accepted the ATM Transaction.

System Outage Interruption of Network systems services due to a computer system failure,
telecommunications failure, or regularly scheduled downtime.

System Time The time the Funds Access System (FAS) accepted the ATM Transaction.

Systems Trace Audit Number This is a unique (where applicable) trace number given to each Transaction
or provisioning request.

Tax Authority Location The location of the tax authority.

Tax Exempt Code 1-4 Identifies the tax-exempt code associated with the Tax Type Code.

Tax Liability Code A code that indicates which entity is liable for the taxes of the Transaction.

Tax Monetary Amount 1-4 The amount associated with the Tax Type Code, stated in the Transaction
currency as it was executed at the Card Acceptor location.

Tax Rate Percent 1-4 The percentage tax rate associated with the Tax Type Code.

Tax Reason Code This code tells Issuers in special markets how to calculate taxes for
Transactions.

Tax Reference Number An identifier linking tax amount(s) in the Transaction to an external taxation
requirement or regulation, taxation authority, tax documentation, or other
tax reporting requirement.

Tax Type Code 1-4 Uniquely identifies the type of tax payment associated with the Transaction
when the tax amounts can be categorized as one tax type.

Taxi Driver Identification A unique identifier assigned by the taxi company to the taxi driver.
Number

Page 10-68 October 2019

Definitions (continued)

Taxi Driver Tax Identification The Tax Identification Number (Tax ID) of the taxi driver.
Number Note: For Australia, this is the driver’s Australia Business Number (ABN).

Taxi Dropoff Location The location where the taxi passenger was dropped off.

Taxi Vehicle Identification A unique identifier assigned to the vehicle.

Number

Terminal Country Code Identifies where the terminal is located. The Network supplies the alpha
country code of the terminal at the Card Acceptor location.

Terminal Location Free form text that describes where the ATM is located.

Terminal Verification Results The status of various functions as determined by the terminal. The contents
(TVR) of this element are described in the AEIPS Chip Card Specifications.

Ticket Issue City The name of the city where the ticket was issued.

Ticket Issue Date The century, year, month, and day the ticket was issued. The default date is
the Transaction date.

Ticket Issuer Name The name of the Card Acceptor that issued the ticket.

Ticket Number Identifies the travel ticket for the Transaction.

Tier Value An AEGNS defined code that uniquely identifies each Issuer participating in
the Fusion Membership Rewards program.

Tip The amount of gratuity included in the purchase. The position of the implied
decimal point is determined by the Currency Code, Transaction (Bit 49).
Refer to the Currency Codes section of the Codes Reference Guide for a
complete list of codes and descriptions.

Token A surrogate PAN value consisting of a series of digits used to identify a

customer account or relationship.

Token Domain A set of rules that define the types of Transactions for which a Payment
Token may be used.

October 2019 Page 10-69

Definitions (continued)

Token Length The number of positions or length of the token.

Token Life Cycle Management Activities related to the ongoing management of Tokens and existing
business-as-usual processes throughout the Transaction Life Cycle.

Token Requestor An entity that initiates requests that PANs be tokenized, by submitting
Token Requests to a Token Service Provider.

Token Requestor ID (TRID) An 11-byte code pairing Token Requestor with Token Domain.

Token Service Provider (TSP) An entity that provides a Token Service.

Total Due The total amount owed by the Cardmember including:

(30 Day Balance) + (60 Day Balance) + (90 Day Balance) + (unbilled new
Charges) + (Transactions billed, but not delinquent).

Default is zero.

Total Number of Records Total number of records in the file. The header and trailer are not included
in this total.

Total Record Count The number of records in the Participant File Acknowledgment (1824) file.

Total Records Processed The total number of request records processed.

Total Records Received The total number of request records received in the request file.

Total Records Rejected The total number of rejected request records.

Total Settlement Dispensed Hash total of all Settlement Amount Dispensed fields of all records in the
Amount file.

Total Tax Amount The total amount of tax assessed at the point of sale for all items.

Track 1 Data This is the data encoded in a Track 1 magnetic stripe read or the data
stored in the Track 1 field on the chip of a Chip Card.

Track 2 Data This is the data encoded in a Track 2 magnetic stripe read or the data
stored in the Track 2 field on the chip of a Chip Card.

Page 10-70 October 2019

Definitions (continued)

Trailer Indicator Indicates the type of record.

Transaction A Charge, Credit, Cash Advance (or other cash access), or ATM Transaction.

Transaction Amount ATM The dispensed amount including service fees charged by the dispensing unit
in the Transaction Currency as it was executed at the Card Acceptor
expressed in the currency and decimalization of the Transaction amount.

Transaction Amount POS The sale or credit amount of the original Cardmember Transaction in the
Transaction currency as it was executed at the Card Acceptor location. This
is the exact sales invoice amount, including taxes. It does not include fees.

Transaction Amount, The maximum Transaction amount that the Network will block as part of the
Maximum Recurring Billing Cancellation Service.

Transaction Amount, Minimum The minimum Transaction amount that the Network will block as part of the
Recurring Billing Cancellation Service.

Transaction Certificate The Chip Card’s Transaction Certificate authenticates that the Cardmember
is using the Card by verifying the PIN or other data about the Cardmember.
This data is sent to the Issuer in its first format.

Transaction Code This code requests that the Network perform an action.

Transaction Currency Code The currency code in which the Transaction was executed.

Transaction Date The local date when the Cardmember’s original Transaction occurred at a
Card Acceptor location or sent by the designated Authorized Processor.
• For telecommunication Transactions, the Transaction Date is the date
the bill summary was presented.
• For Mail/Telephone/Internet Transactions, the Transaction date is the
Date goods are shipped.

Transaction Date (for Retrieval

Request (1642), Fulfillment The local date when a dispute message is created by a Participant.
Notification (1640), 1st & Final
CB (1442), 2nd P (1240))

Transaction Decimalization The number of places the decimal must be moved to the left to correctly
represent the Transaction Amount.

October 2019 Page 10-71

Definitions (continued)

Transaction Identifier (TID) A unique number given by the Network to identify a Cardmember
Transaction throughout its life cycle.

Transaction Indicator Indicates the status of the Transaction based on the Transaction logs at the
time of the authorization request.

Transaction Life Cycle The steps involved in processing Charge or Credit Transactions as viewed
from the perspective of the Network.

Transaction Status Used to determine the status of a Transaction. This table shows the
applicable code for the Participant and message type.

Transaction Time The local time when a Cardmember’s original Transaction occurred at a
Card Acceptor location or was sent by the designated Authorized Processor.
On a Second Presentment, this is the time the second presentment
Transaction was executed by the Acquirer or its designated Authorized
Processor.

Transaction to Presentment The rate used when the fee Transaction is not an authorized presentment
Conversion Rate currency that is used to convert the Transaction Amount to the Presentment
Amount in an applicable presentment currency.

If no conversion is required, this value will be 0000001.00000000. The

amount must be greater than zero.

Transaction Type Indicates the type of financial Transaction when a Chip Card is used.

Transit Access Terminal (TAT) An Expresspay-enabled POS Device that, when “tapped” by an
authenticated Expresspay Card, allows the Cardmember access to the
transit system.

Transmittal Date The date when the file was transmitted by the institution identified by the
Forwarding Identification Code.

Transmittal Time The time when the file was transmitted by the institution identified by the
Forwarding Identification Code.

Transport Data This field is used by the Participant to identify the file, S/E, or the
Transaction. This field, if populated, will be returned unchanged to the
Participant.

Travel Agency Name Indicates the name of the travel agency that sold the travel arrangements.

Page 10-72 October 2019

Definitions (continued)

Travel Agency Number The industry assigned identifier for a travel agency. Must be a valid IATA
Travel Agency Identifier.

Travel Document Type Code Classifies the nature of a travel carrier (e.g., airline, railway, etc.)
document.

Travel Process Identifier The IATA Carrier Number of the travel carrier (e.g. airline, railway, etc.) that
sold and ticketed the travel; or if the travel was sold through a travel
agency, the transportation provider on which the travel will be conducted;
or for a non-IATA carrier, a 3-digit code of “000”.

Travel Transaction Type Code Classifies the type of charge used in an airline or rail Transaction.

Travel/Cruise Industry The Travel/Cruise Industry Specific Detail message fields contain more data
Specific Detail (9240/9340) for a Travel/Cruise Transaction. If the Format Code included in the 1240
Presentment message is 14, the Travel/Cruise addendum must be sent with
the Presentment.

Each First and Second Presentment can have multiple addenda records, but
can have only one Industry Specific Detail Addendum record.

Type of Plan Code The type of payment plan offered to the Cardmember.

Type of Policy The type/classification of a policy (i.e., life, health, etc.).

Unpredictable Number A random number generated by the terminal to supply uniqueness into the
cryptogram value generated.

User Number The approved person providing data to the Network.

Valid Billing Unit Code The Valid Billing Unit Code indicates the specific purpose for the fee being
charged in the Fee Collection Message (1744)

Variable Length Indicator The total length of variable data in the field (not including VLI).
(VLI)

Voice Referral Handling An AEGNS service that enables indirect voice communication between an
Service Issuer and their Cardmember during an Authorization Request at a Service
Establishment (S/E).

Wallet Provider ID A two byte code, assigned by the Network, used to identify the Wallet
Provider.

October 2019 Page 10-73

Page 10-74 October 2019

Chapter 11 Index
Numerics Average Revolved Balance 7-15
B
9324
Fraud Repository Update Below Floor Limit Transactions
how to submit 6-2 for Authorization 2-6
9334 Beta Testing
Fraud Repository Response 6-6 certification 5-4
9644
Fraud Report Record 6-12
C
A Card
Identification Number Detail Record
Acquirer message layout 4-51
Authorization messages 2-13 programming notes 4-52
contract agreement 2-28 Identification Number Header Record
Detail report 7-54 message layout 4-46
Local and Inbound Discount Business and programming notes 4-47
Transactions by Industry report 7-23 Identification Number Trailer Record
Reports 2-18 message layout 4-55
responsibilities 4-2 programming notes 4-56
role 2-2 Security Code Key (CSCK) 4-39
S/E Fraud Detail Report 7-111 usage parameters 4-27
S/E Fraud Summary Report 7-109 CAS
Service Establishments and Locations in Force Activity Summary – Authorizations Activity
by Industry report 7-20 report 7-27
Acronyms 9-1 Activity Summary – Entry Activity Section
AEIPS Chip Card Specification manual 8-1 report 7-37
AEIPS Terminal Technical Manual 8-1 Activity Summary – Summary by Point of Sale
amount report 7-33
format standards 3-2 Activity Summary – Summary by S/E Type
ANSI X4.16 report 7-35
Track 1 certification
message layout 4-16 Acquirer requirements 5-12
programming notes 4-17 Beta Testing 5-4
Track 1 and 2 formatting 4-15 for Network features 5-13
Track 2 Issuer requirements 5-11
message layout 4-21 Network Test Simulator 5-14
programming notes 4-22 Phase I 5-3
Authorization unattended testing 5-6
Below Floor Limit Transactions 2-6 Phase II 5-3
Decline Transaction Stand-in Detail report connectivity testing 5-8
7-57 Phase III 5-4
DPP Transaction Detail Report 7-49 testing with AEGNS 5-9
exceptions 2-5 phases
messages for Acquirers 2-13 overview 5-3
Referred Stand-in Detail report 7-59 change bar 1-2
reports 7-26 Check Digits
Transaction Detail report 7-51 computing for PAN
Transaction Edit Error Detail report 7-43 PAN
Transaction Life Cycle diagram 2-8 Check Digit Computation 4-26
Transaction Stand-in Detail report 7-47 Clearing and Settlement
Authorization Stand-In 2-5 Reports 7-63
Average Merchant Discount Rate Codes Reference Guide 8-1
by Industry 7-25

October 2019 Page 11-1

contract agreement types 2-28 time 3-2

creating Personal Identification Numbers 4-28 formatting
Cryptographic Keys Primary Account Numbers 4-25
equipment to protect 4-33 fraud
CSC by Acquirer Market and Cardmember Market
generation 4-40 report 7-106
hardware encryption 4-39 by Acquirer Market and Industry report 7-107
location on the Card 4-39 by Acquirer Market, Cardmember Market and
CSCK Fraud Type report 7-108
Card Security Code Key 4-39 by Issuer and Industry report 7-97
D by Issuer Market and S/E Market report 7-96
by Issuer Market, S/E Market and Fraud Type
Daily Settlement Advisement report 7-64 report 7-98
data mitigation tools 6-15
formats 3-6 prevention services 6-1
date rejected update file 6-8
format standards 3-2 reports 7-95
debit/credit amount GLOBE 6-10
format standards 3-2 Message Transaction Sequence Number
Definitions 10-1 6-12
DES Number of Report Lines Present 6-12
implementation 4-39 Reports delivery 6-9
Repository Response
E frequency 6-8
Fraud Report Record 9644 6-12
Emergency Card Replacement 4-59 Fraud Repository Response 9334 6-6
encryption Fraud Repository Update 6-2
hardware 4-32 file structure 6-8
TDEA 4-39 how to submit 6-2
encryption room Fraud to Gross Ratio 6-10
requirements 4-31
equipment to protect G
Cryptographic Keys 4-33
Exception Detail Report 7-56 GLOBE
exceptions Fraud Reports 6-10
Authorization 2-5 technical certification 5-1
External File Tracking Report 7-71–7-73 GNS Fraud Repository 6-1
GNS FraudNet 6-1, 6-9, 6-13, 6-14
F Gross Settlement Summary Report 7-77–7-79

feature based H
functionality 2-27
feature certification 5-13 hard supplier
fields Thales 4-39
optionality 3-5 hardware encryption 4-39
fields, defined 3-3 hardware vs. software
Financial messages encryption 4-32
DAF File Returned 10-23 hash amount
format format standards 3-2
data 3-6 High Risk
standards Indicators
amount 3-2 Service Establishment 6-13
date 3-2 submitting 6-13
debit/credit amount 3-2 S/E List
hash amount 3-2 accessing 6-14

Page 11-2 October 2019

I ANSI X4.16 4-21

ANSI X4.16 Track 1 4-16
IATA Airline Coding Directory 8-1 Card Identification Number Detail Record 4-51
icon Card Identification Number Header Record
trash can 1-3 4-46
Inclear Card Identification Number Trailer Record
process 2-7 4-55
Independent Operator 2-28 ISO 7813 Standard Track 1 4-4
informational Reject Reason Codes ISO 7813 Standard Track 2 4-10
definition 3-7 messages
ISO 8-1 how to use 3-9
4909 Track 3 4-14 MIS Fraud reporting 6-1
7813 Standard Track 1 MR 7-17
message layout 4-4 N
programming notes 4-5
7813 Standard Track 2 NCL (Network Card License) 2-28
message layout 4-10 Net Settlement Summary Report 7-74–7-76
programming notes 4-11 Networ Test Simulator
7813 Track 1 and 2 formatting 4-3 certification 5-14
8583 8-1 Network
IEC 7811-2 4-1 Card License NCL 2-28
Issuer defined 2-3
responsibilities of 4-1 feature based functionality 2-27
role 2-2 mandatory functionality 2-26
Issuer Account Balances Outstanding, Write-offs, Non-Actioned Rejected Transaction reports
and Recoveries report 7-14 7-102–7-105
Issuer Authorization messages 2-19
Issuer Billed Business and Transactions by
O
Industry and Card Product report 7-9–7-14
OpsNet
Issuer Card Statistics by Product report 7-6–7-8
reports 7-115
Issuer Fraud Summary report 7-100–7-101
overview
Issuer Gross Fraud Update report 7-99
certification phases 5-3
Issuer MR Statistics by Product report 7-17
technical certification 5-1
J P
Joint Venture 2-28
PAN Scrambling Routine 4-44
K Participant
defined 2-2
Key profiles 2-29
creation and exchange procedure (exporting system & software responsibility 3-16
Participant) 4-34 Personal Identification Number
Management 4-30 creating 4-28
Key component Phase I
requirements 4-32 certification 5-3
L Phase II
certification 5-3
life cycle Phase III
of Transaction 2-4 certification 5-4
PIN
M working with 4-25
Primary Account Number 4-25
Mandatory Network functionality 2-26
Scrambling Routine 4-44
Membership Rewards, see MR
Primary Account Numbers 4-25
message layout

October 2019 Page 11-3

computing check digits 4-26 hardware supplier 4-39

profiles of Participants 2-29 The Network 2-3
Program Progress Reports 7-4 TID (Transaction Identifier)
programming notes for tracking fraud Transactions 6-6
ANSI X4.16 Track 1 4-17 time
ANSI X4.16 Track 2 4-22 format standards 3-2
Card Identification Number Detail Record 4-52 Top 40 S/Es 6 Month Detail Report 7-114
Card Identification Number Header Record Top 40 S/Es 6 Month Summary Report 7-113
4-47 Track 3 ISO 4909 4-14
Card Identification Number Trailer Record Transaction Life Cycle 2-4
4-56 trash can icon 1-3
ISO 7813 Standard Track 1 4-5 types of contract agreements 2-28
ISO 7813 Standard Track 2 4-11 U
R
Unacknowledged Voids, Refunds, and Reversals
Reject Reason Codes Report 7-45, 7-46
informational definition 3-7 Z
reports
delivery 7-1 Zone Master Keys 4-38
for
authorization 7-26
clearing and settlement 7-63
fraud 7-94
OpsNet 7-115
program progress 7-4
for Acquirers 2-18
list of 7-1
overview 7-1–7-3
S
scrambling routine for PAN 4-44
Self-Validation Testing 5-3
Service Establishment
High Risk Indicators
submitting 6-13
On Us relationships 10-49, 10-50
services
fraud prevention 6-1
Stand-In
for Authorization 2-5
subfields
Bit 55 format 3-7
variable length 3-4
Subsidiary/Working Keys
exchanging 4-37
T
TDEA 4-39
technical certification
GLOBE 5-1
overview 5-1
Test Cards 4-24
Thales

Page 11-4 October 2019

October 2019 Page 11-5

Network Specifications - Authorization October 2019
No ratings yet
Network Specifications - Authorization October 2019
348 pages
Network Specifications - Financial - NonFinancial October 2019
100% (1)
Network Specifications - Financial - NonFinancial October 2019
876 pages
BASE24 R6.0 Post v10 2017-03-17 - BIC ISO Standards Manual
No ratings yet
BASE24 R6.0 Post v10 2017-03-17 - BIC ISO Standards Manual
308 pages
API Implementation Guide - V2.1
No ratings yet
API Implementation Guide - V2.1
105 pages
BASE24-Pos SPDH Device Config
No ratings yet
BASE24-Pos SPDH Device Config
462 pages
AEXP Codes Reference Guide - October 2021
No ratings yet
AEXP Codes Reference Guide - October 2021
540 pages
Visa TADG
100% (1)
Visa TADG
212 pages
MC Onbehalf Key MGMT Interface Spec
100% (1)
MC Onbehalf Key MGMT Interface Spec
100 pages
VSDC Perso 2 0 2 June2014
100% (1)
VSDC Perso 2 0 2 June2014
128 pages
Part VIII Display Card Specification
No ratings yet
Part VIII Display Card Specification
48 pages
DCI Contactless D-PAS Acquirer Host Test Plan v1.2
100% (1)
DCI Contactless D-PAS Acquirer Host Test Plan v1.2
88 pages
Visa Tap To Phone Framework
No ratings yet
Visa Tap To Phone Framework
19 pages
VOP Enrollment API August 2016
100% (1)
VOP Enrollment API August 2016
45 pages
BASE24-eps 3.0.25, 2.1.37, and 2.0.45 - Service Pack Release Notes First Quarter 2025
No ratings yet
BASE24-eps 3.0.25, 2.1.37, and 2.0.45 - Service Pack Release Notes First Quarter 2025
159 pages
Users Guide
100% (1)
Users Guide
51 pages
Vip System Services
No ratings yet
Vip System Services
567 pages
05 v.I.P. System BASE I Processing Specifications 0847
No ratings yet
05 v.I.P. System BASE I Processing Specifications 0847
224 pages
M Tip
No ratings yet
M Tip
60 pages
04 v.I.P. System Reports 0852
No ratings yet
04 v.I.P. System Reports 0852
401 pages
3DS 2.2 FAQs - v1.0 JULY 2019 FINAL
No ratings yet
3DS 2.2 FAQs - v1.0 JULY 2019 FINAL
4 pages
Security Rules and Procedures 30 July 2015
100% (1)
Security Rules and Procedures 30 July 2015
227 pages
IPM Clearing Formats Overview 2022
No ratings yet
IPM Clearing Formats Overview 2022
1,300 pages
Secure IoT Payments with Digital Wallets
No ratings yet
Secure IoT Payments with Digital Wallets
11 pages
Vip System Base I Tech Specs Volume 2
No ratings yet
Vip System Base I Tech Specs Volume 2
352 pages
Chip Card Acceptance Device Ref Guide 6 (1) .0
No ratings yet
Chip Card Acceptance Device Ref Guide 6 (1) .0
143 pages
FHFHMR
No ratings yet
FHFHMR
208 pages
EMVCo White Paper On Payment Account Reference v2.1.1 Final
No ratings yet
EMVCo White Paper On Payment Account Reference v2.1.1 Final
25 pages
PP MTIP UserGuide Dec2011
No ratings yet
PP MTIP UserGuide Dec2011
201 pages
BASE24-eps 3.0.23, 2.1.35, and 2.0.43 - Service Pack Release Notes Third Quarter 2024
No ratings yet
BASE24-eps 3.0.23, 2.1.35, and 2.0.43 - Service Pack Release Notes Third Quarter 2024
253 pages
5.0 Card Manufacturing
No ratings yet
5.0 Card Manufacturing
56 pages
UPI QuickPass Testing Guide For Acquirers - V201803
No ratings yet
UPI QuickPass Testing Guide For Acquirers - V201803
14 pages
03 v.I.P. System Services Volume 2 0853B
100% (1)
03 v.I.P. System Services Volume 2 0853B
531 pages
JCB Terminal Test Cases Guide
No ratings yet
JCB Terminal Test Cases Guide
8 pages
Us Visa Contactless Transit Terminal Testing v2
No ratings yet
Us Visa Contactless Transit Terminal Testing v2
5 pages
MCHIP 4 Version 1.1 Security and Key Management
No ratings yet
MCHIP 4 Version 1.1 Security and Key Management
93 pages
MC - Member ICC Testing Procedures
100% (1)
MC - Member ICC Testing Procedures
161 pages
BASE24-eps 3.0.26 - HA Probe User Guide
No ratings yet
BASE24-eps 3.0.26 - HA Probe User Guide
62 pages
LAC Intraregional IRF Guide
100% (1)
LAC Intraregional IRF Guide
81 pages
Mastercard Global Transit Implementation Guide
No ratings yet
Mastercard Global Transit Implementation Guide
80 pages
Quick Chip For EMV and QVSDC, Specification Version 2.0 (Visa, 2017)
100% (1)
Quick Chip For EMV and QVSDC, Specification Version 2.0 (Visa, 2017)
18 pages
PayPass v3 TTAL2-Testing Env Nov2013
No ratings yet
PayPass v3 TTAL2-Testing Env Nov2013
63 pages
BPC Card Management Solutions Overview
No ratings yet
BPC Card Management Solutions Overview
7 pages
Visa Settlement Funds Transfer Guide
No ratings yet
Visa Settlement Funds Transfer Guide
50 pages
Anexo 5 Major US Bank Replaces Base24 With OmniPayments - 1335820935474
No ratings yet
Anexo 5 Major US Bank Replaces Base24 With OmniPayments - 1335820935474
4 pages
Mpos Development Guidelines
100% (1)
Mpos Development Guidelines
10 pages
Security Guide of UnionPay Card Personalization+Service+Provider
100% (1)
Security Guide of UnionPay Card Personalization+Service+Provider
41 pages
BASE24-eps 3.0.22 - Extract and Reporting User Guide
No ratings yet
BASE24-eps 3.0.22 - Extract and Reporting User Guide
135 pages
Visa Public Key Tables June 2014
No ratings yet
Visa Public Key Tables June 2014
8 pages
J-Secure 2.0 Acquirer Implementation Guide - v1.2
100% (1)
J-Secure 2.0 Acquirer Implementation Guide - v1.2
32 pages
PIN Security RQMT 18-3 Key Blocks 2022 v1.1
No ratings yet
PIN Security RQMT 18-3 Key Blocks 2022 v1.1
15 pages
Visa Merchant Data Standards Manual
100% (1)
Visa Merchant Data Standards Manual
120 pages
Key Block August 2022
No ratings yet
Key Block August 2022
7 pages
Visa Usa Interchange Reimbursement Fees 2015 April 18
No ratings yet
Visa Usa Interchange Reimbursement Fees 2015 April 18
4 pages
EMV Card Basics: Seminar On Demand: Study Guide
No ratings yet
EMV Card Basics: Seminar On Demand: Study Guide
10 pages
Interlink Operating Regulations
100% (1)
Interlink Operating Regulations
374 pages
Fa Batch
100% (1)
Fa Batch
190 pages
TIP Entire Manual
No ratings yet
TIP Entire Manual
105 pages
Codes Reference Guide October 2019
No ratings yet
Codes Reference Guide October 2019
560 pages
AMEX - October 2022 - Codes Reference Guide
No ratings yet
AMEX - October 2022 - Codes Reference Guide
477 pages
Network Participant Updates - October 2019
No ratings yet
Network Participant Updates - October 2019
156 pages

Network Specifications - Instructions October 2019

Uploaded by

Network Specifications - Instructions October 2019

Uploaded by

AXgjbe^FcXV\Y\VTg\baf

GLOBAL NETWORK SERVICES

© 2019 American Express Travel Related Services Co., Inc.

October 2019 Page i

Phase I: Unattended Testing.............................................................................. 5-6

Page ii October 2019

Network Fee Summary Report ......................................................................... 7-80

October 2019 Page iii

Page iv October 2019

October 2019 Page v

Page vi October 2019

October 2019 Page vii

Page viii October 2019

Table 7-52. Non-Actioned Rejected Transaction Reports: Definitions ........................ 7-103

October 2019 Page ix

Page x October 2019

xii October 2019

Overview The Network Specifications - Instructions manual contains:

October 2019 Page 1-1

About This Document

Summary of Important changes are in the Summary of Changes on page xi.

Figure 1-1. Change Bar Example

continued on next page

Page 1-2 October 2019

Trash Can Icon A trash can icon shows erased text.

October 2019 Page 1-3

Page 1-4 October 2019

Chapter 2 American Express Global Network

AEGNS Since 1996, American Express has been pursuing a strategy of

October 2019 Page 2-1

Issuer Role The Network accepts Transactions from Issuers authorized by

Page 2-2 October 2019

Overview The Network is a global communication system that transmits

AEGNS Services AEGNS has these services:

October 2019 Page 2-3

The Transaction Life Cycle

Steps in the The Transaction life cycle has these steps:

Authorization Table 2-1 Authorization on page 2-5 describes step 1 of a

continued on next page

Page 2-4 October 2019

Table 2-1. Authorization

Authorization Exceptions to the Transaction life cycle in Table 2-1 are:

continued on next page

October 2019 Page 2-5

• Below Floor Limit Transactions - An Authorization Response

Table 2-2. Clearing

Page 2-6 October 2019

Table 2-2. Clearing (continued)

Settlement Step 3 of the Transaction life cycle is Settlement.

Table 2-3. Settlement

Refer to the Clearing and Settlement and Financial Messages

continued on next page

October 2019 Page 2-7

2. Salesperson 3. Device connects

9. S/E receives 10. After sale, S/E

Authorization message a First Presentment message, adds to batch

13. The Network opens batch file, sorts

6. Issuer’s system checks

Cardmember’s information and

continued on next page

October 2019 Page 2-8

Fraud Table 2-4 Fraud describes step 4 of a Transaction life cycle.

Table 2-4. Fraud

continued on next page

October 2019 Page 2-9

continued on next page

Page 2-10 October 2019

1.1 Fraud Repository 5.1.1 Fraud

updated (9324). Sends Repository

Figure 2-2. Fraud Transaction Life Cycle

October 2019 Page 2-11

Acquirer This section lists messages and associated functionality for

continued on next page

Page 2-12 October 2019

Table 2-5. Available Authorization Messages for Acquirers

October 2019 Page 2-13

AXgjbe^FcXV\Y\VTg\baf