Accept BLIK payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.
Before you begin
This page assumes you have already:
- Built your API-only integration.
- Added BLIK in your Customer Area.
An API-only integration of BLIK works with all versions of Checkout API. For more information, refer to Release notes.
Build your payment form for BLIK
To show BLIK in your payment form, you need to:
- Show BLIK as an available payment method.
- Include a field where the shopper can enter the
blikCodefor their corresponding payment.
In your /paymentMethods request, specify:
- countryCode: PL
- amount.currency: PLN
- amount.value: The value of the payment, in minor units
- channel: Specify Web, iOS, or Android
You can find the required fields in the object with type blik.
Adyen provides a logo for BLIK that you can use on your payment form. For more information, refer to Downloading logos.
Make a payment
In your /payments request, specify:
paymentMethod.type: blikpaymentMethod.blikCode: TheblikCodethat the shopper entered.
The /payments response contains:
resultCode: Pending (The shopper must complete the payment in their BLIK app.)action: Use this object to display the waiting screen while the shopper completes the payment in their BLIK app.
Show the waiting screen
- Show a waiting screen to the shopper, telling them you're waiting for them to complete the payment.
- Check your webhooks to see the payment result.
We send you an AUTHORISATION webhook after the shopper completes the payment in their BLIK app. - Once you receive the webhook, redirect them to your website, and present the payment result.
Present the payment result
Use the resultCode that you received in the /payments response to inform your shopper of the payment status.
The resultCode values you can receive for payments made through BLIK are:
| resultCode | Action to take |
|---|---|
| Pending | Show the waiting screen to the shopper, informing them that they have to go to their bank app to complete the payment. |
| Refused | Inform the shopper that the payment is refused, for example, because of incorrect blikCode value. |
Wait for webhooks to know the outcome of the payment. The webhooks you can receive for BLIK are:
| eventCode | success field | Description | Action to take |
|---|---|---|---|
| AUTHORISATION | false | The transaction failed. | Cancel the order and inform the shopper that the payment failed. |
| AUTHORISATION | true | The shopper successfully completed the payment. | Inform the shopper that the payment has been successful and proceed with the order. |
Test and go live
You can test BLIK transactions in the test environment using any 6-digit number that starts with 777 as your blikCode.
You can test different refused payment result scenarios by using the following amounts in your /payments request:
| Refusal reason | Amount |
|---|---|
| ALIAS_DECLINED | 288.00 |
| TAS_DECLINED | 192.00 |
| USER_DECLINED | 144.00 |
| SEC_DECLINED | 216.00 |
| SYSTEM_ERROR | 264.00 |
| GENERAL_ERROR | 360.00 |
| INSUFFICIENT_FUNDS | 120.00 |
| TIMEOUT | 312.00 |
| LIMIT_EXCEEDED | 96.00 |
| USER_TIMEOUT | 336.00 |
| ISSUER_DECLINED | 9.99 |
Check the status of BLIK test payments in your Customer Area > Transactions > Payments.
Before you can accept live BLIK payments, add BLIK in your live Customer Area.