Our Android Drop-in renders BLIK in your payment form, and redirects the shopper to complete the payment. As with other redirect payment methods, you need to check the payment result after the shopper returns to your app.
Before you begin
This page assumes you have already:
BLIK for Android requires at least v3.8.0 of Drop-in. For more information, refer to Release notes.
Show BLIK in your payment form
Drop-in uses the
countryCode and the
amount.currency from your /paymentMethods request to show the available payment methods to your shopper.
To show BLIK in your payment form, specify in your /paymentMethods request:
When the shopper proceeds to pay, Drop-in returns the
paymentComponentData.paymentMethodto your server.
These are the shopper details that you need to make the payment.
Adyen provides a logo for BLIK that you can use on your payment form. For more information, refer to Downloading logos.
Make a payment
paymentComponentData.paymentMethodvalue to your server.
From your server, make a POST /payments request, specifying:
paymentComponentData.paymentMethodfrom your client app.
returnURL: The URL the shopper is redirected to after they complete the payment. This URL can have a maximum of 1024 characters. Get this URL from the Component in the
The /payments response contains:
action: Object containing information about the redirect.
actionobject to your client app.
Check the payment result
Drop-in redirects the shopper to complete the payment. When the shopper returns back to your app, Drop-in provides the
From your server, make a POST /payments/details request providing:
actionComponentData.detailsobject from Drop-in.
You receive a response containing:
resultCode: Use this to present the payment result to your shopper.
pspReference: Our unique identifier for the transaction.
Present the payment result
resultCode from the /payments/details response to show the payment outcome on your frontend.
You will also receive the outcome of the payment asynchronously in a webhook.
resultCode values you can receive for BLIK are:
|resultCode||Description||Action to take|
|Authorised||The payment was successful.||Inform the shopper that the payment has been successful.
You will receive the funds in 2-3 days.
|Error||There was an error when the payment was being processed.||Inform the shopper that there was an error processing their payment. The response contains a
|The shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the payments network to confirm this.||Inform the shopper that you've received their order, and are waiting for the payment to be completed.
You will receive the final result of the payment in an AUTHORISATION webhook.
|Refused||The payment was refused by the shopper's bank.||Ask the shopper to try the payment again using a different payment method.|
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
There is no test environment available for BLIK. You can test BLIK transactions in the live environment using any 6-digit number that starts with 777 as your
You can test different refused payment result scenarios by using the following amounts in your /payments request:
Check the status of BLIK test payments in your Customer Area > Transactions > Payments.