[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-how-to-handle-psd2-regulatory-reporting-for-fintech-startups":3,"blog-related-gr-how-to-handle-psd2-regulatory-reporting-for-fintech-startups":36},{"kind":4,"article":5},"gr",{"slug":6,"title":7,"subtitle":8,"meta_title":7,"meta_description":9,"category":10,"author_name":11,"author_title":12,"image_url":13,"read_time":14,"published_at":15,"language_code":16,"content_html":17,"json_ld_str":18,"faqs":19,"recommended_slugs":32},"how-to-handle-psd2-regulatory-reporting-for-fintech-startups","How to Handle PSD2 Regulatory Reporting for Fintech Startups",null,"PSD2 regulatory reporting for fintech startups is simpler with our step-by-step workflow covering obligations, deadlines and submission.","how-to","Editorial Team","Content Writer","https:\u002F\u002Fcdn.grandranker.com\u002Farticles\u002Fhow-to-handle-psd2-regulatory-reporting-for-fintech-startups-1794274784.jpg","13 min read","2026-11-11T00:00:00+00:00","en-GB","\u003Cp>\u003Cem>Last Updated: 10 November 2026\u003C\u002Fem>\u003C\u002Fp>\n\u003Cdiv class=\"article-answer\" style=\"margin:1.5rem 0;padding:16px 20px;background-color:#f8fafc;border:1px solid #e2e8f0;border-radius:8px\">\n\u003Cp style=\"margin:0 0 6px;color:#111827;font-size:14px\">\u003Cstrong>Quick Summary\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp style=\"margin:0;color:#1f2937;font-size:16px;line-height:1.6\">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.\u003C\u002Fp>\n\u003Cul style=\"margin:10px 0 0;padding-left:20px;color:#374151;font-size:15px;line-height:1.6\">\n\u003Cli>Map each obligation to your business model, then confirm your position with your competent authority.\u003C\u002Fli>\n\u003Cli>A registered AISP reports less than a payment institution, but registration maintenance and incident notification still apply.\u003C\u002Fli>\n\u003Cli>Build a control register listing each system, its control, how you test it and how often.\u003C\u002Fli>\n\u003Cli>Prepare a standing incident template with detection, classification and notification times before you need it.\u003C\u002Fli>\n\u003Cli>If you operate in the UK and the EU, run two reporting calendars with separate portals and logins.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fdiv>\n\u003Cdiv class=\"cta-card\" style=\"display:flex;flex-wrap:wrap;align-items:center;gap:16px;margin:24px 0;padding:18px 20px;border:1px solid #908da733;background-color:#f9f9fb;border-radius:12px\">\u003Cdiv style=\"flex:1 1 240px;min-width:0\">\u003Cstrong style=\"display:block;font-size:17px;line-height:1.3;color:#111827\">Need bank data without an AISP licence?\u003C\u002Fstrong>\u003Cspan style=\"display:block;margin-top:4px;font-size:14px;line-height:1.45;color:#4b5563\">Connect 2,400+ European banks to Sheets, your API or an AI assistant through regulated consent flows.\u003C\u002Fspan>\u003C\u002Fdiv>\u003Ca href=\"https:\u002F\u002Fzenith-books.com\" class=\"cta-action-button\" style=\"display:inline-flex;align-items:center;gap:4px;min-height:42px;padding:0 18px;background-color:#908da7;color:#111827;border:1px solid #908da7;border-radius:8px;font-size:15px;font-weight:600;line-height:1.2;text-decoration:none\">Start Free with Zenith\u003C\u002Fa>\u003C\u002Fdiv>\n\n\u003Ch2 id=\"table-of-contents\">Table of Contents\u003C\u002Fh2>\n\u003Cul>\u003Cli>\u003Ca href=\"#what-psd2-regulatory-reporting-means-for-a-fintech-startup\">What PSD2 Regulatory Reporting Means for a Fintech Startup\u003C\u002Fa>\u003C\u002Fli>\u003Cli>\u003Ca href=\"#psd2-reporting-requirements-what-competent-authorities-expect\">PSD2 Reporting Requirements: What Competent Authorities Expect\u003C\u002Fa>\u003Cul>\u003Cli>\u003Ca href=\"#licensing-authorisation-and-ongoing-supervision\">Licensing, Authorisation and Ongoing Supervision\u003C\u002Fa>\u003C\u002Fli>\u003Cli>\u003Ca href=\"#strong-customer-authentication-and-open-banking-evidence\">Strong Customer Authentication and Open Banking Evidence\u003C\u002Fa>\u003C\u002Fli>\u003C\u002Ful>\u003C\u002Fli>\u003Cli>\u003Ca href=\"#mapping-obligations-to-your-business-model-and-authorisation-status\">Mapping Obligations to Your Business Model and Authorisation Status\u003C\u002Fa>\u003Cul>\u003Cli>\u003Ca href=\"#a-decision-path-for-early-stage-teams\">A decision path for early-stage teams\u003C\u002Fa>\u003C\u002Fli>\u003Cli>\u003Ca href=\"#mapping-by-authorisation-status\">Mapping by authorisation status\u003C\u002Fa>\u003C\u002Fli>\u003Cli>\u003Ca href=\"#jurisdiction-routing\">Jurisdiction routing\u003C\u002Fa>\u003C\u002Fli>\u003Cli>\u003Ca href=\"#what-to-do-with-the-map\">What to do with the map\u003C\u002Fa>\u003C\u002Fli>\u003C\u002Ful>\u003C\u002Fli>\u003Cli>\u003Ca href=\"#psd2-reporting-for-account-information-service-providers\">PSD2 Reporting for Account Information Service Providers\u003C\u002Fa>\u003C\u002Fli>\u003Cli>\u003Ca href=\"#psd2-operational-and-security-risk-assessment-building-the-evidence\">PSD2 Operational and Security Risk Assessment: Building the Evidence\u003C\u002Fa>\u003C\u002Fli>\u003Cli>\u003Ca href=\"#psd2-major-incident-reporting-deadlines-data-fields-and-submission-routes\">PSD2 Major Incident Reporting: Deadlines, Data Fields and Submission Routes\u003C\u002Fa>\u003Cul>\u003Cli>\u003Ca href=\"#what-counts-as-a-major-incident\">What counts as a major incident\u003C\u002Fa>\u003C\u002Fli>\u003Cli>\u003Ca href=\"#deadlines-you-should-plan-around\">Deadlines you should plan around\u003C\u002Fa>\u003C\u002Fli>\u003Cli>\u003Ca href=\"#data-fields-to-have-ready-before-you-need-them\">Data fields to have ready before you need them\u003C\u002Fa>\u003C\u002Fli>\u003Cli>\u003Ca href=\"#submission-routes\">Submission routes\u003C\u002Fa>\u003C\u002Fli>\u003Cli>\u003Ca href=\"#a-worked-pattern\">A worked pattern\u003C\u002Fa>\u003C\u002Fli>\u003C\u002Ful>\u003C\u002Fli>\u003Cli>\u003Ca href=\"#uk-and-eu-reporting-differences-after-brexit\">UK and EU Reporting Differences After Brexit\u003C\u002Fa>\u003C\u002Fli>\u003Cli>\u003Ca href=\"#connecting-your-bank-data-without-an-aisp-licence\">Connecting Your Bank Data Without an AISP Licence\u003C\u002Fa>\u003C\u002Fli>\u003Cli>\u003Ca href=\"#frequently-asked-questions\">Frequently Asked Questions\u003C\u002Fa>\u003C\u002Fli>\u003C\u002Ful>\n\u003Ch2 id=\"what-psd2-regulatory-reporting-means-for-a-fintech-startup\">What PSD2 Regulatory Reporting Means for a Fintech Startup\u003C\u002Fh2>\n\u003Cp>\u003Ca rel=\"noopener noreferrer\" target=\"_blank\" href=\"https:\u002F\u002Fwww.eba.europa.eu\u002Factivities\u002Fsingle-rulebook\u002Fregulatory-activities\u002Fpayment-services-and-electronic-money\u002Fguidelines-authorisation-and-registration-under-psd2\">PSD2\u003C\u002Fa> 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.\u003C\u002Fp>\n\u003Cp>This guide maps each obligation to your business model, then shows the deadlines, data fields and submission routes that apply.\u003C\u002Fp>\n\u003Cp>There are three layers:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Authorisation evidence:\u003C\u002Fstrong> the application pack and the documents behind it\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Ongoing supervision:\u003C\u002Fstrong> periodic returns, notifications of change and financial statements\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Event-driven reporting:\u003C\u002Fstrong> major incidents and fraud data\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Miss the third layer and you can face supervisory action even with a clean application.\u003C\u002Fp>\n\u003Ch2 id=\"psd2-reporting-requirements-what-competent-authorities-expect\">PSD2 Reporting Requirements: What Competent Authorities Expect\u003C\u002Fh2>\n\u003Cp>Competent authorities expect a complete, consistent evidence trail. Every claim in your application must be backed by a document you can update later.\u003C\u002Fp>\n\u003Cp>A common mistake is writing the application as a one-off sales pitch.\u003C\u002Fp>\n\u003Cp>Expect scrutiny in four areas:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Governance and named responsible persons\u003C\u002Fli>\n\u003Cli>Safeguarding of client funds, where relevant\u003C\u002Fli>\n\u003Cli>Operational and security controls\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The \u003Ca rel=\"noopener noreferrer\" target=\"_blank\" href=\"https:\u002F\u002Fwww.eba.europa.eu\u002Factivities\u002Fsingle-rulebook\u002Fregulatory-activities\u002Fpayment-services-and-electronic-money\u002Fguidelines-authorisation-and-registration-under-psd2\">European Banking Authority's PSD2 guidance\u003C\u002Fa> sets the supervisory expectations most national regulators follow. Read your own competent authority's page first, then use the EBA material to fill gaps.\u003C\u002Fp>\n\u003Ch3 id=\"licensing-authorisation-and-ongoing-supervision\">Licensing, Authorisation and Ongoing Supervision\u003C\u002Fh3>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>Ongoing supervision typically means:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Annual or periodic reporting returns\u003C\u002Fli>\n\u003Cli>Notification of changes to directors, systems or business plan\u003C\u002Fli>\n\u003Cli>Financial statements filed on the regulator's timetable\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Keep a single source of truth for these facts, so a director change updates three documents the same day.\u003C\u002Fp>\n\u003Ch3 id=\"strong-customer-authentication-and-open-banking-evidence\">Strong Customer Authentication and Open Banking Evidence\u003C\u002Fh3>\n\u003Cp>Strong Customer Authentication is the two-factor check applied when a customer accesses their payment account or initiates a payment.\u003C\u002Fp>\n\u003Cp>Open banking evidence applies the same idea to third-party access. If you rely on another provider's consent flow, document that dependency.\u003C\u002Fp>\n\u003Cp>What supervisors look for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A written description of your authentication flow\u003C\u002Fli>\n\u003Cli>Test results showing the flow works as described\u003C\u002Fli>\n\u003Cli>Logs proving authentication events are recorded\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Read-only access has its own security model, and you must be able to evidence it. Our guide to \u003Ca href=\"\u002Fblog\u002Fread-only-open-banking-security\">read-only open banking security\u003C\u002Fa> explains the controls.\u003C\u002Fp>\n\u003Ch2 id=\"mapping-obligations-to-your-business-model-and-authorisation-status\">Mapping Obligations to Your Business Model and Authorisation Status\u003C\u002Fh2>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ctable style=\"width:100%;border-collapse:collapse;margin:2rem 0;font-size:14px;line-height:1.6\">\n\u003Cthead style=\"background-color:#f8f9fa;color:#111827;padding:12px 16px;text-align:left;font-weight:600;border-bottom:2px solid #e5e7eb\">\n\u003Ctr>\n\u003Cth style=\"background-color:#f8f9fa;color:#111827;padding:12px 16px;text-align:left;font-weight:600;border-bottom:2px solid #e5e7eb\">Business model\u003C\u002Fth>\n\u003Cth style=\"background-color:#f8f9fa;color:#111827;padding:12px 16px;text-align:left;font-weight:600;border-bottom:2px solid #e5e7eb\">Authorisation route\u003C\u002Fth>\n\u003Cth style=\"background-color:#f8f9fa;color:#111827;padding:12px 16px;text-align:left;font-weight:600;border-bottom:2px solid #e5e7eb\">Core reporting load\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Account information only\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Registration as AISP\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Periodic returns, incident notices\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Payment initiation only\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Authorisation as PISP\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Returns, safeguarding evidence, incident notices\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Card or credit issuing\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Authorisation as payment institution\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Full returns, financial statements, fraud data\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Bank connectivity inside a SaaS product\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Usually via a licensed partner\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Partner due diligence, incident escalation\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Internal tool, no client funds\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Often out of scope\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Contract and data protection only\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch3 id=\"a-decision-path-for-early-stage-teams\">A decision path for early-stage teams\u003C\u002Fh3>\n\u003Cp>Work through these questions in order. The first one that applies usually determines your route.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Do you hold client funds or settle payments for third parties?\u003C\u002Fstrong> If yes, you are likely a payment institution or electronic money institution and should plan for full authorisation and ongoing returns.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Do you initiate payments on behalf of a user without holding funds?\u003C\u002Fstrong> If yes, you are likely a PISP and need authorisation plus safeguarding evidence where relevant.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Do you only read account data with the user's consent?\u003C\u002Fstrong> If yes, you are likely an AISP and need registration, incident notification and cooperation with supervision.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Do you connect to banks inside a product where a licensed provider holds the permissions?\u003C\u002Fstrong> If yes, you are probably on the partner route, with duties around due diligence, consent records and incident escalation.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Do you process payment data only as an internal tool with no client funds and no third-party access?\u003C\u002Fstrong> If yes, you may be out of scope for PSD2 authorisation, but data protection and contract duties still apply.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch3 id=\"mapping-by-authorisation-status\">Mapping by authorisation status\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Pre-application:\u003C\u002Fstrong> evidence gathering, governance design, safeguarding arrangements and a documented business plan.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Application:\u003C\u002Fstrong> the full authorisation pack, including programme of operations, evidence of initial capital where required, and descriptions of controls.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Post-authorisation:\u003C\u002Fstrong> periodic returns, notifications of change, financial statements and incident reporting.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3 id=\"jurisdiction-routing\">Jurisdiction routing\u003C\u002Fh3>\n\u003Cp>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 \u003Ca href=\"\u002Fblog\u002Fen\u002Fopen-banking-uk\">guide to open banking in the UK\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3 id=\"what-to-do-with-the-map\">What to do with the map\u003C\u002Fh3>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch2 id=\"psd2-reporting-for-account-information-service-providers\">PSD2 Reporting for Account Information Service Providers\u003C\u002Fh2>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>Building that evidence is a development task as much as a compliance one. If you are weighing the engineering side, our \u003Ca href=\"\u002Fblog\u002Fpsd2-api-integration-startups\">PSD2 API integration guide for startups\u003C\u002Fa> covers the practical build.\u003C\u002Fp>\n\u003Ch2 id=\"psd2-operational-and-security-risk-assessment-building-the-evidence\">PSD2 Operational and Security Risk Assessment: Building the Evidence\u003C\u002Fh2>\n\u003Cp>A risk assessment is only useful if it produces artefacts a supervisor can inspect.\u003C\u002Fp>\n\u003Cp>Build the evidence in this order:\u003C\u002Fp>\n\u003Col>\n\u003Cli>List every system that touches payment account data\u003C\u002Fli>\n\u003Cli>Name the control protecting each one\u003C\u002Fli>\n\u003Cli>Record how you test that control and how often\u003C\u002Fli>\n\u003Cli>Store the output where you can retrieve it on request\u003C\u002Fli>\n\u003Cli>Review the register at least quarterly\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>If you need a structured route to that trail, our \u003Ca href=\"\u002Fblog\u002Fen\u002Ffinance-data-security\">finance data security roadmap\u003C\u002Fa> sets out controls across a 30-, 90- and 180-day plan.\u003C\u002Fp>\n\u003Cp>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 \u003Ca rel=\"noopener noreferrer\" target=\"_blank\" href=\"https:\u002F\u002Ffcaauthorisation.info\u002Fguaranteeing-fca-application-success-for-startups\u002F\">FCA Authorisation\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"psd2-major-incident-reporting-deadlines-data-fields-and-submission-routes\">PSD2 Major Incident Reporting: Deadlines, Data Fields and Submission Routes\u003C\u002Fh2>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cfigure class=\"article-content-image my-8\" style=\"margin:2em 0;padding:0;background:transparent;border:0\">\u003Cimg src=\"https:\u002F\u002Fcdn.grandranker.com\u002Farticles\u002Fhow-to-handle-psd2-regulatory-reporting-for-fintech-startups-content-1-1794274794.jpg\" alt=\"Compliance officer reviewing a PSD2 regulatory reporting for fintech startups checklist on a laptop screen.\" class=\"w-full rounded-lg shadow-lg\" loading=\"lazy\" style=\"display:block;width:100%;max-width:100%;height:auto;border-radius:8px;margin:0 auto\" \u002F>\u003Cfigcaption class=\"text-sm text-gray-600 mt-2 text-center\" style=\"font-size:0.875em;color:inherit;opacity:0.75;text-align:center;margin-top:0.6em\">Compliance officer reviewing a PSD2 regulatory reporting for fintech startups checklist on a laptop screen.\u003C\u002Ffigcaption>\u003C\u002Ffigure>\n\u003Ch3 id=\"what-counts-as-a-major-incident\">What counts as a major incident\u003C\u002Fh3>\n\u003Cp>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:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Transactions affected:\u003C\u002Fstrong> a significant number or value of payment transactions are disrupted, degraded or misdirected.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Duration:\u003C\u002Fstrong> the service is unavailable or impaired beyond a short, defined window.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Clients impacted:\u003C\u002Fstrong> a material proportion of your client base cannot initiate or receive payments.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch3 id=\"deadlines-you-should-plan-around\">Deadlines you should plan around\u003C\u002Fh3>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>A practical reporting calendar for a startup looks like this:\u003C\u002Fp>\n\u003Ctable style=\"width:100%;border-collapse:collapse;margin:2rem 0;font-size:14px;line-height:1.6\">\n\u003Cthead style=\"background-color:#f8f9fa;color:#111827;padding:12px 16px;text-align:left;font-weight:600;border-bottom:2px solid #e5e7eb\">\n\u003Ctr>\n\u003Cth style=\"background-color:#f8f9fa;color:#111827;padding:12px 16px;text-align:left;font-weight:600;border-bottom:2px solid #e5e7eb\">Trigger\u003C\u002Fth>\n\u003Cth style=\"background-color:#f8f9fa;color:#111827;padding:12px 16px;text-align:left;font-weight:600;border-bottom:2px solid #e5e7eb\">What is due\u003C\u002Fth>\n\u003Cth style=\"background-color:#f8f9fa;color:#111827;padding:12px 16px;text-align:left;font-weight:600;border-bottom:2px solid #e5e7eb\">Typical recipient\u003C\u002Fth>\n\u003Cth style=\"background-color:#f8f9fa;color:#111827;padding:12px 16px;text-align:left;font-weight:600;border-bottom:2px solid #e5e7eb\">Internal deadline\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Incident classified as major\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Initial notification\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Competent authority portal\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Within half the external window\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">24-72 hours after initial notification\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Intermediate report with root cause and containment\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Competent authority portal\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Same day as external deadline\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Incident closed\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Final report with remediation and lessons learned\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Competent authority portal\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Within the regulator's stated period after closure\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Suspected fraud or security breach\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Notification under applicable fraud and security rules\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Competent authority and, where relevant, the data protection authority\u003C\u002Ftd>\n\u003Ctd style=\"padding:12px 16px;border-bottom:1px solid #e5e7eb\">Immediately after internal confirmation\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003Cp>Watch out: treating the initial notification as the end of the process. Supervisors expect the intermediate and final reports.\u003C\u002Fp>\n\u003Ch3 id=\"data-fields-to-have-ready-before-you-need-them\">Data fields to have ready before you need them\u003C\u002Fh3>\n\u003Cp>Prepare a standing incident template so the first hour is spent gathering facts, not designing a form. The fields most regulators ask for include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Time of detection, time of classification and time of notification\u003C\u002Fli>\n\u003Cli>Services, channels and jurisdictions affected\u003C\u002Fli>\n\u003Cli>Number of clients and transactions impacted, and estimated value\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Keep the template in the same repository as your control register so the evidence trail is continuous.\u003C\u002Fp>\n\u003Ch3 id=\"submission-routes\">Submission routes\u003C\u002Fh3>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch3 id=\"a-worked-pattern\">A worked pattern\u003C\u002Fh3>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch2 id=\"uk-and-eu-reporting-differences-after-brexit\">UK and EU Reporting Differences After Brexit\u003C\u002Fh2>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>Practical differences to plan for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Regulator:\u003C\u002Fstrong> the Financial Conduct Authority in the UK, your national competent authority in the EU\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Reporting portal:\u003C\u002Fstrong> separate systems, separate logins, separate formats\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Incident routes:\u003C\u002Fstrong> different submission channels and contact points\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch2 id=\"connecting-your-bank-data-without-an-aisp-licence\">Connecting Your Bank Data Without an AISP Licence\u003C\u002Fh2>\n\u003Cp>Most startups do not need a licence to get bank data. They need a licensed provider and a clear contract.\u003C\u002Fp>\n\u003Cp>This is the route most SaaS and ERP teams take.\u003C\u002Fp>\n\u003Cp>What you still must do:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Vet the provider and record the vetting\u003C\u002Fli>\n\u003Cli>Confirm the legal basis for processing account data\u003C\u002Fli>\n\u003Cli>Keep consent records for each connected account\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For teams that want to see how multi-bank aggregation works before committing, our \u003Ca href=\"\u002Fblog\u002Fen\u002Fmulti-bank-data-aggregation\">multi-bank data aggregation guide\u003C\u002Fa> covers the implementation detail, SLAs and build-versus-buy criteria.\u003C\u002Fp>\n\u003Chr \u002F>\n\u003Cp>Getting PSD2 reporting right is less about legal reading and more about building a trail you can retrieve on demand.\u003C\u002Fp>\n\u003Cp>Get started with Zenith and put your bank data where your reporting evidence can actually use it.\u003C\u002Fp>\n\u003Csection style=\"margin:3rem 0 2rem 0\" itemscope itemtype=\"https:\u002F\u002Fschema.org\u002FFAQPage\">\u003Ch2 style=\"font-weight:700;margin:0 0 4px 0\" id=\"frequently-asked-questions\">Frequently Asked Questions\u003C\u002Fh2>\u003Cdiv style=\"padding:20px 0;border-bottom:1px solid #e5e7eb\" itemscope itemprop=\"mainEntity\" itemtype=\"https:\u002F\u002Fschema.org\u002FQuestion\">\u003Ch3 style=\"font-weight:600;margin:0 0 8px 0\" itemprop=\"name\">Which fintech businesses need to report under PSD2?\u003C\u002Fh3>\u003Cdiv style=\"line-height:1.7\" itemscope itemprop=\"acceptedAnswer\" itemtype=\"https:\u002F\u002Fschema.org\u002FAnswer\">\u003Cp itemprop=\"text\" style=\"margin:0\">Reporting duties follow authorisation status, not company size. Payment institutions, e-money institutions, account information service providers and payment initiation service providers authorised by a competent authority carry the full set: incident reporting, operational and security risk assessments, and periodic supervisory returns. Fintechs that only consume bank data through a licensed provider, without holding their own authorisation, generally fall outside those duties. Confirm your position with your competent authority before assuming an exemption applies.\u003C\u002Fp>\u003C\u002Fdiv>\u003C\u002Fdiv>\u003Cdiv style=\"padding:20px 0;border-bottom:1px solid #e5e7eb\" itemscope itemprop=\"mainEntity\" itemtype=\"https:\u002F\u002Fschema.org\u002FQuestion\">\u003Ch3 style=\"font-weight:600;margin:0 0 8px 0\" itemprop=\"name\">What is PSD2 major incident reporting and when does it trigger?\u003C\u002Fh3>\u003Cdiv style=\"line-height:1.7\" itemscope itemprop=\"acceptedAnswer\" itemtype=\"https:\u002F\u002Fschema.org\u002FAnswer\">\u003Cp itemprop=\"text\" style=\"margin:0\">PSD2 major incident reporting is the obligation to notify your competent authority when a security or operational event materially disrupts payment services or affects customer data. Triggers typically include service outages, data breaches, fraud events and failures in third-party access. The Regulatory Technical Standards set the classification criteria and require an initial notification quickly after detection, followed by a fuller report. Exact deadlines and the submission channel are set by your national competent authority, so check its guidance rather than relying on a generic timeline.\u003C\u002Fp>\u003C\u002Fdiv>\u003C\u002Fdiv>\u003Cdiv style=\"padding:20px 0;border-bottom:1px solid #e5e7eb\" itemscope itemprop=\"mainEntity\" itemtype=\"https:\u002F\u002Fschema.org\u002FQuestion\">\u003Ch3 style=\"font-weight:600;margin:0 0 8px 0\" itemprop=\"name\">How does PSD2 reporting differ for account information and payment initiation services?\u003C\u002Fh3>\u003Cdiv style=\"line-height:1.7\" itemscope itemprop=\"acceptedAnswer\" itemtype=\"https:\u002F\u002Fschema.org\u002FAnswer\">\u003Cp itemprop=\"text\" style=\"margin:0\">Both are regulated payment services, so both carry incident reporting and risk assessment duties. The practical difference sits in the evidence: a payment initiation service must show transaction monitoring, fraud prevention and anti-money laundering controls, while an account information service focuses on consent management, data protection and third-party access security. PSD2 reporting for account information service providers leans heavily on consent records and data minimisation. Map your controls to the service you actually provide, not to a combined template.\u003C\u002Fp>\u003C\u002Fdiv>\u003C\u002Fdiv>\u003Cdiv style=\"padding:20px 0;border-bottom:1px solid #e5e7eb\" itemscope itemprop=\"mainEntity\" itemtype=\"https:\u002F\u002Fschema.org\u002FQuestion\">\u003Ch3 style=\"font-weight:600;margin:0 0 8px 0\" itemprop=\"name\">Where can fintechs find official PSD2 reporting guidance?\u003C\u002Fh3>\u003Cdiv style=\"line-height:1.7\" itemscope itemprop=\"acceptedAnswer\" itemtype=\"https:\u002F\u002Fschema.org\u002FAnswer\">\u003Cp itemprop=\"text\" style=\"margin:0\">Start with your national competent authority, which publishes reporting templates, submission portals and deadline rules for its jurisdiction. The European Banking Authority issues the Regulatory Technical Standards and related guidelines that national rules implement, and the European Securities and Markets Authority covers certain market-facing aspects. In the UK, the Financial Conduct Authority publishes its own incident reporting requirements, which now diverge from the EU framework. Always work from the current version of the official text, not a summary.\u003C\u002Fp>\u003C\u002Fdiv>\u003C\u002Fdiv>\u003C\u002Fsection>\n\u003Cdiv style=\"border:1px solid #d6d3d1;border-radius:12px;padding:18px 20px;margin:32px 0\">\u003Ca href=\"https:\u002F\u002Fwww.google.com\u002Fpreferences\u002Fsource?q=zenith-books.com\" target=\"_blank\" rel=\"noopener\" style=\"display:block;text-decoration:none;color:inherit\">\u003Cimg loading=\"lazy\" decoding=\"async\" src=\"https:\u002F\u002Fapp.grandranker.com\u002Fimages\u002Fgoogle-g.svg\" width=\"24\" height=\"24\" alt=\"Google\" style=\"display:inline-block;width:24px !important;height:24px !important;max-width:24px;vertical-align:middle;margin:0 10px 0 0;border:0\" \u002F>\u003Cspan style=\"vertical-align:middle\">Add \u003Cstrong>zenith-books.com\u003C\u002Fstrong> as a preferred source on Google →\u003C\u002Fspan>\u003C\u002Fa>\u003C\u002Fdiv>","{\"@graph\":[{\"url\":\"https:\u002F\u002Fzenith-books.com\u002Fblog\u002Fhow-to-handle-psd2-regulatory-reporting-for-fintech-startups\",\"name\":\"How to Handle PSD2 Regulatory Reporting for Fintech Startups\",\"@type\":\"BlogPosting\",\"image\":{\"url\":\"https:\u002F\u002Fcdn.grandranker.com\u002Farticles\u002Fhow-to-handle-psd2-regulatory-reporting-for-fintech-startups-1794274784.jpg\",\"@type\":\"ImageObject\"},\"author\":{\"name\":\"Editorial Team\",\"@type\":\"Organization\"},\"headline\":\"How to Handle PSD2 Regulatory Reporting for Fintech Startups\",\"keywords\":\"psd2 regulatory reporting for fintech startups, psd2 reporting requirements, psd2 major incident reporting, psd2 operational and security risk assessment, psd2 reporting for account information service providers\",\"publisher\":{\"name\":\"Zenith\",\"@type\":\"Organization\"},\"wordCount\":2556,\"inLanguage\":\"en-GB\",\"articleBody\":\"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. Need bank data without an AISP licence?Connect 2,400+ European banks to Sheets, your API or an AI assistant through regulated consent flows.Start Free with Zenith Table of Contents What PSD2 Regulatory Reporting Means for a Fintech StartupPSD2 Reporting Requirements: What Competent Authorities ExpectLicensing, Authorisation and Ongoing SupervisionStrong Customer Authentication and Open Banking EvidenceMapping Obligations to Your Business Model and Authorisation StatusA decision path for e...\",\"description\":\"PSD2 regulatory reporting for fintech startups is simpler with our step-by-step workflow covering obligations, deadlines and submission.\",\"dateModified\":\"2026-11-10T01:40:22+00:00\",\"datePublished\":\"2026-11-10T01:39:57+00:00\",\"articleSection\":\"how-to\",\"mainEntityOfPage\":{\"@id\":\"https:\u002F\u002Fzenith-books.com\u002Fblog\u002Fhow-to-handle-psd2-regulatory-reporting-for-fintech-startups\",\"@type\":\"WebPage\"}},{\"url\":\"https:\u002F\u002Fzenith-books.com\",\"name\":\"Zenith\",\"@type\":\"Organization\",\"knowsAbout\":\"Finance & Fintech\",\"description\":\"Zenith Bank Sync is an open banking API that connects 2400+ banks across 30 European countries to the tools you already work in. Connect a bank account once, then pull balances and transactions into Google Sheets, a REST API, CSV, or an AI assistant via MCP. No bank integrations to build, no CSV downloads to chase, no screen scraping.\\n\\nBuilt for:\\n• Finance teams and bookkeepers who need live bank data in a spreadsheet\\n• Developers who need PSD2 account data without a six-month integration project\\n• Founders running multi-bank, multi-country operations\\n• AI agents that need read access to real financial data through our MCP server\\n\\nHow it works: authenticate through your bank's own PSD2 consent flow, choose the accounts to sync, and Zenith keeps statements, balances and transactions up to date. Coverage spans the EU, the UK and the wider EEA.\\n\\nPricing is €5 per connected account per month — no platform fee, no minimum volume, no annual contract.\\n\\nZenith also handles what comes after the bank feed: invoice OCR, accounts payable automation and expense management, so month-end runs in one place.\"},{\"@type\":\"BreadcrumbList\",\"itemListElement\":[{\"item\":\"https:\u002F\u002Fzenith-books.com\",\"name\":\"Home\",\"@type\":\"ListItem\",\"position\":1},{\"item\":\"https:\u002F\u002Fzenith-books.com\u002Fblog\",\"name\":\"Blog\",\"@type\":\"ListItem\",\"position\":2},{\"item\":\"https:\u002F\u002Fzenith-books.com\u002Fblog\u002Fhow-to-handle-psd2-regulatory-reporting-for-fintech-startups\",\"name\":\"How to Handle PSD2 Regulatory Reporting for Fintech Startups\",\"@type\":\"ListItem\",\"position\":3}]}],\"@context\":\"https:\u002F\u002Fschema.org\"}",[20,23,26,29],{"name":21,"answer":22},"Which fintech businesses need to report under PSD2?","Reporting duties follow authorisation status, not company size. Payment institutions, e-money institutions, account information service providers and payment initiation service providers authorised by a competent authority carry the full set: incident reporting, operational and security risk assessments, and periodic supervisory returns. Fintechs that only consume bank data through a licensed provider, without holding their own authorisation, generally fall outside those duties. Confirm your position with your competent authority before assuming an exemption applies.",{"name":24,"answer":25},"What is PSD2 major incident reporting and when does it trigger?","PSD2 major incident reporting is the obligation to notify your competent authority when a security or operational event materially disrupts payment services or affects customer data. Triggers typically include service outages, data breaches, fraud events and failures in third-party access. The Regulatory Technical Standards set the classification criteria and require an initial notification quickly after detection, followed by a fuller report. Exact deadlines and the submission channel are set by your national competent authority, so check its guidance rather than relying on a generic timeline.",{"name":27,"answer":28},"How does PSD2 reporting differ for account information and payment initiation services?","Both are regulated payment services, so both carry incident reporting and risk assessment duties. The practical difference sits in the evidence: a payment initiation service must show transaction monitoring, fraud prevention and anti-money laundering controls, while an account information service focuses on consent management, data protection and third-party access security. PSD2 reporting for account information service providers leans heavily on consent records and data minimisation. Map your controls to the service you actually provide, not to a combined template.",{"name":30,"answer":31},"Where can fintechs find official PSD2 reporting guidance?","Start with your national competent authority, which publishes reporting templates, submission portals and deadline rules for its jurisdiction. The European Banking Authority issues the Regulatory Technical Standards and related guidelines that national rules implement, and the European Securities and Markets Authority covers certain market-facing aspects. In the UK, the Financial Conduct Authority publishes its own incident reporting requirements, which now diverge from the EU framework. Always work from the current version of the official text, not a summary.",[33,34,35],"how-long-does-it-take-to-implement-financial-ai","how-to-choose-bank-transaction-import-frequency-options","read-only-open-banking-security",[37,44,49],{"href":4,"slug":33,"locale":38,"title":39,"excerpt":40,"image_url":41,"reading_time":42,"published_at":43,"tag":10},"en","How Long Does It Take to Implement Financial AI?","Financial AI takes 6-16 weeks to implement, depending on scope. Learn the timeline by phase, what slows projects down and how to hit your first milestone.","https:\u002F\u002Fcdn.grandranker.com\u002Farticles\u002Fhow-long-does-it-take-to-implement-financial-ai-1794109250.jpg",11,"2026-11-09T00:00:00+00:00",{"href":4,"slug":34,"locale":38,"title":45,"excerpt":46,"image_url":47,"reading_time":42,"published_at":48,"tag":10},"How to Choose Bank Transaction Import Frequency Options","Choosing the right import frequency keeps your books accurate. Compare daily, weekly and manual options, and spot missing transactions fast.","https:\u002F\u002Fcdn.grandranker.com\u002Farticles\u002Fhow-to-choose-bank-transaction-import-frequency-options-1793857545.jpg","2026-11-06T00:00:00+00:00",{"href":4,"slug":35,"locale":38,"title":50,"excerpt":51,"image_url":52,"reading_time":53,"published_at":54,"tag":10},"7 Things to Know About Read-Only Open Banking Security","Read-only open banking gives apps sight of your account data without payment power. Learn how consent, SCA and revocation keep access secure.","https:\u002F\u002Fcdn.grandranker.com\u002Farticles\u002F7-things-to-know-about-read-only-open-banking-security-1793594200.jpg",12,"2026-11-02T00:00:00+00:00"]