blik
blik payments can be processed with Saferpay without much effort. This chapter describes what needs to be considered in this regard.
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.
A valid blik contract.
For blik activation on the Saferpay terminal, please contact your sales contact.
Feature | Support |
❌ | |
Multipart Captures | ❌ |
Secure Card Data | ❌ |
✅ | |
Recurring Payments | ❌ |
3D Secure | ❌ |
Dynamic Currency Conversion (DCC) | ❌ |
Mail Phone Order | ❌ |
✅ | |
Omni-Channel | ❌ |
Integration
The general integration of Blik can only be done via the Payment Page and requires the following things to be noted:
Spec-Version 1.38, or higher.
Important: Blik has been backported to SpecVersions 1.38 - 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.
Furthermore, for other flows (Refunds etc.), please also refer to the table above.
Testing
Please refer to this chapter, if you want to test blik.
Last updated
