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:

  1. 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.
  2. 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).
  3. Report Specifications Details the structure of the report itself, covering two main categories of fields:
    1. 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.
    2. 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:

PartDescription
<ClientName>Name or short code identifying the client
PresentmentsFixed 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
.csvFile 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

AttributeDescription
FrequencyDaily
Delivery TimeTypically available before the end of day (configurable)
Delivery MethodDelivered via SFTP
File LocationStored in the client-specific folder on the SFTP server
File FormatCSV (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

1234567890

Decimal

Number with a decimal place

250.00

Alphabetic

Letters only

A

Alphanumeric

Letters and digits only

A1B2C3

String

Free text; digits, spaces and symbols

Transaction Failed

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: YYYY-MM-DD HH:mm:ss

2025-12-30 18:00:00

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:

  1. 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.
  2. 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.
  3. 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.
  4. Validate data formats Refer to the Data Format Conventions section to ensure correct parsing (e.g., DateTime format, decimal precision).
  5. Use field mappings for cross-report linking Fields like PY__Transaction_ID, PY__Token, and PY__RID_Authorization can 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: 12345000000005

PY__RID_Authorization

Unique ID for authorisation transaction

Note: This may have value 0 if no Authorisation involved in the transaction

Format: Numeric

Example: 43212345

PY__Account_ID

Account identifier

Format: Numeric

Example: 43212345

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: 784

PY__Token

Public token generated by Paymentology to replace PAN

Format: Numeric

Example: 43212345

PY__Account_External_Reference

Account external reference assigned by Paymentology

Format: Numeric

Example: 433656625

PY__File_ID

Unique file ID assigned by Paymentology

Format: Numeric

Example: 12300

PY__Transaction_ID

Unique transaction thread identifier generated and managed by Paymentology.

Format: Numeric

Example: 2200123456789000000

PY__Network

Indicates the card network provider

Format: Alphabetic

Possible Values:

M - Mastercard

VISA - Visa

MADA - Mada

Example: VISA

PY__MTID

Message Transaction Identifier

Note: This field is not applicable for Visa Presentments report.

Format: Numeric

Example: 1240

PY__Created_Date

Indicates the timestamp when Paymentology processed the file.

Format: DateTime

Pattern: YYYY-MM-DD HH:MM:SS (24-hour format)

Example: 2025-01-01 12:00:00

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:

1 - Matching Step 1

2 - Matching Step 2

3 - Matching Step 3

4 - Matching Step 4

9 - Matching Step 5

Example: 1

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:

-1 - Debits

0 - No Financial Impact

1 - Credit

Example: -1

PY__Product_ID

Paymentology card product identifier

Format: Numeric

Example: 412

PY__Product_Name

Paymentology card product name

Format: String

Example: Visa Platinum

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: ; match (1) on tok+de38

PY__Transaction_Type

Identifies the additional transaction type

Format: Alphabetic

Possible Values:

POS

ECOM

UNKNOWN

Example: POS

Alignment to FAST and other reports

Field

FAST

Report

Usage

PY__RID_Authorization

  • RID in FAST authorization messages
  • ADD_REF_RID in FAST V3 clearing & settlement messages

Match transaction message records

PY__Token

  • "DE2" in FAST authorization messages
  • "2" (Mastercard) or "Account Number" (Visa) in both FAST authorization and FAST V3 clearing and settlement messages.

Token matching across reports and messages

PY__Transaction_ID

TID in both FAST authorization and FAST V3 clearing & settlement messages

Match transaction threads

PY__RID_Settlement

RID in FAST V3 clearing & settlement messages

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: 20

Cardholder_from_Account_Type_Code

Cardholder ‘from’ Account type

Format: Numeric

Example: 00

Cardholder_To_Account_Type_Code

Cardholder ‘to’ Account type

Format: Numeric

Example: 00

Transaction_Amount

It carries the amount in the transaction currency.

Format: Decimal

Example: -200.00

Billing_Amount

It carries the cardholder billing amount in the cardholder billing currency. Applicable for cross currency transactions

Format: Numeric

Example: -200.00

Conversion_Rate_Billing

It carries the conversion rate of billing Amount. Applicable for cross currency transactions

Format: Numeric

Example: 12.30111

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: YYYY-MM-DD HH:MM:SS (24-hour format)

Example: 1972-01-10 17:43:09

POS_Entry_Mode

This element is used to indicate the method used to enter the account number.

Format: Numeric

Example: 810

Function_Code

This element indicates the purpose of the different types of clearing messages.

Format: Numeric

Possible Values:

266 - Void

200 - Presentment(With Auth)

260 - Offline Presentment (Without Auth)

263 - Offline Refund (Without Auth)

262 - Refund

269 - Refund Reversal

420 - Reversal of Presentment (With Auth)

Example: 260

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: 784197197

Retrieval_Reference_Number

It is used to identify and track all messages related to a given cardholder transaction.

Format: Numeric

Example: 529010020322

Approval_Code

This element contains the code allotted to an authorized transaction by an issuer/authorizing entity.

Format: Alphanumeric

Example: 622911

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: A0000001

Card_Acceptor_ID_Code

This element uniquely identifies the card acceptor id in an acquiring system.

Format: Numeric

Example: 123456789012345

Card_Acceptor_Name

The field carries the card acceptor name.

Format: Alphanumeric

Example: FIME TEST eComm

Card_Acceptor_City

The city of the card acceptor.

Format: Alphanumeric

Examples: Abu Dhabi

Card_Acceptor_State_Code

The data element will carry the state code of the card acceptor.

Format: Alphabetic

Example: AZ

Card_Acceptor_Country_Code

The country code of the card acceptor. Country code should be ISO standard.

Format: Alphabetic

Example: AE

Message_Reversal_Indicator

Identifies whether it is the original message or the reversal of the original message.

Format: Numeric

Possible Values:

1 - Original Message

-1- Reversal of the original

Example: 1

Network_File_Reference

This field will carry the unique file name.

Format: Numeric

Example: 0027844098872529000

Reconciliation_Date

This field contains the date on which the transaction is processed for clearing.

Format: DateTime

Pattern: YYYY-MM-DD

Example: 2025-10-18

Currency_Code_Transaction

This element defines the currency code of the transaction

Format: Numeric

Example: 784

Currency_Code_Billing

This element defines the currency code of the amount carried in Amount, Cardholder Billing.

Format: Numeric

Example: 784

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: 784

Transaction_Destination_Institution_ID

It carries the identification of transaction destination institution.

Format: Numeric

Example: 784409887

Transaction_Originator_Institution_ID

It carries the identification of transaction originator institution.

Format: Numeric

Example: 784409887

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.

Note

All new clients should integrate with the latest report version

Mastercard v1.0

❗️

Important

This 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: 20

DE3_2__Cardholder_from_Account_Type_Code

Position 3-4 = Cardholder ‘from’ Account type

Format: Numeric

Example: 10

DE3_3__Cardholder_To_Account_Type_Code

Position 5-6 = Cardholder ‘to’ Account type

Format: Numeric

Example: 00

DE4__Transaction_Amount

Local amount with the sign, indicating the net direction of funds flow. Currency provided in DE49

Format: Decimal

Example: -250.00

DE5__Reconciliation_Amount

Settlement amount with the sign, indicating the net direction of funds flow. Currency provided in DE50

Format: Decimal

Example: -250.00

DE6__Billing_Amount

Cardholder Billing amount with the sign, indicating the net direction of funds flow. Currency provided in DE51

Format: Decimal

Example: -250.00

DE9__Conversion_Rate_Reconciliation

Conversion rate to Reconciliation/Settlement currency

Format: Decimal

Example: 2.651027

DE10__Conversion_Rate_Billing

Conversion rate to Cardholder billing currency

Format: Decimal

Example: 1.1142

DE12__Transaction_Date_Time

Date/time of local original spend.

Note: Mastercard frequently provide 00:00:00 as time element.

Format: DateTime

Pattern: 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:
0 - Card not present
1 - Card present
9 - Unknown

Example: 1

DE22_7__Card_Data_Input_Mode

Indicates the method used for PAN entry to initiate a transaction

Format: Alphanumeric

Possible Values:
0
1
2
6
7

(Refer to the Mastercard IPM Clearing Specifications for full list of supported values)

Example: S

DE23__Card_Sequence_Number

Distinguishes among separate cards that have the same PAN

Format: Numeric

Example: 000

DE24__Function_Code

Indicates the specific purpose for a message

Format: Numeric

Example: 200

DE25__Message_Reason_Code

Provides the message receiver with the reason for sending the message

Format: Numeric

Example: 1401

DE26__Merchant_Category_Code

Classifies the type of business applicable to the acceptor

Format: Numeric

Example: 5411

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: -150.20

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: 0

DE31__Acquirer_Reference_Data

Acquirer Reference Data

Format: Numeric

Example: 54321222123456780000000

DE32__Acquiring_Institution_ID_Code

Identifies the transaction acquirer

Format: Numeric

Example: 123456

DE33__Forwarding_Institution_ID_Code

Identifies a message’s forwarding institution

Format: Numeric

Example: 123456

DE37__Retrieval_Reference_Number

It is a transaction information document reference number the acceptor’s or designated agent’s system supplies.

Format: Numeric

Example: 326548752162

DE38__Approval_Code

It is a code the authorizing institution assigns indicating approval

Format: Numeric

Example: 190654

DE40__Service_Code

Service Code

Format: Numeric

Example: 0

DE41__Card_Acceptor_Terminal_ID

Card Acceptor Terminal Identification

Format: Numeric

Example: 40551234

DE42__Card_Acceptor_ID_Code

Card Acceptor ID Code

Format: Numeric

Example: 300-9876654321

DE43_1__Card_Acceptor_Name

Card Acceptor Name (22 long)

Format: Alphanumeric

Example: GULF AIR0987654321

DE43_2__Card_Acceptor_Street_Address

Card Acceptor Street address (48 long)

Format: Alphanumeric

Example: P.O. Box

DE43_3__Card_Acceptor_City

Card Acceptor City (13 long)

Format: Alphabetic

Example: Bahrain

DE43_4__Card_Acceptor_Zip_Code

Post/zip code (10 long)

Format: Alphanumeric

Example: W127GE

DE43_5__Card_Acceptor_State_Code

State or province (3 long)

Format: Alphabetic

Example: BHR

DE43_6__Card_Acceptor_Country_Code

Country Code (3 long)

Format: Alphabetic

Example: BHR

DE48_0002__GCMS_Product_Identifier

GCMS Product Identifier

Format: Alphabetic

Example: MRW

DE48_0003__Licensed_Product_Identifier

Licensed Product Identifier

Format: Alphabetic

Example: MRW

DE48_0023__Terminal_Type

Terminal Type, identifies the type of terminal used at the point of interaction

Format: Alphabetic

Example: MAN

DE48_0025_1__Message_Reversal_Indicator

Identifies whether it is the original message or the reversal of the original message.

Format: Numeric

Possible Values:
1 - Original message
-1 - Reversal of the original

Example: 1

DE48_0105__Network_File_Reference

File ID from the network

Format: Numeric

Example: 123032100000012000000

DE48_0158_1__Card_Program_Identifier

Identifies the card program or financial network to which a transaction belongs

Format: Alphabetic

Example: MCC

DE48_0158_2__Business_Service_Arrangement_Type_Code

Identifies the business relationship between the transaction’s participants.

Format: Numeric

Possible Values:
1 - Interregional
2 - Intraregional
3 - Intercountry
4 - Intracountry
8 - Member-to-member

Example: 2

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: 060001

DE48_0158_4__Interchange_Rate_Designaor

Indicates the interchange rate and editing rules applied to the transaction

Format: Numeric

Example: 61

DE48_0158_5__Central_Site_Business_Date

Identifies the official business processing date when the business service reconciles a transaction

Format: DateTime
Pattern: DD/MM/YYYY

Example: 24/09/2023

DE48_0158_6__Business_Cycle

Identifies a reconciliation period in a Business Date

Format: Numeric

Example: 02

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: 0

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: MAB

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:
N
V
1
2

Example: N

DE48_0158_10__Special_Conditions_Indicator

Indicate whether an adjustment was included in the Fee amount

Format: Alphanumeric

Possible Values:
N
Y
2
3

Example: N

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:
Y
N

Example: N

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:
N
B
M
P

Example: N

DE48_0158_13__Rate_Indicator

Indicates the rate applied by GCMS to the transaction

Format: Alphabetic

Possible Values:
B
C
E
F
P

(Refer to the Mastercard IPM Clearing Specifications for full list of supported values)

Example: B

DE48_0158_14__Masterpass_Incentive_Indicator

Identifies the transaction as having received the Masterpass-Enabled Merchant Incentive.

Format: Alphabetic

Possible Values:
Y
N

Example: N

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:
1 - Regional
3 - Intracurrency

Example: 1

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: YYYY-MM-DD

Example: 2023-09-23

DE48_159_7__Reconciliation_Cycle

Identifies a reconciliation period in a reconciliation date.

Format: Numeric

Possible Values:
01 - Cycle 1
02 - Cycle 2
03 - Cycle 3
04 - Cycle 4
05 - Cycle 5
06 - Cycle 6

Example: 01

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: YYYY-MM-DD

Example: 2023-09-23

DE48_159_9__Settlement_Cycle

Identifies a settlement period in a settlement date

Format: Numeric

Possible Values:
01 - Cycle 1

Example: 01

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:
Y - Qualifies as a cross-border transaction
N - Does not qualify as a cross-border transaction

Example: Y

DE48_0177_2__Currency_Indicator

Identifies whether the transaction was submitted to Mastercard in the local currency of the merchant.

Format: Alphabetic

Possible Values:
- Does not qualify as a cross-border transaction
Y - Transaction submitted in the local currency of the merchant
N - Transaction not submitted in the local currency of the merchant

Example: N

DE49__Currency_Code_Transaction

Currency of transaction (local currency)

Format: Numeric

Example: 048

DE50__Currency_Code_Reconciliation

Currency of reconciliation/Settlement

Format: Numeric

Example: 840

DE51__Currency_Code_Billing

Currency of Cardholder Billing

Format: Numeric

Example: 048

DE54_2__Additional_Amount_Type

Other Amounts – e.g. cashback portions in cash back transactions. Surcharges also appear here

Format: Numeric

Example: 0

DE54_3__Additional_Amount_Currency_Code

Indicates currency of the Surcharge amount

Format: Numeric

Example: 48

DE54_4__Additional_Amount_Sign

Additional Amount Sign (D for debit and C for Credit)

Format: Alphabetic

Example: D

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: 0

DE63__Transaction_Life_Cycle_ID

Transaction Life Cycle ID

Format: Alphanumeric

Example: MNO1P2QRS0123

DE71__Message_Number

Message Number – identifies the message within the T112 Mastercard file

Format: Numeric

Example: 54

DE72__Data_Record

Used in Fee type messages to provide description of the fee

Format: String

Example: Late Payment Penalty

DE73__Action_Date

In Fee Collection messages, this data element identifies a reference date related to the Fee.

Format: DateTime
Pattern: YYYY-MM-DD

Example: 2023-09-23

DE94__Transaction_Originator_Institution_ID

Transaction Originator Institution ID, identifies the transaction originator institution

Format: Numeric

10456

DE100__Receiving_Institution_ID

Receiving Member ID (Paymentology processor id)

Format: Numeric

12345

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: 0

Sample report file

Link to the MC v1.0 Sample Presentment report

Mastercard v2.0

📓

Key changes

Below 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: 20

DE3_2__Cardholder_from_Account_Type_Code

Position 3-4 = Cardholder ‘from’ Account type

Format: Numeric

Example: 10

DE3_3__Cardholder_To_Account_Type_Code

Position 5-6 = Cardholder ‘to’ Account type

Format: Numeric

Example: 00

DE4__Transaction_Amount

Local amount with the sign, indicating the net direction of funds flow. Currency provided in DE49

Format: Decimal

Example: -250.00

DE5__Reconciliation_Amount

Settlement amount with the sign, indicating the net direction of funds flow. Currency provided in DE50

Format: Decimal

Example: -250.00

DE6__Billing_Amount

Cardholder Billing amount with the sign, indicating the net direction of funds flow. Currency provided in DE51

Format: Decimal

Example: -250.00

DE9__Conversion_Rate_Reconciliation

Conversion rate to Reconciliation/Settlement currency

Format: Decimal

Example: 2.651027

DE10__Conversion_Rate_Billing

Conversion rate to Cardholder billing currency

Format: Decimal

Example: 1.1142

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:
0 - Card not present
1 - Card present
9 - Unknown

Example: 1

DE22_7__Card_Data_Input_Mode

Indicates the method used for PAN entry to initiate a transaction

Format: Alphanumeric

Possible Values:
0
1
2
6
7

(Refer to the Mastercard IPM Clearing Specifications for full list of supported values)

Example: 1

DE23__Card_Sequence_Number

Distinguishes among separate cards that have the same PAN

Format: Numeric

Example: 000

DE24__Function_Code

Indicates the specific purpose for a message

Format: Numeric

Example: 200

DE25__Message_Reason_Code

Provides the message receiver with the reason for sending the message

Format: Numeric

Example: 1401

DE26__Merchant_Category_Code

Classifies the type of business applicable to the acceptor

Format: Numeric

Example: 5411

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: -150.22

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: 0

DE31__Acquirer_Reference_Data

Acquirer Reference Data (See MC IPM Clearing Formats document)

Format: Numeric

Example: 54321222123456780000000

DE32__Acquiring_Institution_ID_Code

Identifies the transaction acquirer

Format: Numeric

Example: 123456

DE33__Forwarding_Institution_ID_Code

Identifies a message’s forwarding institution

Format: Numeric
Example: 123456

DE37__Retrieval_Reference_Number

It is a transaction information document reference number the acceptor’s or designated agent’s system supplies.

Format: Numeric

Example: 326548752162

DE38__Approval_Code

It is a code the authorizing institution assigns indicating approval

Format: Numeric

Example: 190654

DE40__Service_Code

Service Code

Format: Numeric

Example: 0

DE41__Card_Acceptor_Terminal_ID

Card Acceptor Terminal Identification

Format: Numeric

Example: 40551234

DE42__Card_Acceptor_ID_Code

Card Acceptor ID Code

Format: Numeric

Example: 300-9876654321

DE43_1__Card_Acceptor_Name

Card Acceptor Name (22 long)

Format: Alphanumeric

Example: GULF AIR0987654321

DE43_2__Card_Acceptor_Street_Address

Card Acceptor Street address (48 long)

Format: Alphanumeric

Example: P.O. Box

DE43_3__Card_Acceptor_City

Card Acceptor City (13 long)

Format: Alphabetic

Example: Bahrain

DE43_4__Card_Acceptor_Zip_Code

Post/zip code (10 long)

Format: Alphanumeric

Example: W127GE

DE43_5__Card_Acceptor_State_Code

State or province (3 long)

Format: Alphabetic

Example: BHR

DE43_6__Card_Acceptor_Country_Code

Country Code (3 long)

Format: Alphabetic

Example: BHR

DE48_0002__GCMS_Product_Identifier

GCMS Product Identifier

Format: Alphabetic

Example: MRW

DE48_0003__Licensed_Product_Identifier

Licensed Product Identifier

Format: Alphabetic

Example: MRW

DE48_0023__Terminal_Type

Terminal Type, identifies the type of terminal used at the point of interaction

Format: Alphabetic

Example: MAN

DE48_0025_1__Message_Reversal_Indicator

Identifies whether it is the original message or the reversal of the original message.

Format: Numeric

Possible Values:
1 - Original message
-1 - Reversal of the original

Example: 1

DE48_0105__Network_File_Reference

File ID from the network

Format: Numeric

Example: 123032100000012000000

DE48_0158_1__Card_Program_Identifier

Identifies the card program or financial network to which a transaction belongs

Format: Alphabetic

Example: MCC

DE48_0158_2__Business_Service_Arrangement_Type_Code

Identifies the business relationship between the transaction’s participants.

Format: Numeric

Possible Values:
1 - Interregional
2 - Intraregional
3 - Intercountry
4 - Intracountry
8 - Member-to-member

Example: 2

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: 60001

DE48_0158_4__Interchange_Rate_Designaor

Indicates the interchange rate and editing rules applied to the transaction

Format: Numeric

Example: 61

DE48_0158_5__Central_Site_Business_Date

Identifies the official business processing date when the business service reconciles a transaction

Format: DateTime
Pattern: DD/MM/YYYY

Example: 24/09/2023

DE48_0158_6__Business_Cycle

Identifies a reconciliation period in a Business Date

Format: Numeric

Example: 02

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: 0

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: MAB

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:
N
V
1
2

Example: N

DE48_0158_10__Special_Conditions_Indicator

Indicates whether an adjustment was included in the Fee amount

Format: Alphanumeric

Possible Values:
N
Y
2
3

Example: N

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:
Y
N

Example: N

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:
N
B
M
P

Example: N

DE48_0158_13__Rate_Indicator

Indicates the rate applied by GCMS to the transaction

Format: Alphanumeric

Possible Values:
B
C
E
F
P

(Refer to the Mastercard IPM Clearing Specifications for full list of supported values)

Example: C

DE48_0158_14__Masterpass_Incentive_Indicator

Identifies the transaction as having received the Masterpass-Enabled Merchant Incentive.

Format: Alphabetic

Possible Values:
Y
N

Example: N

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:
1 - Regional
3 - Intracurrency

Example: 1

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: YYYY-MM-DD

Example: 2023-09-23

DE48_159_7__Reconciliation_Cycle

Identifies a reconciliation period in a reconciliation date.

Format: Numeric

Possible Values:
01 - Cycle 1
02 - Cycle 2
03 - Cycle 3
04 - Cycle 4
05 - Cycle 5
06 - Cycle 6

Example: 01

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: YYYY-MM-DD

Example: 2023-09-23

DE48_159_9__Settlement_Cycle

Identifies a settlement period in a settlement date

Format: Numeric

Possible Values:
01 - Cycle 1

Example: 01

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:
Y - Qualifies as a cross-border transaction
N - Does not qualify as a cross-border transaction

Example: Y

DE48_0177_2__Currency_Indicator

Identifies whether the transaction was submitted to Mastercard in the local currency of the merchant.

Format: Alphabetic

Possible Values:
- Does not qualify as a cross-border transaction
Y - Transaction submitted in the local currency of the merchant
N - Transaction not submitted in the local currency of the merchant

Example: N

DE49__Currency_Code_Transaction

Currency of transaction (local currency)

Format: Numeric

Example: 048

DE50__Currency_Code_Reconciliation

Currency of reconciliation/Settlement

Format: Numeric

Example: 840

DE51__Currency_Code_Billing

Currency of Cardholder Billing

Format: Numeric

Example: 048

DE54_2__Additional_Amount_Type

Other Amounts – e.g. cashback portions in cash back transactions. Surcharges also appear here

Format: Numeric

Example: 0

DE54_3__Additional_Amount_Currency_Code

Indicates currency of the Surcharge amount

Format: Numeric

Example: 48

DE54_4__Additional_Amount_Sign

Additional Amount Sign (D for debit and C for Credit)

Format: Alphabetic

Example: D

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: 0

DE63__Transaction_Life_Cycle_ID

Transaction Life Cycle ID

Format: Alphanumeric

Example: MNO1P2QRS0123

DE71__Message_Number

Message Number – identifies the message within the T112 Mastercard file

Format: Numeric

Example: 54

DE72__Data_Record

Used in Fee type messages to provide description of the fee

Format: String

Example: Late Payment Penalty

DE73__Action_Date

In Fee Collection messages, this data element identifies a reference date related to the Fee.

Format: DateTime
Pattern: YYYY-MM-DD

Example: 2023-09-23

DE94__Transaction_Originator_Institution_ID

Transaction Originator Institution ID, identifies the transaction originator institution

Format: Numeric

10456

DE100__Receiving_Institution_ID

Receiving Member ID (Paymentology processor id)

Format: Numeric

12345

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: 0

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: 20

DE3_2__Cardholder_from_Account_Type_Code

Position 3-4 = Cardholder ‘from’ Account type

Format: Numeric

Example: 10

DE3_3__Cardholder_To_Account_Type_Code

Position 5-6 = Cardholder ‘to’ Account type

Format: Numeric

Example: 00

DE4__Transaction_Amount

Local amount with the sign, indicating the net direction of funds flow. Currency provided in DE49

Format: Decimal

Example: -250.00

DE5__Reconciliation_Amount

Settlement amount with the sign, indicating the net direction of funds flow. Currency provided in DE50

Format: Decimal

Example: -250.00

DE6__Billing_Amount

Cardholder Billing amount with the sign, indicating the net direction of funds flow. Currency provided in DE51

Format: Decimal

Example: -250.00

DE9__Conversion_Rate_Reconciliation

Conversion rate to Reconciliation/Settlement currency

Format: Decimal

Example: 2.651027

DE10__Conversion_Rate_Billing

Conversion rate to Cardholder billing currency

Format: Decimal

Example: 1.1142

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

DE17__Capture_Date

This data element contains the month and day when the transaction data was processed (acquired) by the acquirer.

Format: DateTime Pattern: MMDD

Example: 1219

DE22_6__Card_Present_Data

Indicates if the card is present at the point of service

Format: Numeric

Possible Values: 0 - Card not present 1 - Card present 9 - Unknown

Example: 1

DE22_7__Card_Data_Input_Mode

Indicates the method used for PAN entry to initiate a transaction

Format: Alphabetic

Possible Values: M - C - S - 1 -

Example: M

DE23__Card_Sequence_Number

Distinguishes among separate cards that have the same PAN

Format: Numeric

Example: 000

DE24__Function_Code

Indicates the specific purpose for a message

Format: Numeric

Example: 200

DE25__Message_Reason_Code

Provides the message receiver with the reason for sending the message

Format: Numeric

Example: 1401

DE26__Merchant_Category_Code

Classifies the type of business applicable to the acceptor

Format: Numeric

Example: 5411

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: -150.23

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: 0

DE31__Acquirer_Reference_Data

Acquirer Reference Data

Format: Numeric

Example: 54321222123456780000000

DE32__Acquiring_Institution_ID_Code

Identifies the transaction acquirer

Format: Numeric

Example: 123456

DE33__Forwarding_Institution_ID_Code

Identifies a message’s forwarding institution

Format: Numeric Example: 123456

DE37__Retrieval_Reference_Number

It is a transaction information document reference number the acceptor’s or designated agent’s system supplies.

Format: Numeric

Example: 326548752162

DE38__Approval_Code

It is a code the authorizing institution assigns indicating approval

Format: Numeric

Example: 190654

DE40__Service_Code

Service Code

Format: Numeric

Example: 0

DE41__Card_Acceptor_Terminal_ID

Card Acceptor Terminal Identification

Format: Numeric

Example: 40551234

DE42__Card_Acceptor_ID_Code

Card Acceptor ID Code

Format: Numeric

Example: 300-9876654321

DE43_1__Card_Acceptor_Name

Card Acceptor Name (22 long)

Format: Alphanumeric

Example: GULF AIR0987654321

DE43_2__Card_Acceptor_Street_Address

Card Acceptor Street address (48 long)

Format: Alphanumeric

Example: P.O. Box

DE43_3__Card_Acceptor_City

Card Acceptor City (13 long)

Format: Alphabetic

Example: Bahrain

DE43_4__Card_Acceptor_Zip_Code

Post/zip code (10 long)

Format: Alphanumeric

Example: W127GE

DE43_5__Card_Acceptor_State_Code

State or province (3 long)

Format: Alphabetic

Example: BHR

DE43_6__Card_Acceptor_Country_Code

Country Code (3 long)

Format: Alphabetic

Example: BHR

DE48_0002__GCMS_Product_Identifier

GCMS Product Identifier, e.g. MRW is Prepaid Mastercard Business Card (Non-U.S.)

Format: Alphabetic

Example: MRW

DE48_0003__Licensed_Product_Identifier

Licensed Product Identifier

Format: Alphabetic

Example: MRW

DE48_0023__Terminal_Type

Terminal Type, identifies the type of terminal used at the point of interaction

Format: Alphabetic

Example: MAN

DE48_0025_1__Message_Reversal_Indicator

Identifies whether it is the original message or the reversal of the original message.

Format: Numeric

Possible Values: 1 - Original message -1 - Reversal of the original

Example: 1

DE48_0105__Network_File_Reference

File ID from the network

Format: Numeric

Example: 123032100000012000000

DE48_0158_1__Card_Program_Identifier

Identifies the card program or financial network to which a transaction belongs

Format: Alphabetic

Example: MCC

DE48_0158_2__Business_Service_Arrangement_Type_Code

Identifies the business relationship between the transaction’s participants

Format: Numeric

Possible Values: 1 - Interregional 2 - Intraregional 3 - Intercountry 4 - Intracountry 8 - Member-to-member

Example: 2

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: 60001

DE48_0158_4__Interchange_Rate_Designaor

Indicates the interchange rate and editing rules applied to the transaction

Format: Numeric

Example: 61

DE48_0158_5__Central_Site_Business_Date

Identifies the official business processing date when the business service reconciles a transaction

Format: DateTime Pattern: DD/MM/YYYY

Example: 24/09/2023

DE48_0158_6__Business_Cycle

Identifies a reconciliation period in a Business Date

Format: Numeric

Example: 02

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: 0

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: MAB

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: N V 1 2

Example: N

DE48_0158_10__Special_Conditions_Indicator

Indicates whether an adjustment was included in the Fee amount

Format: Alphanumeric

Possible Values: N Y 2 3

Example: N

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: Y N

Example: N

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: N B M P

Example: N

DE48_0158_13__Rate_Indicator

Indicates the rate applied by GCMS to the transaction

Format: Alphabetic

Possible Values: B C E F P

(Refer to the Mastercard IPM Clearing Specifications for full list of supported values)

Example: B

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: N

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: 1 - Regional 9 - Intracurrency

Example: 1

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: YYYY-MM-DD

Example: 2023-09-23

DE48_159_7__Reconciliation_Cycle

Identifies a reconciliation period in a reconciliation date.

Format: Numeric

Possible Values: 01 - Cycle 1 02 - Cycle 2 03 - Cycle 3 04 - Cycle 4 05 - Cycle 5 06 - Cycle 6

Example: 01

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: YYYY-MM-DD

Example: 2023-09-23

DE48_159_9__Settlement_Cycle

Identifies a settlement period in a settlement date

Format: Numeric

Possible Values: 01 - Cycle 1

Example: 01

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: Y - Qualifies as a cross-border transaction N - Does not qualify as a cross-border transaction

Example: Y

DE48_0177_2__Currency_Indicator

Identifies whether the transaction was submitted to Mastercard in the local currency of the merchant.

Format: Alphabetic

Possible Values: - Does not qualify as a cross-border transaction Y - Transaction submitted in the local currency of the merchant N - Transaction not submitted in the local currency of the merchant

Example: N

DE49__Currency_Code_Transaction

Currency of transaction (local currency)

Format: Numeric

Example: 048

DE50__Currency_Code_Reconciliation

Currency of reconciliation/Settlement

Format: Numeric

Example: 840

DE51__Currency_Code_Billing

Currency of Cardholder Billing

Format: Numeric

Example: 048

DE54_2__Additional_Amount_Type

Other Amounts – e.g. cashback portions in cash back transactions. Surcharges also appear here

Format: Numeric

Example: 0

DE54_3__Additional_Amount_Currency_Code

Indicates currency of the Surcharge amount

Format: Numeric

Example: 48

DE54_4__Additional_Amount_Sign

Additional Amount Sign (D for debit and C for Credit)

Format: Alphabetic

Example: D

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: 0

DE63__Transaction_Life_Cycle_ID

Transaction Life Cycle ID

Format: Alphanumeric

Example: MNO1P2QRS0123

DE71__Message_Number

Message Number – identifies the message within the T112 Mastercard file

Format: Numeric

Example: 54

DE72__Data_Record

Used in Fee type messages to provide description of the fee

Format: String

Example: Late Payment Penalty

DE73__Action_Date

In Fee Collection messages, this data element identifies a reference date related to the Fee.

Format: DateTime Pattern: YYYY-MM-DD

Example: 2023-09-23

DE94__Transaction_Originator_Institution_ID

Transaction Originator Institution ID, identifies the transaction originator institution

Format: Numeric

10456

DE97__Net_Reconciliation_Amount

DE100__Receiving_Institution_ID

Receiving Member ID (Paymentology processor id)

Format: Numeric

12345

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: 0

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: ALBIP1

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: 43212345

Merchant_Reference_ID

Merchant allocated unique Order Identifier used as a merchant reference for inquiry and tracking.

Format: Alphanumeric

Example: c3559d1d9b8abcbee1177771f249a7fd

Gateway_ID

Primary & Secondary Gateway Identifier

Format: Alphanumeric (can be blank or contain whitespaces)

Possible Values: CSRC - Visa CyberSource

HPAY - HyperPay

COUT - Checkout

MPGS - Mastercard MPGS

MIGS - Mastercard MIGS

(Refer to the Mada TLF Specifications for full list of supported values)

Example: CSRC-HPAY

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: 03R

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: 3000330681

Biller_ID

To be used to identify the specific biller in accordance with ongoing billers supported by Sadad.

Format: Numeric

Example: 60

Bill_ID

Unique bill identification number for the specified biller.

Format: Numeric

Example: 604390105

Payment_Status

Note: Issuers will only receive this Tag field for reversals."

Format: Alphabetic

Possible Values: Adviced – For transactions that are approved by the Issuer, Validated – For transactions that are declined by the Issuer. Reversed – For reversal transactions.

Example: Adviced

Bill_Payment_Amount_Due

Format: Decimal

Example: 500.00

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.

Note

All new clients should integrate with the latest report version

Visa v2.0

❗️

Important

This 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:
05 - Sales draft or dispute response financial
06 - Credit voucher or dispute response financial
07 - Cash disbursement or dispute response financial
25 - Sales draft reversal
26 - Credit voucher reversal
27 - Cash disbursement reversal

Example: 05

Transaction_Code_Qualifier

Format: Numeric

Possible Values:
0 - Default
1 - Account Funding
2 - Original Credit

Example: 0

Acquirer_Reference_Number

A 23-digit identification number assigned by the acquirer.

Format: Numeric

Example: 70000001119000000072620

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: 10000001

Purchase_Date

Date the purchase transaction was made.

Format: DateTime
Pattern: YYYY-MM-DD

Example: 2021-09-22

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: -5000.00

Destination_Currency_Code

The currency type presented to the member on incoming transactions.It is the billing currency

Format: Numeric

Example: 826

Source_Amount

The purchase value in transaction currency

Format: Decimal

Example: -5000.00

Source_Currency_Code

Currency code used in the transaction

Format: Numeric

Example: 826

Merchant_Name

Name of the merchant in the original transaction

Format: Alphanumeric

Example: ACQUIRER NAME

Merchant_City

Merchant city, telephone number, email address, or URL

Format: Alphabetic

Example: CITY NAME

Merchant_Country_Code

Code indicating country where the Visa transaction
occurred, regardless of the location of entry to the system

Format: Alphabetic

Example: US

Merchant_Category_Code

Indicates merchant’s type of business product or service

Format: Numeric

Example: 7311

Merchant_ZIP_Code

Postal code of the merchant where the transaction took place

Format: Numeric

Example: 12345

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: ON

Settlement_Flag

Indicates the service used for settlement

Format: Numeric

Possible Values:
0 - International settlement service
3 - Clearing only international settlement
4 - Clearing only national net settlement
8 - National Net settlement service (valid only for countries with
defined service)
9 - BASE II selects the appropriate settlement service based on routing and country-defined default

Example: 0

Authorization_Characteristics_Indicator

Code used by the acquirer to request CPS qualification

Format: Alphanumeric (can be blank or contain whitespace)

Possible Values:
(space), N - Not a payment service transaction
T - A CPS Program was not available when authorized.
E - Card present with merchant name and location data
X - Disqualified custom payment service transaction (inserted by BASE II)

Example: N

Authorization_Code

Code that an issuer, its authorizing processor, or Stand-In Processing (STIP) provides to indicate approval of a transaction

Format: Alphanumeric

Example: 104532

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:
(space)
1 to 4

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:
(spaces)
00 - Unknown
01 - Manual (key entry)
02 - Magnetic stripe read; CVV checking may not be possible.
03 - Optical code
04 - Reserved for future use.\ (Refer to the Visa Base II Specifications for full list of supported values)

Example: 00

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
Pattern: YYYY-MM-DD

Example: 2025-09-23

Member_Message_Text

This field is used to send text messages

Format: String

Example: This is a sample message

Card_Acceptor_ID

Code that identifies the card acceptor operating the POS terminal.

Format: Alphanumeric

Example: 000028005917000

Terminal_ID

Code that identifies the card acceptor terminal or ATM.

Format: Alphanumeric

Example: 17000100

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: U

Authorization_Source_Code

Indicates whether authorization was obtained and the source of the authorization.

Format: Alphanumeric (can be blank or contain whitespace)

Possible Values:
V
6
7
9
B\ (Refer to the Visa Base II Specifications for full list of supported values)

Example: V

Transaction_Code_Qualifier__TCR3

TCQ for the Base II TCR3 record

Format: Numeric

Possible Values:
0 - Default
1 - Account Funding
2 - Original Credit

Example: 0

Transaction_Component_Sequence_Number__TCR3

TCS Number for the Base II TCR3 record

Format: Numeric

Possible Values:
3

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: CR

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: WT

Source_of_Funds

Format: Numeric (can be blank or contain whitespace)

Possible Values:
1 - Cash
2 - Check
3 - Card

Payment_Reversal_Reason_Code

Format: Numeric (can be blank or contain whitespace)

01 - Returned check not sufficient funds (NSF)
02 - Returned check stop payment
03 - Returned check account closed
04 - Returned check refer to maker
05 - Returned check – other
(Spaces) - Unspecified

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: 578904218024611

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:
0 - Default
1 - Account Funding
2 - Original Credit

Example: 0

Transaction_Component_Sequence_Number__TCR5

TCS Number for the Base II TCR5 record

Format: Numeric

Possible Values:
5

Transaction_Identifier

A unique value that Visa assigns to each transaction and returns to the acquirer in the authorization response.

Format: Numeric

Example: 316190801000252

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: 1740

Authorization_Currency_Code

Currency code of the authorized source amount

Format: Numeric

Example: 826

Interchange_Fee_Amount

Specifies the interchange fee amount (in the settlement currency of the member) calculated by Visa for this transaction

Format: Decimal

Example: 0.30

Interchange_Fee_Sign

Specifies if the interchange fee amount is a credit or a debit for the receiving member.

Format: Alphabetic

Possible Values:
C - Credit
D - Debit

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: 0.272213

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: 0.00359748

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: 0.0

Product_ID

Product identifier code

Format: Alphanumeric

Example: G3

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: M

Sample report file

Link to the Visa v2.0 Sample Presentment report

Visa v3.0

❗️

Important

This 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 changes

Below 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:
05 - Sales draft or dispute response financial
06 - Credit voucher or dispute response financial
07 - Cash disbursement or dispute response financial
25 - Sales draft reversal
26 - Credit voucher reversal
27 - Cash disbursement reversal

Example: 05

Transaction_Code_Qualifier

Possible Values:
0 - Default
1 - Account Funding
2 - Original Credit

Example: 0

Usage_Code

Indicates whether this is the first presentment or the second.

Format: Numeric

Possible Values:
1 - First presentment
9 - Dispute Financial

Example: 1

Acquirer_Reference_Number

A 23-digit identification number assigned by the acquirer.

Format: Numeric

Example: 70000001119000000072620

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: 0

Purchase_Date

Date the purchase transaction was made.

Format: DateTime
Pattern: YYYY-MM-DD

Example: 2021-09-22

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: -5000.00

Destination_Currency_Code

The currency type presented to the member on incoming transactions.It is the billing currency

Format: Numeric

Example: 826

Source_Amount

The purchase value in transaction currency

Format: Decimal

Example: -5000.00

Source_Currency_Code

Currency code used in the transaction

Format: Numeric

Example: 826

Merchant_Name

Name of the merchant in the original transaction

Format: Alphanumeric

Example: ACQUIRER NAME

Merchant_City

Merchant city, telephone number, email address, or URL

Format: Alphabetic

Example: CITY NAME

Merchant_Country_Code

Code indicating country where the Visa transaction
occurred, regardless of the location of entry to the system

Format: Alphabetic

Example: US

Merchant_Category_Code

Indicates merchant’s type of business product or service

Format: Numeric

Example: 7311

Merchant_ZIP_Code

Postal code of the merchant where the transaction took place

Format: Numeric

Example: 12345

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: ON

Settlement_Flag

Indicates the service used for settlement

Format: Numeric

Possible Values:
0 - International settlement service
3 - Clearing only international settlement
4 - Clearing only national net settlement
8 - National Net settlement service (valid only for countries with
defined service)
9 - BASE II selects the appropriate settlement service based on routing and country-defined default

Example: 0

Authorization_Characteristics_Indicator

Code used by the acquirer to request CPS qualification

Format: Alphanumeric (can be blank or contain whitespace)

Possible Values:
(space), N - Not a payment service transaction
T - A CPS Program was not available when authorized.
E - Card present with merchant name and location data
X - Disqualified custom payment service transaction (inserted by BASE II)

Example: N

Authorization_Code

Code that an issuer, its authorizing processor, or Stand-In Processing (STIP) provides to indicate approval of a transaction

Format: Alphanumeric

Example: 104532

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:
(space)
1 to 4

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:
(spaces)
00 - Unknown
01 - Manual (key entry)
02 - Magnetic stripe read; CVV checking may not be possible.
03 - Optical code
04 - Reserved for future use.\ (Refer to the Visa Base II Specifications for full list of supported values)

Example: 00

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
Pattern: YYYY-MM-DD

Example: 2025-09-23

Member_Message_Text

This field is used to send text messages

Format: String (can be empty or contain whitespace)

Example: This is a sample message

Card_Acceptor_ID

Code that identifies the card acceptor operating the POS terminal.

Format: Alphanumeric

Example: 000028005917000

Terminal_ID

Code that identifies the card acceptor terminal or ATM.

Format: Alphanumeric

Example: 17000100

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: U

Authorization_Source_Code

Indicates whether authorization was obtained and the source of the authorization.

Format: Alphanumeric (can be blank or contain whitespace)

Possible Values:
V
6
7
9
B\ (Refer to the Visa Base II Specifications for full list of supported values)

Example: V

Transaction_Code_Qualifier__TCR3

TCQ for the Base II TCR3 record

Format: Numeric

Possible Values:
0 - Default
1 - Account Funding
2 - Original Credit

Example: 0

Transaction_Component_Sequence_Number__TCR3

TCS Number for the Base II TCR3 record

Format: Numeric

Possible Values:
3

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: CR

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: WT

Source_of_Funds

Format: Numeric (can be blank or contain whitespace)

Possible Values:
1 - Cash
2 - Check
3 - Card

Payment_Reversal_Reason_Code

Format: Numeric (can be blank or contain whitespace)

01 - Returned check not sufficient funds (NSF)
02 - Returned check stop payment
03 - Returned check account closed
04 - Returned check refer to maker
05 - Returned check – other
(Spaces) - Unspecified

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: 578904218024611

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:
0 - Default
1 - Account Funding
2 - Original Credit

Example: 0

Transaction_Component_Sequence_Number__TCR5

TCS Number for the Base II TCR5 record

Format: Numeric

Possible Values:
5

Transaction_Identifier

A unique value that Visa assigns to each transaction and returns to the acquirer in the authorization response.

Format: Numeric

Example: 316190801000252

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: 1740

Authorization_Currency_Code

Currency code of the authorized source amount

Format: Numeric

Example: 826

Interchange_Fee_Amount

Specifies the interchange fee amount (in the settlement currency of the member) calculated by Visa for this transaction

Format: Decimal

Example: 0.30

Interchange_Fee_Sign

Specifies if the interchange fee amount is a credit or a debit for the receiving member.

Format: Alphabetic

Possible Values:
C - Credit
D - Debit

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: 0.272213

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: 0.00359748

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: 0.0

Product_ID

Product identifier code

Format: Alphanumeric

Example: G3

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: M

Sample report file

Link to the Visa v3.0 Sample Presentment report

Visa v4.0

📓

Key changes

Below 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:

05 - Sales draft or dispute response financial

06 - Credit voucher or dispute response financial

07 - Cash disbursement or dispute response financial

25 - Sales draft reversal

26 - Credit voucher reversal

27 - Cash disbursement reversal

Example: 05

Transaction_Code_Qualifier

Possible Values: 0 - Default 1 - Account Funding 2 - Original Credit

Example: 0

Usage_Code

Indicates whether this is the first presentment or the second.

Format: Numeric

Possible Values:

1 - First presentment

9 - Dispute Financial

Example: 1

Acquirer_Reference_Number

A 23-digit identification number assigned by the acquirer.

Format: Numeric

Example: 70000001119000000072620

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: 0

Purchase_Date

Date the purchase transaction was made.

Format: DateTime Pattern: YYYY-MM-DD

Example: 2021-09-22

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: -5000.00

Destination_Currency_Code

The currency type presented to the member on incoming transactions.It is the billing currency

Format: Numeric

Example: 826

Source_Amount

The purchase value in transaction currency

Format: Decimal

Example: -5000.00

Source_Currency_Code

Currency code used in the transaction

Format: Numeric

Example: 826

Merchant_Name

Name of the merchant in the original transaction

Format: Alphanumeric

Example: ACQUIRER NAME

Merchant_City

Merchant city, telephone number, email address, or URL

Format: Alphabetic

Example: CITY NAME

Merchant_Country_Code

Code indicating country where the Visa transaction occurred, regardless of the location of entry to the system

Format: Alphabetic

Example: US

Merchant_Category_Code

Indicates merchant’s type of business product or service

Format: Numeric

Example: 7311

Merchant_ZIP_Code

Postal code of the merchant where the transaction took place

Format: Numeric

Example: 12345

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: ON

Settlement_Flag

Indicates the service used for settlement

Format: Numeric

Possible Values:

0 - International settlement service

3 - Clearing only international settlement

4 - Clearing only national net settlement

8 - National Net settlement service (valid only for countries with defined service)

9 - BASE II selects the appropriate settlement service based on routing and country-defined default

Example: 0

Authorization_Characteristics_Indicator

Code used by the acquirer to request CPS qualification

Format: Alphanumeric (can be blank or contain whitespace)

Possible Values:

(space), N - Not a payment service transaction

T - A CPS Program was not available when authorized.

E - Card present with merchant name and location data

X - Disqualified custom payment service transaction (inserted by BASE II)

Example: T

Authorization_Code

Code that an issuer, its authorizing processor, or Stand-In Processing (STIP) provides to indicate approval of a transaction

Format: Alphanumeric

Example: 104532

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:

(space)

1 to 4

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:

(spaces)

00 - Unknown

01 - Manual (key entry)

02 - Magnetic stripe read; CVV
checking may not be possible.

03 - Optical code

04 - Reserved for future use.

(Refer to the Visa Base II Specifications for full list of supported values)

Example: 00

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: YYYY-MM-DD

Example: 2025-09-23

Member_Message_Text

This field is used to send text messages

Format: String (can be empty or contain whitespace)

Example: This is a sample message

Card_Acceptor_ID

Code that identifies the card acceptor operating the POS terminal.

Format: Alphanumeric

Example: 000028005917000

Terminal_ID

Code that identifies the card acceptor terminal or ATM.

Format: Alphanumeric

Example: 17000100

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: U

Authorization_Source_Code

Indicates whether authorization was obtained and the source of the authorization.

Format: Alphanumeric (can be blank or contain whitespace)

Possible Values: V 6 7 9 B

(Refer to the Visa Base II Specifications for full list of supported values)

Example: V

Transaction_Code_Qualifier__TCR3

TCQ for the Base II TCR3 record

Format: Numeric

Possible Values: 0 - Default 1 - Account Funding 2 - Original Credit

Example: 0

Transaction_Component_Sequence_Number__TCR3

TCS Number for the Base II TCR3 record

Format: Numeric

Possible Values: 3

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: CR

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: WT

Source_of_Funds

Format: Numeric (can be blank or contain whitespace)

Possible Values: 1 - Cash 2 - Check 3 - Card

Payment_Reversal_Reason_Code

Format: Numeric (can be blank or contain whitespace)

Possible Values: 01 - Returned check not sufficient funds (NSF) 02 - Returned check stop payment 03 - Returned check account closed 04 - Returned check refer to maker 05 - Returned check – other (Spaces) - Unspecified

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: 578904218024611

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: 0 - Default 1 - Account Funding 2 - Original Credit

Example: 0

Transaction_Component_Sequence_Number__TCR5

TCS Number for the Base II TCR5 record

Format: Numeric

Possible Values: 5

Transaction_Identifier

A unique value that Visa assigns to each transaction and returns to the acquirer in the authorization response.

Format: Numeric

Example: 316190801000252

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: 1740

Authorization_Currency_Code

Currency code of the authorized source amount

Format: Numeric

Example: 826

Interchange_Fee_Amount

Specifies the interchange fee amount (in the settlement currency of the member) calculated by Visa for this transaction

Format: Decimal

Example: 0.30

Interchange_Fee_Sign

Specifies if the interchange fee amount is a credit or a debit for the receiving member.

Format: Alphabetic

Possible Values: C - Credit D - Debit

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: 0.272213

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: 0.00359748

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: 0.0

Product_ID

Product identifier code

Format: Alphanumeric

Example: G3

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: M

Sample report file

Link to the Visa v4.0 Sample Presentment report