Presentments
Introduction
The Presentments Report provides detailed data on clearing records, including matched transactions and their originating authorizations. It is designed to support reconciliation, reporting, and operational analysis by offering both standardized and scheme-specific information.
This document outlines how to interpret and consume the Presentments Report effectively. It is organized into the following key sections:
- Report File Conventions Describes how the report files are named, formatted, and delivered, ensuring clients can reliably identify and retrieve the correct files each day.
- Best Practices for Using Presentment Reports Offers guidance on safely consuming the reports, including recommendations for parsing logic and tips for handling data variations (e.g., field ordering, blank values).
- Report Specifications
Details the structure of the report itself, covering two main categories of fields:
- Paymentology-Specific Fields: Custom fields added by Paymentology to support enhanced reconciliation, tracking, and cross-report alignment. These fields are consistent across all card schemes.
- Card Scheme-Specific Fields: Native fields provided by schemes such as Mastercard, Visa, and Mada. These fields reflect the unique data elements of each scheme.
Use this documentation as a reference for both integrating and troubleshooting the Presentments Report.
Report File Conventions
Filename Convention
Each report file follows a consistent naming pattern to help clients easily identify the report type and coverage period. The filenames include key elements such as the client identifier and the date or date range the report covers. The structure is as follows:
| Part | Description |
|---|---|
<ClientName> | Name or short code identifying the client |
Presentments | Fixed keyword identifying the type of report. |
<YYYYMMDD> | Calendar date in 4-digit year, 2-digit month, and 2-digit day format (e.g., 20250710) |
to_<YYYYMMDD> | (Optional) Used when the report covers a date range |
.csv | File extension indicating it is a CSV (comma-separated values) file. |
Examples
ABCBank_Presentments_20250710.csv → Report for 10th July 2025
ABCBank_Presentments_20250701_to_20250710.csv → Report covering 1st to 10th July 2025
Report Delivery Details
| Attribute | Description |
|---|---|
| Frequency | Daily |
| Delivery Time | Typically available before the end of day (configurable) |
| Delivery Method | Delivered via SFTP |
| File Location | Stored in the client-specific folder on the SFTP server |
| File Format | CSV (comma-separated values) |
Data Format Conventions
This section defines the format conventions used across all field definitions in this document.
Format | Description | Examples |
|---|---|---|
Numeric | Digits only, no decimals or separators |
|
Decimal | Number with a decimal place |
|
Alphabetic | Letters only |
|
Alphanumeric | Letters and digits only |
|
String | Free text; digits, spaces and symbols |
|
DateTime | A timestamp value that may represent a date, time, or a full date-time combination. The exact expected pattern for each field will be specified in its description. | Pattern:
|
Note: All data in the CSV file is stored as text, and therefore every field is enclosed in double quotes for consistency. The formats described here indicate the expected pattern or type of each field’s value, even though the underlying representation is textual.
since all data is enclosed in double quotes, any data within a field that contains a double quote will be escaped with an additional double quote. e.g. the value of Lidosta "Riga" will be presented in the CSV file as “x","y","Lidosta ""Riga""","z",.... Note the two double quotes around the “Riga”.
Best Practices for Using Presentment Reports
To ensure your integration with the Presentments report remains stable and maintainable over time, we recommend following these best practices:
- Avoid relying on field positions (column order) Always identify fields by their header names rather than assuming a fixed position in the CSV. Field positions may change over time as new fields are added or deprecated.
- Use the header row as the source of truth The first row in the report contains all field names. Your processing logic should dynamically map fields based on these headers.
- Account for optional or conditional fields Some fields (e.g., scheme-specific or provisional fields) may only be present in specific reports or under certain conditions. Your logic should handle missing columns gracefully.
- Validate data formats Refer to the Data Format Conventions section to ensure correct parsing (e.g., DateTime format, decimal precision).
- Use field mappings for cross-report linking
Fields like
PY__Transaction_ID,PY__Token, andPY__RID_Authorizationcan be used to cross-reference records across multiple report types.
Report Specifications
Paymentology-Specific Data Fields
The table below specifies the general data included in a presentment report and can be used to help you interpret the data in the report:
Report Field | Explanation |
|---|---|
PY__RID_Settlement Unique ID for settlement transaction | Format: Numeric Example: |
PY__RID_Authorization Unique ID for authorisation transaction Note: This may have value 0 if no Authorisation involved in the transaction | Format: Numeric Example: |
PY__Account_ID Account identifier | Format: Numeric Example: |
PY__Account_Currency Numeric currency code of the account that performed the transaction Note: This field is only applicable for Visa Presentments report. | Format: Numeric Example: |
PY__Token Public token generated by Paymentology to replace PAN | Format: Numeric Example: |
PY__Account_External_Reference Account external reference assigned by Paymentology | Format: Numeric Example: |
PY__File_ID Unique file ID assigned by Paymentology | Format: Numeric Example: |
PY__Transaction_ID Unique transaction thread identifier generated and managed by Paymentology. | Format: Numeric Example:
|
PY__Network Indicates the card network provider | Format: Alphabetic Possible Values:
Example: |
PY__MTID Message Transaction Identifier Note: This field is not applicable for Visa Presentments report. | Format: Numeric Example: |
PY__Created_Date Indicates the timestamp when Paymentology processed the file. | Format: DateTime Pattern: Example:
|
PY__Matched_Status Indicates the matching step when matching the authorisation and the clearing record. Provisional field, reserved for future use Note: If a value of 0 is present please raise a ticket on our Customer Support Platform | Format: Numeric Possible Values:
Example: |
PY__Is_Debit This field determines the direction of funds flow of the original transaction. Settlement Reversal will still hold the value of the original settlement. Note: This field is not applicable for Visa Presentments report. | Format: Numeric Possible Values:
Example: |
PY__Product_ID Paymentology card product identifier | Format: Numeric Example: |
PY__Product_Name Paymentology card product name | Format: String Example: |
PY__Settlement_Note Position for Paymentology to assign notes that may be of relevance to the client, relating to the presentment. Provisional field, reserved for future use | Format: String Examples:
|
PY__Transaction_Type Identifies the additional transaction type | Format: Alphabetic Possible Values:
Example: |
Alignment to FAST and other reports
Field | FAST | Report | Usage |
|---|---|---|---|
PY__RID_Authorization |
|
| Match transaction message records |
PY__Token |
|
| Token matching across reports and messages |
PY__Transaction_ID |
|
| Match transaction threads |
PY__RID_Settlement |
|
| Settlement reference matching |
Jaywan
This section outlines the structure of the Presentment Report for Jaywan
Report Field | Explanation |
|---|---|
Cardholder_Transaction_Type Identifies the transaction type | Format: Numeric Example: |
Cardholder_from_Account_Type_Code Cardholder ‘from’ Account type | Format: Numeric Example: |
Cardholder_To_Account_Type_Code Cardholder ‘to’ Account type | Format: Numeric Example: |
Transaction_Amount It carries the amount in the transaction currency. | Format: Decimal Example: |
Billing_Amount It carries the cardholder billing amount in the cardholder billing currency. Applicable for cross currency transactions | Format: Numeric Example: |
Conversion_Rate_Billing It carries the conversion rate of billing Amount. Applicable for cross currency transactions | Format: Numeric Example: |
Transaction_Date_Time This element contains the actual date and time at which the transaction takes place at the card acceptor location | Format: DateTime Pattern: Example: |
POS_Entry_Mode This element is used to indicate the method used to enter the account number. | Format: Numeric Example:
|
Function_Code This element indicates the purpose of the different types of clearing messages. | Format: Numeric Possible Values:
Example: |
Acquiring_Institution_ID_Code This element identifies the transaction acquirer. For clearing transactions, it identifies the financial institution that owns the merchant agreement. This code is allotted by Network. | Format: Numeric Example: |
Retrieval_Reference_Number It is used to identify and track all messages related to a given cardholder transaction. | Format: Numeric Example:
|
Approval_Code This element contains the code allotted to an authorized transaction by an issuer/authorizing entity. | Format: Alphanumeric Example: |
Card_Acceptor_Terminal_ID This element depicts the unique code assigned to a terminal at the card Acceptor location and is unique in an acquiring system. | Format: Alphanumeric Example: |
Card_Acceptor_ID_Code This element uniquely identifies the card acceptor id in an acquiring system. | Format: Numeric Example: |
Card_Acceptor_Name The field carries the card acceptor name. | Format: Alphanumeric Example: |
Card_Acceptor_City The city of the card acceptor. | Format: Alphanumeric Examples:
|
Card_Acceptor_State_Code The data element will carry the state code of the card acceptor. | Format: Alphabetic Example: |
Card_Acceptor_Country_Code The country code of the card acceptor. Country code should be ISO standard. | Format: Alphabetic Example: |
Message_Reversal_Indicator Identifies whether it is the original message or the reversal of the original message. | Format: Numeric Possible Values:
Example: |
Network_File_Reference This field will carry the unique file name. | Format: Numeric Example: |
Reconciliation_Date This field contains the date on which the transaction is processed for clearing. | Format: DateTime Pattern: Example: |
Currency_Code_Transaction This element defines the currency code of the transaction | Format: Numeric Example: |
Currency_Code_Billing This element defines the currency code of the amount carried in Amount, Cardholder Billing. | Format: Numeric Example: |
Message_Number Identifies the record number for a record in a file. This record could be pertaining to financial/ non-financial transactions. | Format: Numeric Example: |
Transaction_Destination_Institution_ID It carries the identification of transaction destination institution. | Format: Numeric Example: |
Transaction_Originator_Institution_ID It carries the identification of transaction originator institution. | Format: Numeric Example: |
Sample report file
Link to Jaywan Sample Presentment Report
Mastercard
This section outlines the structure of the Presentment Report for Mastercard. Two versions are currently supported: v1.0 and v2.0. If your setup includes Mastercard processing, please verify which version of the report you are receiving.
NoteAll new clients should integrate with the latest report version
Mastercard v1.0
ImportantThis report version (Mastercard v1.0) will be discontinued by 1st November 2025.
You can refer to our Migration guidelines for helpful information on how you can upgrade from v1.0 to v2.0.
Official communication was sent to you around 1st November 2024.
Below are the data fields and format of the Mastercard v1.0 Presentments report.
Click to view the complete list of fields
Report Field | Explanation |
|---|---|
PY__RID_Settlement PY__RID_Authorization PY__Account_ID PY__Token PY__Account_External_Reference PY__File_ID PY__Transaction_ID PY__Network PY__MTID PY__Created_Date PY__Matched_Status PY__Is_Debit PY__Product_ID PY__Product_Name PY__Settlement_Note | (Refer to the section Paymentology-Specific Data Fields) |
DE3_1__Cardholder_Transaction_Type Processing Code, describes the effect of a transaction on a customer account and the type of accounts affected.Position 1-2 = Cardholder transaction type (numeric) | Format: Numeric Example: |
DE3_2__Cardholder_from_Account_Type_Code Position 3-4 = Cardholder ‘from’ Account type | Format: Numeric Example: |
DE3_3__Cardholder_To_Account_Type_Code Position 5-6 = Cardholder ‘to’ Account type | Format: Numeric Example: |
DE4__Transaction_Amount Local amount with the sign, indicating the net direction of funds flow. Currency provided in DE49 | Format: Decimal Example: |
DE5__Reconciliation_Amount Settlement amount with the sign, indicating the net direction of funds flow. Currency provided in DE50 | Format: Decimal Example: |
DE6__Billing_Amount Cardholder Billing amount with the sign, indicating the net direction of funds flow. Currency provided in DE51 | Format: Decimal Example: |
DE9__Conversion_Rate_Reconciliation Conversion rate to Reconciliation/Settlement currency | Format: Decimal Example: |
DE10__Conversion_Rate_Billing Conversion rate to Cardholder billing currency | Format: Decimal Example: |
DE12__Transaction_Date_Time Date/time of local original spend. Note: Mastercard frequently provide 00:00:00 as time element. | Format: DateTime Pattern: Example: |
DE22_6__Card_Present_Data Indicates if the card is present at the point of service | Format: Numeric Possible Values: Example: |
DE22_7__Card_Data_Input_Mode Indicates the method used for PAN entry to initiate a transaction | Format: Alphanumeric Possible Values: Example: |
DE23__Card_Sequence_Number Distinguishes among separate cards that have the same PAN | Format: Numeric Example: |
DE24__Function_Code Indicates the specific purpose for a message | Format: Numeric Example: |
DE25__Message_Reason_Code Provides the message receiver with the reason for sending the message | Format: Numeric Example: |
DE26__Merchant_Category_Code Classifies the type of business applicable to the acceptor | Format: Numeric Example: |
DE30_1__Original_Amount_Transaction Contains the “amount” data element values from the First Presentment or Fee Collection (DE4). Used for chargeback or retrieval request. | Format: Numeric Example: |
DE30_2__Original_Amount_Reconciliation DE 30 (Amounts, reconciliation) Note: Mastercard populate this with all zeros which in turn is displayed as 0 | Format: Numeric Example: |
DE31__Acquirer_Reference_Data Acquirer Reference Data | Format: Numeric Example: |
DE32__Acquiring_Institution_ID_Code Identifies the transaction acquirer | Format: Numeric Example: |
DE33__Forwarding_Institution_ID_Code Identifies a message’s forwarding institution | Format: Numeric Example: |
DE37__Retrieval_Reference_Number It is a transaction information document reference number the acceptor’s or designated agent’s system supplies. | Format: Numeric Example: |
DE38__Approval_Code It is a code the authorizing institution assigns indicating approval | Format: Numeric Example: |
DE40__Service_Code Service Code | Format: Numeric Example: |
DE41__Card_Acceptor_Terminal_ID Card Acceptor Terminal Identification | Format: Numeric Example: |
DE42__Card_Acceptor_ID_Code Card Acceptor ID Code | Format: Numeric Example: |
DE43_1__Card_Acceptor_Name Card Acceptor Name (22 long) | Format: Alphanumeric Example: |
DE43_2__Card_Acceptor_Street_Address Card Acceptor Street address (48 long) | Format: Alphanumeric Example: |
DE43_3__Card_Acceptor_City Card Acceptor City (13 long) | Format: Alphabetic Example: |
DE43_4__Card_Acceptor_Zip_Code Post/zip code (10 long) | Format: Alphanumeric Example: |
DE43_5__Card_Acceptor_State_Code State or province (3 long) | Format: Alphabetic Example: |
DE43_6__Card_Acceptor_Country_Code Country Code (3 long) | Format: Alphabetic Example: |
DE48_0002__GCMS_Product_Identifier GCMS Product Identifier | Format: Alphabetic Example: |
DE48_0003__Licensed_Product_Identifier Licensed Product Identifier | Format: Alphabetic Example: |
DE48_0023__Terminal_Type Terminal Type, identifies the type of terminal used at the point of interaction | Format: Alphabetic Example: |
DE48_0025_1__Message_Reversal_Indicator Identifies whether it is the original message or the reversal of the original message. | Format: Numeric Possible Values: Example: |
DE48_0105__Network_File_Reference File ID from the network | Format: Numeric Example: |
DE48_0158_1__Card_Program_Identifier Identifies the card program or financial network to which a transaction belongs | Format: Alphabetic Example: |
DE48_0158_2__Business_Service_Arrangement_Type_Code Identifies the business relationship between the transaction’s participants. | Format: Numeric Possible Values: Example: |
DE48_0158_3__Business_Service_ID_Code Identifies the business service to which the transaction is assigned for reconciliation and rules basis | Format: Numeric Example: |
DE48_0158_4__Interchange_Rate_Designaor Indicates the interchange rate and editing rules applied to the transaction | Format: Numeric Example: |
DE48_0158_5__Central_Site_Business_Date Identifies the official business processing date when the business service reconciles a transaction | Format: DateTime Example: |
DE48_0158_6__Business_Cycle Identifies a reconciliation period in a Business Date | Format: Numeric Example: |
DE48_0158_7__Card_Acceptor_Classification_Override_Indicator Indicate whether Card Acceptor Business Code (MCC) override rates, Card Acceptor Business (CAB) Type override rates, or neither, were used in the interchange fee amount designated in PDS 0146 (Amount, Transaction Fees) | Format: Alphanumeric (can be blank or contain whitespace) Possible Values: (Refer to the Mastercard IPM Clearing Specifications for full list of supported values)Example: |
DE48_0158_8__Product_Class_Override_Indicator Indicate whether product class override interchange rates were used in the interchange fee amount designated in PDS 0146 (Amount, Transaction Fees) | Format: Alphabetic (can be blank or whitespace) Possible Values: (Refer to the Mastercard IPM Clearing Specifications for full list of supported values)Example: |
DE48_0158_9__Corporate_Incentive_Rates_Apply_Indicator It indicates if corporate incentive rates were used in the interchange fee amount designated in PDS 0146 (Amounts, Transaction Fee) | Format: Alphanumeric Possible Values: Example: |
DE48_0158_10__Special_Conditions_Indicator Indicate whether an adjustment was included in the Fee amount | Format: Alphanumeric Possible Values: Example: |
DE48_0158_11__MC_Assigned_ID_Override_Indicator Indicates whether override rates were used in the interchange fee amount designated in PDS 0146 (Amount, Transaction Fees) | Format: Alphabetic Possible Values: Example: |
DE48_0158_12__Account_Level_Management_Account_Category_Code Account Level Management Account Category Code, indicates whether the account associated with the transaction (stored on DE 2 is participating in one or several Account Level Management programs where an incremental interchange is included in the transaction’s interchange amount. N = default | Format: Alphabetic Possible Values: Example: |
DE48_0158_13__Rate_Indicator Indicates the rate applied by GCMS to the transaction | Format: Alphabetic Possible Values: Example: |
DE48_0158_14__Masterpass_Incentive_Indicator Identifies the transaction as having received the Masterpass-Enabled Merchant Incentive. | Format: Alphabetic Possible Values: Example: |
DE48_159_3__Settlement_Service_Level_Code It is a one-digit code that identifies the settlement level of the settlement service | Format: Numeric Possible Values: Example: |
DE48_159_6__Reconciliation_Date Identifies the clearing system’s processing date expressed in the local time zone of the clearing system’s processing center | Format: DateTime Example: |
DE48_159_7__Reconciliation_Cycle Identifies a reconciliation period in a reconciliation date. | Format: Numeric Possible Values: Example: |
DE48_159_8__Settlement_Date Identifies the date that the settlement service initiates settlement for the message, such as the settlement advisement date, which is based on the clearing date, settlement service cutoff cycle, and calendar for the settlement service. | Format: DateTime Example: |
DE48_159_9__Settlement_Cycle Identifies a settlement period in a settlement date | Format: Numeric Possible Values: Example: |
DE48_0177_1__Cross_Border_Indicator Identifies whether the transaction qualified as a Crossborder transaction and could be subject to Cross-border transaction pricing guidelines. | Format: Alphabetic Possible Values: Example: |
DE48_0177_2__Currency_Indicator Identifies whether the transaction was submitted to Mastercard in the local currency of the merchant. | Format: Alphabetic Possible Values: Example: |
DE49__Currency_Code_Transaction Currency of transaction (local currency) | Format: Numeric Example: |
DE50__Currency_Code_Reconciliation Currency of reconciliation/Settlement | Format: Numeric Example: |
DE51__Currency_Code_Billing Currency of Cardholder Billing | Format: Numeric Example: |
DE54_2__Additional_Amount_Type Other Amounts – e.g. cashback portions in cash back transactions. Surcharges also appear here | Format: Numeric Example: |
DE54_3__Additional_Amount_Currency_Code Indicates currency of the Surcharge amount | Format: Numeric Example: |
DE54_4__Additional_Amount_Sign Additional Amount Sign (D for debit and C for Credit) | Format: Alphabetic Example: |
DE54_5__Additional_Amount Other Amounts – e.g. cashback portions in cash back transactions. Surcharges also appear here. DE54_5 is amount, DE54_4 is amount sign | Format: Numeric Example: |
DE63__Transaction_Life_Cycle_ID Transaction Life Cycle ID | Format: Alphanumeric Example: |
DE71__Message_Number Message Number – identifies the message within the T112 Mastercard file | Format: Numeric Example: |
DE72__Data_Record Used in Fee type messages to provide description of the fee | Format: String Example: |
DE73__Action_Date In Fee Collection messages, this data element identifies a reference date related to the Fee. | Format: DateTime Example: |
DE94__Transaction_Originator_Institution_ID Transaction Originator Institution ID, identifies the transaction originator institution | Format: Numeric
|
DE100__Receiving_Institution_ID Receiving Member ID (Paymentology processor id) | Format: Numeric
|
DE111__Amount_Currency_Conversion_Assessment The amount based on the result of Applying the multi-currency conversion rate (Currency Conversion Assessment) adjustment to the currency conversion rate used to convert DE 4 (Amount, Transaction) to DE 6 (Amount, Cardholder Billing) for qualified transactions. | Format: Numeric Example: |
Sample report file
Link to the MC v1.0 Sample Presentment report
Mastercard v2.0
Key changesBelow are the notable differences between v1.0 and v2.0:
- Addition of a new field
PY__Transaction_Type
Below are the data fields and format of the Mastercard v2.0 Presentment report.
Report Field | Explanation |
|---|---|
PY__RID_Settlement PY__RID_Authorization PY__Account_ID PY__Token PY__Account_External_Reference PY__File_ID PY__Transaction_ID PY__Network PY__MTID PY__Created_Date PY__Matched_Status PY__Is_Debit PY__Product_ID PY__Product_Name PY__Settlement_Note PY__Transaction_Type | (Refer to the section Paymentology-Specific Data Fields ) |
DE3_1__Cardholder_Transaction_Type Processing Code, describes the effect of a transaction on a customer account and the type of accounts affected.Position 1-2 = Cardholder transaction type (numeric) | Format: Numeric Example: |
DE3_2__Cardholder_from_Account_Type_Code Position 3-4 = Cardholder ‘from’ Account type | Format: Numeric Example: |
DE3_3__Cardholder_To_Account_Type_Code Position 5-6 = Cardholder ‘to’ Account type | Format: Numeric Example: |
DE4__Transaction_Amount Local amount with the sign, indicating the net direction of funds flow. Currency provided in DE49 | Format: Decimal Example: |
DE5__Reconciliation_Amount Settlement amount with the sign, indicating the net direction of funds flow. Currency provided in DE50 | Format: Decimal Example: |
DE6__Billing_Amount Cardholder Billing amount with the sign, indicating the net direction of funds flow. Currency provided in DE51 | Format: Decimal Example: |
DE9__Conversion_Rate_Reconciliation Conversion rate to Reconciliation/Settlement currency | Format: Decimal Example: |
DE10__Conversion_Rate_Billing Conversion rate to Cardholder billing currency | Format: Decimal Example: |
DE12__Transaction_Date_Time Date/time of local original spend. Note: Mastercard frequently provide 00:00:00 as time element. | Datetime: YYYY-MM-DD HH:MM:SS Example: 2023-09-23 21:21:10 |
DE22_6__Card_Present_Data Indicates if the card is present at the point of service | Format: Numeric Possible Values: Example: |
DE22_7__Card_Data_Input_Mode Indicates the method used for PAN entry to initiate a transaction | Format: Alphanumeric Possible Values: Example: |
DE23__Card_Sequence_Number Distinguishes among separate cards that have the same PAN | Format: Numeric Example: |
DE24__Function_Code Indicates the specific purpose for a message | Format: Numeric Example: |
DE25__Message_Reason_Code Provides the message receiver with the reason for sending the message | Format: Numeric Example: |
DE26__Merchant_Category_Code Classifies the type of business applicable to the acceptor | Format: Numeric Example: |
DE30_1__Original_Amount_Transaction Contains the “amount” data element values from the First Presentment or Fee Collection (DE4). Used for chargeback or retrieval request. | Format: Numeric Example: |
DE30_2__Original_Amount_Reconciliation DE 30 (Amounts, reconciliation) Note: Mastercard populate this with all zeros which in turn is displayed as 0 | Format: Numeric Example: |
DE31__Acquirer_Reference_Data Acquirer Reference Data (See MC IPM Clearing Formats document) | Format: Numeric Example: |
DE32__Acquiring_Institution_ID_Code Identifies the transaction acquirer | Format: Numeric Example: |
DE33__Forwarding_Institution_ID_Code Identifies a message’s forwarding institution | Format: Numeric |
DE37__Retrieval_Reference_Number It is a transaction information document reference number the acceptor’s or designated agent’s system supplies. | Format: Numeric Example: |
DE38__Approval_Code It is a code the authorizing institution assigns indicating approval | Format: Numeric Example: |
DE40__Service_Code Service Code | Format: Numeric Example: |
DE41__Card_Acceptor_Terminal_ID Card Acceptor Terminal Identification | Format: Numeric Example: |
DE42__Card_Acceptor_ID_Code Card Acceptor ID Code | Format: Numeric Example: |
DE43_1__Card_Acceptor_Name Card Acceptor Name (22 long) | Format: Alphanumeric Example: |
DE43_2__Card_Acceptor_Street_Address Card Acceptor Street address (48 long) | Format: Alphanumeric Example: |
DE43_3__Card_Acceptor_City Card Acceptor City (13 long) | Format: Alphabetic Example: |
DE43_4__Card_Acceptor_Zip_Code Post/zip code (10 long) | Format: Alphanumeric Example: |
DE43_5__Card_Acceptor_State_Code State or province (3 long) | Format: Alphabetic Example: |
DE43_6__Card_Acceptor_Country_Code Country Code (3 long) | Format: Alphabetic Example: |
DE48_0002__GCMS_Product_Identifier GCMS Product Identifier | Format: Alphabetic Example: |
DE48_0003__Licensed_Product_Identifier Licensed Product Identifier | Format: Alphabetic Example: |
DE48_0023__Terminal_Type Terminal Type, identifies the type of terminal used at the point of interaction | Format: Alphabetic Example: |
DE48_0025_1__Message_Reversal_Indicator Identifies whether it is the original message or the reversal of the original message. | Format: Numeric Possible Values: Example: |
DE48_0105__Network_File_Reference File ID from the network | Format: Numeric Example: |
DE48_0158_1__Card_Program_Identifier Identifies the card program or financial network to which a transaction belongs | Format: Alphabetic Example: |
DE48_0158_2__Business_Service_Arrangement_Type_Code Identifies the business relationship between the transaction’s participants. | Format: Numeric Possible Values: Example: |
DE48_0158_3__Business_Service_ID_Code Identifies the business service to which the transaction is assigned for reconciliation and rules basis | Format: Numeric Example: |
DE48_0158_4__Interchange_Rate_Designaor Indicates the interchange rate and editing rules applied to the transaction | Format: Numeric Example: |
DE48_0158_5__Central_Site_Business_Date Identifies the official business processing date when the business service reconciles a transaction | Format: DateTime Example: |
DE48_0158_6__Business_Cycle Identifies a reconciliation period in a Business Date | Format: Numeric Example: |
DE48_0158_7__Card_Acceptor_Classification_Override_Indicator Card Acceptor Classification Override Indicator, with appropriate values to indicate whether Card Acceptor Business Code (MCC) override rates, Card Acceptor Business (CAB) Type override rates, or neither, were used in the interchange fee amount designated in PDS 0146 (Amount, Transaction Fees) | Format: Alphanumeric (can be blank or contain whitespace) Possible Values: (Refer to the Mastercard IPM Clearing Specifications for full list of supported values)Example: |
DE48_0158_8__Product_Class_Override_Indicator Indicate whether product class override interchange rates were used in the interchange fee amount designated in PDS 0146 (Amount, Transaction Fees) | Format: Alphabetic (can be blank or whitespace) Possible Values: (Refer to the Mastercard IPM Clearing Specifications for full list of supported values)Example: |
DE48_0158_9__Corporate_Incentive_Rates_Apply_Indicator It indicates if corporate incentive rates were used in the interchange fee amount designated in PDS 0146 (Amounts, Transaction Fee) | Format: Alphanumeric Possible Values: Example: |
DE48_0158_10__Special_Conditions_Indicator Indicates whether an adjustment was included in the Fee amount | Format: Alphanumeric Possible Values: Example: |
DE48_0158_11__MC_Assigned_ID_Override_Indicator Indicates whether override rates were used in the interchange fee amount designated in PDS 0146 (Amount, Transaction Fees) | Format: Alphabetic Possible Values: Example: |
DE48_0158_12__Account_Level_Management_Account_Category_Code Indicates whether the account associated with the transaction (stored on DE 2 is participating in one or several Account Level Management programs where an incremental interchange is included in the transaction’s interchange amount. N = default | Format: Alphabetic Possible Values: Example: |
DE48_0158_13__Rate_Indicator Indicates the rate applied by GCMS to the transaction | Format: Alphanumeric Possible Values: Example: |
DE48_0158_14__Masterpass_Incentive_Indicator Identifies the transaction as having received the Masterpass-Enabled Merchant Incentive. | Format: Alphabetic Possible Values: Example: |
DE48_159_3__Settlement_Service_Level_Code It is a one-digit code that identifies the settlement level of the settlement service | Format: Numeric Possible Values: Example: |
DE48_159_6__Reconciliation_Date Identifies the clearing system’s processing date expressed in the local time zone of the clearing system’s processing center | Format: DateTime Example: |
DE48_159_7__Reconciliation_Cycle Identifies a reconciliation period in a reconciliation date. | Format: Numeric Possible Values: Example: |
DE48_159_8__Settlement_Date Identifies the date that the settlement service initiates settlement for the message, such as the settlement advisement date, which is based on the clearing date, settlement service cutoff cycle, and calendar for the settlement service. | Format: DateTime Example: |
DE48_159_9__Settlement_Cycle Identifies a settlement period in a settlement date | Format: Numeric Possible Values: Example: |
DE48_0177_1__Cross_Border_Indicator Identifies whether the transaction qualified as a Crossborder transaction and could be subject to Cross-border transaction pricing guidelines. | Format: Alphabetic Possible Values: Example: |
DE48_0177_2__Currency_Indicator Identifies whether the transaction was submitted to Mastercard in the local currency of the merchant. | Format: Alphabetic Possible Values: Example: |
DE49__Currency_Code_Transaction Currency of transaction (local currency) | Format: Numeric Example: |
DE50__Currency_Code_Reconciliation Currency of reconciliation/Settlement | Format: Numeric Example: |
DE51__Currency_Code_Billing Currency of Cardholder Billing | Format: Numeric Example: |
DE54_2__Additional_Amount_Type Other Amounts – e.g. cashback portions in cash back transactions. Surcharges also appear here | Format: Numeric Example: |
DE54_3__Additional_Amount_Currency_Code Indicates currency of the Surcharge amount | Format: Numeric Example: |
DE54_4__Additional_Amount_Sign Additional Amount Sign (D for debit and C for Credit) | Format: Alphabetic Example: |
DE54_5__Additional_Amount Other Amounts – e.g. cashback portions in cash back transactions. Surcharges also appear here. DE54_5 is amount, DE54_4 is amount sign | Format: Numeric Example: |
DE63__Transaction_Life_Cycle_ID Transaction Life Cycle ID | Format: Alphanumeric Example: |
DE71__Message_Number Message Number – identifies the message within the T112 Mastercard file | Format: Numeric Example: |
DE72__Data_Record Used in Fee type messages to provide description of the fee | Format: String Example: |
DE73__Action_Date In Fee Collection messages, this data element identifies a reference date related to the Fee. | Format: DateTime Example: |
DE94__Transaction_Originator_Institution_ID Transaction Originator Institution ID, identifies the transaction originator institution | Format: Numeric
|
DE100__Receiving_Institution_ID Receiving Member ID (Paymentology processor id) | Format: Numeric
|
DE111__Amount_Currency_Conversion_Assessment The amount based on the result of Applying the multi-currency conversion rate (Currency Conversion Assessment) adjustment to the currency conversion rate used to convert DE 4 (Amount, Transaction) to DE 6 (Amount, Cardholder Billing) for qualified transactions. | Format: Numeric Example: |
Sample report file
Link to the MC v2.0 Sample Presentment report
Mastercard and Mada
Mastercard and Mada v1.0
Below specifies the format of a Presentment report when the scheme is Mastercard and using Mada as well.
Report Field | Explanation |
|---|---|
PY__RID_Settlement PY__RID_Authorization PY__Account_ID PY__Token PY__Account_External_Reference PY__File_ID PY__Transaction_ID PY__Network PY__MTID PY__Created_Date PY__Matched_Status PY__Is_Debit PY__Product_ID PY__Product_Name PY__Settlement_Note | (Refer to the section Paymentology-Specific Data Fields ) |
DE3_1__Cardholder_Transaction_Type Processing Code, describes the effect of a transaction on a customer account and the type of accounts affected.Position 1-2 = Cardholder transaction type (numeric) | Format: Numeric Example: |
DE3_2__Cardholder_from_Account_Type_Code Position 3-4 = Cardholder ‘from’ Account type | Format: Numeric Example: |
DE3_3__Cardholder_To_Account_Type_Code Position 5-6 = Cardholder ‘to’ Account type | Format: Numeric Example: |
DE4__Transaction_Amount Local amount with the sign, indicating the net direction of funds flow. Currency provided in DE49 | Format: Decimal Example: |
DE5__Reconciliation_Amount Settlement amount with the sign, indicating the net direction of funds flow. Currency provided in DE50 | Format: Decimal Example: |
DE6__Billing_Amount Cardholder Billing amount with the sign, indicating the net direction of funds flow. Currency provided in DE51 | Format: Decimal Example: |
DE9__Conversion_Rate_Reconciliation Conversion rate to Reconciliation/Settlement currency | Format: Decimal Example: |
DE10__Conversion_Rate_Billing Conversion rate to Cardholder billing currency | Format: Decimal Example: |
DE12__Transaction_Date_Time Date/time of local original spend. Note: Mastercard frequently provide 00:00:00 as time element. | Datetime: Example: |
DE17__Capture_Date This data element contains the month and day when the transaction data was processed (acquired) by the acquirer. | Format: DateTime
Pattern: Example: |
DE22_6__Card_Present_Data Indicates if the card is present at the point of service | Format: Numeric Possible Values:
Example: |
DE22_7__Card_Data_Input_Mode Indicates the method used for PAN entry to initiate a transaction | Format: Alphabetic Possible Values:
Example: |
DE23__Card_Sequence_Number Distinguishes among separate cards that have the same PAN | Format: Numeric Example: |
DE24__Function_Code Indicates the specific purpose for a message | Format: Numeric Example: |
DE25__Message_Reason_Code Provides the message receiver with the reason for sending the message | Format: Numeric Example: |
DE26__Merchant_Category_Code Classifies the type of business applicable to the acceptor | Format: Numeric Example: |
DE30_1__Original_Amount_Transaction Contains the “amount” data element values from the First Presentment or Fee Collection (DE4). Used for chargeback or retrieval request. | Format: Numeric Example: |
DE30_2__Original_Amount_Reconciliation DE 30 (Amounts, reconciliation) Note: Mastercard populate this with all zeros which in turn is displayed as 0 | Format: Numeric Example: |
DE31__Acquirer_Reference_Data Acquirer Reference Data | Format: Numeric Example:
|
DE32__Acquiring_Institution_ID_Code Identifies the transaction acquirer | Format: Numeric Example: |
DE33__Forwarding_Institution_ID_Code Identifies a message’s forwarding institution | Format: Numeric
Example: |
DE37__Retrieval_Reference_Number It is a transaction information document reference number the acceptor’s or designated agent’s system supplies. | Format: Numeric Example: |
DE38__Approval_Code It is a code the authorizing institution assigns indicating approval | Format: Numeric Example: |
DE40__Service_Code Service Code | Format: Numeric Example: |
DE41__Card_Acceptor_Terminal_ID Card Acceptor Terminal Identification | Format: Numeric Example: |
DE42__Card_Acceptor_ID_Code Card Acceptor ID Code | Format: Numeric Example: |
DE43_1__Card_Acceptor_Name Card Acceptor Name (22 long) | Format: Alphanumeric Example: |
DE43_2__Card_Acceptor_Street_Address Card Acceptor Street address (48 long) | Format: Alphanumeric Example: |
DE43_3__Card_Acceptor_City Card Acceptor City (13 long) | Format: Alphabetic Example: |
DE43_4__Card_Acceptor_Zip_Code Post/zip code (10 long) | Format: Alphanumeric Example: |
DE43_5__Card_Acceptor_State_Code State or province (3 long) | Format: Alphabetic Example: |
DE43_6__Card_Acceptor_Country_Code Country Code (3 long) | Format: Alphabetic Example: |
DE48_0002__GCMS_Product_Identifier GCMS Product Identifier, e.g. MRW is Prepaid Mastercard Business Card (Non-U.S.) | Format: Alphabetic Example: |
DE48_0003__Licensed_Product_Identifier Licensed Product Identifier | Format: Alphabetic Example: |
DE48_0023__Terminal_Type Terminal Type, identifies the type of terminal used at the point of interaction | Format: Alphabetic Example: |
DE48_0025_1__Message_Reversal_Indicator Identifies whether it is the original message or the reversal of the original message. | Format: Numeric Possible Values:
Example: |
DE48_0105__Network_File_Reference File ID from the network | Format: Numeric Example:
|
DE48_0158_1__Card_Program_Identifier Identifies the card program or financial network to which a transaction belongs | Format: Alphabetic Example: |
DE48_0158_2__Business_Service_Arrangement_Type_Code Identifies the business relationship between the transaction’s participants | Format: Numeric Possible Values:
Example: |
DE48_0158_3__Business_Service_ID_Code Identifies the business service to which the transaction is assigned for reconciliation and rules basis | Format: Numeric Example: |
DE48_0158_4__Interchange_Rate_Designaor Indicates the interchange rate and editing rules applied to the transaction | Format: Numeric Example: |
DE48_0158_5__Central_Site_Business_Date Identifies the official business processing date when the business service reconciles a transaction | Format: DateTime
Pattern: Example: |
DE48_0158_6__Business_Cycle Identifies a reconciliation period in a Business Date | Format: Numeric Example: |
DE48_0158_7__Card_Acceptor_Classification_Override_Indicator Indicate whether Card Acceptor Business Code (MCC) override rates, Card Acceptor Business (CAB) Type override rates, or neither, were used in the interchange fee amount designated in PDS 0146 (Amount, Transaction Fees) | Format: Alphanumeric (can be blank or contain whitespace) Possible Values: (Refer to the Mastercard IPM Clearing Specifications for full list of supported values)Example: |
DE48_0158_8__Product_Class_Override_Indicator Indicate whether product class override interchange rates were used in the interchange fee amount designated in PDS 0146 (Amount, Transaction Fees) | Format: Alphabetic (can be blank or whitespace) Possible Values: (Refer to the Mastercard IPM Clearing Specifications for full list of supported values)Example: |
DE48_0158_9__Corporate_Incentive_Rates_Apply_Indicator It indicates if corporate incentive rates were used in the interchange fee amount designated in PDS 0146 (Amounts, Transaction Fee) | Format: Alphanumeric Possible Values:
Example: |
DE48_0158_10__Special_Conditions_Indicator Indicates whether an adjustment was included in the Fee amount | Format: Alphanumeric Possible Values:
Example: |
DE48_0158_11__MC_Assigned_ID_Override_Indicator Indicates whether override rates were used in the interchange fee amount designated in PDS 0146 (Amount, Transaction Fees) | Format: Alphabetic Possible Values:
Example: |
DE48_0158_12__Account_Level_Management_Account_Category_Code Account Level Management Account Category Code, indicates whether the account associated with the transaction (stored on DE 2 is participating in one or several Account Level Management programs where an incremental interchange is included in the transaction’s interchange amount. N = default | Format: Alphabetic Possible Values:
Example: |
DE48_0158_13__Rate_Indicator Indicates the rate applied by GCMS to the transaction | Format: Alphabetic Possible Values:
Example: |
DE48_0158_14__Masterpass_Incentive_Indicator Masterpass Incentive Indicator, is populated by GCMS and identifies the transaction as having received the Masterpass-Enabled Merchant Incentive. Yes or No | Format: Alphabetic Example: |
DE48_159_3__Settlement_Service_Level_Code It is a one-digit code that identifies the settlement level of the settlement service | Format: Numeric Possible Values:
Example: |
DE48_159_6__Reconciliation_Date Identifies the clearing system’s processing date expressed in the local time zone of the clearing system’s processing center | Format: DateTime
Pattern: Example: |
DE48_159_7__Reconciliation_Cycle Identifies a reconciliation period in a reconciliation date. | Format: Numeric Possible Values:
Example: |
DE48_159_8__Settlement_Date Identifies the date that the settlement service initiates settlement for the message, such as the settlement advisement date, which is based on the clearing date, settlement service cutoff cycle, and calendar for the settlement service. | Format: DateTime
Pattern: Example: |
DE48_159_9__Settlement_Cycle Identifies a settlement period in a settlement date | Format: Numeric Possible Values:
Example: |
DE48_0177_1__Cross_Border_Indicator Identifies whether the transaction qualified as a Crossborder transaction and could be subject to Cross-border transaction pricing guidelines. | Format: Alphabetic Possible Values:
Example: |
DE48_0177_2__Currency_Indicator Identifies whether the transaction was submitted to Mastercard in the local currency of the merchant. | Format: Alphabetic Possible Values:
Example: |
DE49__Currency_Code_Transaction Currency of transaction (local currency) | Format: Numeric Example: |
DE50__Currency_Code_Reconciliation Currency of reconciliation/Settlement | Format: Numeric Example: |
DE51__Currency_Code_Billing Currency of Cardholder Billing | Format: Numeric Example: |
DE54_2__Additional_Amount_Type Other Amounts – e.g. cashback portions in cash back transactions. Surcharges also appear here | Format: Numeric Example: |
DE54_3__Additional_Amount_Currency_Code Indicates currency of the Surcharge amount | Format: Numeric Example: |
DE54_4__Additional_Amount_Sign Additional Amount Sign (D for debit and C for Credit) | Format: Alphabetic Example: |
DE54_5__Additional_Amount Other Amounts – e.g. cashback portions in cash back transactions. Surcharges also appear here. DE54_5 is amount, DE54_4 is amount sign | Format: Numeric Example: |
DE63__Transaction_Life_Cycle_ID Transaction Life Cycle ID | Format: Alphanumeric Example: |
DE71__Message_Number Message Number – identifies the message within the T112 Mastercard file | Format: Numeric Example: |
DE72__Data_Record Used in Fee type messages to provide description of the fee | Format: String Example: |
DE73__Action_Date In Fee Collection messages, this data element identifies a reference date related to the Fee. | Format: DateTime
Pattern: Example: |
DE94__Transaction_Originator_Institution_ID Transaction Originator Institution ID, identifies the transaction originator institution | Format: Numeric
|
DE97__Net_Reconciliation_Amount | |
DE100__Receiving_Institution_ID Receiving Member ID (Paymentology processor id) | Format: Numeric
|
DE111__Amount_Currency_Conversion_Assessment The amount based on the result of Applying the multi-currency conversion rate (Currency Conversion Assessment) adjustment to the currency conversion rate used to convert DE 4 (Amount, Transaction) to DE 6 (Amount, Cardholder Billing) for qualified transactions. | Format: Numeric Example: |
DE122__Card_Scheme_Sponser_ID The Card Scheme Sponsor Identifier, assigned by mada, is a unique identifier for the financial institution. It contains the identifier of the Card Scheme Acquirer Bank, which agrees to settle a Bank Card Scheme's transactions. | Format: Alphanumeric Example: |
DE124__POS_Terminal_Reconcile_Total The mada POS Terminal Reconcile Total is used to carry terminal transaction activity. The transaction details are calculated by the terminal for each card scheme accepted at that terminal. | Format: Alphanumeric |
DE127__POS_Host_Reconcile_Total The mada POS Host Reconcile Total is used to carry terminal transaction activity. The transaction details are calculated by the mada host for each card scheme accepted at that terminal. | Format: Alphanumeric |
ADD_REF_RID Indicates the RID of the original linked authorisation in case of refund or reversal | Format: Numeric Example: |
Merchant_Reference_ID Merchant allocated unique Order Identifier used as a merchant reference for inquiry and tracking. | Format: Alphanumeric Example: |
Gateway_ID Primary & Secondary Gateway Identifier | Format: Alphanumeric (can be blank or contain whitespaces) Possible Values:
Example: |
COF_Data Card On File (COF) Transaction Context. This sub-element is mandatory for all COF transactions and when present, it indicates the COF transaction use-case and relation type. | Format: Alphanumeric Possible Values: (Refer to the Mada TLF Specifications for full list of supported values)Example: |
Payment_Transaction_Number SADAD Payment Transaction Number Unique transaction number identifier for each payment at Sadad, it is generated by Sadad System | Format: Numeric Example: |
Biller_ID To be used to identify the specific biller in accordance with ongoing billers supported by Sadad. | Format: Numeric Example: |
Bill_ID Unique bill identification number for the specified biller. | Format: Numeric Example: |
Payment_Status Note: Issuers will only receive this Tag field for reversals." | Format: Alphabetic Possible Values:
Example: |
Bill_Payment_Amount_Due | Format: Decimal Example: |
Sample report file
Link to the Mada v1.0 Sample Presentment report
Visa
This section outlines the structure of the Presentment Report for Visa. Three versions are currently supported: v2.0, v3.0, and v4.0. If your setup includes Visa processing, please confirm which version of the report you are receiving.
NoteAll new clients should integrate with the latest report version
Visa v2.0
ImportantThis report version (Visa v2.0) will be discontinued by 1st November 2025.
You can refer to our Migration guidelines for helpful information on how you can upgrade from v2.0 to v4.0.
Official communication was sent to you around 1st November 2024.
Below are the data fields and format of the Visa v2.0 Presentments report.
Click here to view the complete list of fields
Report Field | Explanation |
|---|---|
PY__RID_Settlement PY__RID_Authorization PY__Account_ID PY__Account_Currency PY__Token PY__Account_External_Reference PY__Transaction_ID PY__Network PY__Created_Date PY__Matched_Status PY__Product_ID PY__Product_Name PY__Settlement_Note | (Refer to the section Paymentology-Specific Data Fields) |
Transaction_Code Two digit code determining the type of transaction | Format: Numeric Possible Values: Example: |
Transaction_Code_Qualifier | Format: Numeric Possible Values: Example: |
Acquirer_Reference_Number A 23-digit identification number assigned by the acquirer. | Format: Numeric Example: |
Acquirer_Business_ID Contains the Visa-assigned business ID of the acquirer that signed the merchant for processing purchase or mail/phone order transactions. In this case, the acquirer is referred to as the Merchant Sponsor. The entry must be numeric | Format: Numeric (can be blank or contain zero) Example: |
Purchase_Date Date the purchase transaction was made. | Format: DateTime Example: |
Destination_Amount Identifies the submitted transaction amount in the currency that is appropriate to the destination endpoint.It is the billing amount. | Format: Decimal Example: |
Destination_Currency_Code The currency type presented to the member on incoming transactions.It is the billing currency | Format: Numeric Example: |
Source_Amount The purchase value in transaction currency | Format: Decimal Example: |
Source_Currency_Code Currency code used in the transaction | Format: Numeric Example: |
Merchant_Name Name of the merchant in the original transaction | Format: Alphanumeric Example: |
Merchant_City Merchant city, telephone number, email address, or URL | Format: Alphabetic Example: |
Merchant_Country_Code Code indicating country where the Visa transaction | Format: Alphabetic Example: |
Merchant_Category_Code Indicates merchant’s type of business product or service | Format: Numeric Example: |
Merchant_ZIP_Code Postal code of the merchant where the transaction took place | Format: Numeric Example: |
Merchant_State_Province_Code If the Merchant Country Code is US or CA, this field will contain a valid U.S. State Code or Canadian Province Code, respectively. Otherwise, it must contain spaces. | Format: Alphabetic (can be blank or contain whitespace) Example: |
Settlement_Flag Indicates the service used for settlement | Format: Numeric Possible Values: Example: |
Authorization_Characteristics_Indicator Code used by the acquirer to request CPS qualification | Format: Alphanumeric (can be blank or contain whitespace) Possible Values: Example: |
Authorization_Code Code that an issuer, its authorizing processor, or Stand-In Processing (STIP) provides to indicate approval of a transaction | Format: Alphanumeric Example: |
Cardholder_ID_Method Indicates method used to identify cardholder (e.g., signature, Personal Identification Number (PIN), etc.). | Format: Alphanumeric (can be blank or contain whitespace) Possible Values: |
POS_Entry_Mode A V.I.P. System field indicating the method by which a point-of-transaction terminal obtains and transmits the cardholder information necessary to complete a Transaction. | Format: Alphanumeric (can be blank or contain whitespace) Possible Values: Example: |
Central_Processing_Date The date that BASE II processes this transaction or item. Note: You should use this date for your financial reconcilation with the scheme. | Format: DateTime Example: |
Member_Message_Text This field is used to send text messages | Format: String Example: |
Card_Acceptor_ID Code that identifies the card acceptor operating the POS terminal. | Format: Alphanumeric Example: |
Terminal_ID Code that identifies the card acceptor terminal or ATM. | Format: Alphanumeric Example: |
Interface_Trace_Number Trace Number from the dispute or dispute response. | Reserved field. |
AVS_Response_Code Contains the response to an Address Verification Service (AVS) request, indicating matches or discrepancies between addresses and ZIP codes. | Format: Alphanumeric (can be blank or contain whitespace) Example: |
Authorization_Source_Code Indicates whether authorization was obtained and the source of the authorization. | Format: Alphanumeric (can be blank or contain whitespace) Possible Values: Example: |
Transaction_Code_Qualifier__TCR3 TCQ for the Base II TCR3 record | Format: Numeric Possible Values: Example: |
Transaction_Component_Sequence_Number__TCR3 TCS Number for the Base II TCR3 record | Format: Numeric Possible Values: |
Fast_Funds_Indicator VIC will return the transaction if any non-space value is present on an Original Transaction. | Format: Alphanumeric (can be blank or contain whitespace) |
Business_Format_Code Code indicating the type of business that is applicable to this transaction. | Format: Alphanumeric (can be blank or contain whitespace) Example: |
Business_Application_ID This field provides additional information regarding the usage and application of the transaction | Format: Alphanumeric (can be blank or contain whitespace) Example: |
Source_of_Funds | Format: Numeric (can be blank or contain whitespace) Possible Values: |
Payment_Reversal_Reason_Code | Format: Numeric (can be blank or contain whitespace)
|
Sender_Reference_Number This field will contain a transaction reference number that is provided by the originator and can be used to uniquely identify the sender | Format: Alphanumeric (can be blank or contain whitespace) Example: |
Sender_Account_Number This field will contain the sender's card number or bank | Format: Alphanumeric (can be blank or contain whitespace) |
Sender_Name This field will contain the name of the person or entity for the account from which funds are to be taken. | Format: Alphanumeric (can be blank or contain whitespace) |
Sender_Address This field will contain the address of the person or entity for the account from which funds are to be taken | Format: Alphanumeric (can be blank or contain whitespace) |
Sender_City This field will contain the city of the person or entity for the account from which funds are to be taken. | Format: Alphanumeric (can be blank or contain whitespace) |
Sender_State This field will contain the geographical state or province of the person or entity for the account from which funds are to be taken. | Format: Alphanumeric (can be blank or contain whitespace) |
Sender_Country This field will contain the country of the person or entity for the account from which funds are to be taken | Format: Alphanumeric (can be blank or contain whitespace) |
Transaction_Code_Qualifier__TCR5 TCQ for the Base II TCR5 record | Format: Numeric Possible Values: Example: |
Transaction_Component_Sequence_Number__TCR5 TCS Number for the Base II TCR5 record | Format: Numeric Possible Values: |
Transaction_Identifier A unique value that Visa assigns to each transaction and returns to the acquirer in the authorization response. | Format: Numeric Example: |
Authorized_Amount Amount the issuer originally authorized. The entry must be numeric. For CPS original draft transactions and their reversals, this entry may not be zeros. CPS credit vouchers and their reversals must contain zeros in this field. | Format: Numeric Example: |
Authorization_Currency_Code Currency code of the authorized source amount | Format: Numeric Example: |
Interchange_Fee_Amount Specifies the interchange fee amount (in the settlement currency of the member) calculated by Visa for this transaction | Format: Decimal Example: |
Interchange_Fee_Sign Specifies if the interchange fee amount is a credit or a debit for the receiving member. | Format: Alphabetic Possible Values: |
Source_Currency_to_Base_Currency_Exchange_Rate Specifies the currency exchange rate applied to this transaction when Visa converts the source amount to the transaction amount in the destination currency | Format: Decimal Example: |
Base_Currency_to_Destination_Currency_Exchange_Rate Specifies the currency exchange rate applied to this transaction when Visa converts the source amount to the transaction amount in the destination currency | Format: Decimal Example: |
Optional_Issuer_ISA_Amount This ISO-defined field can be used for any charge type or any fee applied to a transaction. Currently, Visa uses this field to carry optional International Service Assessment (ISA) data for issuers in the LAC region | Format: Decimal (can be blank or contain zero) Example: |
Product_ID Product identifier code | Format: Alphanumeric Example: |
CVV2_Result_Code Card Verification Value 2 (CVV2) is the verification result for card-not-present transactions and also for card-present CVV2 verification-only requests | Format: Alphanumeric (can be blank or contain whitespace) Example: |
Sample report file
Link to the Visa v2.0 Sample Presentment report
Visa v3.0
ImportantThis report version (Visa v3.0) will be discontinued by 1st November 2025.
You can refer to our Migration guidelines for helpful information on how you can upgrade from v3.0 to v4.0.
Official communication was sent to you around 1st November 2024.
Key changesBelow are the notable differences between v2.0 and v3.0:
- Addition of a new field
Usage_Code
Click here to view the complete list of fields and a sample file
Report Field | Explanation |
|---|---|
PY__RID_Settlement PY__RID_Authorization PY__Account_ID PY__Account_Currency PY__Token PY__Account_External_Reference PY__Transaction_ID PY__Network PY__Created_Date PY__Matched_Status PY__Product_ID PY__Product_Name PY__Settlement_Note | (Refer to the section Paymentology-Specific Data Fields) |
Transaction_Code Two digit code determining the type of transaction | Format: Numeric Possible Values: Example: |
Transaction_Code_Qualifier | Possible Values: Example: |
Usage_Code Indicates whether this is the first presentment or the second. | Format: Numeric Possible Values: Example: |
Acquirer_Reference_Number A 23-digit identification number assigned by the acquirer. | Format: Numeric Example: |
Acquirer_Business_ID Contains the Visa-assigned business ID of the acquirer that signed the merchant for processing purchase or mail/phone order transactions. In this case, the acquirer is referred to as the Merchant Sponsor. The entry must be numeric | Format: Numeric (can be blank or contain zero) Example: |
Purchase_Date Date the purchase transaction was made. | Format: DateTime Example: |
Destination_Amount Identifies the submitted transaction amount in the currency that is appropriate to the destination endpoint.It is the billing amount. | Format: Decimal Example: |
Destination_Currency_Code The currency type presented to the member on incoming transactions.It is the billing currency | Format: Numeric Example: |
Source_Amount The purchase value in transaction currency | Format: Decimal Example: |
Source_Currency_Code Currency code used in the transaction | Format: Numeric Example: |
Merchant_Name Name of the merchant in the original transaction | Format: Alphanumeric Example: |
Merchant_City Merchant city, telephone number, email address, or URL | Format: Alphabetic Example: |
Merchant_Country_Code Code indicating country where the Visa transaction | Format: Alphabetic Example: |
Merchant_Category_Code Indicates merchant’s type of business product or service | Format: Numeric Example: |
Merchant_ZIP_Code Postal code of the merchant where the transaction took place | Format: Numeric Example: |
Merchant_State_Province_Code If the Merchant Country Code is US or CA, this field will contain a valid U.S. State Code or Canadian Province Code, respectively. Otherwise, it must contain spaces. | Format: Alphabetic (can be blank or contain whitespace) Example: |
Settlement_Flag Indicates the service used for settlement | Format: Numeric Possible Values: Example: |
Authorization_Characteristics_Indicator Code used by the acquirer to request CPS qualification | Format: Alphanumeric (can be blank or contain whitespace) Possible Values: Example: |
Authorization_Code Code that an issuer, its authorizing processor, or Stand-In Processing (STIP) provides to indicate approval of a transaction | Format: Alphanumeric Example: |
Cardholder_ID_Method Indicates method used to identify cardholder (e.g., signature, Personal Identification Number (PIN), etc.). | Format: Alphanumeric (can be blank or contain whitespace) Possible Values: |
POS_Entry_Mode A V.I.P. System field indicating the method by which a point-of-transaction terminal obtains and transmits the cardholder information necessary to complete a Transaction. | Format: Alphanumeric (can be blank or contain whitespace) Possible Values: Example: |
Central_Processing_Date The date that BASE II processes this transaction or item. Note: You should use this date for your financial reconcilation with the scheme. | Format: DateTime Example: |
Member_Message_Text This field is used to send text messages | Format: String (can be empty or contain whitespace) Example: |
Card_Acceptor_ID Code that identifies the card acceptor operating the POS terminal. | Format: Alphanumeric Example: |
Terminal_ID Code that identifies the card acceptor terminal or ATM. | Format: Alphanumeric Example: |
Interface_Trace_Number Trace Number from the dispute or dispute response. | Reserved field. |
AVS_Response_Code Contains the response to an Address Verification Service (AVS) request, indicating matches or discrepancies between addresses and ZIP codes. | Format: Alphanumeric (can be blank or contain whitespace) Example: |
Authorization_Source_Code Indicates whether authorization was obtained and the source of the authorization. | Format: Alphanumeric (can be blank or contain whitespace) Possible Values: Example: |
Transaction_Code_Qualifier__TCR3 TCQ for the Base II TCR3 record | Format: Numeric Possible Values: Example: |
Transaction_Component_Sequence_Number__TCR3 TCS Number for the Base II TCR3 record | Format: Numeric Possible Values: |
Fast_Funds_Indicator VIC will return the transaction if any non-space value is present on an Original Transaction. | Format: Alphanumeric (can be blank or contain whitespace) |
Business_Format_Code Code indicating the type of business that is applicable to this transaction. | Format: Alphanumeric (can be blank or contain whitespace) Example: |
Business_Application_ID This field provides additional information regarding the usage and application of the transaction | Format: Alphanumeric (can be blank or contain whitespace) Example: |
Source_of_Funds | Format: Numeric (can be blank or contain whitespace) Possible Values: |
Payment_Reversal_Reason_Code | Format: Numeric (can be blank or contain whitespace)
|
Sender_Reference_Number This field will contain a transaction reference number that is provided by the originator and can be used to uniquely identify the sender | Format: Alphanumeric (can be blank or contain whitespace) Example: |
Sender_Account_Number This field will contain the sender's card number or bank | Format: Alphanumeric (can be blank or contain whitespace) |
Sender_Name This field will contain the name of the person or entity for the account from which funds are to be taken. | Format: Alphanumeric (can be blank or contain whitespace) |
Sender_Address This field will contain the address of the person or entity for the account from which funds are to be taken | Format: Alphanumeric (can be blank or contain whitespace) |
Sender_City This field will contain the city of the person or entity for the account from which funds are to be taken. | Format: Alphanumeric (can be blank or contain whitespace) |
Sender_State This field will contain the geographical state or province of the person or entity for the account from which funds are to be taken. | Format: Alphanumeric (can be blank or contain whitespace) |
Sender_Country This field will contain the country of the person or entity for the account from which funds are to be taken | Format: Alphanumeric (can be blank or contain whitespace) |
Transaction_Code_Qualifier__TCR5 TCQ for the Base II TCR5 record | Format: Numeric Possible Values: Example: |
Transaction_Component_Sequence_Number__TCR5 TCS Number for the Base II TCR5 record | Format: Numeric Possible Values: |
Transaction_Identifier A unique value that Visa assigns to each transaction and returns to the acquirer in the authorization response. | Format: Numeric Example: |
Authorized_Amount Amount the issuer originally authorized. The entry must be numeric. For CPS original draft transactions and their reversals, this entry may not be zeros. CPS credit vouchers and their reversals must contain zeros in this field. | Format: Numeric Example: |
Authorization_Currency_Code Currency code of the authorized source amount | Format: Numeric Example: |
Interchange_Fee_Amount Specifies the interchange fee amount (in the settlement currency of the member) calculated by Visa for this transaction | Format: Decimal Example: |
Interchange_Fee_Sign Specifies if the interchange fee amount is a credit or a debit for the receiving member. | Format: Alphabetic Possible Values: |
Source_Currency_to_Base_Currency_Exchange_Rate Specifies the currency exchange rate applied to this transaction when Visa converts the source amount to the transaction amount in the destination currency | Format: Decimal Example: |
Base_Currency_to_Destination_Currency_Exchange_Rate Specifies the currency exchange rate applied to this transaction when Visa converts the source amount to the transaction amount in the destination currency | Format: Decimal Example: |
Optional_Issuer_ISA_Amount This ISO-defined field can be used for any charge type or any fee applied to a transaction. Currently, Visa uses this field to carry optional International Service Assessment (ISA) data for issuers in the LAC region | Format: Decimal (can be blank or contain zero) Example: |
Product_ID Product identifier code | Format: Alphanumeric Example: |
CVV2_Result_Code Card Verification Value 2 (CVV2) is the verification result for card-not-present transactions and also for card-present CVV2 verification-only requests | Format: Alphanumeric (can be blank or contain whitespace) Example: |
Sample report file
Link to the Visa v3.0 Sample Presentment report
Visa v4.0
Key changesBelow are the notable differences between v3.0 and v4.0:
- Addition of a new field
PY__Transaction_Type.
Below are the data fields and format of the Visa v4.0 Presentment report.
Report Field | Explanation |
|---|---|
PY__RID_Settlement PY__RID_Authorization PY__Account_ID PY__Account_Currency PY__Token PY__Account_External_Reference PY__Transaction_ID PY__Network PY__Created_Date PY__Matched_Status PY__Product_ID PY__Product_Name PY__Settlement_Note PY__Transaction_Type | (Refer to the section Paymentology-Specific Data Fields ) |
Transaction_Code Two digit code determining the type of transaction | Format: Numeric Possible Values:
Example: |
Transaction_Code_Qualifier | Possible Values:
Example: |
Usage_Code Indicates whether this is the first presentment or the second. | Format: Numeric Possible Values:
Example: |
Acquirer_Reference_Number A 23-digit identification number assigned by the acquirer. | Format: Numeric Example: |
Acquirer_Business_ID Contains the Visa-assigned business ID of the acquirer that signed the merchant for processing purchase or mail/phone order transactions. In this case, the acquirer is referred to as the Merchant Sponsor. The entry must be numeric | Format: Numeric (can be blank or contain zero) Example: |
Purchase_Date Date the purchase transaction was made. | Format: DateTime
Pattern: Example: |
Destination_Amount Identifies the submitted transaction amount in the currency that is appropriate to the destination endpoint.It is the billing amount. | Format: Decimal Example: |
Destination_Currency_Code The currency type presented to the member on incoming transactions.It is the billing currency | Format: Numeric Example: |
Source_Amount The purchase value in transaction currency | Format: Decimal Example: |
Source_Currency_Code Currency code used in the transaction | Format: Numeric Example: |
Merchant_Name Name of the merchant in the original transaction | Format: Alphanumeric Example: |
Merchant_City Merchant city, telephone number, email address, or URL | Format: Alphabetic Example: |
Merchant_Country_Code Code indicating country where the Visa transaction occurred, regardless of the location of entry to the system | Format: Alphabetic Example: |
Merchant_Category_Code Indicates merchant’s type of business product or service | Format: Numeric Example: |
Merchant_ZIP_Code Postal code of the merchant where the transaction took place | Format: Numeric Example: |
Merchant_State_Province_Code If the Merchant Country Code is US or CA, this field will contain a valid U.S. State Code or Canadian Province Code, respectively. Otherwise, it must contain spaces. | Format: Alphabetic (can be blank or contain whitespace) Example: |
Settlement_Flag Indicates the service used for settlement | Format: Numeric Possible Values:
Example: |
Authorization_Characteristics_Indicator Code used by the acquirer to request CPS qualification | Format: Alphanumeric (can be blank or contain whitespace) Possible Values:
Example: |
Authorization_Code Code that an issuer, its authorizing processor, or Stand-In Processing (STIP) provides to indicate approval of a transaction | Format: Alphanumeric Example: |
Cardholder_ID_Method Indicates method used to identify cardholder (e.g., signature, Personal Identification Number (PIN), etc.). | Format: Alphanumeric (can be blank or contain whitespace) Possible Values:
|
POS_Entry_Mode A V.I.P. System field indicating the method by which a point-of-transaction terminal obtains and transmits the cardholder information necessary to complete a Transaction. | Format: Alphanumeric (can be blank or contain whitespace) Possible Values:
Example: |
Central_Processing_Date The date that BASE II processes this transaction or item. Note: You should use this date for your financial reconciliation with the scheme. | Format: DateTime
Pattern: Example: |
Member_Message_Text This field is used to send text messages | Format: String (can be empty or contain whitespace) Example: |
Card_Acceptor_ID Code that identifies the card acceptor operating the POS terminal. | Format: Alphanumeric Example: |
Terminal_ID Code that identifies the card acceptor terminal or ATM. | Format: Alphanumeric Example: |
Interface_Trace_Number Trace Number from the dispute or dispute response. | Reserved field. |
AVS_Response_Code Contains the response to an Address Verification Service (AVS) request, indicating matches or discrepancies between addresses and ZIP codes. | Format: Alphanumeric (can be blank or contain whitespace) Example: |
Authorization_Source_Code Indicates whether authorization was obtained and the source of the authorization. | Format: Alphanumeric (can be blank or contain whitespace) Possible Values:
Example: |
Transaction_Code_Qualifier__TCR3 TCQ for the Base II TCR3 record | Format: Numeric Possible Values:
Example: |
Transaction_Component_Sequence_Number__TCR3 TCS Number for the Base II TCR3 record | Format: Numeric Possible Values:
|
Fast_Funds_Indicator VIC will return the transaction if any non-space value is present on an Original Transaction. | Format: Alphanumeric (can be blank or contain whitespace) |
Business_Format_Code Code indicating the type of business that is applicable to this transaction. | Format: Alphanumeric (can be blank or contain whitespace) Example: |
Business_Application_ID This field provides additional information regarding the usage and application of the transaction | Format: Alphanumeric (can be blank or contain whitespace) Example: |
Source_of_Funds | Format: Numeric (can be blank or contain whitespace) Possible Values:
|
Payment_Reversal_Reason_Code | Format: Numeric (can be blank or contain whitespace) Possible Values:
|
Sender_Reference_Number This field will contain a transaction reference number that is provided by the originator and can be used to uniquely identify the sender | Format: Alphanumeric (can be blank or contain whitespace) Example: |
Sender_Account_Number This field will contain the sender's card number or bank account number from which the funds are to be taken. | Format: Alphanumeric (can be blank or contain whitespace) |
Sender_Name This field will contain the name of the person or entity for the account from which funds are to be taken. | Format: Alphanumeric (can be blank or contain whitespace) |
Sender_Address This field will contain the address of the person or entity for the account from which funds are to be taken | Format: Alphanumeric (can be blank or contain whitespace) |
Sender_City This field will contain the city of the person or entity for the account from which funds are to be taken. | Format: Alphanumeric (can be blank or contain whitespace) |
Sender_State This field will contain the geographical state or province of the person or entity for the account from which funds are to be taken. | Format: Alphanumeric (can be blank or contain whitespace) |
Sender_Country This field will contain the country of the person or entity for the account from which funds are to be taken | Format: Alphanumeric (can be blank or contain whitespace) |
Transaction_Code_Qualifier__TCR5 TCQ for the Base II TCR5 record | Format: Numeric Possible Values:
Example: |
Transaction_Component_Sequence_Number__TCR5 TCS Number for the Base II TCR5 record | Format: Numeric Possible Values:
|
Transaction_Identifier A unique value that Visa assigns to each transaction and returns to the acquirer in the authorization response. | Format: Numeric Example: |
Authorized_Amount Amount the issuer originally authorized. The entry must be numeric. For CPS original draft transactions and their reversals, this entry may not be zeros. CPS credit vouchers and their reversals must contain zeros in this field. | Format: Numeric Example: |
Authorization_Currency_Code Currency code of the authorized source amount | Format: Numeric Example: |
Interchange_Fee_Amount Specifies the interchange fee amount (in the settlement currency of the member) calculated by Visa for this transaction | Format: Decimal Example: |
Interchange_Fee_Sign Specifies if the interchange fee amount is a credit or a debit for the receiving member. | Format: Alphabetic Possible Values:
|
Source_Currency_to_Base_Currency_Exchange_Rate Specifies the currency exchange rate applied to this transaction when Visa converts the source amount to the transaction amount in the destination currency | Format: Decimal Example: |
Base_Currency_to_Destination_Currency_Exchange_Rate Specifies the currency exchange rate applied to this transaction when Visa converts the source amount to the transaction amount in the destination currency | Format: Decimal Example: |
Optional_Issuer_ISA_Amount This ISO-defined field can be used for any charge type or any fee applied to a transaction. Currently, Visa uses this field to carry optional International Service Assessment (ISA) data for issuers in the LAC region | Format: Decimal (can be blank or contain zero) Example: |
Product_ID Product identifier code | Format: Alphanumeric Example: |
CVV2_Result_Code Card Verification Value 2 (CVV2) is the verification result for card-not-present transactions and also for card-present CVV2 verification-only requests | Format: Alphanumeric (can be blank or contain whitespace) Example: |
Sample report file
Updated 2 months ago
