BLIK
Beta

BLIK is a popular mobile payment method in Poland that enables users to make instant payments using their mobile banking app. Embedded in banking applications, it's supported by all major Polish banks.

BLIK enables customers to perform one-time purchases, or sign up for a recurring payment.

Information

To enable BLIK payments on your account, contact your account manager or request support.

Model	Collecting
Payment flow	Direct
Payment method type	Account to account
Auto-capture payment
Manual-capture payment
Refund	Full and partial refunds
Recurring payment
Disputes

To process recurring payments with BLIK, you need a BLIK PayID. This ID enables you to set up an agreement to process merchant-initiated transactions (MITs), so your customer does not need to authorize the payment every time.

You can process recurring payments in two ways:

Storing your BLIK PayID with Checkout.com
Storing your BLIK PayID on your own

Checkout.com creates a payment instrument to store the agreement. You then provide either our payment instrument or your BLIK PayID in subsequent transactions to process the payment.

You can create a standalone agreement, or create the agreement during the initial payment.

BLIK supports two recurring models. Choose the one that matches your subscription type:

Model	Use case
Model A	Fixed-cost subscriptions, such as a 12-month plan billed at the same amount on a fixed schedule. Both amount and frequency of the payments are fixed when creating the agreement.
Model O	Variable-cost subscriptions, such as usage-based billing or marketplace top-ups. Both amount and frequency of the payments vary per merchant-initiated transaction.

Model

Use case

Model A

Fixed-cost subscriptions, such as a 12-month plan billed at the same amount on a fixed schedule.

Both amount and frequency of the payments are fixed when creating the agreement.

Model O

Variable-cost subscriptions, such as usage-based billing or marketplace top-ups.

Both amount and frequency of the payments vary per merchant-initiated transaction.

If you know the exact amount and schedule at signup, use Model A. If either is variable or unknown, use Model O.

For Model O, you can set a fixed expiry date. If you do not provide an expiry date for the agreement, it is valid for a maximum period of 10 years.

The onboarding process for BLIK Recurring is manual. BLIK must approve you to onboard into the recurring model and review your UX implementation before you can process BLIK payments.

For more information about processing BLIK recurring payments, contact your account manager or request support.

When integrating with BLIK, you can configure the following webhooks using the API, or the Dashboard:

Webhook	Description
`payment_pending`	Occurs when an asynchronous payment request has successfully initiated. See example.
`payment_capture_pending`	Occurs when the customer approves the payment on the BLIK app. See example.
`payment_captured`	Occurs when a capture is successful. See example.
`payment_capture_declined`	Occurs when a capture is declined. See example.
`payment_declined`	Occurs when a payment authorization request times out, or if there is a rejection during authorization. For example, due to insufficient funds, the issuer blocking the transaction, or a Do Not Honor instruction. See example.
`payment_expired`	Occurs when an APM payment expires. See example.
`payment_voided`	Occurs when: The payment is voided after authorization. The payment is voided after partial capture, releasing the remaining amount. The payment expires.
`payment_void_declined`	Occurs when a void request is declined.
`payment_refunded`	Occurs when the payment is fully or partially refunded.
`payment_refund_declined`	Occurs when a refund is declined.

BLIK
Beta

Information

Recurring payments

Recurring models

Onboarding

Manage webhooks

Available on

Web

Payment Setup API

API only