SPC Delimited File Reports v7.1.0.0

D ELIMITED F ILE R EPORTS
File Format Specification
June 2019
Version 7.1.0.0
Copyright © 2019 JPMorgan Chase & Co. All rights reserved.
All Information contained herein is STRICTLY CONFIDENTIAL AND PROPRIETARY – Not for Use
or Disclosure outside JPMorgan Chase Bank N.A., and its respective affiliates or customers.
This publication is for informational purposes only, and its content does not represent a contract or
agreement, in any form. Chase reserves the right to alter product specifications without notice. No part of
this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical,
including photocopy, recording, or any information storage or retrieval system, without Chase’s
permission.
All brand names and product names used in this document are trade names, service marks, or registered
trademarks of their respective owners. No part of this publication shall be construed as any license,
express or implied, to any of the respective owners’ trade names, service marks or trademarks or any
patents, copyrights or other intellectual property of JPMorgan Chase Bank, N.A., and its respective
affiliates and shall not be used or furnished as any reference and/or in connection with any
advertisement, announcement, release or promotional materials by any persons other than such
respective owners.
What’s New
The following updates have been made to this version of the guide since Release 7.0.0.0.
Changed the report data record of the ACT0082 Dynamic Debit Routing Comparison Dynamic Debit
Routing Comparison.
 Added field number 5, the Average Ticket Amount field.
 Changed the name of field number 7 from Sale Amount to Transaction Amount.
 Added field number 13, the Debit Type field.
 Updated the sample record.
 Updated the maximum length of the Average Ticket Amount field.
 Updated the maximum length of the Routed Network Calculated Cost field.
 Updated the maximum length of the Other Network Calculated Cost field.
3
Table of Contents
What’s New ............................................................................................................................................... 3
Table of Contents ..................................................................................................................................... 4
Format Specifications ................................................................................................................................. 6
Report Layouts Overview ....................................................................................................................... 10
File Naming Convention ..................................................................................................................... 12
Numeric Formatting ............................................................................................................................ 14
Other Formatting ................................................................................................................................ 16
Account Masking ................................................................................................................................ 16
Appendix Section ................................................................................................................................ 16
File Sort Order .................................................................................................................................... 17
Record Layouts ......................................................................................................................................... 20
File Header ............................................................................................................................................. 20
Financial Reports .................................................................................................................................... 22
Financial Reports – Deposit Activity Summary (FIN0010) ................................................................. 22
Financial Reports – Deposit Activity Transfer Summary (FIN0010T) ................................................ 28
Financial Reports – Transaction Summary (LNK010A) ..................................................................... 32
Financial Reports – Reject Summary (ACT0033) .............................................................................. 37
Financial Reports – Submission Listing (ACT0012) ........................................................................... 41
Financial Reports – Service Charge Detail (FIN0011) ....................................................................... 46
Financial Reports – Debit Authorization Aging (ANS0039) ................................................................ 53
Financial Reports – Merchant Settlement Aging (ANS0041) ............................................................. 58
Financial Reports – Exception Detail (ACT0002) ............................................................................... 63
Financial Reports – Deposit Detail (ACT0010) .................................................................................. 73
Financial Reports – Terminal/Batch Detail (ACT0027) ...................................................................... 87
Financial Reports – Authorization Detail (ACT0036) ......................................................................... 92
Financial Reports – Interchange Qualification Detail (ANS0013) .................................................... 105
Financial Reports – Interchange Qualification Summary (ANS0016) .............................................. 110
Financial Reports – Interchange Downgrade Summary (ANS0017)................................................ 115
Financial Reports – IBAN Conversion Detail (ACT0069) ................................................................. 120
Financial Reports – Mastercard Excessive Chargeback (RSK0030) ............................................... 126
Financial Reports – Discover Chargeback Summary (RSK0036).................................................... 131
Exception Reports ................................................................................................................................ 139
Exception Reports – Chargeback Activity (PDE0017) ..................................................................... 139
Exception Reports – ECP Returns (PDE0018) ................................................................................ 154
Exception Reports – Chargebacks Received (PDE0020) ................................................................ 165
Exception Reports – ECP Returns Received (PDE0022) ................................................................ 172
Exception Reports – Retrieval Detail (PDE0029) ............................................................................. 180
4
Exception Reports – Debit Adjustments (PDE0036) ........................................................................ 186
Exception Reports – Notification of Change (ACT0019) .................................................................. 191
Exception Reports – E-File Image Upload Exception (ACT0062).................................................... 198
Informational Reports ........................................................................................................................... 203
Informational Reports – Merchant FX Rate File (INF0042) .............................................................. 203
Attribute Reports ................................................................................................................................... 207
Deposit Activity Attributes (ACT0078) .............................................................................................. 207
Dynamic Debit Routing Reports ........................................................................................................... 213
Dynamic Debit Routing Comparison (ACT0082).............................................................................. 213
Fraud Advice Reports ........................................................................................................................... 220
Visa Fraud Advice (RSK0068).......................................................................................................... 220
Mastercard Fraud Advice (RSK0069) .............................................................................................. 231
File Trailer ............................................................................................................................................. 239
Appendices .............................................................................................................................................. 241
Appendix A – Currency Abbreviations .................................................................................................. 241
Appendix B – MOP Codes .................................................................................................................... 242
Appendix C – Category Values ............................................................................................................ 243
Appendix D – Sub-Category Values ..................................................................................................... 247
Appendix E – Country Codes ............................................................................................................... 249
Appendix F – NOC Reason Codes ....................................................................................................... 250
Appendix G – Cross Currency Processing ........................................................................................... 252
Appendix H – Action Codes .................................................................................................................. 255
Appendix I – Encryption and Compression .......................................................................................... 257
Appendix J – Availability ....................................................................................................................... 258
Appendix K – Data Field Numbering .................................................................................................... 259
Appendix L – Card Usage Type ........................................................................................................... 259
Appendix M – Card Product Type ........................................................................................................ 261
Appendix N – Accountholder Authorization Method ............................................................................. 263
Appendix O – Fraud Type Codes Abbreviations .................................................................................. 264
Appendix P – POS Entry Mode Codes Abbreviations .......................................................................... 265
Appendix Q – PDE0017 and PDE0020 Sample Data Record ............................................................. 266
5
Format Specifications
Introduction The Chase Merchant Services’ Delimited File Reporting (DFR) format was
developed for merchants and vendors who want to use Merchant Services
reporting data in an automated manner for direct uploading into a database
or other application.
Delimited files provide summary or detail information about the activity

processed by Merchant Services during the period. Data files may be
delivered with a choice of delimit characters (comma, tab or pipe) and are
customized to include the specific report data that your company requests.
To sign up for Delimited File Reporting or to modify an existing DFR setup,

please contact your Merchant Services Account Manager.
This This document provides specifications for every report available in a

document Delimited Reporting File. Please note that a given file may not include
every report in this document. If you would like to modify the reports to be
included in your company’s future delimited reporting files, please contact
your Merchant Services Account Manager.
Merchant Services offers a choice of character with which to delimit the data
records in a given DFR file setup. For purposes of illustration throughout this
document, the comma (,) is used as the delimiter. Other options are tab or
pipe ( | ), with a carriage return at the end of each record.
Delivery Delimited file reports may be delivered via any Merchant Services supported
options connectivity. Files are generated seven days per week, 365 days per year.
There are four delivery methods to choose from:
1. Flat file
2. Compressed file
3. Encrypted file
4. Compressed and Encrypted file
See Appendix I - Encryption and Compression, for more information.
Continued on next page
6
Request For The RFR Record is a Request For Response record that enables merchants
Response and vendors to connect to Merchant Services systems to retrieve the DFR
Files file(s). The software used to pick up a DFR file must have the ability to send
the RFR Record on demand.
An additional EOFEOFEOF record needs to follow the RFR record for

merchants using TCP/IP Berkeley Socket protocol.
RFR is not required if processing via SFTP or NDM.
Note: The RFR is a separate, fixed format record sent to Merchant Services.
Please see detailed specification on the next page.
7
Transaction File Request for Response (RFR) Record
1 2 3 4 5 6 7 8 12
12345678901234567890123456789012345678901234567890123456789012345678901234567890 . . . 0
AAAANNNNNNAAAAAAAAAAAAAANNNNNNAAAAAAAAAAAAAAANNNNNNAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
PID=123456 XYZCO SID=123456 XYZCO RFR 031115 
Data
Position Length Type Field Name Comments
1,4 4 A Constant PID=
5,10 6 N Presenter’s ID (PID) Assigned by Merchant Services
The PID is a number assigned to the

location that physically sends the data
file. (Presenter)
11 1 A Constant Blank
12,19 8 A PID Password Assigned by Merchant Services
21,24 4 A Constant SID=
25,30 6 N Submitter’s ID (SID) Assigned by Merchant Services
32,39 8 A SID Password Assigned by Merchant Services
41,43 3 A Constant RFR
44,45 2 A Constant Blanks
46,51 6 N Creation Date The date the file was created (Optional)
YYMMDD format
52+ 69+ A Reserved Blanks
8
RFR No File If an RFR record is received by Merchant Services, and there is no file
Response available for pick up, the following message is given:
YY-MM-DD HH:MM:SS No data to send back at this time.
EOFEOFEOF
 Message is sent in text file format without header or PID information
and begins in position 2
 TCPIP merchants receive the entire message noted above, with the
EOF line
 Bsync merchants receive the message above, without the EOF line
RFR is a separate record sent to Merchant Services. It should not be sent as

part of the input data file.
This record is not needed for SFTP or NDM file processing.
9
Report Layouts Overview
Introduction The following pages define the physical layouts of the various record types.
Each record definition is preceded by an example. The report data record

field definition table following the example contains all necessary field
information.
A length and a data type are provided for each field. The data type is either A
(alpha-numeric) or N (numeric only).
Note: Fields such as date (MM/DD/YYYY) or time (HH:MM:SS) that contain

non-numeric characters in addition to numbers are indicated as A (alpha-
numeric). Amounts, which may contain a decimal point in addition to
numbers, are indicated as N. See “Numeric formatting” for more information.
The comments column gives the values of constants or a short description of

the field’s meaning.
A sort order definition follows the report data record field definition table for
each report.
Each unique report header record appears no more than once in a given file.
10
Data Included All reports that have been selected for receipt for one company, at the same
in Report File frequency, are delivered within one set of files. If the company receives
report files at more than one frequency, each frequency constitutes a
separate set of files. Each aggregate set of merchant reports for the same
frequency are concatenated into one or two files (a file “set”) based on the
report type.
The three reports types are:

 Exception – Any report related to a Post-Deposit Event (PDE) such
as Chargeback and ECP Return related reports.
 Financial – Reports related to reconciliation, submission activity and
transaction detail reports.
 Informational – Reports providing information about items such as
foreign exchange rates.
All Exception reports are aggregated into one file with an “A” naming
convention. See File Naming Conventions for more information.
All Financial reports are aggregated into one file with a “B” naming
All Informational reports are aggregated into one file with an “E” naming
For example, if the company were to receive the FIN0010, FIN0011 and
PDE0017 on a daily basis, then each day two files are generated. One
contains the PDE0017 only and has the “A” naming convention. The second
contains the FIN0010 and FIN0011 and has the “B” naming convention.
No Data Files In the event that the entity has no activity to report for a given period, an
empty report file is generated. An empty file includes the File Header
Record, each applicable Header Record with no Data Records, and the File
Trailer record only.
11
File Naming Convention
File Naming This section describes the naming convention used for Delimited File
Convention Reports. Please note that the file names are only visible if the files are
retrieved via SFTP.
File Name The following table defines the fields included in the file name preceded by
Field an example. Fields within the file name are separated with a decimal point
Descriptions character ( . ) Please note that file name fields are fixed in length.
Sample File Name

0000123456.020301.d.A212.dfr
Field Data
Number Length Type Field Name Comments
1 10 N Company ID/Entity Assigned by Merchant Services. Right
ID justified and zero-filled
Notes: For those merchants set up for
entity level reporting, Company ID
becomes the Entity ID.
The first character of the Company
ID/Entity ID field identifies the entity level.
Valid values:
0 Company
1 Business Unit
2 Transaction Division
3 Funds Transfer Instruction
4 Reporting Group Company
5 Reporting Group Business Unit
6 Reporting Group Transaction
Division
7 Reporting Group Funds Transfer
Instruction
12
Sample File Name (continued)
Field Data
2 6 N Activity Date The last activity date included in a
file. For example, a monthly file
created for the calendar month
March 2011 would have an activity
date of “110331”
Format: YYMMDD
3 1 A Frequency Indicates the frequency for the
report file.
Valid values:
d Daily
w Weekly
f Fiscal Monthly
c Calendar Monthly
o Other
4 4 A File Identification This field is used to distinguish
# between three files that would
otherwise share the same file
name. The first character is always
an “A” for an Exception-type file,
“B” for a Financial-type file or an “E”
for an Informational-type file. The
remaining three characters are
Merchant Services-assigned based
on the file generation.
For example: A123 or B456 or

E789
5 3 A Constant “dfr”
13
Numeric Formatting
Formatting of All monetary values are formatted including decimal point and are two
Counts and decimal places except for these zero decimal currencies:
Amounts
Belarussian Ruble
Burundi Franc
CFA Franc BCEAD
CFA Franc BEAC
CFP Franc
Comoro Franc
Djibouti Franc
Japanese Yen
Laos Kip
Malagasy Franc
Paraguay Guarani
Rwanda Franc
South Korean Won
Turkish Lira (New)
Uganda Shilling
Vanuatu Vatu
Zero decimal currencies do not include decimal points or decimal places.

Comma separators are not used for any numeric value—count or amount—
anywhere in the delimited report file.
Example:
1,000 United States Dollars = 1000.00
1,000 Japanese Yen = 1000
Negative Negative values are indicated by a minus sign (-) preceding the value. All
Values other amounts are positive. A negative value normally indicates a debit to
the merchant, unless otherwise indicated within the field description.
Example:
-1000.00 = 1,000 debit to the merchant
Certain reports, such as the Chargeback Activity report or the ECP Return
Activity report, reflect values that are normally negative. In these cases, a
negative value indicates a credit to the merchant. Please see individual
Data Record Field Descriptions for more information on interpreting data for
a specific report.
14
Date and Time All dates are stated as MM/DD/YYYY, unless otherwise indicated for that
Formats field. Times are generally HH:MM:SS, unless otherwise stated, and always
refer to military time (24-hour clock).
Entity Number Entity number and company number fields do not include any leading zeros
even if the zeros are used in submission processing. For merchants who
utilize Alternate ID numbers at the Transaction Division (TD) level, the entity
number is replaced by the Alternate ID for any entity number field that
represents a TD within the delimited report.
Entity Reports An entity report is a set of hierarchical entities that are grouped together to
summarize their transactions. This relationship can be defined to any entities
such as:
 Company (CO)
 Business unit (BU)
 Transaction division (TD)
 Funds Transfer Instruction (FTI)
 Reporting Group (RG).
Entity reports provide a way of excluding entities that would otherwise be

included in a summary at the company, business unit, transaction division, or
funds transfer instruction.
Note:
All entities in a group must have a common parent company
15
Other Formatting
Text Identifier Some fields may contain the same characters that are used to delimit fields.
In these cases, the field is surrounded with double quotes (“”) to denote the
characters as text data. Please see individual report descriptions for the
specific Data Records to which this applies. Field lengths for double-quoted
fields do not include quotation marks.
Suppressed Some data fields and records are noted in this technical specification as
Fields suppressed unless a merchant participates in a particular kind of processing,
such as Cross-Currency. If a field is noted as suppressed, the entire field and
its associated delimiter are not present in the file. This is different from a
field that is noted to have a blank value under specific circumstances. A
blank value field does NOT result in suppression of the delimiter character(s).
Account Masking
Account Masking is offered with DFR Reporting. When this option is selected, the
account number and IBAN are presented with the last 4 data elements in the
clear and all others converted to X’s. This applies to all reports unless otherwise
noted.
Appendix Section
Changes in report format are not made without merchant notification.
The values in this section are dynamic and additions may have been made since
this specification was released.
16
File Sort Order
File Sort Within any one file, the records are arranged in the following order (including
Order headers and trailers). Your company’s file contains only those report
elements you have elected to receive. File Header and File Trailer are
included in all files.
“A” Files All Exception Reports are compiled into one file, denoted by an “A” in the file
name. The sort for the “A” file is:
File Header Record

PDE0017 – Chargeback Activity
PDE0018 – ECP Returns
PDE0020 – Chargebacks Received
PDE0022 – ECP Returns Received
PDE0029 – Retrieval Detail
ACT0019 – Notification of Change
PDE0036 – Debit Adjustments
ACT0062 – E -File Image Upload Exception Header Record
File Trailer Record
17
“B” Files All Financial Reports are compiled into one file, denoted by a “B” in the file
name. The sort for the “B” file is:
File Header Record

FIN0010 – Deposit Activity Summary
FIN0010T – Deposit Activity Summary Transfer
LNK010A – Transaction Summary
ACT0033 – Reject Summary
ACT0012 – Submission Listing
FIN0011 – Service Charge Detail
ACT0010 – Deposit Detail
ANS0039 – Debit Authorization Aging
ANS0041 – Merchant Settlement Aging
ACT0002 – Exception Detail
ACT0027 – Terminal Batch Detail
RSK0030 – MC Excessive Chargeback
RSK0036 – Discover Excessive Chargeback
ANS0016 – Interchange Qualification Summary
ACT0036 – Authorization Detail
ANS0013 – Interchange Qualification Detail
ANS0017 – Interchange Downgrade Summary
ACT0069 – IBAN Conversion Detail
File Trailer Record
“E” Files All Informational Reports are compiled into one file, denoted by an “E” in the
file name. The sort for the “E” file is:
File Header Record

INF0042 – Merchant FX Rate File
“H” Files All Attribute Reports are compiled into one file, denoted by an “H” in the file
name. The sort for the “H” file is:
File Header Record

ACT0078 – Deposit Activity Attributes
“I” Files All Dynamic Debit Routing Comparison Reports are compiled into one file,
denoted by an “I” in the file name. The sort for the “I” file is:
File Header Record

ACT0082 – Dynamic Debit Routing Comparison
18
“J” Files The Visa Fraud Advice Reports are delivered in one file denoted by a “J” in
the file name. The sort for the “J” file is:
File Header Record

RSK0068 – Visa Fraud Advice
“K” Files The Mastercard Fraud Advice Reports are delivered in one file denoted by a
“K” in the file name. The sort for the “K” file is:
File Header Record

RSK0069 – Mastercard Fraud Advice
19
Record Layouts
File Header
File Header The file header is used by the recipient system to identify the contents of the
file to follow.
File Header The following table defines the fields included in the File Header preceded by
Field an example data record.
Descriptions
Sample File Header

*DFRBEG,PID=123456,FREQ=DAILY,CO=111111
Field Maximum Data

1 7 A Constant *DFRBEG
2 14 A Presenter’s ID Assigned by Merchant Services.
(PID)
Preceded by PID=
Note: Field length includes preceding

characters
3 14 A Frequency Frequency at which this file is
generated and delivered.
Preceded by FREQ=
Valid values:
CALENMON Calendar Month
DAILY Daily
FISCALMON Fiscal Month
OTHER Other Frequency
WEEKLY Weekly
Note: Field length includes preceding

characters
20
File Header
Continued
Field Maximum Data

4 13 A Company Assigned by Merchant Services.
ID/Entity ID
The first two characters of the
Company ID/Entity ID field identify the
entity level.
Valid values:
CO Company
BU Business Unit
TD Transaction Division
FT Funds Transfer Instruction
RC Reporting Group - Company
RB Reporting Group - Business
Unit
RT Reporting Group – Transaction
Division
RF Reporting Group - Funds
Transfer Instruction
Entity level value is followed by an

equal sign (=) and then the entity
number.
21
Financial Reports
All Financial Reports are compiled into one file, denoted by a “B” in the file name.
Financial Reports – Deposit Activity Summary

(FIN0010)
FIN0010 Merchants use this report to get a high level view of their successful deposits
Report for a date range. This report assists merchants in reconciling processing
Description activity by comparing any applicable internal reports to the data from this
report.
How This The FIN0010 summarizes the deposit activity Merchant Services received
Report Is during a specified date range and is used for verification and reconciliation to
Used merchant systems. This report also summarizes any fees and adjustments
that financially impact the merchant.
FIN0010 The FIN0010 Header Record identifies the data to follow and its layout to the
Header recipient system.
Record
22
Sample Header Record
HFIN0010,543210,07/12/2005,07/12/2005,07/13/2005,14:15:01
FIN0010 The following table defines the fields included in the FIN0010 Header
Header Record.
Record Field
Descriptions
Field Maximum Data Field Name Comments

Number Length Type
1 8 A Record Type Constant “HFIN0010”
2 10 N Company ID # Assigned by Merchant Services .
3 10 A Report Date From Date report activity begins. Based
on merchant end of day.
Format: MM/DD/YYYY
4 10 A Report Date To Date report activity ends. Based on
merchant end of day.
Format: MM/DD/YYYY
5 10 A Report Generation Date report was created. This is
Date the calendar date in the Eastern
time zone.
Format: MM/DD/YYYY
6 8 A Report Generation Time the report was generated,
Time based on Eastern time.
Format: HH:MM:SS
23
FIN0010 Data The FIN0010 Data Record contains the financial summary data arranged as
Record follows. A FIN0010 Report normally contains many Data Records.
Sample Data Record

RFIN0010,TD,234567,222222,307111111,USD,VI,SALE,S,2934,68628.40
Sample Data Record - Cross Currency

RFIN0010,TD,234567,222222,307111111,GBP,VI,SALE,S,2934,68628.40,USD,1.74
FIN0010 Data The following table defines the fields included in a FIN0010 Data Record.
Record Field
Descriptions
Field Maximum Data

1 8 A Record Type Constant “RFIN0010”
2 2 A Entity Type Level at which reported event
occurred.
Valid values:
BU Business Unit
CO Company
3 10 A Entity # Associated CO, BU or TD
identification number less any
leading zeros.
Merchant Services assigned

4 10 N Funds Transfer Funds Transfer Instruction number
Instruction # associated with the reported
activity.
Note: A blank value in this field

indicates that a financial event was
not yet included in a Funds
Transfer
24
FIN0010 Data Record Field Descriptions (continued)
Field Maximum Data

5 10 N Secure BA # Merchant Services assigned secure Bank
Account Number.
Note: A blank value in this field indicates

that a financial event was not yet included
in a Funds Transfer.
6 3 A Presentment Three character abbreviation for currency
Currency in which the cardholder transaction was
conducted.
See Appendix A for values

7 2 A MOP Two character code to identify payment
method (Visa, Mastercard etc.).
See Appendix B for values
Note: This field is blank for Data Records

with a Category other than SALE or REF.
8 6 A Category Indicates the type of activity represented in
this record.
Valid values:
BUW Back Up Withholding
CB Net Chargeback Activity
DBADJ Net Debit Adjustment
Activity
ERET Net ECP Return Activity
IA Interchange/Assessment Fees
OTH Other Adjustments
PFEE Merchant Services Fees
REF Refunds
RES Reserve Adjustments
SALE Sales
See Appendix C for more information.
25
Field Maximum Data

