How to retrieve ARN (Acquirer Reference Number) for tracking lost international card refunds

by

An Acquirer Reference Number (ARN) is a unique 23-digit identifier generated by the merchant’s acquiring bank when an international credit or debit card refund is routed through payment card networks (Visa, Mastercard, or American Express). When an international refund fails to reflect in the cardholder’s issuing bank account, it is typically because the cross-border settlement clearing file has been processed by the card scheme network, but the receiving bank’s core banking system (CBS) failed to map the inbound credit to the local account automatically. Without an ARN, issuing banks cannot trace or manually reconcile unallocated inbound clearing logs stored within their SWIFT/card network settlement queues.

Root Cause Diagnosis

International card refunds pass through three distinct entities: the merchant’s acquiring bank, the card scheme network (Visa/Mastercard base II clearing networks), and the cardholder’s issuing bank. When currency conversion or cross-border clearing protocols are involved, issuing banks often fail to auto-match the incoming credit message (ISO 8583 / ISO 20022 format) to the original debit transaction ID. Consequently, the funds remain stranded in the issuing bank’s internal Nostro account or unallocated suspense ledger until an explicit manual search is executed using the 23-digit ARN generated during the clearing cycle.

Quick Fix

Contact the merchant’s billing/support team via their API or direct escalation channel and request the 23-digit Acquirer Reference Number (ARN) or Visa/Mastercard Refund Clearing Receipt. For developers or merchants using payment gateways like Stripe, query the Refund API endpoint directly:

Bash

# Retrieve ARN directly via Stripe API for a specific refund object
curl -X GET "https://api.stripe.com/v1/refunds/re_3MvX922eZvKYlo2C0X1Y2Z3A" \
  -u "sk_live_YOUR_RESTRICTED_SECRET_KEY:" \
  -G -d "expand[]=destination_details"

Step-by-Step Resolution

  1. Extract the ARN from the Merchant or Payment Gateway
    • For Customers: Request the merchant to provide the ARN/Trace ID from their merchant acquiring portal (e.g., Stripe, PayPal, Adyen, Checkout.com).
    • For Merchants/Developers: Parse the JSON response payload from your payment processor API. Ensure you fetch the nested destination_details parameter:
      JSON{ "id": "re_3MvX922eZvKYlo2C0X1Y2Z3A", "object": "refund", "amount": 15000, "currency": "usd", "destination_details": { "card": { "reference_status": "available", "reference_number": "74531232304910008432198" } }, "status": "succeeded" }
    • Note: The 23-digit string (74531232304910008432198) is the global tracking identifier.
  2. Validate the ARN Structure
    • Verify that the number matches standard card scheme formats:
      • Visa ARNs: 23 digits starting with a 7 (e.g., 7453...).
      • Mastercard ARNs: 23 digits starting with a 2 or 5 (e.g., 2422... or 5521...).
      • Amex Trace Numbers: 15-digit or 30-digit numeric strings.
  3. Submit a Formal Chargeback / Trace Dispute with the Issuing Bank
    • Submit an official written request to the issuing bank’s Chargeback & International Settlements Department (not frontline customer support).
    • Provide the ARN, refund date, original transaction date, currency amount, and original merchant ID (MID).
    • Instruct the bank’s back-office operations team to perform a Manual Base II Clearing Search using the ARN against their Visa / Mastercard Inbound Settlement Files.
  4. Escalate via Scheme Trace Request (If Funds Are Not Located)
    • If the issuing bank claims the ARN is untraceable, request them to open an official Visa VROL (Visa Resolve Online) or Mastercard MasterCom enquiry ticket.
    • Cite the ARN to compel the issuing bank to query the card scheme’s central clearing database for proof of delivery (POD) to their clearing settlement bin.
See also  Step-by-step guide to resolving unreversed authorization holds on RuPay / Visa cards

Why This Fails for Some Users

  • Refund Processed as Void/Reversal: If the refund was initiated on the same day as the original charge, the transaction was canceled before settling. In this scenario, no ARN is generated; instead, the original authorization hold is simply dropped from the statement.
  • Pending Gateway Clearing Window: Payment processors require 2 to 4 business days after triggering a refund to obtain the finalized ARN from the acquiring bank. Requesting an ARN immediately upon refund confirmation will yield a null or pending status.
  • Virtual Cards and Prepaid Instruments: Single-use virtual cards or international prepaid cards may lack direct routing tables for cross-border credit processing, causing the inbound settlement to be permanently rejected back to the merchant’s acquirer.
  • Non-Card Payment Rails: Transactions initiated via alternative international payment rails (e.g., SEPA, ACH, SWIFT wires, or local wallet schemes) do not utilize the 23-digit Visa/Mastercard ARN format and instead require an MT103 document or end-to-end ID (E2E ID).

Leave a Comment