Acquirer Reference Number
What Is an Acquirer Reference Number (ARN)? Definition and How It Works
Definition
An Acquirer Reference Number (ARN) is a unique 23-digit identifier assigned to a card transaction by the acquiring bank that enables the transaction to be traced through the entire card scheme network for dispute resolution, refund tracking, and reconciliation.
How it works
An ARN is generated by the acquirer at the point of settlement and assigned to every processed card transaction. The 23-digit number encodes specific information: the first 6 digits identify the acquiring bank, the next 4 digits represent the Julian date of processing, and the remaining digits form a unique sequence number within that batch. This structure means an ARN is globally unique to a single transaction and carries enough encoded information to identify the processing bank and date without external reference.
The primary operational use of ARNs is in dispute and refund tracing. When a cardholder contacts their issuing bank to query a transaction, the issuer can use the ARN to trace the payment through the card network back to the acquirer and merchant. This tracing capability is what allows issuers to verify transaction details, confirm that a refund has been processed, and retrieve documentation for chargeback investigation. Without an ARN the tracing process requires manual escalation through the card scheme.
For merchants, the ARN is particularly valuable in customer service scenarios involving refunds. When a merchant processes a refund, the refund is assigned an ARN by the acquirer. If a cardholder disputes that a refund was received, the merchant can provide the ARN to the cardholder, who can then present it to their issuing bank to trace the refund through the network. This is often faster than waiting for chargeback proceedings and can resolve the dispute without a formal chargeback being filed.
ARNs are available in the acquirer's transaction reporting and settlement files. Merchants should ensure their customer service and finance teams know how to retrieve and communicate ARNs, as this capability directly reduces the number of preventable chargebacks that arise from refund disputes.
Why it matters
Providing an ARN when a customer disputes a refund enables the issuer to trace the refund credit instantly, often resolving the dispute before a formal chargeback is filed. The ARN for a processed refund is the definitive proof that the refund was submitted to the card network; it is stronger evidence than an internal system record. Acquirers and card schemes use ARNs to retrieve transaction documentation during chargeback investigation; merchants who include ARNs in dispute responses accelerate the resolution timeline. Communicating the ARN to a cardholder for a refund they claim not to have received shifts the tracing responsibility to the issuer and removes the merchant from the middle of the investigation. ARNs provide a reliable join key between the merchant's order management system and the acquirer's settlement file, enabling precise transaction-level reconciliation.
With PXP
PXP provides ARNs for all processed transactions and refunds in transaction reporting and settlement files. PXP's dispute management tooling surfaces ARNs in the chargeback workflow, enabling merchants to include ARN evidence in dispute responses and customer service interactions.
Frequently asked questions
What does an ARN look like and where does it appear?
An ARN is a 23-digit numeric string, for example: 74491260312859200000001. The structure encodes the acquirer BIN (6 digits), Julian processing date (4 digits in YDDD format), and a unique sequence. ARNs appear in the acquirer's transaction reporting, settlement files, and in the chargeback notification when a dispute is raised. Merchants should store the ARN at the transaction level in their order management system alongside the internal order ID for fast retrieval when needed for customer service or dispute response.
How do I use an ARN to help a customer who claims their refund hasn't arrived?
Retrieve the ARN from your acquirer's reporting for the refund transaction. Provide the ARN to the customer and instruct them to contact their card-issuing bank with the ARN and ask the bank to trace the credit using it. The issuer can use the ARN to confirm whether the refund credit has been received into the card network and when it was applied to the account. This process typically resolves refund queries within 1-3 business days and avoids a formal chargeback being filed for a refund that was correctly processed.
Is the ARN the same as the transaction authorisation code?
No. The authorisation code (also called the approval code) is a 6-character alphanumeric code returned by the issuer at the point of authorisation to confirm the transaction was approved. The ARN is assigned by the acquirer at settlement and is a 23-digit number. The authorisation code confirms approval; the ARN enables post-settlement tracing through the card network. Both are useful in dispute contexts but serve different purposes: the authorisation code proves the issuer approved the transaction; the ARN enables the transaction to be located in the settlement network.
How long does an ARN remain valid for dispute tracing?
ARNs do not expire and can be used to trace transactions historically through the card network. However the practical window for dispute resolution is governed by chargeback time limits: Visa and Mastercard generally allow chargebacks to be filed within 120 days of the transaction or expected service date. Within this window, ARN tracing is most operationally relevant. Beyond the chargeback window, ARNs remain useful for reconciliation and audit purposes but their dispute prevention utility is limited to the scheme's dispute timeframes.
Revolutionize your business with PXP
Take complete control of your commerce and payments with one platform.
Get Started