BLIK

BLIK payments can be processed with Saferpay without much effort. This chapter describes what needs to be considered in this regard.

General requirements

The handling of BLIK payments with Saferpay requires:

• A corresponding license and thus a valid identification with a username and password for the Saferpay system.

• Availability of at least one active Saferpay terminal via which payment can be carried out and availability of the associated Saferpay TerminalId.

Need a BLIK contract? Simply contact our sales to get one.

Technical requirements

The general integration of BLIK can only be done via the Payment Page or the Transaction Interface (see Alternative Mode) and requires the following things to be noted:

• SpecVersion 1.38 or higher.

  • Important: BLIK has been backported to SpecVersions 1.38 to 1.42. When implementing BLIK for Spec-Versions lower than 1.43, please make sure that your implementation is capable of processing the new values returned by the Saferpay API, e.g. PaymentMethods now returning "BLIK" as a value, which was previously not specified.

• For Alternative Mode:

  • Payer.IpAddress is mandatory.

  • Payer.UserAgent is mandatory.

Furthermore, for other flows (Refunds etc.), please also refer to the table below.

Supported features

Feature	Support
Capture/Cancel	❌
Multipart Captures	❌
Secure Card Data	❌
Refunds	✅
Recurring Payments	❌
3D Secure	❌
Dynamic Currency Conversion (DCC)	❌
Mail Phone Order	❌
Testing	✅
Omni-Channel	❌

Alternative Mode

As an alternative to the Payment Page, BLIK can be seamlessly integrated into the webshop using the Alternative Payment interface.

Flow description

1. First, the merchant's application needs to display a code field during checkout.

2. Said code is generated inside the BLIK app on the payer's device. This code then has to be entered inside the webshop.

3. Once the form has been submitted, the shop initializes the payment using the Transaction AlternativePayment request.

4. This request initiates two things in the background.

   1. Once initiated, Saferpay will generate a payment token and return it with the AlternativePayment response.

   2. This token must be saved by the shop in order to initiate further processing.

5. At the same time, BLIK will send a notification to the payer's device. The payer then acknowledges and confirms the payment inside the app.

6. Upon successful processing, Saferpay will receive the payment data and notify the shop by calling the Notification.StateNotificationUrl that has been defined with the AlternativePayment request.

7. The shop then uses the previously saved payment token and queries the payment data using the Transaction QueryAlternativePayment request. The shop verifies the response and shows the payment result to the payer. With that, the payment is finished.

Please remember the mandatory additional data for the AlternativePayment request.

Testing

Please refer to this chapter if you want to test BLIK.