9 1 A Settled/ Indicates whether the Data Record
Conveyed activity is Settled (impacts Funds
Transfer to merchant's bank) or
Conveyed (memo post for T & E cards).
Valid values:
C Conveyed
S Settled
10 10 N Count The number of items included in a Data
Record.
See “Numeric formatting” for more

information
Note: This field is blank for Data

Records with a Category other than
SALE or REF.
11 17 N Amount The value of the items included in a
Data Record.

information
For cross-currency, amount is populated

based on category as follows:
CB Settlement Currency
DBADJ (N/A)
ERET (N/A)
IA Settlement Currency
OTH Settlement Currency
PFEE Settlement Currency
REF Presentment Currency
RES Settlement Currency
SALE Presentment Currency
When the file is generated at a Funds

Transfer Instruction Level (FTI) all
amounts are in the Settlement
Currency.
26
Field Maximum Data

12 3 A Settlement Three character abbreviation for
Currency currency in which the merchant is
being funded.
See Appendix A for values.
This field is suppressed unless

cross-currency is selected.
13 17 N Foreign The foreign exchange rate multiplier
Exchange Rate applied to the currency pair in this
data record for cross currency
transactions. This field is blank for
any rows with a category other than
SALE or REF.

Sort Order Data Records within the FIN0010 Report are sorted based on the following
For FIN0010 order:
Data Records
Currency (field 6) – USD first, then all others by alpha
Entity type – Co first, then BU, then TD
Entity # - Ascending
FTI - Ascending
Category – See Appendix C
MOP – See Appendix B
27
Financial Reports – Deposit Activity Transfer
Summary (FIN0010T)
FIN0010T Merchants use this report to get a high level view of their funds transfer
Report activity for a date range. This report assists merchants in reconciling their
Description bank accounts by comparing their bank statements to the data from this
report.
How This The FIN0010T summarizes the funds transfers that have been created and
Report Is are pending, on hold, rejected or scheduled for credit to their bank account
Used on the current date.
FIN0010T The FIN0010T Header Record identifies the data to follow and its layout to
Header the recipient system.
Record

HFIN0010T,543210,07/12/2005,07/12/2005,07/13/2005,14:15:01
FIN0010T The following table defines the fields included in the FIN0010T Header
Header Record.
Record Field
Descriptions
Field Maximum Data

1 9 A Record Type Constant “HFIN0010T”
2 10 N Company ID # Assigned by Merchant Services
(formerly the MA NUMBER).
Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
28
Transfer The FIN0010T Data Record contains the funds transfer summary data
Section - arranged as follows.
FIN0010T
Data Record
Sample Data Record

RFIN0010T,TD,234567,222222,307111111,USD,222222,PENDFT,07/12/2005,,6050.40

RFIN0010T,TD,234567,222222,307111111,GBP,222222,PENDFT,07/12/2005,0,6050.40,USD,1.74
FIN0010T The following table defines the fields included in a FIN0010T Data Record.
Data Record
Field
Descriptions
Field Maximum Data

1 9 A Record Type Constant “RFIN0010T”
occurred.
.
Valid values:
BU Business Unit
CO Company
3 10 A Entity # Associated CO, BU or TD
identification number less any
leading zeros.

activity.
5 10 N Secure BA # Merchant Services assigned secure

Bank Account Number.
29
FIN0010T Data Record Field Descriptions (continued)
Field Maximum Data

6 3 A Presentment Three character abbreviation for
Currency currency in which the cardholder
transaction was conducted.

7 38 N Funds Transfer # Numeric identifier assigned to each
unique funds transfer created by
Merchant Services.
8 6 A Category Indicates the type of activity represented
in this record.
Valid values:
EFEFT Effective Funds Transfer
HOLDFT On Hold Funds Transfer
PENDFT Pending Funds Transfer
REJFT Rejected Funds Transfer

9 10 A Effective Date Indicates the date on which the funds
transfer is scheduled to be credited to
the merchant’s bank account.
Format: MM/DD/YYYY
30
FIN0010T Data Record Field Descriptions (continued)
Field Maximum Data

10 1 N Count This field is populated with a zero in
this report. It’s a placeholder to
maintain data field location
consistency with the FIN0010.
Data Record.

information.
For Cross Currency merchants, the

amount is expressed in Settlement
Currency
being funded.

13 17 N Foreign The foreign exchange rate multiplier
Exchange Rate applied to the currency pair in this
data record.
Sort Order Data Records within the FIN0010T Report are sorted based on the following
For FIN0010T order:
Data Records
Presentment Currency (field 6) – USD first, then all others by alpha
FTI - Ascending
Funds Transfer # - Ascending
31
Financial Reports – Transaction Summary (LNK010A)
LNK010A This report is additional detail for the FIN0010 and is normally only delivered
Report in conjunction with it.
Description
How This Merchants use this report to understand how we arrived at Successful
Report Is Deposits on the FIN0010. The merchant’s financial contact may use this
Used report to help reconcile the activity that resulted in successful deposit
transactions. The report provides a count of transactions processed,
authorizations, rejects, declined deposits, and non-financial transactions.
When used in conjunction with the FIN0010, it provides the merchant with a
complete picture of all transactions received for processing for a given
activity period.
LNK010A The LNK010A Header Record identifies the data to follow and its layout to
Record
32
HLNK010A,543210,07/12/2005,07/12/2005,07/13/2005,14:15:01
LNK010A The following table defines the fields included in the LNK010A Header
Header Record.
Record Field
Descriptions
Field Maximum Data

1 8 A Record Type Constant “HLNK010A”
2 10 N Company ID # Assigned by Merchant Services .
Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
33
LNK010A The LNK010A Data Record contains the financial summary data arranged as
Data Record follows. A LNK010A Report normally contains many Data Records.
Sample Data Record

RLNK010A,TD,234567,222222,307111111,USD,CC,AUTH,,758,758.00
Sample Data Record for a Cross Currency Merchant

RLNK010A,TD,234567,222222,307111111,GBP,CC,AUTH,,758,758.00,USD
LNK010A The following table defines the fields included in a LNK010A Data Record.
Data Record
Field
Descriptions
Field Maximum Data

1 8 A Record Type Constant “RLNK010A”
occurred. For this report, the value
is always:
3 10 A Entity # Associated TD identification
number less any leading zeros.
Merchant Services assigned.
activity.
Note: This field is blank for records

with a Category of REJ.
5 10 N Secure BA # Merchant Services-assigned
secure Bank Account Number.
Note: This field is blank for records

with a Category of REJ.
34
LNK010A Data Record Field Descriptions (continued)
Field Maximum Data

Currency currency being reported.

7 2 A MOP Two character code to identify payment
method (Visa, Mastercard etc.)
See Appendix B for values.
Note: This field is blank for records with

a Category of REJ or NON.
in this record.
Valid values:
AUTH Authorization Only
(credit)
DBSALE Auth Only – Debit Sale
DBREF Auth Only – Debit
Refund
PREDB Pre-Auth - Debit
PRE ECP Val/Ver/Prenote
NON Non-financial
REJ Rejected Item
DEC Declined Deposit
CNSALE Cancelled Sale
CNREF Cancelled Refund

9 0 Blank Settled/ This field is not populated within this
Conveyed report. It’s a placeholder to maintain
data field location consistency with the
FIN0010.
35
LNK010A Data Record Field Descriptions (continued)
Field Maximum Data

10 10 N Count The number of items included in a
Data Record.

information
Data Record.

information.
Note: This field is blank for any

Data Record with Category of PRE
or NON and may be blank for a
Category of REJ if the reject was
due to invalid amount
being funded.

Sort Order Data Records within the LNK010A Report are sorted based on the following
For LNK010A order:
Data Records
FTI - Ascending
36
Financial Reports – Reject Summary (ACT0033)
ACT0033 Provides a summary of rejects by action code. This report assists a large
Report volume processor with reject management when the volume makes a detail
Description level report unmanageable.
How This Merchant uses data in the ACT0033 report to categorize rejects by action
Report Is code.
Used
ACT0033 The ACT0033 Header Record identifies the data to follow and its layout to
Record

HACT0033,543210,07/12/2005,07/12/2005,07/13/2005,14:15:01
ACT0033 The following table defines the fields included in the ACT0033 Header
Header Record.
Record Field
Descriptions
Field Maximum Data

1 8 A Record Type Constant “HACT0033”
2 10 N Company ID # Assigned by Merchant Services.
Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
37
ACT0033 Data The ACT0033 Data Record contains the financial summary data arranged as
Record follows. An ACT0033 Report normally contains many Data Records.
Sample Data Record

RACT0033,TD,749499,1234,30704329,USD,,B,,118,5427.19

RACT0033,TD,749499,1234,30704329,GBP,,B,,118,5427.19,USD
ACT0033 Data The following table defines the fields included in an ACT0033 Data
Record Field Record.
Descriptions
Field Maximum Data

1 8 A Record Type Constant “RACT0033”
is always:
number less any leading zeros.
4 0 Blank Funds Transfer This field is not populated within
Instruction # this report. Placeholder to maintain
data field location consistency with
the FIN0010.
5 0 Blank Secure BA # This field is not populated within
this report. Placeholder to maintain
data field location consistency with
the FIN0010.
38
ACT0033 Data Record Field Descriptions (continued)
Field Maximum Data
Currency currency being reported. May be
blank if item rejected for invalid
currency.

7 0 Blank MOP This field is not populated within this
report. Placeholder to maintain data
field location consistency with the
FIN0010.
8 2 A Action Code Indicates the action code that was
(Category) included with this transaction in the
merchant's submission file.
Note: the ACT0033 fields agree with

the FIN0010 and LNK010A field so
that they may be processed as one
report if the merchant chooses. For
purposes of this report, the Action
Code functions as the Category.
9 0 Blank Settled/Conveyed This field is not populated within this
report. Placeholder to maintain data
field location consistency with the
FIN0010.
10 10 N Count The number of items rejected for this
action code.

information.
11 17 N Amount The value of the items rejected.

information.
Note: An item that is rejected for

invalid amount is included in this
sum as "0".
39
Field Maximum Data
being funded.

Sort Order Data Records within the ACT0033 Report are sorted based on the following
For ACT0033 order:
Data Records
Currency (field 6) – USD first, then all others by alpha. Blank currency
records appear last
Entity type – CO first, then BU, then TD
Entity # – Ascending
FTI – Ascending
Action Code – Ascending
40
Financial Reports – Submission Listing (ACT0012)
ACT0012 Provides a listing of submissions received from a merchant or presenter

Report within a specified timeframe including a summary of transactions per file.
Description
How This Merchants use this report to determine what submissions were received at
Report Is Merchant Services by date and time. Merchants also use this report to verify
Used the contents and status of a submission or a summary-level status of
transactions.
Record

HACT0012,543210,07/12/2005,07/12/2005,07/13/2005,14:15:01
Header Record.
Record Field
Descriptions
Field Maximum Data

Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
41
Sample Data Record

RACT0012,TD,123456,USD,”1234.5236a”,123456,”abcn”,04/23/2005,07:16:11,844,290,50,7,2,0
,0,495,4850.21,Accepted

RACT0012,TD,123456,GBP,”1234.5236a”,123456,”abcn”,04/23/2005,07:16:11,844,290,50,7,2,0
,0,495,4850.21,Accepted,USD
ACT0012 Data The following table defines the fields included in a ACT0012 Data Record.
Record Field
Descriptions
Field Maximum Data

is always:
3 10 N Entity # Associated TD identification
number, less any leading zeroes.

5 13 A Submission # Merchant Services assigned unique
identification number for the
submission.
Note: This field is double-quoted.
42
Field Maximum Data

6 10 N PID # Merchant's presenter id number.
7 6 A PID Short name Merchant's presenter id abbreviated
name
Note: This field is double-quoted

8 10 A Submission Date Date the submission was fully
received at Merchant Services.
9 8 A Submission Time Time the submission was fully
Format: HH:MM:SS
10 10 N Transaction Count Total number of transactions
included in the submission for the
TD.

information
11 10 N Authorization Number of transactions with
Count Authorization Only action codes
submitted in the submission for the
TD.

information.
Note: This also includes ECP

Verification/Validation/ Prenote.
Authorizations performed on B
(conditional deposit) action codes
are not included. Merchant Services
re-authorizations and partial
authorizations are not included.
43
Field Maximum Data

12 10 N Non-Financial Number of non-financial
Transaction Count transactions included in the
submission for this TD. This data
record refers to specific FPO Starts
and Modifications and Stored
Values Transactions.

information
13 10 N Declined Deposit Number of transactions received for
Count deposit that were not processed
due to declined authorization
request.

information
14 10 N Rejected Number of transactions received
Transaction Count that were not processed due to
failure to pass Merchant Services
front-end edit checks.

information
15 10 N Cancelled/On-Hold Number of transactions that were
Deposit Count included in a submission with a
Cancelled/On-Hold status as of the
end of the report activity period.

information
16 17 N Cancelled/ On- Monetary value of transactions that
Hold Net Deposit were included in a submission with
Amount a Cancelled/On-Hold status. Stated
as a net amount (i.e. Sales less
Refunds).

information
44
Field Maximum Data

17 10 N Successful Number of transactions received for
Deposit Count deposits that were successfully
processed. Stated as a gross count (i.e.
Sales plus Refunds).

information
18 19 N Successful Net Monetary value of transactions received
Deposit Amount for deposits that were successfully
processed. Stated as a net amount (i.e.
Sales less Refunds).

information
19 8 A Status Status of the submission:
Valid values:
Accepted Successfully processed
Cancelled Cancelled Submission
On Hold Temporarily on hold
20 3 A Settlement Three character abbreviation for currency
Currency in which the merchant is being funded.
This field is suppressed unless cross-

currency is selected.
Sort order for Data Records within the ACT0012 Report are sorted based on the following
ACT0012 Data order:
Records
PID - Ascending
Submission # – Ascending
45
Financial Reports – Service Charge Detail (FIN0011)
FIN0011 This report identifies fees assessed for services that were posted
Report during the reporting period.
Description
How this Merchants use this report to identify the total service charges (fees)
Report is posted for a timeframe by category and to validate all such fees at a
Used more granular level than is presented on the FIN0010.
FIN0011 The FIN0011 Header Record identifies the data to follow and its layout
Header to the recipient system.
Record

HFIN0011,543210,07/12/2005,07/12/2005,07/13/2005,14:15:01
FIN0011 The following table defines the fields included in the FIN0011 Header
Header Record.
Record Field
Descriptions
Field Maximum Data

1 8 A Record Type Constant “HFIN0011”
Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
46
FIN0011 Data The FIN0011 Data Record contains the financial summary data arranged as
Record follows. A FIN0011 Report normally contains many Data Records.
Sample Data Record

RFIN0011,IA,IC,TD,234567,222222,307111111,USD,7567711,VI,VCE,”Interchange”,S,1,-
0.1,242.15,-0.021,-5.19

RFIN0011,IA,IC,TD,234567,222222,307111111,GBP,7567711,VI,VCE,”Interchange”,S,1,-
0.1,242.15,-0.021,-5.19,USD
FIN0011 Data The following table defines the fields included in a FIN0011 Data Record.
Record Field
Descriptions
Field Maximum Data

1 8 A Record Type Constant “RFIN0011”
2 6 A Category These are codes identifying the
different categories that group similar
fees.
Valid values:
IA Interchange and Assessment
PFEE Merchant Services Fees
These categories may be used to

validate the FIN0011 data against the
FIN0010 data.
See Appendix C for values.

3 6 A Sub-Category These are codes identifying the
different sub-categories that group
similar fees.
See Appendix D for values.
47
Field Maximum Data

occurred.
Valid values:
BU Business Unit
CO Company
5 10 N Entity # Associated CO, BU or TD
identification number, These
numbers are Merchant Services-
assigned.
activity.

Transfer.
7 10 N Secure BA # Merchant Services assigned
Secure Bank Account Number.

Transfer.

9 10 N Fee Schedule Merchant Services-assigned Fee
schedule ID that is associated with
this report data record.
This field may be blank.

10 2 A MOP Two character code to identify
payment method (Visa, Mastercard
etc.).
48
Field Maximum Data

11 4 A Interchange This is a code that identifies the
Qualification rate at which Merchant Services
qualified the transaction on the
front-end. This field would also
display the interchange rate
assessed by the settled endpoint
for back-end downgrades (non-
qualified transactions). There are
separate data records for front-end
and back-end qualification fees.
Note: This field has a value of

“NONE” for ChaseNet transactions
and may be blank or have a value
of “NONE” for other fee types
12 30 A Fee Type Text description of the fee type for
Description this report data record.

13 1 A Action Type Code that refers to the kind of
transaction that was being
performed relative to the charge.
Valid values:
A Authorizations
C Chargebacks
P Representments
R Refunds
S Sales
V Verifications

14 10 N Unit Quantity Number of items for which the fee
in this Data Record is assessed.
information
49
Field Maximum Data

15 11 N Unit Fee Fee per item identified in the
merchant’s fee schedule for each
line item. The unit fee is applied to
the unit quantity.
 Up to 4 decimal places
 Zero is a valid value for this
field
 May be blank
 For this field, a positive amount
indicates a debit unit fee to the
merchant. A negative amount
indicates a credit unit fee

unit fee is expressed in settlement
currency
16 17 N Amount Monetary value of the transactions
for this Data Record.

information.

amount is expressed in settlement
currency.
Notes:
May be blank if Field 17 is blank.
Zero is a valid value for this field.
50
Field Maximum Data

17 10 N % Rate The percentage rate fee applied to
the transaction values presented in
the previous field.
 May be blank if Field 16 is
blank.
field
indicates a debit % rate to the
indicates a credit % rate
18 17 N Total Charge The total fee assessed for this Data
Record.

information.
Calculation = Sum of the (count *

unit fee) + (amount * %rate).

total charge is expressed in
settlement currency
Note:
Calculation may not always agree
due to rounding.
transaction occurred.

51
Sort order for Data Records within the FIN0011 Report are sorted based on the following
FIN0011 Data order:
Records
FTI - Ascending
Sub-Category – See Appendix D
Interchange Qualification – Ascending
% Rate – Ascending
Unit Fee – Ascending
52
Financial Reports – Debit Authorization Aging
(ANS0039)
ANS0039 This report provides a detailed listing of debit transactions for which the
Report merchant has submitted an authorization transaction but has not yet
Description submitted a deposit transaction and therefore has not been funded. This
report helps merchants to reconcile transactions presented to Merchant
Services for authorization with transactions presented to Merchant Services
for settlement. The report may assist merchants with identifying operational
issues that may be impacting their bottom line.
This report is a snapshot of a given moment in time. As such, it can only be

set up as a daily frequency report (monthly or weekly are not allowed) and
cannot be re-generated for a historical date or date range.
How this Merchants use this data to trigger their reconciliation and/or collection and
Report is recovery processes. This may include research, updates to their customer
Used databases, contact with the endpoint or the customer, etc.
53
ANS0039 The ANS0039 Header Record identifies the data to follow and its layout to
Record

HANS0039,543210,07/12/2005,07/12/2005,07/13/2005,14:15:01
ANS0039 The following table defines the fields included in the ANS0039 Header
Header Record.
Record Field
Descriptions
Field Maximum Data

1 8 A Record Type Constant “HANS0039”
Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
54
ANS0039 Data The ANS0039 Data Record contains the outstanding settlement aging
Record transaction detailed data arranged as follows. An ANS0039 Report normally
contains many ANS0039 Data Records.
Sample Data Record

RANS0039,TD,234567,USD,SP,4,012345,07/08/2005,D,28.95,5444481005851350,55order6
6,000123,,
ANS0039 Data The following table defines the fields included in an ANS0039 Data Record.
Record Field
Descriptions
Field Maximum Data

1 8 A Record Type Constant “RANS0039”
always is:
3 10 N Entity # Associated TD identification number,
less any leading zeroes. Merchant
Services assigned.
4 3 A Currency Three character abbreviation for
currency being reported.

5 2 A Method of Identifies the MOP for the settlement
Payment (MOP) aging activity.

6 7 N # of Days This is the precise number of days
Outstanding the item has been in the Merchant
Services system, i.e. the number of
days since submission was received.
55
ANS0039 Data Record Field Descriptions (continued)
Field Maximum Data

7 6 A Authorization Six character code related to a
Code positive response from the endpoint.
8 10 A Authorization Date Date of the original transaction
submission.
Format: MM/DD/YYYY
9 2 A Action Code Merchant supplied code that indicates
the type of transaction conducted.
Data Record.

information
11 22 A Account # Customer's account number
12 22 A Merchant Order # The order number submitted by the
merchant with the original sale.

13 8 A Trace # A sequential identifier assigned by
Merchant Services ranging from 1-
99999999 that is applied to debit
transactions. This number is rolling
so a merchant may see the same
number more than once.
56
Sort Order for Data Records within the ANS0039 Report are sorted based on the following
ANS0039 Data order:
Records
Currency – USD first, then all others by alpha
# of Days Outstanding - Ascending
Entity type – CO first, then BU, then TD
57
Financial Reports – Merchant Settlement Aging
(ANS0041)
ANS0041 This report provides a detailed listing of transactions that have not been
Report settled by the endpoint and therefore are not funded. This report helps
Description merchants to reconcile transactions presented to Merchant Services for
authorization with transactions presented to Merchant Services for
settlement. The report assists merchants with identifying operational issues
that may be impacting their bottom line.
This report is a snapshot of a given moment in time. As such, it can only be

set up as a daily frequency report (monthly or weekly are not allowed) and
cannot be re-generated for a historical date or date range. Outstanding
transaction details are stored for 30 days only. On the 31st day a transaction
falls off of this report whether or not it has been funded.
How this Merchants use this data to trigger their reconciliation and/or collection and
Report is recovery processes. This may include research, updates to their customer
Used databases, contact with the endpoint or the customer, etc.
58
Record

HANS0041,543210,07/12/2005,07/12/2005,07/13/2005,14:15:01
Header Record.
Record Field
Descriptions
Field Maximum Data

Format: MM/DD/YYYY
Format: MM/DD/YYYY
Note: As this is a snapshot report,

the Report Date From and Report
date to fields are always equal.
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
59
ANS0041 Data The ANS0041 Data Record contains the outstanding settlement aging
Record transaction detailed data arranged as follows. An ANS0041 Report normally
contains many ANS0041 Data Records.
Sample Data Record

RANS0041,TD,234567,USD,PY,4,07/08/2005,D,28.95,1234acct9876,55order66,77contract88
,USD,,
Record Field
Descriptions
Field Maximum Data

occurred. For this report, the value is
always:
less any leading zeroes. This number
is assigned by Merchant Services

5 2 A Method of Identifies the MOP for the settlement
Payment (MOP) aging activity.

6 7 N # of Days This is the precise number of days
Outstanding the item has been in the Merchant
Services system, i.e. the number of
days since the submission was
received.
60
Field Maximum Data

7 10 A Submission Date Date of the original transaction
submission.
Format: MM/DD/YYYY
9 16 N Presentment The value of the items included in a
Currency Amount Data Record expressed in the
cardholder’s presentment currency.

information
10 22 A Account # Customer’s account number

12 20 A Contract ID For PayPal transactions, this is the
reference number used to the
contract identify recurring. May be
blank.
being funded.

14 0 Blank Reserved This field is not populated within this
report. Field is reserved for future
Merchant Services use.
61
Sort order for Data Records within the ANS0041 Report are sorted based on the following
ANS0041 Data order:
Records
# of Days Outstanding – Ascending
62
Financial Reports – Exception Detail (ACT0002)
ACT0002 The ACT0002 Report provides transaction level detail for unsuccessful
Report deposit transactions. Exception items within the scope of this report include
Description rejected transactions, declined deposits and transactions that were included
in a submission that was cancelled in its entirety.
How this Merchants use this report to verify what was sent and processed against the
Report is merchant’s own internal transaction reports. Specific usage varies by
Used merchant, but may be used for reconciliation or research of deposit activity.
Any transaction that appears on this report was not included in a merchant’s
funded activity for the activity date of the report. This information can be
extremely valuable in reconciling a merchant’s submitted transaction activity
to a bank account statement or other Merchant Services Solutions report,
such as the FIN0010 – Deposit Summary.
Options for The ACT0002 report allows merchants to extend the standard report data
this Report record with additional data fields. Options available for this report include:
 Cross Currency (Merchants presenting and settling in different

currencies.)
 IBAN Detail (Merchants processing SEPA EUDD transactions.)
As a result of option selection, additional data fields (data and delimiter) are
appended to each standard data record. The sequence that the optional data
are appended is outlined below.
Sequence 1 Standard Data Record (Data Field Number 1 to 25)

Sequence 2 Optional Cross Currency Data Record (1 Data Field)
Sequence 3 Optional IBAN Detail Data Record (7 Data Fields)
See “Appendix K – Data Field Numbering” for more information.
Record
63
HACT0002,543210,07/12/2005,07/12/2005,07/13/2005,14:15:01
Header Record.
Record Field
Descriptions
Field Maximum Data

Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
64
ACT0002 Data The ACT0002 Data Record contains the transaction level detail data
Record arranged as follows. An ACT0002 Report normally contains many Data
Records.
Sample Data The following table provides examples of data rows for various types of
Record transactions.
Rejected Transaction – ECP

RACT0002,07/12/2005,999999,”cdabe”,”50712.0106f”,273,TD,123456,USD,”01208D3”,411298902,4254970
00,,5.22,EC,H,07/10/2005,123456,100,,,REJECT,,212,ACCEPT
Declined Deposit – Credit Card Transaction
RACT0002,07/12/2005,123456,”cdabe”,”50712.0106f”,1,TD,654321,USD,”4857X2”,,4444444433333330,08
/04,5.00,VI,D,07/10/2005,622233,100,,,DECLINE,,,ACCEPT
Cancelled Submission – Credit Card Transaction
RACT0002,07/12/2005,123456,”cdabe”,”50712.0108f”,4,TD,654321,USD,”321ZZ8”,,4444333322221111,,1
5.00,MC,D,07/10/2005,998822,100,,,CANCEL,,,CANCEL
Cancelled Submission – Euro Direct Debit Transaction with IBAN
RACT0002,11/12/2013,123456,”cdabe”,”50712.0108f”,4,TD,654321,EUR,”321ZZ8”,,4444333322221111,,1
5.00,ED,D,11/10/2013,998822,100,,,CANCEL,,,CANCEL,1001100020,FR76 1001 1000 2000 1234 5678
934,PSSTFRPPCNE,"FR97ZZZ12345678","ABCD 1234",5,11/01/2013
ACT0002 The following table defines the fields included in an ACT0002 Standard Data
Standard Data Record.
Record Field
Descriptions
Field Maximum Data

2 10 A Submission Date The date on which the submission
was fully received at Merchant
Services. This is the calendar date
in the Eastern time zone.
Format: MM/DD/YYYY
3 10 N PID Merchant’s presenter ID number
4 6 A PID Short Name Merchant’s presenter ID
abbreviated name
65
ACT0002 Standard Data Record Field Descriptions (continued)
Field Maximum Data

submission.

6 10 N Record # Record number is the sequential
number of a transaction within a
submission file.
is always:
number. Merchant Services
assigned less any leading zeros.


11 10 N RDFI # Receiving Depository Financial
Institution number.
Note: This field is blank for

transactions other than ECP or
Euro Debit.
12 22 A Account # Customer’s credit card or
depository financial institution
account number.
Note: A four character "IBAN"

identifier is presented in this field
for EUDD transactions that are
submitted with the IBAN.
66
Field Maximum Data

13 5 A Expiration Date The credit card account expiration
date (month and year) as submitted
by the merchant with this
transaction. This field is blank for
ECP and debit transactions.
Format: MM/YY
14 17 N Amount The monetary value of the
transaction.

information.
For Cross-Currency merchants, the

Amount is expressed in
presentment currency.
etc.).

