A tailored course, built for your situation
Influence across more business lines with PSD2
A 199 course to extend your PSD2 expertise beyond compliance and into cross-functional leadership
Who this is for
Senior Business Analyst in financial services driving PSD2 implementation across credit cards and payment systems
Who this is not for
Entry-level analysts, developers without regulatory scope, or professionals outside payment services
What you walk away with
- Lead PSD2 initiatives that span business units and technical domains
- Translate compliance mandates into clear, actionable workflows for engineering teams
- Build trusted partnerships with product, legal, and fraud teams around common artefacts
- Deliver customer-facing payment features faster without compromising compliance
- Establish yourself as the go-to practitioner when new markets or lines of business adopt PSD2
The 12 modules (with all 144 chapters)
- Defining the PSD2 scope per business line
- Mapping access rights to cardholder journeys
- Shared services vs local implementation
- Customer authentication across geographies
- Common misconceptions in credit card tokenisation
- How payment initiation differs in B2B context
- Role of ASPSPs in multi-brand structures
- Handling legacy systems under RTS
- Interpreting XS2A for internal platforms
- Balancing customer experience with SCA
- Data sharing obligations across regions
- Common gaps in fraud monitoring design
- Breaking down SCA into testable criteria
- Working with developers on exemption logic
- Clarifying whitelisting for operations
- Mapping consent models to UI patterns
- Documenting AISP vs PISP access flows
- Aligning fraud logs with regulatory expectations
- Translating 90-day re-authentication
- Explaining dynamic linking to product teams
- Clarifying fallback mechanisms
- Handling certificate lifecycle discussions
- Negotiating liability boundaries
- Standardising incident reporting triggers
- Identifying decision owners early
- Creating shared definitions across silos
- Running effective exception workshops
- Presenting trade-offs without bias
- Using journey maps to align teams
- Managing conflicting timelines
- Building consensus on edge cases
- Avoiding rework with pre-sign-off
- Tracking open items in one source
- Communicating changes without noise
- Running post-implementation reviews
- Documenting rationale for future reuse
- Template architecture for ASPSP interfaces
- Localising SCA without fragmentation
- Common integration points with core banking
- Handling multi-currency payment initiation
- Building regional exemptions matrices
- Scaling certificate management
- Designing for cross-border AISP use
- Managing sunset paths for legacy APIs
- Configuring monitoring per jurisdiction
- Standardising audit trails
- Testing compliance at scale
- Documenting local adaptations
- Writing testable acceptance criteria
- Building API specs with compliance baked in
- Creating fraud monitoring rulesets
- Designing SCA exemption checklists
- Documenting customer journey breakpoints
- Specifying consent storage formats
- Mapping data flows for DPIA
- Building audit-ready logs
- Defining fallback authentication paths
- Creating cross-team onboarding packs
- Versioning compliance artefacts
- Automating control checks
- Positioning PSD2 as enabler not blocker
- Finding natural allies in product teams
- Using data to show implementation cost
- Reframing resistance as input
- Building credibility through precision
- Escalating only when necessary
- Maintaining neutrality in disputes
- Creating shared success metrics
- Celebrating small wins publicly
- Documenting decisions to prevent rework
- Staying visible across delivery cycles
- Owning the narrative without title
- Positioning PSD2 in open banking roadmap
- Connecting to instant payments evolution
- Preparing for PSD3 anticipation
- Supporting embedded card features
- Enabling third-party value creation
- Defending against fintech disintermediation
- Building API monetisation guardrails
- Balancing innovation with compliance
- Tracking regulatory sandboxes
- Influencing platform architecture
- Planning for AISP-led product models
- Future-proofing access control models
- Measuring SCA impact on conversion
- Designing customer-friendly fallbacks
- Communicating authentication changes
- Reducing friction in card-on-file flows
- Building trust through transparency
- Testing messaging with real users
- Handling customer support escalations
- Optimising exemption usage fairly
- Tracking false decline patterns
- Reporting customer impact to leadership
- Balancing fraud reduction with CX
- Improving first-time success rates
- Defining liability shift triggers
- Monitoring for AISP misuse
- Detecting bulk account access
- Logging for dispute resolution
- Establishing fraud thresholds
- Responding to unauthorised payments
- Building forensic data packages
- Validating third-party behaviour
- Detecting credential stuffing
- Assessing AISP risk profiles
- Reporting fraud trends to regulators
- Updating detection logic iteratively
- Assessing AISP compliance posture
- Evaluating PISP security practices
- Reviewing certificate management
- Auditing third-party logs
- Managing certificate lifecycle risks
- Setting up monitoring for external access
- Establishing access revocation paths
- Handling onboarding at scale
- Negotiating technical SLAs
- Building partner accountability
- Creating exit strategies
- Maintaining independence in assessment
- Building evidence as you go
- Mapping controls to EBA guidance
- Documenting exemption logic clearly
- Preparing for supervisory review
- Creating regulator-facing summaries
- Demonstrating SCA effectiveness
- Showing customer communication
- Proving fraud monitoring coverage
- Verifying certificate compliance
- Presenting testing results
- Updating playbooks for inspections
- Anticipating follow-up questions
- Creating internal training packs
- Building self-service guidance
- Developing checklists for new hires
- Standardising implementation patterns
- Running peer review sessions
- Mentoring junior analysts
- Documenting decision precedents
- Sharing playbooks across regions
- Creating audit feedback loops
- Improving onboarding speed
- Reducing rework through clarity
- Establishing community of practice
How this maps to your situation
- Leading multi-unit PSD2 rollout
- Aligning technical and business stakeholders
- Preparing for audit or review
- Scaling best practices across regions
Before vs. after
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters)
- Downloadable templates and worked examples for every module
- Hand-built implementation playbook delivered alongside course access
- 30-day money-back guarantee
Delivery and format
- Course and learning environment access provisioned within 24 hours of purchase
- Hand-built implementation playbook delivered alongside course access
Format: Text-based modules and chapters in the Art of Service learning environment, plus downloadable templates and worked examples for every chapter, plus the hand-built implementation playbook delivered alongside course access.
Time investment: Approximately 3 hours per module, designed to be consumed in parallel with ongoing work.
How this compares to the alternatives
Unlike generic compliance courses, this focuses exclusively on PSD2 in complex, multi-line banking environments, exactly the context where influence matters most.
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.