PSD2, the EU's revised Payment Services Directive, requires payment service providers to implement strong customer authentication and secure communication for open banking APIs, with regulatory technical standards on security measures that supervisors expect to see evidenced through testing, not policy alone.
We test the payment platform, authentication flows and open banking API layer against what PSD2's security expectations actually require in practice.
We test strong customer authentication implementation, the security of open banking API access (account information and payment initiation services), and the broader payment platform, mapping findings to the RTS on strong customer authentication and secure communication.
Why it matters
Open banking APIs expose account and payment functionality by design, which makes authentication and API security the central risk PSD2 is built around. A gap in strong customer authentication or API access control is not a theoretical compliance issue — it is a direct path to account takeover and payment fraud across your customer base.
What we test
- Strong customer authentication implementation testing
- Open banking API penetration testing (AIS / PIS)
- Payment platform & transaction integrity testing
- Session & authentication security testing
- Third-party provider (TPP) access control review
- PSD2 RTS evidence pack preparation
Common vulnerabilities we uncover
- Strong customer authentication exemptions that can be abused
- Open banking APIs with insufficient authorization checks
- Payment initiation flows vulnerable to manipulation
- Weak session handling enabling account takeover
- Third-party provider access broader than PSD2 permits
- No documented evidence of security testing for supervisors
Our methodology
- Scoping & rules of engagement. We agree objectives, targets and boundaries for your psd2 security penetration testing, so testing is safe, authorized and focused on what matters to your business.
- Reconnaissance & mapping. We enumerate the full attack surface in scope, building a complete picture before any exploitation begins.
- Manual exploitation. Our senior testers chain vulnerabilities by hand — going far beyond automated scanners — to prove real, demonstrable impact.
- Analysis & reporting. Every finding is triaged, risk-rated with CVSS and written up with a copy-paste reproduction and clear remediation.
- Remediation support & free retest. We support your team through the fixes and retest the remediated issues to confirm they are genuinely closed.
Tools & techniques
We test your strong customer authentication implementation for the exemptions and edge cases attackers actually target, assess the security of your open banking APIs against unauthorized account access and payment initiation abuse, and review the broader payment platform for the controls PSD2's security RTS expects.
When you need this engagement
- You are a payment service provider regulated under PSD2
- You operate or consume open banking APIs (AIS or PIS)
- Your regulator or auditor has requested security testing evidence
- You are launching a new payment or account information service
- You need independent validation of your strong customer authentication implementation
What you receive
- Authentication & API penetration test report
- Payment platform security findings
- Third-party provider access control review
- PSD2 RTS evidence pack
- Prioritised remediation roadmap
- Free retest after remediation
What’s included in your report
Every psd2 security penetration testing engagement concludes with a comprehensive, board-ready report and a working session to walk your team through it. Your report includes:
- An executive summary with overall risk posture for non-technical stakeholders
- Detailed technical findings, each with a step-by-step, copy-paste reproduction
- CVSS v3.1 severity ratings and business-impact context for every issue
- Prioritized, actionable remediation guidance your engineers can apply directly
- A complimentary retest to confirm fixes and update finding status
- A formal attestation letter for customers, auditors and compliance programs
Standards & frameworks
PSD2 (EU 2015/2366)
RTS on Strong Customer Authentication and Secure Communication
Outcomes you can expect
After your psd2 security penetration testing, you will have clear, evidence-based visibility into your real security risk — not a scanner’s guesswork. You will know exactly which weaknesses an attacker could exploit, what the business impact would be, and the precise steps to fix them in priority order. Teams use our findings to close critical gaps, satisfy customer and regulator security requirements, and demonstrate due diligence to their board. With a complimentary retest included, you also get documented proof that the issues are genuinely resolved.
Engagement details & logistics
Every psd2 security penetration testing starts with a short, no-obligation scoping call to understand your goals, environment and constraints, followed by a fixed-price proposal and a clear statement of work. Most engagements are delivered fully remotely, with on-site work arranged where it genuinely adds value. Throughout testing we maintain an agreed communication cadence and escalate any critical, high-impact finding to you immediately rather than waiting for the final report. All work is performed under a signed NDA with strict data-handling controls, using safe, non-disruptive techniques and carefully coordinated rules of engagement to protect your production systems. On completion you receive your report and a walkthrough session, followed by a complimentary retest once your fixes are in place. Typical engagements are booked one to three weeks in advance, and urgent or pre-deadline testing can often be accommodated — just ask at hi@agentoffense.com.
Why organizations choose AgentOffense
Our psd2 security penetration testing is delivered by senior offensive-security engineers who test the way real attackers do — manually, creatively and with a relentless focus on proving genuine, demonstrable impact. Here is what sets our engagements apart:
- Manual, exploit-driven testing that chains vulnerabilities the way a real attacker would, going far beyond what automated scanners can find.
- Reproducible proof for every finding, with copy-paste reproduction steps your engineers can follow and independently verify.
- Honest severity calibration so you invest in fixing what genuinely matters and avoid wasting effort on false positives and noise.
- Clear, business-focused reporting that speaks to engineers and executives alike, tying every issue to real-world impact.
- A complimentary retest included, so you get documented proof that your fixes actually close the attack path.
- Responsible, collaborative delivery with a named point of contact and secure handling of all data throughout the engagement.
Explore related services
PSD2 Security Penetration Testing is frequently scoped alongside our other offensive-security services for broader coverage. Explore related engagements that complement it:
How much does PSD2 Security Penetration Testing cost?
Every psd2 security penetration testing is scoped and priced individually, so you pay for exactly the coverage you need — with no hidden extras. After a short, no-obligation scoping call we send a fixed-price quote, usually within one business day, with clear deliverables, a firm timeline and a complimentary retest included. The price of your psd2 security penetration testing depends on the size and complexity of the target and the depth of testing required, so you always know the cost up front before any work begins.
Get a fixed-price quote
Frequently asked questions
Does PSD2 require penetration testing?
The regulatory technical standards on security measures require robust testing of security measures and controls, which supervisors and auditors in practice expect evidenced through penetration testing, particularly of authentication and API layers.
What is the biggest PSD2-specific risk?
Gaps in strong customer authentication and open banking API authorization — these translate directly into account takeover and payment fraud, so we prioritise them accordingly.
Do you test both account information and payment initiation services?
Yes, both AIS and PIS flows are tested where they are part of your platform, since they carry different risk profiles.
How does this relate to DORA?
For payment institutions that also meet DORA's scope as financial entities, we can align a single engagement to cover both sets of evidence requirements.