16 2 A Action Code Merchant supplied code that
indicates the type of transaction
conducted.
17 10 A Auth Date Date on which the authorization for
this deposit transaction was
performed.
Format: MM/DD/YYYY
18 6 A Auth Code Six character code related to a
positive response from the
endpoint.
19 3 A Auth Response Merchant Services response code
Code describing the result of an
authorization attempt that was
either received from an endpoint or
Merchant supplied.
Please refer to the Merchant

Services Technical Specification
Manual for more information on
specific codes.
67
Field Maximum Data

20 8 N Trace # For US Debit transactions only, this
field is used for Trace Number, a
sequential eight-digit identifier
assigned by Merchant Services
ranging from 1-99999999. This
number is rolling so a merchant
may see the same number more
than once.

transactions other than US Debit
21 12 A Consumer For European Direct Debit
Country Code transactions only, this field is used
for Consumer Country Code, a two-
character alpha code indicating the
country in which the consumer’s
bank account is located.
See Appendix E for valid values

transactions other than Euro Direct
Debit.
22 7 A Category The type of exception being
reported in this data record.
Valid values:
CANCEL submission was
cancelled
DECLINE issuer declined
authorization
REJECT failed a front-end
edit
68
ACT0002 Standard Data Record and Cross Currency Option Field Descriptions,
(continued)
Field Maximum Data

23 4 A MCC Merchant Category Code.
May be blank
24 3 A Reject Code Three-character code used to identify
the reason that a transaction fails a
Merchant Services Solutions front-end
edit.
Refer to most current Merchant

Services Technical Specification for
valid Response Reason Code
Description values.

transactions with an Exception Type
other than REJECT.
25 6 A Submission The status of the submission in which
Status this transaction was included.
Valid values
ACCEPT Successfully processed
submission
CANCEL Cancelled submission
ONHOLD Submission is on hold
Sequence 2 – Cross Currency Option: The following data field is appended to a standard
ACT0002 data record ONLY if the “Cross Currency Option” is enabled. In all other
instances this field and its delimit character are suppressed.
See 3 A Settlement Three-character abbreviation for
Appendix Currency currency in which the merchant is
K being funded.
Note: This field may be blank if the

merchant is not cross currency
enabled.
69
ACT0002 IBAN Detail Option Field Descriptions
Sequence 3 - IBAN Detail Option: The following data fields are appended to a standard
ACT0002 data record ONLY if the “IBAN Detail Option” is enabled. In all other instances
these fields and their delimit characters are suppressed.
Field Maximum Data

Number Length Type Field Name Field Values and Comments
See 10 A Bank Sort Code Identifies both the bank and the
Appendix branch where the account is held.
K
See 34 A IBAN International Bank Account Number
Appendix that is comprised of the bank’s
K Country Code, a checksum and the
Base Bank Account Number
(BBAN).
Note: Base Bank Account Number

consists of up to thirty alphanumeric
characters and contains the
domestic bank account details
specific for each country.
See 11 A BIC Bank Identification Code.
Appendix
K This field may be blank.
See 35 A Creditor ID A merchant’s unique identification
Appendix number in the SEPA Direct Debit
K (SDD) scheme.
This field is double-quoted.
70
ACT0002 IBAN Detail Option Field Descriptions
Field Maximum Data

See 35 A Mandate ID A code that identifies the agreement
Appendix between the consumer and
K merchant to allow the consumer’s
direct debit account to be debited in
an automated manner over a period
of time.

See 1 N Mandate Type Sequence type of the mandate
Appendix
Valid values:
K
1 First
2 Recurrence
3 Last
4 One-off
5 New
6 Cancel
7 Change from manual to
electronic
Blank If Mandate ID and
Signature Date are blank.
See 10 A Signature Date Date customer signed the mandate.
Appendix
K Format: MM/DD/YYYY
71
Sort Order for Data Records within the ACT0002 Report are sorted based on the following
ACT0002 Data order:
Records
Category – REJECT, DECLINE, then CANCEL
PID – Ascending
Record # – Ascending
72
Financial Reports – Deposit Detail (ACT0010)
ACT0010 The ACT0010 Report provides transaction level detail for successful deposit
Report transactions.
Description
How This Merchants use this report to verify what was sent and processed against the
Report Is merchant’s own internal transaction reports. Specific usage varies by
Used merchant, but may be used for reconciliation or research of deposit activity.
The ACT0010 report is available in multiple options. The format and total
data record length varies depending on the report options selected.
Options For The ACT0010 report allows merchants to extend the standard report data
This Report record with additional data fields. Options available for this report include:
 Debit Detail (Data elements to further define debit transactions)

 Interchange Detail (Data elements associated with Interchange)
 Cross Currency (Data elements to support merchants presenting in
one currency and settling in a different currency.)
 Ext Detail (Data submitted in the “Product Record: Various Text” and
“Surcharge Amount”)
appended to each standard data record. The sequence that the optional data
fields are appended is outlined below:
Sequence 1 Standard Data Record (Data Field Number 1 to 24)

Sequence 2 Optional Debit Detail Data Record (4 Data Fields)
Sequence 3 Optional Interchange Detail Data Record (7 Data Fields)
Sequence 4 Optional Cross Currency Data Record (1 Data Fields)
Sequence 5 Optional Ext Detail Data Record (2 Data Fields)
See Appendix K – Data Field Numbering” for more information.
Record
73
HACT0010,543210,07/12/2006,07/12/2006,07/13/2006,14:15:01
Header Record.
Record Field
Descriptions
Field Maximum Data

Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
74
ACT0010 Data The ACT0010 Data Record contains the transaction detail data arranged as
Sample Data Records
ECP
RACT0010,07/12/2006,999999,”cdabe”,”20518.0106f”,273,TD,123456,USD,”01208D3”,123511111,425
497000,,5.22,EC,H,07/10/2006,123456,100,,,,,1
Credit or Debit Card
RACT0010,07/12/2006,123456,”cdabe”,”20518.0106f”,1,TD,654321,USD,”4857X2”,,444444443333333
0,08/04,5.00,VI,D,07/10/2006,622233,100,,,5999,1
Euro Direct Debit with IBAN
RACT0010,11/12/2013,123456,”cdabe”,”20518.0106f”,4,TD,654321,EUR,”4857X2”,,12345678901234,
,15.00,ED,D,11/10/2013,123456,100,,FR,,,1,1001100020,FR76 1001 1000 2000 1234 5678
934,PSSTFRPPCNE,"FR97ZZZ12345678","ABCD 1234",5,11/01/2013
Credit or Debit Card with Interchange Detail
RACT0010,07/12/2013,123456,"cdabe","12345.4321f",1,TD,654321,USD,"4857X2",,444444443333333
0,08/13,5.00,VI,D,07/10/2013,622233,100,,,,5678,1,VPDM,N,.10,.0185,.19,0,
Cross Currency
RACT0010,07/12/2006,123456,”cdabe”,”20518.0106f”,4,TD,654321,GBP,”4857X2”,,12345678901234,
,15.00,VI,D,07/10/2006,123456,100,,,,,1,USD
Cross Currency with Interchange Detail
RACT0010,07/12/2006,123456,”cdabe”,”20518.0106f”,4,TD,654321,GBP,”4857X2”,,12345678901234,
,15.00,VI,D,07/10/2006,123456,100,,,,,1,VPDM,.10,.0185,.38,,USD
Credit or Debit Card with Debit Detail
RACT0010,07/12/2006,123456,”cdabe”,”20518.0106f”,4,TD,654321,USD,”4857X2”,,12345678901234,
,15.00,EB,D,07/10/2006,123456,100,23456700,,,5542,1,10.00,0.00,1234567890,C
Credit or Debit Card with Ext Detail
RACT0010,07/12/2006,123456,”cdabe”,”20518.0106f”,1,TD,654321,USD,”4857X2”,,444444443333333
0,08/04,5.00,VI,D,07/10/2006,622233,100,,,,,1,”ABC123DEF456”,200,1
75
Standard Data Record .
Record Field
Descriptions
Field Maximum Data

2 10 A Submission Date The date on which the submission
Services. This is the calendar date
in the Eastern time zone.
Format: MM/DD/YYYY
3 10 N PID Merchant's presenter ID number.
4 6 A PID Short Name Merchant's presenter ID
abbreviated name.

submission.

6 10 N Record # Record Number is the sequential
number of a transaction within a
submission file.
76
Field Maximum Data

is always:
8 10 N Entity # Associated TD identification
number. Merchant Services
assigned.


Institution number.

transactions other than ECP or
EUDD.
12 22 A Account # Customer's credit card or
account number.

identifier is presented in this field
for EUDD transactions that are
submitted with the IBAN.
13 5 A Expiration Date The credit card account expiration
by the merchant with this
transaction.
Format: MM/YY
77
Field Maximum Data

14 17 N Amount The monetary value of the
transaction in presentment
currency.

information
etc.).

16 2 A Action Code Merchant supplied code that
indicates the type of transaction
conducted.
17 10 A Auth Date Date on which the authorization for
performed.
Format: MM/DD/YYYY
positive response from the
endpoint.
authorization attempt that was
either received from an endpoint or
Merchant supplied.

specific codes.
78
ACT0010 Standard Data Record and Debit Detail Option Field Descriptions (continued)
Field Maximum Data

20 8 N Trace # For US Debit transactions only, this
field is used for Trace Number, a
sequential eight-digit identifier
assigned by Merchant Services
ranging from 1-99999999. This
number is rolling so a merchant
may see the same number more
than once.

transactions other than US Debit.
21 12 A Consumer For European Direct Debit
Country Code transactions only, this field is used
for Consumer Country Code, a two-
character alpha code indicating the
country in which the consumer’s
bank account is located.
See Appendix E for valid values.

transactions other than Euro Direct
Debit.
22 - Blank Reserved This field is reserved for future
Note: This field is blank.

23 4 N MCC Merchant Category Code. This
field may be blank.
24 1 A Token Indicator Valid values:
1 Chase Pay Funding PAN
2 Chase Pay Consumer Digital
E-comm Payment Token
3 Consumer Digital Payment
Token
4 Chase Pay Digital POS
Token
0 Null
Blank This field may be blank
Sequence 2 - Debit Detail Option: The following data fields are appended to a standard
ACT0010 data record ONLY if the “Debit Detail Option” is enabled. In all other instances
these fields and there delimit characters are suppressed.
79
ACT0010 Debit Detail Option and Interchange Detail Option Field Descriptions
(continued)
Field Maximum Data

See 8 N Cash Back The amount of cash returned to the
Appendix Amount cardholder that was included in the
K total transaction value. May be
blank. This field is valid for retail
debit transactions and to display
Discover or Mastercard Cash Over
Amount.
See 7 N Surcharge The amount of any surcharge to the
Appendix Amount cardholder that was included in the
K total transaction value. This field is
only valid for debit transactions.
Right justified/zero filled

See 15 A Voucher # An identifying number used for EBT
Appendix debit transactions only. May be
K blank.
Left justified/blank filled

See 1 A EBT Account The Account Type for an EBT
Appendix Type (Electronic Benefits Transfer) debit
K transaction.
Valid values:
F Food Stamps
C Cash Benefits
Note: This field may be blank.

Sequence 3 – Interchange Detail Option: The following data fields are appended to a
standard ACT0010 data record ONLY if the “Interchange Detail Option” is enabled. In all
other instances these fields and their delimit characters are suppressed.
See 4 A Interchange This is a code that identifies the
Appendix Qualification Code rate at which Merchant Services
K qualified the transaction on the
front-end.
Note: This field has a value of

“NONE” for ChaseNet transactions
and may be blank or have a value
of “NONE” for other fee types.
80
ACT0010 Interchange Detail Option Field Descriptions (continued)
Field Maximum Data

See 1 A Durbin Regulated Indicates whether the issuing bank’s
Appendix card range is regulated or not as
K defined by the Durbin Amendment.
Valid values:
Y Regulated
N Exempt
See 5 N Interchange Unit Interchange fee per item as
Appendix Fee assessed by the card associations.
K
 Zero is a valid value for this field
 May be blank
See 8 N Interchange Face The interchange percentage rate
Appendix Value % Fee fee applied to the face value of this
K transaction.
 May be blank
 Zero is a valid value for this field
indicates a debit % rate to the
indicates a credit % rate
81
ACT0010 Interchange Detail Option Field Descriptions (continued)
Field Maximum Data

See 10 N Total Interchange The total interchange fee assessed
Appendix Amount by the card associations for this
K Data Record.

information.
Calculation = Sum of the (unit fee)

+ (amount * %rate).
 Decimal places agree with the

currency (i.e. 2 for USD)
field
 May be blank
Note: Calculation may not always

agree due to rounding.
See 10 N Total Assessment The total Assessment fee assessed
Appendix Amount by the card associations for this
K Data Record.

information.

field
 May be blank
indicates a debit to the
indicates a credit
82
ACT0010 Interchange Detail Option and Cross Currency Option Field Descriptions
(continued)
Field Maximum Data

See 10 N Other Debit Fee per item identified in the
Appendix Passthrough Fees merchant’s fee schedule for each
K line item. The unit fee is applied to
the unit quantity.

field
 May be blank
indicates a debit to the
indicates a credit
Sequence 4 – Cross Currency: The following data field is appended to a standard
ACT0010 data record ONLY if the “Cross Currency Option” is enabled. In all other
instances this field and its delimit character are suppressed.
See 3 A Settlement Three character abbreviation for
K being funded.
83
ACT0010 Ext Detail Option and EUDD Detail Option Field Descriptions (continued)
Sequence 5 – Ext Detail: The following data field is appended to a standard ACT0010 data
record ONLY if the “Ext Detail Option” is enabled. In all other instances this field and its
delimit character are suppressed.
Field Maximum Data
See 99 A Merchant A customized free form block of
Appendix Information Merchant specific data (up to 99
K bytes) sent in with this submission.
Left justified
See 10 N Surcharge Total surcharge amount submitted
Appendix Amount by the merchant for this
K transaction.
information.
Sequence 6 – EUDD Detail: The following data fields are appended to a standard
ACT0010 data record ONLY if the “EUDD Detail Option” is enabled. In all other instances
Field Maximum Data

K
(BBAN).
See 11 A BIC Bank Identification Code
Appendix
K
K (SDD) scheme.
84
ACT0010 IBAN Detail Option Field Descriptions (continued)
Field Maximum Data

of time.

Appendix
Valid values:
K
1 First
2 Recurrence
3 Last
4 One-off
5 New
6 Cancel
electronic
Signature Date fields are
blank.
Appendix
85
Financial Reports – Deposit Detail (ACT0010) Continued
ACT0010 Data order:
Records
PID – Ascending
Record # – Ascending
86
Financial Reports – Terminal/Batch Detail (ACT0027)
ACT0027 This delimited report provides transaction level detail (sales and refunds)
Report received from a POS terminal or similar device presented by batch. This
Description report is specific to retail merchants.
How this Merchants use this report to compare and identify discrepancies between the
Report is transaction detail reports from their terminals and those reported in the
Used Terminal Batch Detail Report. (ACT0027)
Record

HACT0027,543210,06/27/2007,06/27/2007,06/28/2007,14:15:01
87
Header Record.
Record Field
Descriptions
Field Maximum Data

2 10 A Company ID # Assigned by Merchant Services
Less any leading zeros.
Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
88
Sample Data Record

RACT0027,TD,234567,USD,987,123456,1234567898765432112,”98765432112345678912”,06/2
7/2007,Sale,100,357178.47,8976543.99
ACT0027 Data The following table defines the fields included in an ACT0027 Data Record.
Record Field
Descriptions
Field Maximum Data

occurred.
Valid value:
3 10 A Entity # Unique identifier for the transaction
division associated with the
identified terminals less any leading
zeroes, This number is Merchant
Services assigned.
Entity number does not include any

leading zeros.

5 50 A Terminal # Number identifying the POS
terminal or similar device through
which the transaction was
processed.
6 50 A Batch # Number identifying a group of sale
and refund transactions processed
through the POS terminal or similar
device indicated in the previous
field.
89
Field Maximum Data

7 22 A Account # Unique identifier that identifies the
consumer account.
8 1 A Encrypt PAN Encryption Account Status
Valid values:
blank Encryption not attempted
(default)
N Encryption not attempted
Y Encryption attempted,
decryption successful
F Encryption attempted,
decryption failed
9 22 A Merchant Unique identifier assigned to the
Order # transaction by the merchant and
submitted with the transaction.

10 10 A Transaction Date the sale or refund transaction was
Date entered into the POS terminal or similar
device.
Format: MM/DD/YYYY
11 6 A Action Type Identifies if the transaction was a sale
or refund.
Valid values:
Refund
Sale
12 6 A Auth Code 6-character code related to the positive
authorization response from the
endpoint.
13 17 N Amount Monetary value of the transaction.
See “numeric formatting” for more

information.
14 17 N Total Sum of the values in the Amount field.
This represents the total of all
transactions in the Batch # for the
Terminal Number for the Transaction
Division Number.
90
ACT0027 Data order:
Records
Entity type – TD
Terminal # - Ascending
Batch # - Ascending
91
Financial Reports – Authorization Detail (ACT0036)
ACT0036 This delimited file report provides transaction detail information on credit card
Report authorizations and ECP verification/validation and pre-notes for Merchants.
Description The report is available in coma (,), pipe (|) or tab delimited format.
How This Merchants use this report to help justify credit card authorizations, ECP
Report Is Verification/Validation and Pre-Notes fees and verifies activity reporting in the
Used submission summary and service charge detail.
Options For The ACT0036 Report allows merchants to extend the standard report data
This Report record with additional data fields. Options available for this report include:
 Fuel Option (Merchants processing fuel transactions)

 IBAN Detail (Merchants processing SEPA EUDD transactions)
appended to each standard data record. The sequence in which the optional
data fields are appended is outlined below.
Sequence 1 Standard Data Record (Data Field Positions 1 to 34)

Sequence 2 Fuel Option (2 Data Fields)
Sequence 3 Standard Data Record (16 Data Fields)
92
Record

HACT0036,543210,07/12/2004,07/12/2004,07/13/2004,14:15:01
Header Record.
Record Field
Descriptions
Field Maximum Data

Company ID less any leading

zeros.
3 10 A Report Date From The date the report activity begins.
Based on merchant end of day.
Format: MM/DD/YYYY
4 10 A Report Date To The date the report activity ends.
Format: MM/DD/YYYY
5 10 A Generation Date Date report was created. This is
the calendar date in the Eastern
time zone.
Format: MM/DD/YYYY
6 8 A Generation Time Time the report was generated,
based on Eastern time.
Format: HH:MM:SS
93
Detail Section The ACT0036 Data Record contains transaction detail for Authorizations as
- ACT0036 follows. An ACT0036 Report normally contains many ACT0036 Data
Data Record Records.
Sample Standard Data Record

RACT0036,CO,234567,USD,07/12/2004,945260,wsibpr,00303.03ABg,
13574,123456,12345678,,4444555566667777,06/11,1124.36,USD,
VI,AU,7,07/11/2004 10:25:45AM,00317C,100,57,Merchant,V,5,N,MA6T8,
I3,Y,M, USA,123456,5999,,,YYYYY,N, KT01,K001,USA,N,Y,N,N,N,N,N,N,N,,,F,1
Sample Standard Data Record with IBAN

RACT0036,CO,234567,EUR,11/12/2013,945260,wsibpr,00303.03ABg,
13574,123456,12345678,,4444555566667777,11/11,1124.36,EUR,
ED,AU,7,11/11/2013 10:25:45AM,00317C,100,57,Merchant,V,5,N,MA6T8,
I3,Y,M,FR,123456,5999,,,YYYYY,N,KT01,K001,USA,N,Y,N,N,N,N,N,N,N,,,F,1,1001100020,F
R76 1001 1000 2000 1234 5678 934,PSSTFRPPCNE,"FR97ZZZ12345678","ABCD
1234",5,11/01/2013
Record Field
Descriptions
Field Maximum Data

occurred.
Valid values:
BU Business Unit
CO Company
3 10 A Entity # Associated CO identification number.
Paymentech assigned.
4 3 A Presentment 3 character abbreviation that
Currency represents the transaction division’s
presentment currency.
5 10 A Submission Date Date of submission received by
Paymentech.
Format: MM/DD/YYYY
6 10 N PID Merchant’s presenter id number.
94
Field Maximum Data

7 6 A PID Short Name Merchant’s presenter id abbreviated
name.
submission.
9 10 N Record # Sequential number of the transaction
within the submission.
10 10 N Transaction Transaction division number assigned
Division # internally by Merchant Services.
merchant for the original sale.

Institution number.
transactions other than ECP and Euro
Debit.
13 22 A Account # Customer’s credit card or depository
financial institution account number.

identifier is presented in this field for
EUDD transactions that are submitted
with the IBAN.
14 5 A Expiration Date The credit card expiration date
(month and year) as submitted by the
merchant with this transaction. This
field is blank for ECP.
Format: MM/YY
15 17 N Amount The monetary value of the transaction
in Presentment Currency.
16 3 A Settlement 3 character abbreviation that
Currency represents the transaction division’s
settlement currency.

17 2 A Method of Code that identifies the (MOP)
Payment (MOP) method of payment for the
transaction.

95
Field Maximum Data

19 1 A Transaction Type One character code identifying the
submission type.
20 22 A Auth Performed The date and time on which the
Date/Time authorization was performed for the
transaction.
Note: The Time element of this field

may not always be present.
positive response from the endpoint.
authorization attempted that was
either received from and endpoint or
Merchant Supplied.
Please refer to the Merchant Services

Technical Specification Manual for
more information on specific codes.
23 3 A Vendor Auth The actual auth response received
Response from the endpoint.
24 10 A Auth Initiator Who initiated the authorization, ECP
Verification/Validation and Pre-Notes
attempt.
25 1 A Auth Source Provider of the response (i.e.
merchant or endpoint).
26 1 A POS Auth Source
27 1 A Voice Auth Indicates if voice authorization was
Indicator used.
28 5 A Vendor Line Indicates which communication line
Merchant Services used when
performing the authorization, ECP
Verification/Validation and Pre-Notes.
96
ACT0036 Standard Data Record, Fuel Option, and Standard Detail Data Record Field
Descriptions (continued)
Field Maximum Data

29 2 A PTI AVS Merchant Services code describing
Response Address Verification Response for the
authorization.

