Skip to content

PA security: merchant controls, authentication and data

Security obligations cover the PA, relevant merchant infrastructure and the connected payment chain.

Published by Finin2min · Updated 24 October 2026

How this provision works

Practical illustration

A PA’s vendor contract says it is a technology gateway, but the PA stores sensitive card credentials on the merchant server. The label does not make that storage compliant or postpone the PA’s cyber implementation date.

The example is illustrative; it is not a reported company or court case.

Questions answered

Is the 2024 baseline optional for a PA because it is called recommendations?

The 2025 PA annex explicitly makes its baseline mandatory for PAs and recommends adoption for pure PGs.

Does outsourcing the checkout remove the PA’s security responsibility?

No. The PA’s framework, vendor controls and regulatory accountability remain applicable.

Primary source and edition

RBI PA Directions of 15 September 2025, read with the stated current common and payment-system instruments. PA paragraph 9,10(e), Annex 1; Cyber Directions 2024 paragraphs 3–5,27; Authentication Directions 2025 paragraphs 3–10.

Open the official instrument at this provision

Legal effect follows the instrument’s commencement and amendment provisions; a website upload date does not by itself change the law.

Related primary authorities

Scope and source editions

Reviewed against the named official editions on 24 October 2026. Product, regulated entity, transaction type and the instrument’s commencement or saving provisions determine applicability. Examples are illustrations rather than reported company cases.

Related resources and source collections

Further reading and resources