Ways of integration
Last updated
Last updated
Saferpay consists of two main interfaces and a set of different additional modules that can be added to each interface depending on the business requriements and desired payment flow.
The main components of the Saferpay JSON API are:
Payment Page Interface
Transaction Interface
and the additional Secure Card Data module
It is important to understand the different intended uses and functionalities of each component to decide which Interface is best suited for your business and desired payment flows.
Before implementing, it is important to clarify which functions are important for you.
If you have access to Saferpay Business, you also have access to all API functions Saferpay has to offer. You don't have to stick to one interface or the other, you can also mix both interfaces.
Still unsure what you need?
-Integration via this method requires special attention. See the respective payment method chapter for more information!
You only want to do transactions: Do you have a small and simple web shop? Are , or not important for you? The Payment Page and a regular E-Commerce contract probably are sufficient for you.
You want to have one solution for every payment method: does support every payment method Saferpay has to offer. Once integrated, it is a simple matter of activating the payment methods you need, and they will show up on the page.
You want a more embedded/integrated solution: does offer a more integrated and personalized payment flow for credit cards, via , or . Think of it as reduced down to the card entry form, which can be embedded into every HTML-based application.
You want to do recurring payments: need special API functions, that are only available over Saferpay Business!
You want to execute refunds via the API: (Consider that refunds are also possible via the Saferpay Backoffice) are only possible with the transaction interface and a Saferpay Business license.
You want to save and use card data in our Secure Card Data store: Similar to , but Secure Card Data can do more than just that. Furthermore, you could also spare your customer from entering his card data over and over again, even for 3D Secure payments.
In some cases, you have to use the . For example, if you want to use , or any other 3rd party provider.
Another use case could be that you do all your normal authorizations over the , but then you use the .
If you decide to upgrade from E-Commerce to Business (For example for executing refunds via API) and already have a , you can simply extend your integration for the functions you need, without changing the whole existing implementation.
and we will help you to decide.
Payment method
Transaction Interface
Payment Page
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
❌
✅
❌
✅
❌
✅
❌
✅
❌
✅
❌
✅
❌
✅
✅
❌
✅
❌
✅
✅
Klarna Payments + Billie
❌
✅
❌
✅
✅
✅
❌
✅
❌
✅