specific codes.
30 1 A Vendor AVS The endpoint code describing the
Response Address Verification Response.
31 1 A Card Security Value returned by the endpoint in
Value Response response to CVV2, CVC2 or CID
validation request from the merchant.
32 3 A Consumer Bank Indicates the country that the
Country Code consumers bank in located in.
Note: This is for EU Direct Debit.

33 8 A Trace # A sequential identifier assigned by
Merchant Services ranging from 1-
99999999 that is applied to debit
transactions. This number is rolling
so the merchant may see it more than
once.
34 4 A MCC Merchant Category Code.
Sequence 2 – Fuel Option: The following data fields are appended to a standard ACT0036
data record ONLY if the “Fuel Option” is enabled. In all other instances these fields and
their delimit characters are suppressed.
See 50 N Invoice # A number that is received in the
Appendix incoming file from a fuel merchant.
K
See 50 N Dealer # A number that is received in the
Appendix incoming file from a fuel merchant.
K
Sequence 3 – Standard Detail Data Record: The following data fields are appended as a
continuation of the standard ACT0036 detail data record. These fields are not optional and
are always present. The location varies depending on the Fuel Option.
97
ACT 0036 Standard Detail Data Record Field Descriptions (continued)
Field Maximum Data

See 5 A Enhanced AVS Responses are for Postal Code, Street,
Appendix Response Name, Phone, and Email.
K Valid values:
N Data does not match
R Retry
S Service not allowed
U Data unchecked
Y Data matches
Blank Data not sent
See 1 A Encrypt Pan Encryption Account Status:
Appendix
K Valid values:
blank Encryption not attempted
(default)
N Encryption not attempted
Y Encryption attempted,
decryption successful
F Encryption attempted,
decryption failed
See 4 A Fraud Score Fraud score request from the merchant.
Appendix Request
K Valid values:
KT01 Fraud Analysis Request –
Short Form
KT02 Fraud Analysis Request –
Long Form
Blank No Fraud Analysis requested
See 4 A Fraud Score Fraud score response from Safetech to
Appendix Response the merchant.
K
Please refer to the Merchant Services
Technical Specification Manual for more
information on specific codes.
See 3 A Country of Standard alpha ISO country code that
Appendix Issuance identifies the card’s issuing country.
K
Note: This field may be blank for
transactions on unsupported methods of
payment.
98
Field Maximum Data

See 1 A Durbin Regulated Card Type Indicator (CTI)
Appendix Indicates whether the issuing bank’s
K card range is regulated or not as
defined by the Durbin Amendment.
Valid Values:
Y Yes (assets greater than $10B
– regulated)
N No (assets less than $10B –
not regulated)
X Not applicable or unknown
Blank When a Card Type Indicator
response was not requested
See 1 A Commercial Card Card Type Indicator (CTI)
Appendix Indicates whether the card is a
K commercial card and is capable of
processing Level 2 or Level 3
transactions.
Valid values:
Y Yes
N No
Blank When a Card Type
Indicator response was not
requested
See 1 A Prepaid Card Card Type Indicator (CTI)
K prepaid card.
Valid values:
Y Yes
N No
requested
99
Field Maximum Data

See 1 A Payroll Card Card Type Indicator (CTI)
Appendix Indicates whether the card is a payroll
K card.
Valid values:
Y Yes
N No
requested
See 1 A Healthcare Card Card Type Indicator (CTI)
K Healthcare card.
Valid values:
Y Yes
N No
requested
See 1 A Affluent Card Card Type Indicator (CTI)
Appendix Indicates whether the card supports
K account holders with higher credit
limits.
Valid values:
Y Yes
N No
requested
100
Field Maximum Data

See 1 A Signature Debit Card Type Indicator (CTI)
K signature debit card.
Valid values:
Y Yes
N No
requested
See 1 A PINless Debit Card Type Indicator (CTI)
Appendix Indicates whether the card is PINless
K debit capable.
Valid values:
Y Yes
N No
requested
See 1 A Level III Capable Card Type Indicator (CTI)
Appendix Indicates whether the card is Level III
K capable.
Valid values:
Y Yes
N No
requested
See 0 A Reserved Reserved for future Card Type
Appendix Indicator use.
K
See 0 A Reserved Reserved for future Card Type
Appendix Indicator use.
K
See 1 A Pre/Final Valid values:
Appendix Authorization F Final
K N Undefined
P Pre Auth
May be blank
101
ACT 0036 IBAN Detail Option Field Descriptions (continued)
See 1 A Token Indicator Valid values:
Appendix 1 Chase Pay Funding PAN
K 2 Chase Pay Consumer Digital
Token
4 Chase Pay Digital POS
Token
0 Null
Sequence 4 – IBAN Detail Option: The following data fields are appended to a standard
ACT0036 data record ONLY if the “IBAN Detail Option” is enabled. In all other instances
Field Maximum Data
K
May be blank
(BBAN).

See 11 A BIC Bank Identification Code
Appendix
K This field may be blank.
K (SDD) scheme.
102
ACT 0036 IBAN Detail Option Field Descriptions (continued)
Field Maximum Data

of time.

Appendix
Valid values:
K
1 First
2 Recurrence
3 Last
4 One-off
5 New
6 Cancel
electronic
Appendix
103
ACT0036 Data order:
Records
The default sort for this report is MOP
The secondary sort is Auth Performed Date/Time
The third sort is Account #
104
Financial Reports – Interchange Qualification Detail
(ANS0013)
ANS0013 This delimited file report provides transaction detail information for Merchants
Report on front end downgrades to facilitate further research
Description
How this Merchants use this report to see if they are qualifying for the best possible
Report is rates based on their business environment.
Used
105
Record

HANS0013,543210,07/12/2004,07/12/2004,07/13/2004,14:15:01
Header Record.
Record Field
Descriptions
Field Maximum Data


zeros.
Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
106
Detail Section The ANS0013 Data Record contains transaction detail for Interchange as
- ANS0013 follows. An ANS0013 Report normally contains many ANS0013 Data
Data Record Records.
Sample Data Record

RANS0013,TD,234567,USD,VI,VCE,671,No Additional Commercial Data,
0123455432102314568,544448100585135order66,04/07/2008,121.80
Record Field
Descriptions
Field Maximum Data

always:
3 10 A Entity # Associated TD identification number.
4 10 N PID # Merchant’s presenter id number.
5 3 A Currency 3 character abbreviation for
settlement currency being reported.

transaction.

7 4 A Interchange A code that identifies the rate at
Qualification which Merchant Services qualified the
transaction.
107
Field Maximum Data

8 4 A Downgrade The value representing the reason
Reason Code the transaction qualified for a specific
Interchange Qualification.
9 70 A Downgrade The description of the value
Reason Code representing the reason the
Description transaction qualified for a specific
Interchange Qualification.
10 22 A Account # Cardholders account number.
11 22 A Merchant Order The order number submitted by the
Note: This report field is double-

quoted if the delimiter character is
used in the merchant order number.
12 10 A Deposit Date Merchants day the deposit
transaction was received.
Format: MM/DD/YYYY
Data Record.

information.
108
ANS0013 Data order:
Records
Entity type –
109
Financial Reports – Interchange Qualification
Summary (ANS0016)
ANS0016 This delimited report provides merchants with a summary of different

Report Bankcard Interchange Rates which their transactions have qualified for in a
Description given time frame. It is a snapshot which identifies if the merchant is qualifying
at the best possible rates based on their specific business environment.
How This Merchants use this data to determine if their transactions are qualifying at the
Report Is best possible rate.
Used
Record

HANS0016,543210,04/07/2008,04/07/2008,04/08/2008,14:15:01
Header Record.
Record Field
Descriptions
110
Field Maximum Data
2 10 A Company ID # Assigned by Merchant Services.
3 10 A Report Date From The date report activity begins.
Format: MM/DD/YYYY
4 10 A Report Date To The date report activity ends.
Format: MM/DD/YYYY
5 10 A Generation Date The date report was created. This
is the calendar date in the Eastern
time zone.
Format MM/DD/YYYY
Format: HH:MM:SS
111
Sample Data Record
RANS0016,TD,234567,USD,VI,V231,”Visa Business Card –CNP”,
2.00,.10,19,.20,8414.20,.21
Record Field
Descriptions
Field Maximum Data

occurred.
For this report, the value is always TD

(Transaction Division).
3 10 A Entity # Merchant Services assigned
identification number.
Entity number does not include any
leading zeros.

5 2 A Method of Two character code to identify the
Payment (MOP) method of payment (MOP).

transaction on the front end.
112
Field Maximum Data

7 30 A Interchange The description of the reason the
Qualification transaction qualified for a specific
Description Interchange Qualification.
Notes: This field is double-quoted.

8 10 N % Rate Percentage rate applied to the
amount.
If the rate changes over the course of
the reporting period there is one line
item per rate at each category.
Notes: This field may be zero.

The percentage (%) is carried to the
hundredths.
9 10 N Unit Fee Fee per item identified in the
merchant’s fee schedule for each line
item.
field
 Field may be blank
 For this field a positive amount
merchant.
 A negative amount indicates a
credit unit fee.
10 10 N Sales Count Total number of successful sales
transactions submitted for the entity
reported on within the Interchange
Qualification.
See numeric formatting for more

information.
113
Field Maximum Data

11 10 N Count % Percentage of Sales Count for the
specific Interchange Qualification for
a specific Entity Number, Currency,
MOP.
Note: The percentage (%) is carried
to the hundredths.
12 10 N Sales Amount Total amount of the successful Sales
transactions submitted for the entity
reported on within the Interchange
Qualification.
Note: This number may be positive or

negative.
13 10 N Amount % % Percentage of Sales Amount for
the specific Interchange Qualification
for the specific Entity #, Currency,
MOP.
Note: The percentage (%) is carried
to the hundredths.
ANS0016 Data order:
Records
Entity type TD
114
Financial Reports – Interchange Downgrade Summary
(ANS0017)
ANS0017 This delimited file report provides merchants with a summary of Front End
Report Interchange Downgrades for which their transactions have qualified for in a
Description given time frame.
It reports Front End downgrade reasons within each Interchange code and
(MOP) Method of Payment and should help merchants to identify their most
common Front End downgrade reasons within each Interchange Code.
How this Merchants use this report to help identify the most common Front End
Report is downgrade reasons within each interchange code.
Used
115
Record

HANS0017,543210,07/12/2004,07/12/2004,07/13/2004,14:15:01
Header Record.
Record Field
Descriptions
Field Maximum Data

Company ID less any leading zeros

Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
116
Detail Section An ANS0017 Report normally contains many ANS0017 Data Records.
- ANS0017
Data Record
Sample Data Record

RANS0017,CO,234567,USD,VI,VF01,24,708,Invalid POS Data,24,100.00,7731.37,100.00
Record Field
Descriptions
Field Maximum Data

occurred. For this report the value is
always TD.
3 10 A Entity # Associated CO identification number.
4 3 A Currency 3 character abbreviation for

transaction.

transaction.
117
Field Maximum Data

7 10 N Count Within the date range, entity,
currency, MOP:
The number of sales transactions that
qualified for this interchange level.
8 4 N Front End Front End Downgrade Reason Code.
Downgrade
Reason Code
9 70 A Downgrade Front End Downgrade Reason
Reason Code description.
Description
10 10 N Sales Count Within the date range, entity,
currency, MOP, Interchange Level:
The number of sales transactions that
that where downgraded for this
reason.
11 6 N Count % Within the date range, entity,
The % of sales transactions that
where downgraded for this reason.
Field carried to the hundredth.
12 10 N Sale Amount Within the date range, entity,
Total Sales amount of the
transactions that where downgraded
for this reason.
information.
13 6 N Amount % Within the date range, entity,
Percent Sales Amount of the
transactions that where downgraded
for this reason.
Field carried to the hundredth.
118
Sort order for Data Records within the ANS0017 Report are sorted based on the following
ANS0017 Data order:
Records
Currency
Entity
MOP (VISA prior to Mastercard prior to Carte Blanche prior to Diner’s Club
prior to Settled Diner’s Carte Blanche).
Interchange Qualification
Sales amount % of the Interchange Qualifications in descending order within
the Card Type.
Count % in descending order within the Interchange Qualification. Applies
only to Front End Downgrade Summary.
119
Financial Reports – IBAN Conversion Detail (ACT0069)
ACT0069 This delimited file report provides merchants with the detail needed to
Report support the Euro-zone’s migration from legacy bank account numbers and
Description SORT Codes to International Bank Account Numbers (IBANs) and Bank
Identification Codes (BICs) in order to process European Direct Debit
(EUDD) payments.
How This Merchants use this report to help identify IBANs and BICs provided to
Report Is consumers that use (European) Direct Debit as a method of payment but
Used have not provided merchants the required account details in the new format.
120
ACT0069 The ACT0069 Header Record identifies the data to follow and its
Header layout to the recipient system.
Record

HACT0069,543210,07/12/2004,07/12/2004,07/13/2004,14:15:01
Header Record.
Record field
descriptions
Field Maximum Data


zeros.
Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
121
Detail Section An ACT0069 Report normally contains many ACT0069 Data Records.
– ACT0069
Data Record
Sample Data Record

RACT0069,11/12/2013,00303.03ABg,TD,234567,"4857X2","ABCD1234",5,11/01/2013,"FR97ZZ
Z12345678",1001100020,12345678901234,FR76 1001 1000 2000 1234 5678
934,PSSTFRPPCNE,FR,DO,123.12,R02
Record field
descriptions
Field Maximum Data

2 10 A Submission Date Date the submission was fully
submission.
occurred. For this report the value is
always:
5 10 N Entity # Associated TD identification number
less any leading zeros. Merchant
Services assigned.

7 35 A Mandate ID A code that identifies the agreement
between the consumer and merchant
to allow the consumer’s direct debit
account to be debited in an
automated manner over a period of
time.
122
ACT0069 Data Record field descriptions (continued)
Field Maximum Data

8 1 N Mandate Type Sequence type of the mandate
Valid Values:
1 First
2 Recurrence
3 Last
4 One-off
5 New
6 Cancel
electronic
9 10 A Signature Date Date customer signed the mandate.
Format: MM/DD/YYYY
10 35 A Creditor ID A merchant’s unique identification
number in the SEPA Direct Debit
(SDD) scheme.

11 10 A Bank Sort Code Identifies both the bank and the
branch where the account is held.

12 22 A Account # Customer's account number at the
depository financial institution.
Notes: A four character "IBAN"

with the IBAN.
Account number masking is not
applied to this field.
Also referred to as Base Bank
Account Number (BBAN).
123
ACT0069 Data Record field descriptions (continued)
Field Maximum Data

13 34 A IBAN International Bank Account Number
that is comprised of the bank’s
Country Code, a checksum and the
Base Bank Account Number (BBAN).
Notes: Base Bank Account Number

characters and contains the domestic
bank account details specific for each
country.
Account number masking is not

applied to this field.
14 11 A BIC Bank Identification Code

15 2 A Country Code A code used to indicate the country in
which the consumer’s bank account is
located.
16 2 A Action Code A code that indicates the type of
transaction conducted.
17 11 N Amount The “Presentment” currency
monetary value of the transaction
submitted with legacy Account
Number.
18 3 A Response Reason A code used to identify the response
Code to the IBAN transaction action
request.
124
Continued
Sort order for Data Records within the ACT0069 Report are sorted based on the following
ACT0069 Data order:
Records
Currency
Country Code
125
Financial Reports – Mastercard Excessive Chargeback
(RSK0030)
RSK0030 This delimited report provides an account of the Mastercard Merchant

Report Chargeback to Transaction Ratio (CTR) activity. It is used to monitor a
Description merchant’s status in the MC Excessive Chargeback Program.
How This This report allows a merchant to review their Chargeback to Sales activity
Report Is and CTR (ratio). It is expected to assist the merchant in monitoring their
Used activity and in preventing reporting fees and penalties assessed in the MC
Excessive Chargeback Program.
126
Exception Reports – Mastercard Excessive Chargeback
(RSK0030)
RSK0030 The RSK0030 Header Record identifies the data to follow and its layout to the
Header recipient system.
Record

HRSK0030,654321,04/07/2008,04/07/2008,04/08/2008,14:15:01
RSK0030 The following table defines the fields included in the RSK0030 Header Record.
Header
Record Field
Descriptions
Field Maximum Data

1 8 A Record Type Constant “HRSK0030”
2 10 A Company ID # Merchant Services assigned
Company ID number less any
leading zeros.

Format: MM/DD/YYYY
Format: MM/DD/YYYY

time zone.
Format: MM/DD/YYYY
Format HH:MM:SS
127
Detail Section The RSK0030 Data Record contains details for the chargeback transactions
- RSK0030 used in calculating the merchants CTR (ratio) Chargeback to Sales Ratio for the
Data Record MC Excessive Chargeback Program
The RSK0030 Report normally contains many RSK0030 Data Records.
Sample Data Record

RRSK0030,TD,654321,USD,,9876543211,MerchantOrderNumber511,123454321234,MCC,08,M
C,04/07/2008,05/05/2008,05/05/2008,120,Descriptor,Boston,MA,C
RSK0030 Data The following table defines the fields included in an RSK0030 Data Record.
Record Field
Descriptions
Field Maximum Data

1 8 A Record Type Constant “RRSK0030”
always:
Services assigned.
4 3 A Currency 3 character abbreviation for the

5 1 A PTI Reversal Flag Set to “R” if this chargeback activity is
related to a Reversed item.
Valid value:
R Reversal

6 10 N Sequence # Merchant Services assigned
chargeback transaction identification
number.
128
RSK0030 Data Record Field Descriptions
Field Maximum Data


8 22 A Account # Cardholder's account number.
9 4 A MCC Four digit code used.
Merchant Category Code assigned to
the original transaction.
10 3 A Reason Code Code used to identify the reason for
the chargeback.
Note: Reason Codes are subject to

change. Please refer to Merchant
Services’ Chargeback Reporting
Manual for specific codes and their
descriptions.
payment method.

12 10 A Original Date of the original transaction.
Transaction Date
Format: MM/DD/YYYY
13 10 A Initiated Date The date the chargeback was initiated
by the issuing bank.
Format: MM/DD/YYYY
129
RSK0030 Data Record Field Descriptions (continued)
Field Maximum Data

14 10 A Activity Date Merchant Services’ activity date for
this report data record.
Format: MM/DD/YYYY
15 10 A Amount The value of the item included in a
report data record.
See “Numeric Formatting for more

information”.
Implied decimal
“-“ Indicates a negative amount

16 50 A Descriptor Merchant Descriptor.
17 50 A City Merchant City.
18 2 A State Merchant State.

19 1 A CNP/Retail Code indicating transaction type.
Indicator
Valid values:
C Card Not Present
R Retail
Sort Order Data Records within the RSK0030 Report are sorted based on the following
For RSK0030 order:
Data Records
TD Entity # - Ascending
PDE #
130
Financial Reports – Discover Chargeback Summary
(RSK0036)
RKS0036 This delimited summary report provides merchants with counts and amounts
Report of Discover chargeback activity to net sales and calculates their chargeback
Description ratio.
This data is used in determining whether a merchant’s chargeback activity is
qualified by Discover as excessive.
How This Merchants and internal users use this report to monitor and track Discover
Report Is chargeback activity to ensure compliance and prevent penalties in relation to
Used Discover’s excessive chargeback guidelines.
The user should be able to run this report monthly to produce a snapshot of
their status in relation to these guidelines.
131
RKS0036 The RKS0036 Header Record identifies the data to follow and its layout to
Record

HRKS0036,543210,04/07/2008,04/07/2008,04/07/2008,14:15:01
RKS0036 The following table defines the fields included in the RKS0030 Header
Header Record.
Record Field
Descriptions
Field Maximum Data

2 10 A Company ID # Merchant Services assigned
Company ID number less any
leading zeros.

Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format HH:MM:SS
132
RKS0036 Data An RKS0036 Report normally contains many RKS0036 Data Records.
Record
Sample Data Record

RRSK0036TD 234567
USD,SP,4,012345,07/08/2004,D,28.95,5444481005851350,55order66,000123,
RKS0036 Data The following table defines the fields included in an RKS0036 Data Record.
Record Field
Descriptions
Field Maximum Data

1. 8 A Record Type Constant “RSKS0036”
2. 15 A SE # Discover reference number for
Service Establishment.
3. 2 A Entity Type For this report, the value is always:
CO Company
4. 10 A Entity # The Merchant Services assigned
Company identification number for
this entity, less any leading zeroes.
5. 2 A Entity Type For this report, the value is always:
BU Business Unit
133
RKS0036 Data Record Field Descriptions (continued)
Field Maximum Data

6 10 A Entity # The Merchant Services assigned
Business Unit identification number
for this entity.
occurred. For this report, the values
is always:
8 10 A Entity # The Merchant Services assigned
Transaction Division identification
number.
9 20 A Entity Name The name associated with the
Merchant Services assigned TD
transaction identification number.
10 3 A Currency 3 character abbreviation for the

11 10 N Sales Count The number of Sales items included
in the report data record.

information.
134
Field Maximum Data

12 10 N Sales Amount The value of the Sales items included
in the Data Record.

information
13 10 N Refund Count The count of the Refund items
included in the Data Record.
14 10 N Refund Amount The value of the Refund items
included in the Data Record.

information.
15 10 N Net Transaction Net Transaction Count =
Sales Count minus Refund Count
16 10 N Chargeback The number of Chargeback items
Count included in the report data record.

information.
17 10 N Chargeback The value of the Chargeback items
Amount included in the Data Record.

information.
18 10 N Representment The number of Representment items
Count included in the report data record.

information.
135
Field Maximum Data

19 10 N Representment The value of the Representment
Amount items included in the Data Record.

information.
20 10 N Dispute Arbitration The number of Dispute Arbitration
Count items included in the report data
record.

information.
21 10 N Dispute Arbitration The value of the Dispute Arbitration
Amount items included in the Data Record.

information.
22 10 N Reversal Count The number of Reversal items
included in the report data record.

information.
23 10 N Reversal Amount The value of the Reversal items
included in the report data record.

information.
136
Field Maximum Data

24 10 N Net Sales Amount Net Sales Amount =
Sales Amount minus Refund Amount
minus Chargeback Amount plus
Representment Amount plus or minus
Dispute Arbitration Amount plus or
minus Reversal Amount.

information
25 10 N Chargeback Ratio Chargeback Ratio=
Chargeback Amount divided by Net
Sales Amount
Expressed as a %
2 decimal point implied

(0000001032=10.32%)
137
Sort Order Data Records within the RKS0036 Report are sorted based on the following
For RKS0036 order:
Data Records
# of Days Outstanding - Ascending
138
Exception Reports
All Exception Reports are compiled into one file, denoted by an “A” in the file name.
Exception Reports – Chargeback Activity (PDE0017)
PDE0017 Provides a detailed listing of chargeback transactions by division at each

Report stage of the chargeback life cycle. Identifies new chargebacks received,
Description returned to the merchant, received for recourse or represented to the issuing
bank.
This delimited report contains two sections: the summary section and the
detail section. The summary section, indicated by the Record Type
PDE0017S, provides totals for activity within each category. The detail
section, indicated by the Record Type PDE0017D, provides transaction level
details about each chargeback. Further detail about the record layouts is
provided in the Data Record Field Descriptions.
How This Merchants use this data to trigger their chargeback management process.
Report Is This may include research, updates to their customer databases, gathering
Used documentation for representments, etc.
Options for The PDE0017 report allows merchants to extend the standard report detail
this Report data record with additional data fields. Options available for this report
include:
 Cross Currency (Merchants presenting and settling in different

currencies.)
appended to each standard detail data record. The sequence in which the
optional data fields are appended is outlined below.
Sequence 1 Standard Detail Data Record (Data Field Positions 1 to 18)

Sequence 2 Optional Cross Currency Data Record (3 Data Fields) *
Sequence 3 Standard Detail Data Record (6 Data Fields) *
* Notes: If the optional Cross Currency Data Record is not selected, the
Standard Detail Data Record is Data Field Positions 1 to 22.
If the Cross Currency Option is selected the summary data record also
has Cross Currency fields appended as outlined in the Summary Record
Field Description table.
139
PDE0017 The PDE0017 Header Record identifies the data to follow and its layout to
Record

HPDE0017,543210,07/12/2005,07/12/2005,07/13/2005,14:15:01
PDE0017 The following table defines the fields included in the PDE0017 Header
Header Record.
Record Field
Descriptions
Field Maximum Data

1 8 A Record Type Constant “HPDE0017”
Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
140
Summary The PDE0017S Summary Data Record contains the chargeback transaction
Section - summary data arranged as follows. A PDE0017 Report normally contains
PDE0017S many PDE0017S Report Summary Data Records.
Summary
Data Record
Sample Summary Data Record

