PSD3 · PSR · Berlin Group openFinance Framework

Your PSD2 setup wasn't built for what's next

Salt Edge covers PSD3 and PSR compliance for ASPSPs, including fraud data sharing under FRIDA, and Premium APIs.

Last updated:

PSD3 and PSR regulatory timeline showing expected EU approval in December 2026, publication in early 2027, EBA technical standards in 2027-2028, and PSD3/PSR compliance milestones in Q4 2028.
What is your current PSD2 setup?

Whatever your setup, make compliance a low, predictable cost

We plug into your existing gateway or middleware to deliver off-the-shelf compliance, and if you are migrating from a vendor, we reuse your existing integration layer to keep the switch minimal.
Your current setup
Typical stack
What breaks at PSD3/PSR layer
Salt Edge fit

In-house/API Gateway build + vendor

  • API gateway
  • Custom/Berlin Group/STET/Polish API implementation
  • Third-party TPP validation layer
  • In-house TPP management

Each new regulation adds complexity and extra cost to maintain in-house.

Predictable lower cost, all compliance and TPP management absorbed.

Consortium member

  • National or group scheme

Consortium roadmap rarely covers Premium APIs at the speed individual banks want. Commercial flexibility is capped.

In addition to PSD3/PSR compliance, adds Premium APIs outside the scheme's scope and supports your connection to FRIDA.

Vendor-managed

  • Legacy, regional player, or small PSD2 vendor

Underperforming APIs, friction-filled journeys, manual TPP management, PSR reporting, and few monetisable Premium APIs.

Future compliance absorbed, Premium APIs unlocked, minimal migration burden.

EMI (future payment institutions)

  • Basic fallback interface
  • Generic gateway
  • Manual TPP onboarding
  • Unmaintained API placeholder

Under the PSR, a dedicated API is mandatory. Either prove your accounts are out of scope, or comply in full.

All future compliance absorbed, at minimal cost, delivered in weeks.

Request a workshop

Ways to get there

Run your own PSD3 & PSR readiness analysis or do it with us

Start with the handbook, or work with our team on your regulatory and Premium API roadmap.

 

PSD3 & PSR handbook

What PSD3 and PSR change for your setup: in-house, consortium or vendor.

Read the handbook
  • PDF
  • ~6 min read
  • No email required
Recommended

PSD3/PSR & Premium APIs workshop

A working session under NDA on your architecture and your PSD3/PSR and Premium API roadmap.

Request a workshop
  • 3-hour working session
  • Under NDA, non-binding
  • Written roadmap output

Salt Edge's PSD3/PSR layer is already available for its 100+ customers

Banks and payment institutions in the EEA and beyond have delegated their regulatory layer to Salt Edge.
Salt Edge clients include HyperJar, Bank of Valletta, Curve, Landsbankinn, Sodexo, Ahli, Western Union, GTCO and LHV

The architecture

Salt Edge Open Finance suite. Two layers. Comply with every regulation. Monetise your APIs

Layer 1

PSD3/PSR Compliance

Future compliance requirements absorbed out of the box.

  • Berlin Group/Open Finance framework
  • Consent dashboard and consent management API
  • Availability and performance at PSR levels
  • Statistics and reporting to your NCA
  • SCA orchestration and exemptions
  • Fraud data sharing obligations covered, including connection to FRIDA
  • Full audit trail for every API call and consent event
  • TPP first-line support
  • Sandbox and developer documentation

Layer 2

Premium APIs

Turn your API layer into a revenue stream by opening your Berlin Group openFinance Framework APIs to commercial partners, corporates, and embedded-finance platforms.

  • Premium AIS and PIS
  • Variable recurring payments, sweeping and Request to Pay
  • Real-time account notifications
  • Corporate PIS, single and bulk
  • ERP integration and multi-banking APIs
  • Corporate access monitoring dashboard
  • Direct access. Embedded banking

Where Salt Edge sits

Salt Edge against your alternatives

Salt Edge

Other vendor
In-house build
Consortium
Standards & regulatory updates

