Skip to content

PSP operations

Compliance for Payment Service Providers: Checklist

A PSP answers to several rulebooks at once. Its regulator sets the license and AML rules. The card schemes set PCI DSS and dispute rules through its acquirers. Data protection law covers the personal data in every payment.

Compliance for payment service providers is easier to run when it's one list with owners rather than separate projects. This page sets out that list, with the public rules behind each item and what changes when a PSP works with several acquirers.

A checklist of compliance for payment service providers

This PSP compliance checklist lists the main areas, who sets the rules, and what a PSP has to show. Each area needs a named owner and evidence that the control works.

Area Who sets the rules What you need to show
License The national regulator Authorization for each payment service you provide, and its conditions met
Safeguarding The national regulator Merchants' funds kept separate from your own and reconciled
AML and sanctions AML law and the regulator Risk assessment, due diligence, monitoring and reporting
PCI DSS The PCI Security Standards Council and the card schemes Annual validation at the right level, quarterly scans
Customer authentication PSD2 in the EU, local rules elsewhere Strong customer authentication where required, exemptions applied correctly
Scheme rules Visa, Mastercard and other networks Merchant checks, monitoring thresholds, facilitator registration
Operational resilience Financial regulators Incident management, outsourcing oversight, recovery plans
Data protection Data protection law A lawful basis for processing, retention limits, breach procedures
Complaints The regulator or ombudsman A complaints process with deadlines and records

Not every row is equally heavy for every PSP. A PSP that never holds merchants' money carries lighter safeguarding duties, while one acting as a payment facilitator takes on the scheme rules for every sub-merchant it signs.

Safeguarding and reporting

Safeguarding rules protect merchants if the PSP fails. In the UK, the FCA's new safeguarding rules for payment and e-money firms came into effect on May 7, 2026, and authorized payment and e-money institutions must submit monthly safeguarding reports within 15 business days of each month's end, according to the FCA's safeguarding page.

That makes reconciliation a compliance control, not only a finance task. The report is only as good as the daily match between what merchants are owed and what sits in the safeguarding account.

How to handle PCI DSS compliance as a PSP

A PSP that handles card data is a service provider in PCI DSS terms. Volume sets the level. Visa's service provider requirements put companies handling 300,000 or more Visa transactions a year at Level 1, which means a full assessment rather than a self-assessment, and Visa expects acquirers to make sure their service providers show PCI DSS compliance at least every 12 months.

Licensed gateway software reduces the work but doesn't remove it. On our SaaS, the hosted platform runs under our PCI DSS Level 1 certification. On your own infrastructure you certify your environment, and we support the audit. The PCI DSS guide covers the requirements and the validation cycle in detail.

Authentication and operational resilience in the EU

Article 97 of PSD2 requires strong customer authentication when a payer initiates an electronic payment, so a European PSP needs 3-D Secure in its card flow and a clear policy on exemptions.

Operational resilience now has its own regulation as well. The EU's Digital Operational Resilience Act entered into application on January 17, 2025, according to EIOPA, and it applies to financial entities including payment and e-money institutions. It covers ICT risk and incident reporting as well as the oversight of technology providers, your gateway vendor included.

Compliance across several acquirers and PSPs

Each acquirer adds its own contract terms and audit requests on top of the scheme rules. Handling them one by one multiplies the work, so these habits keep it manageable.

  1. Keep one register of every obligation, its source and its owner, with each acquirer's specific terms marked.
  2. Collect PCI DSS evidence once and reuse it for every acquirer's request.
  3. Monitor fraud and dispute ratios per acquirer as well as per merchant, since each acquirer is measured on its own portfolio.
  4. Hold one set of merchant due diligence records that any acquirer can audit.

The third habit matters most when you route. A merchant moved between acquirers can push one acquirer's ratios over a threshold while the overall numbers look fine.

Where the platform helps

Our white label gateway supplies the controls a compliance team needs evidence from, starting with KYB and KYC at onboarding and real-time transaction monitoring with configurable rules. It adds 3-D Secure with support for an external MPI, tokenization, and an audit trail with role-based permissions.

The platform has a 99.95% uptime SLA, and the SaaS version is covered by our own PCI DSS Level 1 certificate. The obligations themselves, and the decisions behind them, stay with your compliance officer.

Questions

What does compliance for payment service providers cover?

Licensing, safeguarding of merchants' funds, AML and sanctions, PCI DSS, customer authentication, card scheme rules, operational resilience, data protection and complaints handling.

What PCI DSS level does a PSP need?

Under Visa's service provider requirements, a provider handling 300,000 or more Visa transactions a year is Level 1 and needs a full assessment. Smaller providers are Level 2.

How often do UK payment firms report on safeguarding?

Monthly. Authorized payment and e-money institutions submit safeguarding reports within 15 business days of the end of each calendar month.

How can a PSP simplify compliance with several acquirers?

Keep one register of obligations with owners, reuse one set of PCI DSS evidence and merchant records for every acquirer, and monitor fraud and dispute ratios per acquirer.

Review your compliance evidence with us

Tell us your license and your acquirers, and we'll show which controls and records the platform provides for your audits.