RPDE0017S,TD,123456,,,USD,CC,BEGINV,NON,5525,38009.92,
Sample Summary Data Record - Cross Currency

RPDE0017S,TD,123456,,,GBP,CC,BEGINV,NON,5525,38009.92,66137.26,USD
PDE0017S The following table defines the fields included in a PDE0017S Summary Data
Summary Record.
Record Field
Descriptions
Field Maximum Data

1 9 A Record Type Constant “RPDE0017S”
always:
3 10 N Entity # Associated TD identification number.
See Appendix A of Full DFR

Specifications for values.
7 2 A MOP Type Identifies the MOP type for the
Chargeback or ECP Return activity.
For this report, the value is always:
CC Credit Card
141
PDE0017S Summary Record Field Descriptions (continued)
Field Maximum Data

8 9 A Category Indicates the type of activity
represented in this record.
Valid Values
ADJPAR Adjustment for
Partial
ADJPDE Merchant Services
Adjustments
BEGINV Beginning
Inventory
ENDINV Ending Inventory
OPAREQ Outgoing pre-arb
request
OPADENY Outgoing pre-arb
denied by issuer
OPAACCEPT Outgoing pre-arb
accepted by issuer
PARREP Partial
Representments
PARRTM Partial RTM
RECD CB/Returns
Received
RECRS Accepted for
Recourse
REPR Items
Represented
RTM Representments
Returned to
Merchant
See Appendix C of Full DFR
Specifications for more information.
9 3 A Financial/ Non- Code indicating whether the activity for
Financial this data record has financial impact to
the merchant. Valid Values are:
FIN Financial
NON Non-Financial
142
Field Maximum Data

Data Record. See “Numeric
formatting” for more information.
Note: For the categories REPR and

RTM, counts are expressed as a
negative number, reflecting a
reduction to the Ending Inventory
numbers. For the category
ADJPDE, count could be either
positive or negative.
cardholder’s Presentment Currency.
The amount is always preceded by
either a dash (-) if the value is
negative or by a space if the value is
positive.
information
Notes: On this report, a positive
amount indicates an addition to
inventory. A negative amount
indicates a deletion from inventory.
This field is blank for any records
with a category of ADJPAR.
being funded.
143
Field Maximum Data

13 16 N Settlement The value of the items included in a
merchant’s settlement (funding)
currency. The amount is always
preceded by either a dash (-) if the
value is negative or by a space if the
value is positive. See “Numeric
This field is blank for any records
with a category of ADJPAR.
144
Detail Section The PDE0017D Detail Data Record contains the chargeback transaction
- PDE0017D data fields arranged as follows. A PDE0017 Report may contain many
Detail Data PDE0017D Report Detail Data Records.
Record
Sample Detail Data Record

RPDE0017D,TD,234567,8.90,N,USD,RECD,,297332290,”36H592”,4444444442881111,83,06/01/2009,07/1
1/2009,07/12/2009,8.90,,1,MC,06/01/2009,06/22/2009,123456789012345,Y,1
Sample Detail Data Record with Cross Currency
RPDE0017D,TD,234567,8.90,N,GBP,RECD,,297332290,”36H592”,4444444442881111,83,06/01/2009,07/1
1/2009,07/12/2009,8.90,,1,USD,15.49,15.49,MC,06/01/2009,06/22/2009,123456789012345,Y,1
PDE0017D The following table defines the fields included in a PDE0017D Standard
Standard Detail Data Record.
Detail Data
Record Field
Descriptions
Field Maximum Data

1 9 A Record Type Constant “RPDE0017D”
always:
3 10 N Entity # Associated TD identification number.
145
PDE0017D Standard Detail Data Record Field Descriptions (continued)
Field Maximum Data

4 17 N Issuer The amount of this chargeback at the
Chargeback time it was received from the issuer,
Presentment expressed in the cardholder’s
Currency Amount Presentment Currency. The amount
is always preceded by either a dash
(-) if the value is negative or by a
space if the value is positive.

information.

This field is blank for any records with

a category of ADJPAR.
5 1 A Previous Partial Indicates if a partial representment
Representment was processed as part of an earlier
action on this chargeback. Possible
values are:
Y Yes – a previous partial

representment applies
N No – a previous partial
representment does not apply

146
Field Maximum Data

Valid Values:
Adjustments
FEEREC Fee Received
FEEREP Fee Represent
OPAREQ Outgoing pre-arb
request
OPADENY Outgoing pre-arb
denied by issuer
OPAACCEPT Outgoing pre-arb
accepted by issuer
PARREP Partial
Representments
PARRTM Partial RTM
RECD CB/Returns
Received
RECRS Accepted for
Recourse
REPR Items
Represented
RTM Returned to
Merchant
8 1 A Status Flag Set to “R” if this CB activity is related
to a Reversed item that has been
matched incorrectly, then unmatched
by CPS.
Note: If an issuer reverses a
chargeback, there is a separate
chargeback record with a reason
code of “RV.” The reverse field is
blank.
147
Field Maximum Data

number.

11 22 A Account # Customer's credit card account
number.
the Chargeback. Reason codes are
subject to change.
Please refer to Merchant Services’

Chargeback Reporting Manual for
specific codes and their descriptions.
13 10 A Transaction Date Date of the original transaction.
Format: MM/DD/YYYY
14 10 A Chargeback Date that the chargeback was
Initiated Date initiated by the issuing bank.
Format: MM/DD/YYYY
15 10 A Activity Date Merchant Services' activity date for
this Data Record.
Format: MM/DD/YYYY
148
Field Maximum Data

16 17 N Current Action The value of the current action, as
Presentment indicated by the Category, for the
Currency item included in this Data Record and
Chargeback indicated in the merchant’s
Amount presentment currency.
For example, for an item with a

category of REPR, this would be the
amount that was represented, which
may or may not agree with the Issuer
Chargeback amount. The amount is
always preceded by either a dash (-)
if the value is negative or by a space
if the value is positive.

information.
Note: On this report, a positive

17 17 N Fee Amount The amount of the fee that may be
assessed by the issuing bank for
certain Mastercard chargeback
reason codes. The amount is always
value is positive.

information.
Notes: This field is blank for any

records with categories other than
FEEREC or FEEREP.
For Cross-Currency merchants, this

fee is expressed in the settlement
currency only.
149
PDE0017D Standard Detail Data and Cross Currency Option Field Descriptions
(continued)
Field Maximum Data

18 1 N Usage Code Single digit code 1, 2, 3, or 9 identifying
whether this is a first or second chargeback or a
dispute that falls under the Visa Claims
Resolution process. This field may be blank.
1 = First-time chargeback – all card brands

(Visa: only for disputes initiated prior to April 15,
2018)
2 = Second-time chargeback – all card brands
(Visa: only for disputes initiated prior to April 15,
2018)
3 = Second-time chargeback – MasterCard only
9 = Visa Claims Resolution (VCR) disputes
initiated April 15, 2018 or later.
Note: Some legacy Visa disputes that were

initiated prior to April 14, 2018 may still appear
with a value of “1” or “2.”
150
PDE0017D Cross Currency Option Field Descriptions (continued)
Sequence 2 – Cross Currency Option: The following data fields are appended to a standard
PDE0017 data record ONLY if the “Cross Currency Option” is enabled. In all other
instances these fields and their delimit characters are suppressed.
Field Maximum Data
See 3 A Settlement Three character abbreviation for
K being funded.

See 16 N Issuer CB The amount of this chargeback,
Appendix Settlement expressed in the merchant’s
K Currency Amount settlement currency, at the time it was
received from the issuer. The amount
is always preceded by either a dash
(-) if the value is negative or by a
space if the value is positive.

information.

See 16 N Current Action The value of the items included in a
Appendix Settlement Data Record expressed in the
K Currency Amount merchant’s settlement (funding)
value is positive.

information.

151
Sequence 3 – Standard Detail Data Record: The following data fields are appended as a
continuation of the standard PDE0017 detail data record. These fields are not optional and
are always present. Their location varies depending on the Cross Currency Option
selection.
Field Maximum Data

See 2 A MOP Code Method of payment code describing
Appendix the Payment Type associated to the
K chargeback.
See 10 A Authorization Date Date of the original authorization.
Appendix
K
Format: MM/DD/YYYY
See 10 A Chargeback Due This date represents the due date of
Appendix Date the chargeback.
K
Format: MM/DD/YYYY
See 15 A Ticket # An alpha-numeric ticket number
Appendix submitted with the original sale. This
K field is only applicable to merchants
with the Airline MCC codes.

See 1 A Potential Bundled Indicates multiple items may be
Appendix Chargebacks included in this line item.
K
Valid values:
Y Yes
See 1 A Token Indicator Valid values:
Appendix 1 Chase Pay Funding PAN
K 2 Chase Pay Consumer Digital
Token
4 Chase Pay Digital POS Token
0 Null
152
Sort order for Data Records (Summary and Detail) within the PDE0017 Report are sorted
PDE0017 Data based on the following order:
Records
FTI - Ascending
Category – See Appendix C of Full DFR Specifications
Sequence # - Ascending
153
Exception Reports – ECP Returns (PDE0018)
PDE0018 Provides a detailed listing of ECP return transactions by division at each

Report stage of the ECP return life cycle. Identifies any new ECP returns received,
Description returned to the merchant, or represented to the depository financial
institution.
This report contains two sections: the summary section and the detail
section. The summary section, indicated by the Record Type PDE0018S,
provides totals for activity within each category. The detail section, indicated
by the Record Type PDE0018D, provides transaction level details about
each ECP return. Further detail about the record layouts is provided in the
Data Record Field Descriptions.
How This Merchants use this data to trigger their ECP return management process.
Report Is This may include research, updates to their customer databases, pursuing
Used alternate methods of payment, etc.
Record
Options For The PDE0018 report allows merchants to extend the standard report detail
This Report data record with additional data fields. Options available for this report
include:

Sequence 2 Optional IBAN Detail Data Record (1 Data Field)
154
HPDE0018,543210,07/12/2016,07/12/2016,07/13/2016,14:15:01
Header Record.
Record Field
Descriptions
Field Maximum Data

Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
6 8 A Report Generation Time the report was generated
Format: HH:MM:SS
155
Summary The PDE0018S Data Record contains the ECP return transaction summary
Section - data arranged as follows. A PDE0018 Report normally contains many
PDE0018S PDE0018S Data Records.
Data Record
Sample Summary Data Record

RPDE0018S,TD,234567,,,USD,EC,RECD,FIN,4397,133470.16
Sample Summary Data Record - European Direct Debit

RPDE0018S,TD,234567,GB,,GBP,ED,RECD,FIN,4397,133470.16
PDE0018S The following table defines the fields included in a PDE0018S Summary Data
Summary Record.
Data Record
Field
Descriptions
Field Maximum Data

1 9 A Record Type Constant “RPDE0018S”
always:
Services assigned.
4 2 A Consumer Bank Used for European Direct Debit
Country Code transactions only. Indicates the
country in which the consumer’s bank
account is located. This field is blank
for any transactions that have a MOP
other than “ED”.
See Appendix E for values.
156
PDE0018S Summary Data Record Field Descriptions (continued)
Field Maximum Data

5 0 Blank Reserved for This field is not populated within this
future use report. Field is reserved for future

7 2 A MOP Identifies the MOP for the ECP Return
activity.
Valid Values:
EC US Electronic Check (ECP)
ED European Direct Debit
in this record.
Valid values:
Adjustments
BEGINV Beginning Inventory
RECD CB/Returns Received
REPR Items Represented
RTM Returned to Merchant

9 3 A Financial/ Non- Code indicating whether the activity for
Financial this data record has financial impact to
the merchant.
Valid values:
FIN Financial
NON Non-Financial
157
PDE0018S Summary Data Record Field Descriptions (continued)
Field Maximum Data

Data Record
Note: For the categories REPR and

RTM, counts are expressed as a
negative number, reflecting a
reduction to the Ending Inventory
numbers. For the category ADJPDE,
count could be either positive or
negative.
Data Record. The amount is always

158
Detail Section The PDE0018D Data Record contains the ECP return transaction detailed
- PDE0018D data arranged as follows. A PDE0018 Report may contain many PDE0018D
Data Record Data Records.
Sample Detail Data Record – ECP

RPDE0018D,TD,234567,,EC,USD,RECD,,297597456,”368F76”,24342343033,R03,05/27/2016,07
/12/2016,07/12/2016, 99.95,1,SALLY*SMITH,001234567,3,I
Sample Detail Data Record - European Direct Debit Return

RPDE0018D,TD,234567,FR,ED,EUR,RECD,,297597456,”368F76”,24342343033,R03,05/27/2016,
07/12/2016,07/12/2016, 99.95,1,SALLY*SMITH,,3,
Sample Detail Data Record - European Direct Debit Return with IBAN
RPDE0018D,TD,234567,FR,ED,EUR,RECD,,297597456,”368F76”,IBAN,R03,05/27/2016,07/12/2
016,07/12/2016, 99.95,1,SALLY*SMITH,,3,,FR76 1001 1000 2000 1234 5678 934
PDE0018D The following table defines the fields included in a PDE0018D Detail Data
Detail Data Record.
Record Field
Descriptions
Field Maximum Data

1 9 A Record Type Constant “RPDE0018D”
always:
Services assigned.
159
PDE0018D Detail Data Record Field Descriptions (continued)
Field Maximum Data

5 2 A MOP Identifies the MOP for the ECP
Return activity.
Valid Values:

Valid values:
Adjustments
BEGINV Beginning Inventory
RECRS Accepted for Recourse
REPR Items Represented
RTM Returned to Merchant

8 1 A Status flag Set to “R” if this CB activity is related
to a Reversed item - may be blank
9 10 N Sequence # Merchant Services assigned ECP
return transaction identification
number
merchant with the original sale


with the IBAN.
160
Field Maximum Data

the ECP return. Reason codes are
subject to change periodically.

Electronic Check Processing Manual
for specific codes and their
descriptions.
Format: MM/DD/YYYY
14 10 A ECP Return Date Date that the ECP return was initiated
Format: MM/DD/YYYY
this Data Record.
Format: MM/DD/YYYY
16 17 N ECP Return Amt The value of the items included in a
Data Record. The amount is always
value is positive.

information

17 1 N Usage Code Single digit code identifying whether
this is a first or second ECP return.
May be blank.
1 = First Time ECP return

2 = Second Time ECP return
18 30 A Consumer Name The cardholder name associated with
the account for this transaction.
161
Field Maximum Data

19 9 N RDFI Receiving depository financial
institution of the accountholder.
20 1 N Reason Code Valid values
Classification 1 – Insufficient /uncollected funds
2 – Unauthorized entry
3 – Administrative
4 – Miscellaneous
21 1 A Accountholder Means by which the accountholder
Authorization authorized the merchant to transact
Method on the account
Valid values
A – ARC
I – Web
P – POP
T – TEL
W – PPD
Notes: See Appendix N for an

explanation of these values.

descriptions.
162
PDE 0018D IBAN Detail Option Field Descriptions
Sequence 2 - IBAN Detail Option: The following data field is appended to a standard
PDE0018 detail data record ONLY if the “IBAN Detail Option” is enabled. In all other
instances this field and delimit character is suppressed.
Field Maximum Data

country.
163
Sort Order for Data Records within the PDE0018 Report are sorted based on the following
PDE0018 Data order:
Records
FTI - Ascending
164
Exception Reports – Chargebacks Received
(PDE0020)
PDE0020 Provides a detailed listing of new chargeback transactions received by

Report Transaction Division. This report is similar to the PDE0017 Chargeback
Description Activity Report, except that it includes detail only for new chargebacks
received. It does not include items returned to the merchant, received for
recourse or represented to the issuing bank, nor does it include the summary
section.
How this Merchants use this data to trigger their chargeback management process.
Report is This may include research, updates to their customer databases, gathering
Used documentation for representments, etc.
Record
165
HPDE0020,543210,07/12/2005,07/12/2005,07/13/2005,14:15:01
Header Record.
Record Field
Descriptions
Field Maximum Data

Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
166
PDE0020 Data The PDE0020 Data Record contains the chargeback transaction detailed
Record data arranged as follows. A PDE0020 Report may contain many Data
Records.
Sample Data Record

RPDE0020,TD,234567,,,USD,RECD,R,29733200,”38Q92”,
4444444442881111,83,05/01/2005,07/12/2005,07/12/2005,-9.90,1,Y,1234567890ABCDE,Y,1
Sample Data Record - Cross-Currency

RPDE0020,TD,234567,,,GBP,RECD,,29733229,”36H52”,4444444442881111,83,06/01/2005,07/11/
2005,07/12/2005,8.90,1,USD,15.49,Y,1234567890ABCDE,Y,1
PDE0020 Data The following table defines the fields included in a PDE0020 Data Record.
Record Field
Descriptions
Field Maximum Data

1 8 A Record Type Constant “RPDE0020”
always:
Services assigned.

represented in this record. For this
report, the value is always:
167
PDE0020 Data Record Field Descriptions (continued)
Field Maximum Data

8 1 A Status flag Set to “R” if this CB activity is related
to a Reversed item - may be blank.
number.
number.
the Chargeback. Reason codes are

Format: MM/DD/YYYY
14 10 A Chargeback Date Date that the chargeback was
initiated by the issuing bank.
Format: MM/DD/YYYY
this chargeback.
Format: MM/DD/YYYY
168
Field Maximum Data

Currency Data Record, expressed in the
Chargeback cardholder’s presentment currency.
Amount The amount is always preceded by
either a dash (-) if the value is negative
or by a space if the value is positive.

information.
Note: On this report, a positive amount

indicates an addition to inventory. A
negative amount indicates a deletion
from inventory.
17 1 N Usage Code Single digit code 1, 2, 3, or 9 identifying
whether this is a first or second
chargeback or a dispute that falls under
the Visa Claims Resolution process.
1 = First-time chargeback – all card

brands (Visa: only for disputes initiated
prior to April 15, 2018)
2 = Second-time chargeback – all card
brands (Visa: only for disputes initiated
prior to April 15, 2018)
3 = Second-time chargeback –
MasterCard only
9 = Visa Claims Resolution (VCR)
disputes initiated April 15, 2018 or later.
Note: Some legacy Visa disputes that

were initiated prior to April 14, 2018
may still appear with a value of “1” or
“2.”
Currency currency in which the merchant is being
funded.

cross-currency enabled and
selected.
169
Field Maximum Data

19 16 N Settlement The value of the items included in a
merchant’s settlement (funding)


cross-currency enabled and
selected.
20 15 A Ticket # An alpha-numeric ticket number
submitted with the original sale. This
field is only applicable to merchants
with the Airline MCC codes.
21 1 A Potential Bundled Indicates multiple items may be
Chargebacks included in this line item.
Valid values:
Y Yes
22 1 A Token Indicator Valid values:
1 Chase Pay Funding PAN
2 Chase Pay Consumer Digital
Token
4 Chase Pay Digital POS Token
0 Null
170
Sort order for Data Records within the PDE0020 Report are sorted based on the following
PDE0020 Data order:
Records
FTI - Ascending
171
Exception Reports – ECP Returns Received (PDE0022)
PDE0022 Provides a detailed listing of new ECP return transactions received by

Report Transaction Division. Identifies any new ECP returns received from the
Description depository financial institution. This report is similar to the PDE0018 ECP
Return Activity report, except that it includes detail only for new ECP Returns
received. It does not include items returned to the merchant or represented
to the issuing bank, nor does it include the summary section.
How this Merchants use this data to trigger their ECP return management process.
Report is This may include research, updates to their customer databases, pursuing
Used alternate methods of payment, etc.
Options for The PDE0022 report allows merchants to extend the standard report detail
this Report data record with additional data fields. Options available for this report
include:

Sequence 2 Optional IBAN Detail Data Record (1 Data Field)
172
Record

HPDE0022,543210,07/12/2016,07/12/2016,07/13/2016,14:15:01
Header Record.
Record Field
Descriptions
Field Maximum Data

Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
173
PDE0022 Data The PDE0022 Data Record contains the ECP return transaction detailed
Record data arranged as follows. A PDE0022 Report may contain many Data
Records.
Sample Data Record

RPDE0022,TD,234567,,EC,USD,RECD,,297503456,”3L8576”,2342343033,R03,05/27/2016,07/
12/2016,07/12/2016,9.95,1,SALLY*SMITH,003456789,3,I
Sample Data Record - European Direct Debit Return

RPDE0022,TD,234567,FR,ED,EUR,RECD,,297597456,”368F76”,24342343033,R03,05/27/2016,
07/12/2016,07/12/2016,99.95,1,SALLY*SMITH,,3,
Sample Data Record - European Direct Debit Return with IBAN Option
RPDE0022,TD,234567,FR,ED,EUR,RECD,,297597456,”368F76”,IBAN,R03,05/27/2016,07/12/2
016,07/12/2016,99.95,1, SALLY*SMITH,,3,,FR76 1001 1000 2000 1234 5678 934
PDE0022 The following table defines the fields included in a PDE0022 Standard Data
Record Field
Descriptions
Field Maximum Data

always:
less any leading zeroes assigned by
Merchant Services.
See Appendix E for values.
174
PDE0022 Standard Data Record Field Descriptions (continued)
Field Maximum Data

5 2 A MOP Identifies the MOP for the ECP
Return activity.
Valid Values:

report section, the value always is:

8 1 A Status Flag Set to “R” if this CB activity is related
to a Reversed item - may be blank.
9 10 N Sequence # Merchant Services assigned ECP
return transaction identification
number.

depository financial institution.

with the IBAN.
the ECP return. Reason codes are

descriptions.
175
Field Maximum Data

Format: MM/DD/YYYY
14 10 A ECP Return Date Date that the ECP return was initiated
Format: MM/DD/YYYY
15 10 A Activity date Merchant Services' activity date for
this Data Record.
Format: MM/DD/YYYY
16 17 N ECP Return The value of the items included in a
Amount Data Record. The amount is always
value is positive.

information.

17 1 N Usage Code Single digit code identifying whether
this is a first or second ECP return.
May be blank.
1 = First Time ECP return
2 = Second Time ECP return
3 = Third Time ECP return
18 30 A Consumer Name The cardholder name associated with
the account for this transaction.
19 9 N RDFI Receiving depository financial
institution of the accountholder.
176
Field Maximum Data

20 1 N Reason Code Valid values
Classification 1 – Insufficient /uncollected funds
2 – Unauthorized entry
3 – Administrative
4 – Miscellaneous

21 1 A Accountholder Means by which the accountholder
Authorization authorized the merchant to transact
Method on the account.
Valid values
A – ARC
I – Web
P – POP
T – TEL
W – PPD

descriptions.
177
PDE0022 IBAN Detail Option Field Descriptions
Sequence 2 - IBAN Detail Option: The following data field is appended to a standard
PDE0022 data record ONLY if the “IBAN Detail Option” is enabled. In all other instances
this field and delimit character is suppressed.
Field Maximum Data
Notes: Base Bank Account Number

country.
178
Sort Order Data Records within the PDE0022 Report are sorted based on the following
For PDE0022 order:
Data Records
179
Exception Reports – Retrieval Detail (PDE0029)
PDE0029 The Retrieval Detail report provides a detailed listing of retrieval requests
Report received from issuers by division and due date. Retrieval requests must be
Description responded to in a timely manner or the merchant runs the risk of
experiencing a chargeback and may forfeit any representment rights. Card
not present merchants have their retrieval requests fulfilled automatically by
Merchant Services, with the exception of Discover retrievals. Card not
present merchants processing Discover settled with Merchant Services need
this report to identify their Discover retrievals.
How This Merchants use this report to trigger their internal retrieval request fulfillment
Report Is processes, such as obtaining copies of sales slips or other transaction
Used validation documentation and providing it to Merchant Services to forward to
the issuing bank.
Record
180
HPDE0029,543210,07/12/2005,07/12/2005,07/13/2005,14:15:01
Header Record.
Record Field
Descriptions
Field Maximum Data

Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Time based on Eastern time
Format: HH:MM:SS
181
Detail Section The PDE0029 Data Record contains the chargeback transaction detailed
- PDE0029 data arranged as follows. A PDE0029 Report normally contains many
Data Record PDE0029 Data Records.
Sample Data Record

RPDE0029,TD,234567,USD,RETREQ,12345678,ABC4567890654321,4444444442881111,123456,21,08/30/2013,
09/30/2013,10/02/2013,8.90,5,12,AUTO,09/29/2013,12345678909876543212345
Record Field
Descriptions
Field Maximum Data

