How Acquirer Reference Number (ARN) Works
When a card payment moves through the banking system, it passes through multiple independent institutions that each need a common reference to identify the same transaction. The ARN is that shared identifier, created by the acquirer and carried through clearing and settlement so every party sees the same record. Understanding how it is assigned and propagated is the foundation for using it effectively.
Transaction Submitted to the Acquirer
The merchant's payment gateway or point-of-sale system forwards the transaction to the acquiring bank. At this stage the transaction carries internal gateway identifiers, but an ARN has not yet been assigned — it is created downstream during the clearing process, not at authorization.
ARN Assignment at Settlement
Once the acquirer submits the transaction for settlement, it generates a unique 23-digit ARN. The number encodes the acquiring institution identifier, a processing date, and a sequential reference. The exact encoding varies between Visa and Mastercard but the length and the cross-network scope are consistent.
Routing Through the Card Network
The ARN travels with the transaction data as it moves through the card scheme's clearing system. Both Visa and Mastercard record the ARN in their central clearing infrastructure, creating a cross-network audit trail that neither the merchant nor the issuer can modify.
Recording at the Issuing Bank
The issuing bank receives the cleared transaction paired with the ARN and records it against the cardholder's account. From this point, the ARN can be used to look up the transaction from either the acquirer side or the issuer side — it is the one identifier both institutions share.
Reconciliation and Reporting
ARNs appear in acquirer settlement files, helping merchants match authorization records to cleared funds during reconciliation. A transaction that never receives an ARN has not settled, and any refund submitted without a recoverable ARN cannot be traced if disputed.
Dispute and Chargeback Resolution
When a chargeback is filed, card network rules require the acquirer to use the ARN to retrieve original transaction data. Merchants who include the ARN in their representment evidence give the arbitrating bank an unambiguous reference, reducing back-and-forth and improving win rates.
Why Acquirer Reference Number (ARN) Matters
ARNs have a direct and measurable impact on dispute outcomes, customer satisfaction, and operational efficiency. Without reliable ARN tracking, merchants cannot prove refunds were issued, cannot respond to disputes with complete evidence, and cannot trace payments that appear missing on a customer's statement.
Three data points frame the stakes. According to Visa dispute process documentation, merchants who submit complete transaction evidence — including the ARN — resolve disputes up to 50% faster than those who provide incomplete responses. Mastercard's industry research puts the average total cost of a chargeback at 2.4 times the original transaction value, once fees, merchandise loss, and staff time are factored in. A 2024 Chargebacks911 industry survey found that 35% of friendly-fraud chargebacks involved refunds that had already been processed — cases where sharing the ARN with the cardholder at refund time would have prevented the dispute entirely.
Proactive refund communication reduces support volume
When issuing a refund, include the ARN in the confirmation email alongside a plain-language explanation: "Your refund reference number is [ARN]. You can provide this to your bank if the credit is not visible within 5 business days." This single message deflects the majority of post-refund support contacts.
ARNs are equally critical in cross-border transactions, where the issuing bank may operate in a different country and has no other way to locate a payment except through the card network's shared clearing record — anchored by the ARN.
Acquirer Reference Number (ARN) vs. Retrieval Reference Number (RRN)
ARNs and Retrieval Reference Numbers (RRNs) are two of the most frequently confused identifiers in card payments. Both are used to look up transactions, both appear in settlement documentation, and both may be requested during a dispute. The differences in who assigns them, when they are created, and what they can prove are significant.
The core distinction is scope: the ARN is a post-settlement, cross-network identifier; the RRN is an authorization-stage identifier that stays primarily on the issuer's side of the transaction.
| Feature | ARN | RRN |
|---|---|---|
| Assigned by | Acquiring bank | Issuing bank or payment processor |
| Length | 23 digits | 12 alphanumeric characters |
| When generated | During clearing and settlement | At authorization |
| Scope | Travels the full card network | Primarily issuer-side |
| Primary use | Refund tracing, dispute evidence | Authorization lookup, POS receipts |
| Visible on | Acquirer and issuer reports | POS receipts, issuer statements |
| Required for chargeback response | Yes — standard practice | Supplementary |
When submitting a chargeback representment, include both identifiers when available. The RRN proves the transaction was authorized; the ARN proves it cleared and settled. Together they form a complete authorization-to-settlement audit trail.
Types of Acquirer Reference Number (ARN)
ARN formats are defined by card scheme rules, but the internal structure and encoding differ between networks. Knowing which format applies to a given transaction matters when developers parse ARNs programmatically or when merchants need to communicate them to issuers in different regions.
Visa ARN (23 digits) Visa ARNs follow a consistent global format: a 6-digit acquiring institution identifier (BIN), a 6-digit Julian date representing the processing date, and an 11-digit sequential transaction reference. This structure is standardized across all Visa transactions regardless of geography.
Mastercard ARN (23 digits) Mastercard uses the same 23-digit length but encodes the date and sequence reference differently. Mastercard ARNs are generated during the clearing cycle and are visible in the Mastercard Settlement and Reconciliation system within 24–48 hours of transaction processing.
American Express Trace ID Amex does not call its identifier an ARN; instead it uses a Trace ID. This serves the same functional purpose — tracing a transaction across Amex's proprietary network — but it is shorter (typically 15 digits) and is managed within Amex's closed-loop system rather than through an open card scheme.
Discover and Regional Networks Discover and regional debit networks such as Interac (Canada) and EFTPOS (Australia) use ARN-equivalent identifiers with their own formats and lengths. When operating across these networks, confirm the correct identifier format and retrieval process directly with your acquirer.
Developer note: store ARNs as strings
Always store ARNs as strings, never as integers or numeric types. ARNs can begin with one or more zeros — casting to a numeric type silently drops leading zeros and produces an invalid reference that cannot be matched by the card network or issuing bank.
Best Practices
Reliable ARN management gives merchants a measurable edge in dispute resolution and customer support efficiency. The operational gap between merchants who actively capture and surface ARNs and those who treat them as a backend detail shows up directly in chargeback win rates and cost-per-dispute metrics.
For Merchants
- Store ARNs at the order level. Map every ARN to its corresponding order ID, customer record, and payment method in your database. This makes dispute responses and customer support queries resolvable in seconds rather than minutes.
- Share ARNs in refund confirmation emails. Include the ARN alongside a brief explanation of how to use it. Customers who receive a traceable reference are far less likely to file a chargeback out of impatience or confusion.
- Monitor settlement files for missing ARNs. An authorized transaction that never receives an ARN within 48 hours may not have settled. Build alerting around this gap — it is often the earliest signal of an acquirer-side processing failure.
- Include ARNs in all dispute evidence packages. Make ARN inclusion a non-negotiable step in your chargeback response workflow. Card network rules explicitly allow and encourage its use in retrieval and representment documentation.
For Developers
- Retrieve ARNs via your acquirer's reporting API. ARNs are not available at authorization time — poll the settlement reporting endpoint separately, typically 24–48 hours after transaction processing.
- Validate ARN length and format. Visa and Mastercard ARNs are exactly 23 characters. Add server-side validation to catch truncated or malformed ARNs before they are persisted.
- Expose ARNs in internal tooling. Support agents, finance teams, and dispute managers should be able to retrieve the ARN for any transaction in under 30 seconds from your admin interface.
- Handle ARN updates. In some scenarios — particularly for refunds and re-presentments — an ARN may be updated or superseded after initial assignment. Design your data model to store ARN history, not just the current value.
Common Mistakes
Even experienced payment operations teams make avoidable ARN-related errors. These mistakes tend to compound: they are invisible in normal operations and surface only during disputes and reconciliation runs, exactly when they are most expensive to fix.
1. Confusing the ARN with the gateway transaction ID The gateway transaction ID is an internal reference. It means nothing to an issuing bank. Using it in a refund confirmation email or chargeback response sends customers and arbitrators in the wrong direction, wasting resolution time.
2. Not storing ARNs in the merchant's own systems Relying entirely on the gateway dashboard to retrieve ARNs on demand is fragile. Gateways change data retention policies, dashboards go down, and manual lookups do not scale during bulk dispute periods. ARNs belong in your own database.
3. Casting ARNs to numeric types As noted in the Types section, leading zeros in ARNs are semantically significant. Storing 00234561234560000000012 as an integer produces a different number that is unresolvable by any card network system.
4. Sharing ARNs only after customers complain By the time a customer files a chargeback, the damage is done. Proactive ARN sharing at refund time costs nothing and prevents a meaningful share of friendly-fraud disputes.
5. Submitting chargeback responses without the ARN A dispute response that omits the ARN forces the arbitrator to trace the transaction manually, signals operational immaturity, and reduces your credibility. Card network arbitration guidelines explicitly reference the ARN as primary transaction evidence — excluding it is a self-inflicted disadvantage.
Acquirer Reference Number (ARN) and Tagada
Tagada automatically captures and surfaces ARNs for every transaction processed through its payment orchestration layer. Rather than requiring merchants to query each acquirer's portal separately — a process that compounds in complexity as routing diversifies across multiple acquirers — Tagada aggregates ARN data into a single, searchable transaction record available via dashboard and API.
ARN lookup in one click
In the Tagada dashboard, every settled transaction displays its ARN alongside the authorization code, settlement date, card network, and payment method. Support teams can copy the ARN directly into customer communications or chargeback response templates without logging in to any acquirer portal.
For merchants running dispute workflows through Tagada, ARNs are automatically included in generated evidence packages. This eliminates manual retrieval steps per dispute, ensures that no representment is filed without the core cross-network reference, and makes it straightforward to audit ARN coverage across the full transaction portfolio during reconciliation.