Retrieval reference number (RRN) is a 12-character reference assigned to a card transaction in the authorization message, used by the acquirer, processor and merchant to locate that exact transaction later. It sits in data element 37 of ISO 8583, is usually generated by the acquirer or terminal host, and stays attached through capture, reversal and refund. Formats vary, often combining a date component with the six-digit system trace audit number. The name comes from retrieval requests for paper sales slips. Acquirers search by RRN while issuers search by the 23-digit acquirer reference number, so disputes often need both. India's UPI also uses a 12-digit RRN, and missing RRNs in transaction logs are a due diligence warning sign.
What is a retrieval reference number
The RRN lives in data element 37 of ISO 8583, the message standard behind most card authorizations. It is usually generated by the acquirer or the terminal's host when the authorization is sent, and it stays attached through the response, the capture and any later reversal or refund linked to the original.
A common construction combines a date component and a sequence number, for example the last digit of the year, the Julian day, the hour, and the six-digit system trace audit number. A value like 626614123456 would then read as 2026, day 266, 14:00, trace 123456. Schemes do not mandate one format, so acquirers vary.
What is RRN in payments used for
The name comes from retrieval requests: when an issuer wanted a copy of a sales slip, the RRN was how the acquirer found the paper. Today it serves refunds, reversals, dispute evidence and support tickets. It is printed on many terminal receipts and appears in acquirer portals and reconciliation files.
Outside cards, the same term is used in India's UPI, where every transfer carries a 12-digit RRN that both banks can search.
How the RRN differs from other references
The system trace audit number is six digits (data element 11) and often resets daily, so it is only unique within a short window. The authorization code, six characters in data element 38, comes from the issuer and proves approval. The acquirer reference number is 23 digits, created at clearing, and is the key the issuer sees on its side.
That split matters. A cardholder's bank normally searches by ARN, while the merchant's acquirer searches by RRN, so a dispute often requires both.
How to track a transaction with RRN
A merchant takes the RRN from the receipt, terminal journal or gateway response and gives it to the acquirer together with the date, amount and terminal ID. The acquirer locates the authorization, confirms whether it was captured and settled, and can return the ARN for the cardholder's bank to trace the credit.
A missing RRN in a platform's transaction logs is a warning sign in due diligence on a payment company. Without it, refunds and disputes must be matched on amount and time, which fails at scale.