always:
less any leading zeroes. Assigned by
Merchant Services.

RETREQ Retrieval Request

6 10 N Sequence # Merchant Services assigned retrieval
transaction identification number.
182
Field Maximum Data

number.
9 6 A Authorization The authorization code that was
Code returned by the issuer. This field may
be blank.
10 3 A Retrieval Reason Code used to identify the reason for
Code the Retrieval Request. Reason codes
are subject to change.

Reason Codes 27 (Visa) & 43

(Mastercard) indicate Healthcare IIAA
transactions
-please refer to CBIS for the contact
information or contact your
chargeback analyst for these details.
Format: MM/DD/YYYY
12 10 A Retrieval Date that the retrieval request was
Received Date initiated by the issuing bank.
Format: MM/DD/YYYY
13 10 A Response Due The date by which the merchant must
Date provide a response to this retrieval
request.
Format: MM/DD/YYYY
183
Field Maximum Data

14 17 N Retrieval The amount for which the issuer is
Amount requesting a retrieval response. The amount
is always preceded by either a dash (-) if the
value is negative or by a space if the value
is positive.

information.
Note: On this report, a positive amount

indicates a sale transaction. A negative
amount indicates a refund transaction.
15 16 N Terminal # The number assigned to the terminal from
which the batch that contained the
referenced transaction was submitted
16 14 N Batch # The number assigned to the batch in which
the referenced transaction was submitted
17 4 A Fulfillment This field indicates whether the retrieval
Attribute request was auto-fulfilled by Merchant
Services or whether a fulfillment response
from the merchant is required.
Valid values:
AUTO Auto-fulfilled by Merchant
Services
RESP Merchant response required by
the due date indicated
18 10 A Authorization Date of the authorization performed for this
Date transaction.
Format: MM/DD/YYYY

19 23 A ARN The acquirer’s reference number assigned
to the transaction at the time of the
sale/refund.
184
For PDE0029 order:
Data Records
185
Exception Reports – Debit Adjustments (PDE0036)
PDE0036 Provides a detailed listing of Debit Adjustment transactions by division at

Report each stage of the Debit Adjustment life cycle.
Description
Debit adjustments are transactions that were originally presented to the debit
networks for settlement and have been disputed by a cardholder or refused
by the bank. This report identifies any new Debit Adjustments received,
returned to the merchant, or represented to the depository financial
institution.
The report provides transaction level details about each Debit Adjustment
(Merchant Initiated) and Debit Chargeback (Issuer Initiated) transaction.
Further detail about the record layouts is provided in the Data Record Field
Descriptions.
How This Merchants use this data to trigger their Debit Adjustment management
Report Is process. This may include research, updates to their customer databases,
Used pursuing alternate methods of payment, etc.
Record
186
HPDE0036,1234567899,03/20/2008,03/20/2008,03/21/2008,06:30:10
Header Record.
Record Field
Descriptions
Field Maximum Data

2 10 N Company ID # Merchant Services assigned
company identification number less
any leading zeros.
Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
187
Sample Data Record
RPDE0036,TD,1234567899,USD,RECD, ,987654321,2345623452,
03/20/2008,03/21/2008,063010,AO8,02/03/2008,03/20/2008,000000005
26,VI,P1,D,03/20/2008,00000008976543212345
Record Field
Descriptions
Field Maximum Data

occurred:
Valid value:
3 10 N Entity # Associated TD identification number
Services assigned.
Left justified/blank filled


Valid value:

6 1 A Status Flag Set to “R” if this Adjustment or
Chargeback activity is related to a
Reversed item; otherwise this field is
blank.

7 10 N Sequence # Merchant Services assigned Debit
Adjustment transaction identification
number.
188
Field Maximum Data

merchant with the original sale
Note: This field is double-quoted and

may be blank.
9 22 A Account # Customer Account Number
the Debit Adjustment. Reason codes
are subject to change periodically.

Debit Bill Payment Processing
Manual or the HLP-0015 Debit
Adjustment Reason Code report for
11 10 A Original Date of the original transaction.
Transaction Date
Format: MM/DD/YYYY
12 10 A Debit Adjustment Date the transaction was processed
Date by Merchant Services.
MM/DD/YYYY Format
13 11 N Debit Adjustment The value of the items included in a
Amt Data Record. The amount is always
value is positive.

information.

189
Field Maximum Data

14 2 A MOP Two character code used to identify
payment method.

15 2 A Action Code Indicates the action associated with
this debit transaction.

16 1 A Debit or Credit Valid values:
Cardholder D- Debit Cardholder
C- Credit Cardholder
17 10 A Auth Date Auth Date of the original transaction.
Format: MM/DD/YYYY
18 20 A Adjustment # Debit network assigned reference
number for an adjustment.
For PDE0036 order:
Data Records
Sequence # – Ascending
190
Exception Reports – Notification of Change (ACT0019)
ACT0019 Provides a detailed listing of updated bank account information for ECP
Report transactions. The source of the updates may be the Receiving Depository
Description Financial Institution (RDFI), which provides notifications via the Federal
Reserve Bank, or Merchant Services may initiate the notification based on
prior transactions.
How This Merchants use this data to update their internal systems with corrected bank
Report Is account information to prevent errors and financial losses on subsequent
Used ECP transactions. The source of the Notification of Change (NOC) helps the
merchant determine whether or not they have been updating their systems
with previous NOC information provided by Merchant Services.
Record
191
HACT0019,543210,07/12/2005,07/12/2005,07/13/2005,14:15:01
Header Record.
Record Field
Descriptions
Field Maximum Data

Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
192
ACT0019 Data The ACT0019 Data Record contains the Notification of Change (NOC)
Record detailed data arranged as follows. An ACT0019 Report normally contains
many Data Records.
Sample Data Record

RACT0019,TD,76936,USD,RECD,CP,054401487,"12349449481F",333316846201,"JAKE
RYAN",03/01/2005,C02,033306041,,,,SUBM,,,
ACT0019 Data The following table defines the fields included in the ACT0019 Data Record.
Record Field
Descriptions
Field Maximum Data

always is:
Services assigned.

RECD NOC Received
193
Field Maximum Data

6 2 A Account Type The type of consumer bank account
that the ECP transaction was drawn
against as provided by the merchant
with the original deposit transaction.
Valid values:
CK Consumer Checking
SV Consumer Savings
CP Corporate Checking
7 10 N RDFI # The Receiving Depository Financial
Institution’s ABA Routing Number as
provided by the merchant with the
original deposit transaction.
8 22 A Merchant Order # The order number as provided by the
merchant with the original deposit
transaction.

9 22 A Account # Consumer's account number as
provided by the merchant with the
original deposit transaction.
10 30 A Consumer Name The consumer’s name as provided by
the merchant with the original deposit
transaction.

11 10 A Deposit Date Date of the original deposit
transaction.
Format: MM/DD/YYYY
194
Field Maximum Data

12 3 A NOC Code Code used to identify the reason for
the NOC. Reason codes are subject
to change periodically.

ECP Processing Manual for specific
codes and their descriptions.
13 10 N Corrected RDFI The RDFI Routing Number
Routing # information that the receiving bank is
requesting be changed, which allows
the transaction to be processed
through their system successfully.
This field is only populated if the NOC
reason includes “Incorrect RDFI
Routing Number”.

14 17 A Corrected RDFI The RDFI Account Number
Account # information that the receiving bank is
This field is only populated if the NOC
reason includes “Incorrect RDFI
Account Number”.

15 30 A Corrected The Consumer Name information that
Consumer Name the receiving bank is requesting be
changed, which allows the transaction
to be processed through their system
successfully. This field is only
populated if the NOC reason includes
“Incorrect Consumer Name”.
195
Field Maximum Data

16 2 A Corrected The Consumer Account Type
Account Type information that the receiving bank is
This field is populated if the NOC
reason includes “Incorrect Consumer
Account Type”. May be blank.
Valid Values:
CK Consumer Checking
SV Consumer Savings
CP Corporate Checking
17 4 A Source The source of the NOC.
Valid values:
RTRN those returned from the
receiving bank directly
SUBM those that are being
changed by Merchant
Services based on NOCs
previously received on the
same RDFI and Account
Number
18 A Reserved This field may be blank.
196
Sort Order Data Records within the ACT0019 report are sorted based on the following
For ACT0019 order:
Data Records
RDFI # – Ascending
Deposit Date – Ascending
Consumer Account # – Ascending
197
Exception Reports – E-File Image Upload Exception
(ACT0062)
ACT0062 This delimited file report provides detail information on exceptions in the
Report image upload process.
Description
How This Merchants use this report to help identify any upload issues relating to E-File
Report Is and determine what areas are involved in the exceptions.
Used
Note: This report is only available for those merchants that have signed up
for and are using the Chargeback Multiple Document Upload Process.
198
Record

HACT0062,543210,04/14/2010,04/14/2010,04/15/2010,14:15:01
Header Record.
Record Field
Descriptions
Field Maximum Data

Company ID less any leading zeros

Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
199
Detail Section An ACT0062 Data Record contains detail for exceptions as part of the E-File
– ACT0062 image upload process.
Data Record
Sample Data Record

RACT0062,TD,234567,10414.0001y.554433.cbztiff.zip,123456789,VI,4444333355558888,
CB,000299199099.0000000000234567.20100413.02,”Image too large”
Record Field
Descriptions
Field Maximum Data

occurred.
3 20 A Entity # Associated TD identification number,
Services assigned.
submission.
5 12 N Sequence The unique sequence number for the
Number item for which there is an exception.
Payment (MOP) method of payment for the transaction

7 22 A Account # Customer’s credit card account
number.
8 2 A CB/RR Type Designates either Chargeback or
Retrieval Request Representment
Valid values:
CB – Chargeback
RR – Retrieval Request
Representment
9 44 A Image Name Name of the image supplied to
Merchant Services.
200
Field Maximum Data

10 255 A Exception Description of specific image
Description exception:
 Image too large
 Max number pages exceeded
 Invalid file ext
 Image not readable
 File could not be opened
Note: Field is double quoted.
201
Sort Order Data Records within the ACT0062 Report are sorted based on the following
For ACT0062 order:
Data Records
Entity Type – CO first, then BU, then TD
MOP
Account #
202
Informational Reports
All Informational Reports are compiled into one file, denoted by an “E” in the file name.
Informational Reports – Merchant FX Rate File

(INF0042)
INF0042 This report is used by merchants who participate in Merchant Services Cross
Report Currency settlement program. The INF0042 report provides a list of each
Description currency pair, presentment currency and settlement currency, exchange rate
(FX) for the following business day.
If a merchant is not setup for Cross Currency settlement funding, this report
does not contain any data.
As part of the Cross Currency program, a merchant may receive a daily DFR
file with the set foreign exchange rate for each currency pair (presentment
currency and settlement currency). Please refer to Merchant Services
Solutions’ Technical Specification for more information on Cross Currency
processing.
How This Merchants use this data as advance notice of the exchange rate to be
Report Is applied for the next activity date.
Used
How This Delivery: DFR only (pipe, comma or tab delimiters).

Report Is Not available in web delivery.
Generated Report is in a new “E” file type
Frequency: Daily Only

This report is generated after the 8:00 pm EST FX rate job is processed.
Hierarchy Level: Company Only
203
INF0042 The INF0042 Header Record identifies the data to follow and its layout.
Header
Record

HINF0042,543210,03/27/2012,03/27/2012,03/26/2012,20:15:01
INF0042 The following table defines the fields included in the INF0042 Header
Header Record.
Record Field
Descriptions
Field Data
Number Maximum Type Field Name Comments
Length
1 8 A Record Type Constant “HINF0042”
Solutions.
3 10 A Beginning The beginning Merchant Services
Merchant activity date to which the rate
Services Activity applies.
date
Format: MM/DD/YYYY
4 10 A Ending Merchant The ending Merchant Services
Services Activity activity date to which the rate
date applies.
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
204
INF0042 Data The INF0042 Data Record contains the FX rates established daily to be used
Record for merchant activity of the next Merchant Services activity day (beginning at
10:00 pm ET for the next activity date).
Sample Data Record

RINF0042,XYZ,999,USD,840,0.857000001
INF0042 Data The following table defines the fields included in an INF0042 Data Record.
Record Field
Descriptions The primary sort for the data in these rows is Settlement Currency Alpha,
secondary Presentment Currency Alpha.
Field Data
Length
1 9 A Record Type Constant “RINF0042”
2 3 A Presentment Three character alpha code to identify
Currency – Alpha the presentment currency.
code
3 3 N Presentment Three character ISO numeric code to
Currency – ISO identify the presentment currency.
numeric code
4 3 A Settlement Three character alpha code to identify
Currency – Alpha the settlement currency.
code
5 3 N Settlement Three character ISO numeric code to

Currency – ISO identify the settlement currency.
numeric code
6 Variable N Daily FX rate The foreign exchange rate for the
currency pair to be applied to
transactions for merchant funding.
Numeric value up to 9 decimal

places.
205
INF0042 Data Record Field Descriptions (continued)
Field Data
Length
7 n/a Blank Reserved This field is not populated within this
Merchant Services Solutions use.
8 n/a Blank Reserved This field is not populated within this
Merchant Services Solutions use.
Sort order for Data Records within the INF0042 Report are sorted based on the following
INF0042 Data order:
Records
Settlement Currency – Alpha
Presentment Currency – Alpha
206
Attribute Reports
All Attribute Reports are compiled into one file, denoted by an “H” in the file name.
Deposit Activity Attributes (ACT0078)
File The ACT-0078 Daily report is generated with a 2 day lag to minimize the risk
Generation that ARN data is not available.
Date Logic  Thursday generation is for Monday Activity
 Friday generation is for Tuesday Activity
 Saturday generation is for Wednesday Activity
 Sunday generation is for Thursday Activity
 Monday generation is for Friday Activity
 Tuesday generation is for Saturday Activity
 Wednesday generation is for Sunday Activity
Sample File 0000543210.141009.d.H212.dfr

Name
ACT0078 File The following table defines the fields included in the ACT0078 File Name.
Name Field
Descriptions
Field Maximu Data

