PSD2 and Payment Services Explained
PSD2 and Payment Services Explained: Define which rules apply to the merchant, provider, payment service and jurisdiction before drawing conclusions. This Merchant Atlas guide focuses on europe / eea requirements, cost drivers, operational questions and the evidence to verify before making a provider decision.
Europe / EEA research lens. European payment research should treat the EEA as a set of connected but distinct markets. SEPA, cards, local methods, authentication, currency and country-level customer behaviour can all affect the right setup.
Decision brief
Define which rules apply to the merchant, provider, payment service and jurisdiction before drawing conclusions.
This guide is designed to help a merchant frame the commercial decision behind PSD2 and Payment Services Explained. The objective is not to identify one universally “best” provider, but to make the assumptions, costs, operational dependencies and verification points visible.
What this topic covers
Payments regulation allocates obligations across payment service providers, financial institutions, merchants and consumers. Scope can depend on the activity, legal entity, customer type and country.
Commercial model: what to separate
- Compliance implementation cost
- Authentication or verification requirements
- Data/security obligations
- Provider contract allocation of responsibilities
- Operational impact of changing rules
A useful comparison applies the same transaction profile to every option: monthly value, transaction count, average ticket, card/payment-method mix, customer geography, currencies, refunds and disputes. Without that normalisation, two quotes can look comparable while including different things.
What to measure after launch
- Compliance exceptions
- Authentication outcomes
- Incident response time
- Complaint/dispute trends
- Audit and control findings
Cost is only one output. A cheaper payment setup can still be a poor commercial result if it causes lower conversion, slower settlement, more manual reconciliation or weaker support. Measure payment performance and operational workload alongside price.
Europe / EEA checkpoints
- Distinguish cards from SEPA Credit Transfer, SEPA Direct Debit and local payment methods.
- Check country-level payment behaviour even when a provider markets one EEA product.
- Verify current EU/EEA authentication and payment-services requirements for the specific use case.
- Model EUR and non-EUR acceptance and settlement separately.
Questions to ask before you sign
- Which legal entity is performing the regulated activity?
- Which regulator or authority is relevant?
- Which obligations apply to the merchant versus provider?
- Do customer/business classifications change the rules?
- What has changed since the contract or process was designed?
Common comparison mistakes
- Treating a general guide as legal advice
- Applying one country’s rules to another
- Ignoring the contracting entity
- Assuming old compliance guidance is still current
Use this guide with the rest of Merchant Atlas
Move from this topic into the Research library, then test cost assumptions with the fee calculator and review the research methodology. Provider prices, product scope and payment rules can change, so verify live information before making a material decision.
Continue your Merchant Atlas research
Compare this topic with the wider research library, your market guide and the fee calculator before making a commercial decision.
Sources & verification
Use primary sources before a material decision.
Merchant Atlas uses regulator, scheme, infrastructure and official provider material as the preferred verification layer. Product scope, pricing and rules can change.
Merchant Atlas, “PSD2 and Payment Services Explained,” updated 20 September 2026. https://webpaymentservice.com/psd2-and-payment-services-explained/