BLIK iOS Drop-in

On this page, you can find additional configuration for adding BLIK to your Drop-in integration.

Before you begin

This page assumes you have already:

• Built your Drop-in integration.
• Added BLIK in your Customer Area.

BLIK for iOS requires at least v3.8.0 of Drop-in. For more information, refer to Release notes.

API reference

Include fields for the endpoint you integrated:

/sessions /payments

/sessions /payments

You don't need to send additional fields for BLIK. To see optional fields that you can send for all payment methods, see:

• /sessions: This is the default with Drop-in v5.0.0 or later.

You must include the following additional fields when making a /payments request with BLIK:

Parameter name	Required	Description
paymentMethod.type		Set this value to blik.
paymentMethod.blikCode		The six-digit code from the shopper's banking app.

For a full list of optional fields that you can send for all payment methods, see /payments.

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.

Drop-in configuration

There is no BLIK specific configuration for Drop-in.

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:

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