VulCode

BLIK payments: by code, code-free and recurring

BLIK on your own page with no redirect, with the store remembered for next time, or in a subscription. We build it through the gateway you choose and match the model to how you sell.

Online payments
The payment step of a store on a phone: BLIK picked and six boxes for the code from the banking app
A code-free BLIK payment on a phone: a request to approve in the banking app, because the store is remembered there

BLIK always goes through a gateway

A shop does not sign with BLIK itself. It accepts BLIK through a settlement agent, a payment gateway integrated with the BLIK system.

  1. Banking app
    the customer's
    A code lives 2 minutesPer the Tpay and Stripe documentation. We design the form and messages around it.
    Confirmation in the bankAfter entering the code the customer approves in the banking app. With Stripe they have 60 seconds.
    payment approval
  2. The BLIK system

    Routes the confirmation request to the app that generated the code.

    confirmation request
  3. Payment gateway
    the settlement agent
    • Przelewy24chargeByCode, chargeByAlias
    • PayUthe code on the store page
    • TpayblikToken, One Click with an alias
    • StripePaymentIntent
    • Paynowa white label payment

    The gateway comparison itself is on our online payments page.

    the code, then a signed result
  4. Your store
    the code form and order statuses
    Złoty onlyBLIK works in PLN. If you sell in other currencies it is one of several methods, not the only one.
    no contract between the store and BLIK

Four BLIK models in a store

Named after the BLIK business materials. Each gateway names them slightly differently.

ModelCustomer stays on your pageA code on every paymentThe BLIK page handles errors and retriesCharge without the customerFor whom
Redirectthe eblik.pl pagenounless the browser is rememberedyesnothe simplest start
Code on your pagenot rememberedyesyesnonostores without customer accounts
Code and a remembered storenext purchases code-freeyesonly the first timenonostores with returning customers
Recurring paymentssubscriptions and billsyesonly when consentingnoyesSaaS, media, insurance, passes
The remembered-store model and recurring payments usually need enabling by the gateway or an annex to the agreement. We check that before writing code.

The life of a recurring payment

From the invitation in the banking app to repeat charges. Most of the work is handling the exits from the main path.

  1. Invitation

    The customer pays by code and gets a consent request for future charges in the banking app.

  2. Consent active

    The gateway returns a token or mandate, which we store with the customer account.

  3. Charge

    Your system initiates a payment without the customer, on the date and amount agreed with them.

  4. Paid

    Service renewed, document issued, next date scheduled.

  • Consent removed or expired

    Removed in the banking app, or past its expiry date. The cycle starts again with a code payment and a new consent.

  • Declined

    No funds or a limit hit. In PayU the gateway does not retry, so your system schedules the retry.

  • The decline path

    On a decline the app retries on an agreed schedule and tells the customer before it blocks access.

Conditions for recurring BLIK

Rules from the gateways' documentation to know before promising a subscription paid by BLIK.

An app panel: one day's BLIK charges, 14 planned, rows paid, declined, with consent removed, above the limit and with consent expired, and the retry schedule in the app

  • A decline, retried by the app

    Retries in the app: attempts 2 and 3, then access paused

    The gateway does not retry it, so the retry schedule and customer messages live in your system.

  • Consent removed or expired

    A row: consent removed in the bank, pay by code at sign-in
    A row: consent expired 30.09, a new consent with a code payment

    The customer removes consent in the banking app, and a consent with an expiry date runs out. Either way we ask for a code payment and a new consent.

  • The amount limit

    A row: PLN 2,388.00, above the PLN 2,000 limit

    PayU gives 2,000 PLN as the maximum single charge without the customer. Higher ones are rejected.

  • The service enabled on the account

    PayU needs an annex to the agreement; Stripe needs the blik_recurring_payments capability active.

  • Liability for fraud

    For charges without the customer, liability moves to the merchant, which PayU marks with a separate parameter.

Common questions about BLIK

Answers about the agreement, code-free payment, the time to confirm and mobile apps.

One-off or by subscription?

Tell us how you sell and which gateway you use or want to use. We will reply within an hour with a BLIK model and a quote.