Number m Length Type Field Name Comments
1 10 N Company ID Assigned by Merchant Services
(formerly the MA#).
Right justified and zero-filled.
2 6 N Activity Date Format: YYMMDD
report file.
Valid value:
d Daily
4 4 A File identification The first character is always “H” for
number this report file.
The remaining three characters are
on the file generation time.
For example: H212
207
Deposit Activity Attributes (ACT0078), (Continued)
ACT0078 This delimited file report provides transaction level informational attributes on
Report transactions processed by the entity. The report is available in comma, pipe
description or tab delimited format.
How this Merchants use this report to supplement information regarding deposited
report is used transactions associated with payment processing.
The ACT0078 report is not intended to be used as a reconciliation tool.
208
Deposit Activity Attributes (ACT0078), (Continued)
ACT0078 Header Record The ACT0078 Report Header Record identifies the data to
follow and its layout to the recipient system.
Header Record The following table defines the fields included in the ACT0078 Header
Field Record.
Descriptions
Sample Report HACT0078,543210,10/09/2014,10/09/2014,10/12/2014,14:12:01

File Header
Record:
Field Data
2 10 N Company ID Assigned by Merchant Services
Number (formerly the MA#)

zeros.
Format: MM/DD/YYYY
Format: MM/DD/YYYY
time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
209
Detail Section The ACT0078 Report Data Record contains transaction detail for
- ACT0078 informational attributes. An ACT0078 Report normally contains many
Report Data ACT0078 Report Data Records.
Record
Sample data RACT0078,10/09/2014,TD,999999,”A1234567”,4444333322221111,VI,DP,10/

rows - 08/2014,12345A,USD,10.00,7,1,”12345678901234567890123”, ”United
Transaction States”,”Issuer Reg”,”Issuer Name”,USD
Informational
Line
ACT0078 The following table defines the fields included in the ACT0078 Report Data
Report Data Records.
Record field
descriptions
Field Maximum Data

1. 8 A Record Type Constant “RACT0078”
2. 10 A Submission Date The date on which the submission
Services. This is the calendar date in
the Eastern time zone.
Format: MM/DD/YYYY
3. 2 A Entity Type Level at which reported event
always:
4. 10 A Entity # Associated TD identification number.
5. 22 A Merchant Order # The order number submitted by the
merchant for the transaction.
6. 22 A Account # Customer’s credit card or depository
financial institution account number

information.
210
Field Maximum Data
7. 2 A MOP Two character code to identify the
Method of Payment (Visa, Mastercard
etc.)

8. 2 A Action Code Merchant supplied code that indicates
See Appendix H for values.

9. 10 N Auth Date Date on which the authorization for
performed.
This field may be null.
Format: MM/DD/YYYY
10. 6 A Auth Code Six character code related to a
positive response from the endpoint.

11. 3 A Presentment Three character abbreviation for
transaction was conducted.
12. 16 N Amount The monetary value of the
transaction.
13. 1 A Card Usage Type Type of Card, i.e. debit or credit, as
defined by the association (Credit,
Debit, Check Card etc.
See Appendix L for values.

14. 1 A Card Product Product associated with the card as
Type defined by the association
(Consumer, Business, Purchasing
etc.)
See Appendix M for Values.

211
Field Maximum Data
15. 30 A ARN The Acquirer’s Reference Number
assigned to the transaction at the
time of the sale/refund.

16. 50 A Issuer Country Issuing Country of the Card Type

17. 50 A Issuer Region Region of the world the card is issued
in as defined by the association.

18. 60 A Issuer Name Name of the financial institution that
Issued the card

19. 3 A Settlement Three character abbreviation for
being funded.
Sort order for Report Data Records within the ACT0078 Report are sorted based on the
ACT0078 following order:
Report Data
Records
The default sort for this report is:
 PID ascending
The following are used for sorting order, but do not appear in the report.
 Submission Number
 Record Number ascending
212
Dynamic Debit Routing Reports
All Dynamic Debit Routing Comparison Reports are compiled into one file, denoted by an “I” in the file
name.
Dynamic Debit Routing Comparison (ACT0082)
File The ACT-0082 Daily report is generated once per day after receipt of the
Generation routing data for the previous Calendar day from 00:00:00 to 23:59:59.
Date Logic
Sample File 0000543210.170215.d.I212.dfr

Name
ACT0082 File The following table defines the fields included in the ACT0082 File
Name Field Name.
Descriptions
Field Maximum Data

1 10 N Entity ID Assigned by Merchant Services.
Right justified and zero-filled
2 6 N Activity Date Format: YYMMDD
report file.
Valid value:
d Daily
4 4 A File identification The first character is always “I” for
For example: I212
213
Dynamic Debit Routing Comparison (ACT0082), (Continued)
ACT0082 This delimited file report provides a detailed list of debit transactions routed
Report using the Cost Based Routing product. This report presents cost data for
description both the routed network, as well as the other eligible networks. There can be
one or more eligible networks depending upon the network(s) associated to
the BIN.
How this Clients can use this information to review the routing decisions made by the
report is used Cost Based Routing product. While standard financial reports from Chase
present only the network routed to, this report displays all eligible networks
and their associated costs.
The ACT0082 report is not intended to be used as a reconciliation tool.
Data Record The data record for this report includes a set of columns to describe the static
transaction attributes and other set of columns that populate conditionally
based upon the total number of debit networks the transaction was eligible
for. There is always at least one network populated, with most cardholder
accounts displaying two to three networks.
Other Eligible Networks

The routed network from the Network Used and Routed Network Costs
columns also appear in the Other Eligible Network, Network Product
Qualification, and Other Network Calculated Cost column.
Eligible networks are populated in the columns based upon the number
of entitled networks. For example, if there are 3 eligible networks for the
transactions, column sets 1 thru 3 are populated.
Please note it is possible for a transaction to only qualify for a single debit
network. While not common, it does occur.
214
Dynamic Debit Routing Comparison (ACT0082), (Continued)
ACT0082 Header Record The ACT0082 Report Header Record identifies the data to
File Header The following table defines the fields included in the ACT0082 Header
Descriptions
Sample Report HACT0082,123456,2/15/2017,2/15/2017,2/16/2017,10:15:12

File Header
Record:
Field Data
Report file Header Record
2 10 N Entity ID Assigned by Chase.

Format: MM/DD/YYYY
Format: MM/DD/YYYY
5 10 A Report Generation The date the report was created.
Date This is the calendar date in the
Eastern time zone.
Format: MM/DD/YYYY
6 8 A Report Generation The time the report was generated,
Format: HH:MM:SS
215
Detail Section The ACT0082 Report Data Record contains transaction detail for cost based
- ACT0082 routing attributes. An ACT0082 Report normally contains many ACT0082
Report Data Report Data Records.
Record
Sample data RACT0082,TD,222222,543210XXXXXX5000,00000000,943749,37.07,SALE,0226

rows - 2017,Y,13,MDS US,0,0.50863,PULSED,Pulse Pay
Transaction Choice,0.52656,STAR2,Standard,0.52863,MAESTR,Standard,0.50863,
,,0,,,0,,,0,,,0,,,0,,,0,,,0,,,0,,,0,,,0,,,0,,,0,,,0,,,0,,,0,,,0
Informational
,,,0
Line
ACT0082 The following table defines the fields included in the ACT0082 Dynamic Debit
Report Data Routing Comparison Report Record.
Record field
descriptions
Field Maximum Data

2 2 A Entity Type Level at which reported event occurred.
Valid value:
3 10 N Transaction Associated Transaction Division
Division Number identification number for the reported event.
4 22 A Account Number Account number associated with the
reported activity.
5 9 N Average Ticket Indicates the average ticket amount used to
Amount calculate the network routing cost.
The field is used for fuel merchants, MCC
5542, when there is an assigned value.
When there is not an assigned average
ticket value, or the merchant is not MCC
5542, then the field is zero-filled.
6 8 N Trace Number A Trace Number is a sequential eight-digit
identifier assigned by Merchant Services
ranging from 1-99999999. This number is
rolling so a merchant may see the same
number more than once.
7 17 N Transaction Monetary value of the transaction.
Amount
Note: Refer to “Numeric Formatting”.
216
Field Maximum Data
8 6 A Transaction Type SALE
(Action Code)
9 8 N Transaction Date Date of transaction.
Format: MMDDYYYY
10 1 A Exempt/Regulated
Indicates whether the issuer is
Status
regulated by the Durbin Amendment.
Valid values:
Y = Exempt, not a Durbin regulated
issuer
N = Regulated, a Durbin Regulated
issuer
11 3 N Routing Method The cost-based routing method used.
Valid values:
12 – Division Level Cost Based
used
13 – Merchant Level Cost Based
used
used; ChaseNet re-routed
Override used; ChaseNet re-
routed
used; first priority unavailable
used
12 varies A Network Network used to route transaction.
Valid values include:
 ACCEL
 INTERLINK
 MDS US
 MPS
 NYCE
 PULSE
 SHAZAM
 STAR
217
Field Maximum Data
13 2 A Debit Type Indicates whether the cardholder was
in person at the point of sale. If not
present, then the field specifies the
reason.
Sample Values:
0 - PIN debit
5 – Cardholder not present, PINless
Debit Bill Pay from a VRU
Debit Bill Pay via website
Debit Bill Pay via call center
Debit Bill Pay recurring
Debit e-commerce
14 11 N Routed Network Cost, inclusive of interchange and
Calculated Cost network/switch fees, of the
transaction for the network selected.
The remaining columns are populated based upon the number of eligible networks that
transaction could have routed to. While the following columns repeat 20 times, the average
number of eligible networks generally are 2 to 3, but more are possible.
218
Field Maximum Data
15 Varied A Other Eligible Eligible network as identified by the
Network (1..20) BIN.
Valid values include:
 ACCELD (ACCEL)
 INTLNK (INTERLINK)
 INTLPV (INTERLINK)
 MAESTR (MDS US)
 AFFN (MPS)
 CU24 (MPS)
 JEANIE (MPS)
 NYCED (NYCE)
 PULSED (PULSE)
 SHAZMD (SHAZAM)
 STAR (STAR)
 STAR2 (STAR)
16 Varied A Network Product The specific network for which the
Qualification product qualified.
17 11 N Other Network Cost, inclusive of interchange and
Calculated Cost network/switch fees, of the
transaction for specified eligible
network.
219
Fraud Advice Reports
Visa Fraud Advice Reports are delivered in one file denoted by a “J” in the file name, and Mastercard
Fraud Advice Reports are delivered in one file denoted by a “K” in the file name.
Visa Fraud Advice (RSK0068)

File The RSK0068 report is generated once per day after receipt of the Visa
Generation Fraud data for the previous Calendar day, or after the first of the month for
Date Logic the previous Calendar Month data.
Sample File 0000543210.170228.d.J212.dfr

Name
RSK0068 File The following table defines the fields included in the RSK0068 File
Name Field Name.
Descriptions
Field Maximum Data

Notes: For those merchants set up
for entity level reporting, Company
ID becomes the Entity ID.
ID/Entity ID field identifies the entity
level.
Valid values:
0 Company
1 Business Unit
4 Reporting Group
Company
5 Reporting Group Business
Unit
6 Reporting Group
Transaction Division
Note: Funds Transfer Instruction
and Reporting Group Funds
Transfer Instruction are not
applicable for this report.
220
Visa Fraud Advice (RSK0068), (Continued)
Field Maximum Data
file. For example, a daily file
created for the activity of the 28th
of February, 2017 would have an
activity date of “170228”
Format: YYMMDD
report file.
Valid values:
c Calendar Month
d Daily
Note: Each Entity ID can only
select a single frequency for the
report. A given entity must select
either Monthly or Daily as their
frequency. They cannot choose
both.
4 4 A File identification The first character is always “J” for
For example: J212
221
RSK0068 Provides a list of fraudulent advice records reported by all Issuers to Visa.
Report This report presents specific information related to the fraud record with
description additional data that allows the record to be tracked against the original
transaction.
How this Merchants can use this information to respond to potential risky transactions
report is used and decision them faster and more accurately. The report can be used to
balance activities in making transaction acceptance decisions by using
processes and tools to keep as many “good” transactions as efficiently and
quickly as possible while preventing those considered risky. Issuers provide
fraudulent records to the networks that then provide them to merchants via
their acquirers.
For further information regarding Visa’s Fraud Advice data, please contact
your Risk Analyst or Account Executive.
The RSK0068 report is not intended to be used as a reconciliation tool.
Data Record The data records for this report includes a set of columns to describe the
static transaction attributes based on fraud records submitted by the Issuer to
Visa. The records also contain enhanced data to support tracking against
original transaction such as Merchant Order Number. The report also
includes other attributes related to customer hierarchy such as Transaction
Division (TD) and Company Number (CO).
222
RSK0068 Header Record The RSK0068 Report Header Record identifies the data to
File Header The following table defines the fields included in the RSK0068 Header
Descriptions
Sample Report HRSK0068,123456,2/28/2017,2/28/2017,3/01/2017,10:15:12

File Header
Record:
Field Data
Format: MM/DD/YYYY
Format: MM/DD/YYYY
Eastern time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
223
Detail Section The RSK0068 Report Data Record contains transaction detail of fraudulent
- RSK0068 accounts reported to Visa. A RSK0068 Report normally contains many
Report Data RSK0068 Report Data Records.
Record
Sample data RRSK0068,TD,222222,“00555555abc“,4003,444444,2469216712100012345678

rows - 9,tst091,222222000123456,436535XXXXXX0000,M,0919,4,246.68,840,6,601
Transaction 2,408-724-9160,NJ,AUTO IVR,03079,NH,1,10,4000,1,01,9,1116
Informational
Line
RSK0068 The following table defines the fields included in the RSK0068 Visa Fraud
Report Data Advice Report record.
Record field
descriptions
RSK0068 Note: Due to the source of the data, some fields may not be available as
Report Data part of a transaction or may be blank.
Omissions Note: Certain fields may contain special characters within the data sent by
the card program. If these special characters are also the merchant delimiter,
CMS will remove the special characters coming from the card program that
are delimiters (comma, pipe) and replace with a space.
Field Maximum Data

occurred.
Valid value:
3 10 N Entity ID Associated identification number for
the reported event.
This is always the Transaction
Division number for this report.
4 22 A Merchant Order Number The order number submitted by the
5 4 N Account Sequence Identifies the associated occurrence
Number that the account was reported as
fraudulent to Visa.
224
Field Maximum Data

6 6 N Reference ID Internal Chase Merchant Services
identification number.
7 23 N Acquirer The acquirer’s reference number
Reference assigned to the transaction at the
Number time of the sale/refund.
8 6 A Authorization The authorization code that was
Code returned by the issuer.
9 15 A Card Acceptor ID A unique value assigned by Chase
Merchant Services to identify the
merchant to the Payment Brand
(Visa).
10 19 N Account Number Cardholders account number
11 1 A Card Capability Indicates the security capability of the
Code card used on the transaction.
Valid values are:
M = Magnetic stripe with no CVV
encoded
V = Magnetic stripe with CVV
encoded
C = Chip Card
null = unidentified
12 4 N Expiration Date The credit card account expiration
by the merchant with this transaction.
Format: MMYY
13 1 A Cardholder Indicates the type of identification
Identification used at the time of the transaction.
Method
Possible Values:
0 = Unknown
1 = Signature
2 = PIN
3 = Unattended terminal; no PIN
pad
4 = Mail or phone order
225
Field Maximum Data

14 12 N Fraud Amount The transaction amount in the
(Local Currency) issuer's currency for the transaction
identified as fraudulent.
When the fraud is reported by an
acquirer, the transaction amount must
be in the currency of the merchant's
country.
15 3 N Fraud Currency Three character currency
Code abbreviation for the transaction being
reported as a fraudulent.

16 1 A Fraud Type Visa defined type of Fraud reported
by the Issuer or the Acquirer.
Valid Values:
0 – Lost – the card was reported
as lost by the cardholder at the
time of the transaction.
1 – Stolen – the card was reported
as stolen by the cardholder at the
2 – Card Not Received as Issued –
the card was reported as not
received by the cardholder at the
3 – Fraudulent Application –the
cardholder never applied for the
card OR the information given on
the application was falsified.
4 – Issuer-Reported Counterfeit –
the cardholder did not knowingly
participate in a transaction OR the
card or magnetic stripe used in a
Card Present environment has
been unlawfully altered or
duplicated.
226
Field Maximum Data
1 A Fraud Type, Valid Values, (Continued):
(Continued) 5 – Miscellaneous/Account
Takeover—the transaction was not
authorized by the cardholder.
6 – Fraudulent Use of Account
Number – the transaction was not
authorized by the cardholder OR the
account was never issued. (Card not
present / MOTO / Internet)
7 – (U.S. only) used by ICS. (Issuers
Clearinghouse Service).
9 – Acquirer-reported counterfeit—
Acquirer indicated that the
transaction involved is an unissued
or invalid Bank Identification Number
(BIN).
A – Incorrect processing.
B – Account or Credential takeover.
17 4 N MCC Merchant Category Code.
18 13 A Merchant City The City or Municipality where the
transaction took place or where the
Merchant doing business has deemed
their address.
Note: Refer to the special character
note under data omissions.
19 3 A Merchant Country The Country where the transaction took
place or where the Merchant doing
business has deemed their address.
20 25 A Merchant Name The name of the merchant originating
the transaction.
21 10 A Merchant Postal The Postal Code where the transaction
Code took place or where the Merchant doing
business has deemed their address.
22 3 A Merchant State or The State or Province where the
Province transaction took place or where the
Merchant doing business has deemed
their address.
227
Field Maximum Data

23 1 A MOTO / ECI Valid values are:
Mail Order, Space = Not available
Telephone Order 1 = Single transaction for a
or Electronic mail/telephone order
Commerce
2 = Recurring transaction
Indicator
3 = Installment payment
4 = Unknown classification/other
mail order
5 = Secure electronic commerce
transaction
6 = Non-authenticated security
transaction at a 3-D Secure-
capable merchant and merchant
attempted to authenticate the
cardholder using 3-D Secure
transaction
8 = Non-secure transaction
transaction at a SET-capable
merchant
24 2 N Multi-clearing A system-generated number
Sequence specifying the clearing sequence of
Number Custom Payment Service
(CPS)/Passenger transport
transactions.
Identifies which transaction within a
group of transactions resulting from a
single authorization.
25 4 N Network ID Identifies a Visa transaction
processing network path.
228
Field Maximum Data

26 1 N Notification Code Indicates the record type of the
transaction from Visa.
Valid Values:
1 – Addition
2 – Addition of subsequent
identical (duplicate) transaction
3 – Change
4 – Delete
5 – Reactivate
27 2 A POS Entry mode Indicates how the transaction was
originated.
Please refer to Appendix O.
229
Field Maximum Data

28 1 A POS Terminal Indicates the capability of the device
Capability used to originate the transaction.
Valid values:
0 – Unknown
1 – No terminal
2 – Magnetic stripe reader
3 – Bar code reader
4 – OCR reader
5 – Integrated circuit chip reader
6 – MICR read (POS Check
Service) U.S. only
7 – MICR read and image CPBL
(POS check service) U.S. only
9 – Key entry only, no electronic
reading capability
N - not provided in the original
transaction
29 4 N Purchase Date The original sale date of the
transaction.
Format: MMDD
230
Mastercard Fraud Advice (RSK0069)
File The RSK0069 report is generated once per day after receipt of the
Generation Mastercard Fraud data for the previous Calendar day, or after the first of the
Date Logic month for the previous Calendar Month data.
Sample File 0000543210.170228.d.K212.dfr

Name
RSK0069 File The following table defines the fields included in the RSK0069 File
Name Field Name.
Descriptions
Field Maximum Data

Notes: For those merchants set up
for entity level reporting, Company
ID becomes the Entity ID.
ID/Entity ID field identifies the entity
level.
Valid values:
0 Company
1 Business Unit
4 Reporting Group
Company
5 Reporting Group Business
Unit
6 Reporting Group
Transaction Division
Note: Funds Transfer Instruction
and Reporting Group Funds
Transfer Instruction are not
applicable for this report.
231
Mastercard Fraud Advice (RSK0069), (Continued)
Field Maximum Data
file. For example, a daily file
created for the activity of the 28th
of February, 2017 would have an
activity date of “170228”
Format: YYMMDD
report file.
Valid values:
c Calendar Month
d Daily
Note: Each Entity ID can only
select a single frequency for the
report. A given entity must select
either Monthly or Daily as their
frequency. They cannot choose
both.
4 4 A File identification The first character is always “K” for
For example: K212
232
RSK0069 Provides a list of fraudulent advice records reported by all Issuers to

Report Mastercard. This report presents specific information related to the fraud
description record with additional data that allows the record to be tracked against the
original transaction.
How this Merchants can use this information to respond to potential risky transactions
report is used and decision them faster and more accurately. The report can be used to
balance activities in making transaction acceptance decisions by using
processes and tools to keep as many “good” transactions as efficiently and
quickly as possible while preventing those considered risky. Issuers provide
fraudulent records to the networks that then provide them to merchants via
their acquirers.
For further information regarding Mastercard’s Fraud Advice data, please

contact your Risk Analyst or Account Executive.
The RSK0069 report is not intended to be used as a reconciliation tool.
Data Record The data records for this report includes a set of columns to describe the
static transaction attributes based on fraud records submitted by the Issuer to
Mastercard. The records also contain enhanced data to support tracking
against original transaction such as Merchant Order Number. The report
also includes other attributes related to customer hierarchy such as
Transaction Division (TD) and Company Number (CO).
233
RSK0069 Header The RSK0069 Report Header Record identifies the data to
Record follow and its layout to the recipient system.
File Header The following table defines the fields included in the RSK0069 Header
Descriptions
Sample Report HRSK0069,123456,2/28/2017,2/28/2017,3/01/2017,10:15:12

File Header
Record:
Field Data
Format: MM/DD/YYYY
Format: MM/DD/YYYY
Eastern time zone.
Format: MM/DD/YYYY
Format: HH:MM:SS
234
Detail Section The RSK0069 Report Data Record contains transaction detail of fraudulent
- RSK0069 accounts reported to Mastercard. A RSK0069 Report normally contains
Report Data many RSK0069 Report Data Records.
Record
Sample data RRSK0069,TD,222222,“00555555abc“,GBR,Great Britain,Chase,

rows - 5555444433332222,08/30/2017,08/30/2017,12:20:01,193.33,840,US
Transaction Dollar,193.33,11111,Agg Merch Name,22222,Key Agg Merch
Name,33333333,Parent Agg Merch Name,123456789,222222000123456,ABC
Informational
International Inc.,London,UK,SE1 2AA,MC Premium
Line Gold,04,123456789,10987654321,111222333,01,United States,5999,MOTO
Merchant,01,71111111111111111111111,01,Y,1,U,N,N,9999,Fraud
RSK0069 The following table defines the fields included in the RSK0069 Visa Fraud
Report Data Advice Report record.
Record field
descriptions
RSK0069 Note: Due to the source of the data, some fields may not be available as
Report Data part of a transaction or may be blank.
Omissions Note: Certain fields may contain special characters within the data sent by
the card program. If these special characters are also the merchant delimiter,
CMS will remove the special characters coming from the card program that
are delimiters (comma, pipe) and replace with a space.
Field Maximum Data

occurred.
Valid value:
3 10 N Entity ID Associated identification number for
the reported event.
This is always the Transaction
Division number for this report.
4 22 A Merchant Order Number The order number submitted by the
5 3 A Issuer Country code Country Code of Card Issuer.
6 30 A Issuer Country name Country Name of Card Issuer.
235

Field Maximum Data
7 60 A Acquirer ICA The name of the payment processing acquirer
Name (Example: Chase Merchant Services).
Note: Refer to the special character note under
data omissions.
8 19 A Account Cardholders account number.
Number
9 10 A Process Date The date that Mastercard processed the fraud
claim.
Format: MM/DD/YYYY
10 10 A Transaction Local date at the merchant location when the
Date transaction occurred.
Format: MM/DD/YYYY
11 6 A Transaction Local time at which the transaction took place at
Time the card acceptor (merchant).
Left Blank if unavailable.
Format: HHMMSS
• HH = Hours
• MM = Minutes
12 20 N Transaction Transaction amount in the original currency of
Amount the transaction.
13 3 A Currency Numeric ISO currency code.
Code Code defining the currency.
14 30 A Currency Currency Description.
Name Note: Refer to the special character note under
data omissions.
15 17 N USD Amount Transaction Amount in US Dollars and Cents.
16 5 N Aggregate Number assigned by Mastercard to a unique
Merchant ID entity for transaction processing.
17 75 A Aggregate The label assigned by Mastercard to a unique
Merchant entity for transaction processing.
Name Note: Refer to the special character note under
data omissions.
18 5 N Key Aggregate Identifies a unique entity assigned by
Merchant ID Mastercard, which represents a processing
group or single transaction division.
19 74 A Key Aggregate The label assigned by Mastercard to the second
Merchant level of hierarchy which represents a processing
Name group or single transaction division.
Note: Refer to the special character note under
data omissions.
20 8 N Parent Identifies a unique entity assigned by
Aggregate Mastercard, which represents the highest level
Merchant ID of the hierarchy.
236
Field Maximum Data
21 75 A Parent Aggregate The label assigned by Mastercard
Merchant Name which represents the highest level of
the hierarchy.
22 9 A Merchant Location Identifies a physical location within a
ID merchant, assigned by Mastercard
where transactions can occur.
23 15 A Merchant Id Card Acceptor/Merchant’s unique
identification number, assigned by the
acquirer.
24 25 A Merchant Name Name of the card acceptor (“Doing
Business As” name).
25 19 A Merchant City City in which merchant is located.
26 30 A Merchant State If the card acceptor is in the United
States, the state in which the
merchant is located.
27 10 A Merchant Postal Postal code at the merchant location.
Code
28 50 A Card Product Describes the type of card the
Type transaction was processed on.
29 2 A Fraud Type Code MC defined type of Fraud reported by
the Issuer or the Acquirer.
See Appendix O for values.
30 9 A Banknet The numeric code given to the
Reference merchant upon approval or decline of
Number a transaction from MC.
31 11 A Mastercard Identifies an internal MC attribute that
Assigned ID indicates the registration of a
(MAID) company.
32 20 N Sequence A number generated to identify a
Number unique occurrence of a transaction in
the MC data repository.
33 2 A Region Code Code that identifies a geographic
region
Sample of valid values:
01 - United States
02 - Canada
237
Field Maximum Data
34 30 A Region Name The label that identifies a geographic
region.
Sample of valid values:
 United States
 Canada
35 4 A Merchant Indicator used to classify a merchant’s
Category product or service.
Code(MCC) May be blank.
36 50 A Merchant Text based on MCC code.
Category Name Note: Refer to the special character
37 2 A Secure Code UCAF data status.
38 23 A Acquirer The acquirer’s reference number
Reference assigned to the transaction at the time
Number of the sale/refund.
39 2 A POS Entry Mode Indicates how the transaction was
Code originated.
See Appendix P for values.
40 1 A Cardholder Indicates whether the card was
Presence Code present at the time of the transaction.
41 1 A CVC Code Indicates whether the CVC 1 or 2 was
valid when authorization was
attempted.
42 1 A Fraud Sub-Type Refer to Sub-fraud Type Codes in
Code SAFE for values.
Valid Values:
K – Convenience or Balance
Transfer check transaction
N – PIN not used in transaction
P – PIN used in transaction
U – Unknown
43 1 A Card Not Present Electronic commerce indicator.
Indicator
44 1 A ATM Code Automated Teller Machine Code.
This field can be blank.
45 4 A Reason Code Code that identifies the type of
fraudulent activity that was reported to
Mastercard.
46 100 A Reason Name Label that identifies the type of
fraudulent activity that was reported to
Mastercard.
238
File Trailer
File Trailer The File Trailer is used by the recipient system to indicate that the end of the
file has been reached.
File Trailer The following table defines the fields included in the File Trailer preceded by
Field an example data record.
Descriptions
Sample File Trailer

*DFREND, PID=123456,FREQ=DAILY,CO=111111
Field Maximum Data

1 7 A Constant *DFREND
2 14 A Presenter’s ID Assigned by Merchant Services;
(PID) preceded by PID=
Note: Field length includes

preceding characters
3 14 A Frequency Frequency at which this file is
generated and delivered.
Preceded by FREQ=
Valid values:
CALENMON Calendar Month
DAILY Daily
FISCALMON Fiscal Month
OTHER Other Frequency
WEEKLY Weekly
Note: Field length includes

preceding characters.
239
File Trailer
Field Maximum Data

4 13 A Company Assigned by Merchant Services.
ID/Entity ID
The first two characters of the
Company ID/Entity ID field identifies
the entity level.
Valid values:
CO Company
BU Business Unit
FT Funds Transfer Instruction
RC Reporting Group - Company
RB Reporting Group - Business
Unit
RT Reporting Group – Transaction
Division
RF Reporting Group - Funds
Transfer Instruction
Entity level value is followed by an

equal sign (=) and then the entity
number.
240
Appendices
Appendix A – Currency Abbreviations
Currency The following table defines the fourteen settlement currencies supported by
Abbreviation Merchant Services that are indicated by the three-character currency codes
Definitions used in delimited file reports. For the full list of 155 presentment currencies
that are available to merchants using Merchant Services’ Cross-Currency
product, please refer to the latest revision of the batch processing technical
specifications.
ISO CURRENCY DESCRIPTION

CODE ABBREVIATION
036 AUD Australian Dollars
124 CAD Canadian Dollars
756 CHF Swiss Franc
208 DKK Danish Krone
978 EUR Euro
826 GBP British Pounds
344 HKD Hong Kong Dollars
392 JPY Japanese Yen
578 NOK Norwegian Krone
544 NZD New Zealand Dollars
752 SEK Swedish Krona
702 SGD Singapore Dollar
840 USD US Dollars
710 ZAR South African Rand
Sort Order The table above indicates the order in which the Currency Abbreviations are
For Currency sorted within each applicable report.
Abbreviations
241
Appendix B – MOP Codes
MOP Code The following table lists the two-character Method Of Payment (MOP) codes
Definitions used in delimited file reports.
MOP Description
AE ACCEL PIN-Based Debit
AF AFFN PIN-Based Debit
AK Alaska PIN-Based Debit
AP ACCEL PINless Debit
AX American Express
BL Bill Me Later
BP Bill Me Later Private Label
CR Chase Signature Debit
CU CU24 PIN-Based Debit
CX Chase PIN-Based Debit (future enhancement)
CZ Chase Credit
DD Discover Diners
DI Discover
DP Generic PINless Debit
EC Electronic Check (non-encrypted and encrypted accounts)
EN Encryption
ID Interac
IL Interlink PIN-Based Debit
IM International Maestro
JC JCB
JN Jeanie PIN-Based Debit
MC Mastercard
MP MoneyPak
MR Mastercard Restricted Debit (future enhancement)
MT Maestro PIN-Based Debit
NP NYCE PINless Debit
NY NYCE PIN-Based Debit
PP Pulse PINless Debit
PS Pulse PIN-Based Debit
PY PayPal
SP Star PINless Debit
SR Star PIN-Based Debit
SV Gift Card
SW UK Domestic Maestro
SZ Shazam PIN-Based Debit
VI Visa
VR Visa Debit (Used for processing “Canadian Restricted Debit” transactions)
For the most currently listing of MOP codes please refer to our Technical Processing Format
Specifications.
242
Appendix C – Category Values
Category The following table defines the categories indicated by the Category Codes
Code used in delimited file reports.
Definitions
Category
Code Category Name Category Description
ADJPAR Adjustment for This line item is provided as an inventory balance
Partial Items control item for ‘split chargebacks’. A ‘split
chargeback enters inventory as one item but is
deducted from inventory two times: once as a
Representment and once as a Return To
Merchant item. This balancing entry adjusts the
inventory counts only (not amounts) to remove
the redundancy.
ADJPDE Merchant Services Any manual adjustments performed by Merchant
Adjustments Services to adjust inventories during the reporting
period
AUTH Auth Only Transactions submitted with an Action Code A.
Auth Only excludes authorizations performed as
a result of a B or D action code. Auth Only
includes authorizations received via batch or
online
BEGINV Beginning Count and value of items in chargeback/return
Inventory inventory at the beginning of the reporting period
BUW Back Up This value represents the amount withheld for the
Withholding timeframe reported. Data records with this
category only appear on the FIN0010 report if the
BUW amount is greater than zero.
Back Up Withholding reflects a percentage of

gross sales withheld by the IRS if the Tax
Identification Number (TIN) on file with Merchant
Services is either blank or invalid according to the
IRS.
CB Net Chargeback The sum of adjustments affecting the merchant’s
Activity current balance related to chargeback activity
CNREF Cancelled Action-code based. This is any refund type
Refunds action code txn that was included in a cancelled
submission
CNSALE Cancelled Sales Action-code based. This is any sale type action
code txn that was included in a cancelled
submission
243
Category Code Definitions (continued)
Category
DBADJ Net Debit The sum of adjustments affecting the merchant’s
Adjustment running balance related to Debit Adjustment
Activity activity
DBREF Auth Only – Debit Debit Refund authorization action codes
Refund
DBSALE Auth Only – Debit Debit Sale authorization action codes
Sale
DEC Declined Deposits Deposit-type action code transactions that were
not depositable due to a hard decline
EFEFT Effective Funds Funds transfer that is anticipated to be credited to
Transfer the merchant’s bank account by the merchant’s
financial institution. These are funds transfers that
have reached their effective date
ENDINV Ending Inventory Items included in chargeback/return inventory at
the end of the reporting period
ERET Net ECP Return The sum of adjustments affecting the merchant’s
Activity running balance related to ECP Return activity
FEEREC Fee Received The amount of the fee assessed by the issuing
bank for certain Mastercard chargeback reason
codes. The monetary impact of the fee itself is
included in the FIN0011 report under the category
PDE. This Category is used on the PDE0017
report to provide detail about the chargeback
transaction that resulted in this fee
FEEREP Fee Represent The amount being returned to the merchant as the
result of representment of the fee assessed by the
issuing bank for certain Mastercard chargeback
reason codes. The monetary impact of
representment of the fee itself is included in the
FIN0011 report under the category PDE. This
Category is used on the PDE0017 report to
provide detail about the chargeback transaction
that resulted in this fee
HOLDFT On Hold Funds Funds transfer that was created but put on hold
Transfer and not yet transferred to the merchant’s financial
institution
244
Category
Report Field
IA Interchange & The sum of fees for all service codes that
Assessment Fees represent pass through costs from certain
endpoints (interchange and assessments).
Note: ChaseNet Fees are reported with this
category code.
NET Net Settled Settled Sales deposited less Settled Refunds
Deposit Amount deposited
NON Non-Financial Non-financial transactions include FPO
Modification requests, Stored Value or any
other transactions that have no financial
impact
OTH Other Adjustments The sum of adjustments affecting the
merchant’s running balance related to
anything other than fees, chargebacks, ECP
Returns, or Reserves
OPAREQ Outgoing Pre- Indicates that an outgoing pre-arbitration has
Arbitration been sent to the issuer to challenge a Visa
Request Allocation dispute
OPADENY Outgoing Pre- Indicates that an outgoing pre-arbitration that
Arbitration was sent to the issuer to challenge a Visa
Request Denied Allocation dispute has been denied by the
issuer
OPAACCEPT Outgoing Pre- Indicates that an outgoing pre-arbitration that
Arbitration was sent to the issuer to challenge a Visa
Request Accepted Allocation dispute has been accepted by the
issuer
PARREP Partial Indicates the represented portion of a ‘split
Representment chargeback’, where a part of the value of the
original CB was able to represented and the
balance is Returned To Merchant
PARRTM Partial Return To Indicates the returned-to-merchant portion of a
Merchant ‘split chargeback’, where a part of the value of
the original CB was able to represented and
the balance is Returned To Merchant
PENDFT Pending Funds Funds transfer that was created to be
Transfer transferred to the merchant’s financial
institution but has not yet reached its effective
date (the date on which it is anticipated that
the financial institution will credit the
merchant’s bank account)
245
Category
PFEE Merchant Services The sum of fees assessed by Merchant Services
Fees for all service codes that include Merchant
Services costs
PRE ECP Transactions that were verified, validated or pre-
Ver/Val/Prenote noted as part of Electronic Check processing
PREDB Pre-Auth - Debit Debit pre-authorization action codes
RECD New New chargeback/return items received during the
Chargebacks/ECP reporting period
Returns Received
RECRS Accepted items Items received from the merchant and accepted
received for for recourse during the reporting period
recourse
REF Refunds All refund type items successfully submitted for
deposit. Rejects and Declined Deposits are not
included
REJ Rejected Items Transactions of any action code that did not pass
Merchant Services front-end edit checks
REJFT Rejected Funds Funds transfer that was created and sent to and
Transfer subsequently rejected by the merchant’s financial
institution
REPR Items represented Items submitted for representment during the
reporting period
RES Reserve The sum of adjustments that affected the
Adjustments merchant’s current balance for reserve entries
during the reporting period
RETREQ Retrieval Request New retrieval request items received during the
Received reporting period
RTM Items Returned to Items returned to the merchant for handling during
Merchant the reporting period
SALE Sales All sale type items successfully submitted for
deposit. Rejects and Declined Deposits are not
included
Sort Order The table above indicates the order in which the Category values are sorted
For Category within each applicable report. Please note that not all values are valid for
Values every report. See individual report field definitions for valid value sets for that
report.
246
Appendix D – Sub-Category Values
Sub-Category The following table defines the categories indicated by the Sub-Category
Code codes used in delimited file reports (FIN0011 Service Charge Detail only).
Definitions
Sub-
Category Sub-Category
Code Name Sub-Category Description
AS Assessment One Data Record for each Visa and
Mastercard Assessment Fee (aggregated
for all Interchange Qualification levels)
AUTH Authorization Includes all Authorization Fees. There are
Fees separate Data Records for each unique item
description
DEP Deposit Fees Fees related to transaction Deposit
processing. There are separate Data
Records for each unique item description
EQUIP Equipment Fees Includes all Equipment Fees. There are
separate Data Records for each unique item
description
FT Funds Transfer Includes all Funds Transfer Fees. There are
Fees separate Data Records for each unique item
description
IC Interchange Includes all pass-through interchange (this
does not include bundled priced fees).
There are separate Data Records for each
qualification category and pricing level.
This subcategory also includes any non-
qualification downgrades (even for
transactions which are priced as bundled)
Note: ChaseNet Fees are reported with this
sub-category code.
MONTH Monthly Fees Includes all monthly Fees. There are
separate Data Records for each unique item
description
247
Sub-Category Code Definitions (continued)
Sub-
Category Sub-Category
Code Name Sub-Category Description
NON Non-Transaction Includes all non-transaction type Fees.
Fees There are separate Data Records for each
unique item description
OTH Other Fees Includes all other fees not otherwise
categorized above. There are separate
Data Records for each unique item
description
PDE Chargeback/ECP Fees related to Chargeback and ECP
Return Fees return processing. There are separate
Data Records for each unique item
description
Sort Order The table above indicates the order in which the Sub-Category values are
For Sub- sorted within the applicable report. Please note that these values are only
Category used for the FIN0011 Service Charge Detail report.
Values
248
Appendix E – Country Codes
Country Code The following table defines the countries indicated by the Consumer Bank
Definitions Country codes used in certain delimited file reports.
Consumer Bank Description

Country Code
AT Austria
BE Belgium
DE Germany
FR France
GB United Kingdom
NL Netherlands
249
Appendix F – NOC Reason Codes
Reason Code The following table defines the possible reasons for an NOC (Notification of
Definitions Change) and the associated Merchant Services-assigned reason code. An
NOC may be sent for one or more attributes of a transaction for which
Merchant Services has updated information on file. The table below
indicates for which attributes new data is being provided for each reason
code. These codes are used by the ACT-0019 Notification of Change report.
Reason Account Account

Code Description RDFI Number Name Type
001 Incorrect DFI (Depository X
Financial Institution) Account #
002 Incorrect Routing # (RDFI) X
003 Incorrect Routing # (RDFI) and X X
Incorrect DFI Account #
004 Incorrect Individual Name X
005 Incorrect Account Type X
006 Incorrect DFI Account # and X X
Incorrect Account Type
007 Incorrect Routing # (RDFI), X X X
Incorrect DFI Account #, and
Incorrect Individual Name
010 Incorrect Routing # (RDFI), X X X
Incorrect Individual Name and
011 Incorrect Individual Name and X X
250
Reason Code Definitions (continued)
Reason Account
Code Description RDFI Number Name Account Type
012 Incorrect Routing # X X X
(RDFI), Incorrect DFI
Account #, and Incorrect
Individual Name
013 Incorrect DFI Account # X X
and Incorrect Individual
Name
014 Incorrect DFI Account #, X X X
Incorrect Individual
Name and Incorrect
Account Type
015 Incorrect Routing # X X X X
(RDFI), Incorrect DFI
Account #, Incorrect
Individual Name and
099 Miscellaneous
C99 Contact Account Holder
Sort Order The NOC reason code does not impact the sort of any report file.
For NOC
Reason
Codes
251
Appendix G – Cross Currency Processing
Cross Merchants who participate in Merchant Services’ Cross-Currency product

Currency receive files that are structurally different from other merchants’ files. Cross
Processing Currency processing creates the need for additional currency and amount
Impacts DFR fields to qualify data at a more granular level than is otherwise necessary. A
Data Record merchant who is processing cross-currency transactions sees multiple
Formats transaction currencies and/or amounts on many reports.
Reporting for Cross-Currency processing has significant impact on DFR. In

order to maintain the structural integrity of the DFR files, these additional
fields impact ALL data rows for a merchant processing Cross-Currency
transactions, even data rows for like-to-like currency transactions or
divisions.
A merchant selecting to display Cross Currency field at company level (CO)

always sees those fields, which would otherwise be suppressed regardless
of participation in cross currency.
Similarly, a merchant selecting to display Cross Currency field at the entity

level (BU, TD, RG, or FTI) always sees those fields, which would otherwise
be suppressed regardless of participation in cross currency.
For merchants who do not process Cross-Currency transactions, the data

record format is unaltered and the additional fields are suppressed.
If a merchant is using DFR reports and later adds the cross currency
product, the following reports have additional fields in subsequent files:
Deposit Activity Summary (FIN0010)

Deposit Activity Transfer Summary (FIN0010T)
Transaction Summary (LNK010A)
Reject Summary (ACT0033)
Submission Summary (ACT0012)
Service Charge Detail (FIN0011)
Deposit Detail (ACT0010)
Chargeback Activity (PDE0017)
Chargebacks Received (PDE0020)
Please refer to individual report specification for more information.
252
253
Uniformity In In order to maintain the structural integrity of the DFR files, these additional
Report fields impact ALL data rows for a merchant processing Cross Currency
Structure transactions, even data rows for like-to-like currency transactions or
divisions. For merchants who do not process Cross Currency transactions,
the data record format is unaltered and the additional data fields are
suppressed, including the delimiter character.
Terms And These report specifications contain an indication for every amount and currency field
Definitions as to whether it represents the “presentment currency” or the “settlement currency”.
The definitions for these terms are:
Term Description
Presentment The currency in which a cardholder’s transaction
Currency is assessed by the merchant and presented to
Merchant Services. Presentment currencies
apply to sale, refund, chargeback and
authorization transaction face values.
Settlement The currency in which a merchant is paid. For
Currency non-Cross Currency processing, the presentment
and settlement currencies are the same. All fees
are assessed in settlement currency and do not
have an associated presentment currency value.
Foreign The rate of conversion that was used by Merchant
Exchange Services to convert the presentment currency
Rate value into the settlement currency value.
254
Appendix H – Action Codes
Action Code The following charts provide the Action Codes for 96-byte transactions and
Definitions for 120-byte and Online transactions
96-Byte Action Codes

A – Authorize (Credit Card, Gift Card, Bill Me Later)
B – Conditional Deposit (Credit Card, Bill Me Later)
D – Deposit (Credit Card, Gift Card, Bill Me Later)
E – Authorization Reversal (Gift Card)
F – Account Verification (Mastercard, Visa)
Note: Dollar amount must be $0.00
G – Validate (formerly Validate and Verify) (ECP U.S.) (dollar
amount should be $0.00)
H – Validate and Deposit (ECP U.S. and CAN)
I – Validate and Deposit (formerly Validate, Verify, and Deposit)
(ECP U.S.)
Note: If validation fails, the transaction does not verify or
deposit
J – Pre-note Only - Credit (ECP U.S.)
K – Issuance (Gift Card)
L – Add Value (Gift Card)
N – Refund (ECP U.S. and CAN)
O – Forced Validate (ECP CAN only)
P – Pre-note Only - Debit (ECP U.S. only) (dollar amount should
be $0.00)
Q – Current Balance Inquiry (Gift Card)
R – Refund (Credit Card, Gift Card, Bill Me Later)
U – Account Updater (MOPs = VI, MC, EN only)
V – Validate Only (ECP U.S. and CAN) (dollar amount should be
$0.00)
Y – Validate and Pre-note – Debit (formerly Validate, Verify, and
Pre-Note) (ECP) (dollar amount should be $0.00)
255
120-Byte and Online Action Codes
AR – Authorization Reversal (Discover, Gift Card, Mastercard, PayPal, Visa)
AU – Authorize (Bill Me Later, Bill Me Later Private Label, Credit Card, Gift Card,
PayPal)
BI – Current Balance Inquiry (Discover, Gift Card, Mastercard, MoneyPak,
Visa)
Note: Amount should be $0.00.
DC – Conditional Deposit (Bill Me Later, Bill Me Later Private Label, Credit Card,
PINless Debit)
DO – Validate and Deposit (ECP U.S. and CAN, European Direct Debit)
DP – Deposit (Bill Me Later, Bill Me Later Private Label, Credit Card, Debit, Gift
Card, , MoneyPak)
DR Refund Authorization Reversal (PINless Debit)
Note: This is an authorization action.
ER – Refund (ECP U.S. and CAN, European Direct Debit)
LO – Validate Only (ECP and European Direct Debit)
Note: Amount must be $0.00 for European Direct Debit
NC – Pre-note Only – Credit (ECP U.S)
ND – Pre-note Only – Debit (ECP U.S.)
OD – Forced Validate and Deposit (ECP CAN)
PA – Purchase Auth (MoneyPak, PINless Debit)
PR – Purchase Auth Reversal (PINless Debit).
RA Refund Auth (MoneyPak, PINless Debit)
Note: This is an authorization action.
RD – Alternative Payments Refund (PayPal)
RF – Refund (Bill Me Later, Bill Me Later Private Label, Credit Card, Debit, Gift
Card, MoneyPak)
RG – Alternative Payments Sale (PayPal)
SA – Add Value (Gift Card)
SI – Issuance Activation (Gift Card)
UP – Account Updater (Encryption, Mastercard, Visa)
VD – Validate and Deposit (formerly Validate, Verify, and Deposit) (ECP U.S.)
Note: If validation fails, the transaction does not verify or deposit
VF – Account Verification (Mastercard, Visa)
Note: Amount must be $0.00
VO – Validate Only (formerly Validate and Verify) (ECP U.S.
Note: Amount should be $0.00
VP – Verify and Pre-note (formerly Validate, Verify, and Pre-note) (ECP U.S.)
For the most currently listing of Action Codes please refer to our Technical Processing Format
Specifications.
256
Appendix I – Encryption and Compression
Introduction The use of Open PGP provides support for all available protocols for
compression and encryption of data. It is a widely accepted flexible tool that
allows for any combination of functionality required: i.e. compression only,
encryption only, or compression and encryption.
This encryption and compression selection is not applicable to NetConnect

Batch as compression and encryption are handled within the NetConnect
Batch Product.
Encryption and/or compression of any file is performed at the file level, not at
the record level.
Merchants must provide a key to Merchant Services to be used in the

creation of the DFR files.
Merchant Public Keys:
 Key must be generated and sent to their Merchant Services technical

representative as an attachment via email. The key should be named
with suffix “.asc” for ASCII Armor.
 Company Name and PID number must be in the comments field of
the generated key.
 There must be one key per PID.
 The same key must be used for production DFR files retrieved from
both test and production environments.
 There is no mandate from Merchant Services for the keys to expire.
However, if the merchant chooses to have the key expire, they must
give their Merchant Services business representative 30 days
advance notice.
Merchant Services Generated Files:
Merchant Services uses ASCII Armor to encrypt files. Please see the chart
below for the file extensions that are used for each delivery option.
Delivery Option File Extension

Compression Only .gpg
Encryption Only .gpg
Both .gpg
257
Appendix J – Availability
Introduction DFRs are generated in batch mode exclusively and cannot be run on
demand. Once generated, flat-files are hosted on Merchant Services servers
and available on NetConnect servers for 72 hours or NetConnect Batch
servers for 30 days.
Daily Reports (generated 365 days per year): Report generation begins
after the merchant’s Merchant Services processing day ends. Typically
reports are generated and transferred to Merchant Services servers prior to 9
AM ET of the next processing day.
Weekly Reports (generated 52 weeks per year): Report generation begins

on Friday after the merchant’s Merchant Services processing day ends,
Typically reports are available on Merchant Services servers within 24 hours.
Monthly Reports (generated 12 months per year): Report generation

begins on the last day of the month (calendar or fiscal) after the merchant’s
Merchant Services processing day ends. Typically reports are loaded on
Merchant Services servers within 48 hours.
258
Appendix K – Data Field Numbering
Introduction As a result of selecting report specific options, additional data fields (data
and delimiter) are appended to standard report data records. The approach
used to identify the sequence in which optional data fields are appended is
outlined below.
Sequence 1 Standard Data Record (Data Field Numbers 1 to x)

Sequence 2 Option Name 1 - Data Records (x Data Fields)
Sequence 3 Option Name 2 - Data Records (x Data Fields)
Sequence 1 is always present as it represents the data record for the

standard report.
Subsequent sequences (Sequence 2, Sequence 3, Sequence 4, etc.) are

optional and are appended to the report data record only if the merchant
elects to receive it, Any combination of optional sequences can be selected
unless otherwise noted.
Field numbering of data fields associated with selected optional data records
begins at the next available (left most) position and increments by one until
the last field is appended. The last data field in the record does not have a
trailing delimiter.
Example: ACT0002 with IBAN Option
Standard ACT0002 Data Record + IBAN Detail Data Record

Field Numbers 1 to 25 + Field Numbers 26 to 32
Appendix L – Card Usage Type
Card Usage The following table lists the one-character Card Usage Type codes used in
Code delimited file reports.
Definitions
Card Usage Type Description

1 Credit Card
2 Debit Card
3 Check Card
4 Check II Card
5 Pre-Paid Card
6 Charge Card
7 European Deferred Debit Card
259
260
Appendix M – Card Product Type
Card Product The following table lists the one-character Card Product Type codes
Code used in delimited file reports.
definitions
Card Product Type Description

1 Consumer
2 Business
3 Purchasing
4 GSA Purchasing
5 Fleet
6 Corporate T & E
7 World T & E
8 Signature
9 Visa Commerce
A Infinite Card Type
B MC Electronic Corp
C Visa Electron
D Visa Rewards
E MC Electronic Consumer
F MC Auth Only (MAV)
G VPAY
H Card Level Result
I Visa Large Ticket Purchasing Card
J Visa Signature Business
K GSA Fleet
L MC World Elite
M Discover Commercial (not Consumer or Stored Value)
N Prepaid/Stored Value
O MC Enhanced
P MC Business World
261
Appendix M – Card Product Type
Card Product Type Description

Q MC Business World Elite
R MC Corporate World
S MC Corporate World Elite
T Visa Signature Preferred
U Mastercard 'New World' Card
V Mastercard Canadian Purchasing
W Discover Premium
X Mastercard Electronic Payment
Y Discover Core Credit
Z Mastercard High Value
a Mastercard or Visa Business Enhanced
b Mastercard Interregional Consumer Premium
c Mastercard Interregional Commercial Premium
d Mastercard European Immediate Debit
e Visa Fleet and Large-Ticket
f Discover Premium Plus
g Visa Gold Card
h Visa Platinum Card
i Visa Distribution
j Visa Large Purchase Advantage
262
Appendix N – Accountholder Authorization
Method
Accountholder The following table expands upon the values in the Accountholder
Authorization Authorization Method field of the ECP Returns (PDE0018) report
Methods
ACCOUNTHOLDER ABBR. DESCRIPTION

AUTHORIZATION
METHOD
A ARC 'Accounts Receivable Conversion' supports the conversion of
checks received via U.S. mail into a merchant’s unattended
lockbox
I WEB Accept e-Check payments from customers via the WEB or
wireless device
P POP 'Point of Purchase Conversion' supports single entry debits
used at the point of purchase
T TEL Accept e-Check payments from customers via the Call Center
W PPD 'Single and Recurring Payments' supports a merchant’s
recurring billing program
263
Appendix O – Fraud Type Codes Abbreviations
CODE DESCRIPTION
00 Lost Fraud—A fraudulent transaction that occurs with the use of a lost credit or debit
card (or other device accessing a credit or debit card account—for example,
convenience and balance transfer checks) without the actual, implied, or apparent
authority of the cardholder.
01 Stolen Fraud—A fraudulent transaction that occurs with the use of a stolen credit or
debit card (or other device accessing a credit or debit card account—for example,
convenience and balance transfer checks) without the actual, implied, or apparent
authority of the cardholder.
02 Never Received Issue—The interception and use of a credit or debit card (or other
device accessing credit or debit card account—for example, convenience and
balance transfer checks) before receipt by the cardholder by a person without the
actual, implied, or apparent authority of the cardholder.
03 Fraudulent Application—A fraudulent transaction that occurs with the use of a credit
or debit card that was obtained with an application using a false name or other false
identification information.
04 Counterfeit Card Fraud—The use of altered or illegally reproduced credit or debit
card (or other physical device accessing a credit or debit card account—for example,
convenience and balance transfer checks) including the replication or alteration of the
magnetic stripe or embossing.
05 Account Takeover Fraud—An existing credit or debit account is used without the
actual, implied, or apparent authority of the cardholder, by a person who gains access
to and use of the account through an unauthorized means, such as a change of
address or request for re-issuance of credit or debit cards (or other device for
accessing a credit or debit account—for example, convenience and balance transfer
checks) but not lost or stolen cards.
06 Card Not Present Fraud—A fraudulent transaction that occurs with the use of credit
or debit account information including pseudo-account information without the
physical card or other device being involved, via the phone, mail, Internet, or other
electronic means without the actual, implied, or apparent authority of the cardholder.
07 Multiple Imprint Fraud—A fraudulent transaction that occurs with a credit or debit
card where the merchant, having completed a legitimate face-to-face transaction,
deposits one or more additional transactions without the actual, implied, or apparent
authority of the cardholder. For example, the merchant makes several imprints of a
card on paper form sets or produces terminal receipts upon receiving additional
online or offline card-read authorization approvals.
51 Bust-out Collusive Merchant—A collusive cardholder engaging in transactions with
a collusive merchant as defined in the Cardholder-Merchant Collusion Program.
264
Appendix P – POS Entry Mode Codes
Abbreviations
CODE DESCRIPTION
00 Terminal not used
01 Key-entered
02 Magnetic stripe reader
03 Barcode reader
04 OCR reader
05 Integrated circuit chip product
06 Track 1 read
07 Proximity payment using VSDC chip data rules
90 Complete magnetic stripe read and transmitted
91 Proximity payment using magnetic stripe data rules
95 Integrated circuit card read—CVV data unreliable
N not provided in original transaction
265
Appendix Q – PDE0017 and PDE0020 Sample Data Record
*DFRBEG,PID=123456,FREQ=DAILY,CO=111111
HPDE0017,543210,07/12/2005,07/12/2005,07/13/2005,14:15:01
RPDE0017S,TD,123456,,,USD,CC,OPAREQ,NON,55,38009.92,USD
RPDE0017S,TD,123456,,,USD,CC,RECD,FIN,10,1215.90,USD
RPDE0017D,TD,234567,8.90,N,USD,RECD,,297332290,”36H592”,4444444442881111,10.4,04/13/2018,05/11/2018,05/11/2018,8.90,
,9,VI,03/01/2018,05/29/2018,123456789012345,Y,1
RPDE0017D,TD,234567,78.45,N,USD,RECD,,387231272,”21F551”,3333123542881234,12.6.2,04/13/2018,05/15/2018,05/15/2018,78
.45,,9,VI,03/12/2018,06/02/2018,123456789012345,,0
HPDE0020,543210,07/12/2005,07/12/2005,07/13/2005,14:15:01
RPDE0020,TD,234567,,,USD,RECD,R,29733200,”38Q92”,4444444442881111,10.4,04/13/2018,05/11/2018,05/11/2018,-
9.90,9,Y,1234567890ABCDE,Y,1
RPDE0020,TD,234567,,,USD,RECD,,29731234,”377F19”,3333123542881234,12.6.1,04/25/2018,05/122/2018,05/22/2018,-
59.32,9,Y,1234567890ABCDE,,0
*DFREND, PID=123456,FREQ=DAILY,CO=111111
Note: The sample data records above are for Visa disputes only.
266

SPC Delimited File Reports v7.1.0.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SPC Delimited File Reports v7.1.0.0

Uploaded by

Copyright:

Available Formats

D ELIMITED F ILE R EPORTS

File Format Specification

 Added field number 5, the Average Ticket Amount field.

 Added field number 13, the Debit Type field.

 Updated the sample record.

 Updated the maximum length of the Average Ticket Amount field.

Delimited files provide summary or detail information about the activity

To sign up for Delimited File Reporting or to modify an existing DFR setup,

This This document provides specifications for every report available in a

There are four delivery methods to choose from:

See Appendix I - Encryption and Compression, for more information.

Continued on next page

An additional EOFEOFEOF record needs to follow the RFR record for

RFR is not required if processing via SFTP or NDM.

Continued on next page

The PID is a number assigned to the

Continued on next page

RFR is a separate record sent to Merchant Services. It should not be sent as

This record is not needed for SFTP or NDM file processing.

Each record definition is preceded by an example. The report data record

Note: Fields such as date (MM/DD/YYYY) or time (HH:MM:SS) that contain

The comments column gives the values of constants or a short description of

Continued on next page

The three reports types are:

Sample File Name

Continued on next page

For example: A123 or B456 or

Zero decimal currencies do not include decimal points or decimal places.

Entity reports provide a way of excluding entities that would otherwise be

File Header Record

Continued on next page

File Header Record

File Header Record

File Header Record

File Header Record

File Header Record

File Header Record

Sample File Header

Field Maximum Data

Note: Field length includes preceding

Note: Field length includes preceding

Continued on next page

Field Maximum Data

Entity level value is followed by an

Financial Reports – Deposit Activity Summary

Continued on next page

Field Maximum Data Field Name Comments

Continued on next page

Sample Data Record

Sample Data Record - Cross Currency

Field Maximum Data

Merchant Services assigned

Note: A blank value in this field

Continued on next page

Field Maximum Data

Note: A blank value in this field indicates

See Appendix A for values

See Appendix B for values

Note: This field is blank for Data Records

See Appendix C for more information.

Continued on next page

Field Maximum Data

See “Numeric formatting” for more