XS2A Adapter

  • live
  • PSD2

There are various ways for a bank to implement a PSD2 compliant XS2A interface. Don’t waste time in connecting different banks with different PSD2 interfaces into your application. Use the free of charge XS2A adapter and concentrate on your true value proposition!

Key Challenge for a Third-Party Provider in Europe

PSD2, as the first regulatory-driven Open Banking initiative, offers many opportunities for both banks and third-party providers (TPPs). TPPs can use the account information and payment services provided by the banks in order to offer new innovative services to the end users. The more banks a TPP can interact with, the more users it can reach with its application, which in consequence raises the value of the application itself.

However, being able to interact with many banks can be a time and cost consuming challenge when developing and maintaining an application. Even though PSD2 sets a standard for bank interfaces, much room for implementation options remains. A bank can have its own PSD2 compliant solution or may have implemented one of the major PSD2 standards, like Open Banking UK, Berlin Group or STET. In general, a PSD2 adapter must be able to process the different messages correctly and react fast to changes on the XS2A interfaces.

The XS2A Adapter Solution by adorsys

The XS2A Adapter is a service component for multi-banking applications. On the one hand, you can interact with the adapter through an own interface based on the Berlin Group specification. On the other hand, the adapter can communicate with different PSD2-interfaces from various banks in Germany and Europe. Our solution is open source and free of charge. It can easily be embedded in your application using either a Java or a REST client. With the help of a growing community, our adapter is kept up-to-date regarding the changes on the XS2A interfaces of the banks. Furthermore, as part of our product vision, a core team will be interacting with the community in order to keep connecting new banks to the adapter.

Icon / 48px / Open SourceCreated with Sketch.


Banks can be connected by the com-munity and changes are quickly applied

Icon / BankCreated with Sketch.


Interaction with the banks that are most relevant for the market, like Sparkasse and Raiffeisenbanken

Icon / Account InformationCreated with Sketch.

Account Information

Aggregate account information like transactions from different banks

Icon / PaymentCreated with Sketch.

Payment Initiation

Let's the user send money from and to different bank accounts

Icon / LikeCreated with Sketch.

One interface,
many options

No matter if Berlin Group, STET or your own XS2A-Intercafe, you only have to communicate with one interface

Icon / IntegrateCreated with Sketch.


Integrate the adapter using the REST-interface or a java client

Use Case

One Adapter - Several Use Cases

With the adapter you are able to fulfill several multi-banking use cases like the aggregation of transactional data and initiation of a payment between different accounts. An application can access the xs2a-interface of a bank by providing the bank code using the standardized interface of the adapter. The adapter is designed so that there is no loss of information when forwarding the response from a bank to the client.

adorsys-xs2a-adapter-infographic@2xCreated with Sketch.PSUTPPAppBank ABank BBank C

Ready to start?

For more information, see the
entire open source project on GitHub.

See GitHub

Any questions?Ask our expert

Stefan Hamm

Managing Director