Law / Canada

Retail Payment Activities Regulations, Risk Management and Incident Response Framework

Retail Payment Activities Regulations, ss. 5-10 (SOR/2023-229)

In force since .

A sector security regimes rule binding private bodies.

Instrument type
a regulation made under an act
Obligation class
Security, Governance

What it requires

  • This binds a payment service provider that performs retail payment activities and has to maintain the framework that section 17(1) of the Retail Payment Activities Act requires; banks, credit unions, insurers and certain other institutions are outside that Act (section 9 of the Act) (reached by declaring that you are a payment provider).
  • Keep the risk management and incident response framework in writing, with reliability targets for the ability to perform retail payment activities and for the availability of the systems, data and information involved, and indicators for whether each objective is met (section 5(1)(a) and (b)).
  • Identify the systems, data, information and business processes used for retail payment activities and classify them by sensitivity and criticality (section 5(1)(e)).
  • Identify your operational risks, including cybersecurity, fraud, information technology, change management and third-party risks, describe the controls that mitigate them, and describe the continuous monitoring that detects incidents and lapses (section 5(1)(f) to (h)).
  • Set out a plan for responding to and recovering from incidents, including those involving or detected by an agent or a third-party service provider, and keep a record of each incident (section 5(1)(i)).
  • If a third-party service provider supplies a service related to a payment function, assess at least once a year, and before entering, renewing, extending or substantially amending the contract, its ability to protect your data, the security of its connections to your systems, how it will tell you of a detected breach, and its risk management practices; keep a record of each assessment; and allocate responsibility for the ownership, integrity, confidentiality and availability of data (section 5(3)).
  • Have the framework approved at least once a year by the senior officer and by the board of directors, where you have them (section 5(6)).
  • Review the framework at least once a year and before a material change, and keep a record of each review (section 8).
  • Establish and implement a testing methodology that is proportionate to the impact of a breakdown of your retail payment activities, set the frequency and scope of testing, test before material changes, and keep a record of each test (section 9).
  • If you have an internal or external auditor, have a sufficiently skilled individual with no role in the framework carry out an independent review at least once every three years (section 10(1)).
  • Make the framework available to everyone with a role in it, protect it from unauthorized deletion, destruction or amendment, and give those people the information and training they need (sections 6 and 7).

These lines are LexLint's reading of the law's text.

If you get it wrong

Penalty structure

Section 48(1) of the Regulations caps the penalty at $1,000,000 for a serious violation and $10,000,000 for a very serious violation; a contravention of section 17(1) of the Act is very serious.

Rule
Fixed only
As of
Currency
CAD
Fixed cap
10,000,000

Who enforces it

Enforcement body

The Bank of Canada, which may assess a payment service provider’s risk management and incident response framework and issue a notice of violation under the Act’s administrative monetary penalty scheme.

Settledness

As of

What this law does

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

Research summary

Legal information, not legal advice. This is LexLint's own research summary of a public legal source, and it creates no attorney-client relationship. For decisions that matter, consult qualified counsel in the relevant jurisdiction. About LexLint

Section 5(1) of the Retail Payment Activities Regulations requires the risk management and incident response framework that the Act calls for to be in writing and sets out what it must contain. The framework must identify the assets, including systems, data and information, and the business processes associated with retail payment activities and classify them according to their sensitivity and their criticality.

The framework must identify the operational risks, including those relating to cybersecurity, fraud, information technology, change management and third parties. Where a payment service provider receives services related to a payment function from a third-party service provider, the framework must address an assessment at least once a year of that provider’s ability to protect data and the security of its connections to the provider’s systems.

A payment service provider must review the framework at least once a year and before making a material change to its operations or systems. A payment service provider must establish and implement a testing methodology to identify gaps in the effectiveness of, and vulnerabilities in, the systems and controls the framework provides for.

A payment service provider that has an internal or external auditor must have a skilled individual with no role in the framework carry out an independent review of it at least once every three years. A contravention of section 17(1) of the Act is classified as a very serious violation. Sections 5 to 23 of the Regulations came into force on .

When LexLint raises it

When your app profile says your app is a payment provider.

Back to the example  ·  Lint your app

Page updated .