What Is a Merchant Reference Number (MRN)? Meaning, Uses, and How to Find It

Every digital payment generates multiple reference numbers: one from the gateway, one from the bank, and one from UPI if that was the payment method. None of them necessarily belong to the merchant. The Merchant Reference Number is the identifier the merchant defines and controls.

It is the internal identifier that connects an order in the system to a payment in the settlement report. Without a consistent reference, payment reconciliation becomes a manual matching exercise across disconnected IDs from different systems.

What Is a Merchant Reference Number?

The Merchant Reference Number is an alphanumeric identifier created by the merchant’s system for a transaction. It is different from the numbers created by the bank or the card network, as the MRN is managed by the merchant.

The MRN may be shared with the payment gateway when a transaction is initiated and can appear in transaction records, settlement files, and receipts or confirmation emails, depending on the merchant’s configuration.

For support queries, refunds, and month-end reconciliation, the MRN can become one of the first identifiers searched by the relevant teams.

Businesses setting up their payment infrastructure can refer to this guide to integrating a payment gateway to understand how order creation and payment tracking fit into the payment flow.

Merchant Reference Number vs Other Transaction IDs

An individual transaction creates several reference numbers across different systems, each with its own function. Mixing them up is a common source of discrepancies during reconciliation. Here is a comparison of these important reference numbers and their respective systems.

Identifier	Generated By	What It Identifies	Primary Use
Merchant Reference Number (MRN)	Merchant’s system or, in some setups, a payment platform	The merchant’s internal record of the transaction	Internal reconciliation, customer support, and dispute management
Payment Gateway Transaction ID	Payment gateway	The transaction processed by the gateway	Gateway-side tracking and reporting
Bank Reference Number / UTR	Bank or payment system, depending on the payment rail	The relevant bank transfer or payment event	Bank reconciliation and payment confirmation
UPI Transaction Reference	UPI payment system	The UPI payment transaction	UPI-specific tracking and dispute resolution
Order ID	Merchant’s order management system or payment integration	The customer’s order	Order tracking and fulfilment

A single customer payment can have all five identifiers. Each exists in a different system. The MRN is the merchant’s internal bridge that helps link them when reconciliation is needed.

For businesses accepting UPI, understanding how UPI payments work for businesses can also help clarify how payment references are used to track and reconcile transactions.

How a Merchant Reference Number Is Generated

MRN generation is not uniform across payment setups. Whether the number comes from a payment platform automatically or from the merchant’s own system depends on how the integration is built. Below are the two approaches and when each applies.

• System-generated MRN: The payment gateway or order management system automatically generates a reference when an order is initiated. The format may include a timestamp, a sequential or random order-specific string, or a combination of these. This is common for businesses using a payment gateway API or an integrated checkout.
• Merchant-defined MRN: Some merchants define their own MRN format and pass it to the payment gateway when creating a transaction. A common format might include the order date, customer ID, and an internal order counter.

Example: ORD-20261010-CUST4521-001

This approach gives merchants more control over the MRN structure and makes the number more readable for support and finance teams.

How MRN Is Used in Practice

The importance of an MRN becomes clear in day-to-day situations when several teams need to access a single transaction across different applications. Here are four scenarios where a consistently maintained MRN proves useful.

1. Reconciliation

Transactions in settlement reports have gateway transaction IDs, while the merchant’s own system contains order records with their respective order IDs. The MRN can help connect the two.

For organisations handling thousands of transactions daily, automated reconciliation can compare the reference stored in the settlement data with the corresponding reference in the order management system. Transactions that cannot be matched are flagged for investigation.

A structured payment reconciliation process helps finance teams identify mismatches, review adjustments, and connect payment records with settlement data.

2. Customer Support

When a customer raises an issue about a charge or asks about a refund, the customer support representative can search for the relevant transaction using its MRN or another available identifier.

This lookup can help the representative access the payment status, gateway transaction ID, and bank transaction reference number, making it easier to investigate the issue and respond to the customer.

3. Dispute and Chargeback Management

When a customer disputes a payment through their bank, the merchant may receive a notification containing a transaction reference. The MRN can help the merchant retrieve the associated order details, payment records, and delivery information.

Keeping these records organised makes it easier to investigate the transaction and prepare supporting evidence. Businesses can also learn more about payment disputes, their process, and prevention.

4. Refund Processing

