Last Updated: 10 November 2026
Quick Summary
PSD2 regulatory reporting for fintech startups means sending your competent authority the notifications, evidence files and periodic returns that prove you meet the Payment Services Directive. It covers three layers: authorisation evidence, ongoing supervision, and event-driven reporting such as major incidents and fraud data. Your duties depend on your business model and authorisation status, not on what you call yourself.
- Map each obligation to your business model, then confirm your position with your competent authority.
- A registered AISP reports less than a payment institution, but registration maintenance and incident notification still apply.
- Build a control register listing each system, its control, how you test it and how often.
- Prepare a standing incident template with detection, classification and notification times before you need it.
- If you operate in the UK and the EU, run two reporting calendars with separate portals and logins.
What PSD2 Regulatory Reporting Means for a Fintech Startup
PSD2 regulatory reporting for fintech startups is the set of notifications, evidence files and periodic returns a licensed or registered provider must send to its competent authority to prove it meets the Payment Services Directive.
This guide maps each obligation to your business model, then shows the deadlines, data fields and submission routes that apply.
There are three layers:
- Authorisation evidence: the application pack and the documents behind it
- Ongoing supervision: periodic returns, notifications of change and financial statements
- Event-driven reporting: major incidents and fraud data
Miss the third layer and you can face supervisory action even with a clean application.
PSD2 Reporting Requirements: What Competent Authorities Expect
Competent authorities expect a complete, consistent evidence trail. Every claim in your application must be backed by a document you can update later.
A common mistake is writing the application as a one-off sales pitch.
Expect scrutiny in four areas:
- Governance and named responsible persons
- Safeguarding of client funds, where relevant
- Operational and security controls
The European Banking Authority's PSD2 guidance sets the supervisory expectations most national regulators follow. Read your own competent authority's page first, then use the EBA material to fill gaps.
Licensing, Authorisation and Ongoing Supervision
Licensing is a threshold, not a finish line. A payment institution needs authorisation before providing payment services; an AISP has a lighter registration route in most member states. Supervision continues after the licence is granted.
Ongoing supervision typically means:
- Annual or periodic reporting returns
- Notification of changes to directors, systems or business plan
- Financial statements filed on the regulator's timetable
Keep a single source of truth for these facts, so a director change updates three documents the same day.
Strong Customer Authentication and Open Banking Evidence
Strong Customer Authentication is the two-factor check applied when a customer accesses their payment account or initiates a payment.
Open banking evidence applies the same idea to third-party access. If you rely on another provider's consent flow, document that dependency.
What supervisors look for:
- A written description of your authentication flow
- Test results showing the flow works as described
- Logs proving authentication events are recorded
Read-only access has its own security model, and you must be able to evidence it. Our guide to read-only open banking security explains the controls.
Mapping Obligations to Your Business Model and Authorisation Status
Your reporting duties depend on what you do, not what you call yourself. A registered AISP and a fully licensed payment institution carry very different loads, and the same product can fall into different categories depending on how it is built and who holds the client relationship.
| Business model | Authorisation route | Core reporting load |
|---|---|---|
| Account information only | Registration as AISP | Periodic returns, incident notices |
| Payment initiation only | Authorisation as PISP | Returns, safeguarding evidence, incident notices |
| Card or credit issuing | Authorisation as payment institution | Full returns, financial statements, fraud data |
| Bank connectivity inside a SaaS product | Usually via a licensed partner | Partner due diligence, incident escalation |
| Internal tool, no client funds | Often out of scope | Contract and data protection only |
The last two rows matter most for startups. Many SaaS and ERP vendors assume they need a licence when a partner route is cleaner. Others assume they are out of scope when they are not.
A decision path for early-stage teams
Work through these questions in order. The first one that applies usually determines your route.
- Do you hold client funds or settle payments for third parties? If yes, you are likely a payment institution or electronic money institution and should plan for full authorisation and ongoing returns.
- Do you initiate payments on behalf of a user without holding funds? If yes, you are likely a PISP and need authorisation plus safeguarding evidence where relevant.
- Do you only read account data with the user's consent? If yes, you are likely an AISP and need registration, incident notification and cooperation with supervision.
- Do you connect to banks inside a product where a licensed provider holds the permissions? If yes, you are probably on the partner route, with duties around due diligence, consent records and incident escalation.
- Do you process payment data only as an internal tool with no client funds and no third-party access? If yes, you may be out of scope for PSD2 authorisation, but data protection and contract duties still apply.
Watch out: assuming a licensed partner removes all reporting duties. You still need to vet the provider, keep consent records and document your escalation path.
Mapping by authorisation status
- Pre-application: evidence gathering, governance design, safeguarding arrangements and a documented business plan.
- Application: the full authorisation pack, including programme of operations, evidence of initial capital where required, and descriptions of controls.
- Post-authorisation: periodic returns, notifications of change, financial statements and incident reporting.
Jurisdiction routing
If you operate in both the UK and the EU, map each obligation to the correct regulator and portal. The Financial Conduct Authority is the UK competent authority; in the EU it is your national competent authority. Reporting routes, formats and some thresholds differ, so run two calendars. For a plain explanation of UK open banking in practice, see our guide to open banking in the UK.
What to do with the map
Turn the row that applies to you into a one-page obligations register: the return, the owner, the deadline, the portal and the evidence file. Review it quarterly and whenever your business model changes.
PSD2 Reporting for Account Information Service Providers
Account information service providers report less than payment institutions, but reporting is not optional. The core duties are registration maintenance, incident notification and cooperation with supervision.
A registered AISP must typically keep its registration details accurate, notify the regulator of material changes, report major incidents within the required window and cooperate with supervisory requests for information.
Your evidence should prove three things: consent was obtained, access was limited to the consented accounts, and data was not used beyond the agreed purpose.
Building that evidence is a development task as much as a compliance one. If you are weighing the engineering side, our PSD2 API integration guide for startups covers the practical build.
PSD2 Operational and Security Risk Assessment: Building the Evidence
A risk assessment is only useful if it produces artefacts a supervisor can inspect.
Build the evidence in this order:
- List every system that touches payment account data
- Name the control protecting each one
- Record how you test that control and how often
- Store the output where you can retrieve it on request
- Review the register at least quarterly
Most startups already have the technical controls; what they lack is the trail. A control nobody documented may as well not exist for supervisory purposes.
If you need a structured route to that trail, our finance data security roadmap sets out controls across a 30-, 90- and 180-day plan.
Watch out: treating the risk assessment as a document you write once at authorisation. Maintaining this level of operational rigour serves as a vital foundation for any firm navigating the complexities of FCA Authorisation.
PSD2 Major Incident Reporting: Deadlines, Data Fields and Submission Routes
Major incident reporting is the obligation startups most often get wrong, usually because nobody owns it until something breaks. A major incident is an operational or security event affecting the availability, integrity or confidentiality of payment services.

