RBI system audit for non-bank payment operators: evidence to prepare
What to collect for an RBI system audit under the 2026 non-bank payment operator directions, from access and supplier records to recovery drills and closure evidence.
- Published
- Reading time
- 2 min
On this page (3)
The Reserve Bank of India’s 5 November 2026 Master Directions give authorised non-bank payment system operators a single reference for cyber resilience, digital payment security and system audit. They consolidate earlier directions and audit guidance. Section V asks auditors to examine both whether a control is designed to address the risk and whether it actually worked. That distinction should shape the evidence your team collects before the audit.
Confirm which obligations govern the payment flow
The revised directions apply on publication to large and medium authorised non-bank payment system operators. For small authorised non-bank operators, paragraph 3 gives an effective date of 1 April 2028. Check your operator category against the directions and map any separate obligations that apply to the services you provide. Keep payment-data localisation obligations separately mapped where they apply.
Keep any conditions in your authorisation letter on a separate list from recurring audit obligations. Record the source of each requirement, the entity and service it covers, who owns it and when evidence is due.
Collect evidence from a real operating period
Start with a payment flow your team is responsible for, from initiation through reconciliation. Use the incident, change and access records your teams already produce to show what happened along that flow.
| Control area | Evidence to have ready |
|---|---|
| Privileged access | Keep the approved access request, the actual role granted, a record of its use and evidence of removal when the need ended. Check that records from the payment platform and identity system agree. |
| Supplier oversight | Keep the agreement and the map of services and dependencies. For one issue raised during the audit period, show who assessed it, what the supplier did and how your team verified the result. |
| Recovery | Keep the business continuity drill record. It should show the service restored, when it became usable and how the payments team checked that transaction records could be reconciled. |
| Change management | Connect the approved change to the artefact that reached production, the verification record and any exception. If a change altered a process submitted at authorisation, tell the auditor which flow changed. |
These are examples of evidence your team can gather. Confirm the audit scope with the auditor against the directions and your authorisation. Use redacted records or appropriate test data when preparing examples.
Give each audit observation an owner and closure evidence
Section V requires the System Audit Report and compliance status to go to the board. For an open observation, paragraph 41 calls for specific corrective action within a maximum of three months, reporting to RBI and acceptance by the auditor before closure. Track the corrective action, deadline and evidence in one record. If a privileged account was removed, for example, retain the evidence that access ended in the relevant systems and give the auditor enough context to verify it.
Source: Reserve Bank of India, Master Directions on Cyber Resilience and Digital Payment Security Controls for non-bank Payment System Operators, 5 November 2026, RBI/DPSS/2026-27/475, especially paragraphs 3–5 and 36–41.
Continue reading
All articles →IFSCA cyber security certification: who needs Basic and Advanced, and when
Which GIFT IFSC roles need Basic and Advanced cyber security certification, how to calculate each deadline, and what evidence to maintain.
API security testing for IFSC banking units with fintech partners
Use the IFSCA internet banking FAQ to scope tests for partner API access and scheduled payouts, from onboarding through revocation.
CERT-In AI Security Auditing Guidelines: prepare evidence for the deployed system
A practical starting point for enterprise AI audit preparation: map the deployed workflow, test its authority and assemble evidence that explains what happened.