Berlin Group openFinance Framework, EBA RTS, PSR

Included in fixed licence

Typically included

Recurring project
At the scheme's pace
FRIDA connectivity support
Connection to your chosen FIP, or to the FCP if the final rulebook allows it
Roadmap-dependent
New build
Scheme-dependent
TPP lifecycle management

Onboarding, verification, monitoring, support

End-to-end TPP lifecycle
Usually no
Requires ops team
Outside mandate
Fraud screening, audit & traceability

PSR-aligned controls

Native, real-time controls
Varies
Internal build
Scheme-dependent
Core banking pre-integration

Tuum, Temenos, Finastra, proprietary cores

Yes. Live customers
No
N/A
Limited
Cost of switching to Salt Edge

From each current setup

Low from every setup
Low. Existing integrations are typically reusable
Low. Salt Edge plugs into your gateway
Low. Standard integration time, redirection possible
Premium APIs
Native. Pre-integrated in ERPs.
Limited; few vendors offer them on the same platform
FTE-heavy and operationally complex
Outside scope
Time to PSD3/PSR compliance
Already done for PSD2 customers, several weeks for new
3-6 months
6-18 months
Scheme-paced
Total cost of ownership
Fixed licence, usage included; predictable cost
Depends on the vendor; surcharges for each new regulation
FTE-heavy; compounds with every new regulation
Shared cost, limited control over scope, pace, and quality

Find out what PSD3 and PSR will cost you, and how much you could save by switching.

We stopped asking banks what compliance costs them. We started asking what inaction is costing them.
a photo of the author
Andrei Scutari
Head of Enterprise Sales at Salt Edge
Fill out the form to get started
FAQ

Regulation

What is the difference between PSD2, PSD3 and the PSR?

PSD3 is a Directive on the authorisation and supervision of payment institutions and EMIs, applied through national law. The PSR is a Regulation that applies directly in every EU country and contains the open banking conduct rules: API performance, permission dashboards, fraud rules and strong customer authentication.

When people refer to "PSD3 API requirements", the obligations they mean sit in the PSR. Salt Edge delivers the PSR conduct layer for banks, EMIs and payment institutions.

When do PSD3 and the PSR apply?

Most PSR rules are expected to apply in the fourth quarter of 2028, 21 months after entry into force. PSD3 must be transposed into national law on the same timeline.

The European Parliament plenary vote is indicated for December 2026, publication in the Official Journal is expected in early 2027, and the texts enter into force 20 days after publication. Until then, PSD2 and the SCA technical standards remain in force. Salt Edge implements each standard release as part of the platform licence.

What happened to FiDA?

On 4 November 2026, the European Commission announced in its 2027 work programme that it will withdraw the proposal for the Financial Data Access Regulation (FiDA).

FiDA would have extended data sharing to savings, investments, mortgages, pensions and insurance. Without FiDA, sharing this data depends on commercial agreements. The PSR obligations are not affected, and the same Berlin Group openFinance Framework interface used for PSR compliance also supports Premium APIs.

What does the PSR require from banks for open banking APIs?

The PSR makes the dedicated API the main access route and sets three duties. The API must perform at least as well as the interface the bank offers its own customers. Customers must get a permission dashboard to withdraw third-party access in real time. The standing fallback interface is replaced by a contingency mechanism supervised by the competent authority.

The EBA will set the performance indicators in technical standards. Salt Edge implements each standards release, including the contingency mechanism, as part of the platform licence.

Does the PSR apply to electronic money institutions and payment institutions, or only to banks?

The PSR applies to all account-servicing payment service providers that hold payment accounts: banks, electronic money institutions and payment institutions. Smaller institutions are not exempt from the API duties. Either the accounts are proven out of scope, or the institution complies in full.

Salt Edge delivers the compliance layer for smaller institutions in weeks.

FRIDA

What is FRIDA?

FRIDA, the Fraud Information Distribution Arrangement, is a European Payments Council (EPC) scheme that sets common rules for how payment service providers share fraud information. It responds to the PSR obligation to share fraud data.

