Card Transaction Evidence: RBI Traceable Records, Immediate Customer Records and Reversal Reconciliation

The customer record and issuer audit trail serve different purposes

The current issuer-specific RBI card Directions require internal records that enable operations to be traced and errors rectified, taking account of limitation and the relevant issuer-specific KYC record framework. They also require an immediate record after a completed transaction, in receipt or another stated form such as statement, email or SMS. These requirements appear in paragraphs 64–65 of the Commercial Bank, Small Finance Bank and Urban Co-operative Bank Directions, and paragraphs 58–59 of the NBFC credit-card Directions. This guide, checked on 27 October 2026, separates them from disputed-transaction liability and failed-payment compensation. The cited Commercial Bank and Small Finance Bank versions are updated on 1 October 2026. Commercial Banks: paragraphs 64–65; Small Finance Banks: paragraphs 64–65; Urban Co-operative Banks: paragraphs 64–65; NBFC credit cards: paragraphs 58–59.

Apply the directions within their stated scope

Identify the issuer and product before applying the current Directions. The Commercial Banks Directions exclude Small Finance Banks, Payments Banks and Local Area Banks from that defined class; Small Finance Banks and Urban Co-operative Banks have separate cited Directions. The NBFC Directions cover their specified NBFC classes and credit-card business requires prior RBI permission. For another issuer class, including State or District Central Co-operative Banks, establish its applicable current framework separately. Do not mechanically extend these card provisions to prepaid instruments. For corporate cards, retain the employee/card reference and transaction purpose without assuming that an employee expense claim is the issuer’s complete operational record. The 2022 Master Direction, updated 7 March 2024, is retained as historical background; its combined scope and paragraph 23 numbering are not the current references used in this guide.

Identify one transaction across the evidence chain

Connect the authorisation or transaction reference, date/time, merchant, amount, currency, customer record, posting and any reversal. Different references or descriptors may relate to the same underlying event. Conversely, equal amounts at the same merchant are not enough to prove duplication. A message evidencing an attempted authorisation should not be labelled a completed settlement without checking the actual status.

Reconcile receipts and alerts to the posted statement

Classify pending, posted, reversed and disputed items separately. Preserve the original record and any corrected entry rather than overwriting the initial amount. Check whether a reversal is partial and whether the statement spans a different cut-off. A corporate accounting team should link the posted amount to the expense evidence and identify personal or unexplained transactions, but accounting approval does not establish customer consent or settle a fraud dispute. RBI Commercial Banks Directions: paragraphs 64–65 (see issuer-specific references below).

Do not invent a universal retention period or refund entitlement

The internal-record provisions—paragraph 64 for the cited Commercial Bank, Small Finance Bank and Urban Co-operative Bank Directions, or paragraph 58 for the NBFC Directions—refer to the relevant issuer-specific 2025 KYC Directions, as amended, and take account of limitation. Establish the current relevant record class and preservation duties before destruction; this article does not prescribe one arbitrary number of years for every card record. Nor does an evidence difference by itself establish an automatic compensation amount. Use the applicable failed-transaction or customer-protection framework and facts for that separate enquiry.

Close errors with a reproducible record

For each exception identify the original event, the alleged error, issuer response, correction reference and final posted amount. Reconcile multiple complaint IDs to the underlying event, and retain the customer-facing record and issuer outcome. Protect sensitive credentials: ordinary reconciliation evidence should not circulate PINs or authentication secrets. A working that adds up but lacks a transaction identity cannot reliably distinguish correction, refund and a new purchase. RBI Commercial Banks Directions: paragraphs 64–65 (see issuer-specific references below).

Applicable primary references

RBI Commercial Banks Directions: paragraphs 64–65 (see issuer-specific references below)

Six worked illustrations

All facts and amounts below are fictional. Assumptions describe the model, not additional statutory rules.

Illustrative example 1: One partial reversal

A completed transaction is ₹8,000 and an identified partial reversal is ₹3,000. The unreversed posted amount is ₹5,000. Retain both events rather than replacing the original transaction with a new ₹5,000 history.

Illustrative example 2: Duplicate import

A single ₹12,000 transaction is imported twice under the same proven transaction reference. The import total ₹24,000 exceeds the underlying event by ₹12,000. This finding does not prove the issuer debited twice.

Illustrative example 3: Same amount, different transactions

Two separately evidenced purchases of ₹2,500 each total ₹5,000. Removing one merely because amounts match would understate the population by ₹2,500.

Illustrative example 4: Receipt-to-statement gap

Receipts for the tested population total ₹45,000, while linked postings total ₹47,000. The ₹2,000 difference needs transaction-level investigation; it is not automatically an undisclosed bank fee.

Illustrative example 5: Cut-off separation

At the review date there are posted purchases ₹30,000 and pending authorisations ₹7,000. Keep the two statuses visible. Reporting ₹37,000 as finally posted overstates the identified posted population by ₹7,000.

Illustrative example 6: Correction completeness

Of 20 exceptions, 15 have a supported final correction and 5 remain open. Closure is 75% of the population. The remaining 25% is a management follow-up metric, not a regulatory permitted error rate.

Ten-step verification table

Step	Action	Evidence
1	Identify the covered product and issuer	Directions’ actual scope.
2	Capture the customer record	Receipt, email, SMS or other completed-transaction record.
3	Link transaction identifiers	Merchant, date, amount and reference.
4	Determine status	Pending, posted, reversed or disputed.
5	Reconcile statement postings	Cut-off and exact population.
6	Test duplicate imports	Same event versus separate equal-value purchases.
7	Trace reversals	Original reference, partial/full amount and posting date.
8	Investigate differences	Issuer explanation and supporting evidence.
9	Apply preservation controls	Relevant KYC/limitation and other duties.
10	Close with proof	Correction reference and reproducible final reconciliation.

Sixteen practitioner FAQs

1. What does the internal-record provision address?

Internal records for traceability and error rectification under its stated framework.

2. What does the customer-record provision require?

An immediate record after a completed transaction in receipt or another stated form.

3. Must every record be on paper?

The provision recognises other forms including statement, email or SMS.

4. Is an authorisation alert always final settlement?

No. Establish the transaction’s actual status.

5. Can matching amounts prove duplicates?

No. Compare identifiers and evidence.

6. Does a duplicate accounting import prove two bank debits?

No. Reconcile the issuer’s actual postings.

7. Can a reversal be partial?

Yes. Preserve the amount and original-event linkage.

8. Should pending amounts be reported as posted?

Keep the statuses separate unless actual posting is established.

9. Does a difference establish an undisclosed fee?

No. Investigate its actual cause.

10. Does an accounting approval establish transaction consent?

Not by itself.

11. Does this guide decide fraud liability?

No. Apply the separate applicable customer-protection framework.

12. Is there one universal retention period stated here?

No. Determine the relevant KYC and other preservation requirements.

13. Are prepaid instruments covered identically?

Do not substitute these card provisions for the separate prepaid framework.

14. Should sensitive PINs be in shared working files?

No. Use appropriate masked transaction evidence.

15. Can complaint references be combined for one event?

Link them while preserving each communication history.

16. What proves correction?

The issuer outcome, correction reference and reconciled final posting.

Conclusion

Link card transaction records to issuer operations, statements and reversals under RBI’s issuer-specific card Directions, without treating an alert as proof of final settlement.