What Is an ARN Number? Tracing Refunds Customers Can't Find
What is an ARN number? Learn where to find the acquirer reference number for a refund and how to use it when a customer says the credit never arrived.

Photo: Pixabay
On this page 6 sections
Key takeaways
- When a customer says a refund is missing, send the ARN of the refund itself. The ARN of the original sale only proves they were charged.
- A void that happens before the batch closes never settles, so it has no ARN. The customer is waiting for a pending charge to drop off, not for a credit to post.
- Don't issue a second refund because the first one can't be found. Give the customer the ARN, and if their bank can't locate the credit, ask your processor to trace it.
- In a "credit not processed" dispute, the refund's ARN is the evidence the issuer can check against its own records.
What is an ARN number? It's the acquirer reference number, a unique ID that the bank behind your merchant account attaches to a card transaction when it sends that transaction through the card network for settlement. Refunds get one too. When a customer says a refund never arrived, the refund's ARN is the detail their card issuer needs to find the credit, so it's the first thing you should give them.
A refund the customer can't see has almost always gone somewhere they didn't look. Either the credit posted under a business name they don't recognize, or it's still sitting with their bank. One phone call with the ARN settles which. Without it, you trade emails for a week, and the pressure builds to send a second refund you don't owe.
What an Acquirer Reference Number Is
Every card transaction has two banks behind it. The issuer is the customer's bank. Your acquirer is the bank that sponsors your merchant account, and it works through your processor (our explainer on processors, acquirers and gateways covers who does what). When the acquirer submits a settled sale or refund to the card network, it attaches an acquirer reference number, and the issuer receives that same number with the transaction.
That shared number is the point. Your business generates plenty of IDs for every sale, but the ARN is the one recorded on both sides of the network. A bank rep can search for it.
| Number | Who creates it | Can the customer's bank search for it? |
|---|---|---|
| Order or invoice number | Your business | No |
| Gateway or POS transaction ID | Your gateway or POS software | No |
| Batch number | Your terminal or processor | No |
| Authorization code | The issuer, at approval | Not reliably. It identifies the approval, not the settled transaction |
| ARN | The acquirer, at clearing | Yes |
A common mistake is reading the customer the gateway transaction ID because it's the number on the screen. Their bank has no record of it, and the call goes nowhere.
How the ARN Is Built and Who Assigns It
Your acquirer, or your processor acting for it, assigns the ARN when the transaction goes into clearing. Clearing is the step after your batch closes, when settled transactions are sent to the network. Neither the card tap nor the click on "refund" creates an ARN. That timing explains a lot of confusion: a refund you entered this afternoon has no ARN until the batch settles.
On Visa and Mastercard transactions, the ARN is a long numeric string. The networks' technical specifications set its layout, which includes an identifier for the acquiring bank and a processing date among other fields. You don't need to decode it. Copy it exactly, because one wrong digit sends the issuer looking for a transaction that doesn't exist. American Express and Discover use reference formats that depend on how your account is set up, so ask your processor which number to give customers who paid with those cards.
Voids cause their own mix-up. A void cancels a transaction before the batch closes, so it never settles and never gets an ARN. If you voided a sale, the customer isn't waiting for a credit. They're waiting for the pending authorization to drop off their account, on the issuer's schedule. A refund, by contrast, is a new transaction that settles and gets its own ARN. Our guide to voids versus refunds covers when to use each. For this problem, what matters is that only a refund leaves a trail the customer's bank can follow.
Where to Find the ARN in Your Processor Dashboard
Portals differ, but the search follows the same order. Start with the transaction detail screen for the refund itself, and open the refund record rather than the original sale. If the ARN isn't there, check your settlement or funding reports, and look in the downloadable export as well as the on-screen view. Your disputes section lists the ARN for every case, though that helps only after a customer has filed.
Look for a field labeled "ARN" or the spelled-out "Acquirer Reference Number." If the field is blank, check whether the refund has settled. An unbatched refund has no ARN yet.
Keyed and phone orders add one wrinkle. If you take them through a virtual terminal for card-not-present sales or a gateway such as Authorize.net, know where the gateway's job ends. It hands transactions to the processor and doesn't handle clearing, so look for the ARN in your processor's reporting portal rather than the gateway screen.
Pull the refund's ARN, not the sale's. If you give the customer the original sale's ARN, their bank will find the purchase and confirm the charge was valid. That is the opposite of what the customer called about.
When you can't find the ARN yourself, call your processor's support line with your merchant ID (MID), the refund date, the exact amount, the card brand with its last four digits, and a note that you need a refund, not a sale. Monthly credit card reconciliation helps here too. A refund netted out of a deposit gives you independent proof that the money left your account.
Example: Resolving a Missing Refund Complaint
This scenario is illustrative. The business and details are made up.
Assumptions: An independent hotel charged a guest in full for a two-night stay at booking. The guest canceled inside the cancellation window, and the front desk issued a full refund the same day. The hotel's batch closes automatically every night. Nine days later, the guest emails: "I never got my refund."
- Find the refund record. Search by the card's last four digits and the refund amount. You want a refund entry dated the day of the cancellation, not the original charge.
- Confirm it settled. Look for a status of settled or funded. Pending or unbatched means the refund never left, so close the batch and tell the guest the corrected date.
- Copy the ARN from the refund record.
- Check your billing descriptor. This is the business name that appears on card statements. If it shows your legal entity name instead of the hotel's name, tell the guest what to look for.
- Send the guest a short message they can read to their bank.
"Our records show a refund of [amount] to your [card brand] ending in [last four], processed on [refund date]. The acquirer reference number is [ARN]. Please call the number on the back of your card and give them that reference number. Your bank can use it to find the credit even if it posted under a different name or to a replacement card. If they can't locate it, tell us what they said and we'll follow up with our processor."
When the guest calls, the issuer's search ends in one of four places: a credit under a descriptor the guest didn't recognize, a credit on a reissued card number, a credit that posted after the statement closed, or a credit still pending at the issuer. Whichever it is, the guest hears the answer from their own bank, and that carries more weight with them than anything you say.
If the issuer truly can't find the credit, send the ARN to your processor and ask for a trace. Don't issue a second refund. Once the first one posts, you'll have paid the guest twice, and recovering a duplicate refund means asking a customer to give money back.
Online stores run into a variation. An order shipped in two boxes and charged at each shipment produces two charges and two refunds, each with its own ARN. Send both, with the amount next to each.
Using ARNs in Chargeback Responses
ARNs matter in disputes for two reasons.
First, the chargeback notice lists the ARN of the original sale. That's how you match the dispute to the right transaction when you had dozens of sales at the same price on the same day.
Second, the card networks have a dispute reason for credits a customer says were never processed. Against that reason, the refund's ARN is your strongest evidence, because the issuer can check it against its own records. Add your refund policy and your messages with the customer, then organize the response around what the reason code asks you to prove. Our references for Visa chargeback reason codes and Mastercard reason codes go through each category.
Timing decides what you do next. If you refunded before the dispute was filed, respond with the refund's ARN to show the customer has already been credited. With a dispute already open, talk to your processor before you refund anything, since a refund on top of a successful chargeback pays the customer twice.
A retrieval request sometimes arrives before any chargeback. Answer it fast and include the refund ARN if one exists. Our guide to answering retrieval requests explains how a quick, complete reply heads off the dispute.
Keep refund records, ARNs included, for at least the length of the dispute window. Our article on chargeback filing windows covers how long that runs.
Refund Timelines Customers Should Expect
A refund moves through three stages: your batch closes, your acquirer clears the refund through the network, and the issuer posts the credit to the customer's account. You and your processor control the first two, and they move quickly if you batch nightly. Most of the waiting happens at the third stage, which belongs to the issuer. Issuers differ in whether they display a pending credit right away or show nothing until it posts. If you serve cardholders from abroad, our guide to dynamic currency conversion (DCC) explains what it means when a foreign cardholder pays in their home currency.
Tell customers to expect several business days, not a specific date, and to count from the date the refund settled rather than the date they asked for it. Weekends and bank holidays add time. Five situations stretch the wait or confuse what the customer sees:
- Statement cycles. A credit that posts after the statement closes appears on the next one, and plenty of customers only check statements.
- Debit and prepaid cards. Money goes back to a bank or card balance, which customers forget to check.
- Foreign cards. The issuer converts the refund at the exchange rate on the day the credit posts, so the amount in the customer's currency differs from the original charge whenever the rate has moved. Our guide to accepting international cards explains why.
- Hotel incidental holds. A released hold is not a refund and has no ARN. The guest is waiting for the authorization hold to expire, a question front desks at hotels and lodging businesses hear constantly.
- Third-party bookings. If an online travel agency charged the traveler, the agency is the merchant of record. Your processor has no ARN for that charge, and the traveler needs to contact the agency.
Before the next complaint comes in, find out where your dashboard shows a refund's ARN and how many days after settlement it appears. Write that down for whoever handles customer service. If the only way to get an ARN is a call to support, raise that when you compare processors. You can request a free quote from MannyPay and ask a specialist how refund reporting works on the platform you'd use.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

