Essential Info

Implementation with redirection to eblik is the easiest and fastest to implement. When paying with a BLIK code, the user can remember the browser in which he pays and on subsequent purchases in that browser he will not have to enter the BLIK code regardless of which store he was redirected from to eblik.

There are two ways to implement the implementation with redirection to eblik:

•  the User is redirected to the agent's paywall, where he/she selects BLIK payment, and then is transferred to eblik, where he/she can pay using the BLIK code or a memorized browser
• in the section of available payment methods in the Store, the "BLIK" method is displayed, after selecting it (and clicking the commit button, e.g. "Submit") User is directly transferred to the eblik service (recommended implementation)

The main advantage of implementation with direct redirection is that the user immediately sees that he can pay with BLIK in the Store.

Implementing a direct redirect to eblik usually requires the Store to send one additional parameter to the Agent along with the payment details. This parameter will indicate that the selected payment method is BLIK and that the customer does not need to be presented with a paywall (the Agent's service). Upon receiving such a parameter, the integrator will skip its page and redirect the user directly to eblik

Green screens - store

Purple screens- user's banking app

ENG:

Example of the process of remembering the browser when deployed with direct redirection

An example of a process with one bank application memorized when deployed with direct redirection

An example of a process with multiple banking applications memorized when deployed with direct redirection