What counts as a major incident
Competent authorities generally follow the EBA's guidelines on major incident reporting, which set out classification criteria rather than a single threshold. In practice, a startup should treat an event as potentially major if it meets any of the following:
- Transactions affected: a significant number or value of payment transactions are disrupted, degraded or misdirected.
- Duration: the service is unavailable or impaired beyond a short, defined window.
- Clients impacted: a material proportion of your client base cannot initiate or receive payments.
You do not need to be certain an event is major before you start the clock. The safer pattern is to classify provisionally, notify, and update. A late notification can be treated as a supervisory finding.
Deadlines you should plan around
The EBA guidelines set an initial notification window that national regulators implement as a short period after classification. Confirm your competent authority's published requirement before you go live, and build to a tighter internal clock.
A practical reporting calendar for a startup looks like this:
| Trigger | What is due | Typical recipient | Internal deadline |
|---|---|---|---|
| Incident classified as major | Initial notification | Competent authority portal | Within half the external window |
| 24-72 hours after initial notification | Intermediate report with root cause and containment | Competent authority portal | Same day as external deadline |
| Incident closed | Final report with remediation and lessons learned | Competent authority portal | Within the regulator's stated period after closure |
| Suspected fraud or security breach | Notification under applicable fraud and security rules | Competent authority and, where relevant, the data protection authority | Immediately after internal confirmation |
Watch out: treating the initial notification as the end of the process. Supervisors expect the intermediate and final reports.
Data fields to have ready before you need them
Prepare a standing incident template so the first hour is spent gathering facts, not designing a form. The fields most regulators ask for include:
- Time of detection, time of classification and time of notification
- Services, channels and jurisdictions affected
- Number of clients and transactions impacted, and estimated value
Keep the template in the same repository as your control register so the evidence trail is continuous.
Submission routes
The submission route is usually your competent authority's secure portal or a designated reporting form. Confirm yours before you need it, and test access with a named backup. If you operate in more than one jurisdiction, record each portal, login owner and format separately.
A worked pattern
Imagine an API outage: the team detects it via monitoring, classifies it as major because a core channel is down and a material number of clients are affected, and sends an initial notification within the internal window. The intermediate report follows with root cause and containment, and the final report records the fix, the monitoring gap and the change to the control register.
UK and EU Reporting Differences After Brexit
The UK and the EU now run separate regimes. The Payment Services Directive has been implemented separately in UK and EU law, so the wording looks familiar but the reporting routes, portals and some thresholds can differ.
Practical differences to plan for:
- Regulator: the Financial Conduct Authority in the UK, your national competent authority in the EU
- Reporting portal: separate systems, separate logins, separate formats
- Incident routes: different submission channels and contact points
If you operate in both markets, run two reporting calendars. Do not assume one template covers both. For a plain explanation of how UK open banking works in practice, see our guide to open banking in the UK.
Connecting Your Bank Data Without an AISP Licence
Most startups do not need a licence to get bank data. They need a licensed provider and a clear contract.
This is the route most SaaS and ERP teams take.
What you still must do:
- Vet the provider and record the vetting
- Confirm the legal basis for processing account data
- Keep consent records for each connected account
For teams that want to see how multi-bank aggregation works before committing, our multi-bank data aggregation guide covers the implementation detail, SLAs and build-versus-buy criteria.
Getting PSD2 reporting right is less about legal reading and more about building a trail you can retrieve on demand.
Get started with Zenith and put your bank data where your reporting evidence can actually use it.




