Ways of integration

Saferpay consists of two main interfaces and a set of different additional modules that can be added to each interface depending on the business requirements 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

(click to enlarge)

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.

Supported payment methods per interface

Payment method	Transaction Interface	Payment Page
Visa/V PAY	✅	✅
Mastercard	✅	✅
Maestro International	✅	✅
American Express	✅	✅
Bancontact	✅	✅
blik		✅
Click to Pay	❌	✅
Diners Club/Discover	✅	✅
JCB	✅	✅
SEPA Direct Debit	✅	✅
PayPal	❌	✅
Przelewy24	❌	✅
eps	❌	✅
iDEAL	❌	✅
Twint		✅
Unionpay	❌	✅
Alipay+	❌	✅
Apple Pay (Wallet)		✅
Klarna Payments + Billie	❌	✅
Google Pay (Wallet)		✅
PostFinance Pay		✅
WeChat Pay	❌	✅
Account-to-Account Payments	❌	✅
Reka	❌	✅
Wero	❌	✅
Boncard OeV Lunch-Check	❌	✅

-Integration via this method requires special attention. See the respective payment method chapter for more information!

Which interface should I choose??

Before implementing, it is important to clarify which functions are important for you.

Use the PaymentPage if...

• You only want to process transactions: Do you have a small and simple webshop? Are refunds via the API or recurring payments not important for you? Then the Payment Page is the method of choice for you.

• You want to have one solution for every payment method: The PaymentPage supports every payment method Saferpay does offer. Once integrated, it is a simple matter of activating the payment methods you need, and they will show up on the page.

Use the Transaction Interface if...

• You want a more embedded or integrated solution: The Transaction Interface does offer a more integrated and personalized payment flow for credit cards, via the Saferpay Fields, or iframe integration. Think of it as the Payment Page reduced to the card entry form, which can be embedded into every HTML-based application.

• You want to do recurring payments: Recurring Payments require special API functions that are only available through the Transaction Interface.

• You want to execute refunds via the API: Refunds via API (note that refunds are also possible via the Saferpay Backoffice) are only possible with the Transaction Interface.

• You want to save and use card data in our Secure Card Data store: Similar to recurring payments, but Secure Card Data can do more than just that. Furthermore, you could also spare your customer from entering their card data over and over again, even for 3D Secure payments.

Why not both?

You don't have to stick to one interface or the other; you can also mix both interfaces.

In some cases, you have to use the PaymentPage. For example, if you want to use PayPal or any other third-party provider.

Another use case could be that you do all your normal authorizations over the PaymentPage, but then you use the Transaction Interface for Refunds.

If you decide to upgrade your license and already have a PaymentPage Integration, you can simply extend your integration to include the functions you need, without changing the entire existing implementation.

Questions?

Still unsure what you need?

Contact the Saferpay Integration Support and we will help you decide.