BLIK payments

BLIK is a single use payment method that requires customers to authenticate their payments. When customers want to pay online using BLIK, they request a six-digit code from their banking application and enter it into the payment collection form.

The bank sends a push notification to your customer’s mobile phone asking to authorize the payment inside their banking application. The BLIK code is valid for 2 minutes; customers have 60 seconds to authorize the payment after starting a payment. After 60 seconds, it times out and they must request a new BLIK code. Customers typically approve BLIK payments in less than 10 seconds.

Payment flow

Customer selects BLIK at checkout.

Customer is directed to their mobile banking app to generate a 6-digit code.

Customer puts the code into the checkout.

Customer is notified that payment is complete.

Get started

You don’t actually have to integrate BLIK and other payment methods individually. If you use our front-end products, Stripe automatically determines the most relevant payment methods to display. Follow a quickstart for one of our hosted UIs:

• Checkout: Our prebuilt, hosted checkout page.
• Elements: Our drop-in UI components.

After setting up your payment form, activate the payment methods you want using the Stripe Dashboard.

If you prefer to manually list payment methods, learn how to manually configure BLIK as a payment.

Disputed payments

BLIK has a claims process that allows transaction disputes. Customers can open disputes for cases of suspected fraud, double payments, or a difference between an order and a transaction amount.

After the customer initiates a dispute, Stripe notifies you using:

• Email
• The Stripe Dashboard
• An API charge.dispute.created event (if your integration is set up to receive webhooks)

Stripe holds back the disputed amount from your balance until BLIK resolves the dispute.

We request that you upload compelling evidence proving that you fulfilled the purchase order using the Stripe Dashboard. This evidence can include the:

• Tracking ID
• Shipping date
• Record of purchase for intangible goods, such as IP address or email receipt
• Record of purchase for services or physical goods, such as phone number or proof of receipt
• Record of refund (for purchase you have already refunded)

To handle disputes programmatically, respond to disputes using the API.

This information helps BLIK determine if a dispute is valid. Make sure the evidence you provide contains as much detail as possible from what the customer provided at checkout. You must submit the requested information within 12 calendar days. If BLIK resolves the dispute with you winning, we return the disputed amount to your Stripe balance. If BLIK rules in favor of the customer, the balance charge becomes permanent.

Refunds

BLIK supports full and partial refunds. Depending on the bank, refunds are processed immediately or within a couple of hours.

Connect

If you use Connect, you must consider the following before you enable and use BLIK.

Request BLIK capabilities for your connected accounts

Set the blik_payments capability to active on your platform account, and on any connected accounts you want to enable BLIK for. You can also request more account capabilities.

Merchant of record and statement descriptors

The charge type of Connect payments might change the default statement descriptor and the merchant name that appears on the customer’s banking application and confirmation emails.