Incident to report to a regulator?Incident to report? Intake Line

PSD2Revised Payment Services Directive regulatory technical standardsDetailed requirements drafted by the European Supervisory Authorities and adopted by the Commission to specify how a regulation applies. DORA relies on RTS for topics such as threat-led penetration testing.

PSD2 SCA Audit

The PSD2Revised Payment Services Directive regulatory technical standardsDetailed requirements drafted by the European Supervisory Authorities and adopted by the Commission to specify how a regulation applies. DORA relies on RTS for topics such as threat-led penetration testing. require your strong customer authenticationAuthentication based on two or more independent elements from knowledge, possession and inherence. PSD2 requires payment service providers to apply it, for example when a payer accesses an account online or starts an electronic payment, subject to the applicable exemptions. measures to be documented, tested, evaluated and audited by auditors who are operationally independent and know ITInformation Technology security and payments. We carry out that audit, and the yearly audit of your transaction risk analysisIn EU payment requirements, a real-time assessment used to identify low-risk remote electronic payments that may qualify for an exemption from strong customer authentication, normally a check using at least two independent factors. The assessment considers spending patterns, devices, locations and fraud indicators. Use of the exemption also depends on payment-value limits and the provider's fraud rates. The methodology, model and reported fraud rates require at least annual independent audit. exemption, and give you a report your competent authority can rely on.

Download the Service Sheet (PDF)

Request a PSD2 SCA Audit Proposal

We respond within two working days. Once the scope is clear, we prepare your written proposal.

Request a PSD2 SCA Audit Proposal
Add assessment details (optional)
Channels in scope
  • Fixed fee, agreed in your proposal before we start
  • Next available start: week of Monday 23 November

We use your details only to prepare your proposal and treat your answers as confidential; we sign your NDA on request. Privacy notice

500+ Regulations Laws and standards
40 Countries Europe, Gulf, Asia and North America
25+ Years In regulated sectors
9 Industries From banking to healthcare

WHY YOU NEED THE AUDIT

SCA has to be audited, not only built

Article 3 of the RTSRegulatory Technical Standards asks for an independent audit of your security measures; Article 18 adds a yearly audit if you use the transaction risk analysisIn EU payment requirements, a real-time assessment used to identify low-risk remote electronic payments that may qualify for an exemption from strong customer authentication, normally a check using at least two independent factors. The assessment considers spending patterns, devices, locations and fraud indicators. Use of the exemption also depends on payment-value limits and the provider's fraud rates. The methodology, model and reported fraud rates require at least annual independent audit. exemption.

The problem

Your own team cannot audit what it built

The RTSRegulatory Technical Standards require auditors who are operationally independent and have expertise in ITInformation Technology security and payments.

  • Your competent authority can ask for the audit report at any time
  • Fraud rates above the reference rates cost you the TRA exemption
  • New channels and apps change what has to be tested

The solution

An independent audit against the RTS

We test each requirement on your channels and review the exemptions you rely on, with evidence for every conclusion.

  • Requirement-by-requirement testing
  • Fraud-rate calculations and the TRA model reviewed
  • Findings with practical recommendations

The outcome

A report you can hand to your regulator

You keep your exemptions with confidence and answer your competent authority with an audit that meets the RTSRegulatory Technical Standards.

  • Audit report available on request
  • Exemptions backed by evidence
  • A clear list of what to improve

What we check

What we audit

For each requirement we review the evidence and check that the control works, so you know exactly where you stand.

Authentication and dynamic linking

The two independent elements, how codes are generated and linked to amount and payee, and what happens after failed attempts.

Sessions, channels and devices

Session time-outs, the security of the devices and apps that carry an element, and the channels where SCAStrong Customer Authentication applies.

Exemptions you rely on

Low-value, trusted beneficiaries, recurring payments and, above all, transaction risk analysisIn EU payment requirements, a real-time assessment used to identify low-risk remote electronic payments that may qualify for an exemption from strong customer authentication, normally a check using at least two independent factors. The assessment considers spending patterns, devices, locations and fraud indicators. Use of the exemption also depends on payment-value limits and the provider's fraud rates. The methodology, model and reported fraud rates require at least annual independent audit.: methodology, model and reported fraud rates.

Each finding with a recommendation

Every gap comes with its risk, the RTSRegulatory Technical Standards article it concerns and a practical recommendation for your teams.

HOW THE AUDIT RUNS

From scoping to audit report

The phases are the same for every payment service providerUnder PSD2, a provider in the statutory categories listed in Article 1(1), or a person exempt under Articles 32 or 33, that provides payment services. The business model and transactions determine the applicable authorisation or registration requirements and when strong customer authentication is required, subject to the relevant exemptions.; their length follows the channels and exemptions in scope, and your proposal gives the dates.

A typical engagement
  1. Scoping

    Scoping

    Channels, authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. methods, exemptions and providers in scope, agreed in a short call.

  2. Evidence

    Documents and data

    Security policies, authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. flows, configuration and the fraud data behind your exemptions.

  3. Testing

    Testing

    Walkthroughs and tests of authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence., dynamic linkingA payment-authentication safeguard that binds approval to a specific payment amount and recipient. The payer is shown those details, and the authentication code must correspond to what the payer agreed. Changing the amount or recipient invalidates that code. Under the PSD2 technical requirements, this protects remote electronic payments against approval being redirected to a different transaction; it does not prescribe one particular technology. and sessions on each channel.

  4. Findings

    Draft findings

    You see every conclusion before it is final and can add evidence.

  5. Report

    Audit report

    The report for your management and your competent authority.