Each provider connects through a Fraud Information Platform (FIP) to a central Fraud Collection Point (FCP), owned by the EPC, which distributes alerts to the other FIPs. The scope is account-to-account payments: SEPA Credit Transfer, SEPA Instant Credit Transfer, SEPA Direct Debit Core and B2B, and One-Leg Out Instant Credit Transfer. Card payments are not in scope.

What does FRIDA require from a bank, and how does the bank connect?

In the draft rulebook, a bank sends and receives fraud alerts through a Fraud Information Platform (FIP) of its choice, and confirms or rejects alerts on accounts it holds. Each alert carries mandatory fields, including the IBAN, the fraud type under the EBA fraud taxonomy, identifiers, timestamps and a status, delivered by push or by pull at least once a day.

An alert is a risk signal, not an instruction to block a payment. Whether a bank can also connect directly to the FCP is a consultation question that the final rulebook will decide.

When does FRIDA apply?

FRIDA is expected to apply together with the PSR fraud data sharing obligation, in the fourth quarter of 2028.

The consultation on the draft rulebook (EPC108-26, version 0.1) closes on 10 December 2026. The EPC plans to publish version 1.0 and the technical specifications in mid-2027.

How does Salt Edge support fraud data sharing?

Salt Edge covers the PSR fraud data sharing obligation as part of the compliance layer, including the connection to FRIDA. Salt Edge is not a FIP. It provides the connection and the operations around it.

Salt Edge connects the bank to the FIP it chooses, or to the FCP directly if the final rulebook allows it, maps fraud data to the mandatory alert fields and the EBA fraud taxonomy, and runs the daily flow of alerts, including passing them to the bank's transaction monitoring.

Buying and switching

Which vendors provide PSD3 and PSR compliance for banks?

Institutions have three options: build the interface in-house, join a national or sector consortium, or use a specialist compliance vendor. Salt Edge is a specialist vendor: an ASPSP compliance and open finance platform covering PSD2, the PSR conduct rules and Premium APIs on the Berlin Group openFinance Framework.

Salt Edge customers include Landsbankinn, Bank of Valletta and LHV in the EEA, and Guaranty Trust Bank and Jordan Ahli Bank outside it.

Should a bank build PSD3 and PSR compliance in-house or use a vendor, and what does it cost?

Both are valid. The cost depends on the starting point, the connection to core systems and the target scope: the PSR only, or the PSR plus Premium APIs. An in-house build must cover standards implementation, regulatory monitoring, third-party operations and interface performance continuously, so most of the cost is recurring.

In a workshop under NDA, the Salt Edge enterprise team produces a written recommendation and an implementation roadmap based on your architecture.

We are in a national consortium. Does it cover Premium APIs, and do we still need anything?

A consortium usually covers the regulated baseline, but Premium APIs are generally outside its scope and its roadmap moves at the scheme's pace. Ask the consortium whether it will offer Premium APIs. Many do not.

Salt Edge adds Premium APIs on top of what the consortium already delivers, and supports your connection to FRIDA.

We already use a PSD2 vendor. How hard is it to switch, and how quickly can Salt Edge deliver?

Switching is an integration project, not a rebuild, because the migration reuses your existing integration layer. The effort depends on the core banking connection and the target scope.

For institutions already on Salt Edge for PSD2, PSR compliance is delivered as part of the platform. For a new institution, the timeline is measured in weeks, against the six to eighteen months an in-house build typically takes.

What are Premium APIs (Commercial APIs) and what does Salt Edge offer?

Premium APIs are services beyond the regulated baseline that a bank can offer commercially. The regulated baseline must be free of charge. Premium APIs can be priced and sold to commercial partners, corporates and embedded finance platforms, using the same interface the bank built for PSD3/PSR compliance.

Salt Edge offers all Premium APIs in the scope of the Berlin Group openFinance Framework as standard. Where a bank requests it, Salt Edge also builds custom APIs.