Refunds are initiated against the original payment using the relevant transaction identifiers supported by the payment platform. Depending on the integration, the merchant may use the original payment ID, gateway transaction ID, order reference, or another supported identifier to locate the transaction.

Where refunds are processed programmatically through a payment API, accurate transaction mapping helps ensure that the correct payment is selected for reversal.

Read more about how online refunds are processed and how businesses can make the process more efficient.

How to Find a Merchant Reference Number

An MRN is useful only if teams can locate it quickly when a dispute, refund, or reconciliation query arises. Where it appears depends on the merchant’s system configuration. Here are the main places to check.

• In the payment gateway dashboard: Payment dashboards can display identifiers such as the order ID and payment ID for individual transactions. In setups that use platform-generated references, these IDs can serve as practical reference points for merchants.
• In the settlement report: Check the transaction-level records for the order ID, merchant reference, payment ID, or other available identifiers. The exact fields vary by provider and report type. Cashfree’s payment settlement cycle guide explains how transaction processing and settlement fit together.
• In the customer receipt or confirmation email: If the merchant has configured receipts to include the MRN, customers can use it when contacting support about a payment or order.
• In the order management system: The merchant reference should be stored alongside the order ID and gateway transaction ID so that teams can connect the order with its payment record.
• In the payment API request or response: When a merchant initiates a transaction through an API, the request and response may contain identifiers such as the merchant-provided order ID and the payment platform’s payment ID. Check the integration documentation to confirm the exact field names and behaviour.

For technical implementation, Cashfree’s developer tools and payment integration resources can help developers explore and test payment flows.

Best Practices for Managing Merchant Reference Numbers

A well-managed MRN system can reduce reconciliation time and cut support overhead across finance and customer-facing teams. The following practices make a practical difference in day-to-day operations.

• Use a consistent, human-readable format: A format like ORD-YYYYMMDD-XXXX can be easier to read than a random identifier when the support team is looking at multiple records. Ensure the format also remains unique and fits the requirements of the systems receiving it.
• Include the MRN on customer-facing documents: Where appropriate, add the reference to order confirmation emails, invoices, and receipts so customers can quote it when contacting support.
• Store the MRN across relevant systems: The reference should be available in the order management system, payment integration, CRM where applicable, and accounting or ERP system. A reference that exists in only one system cannot easily connect records across platforms.
• Automate reconciliation using the appropriate identifier: Manual matching is error-prone at scale. Settlement automation can use consistent identifiers to join order records with payment and settlement data, while flagging exceptions for review.
• Keep transaction references separate: Do not assume that an MRN, order ID, payment ID, UTR, and settlement ID are interchangeable. Store the identifiers in their appropriate fields and map their relationships clearly.

Businesses can also strengthen their processes by reviewing bank reconciliation methods and best practices, particularly when matching gateway settlements against bank statements.

Conclusion

A Merchant Reference Number works best when the relevant transaction references are used consistently across the systems involved in a payment. This makes reconciliation easier, helps support teams investigate payment issues, and enables merchants to retrieve the order and payment records needed to respond to disputes.

Setting up reference mapping correctly from the outset is easier than correcting inconsistencies later. With Cashfree, businesses can use payment records, order IDs, payment IDs, and settlement reports to connect transaction activity with reconciliation workflows.

FAQs

1. What is a Merchant Reference Number (MRN)?

A Merchant Reference Number is an identifier assigned by a merchant’s system to help track and reconcile transactions. Depending on the payment setup, a merchant may also use order IDs or payment platform identifiers as reference points for locating transaction records.

2. What is the difference between an MRN and a payment gateway transaction ID?

An MRN is typically created or controlled by the merchant and links a transaction to internal order records. A payment gateway transaction ID is generated by the payment platform and identifies the transaction within its system. Both can refer to the same payment but serve different tracking purposes.

3. How is a Merchant Reference Number generated?

An MRN can be generated automatically by a merchant’s order management system or another integrated platform. Alternatively, the merchant can define a reference format and pass it when initiating a transaction, provided the integration supports it.

4. Where can I find the Merchant Reference Number for a transaction?

Check the merchant dashboard, settlement reports, order management system, API request or response records, and customer receipts if the merchant has configured them to display the reference. The exact location depends on the system and payment integration.

5. What does a Merchant Reference Number look like?

The format varies by merchant and payment setup. A common structure combines a prefix, date, and order-specific identifier, such as ORD-20261010-CUST4521-001. The reference should be unique enough to identify the intended transaction within the relevant system.