A guide, not a fixed promise: the length of each phase depends on your scope and on how quickly evidence and people are available.

WHEN TO START

Plan the audit around your fraud reporting

Two audits follow a calendar: the audit of your security measures, on the cycle your audit framework sets, and, if you use the exemption, the yearly audit of transaction risk analysisIn EU payment requirements, a real-time assessment used to identify low-risk remote electronic payments that may qualify for an exemption from strong customer authentication, normally a check using at least two independent factors. The assessment considers spending patterns, devices, locations and fraud indicators. Use of the exemption also depends on payment-value limits and the provider's fraud rates. The methodology, model and reported fraud rates require at least annual independent audit..

The calendar that sets your timing
  1. Every quarter

    Monitor fraud rates

    Fraud rates per payment type against the reference rates; two quarters above them and you must stop using the exemption and tell your authority.

  2. Every year

    Report fraud data

    Statistical fraud data to your competent authority, at least once a year.

  3. Every year

    Audit the TRA exemption

    Methodology, model and reported fraud rates, audited at least yearly while you use the exemption.

  4. Audit cycle

    Audit the security measures

    At the interval your audit framework sets, and before you rely on a new channel or method.

Based on RTSRegulatory Technical Standards (EU) 2018/389, Articles 3, 18, 20 and 21, and PSD2Revised Payment Services Directive Article 96(6).

YOUR PSD2 SCA AUDIT

Plan the audit before your next reporting date

Tell us which channels and exemptions are in scope. We send a written proposal with scope, dates and a fixed fee within two working days.

WORKING WITH US

What it takes from your side

Your team's time, how quickly we start, and how the work is organised.

From your go-ahead to kick-off

We start within days, so the audit fits your reporting calendar.

No travel costs

Walkthroughs by video call and screen share; on-site days only when you want them.

A single evidence list

One list mapped to the RTSRegulatory Technical Standards articles, so your teams gather each item once.

What you receive

The audit report

Scope, method and a conclusion for each RTSRegulatory Technical Standards requirement, with the evidence behind it.

PDF

The TRA exemption review

Methodology, model and fraud-rate calculation checked against Article 18 and the reference rates.

Section of the report

Findings and recommendations

Each gap with its risk, the article concerned and a practical recommendation.

Excel finding list

A management summary

The overall result and the decisions management needs to take.

Presentation and a closing call

Why payment service providers choose GRC+

Payments and IT security in one team

The RTSRegulatory Technical Standards ask for both kinds of expertise; our auditors bring them together on every audit.

Independent of your operations

We do not build or run your authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence., so the audit meets the independence the RTSRegulatory Technical Standards require.

Fraud data checked, not taken on trust

We recompute your fraud rates from the underlying data and compare them with the reference rates.

Ready for PSD3 and the PSR

We tell you which findings the new payment services requirements affect, so fixes last.

Credentials

Who does the work

Certified practitioners

Every engagement is led by a senior, certified practitioner.

CIPP/E CISSP CISA CISM

25+

years in regulated sectors

Banks, insurers, payments, healthcare and the public sector across the globe.

Insured

Professional indemnity cover on every engagement.

FAQ

PSD2 SCA audit: frequently asked questions

Something else? Ask us in a 30-minute call.

Book a 30-Minute Call

What does the audit cost?

A fixed fee, set in your written proposal before any work starts. It follows the entities, systems and sections in scope.

How often must the PSD2 SCA security measures be audited?

The RTSRegulatory Technical Standards leave the audit period to your audit framework, taking into account your accounting and statutory audit cycle. If you use the transaction risk analysisIn EU payment requirements, a real-time assessment used to identify low-risk remote electronic payments that may qualify for an exemption from strong customer authentication, normally a check using at least two independent factors. The assessment considers spending patterns, devices, locations and fraud indicators. Use of the exemption also depends on payment-value limits and the provider's fraud rates. The methodology, model and reported fraud rates require at least annual independent audit. exemption, the methodology, the model and the reported fraud rates must be audited at least once a year.

Who can perform the PSD2 SCA audit?

Internal or external auditors who have expertise in ITInformation Technology security and payments and are operationally independent of the functions they audit.

Who receives the PSD2 SCA audit report?

The report stays with you and must be made available to your competent authority on request. We write it with that reader in mind.

Do we need a separate audit for the transaction risk analysis exemption?

If you use the exemption, Article 18 of the RTSRegulatory Technical Standards requires the methodology, the model and the reported fraud rates to be audited at least once a year. We can combine it with the audit of your security measures or run it on its own.

Can the audit cover several channels and brands?

Yes. We scope each channel, app and brand that carries strong customer authenticationAuthentication based on two or more independent elements from knowledge, possession and inherence. PSD2 requires payment service providers to apply it, for example when a payer accesses an account online or starts an electronic payment, subject to the applicable exemptions. and report on them in one audit, with the differences stated.

Want to know more about PSD2?

Our guide to PSD2 explains who it applies to, what it requires, the deadlines and what happens if you do not comply. Revised Payment Services Directive (PSD2) →

Plan your PSD2 SCA audit

Tell us which channels, authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. methods and exemptions are in scope, and when your report is due. We send a written proposal with scope, dates and a fixed fee. sales@grc.plus +31 20 241 66 00

Related: Penetration TestingDORA Compliance AuditSource Code Review

Not ready to talk yet? Read our PSD2 guide →

Loading the form…