No momento, esta página não está disponível em português
Payment-method icon

BLIK Android Drop-in

Add BLIK to an existing Android Drop-in integration.

If you are using Android Drop-in v5.0.0 or later:

This payment method requires no additional configuration.

Follow the Drop-in integration guide.

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.

Requirements

Requirement Description
Integration type Make sure that you have an existing Drop-in integration.

BLIK for Android requires at least v3.8.0 of Drop-in. For more information, refer to Release notes.
Setup steps Before you begin, add BLIK in your test Customer Area.

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.

  1. To show BLIK in your payment form, specify in your /paymentMethods request:

    When the shopper proceeds to pay, Drop-in returns the paymentComponentData.paymentMethod.

  2. Pass the paymentComponentData.paymentMethod to 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

  1. Pass the paymentComponentData.paymentMethod value to your server.

  2. From your server, make a POST /payments request, specifying:

    • paymentMethod: The paymentComponentData.paymentMethod from 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 RedirectComponent.getReturnUrl(context).

    The /payments response contains:

    • action: Object containing information about the redirect.

  3. Pass the action object 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 actionComponentData object.

From your server, make a POST /payments/details request providing:

  • details: The actionComponentData.details object 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

Use the 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.

The 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 refusalReason, indicating the cause of the error.
Pending or
Received		 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 have 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

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.

See also