General level 0 Requirements

Visibility of the BLIK logo

1. Go to the payment method selection screen

The BLIK payment method is marked with the BLIK logo.

The logotype used is consistent with the BLIK brand book.

BLIK in Level 0 on the first screen for selecting a payment method

1. Go to the payment method selection screen

BLIK must be a visible, selectable form of payment directly from the shop's service.

BLIK is first on the list of payment methods

1. Go to the payment method selection screen

We encourage you to display BLIK first on the list, as it is the most popular online payment method in Poland.

Rules of spelling

1. Verify BLIK spelling on all screens where reference appears

All references to BLIK are written in capital letters.

BLIK

BLIK, BLIKIEM, BLIKOWI itd.

BLIK code field - input without numeric placeholder

1. Select the BLIK payment method, and continue the process until you see a field for entering the BLIK cod

Input for entering the BLIK code should be an empty input without any numerical placeholder (e.g. 111 111, 123 456, or other string of digits).

BLIK code field - length of the field

1. Select the BLIK payment method, and continue the process until you see a field for entering the BLIK cod

The width of the field should match the value to be entered there (6 characters with a gap after 3 characters).

BLIK code field - two groups of three digits

1. Select the BLIK payment method, and continue the process until you see a field for entering the BLIK cod

2. Enter the 6-digit BLIK code

The BLIK code should be displayed centered, in two groups of three digits in a single field.

BLIK code field - numeic keyboard (mobile)

Perform the tests on your mobile device:

1. Select the BLIK payment method, and continue the process until you see a field to enter the BLIK code

2. Click on the BLIK code field

On mobile, the input should call up the numeric keyboard.

BLIK code field - character restrictions

1. Select the BLIK payment method, and continue the process until you see a field to enter the BLIK code

2. Click on the BLIK code field

• The maximum number of digits that can be entered is 6

• Characters other than digits and more than 6 digits cannot be pasted into the field

BLIK code field - no autocomplete

1. Select the BLIK payment method, and continue the process until you see a field to enter the BLIK code

2. Click on the BLIK code field

Input for entering the BLIK code should not have the autocomplete attribute (disabled prompting for last entered BLIK codes or other passwords)

BLIK code field - activation by pressing the field

1. Select the BLIK payment method, and continue the process until you see a field to enter the BLIK code

Input for entering the BLIK code should not be automatically activated, it should only activate when the user presses it.

BLIK code field - field naming and supporting messages

1. Select the BLIK payment method, and continue the process until you see a field to enter the BLIK code

The text should clearly inform the user that they are to generate a BLIK code in the banking application and then confirm the payment.

• Recommended header messages instructing to enter the BLIK code:

  • ENG: "Enter the BLIK code", "Enter the 6-digit BLIK code".

  • PL:" Wprowadź kod BLIK", Wprowadź 6-cyfrowy kod BLIK"

• Recommended messages instructing where to find the code:

  • ENG: "You can find the BLIK code in your banking app".

  • PL: "Kod BLIK znajdziesz w aplikacji swojego banku"

• Recommended terms for BLIK code and the name of the BLIK code entry field:

  • ENG: "BLIK code".

  • PL: "Kod BLIK"

In relation to the BLIK code, the terms are not used:

• ENG: "Authorisation code", and "BLIK authorization code".

• PL: 'Kod autoryzacyjny", "Kod autoryzacji BLIK"

BLIK payment - instructions, tooltips

1. Select the BLIK payment method, and continue the process until you see a field to enter the BLIK code

Additional elements (instructions, tooltips, etc.) relating to BLIK payment are not links to external websites or other elements that "throw" the User out of the process.

Additional elements should not cover the BLIK code entry field at any time during the payment process.

In addition, they should not affect the ability to quickly identify the input field as a BLIK code entry field.

Moving to the next payment step using the commit button

1. Select the BLIK payment method, and continue the process until you see a field to enter the BLIK code

2. Enter a valid BLIK code

Moving to the next payment step after entering a valid BLIK code should be done using a commit button.

Recommended button wording: "Pay", "Next".

We recommend that the button should not contain an icon inappropriate to its function, e.g. a padlock icon

Empty field for entering the BLIK code

1. Select a BLIK payment method and leave the BLIK code field blank.

2. If possible, click on the button responsible for moving to the next step ("pay", "next" or similar button)

The user should receive an error message. We recommend dynamic handling of this type of error.
Recommended message content:

• ENG: "Enter the BLIK code".

• PL: "Podaj kod BLIK"

Location of the BLIK code input

1. Select the BLIK payment method, and continue the process until you see a field to enter the BLIK code

The field for entering the code should be in the same section of the service as the selection of a payment method (the user focusing his/her eyes on the selection of a payment method may not notice that input for entering the BLIK code has appeared in another section).

Input for entering the BLIK codes should be visible, immediately identifiable as one where the should enter a BLIK code (and not, for example, a discount code) and not covered by any other system element.

Confirmation in the banking application - user guide

1. Enter the BLIK code and proceed to the payment step, which requires confirmation of the transaction in the banking app

If the BLIK code is correct, a message should be displayed prompting the user to confirm the payment in the banking application.

On the screen, the user shouldn't have any other actions to perform at this step, the user's attention shouldn't be distracted to confirm the transaction.

Recommended text is shown on the screen:

• ENG: "Confirm the payment
in your banking app".

• PL: "Potwierdź płatność w aplikacji swojego banku"

A graphic/icon/animation of the phone is recommended.

Display of the successful payment status page

1. Enter the BLIK code and proceed to the payment step, which requires confirmation of the transaction in the banking app

2. Confirm the transaction in the banking app

The shop presents the user with information on successful payment - displaying a thank-you page for the purchase.

Display of thanks page for purchase - commit button

1. Enter the BLIK code and proceed to the payment step, which requires confirmation of the transaction in the banking app

2. Confirm the transaction in the banking app

We recommend adding a commit button to return to the order details page instead of using an automatic redirect.

Unsuccessful transaction - displaying status information and clearing the BLIK code entry field

1. Proceed with the transaction by triggering any error (invalid BLIK code, rejected transaction, timeout, or other).

When an error occurs:

• transaction error message must be displayed informing the user of the real cause of the error

• the user must be able to repeat the transaction

• the field for entering the BLIK code is cleared, the user can immediately enter a new code.

Wrong BLIK code
(ER_WRONG_TICKET)

1. Proceed with the transaction using an incorrect BLIK code

The user should receive an error message. Recommended content:

"Incorrect BLIK code was entered. Try again."

Expired BLIK code
(ER_TIC_EXPIRED)

1. Proceed with the transaction using an expired BLIK code

The user should receive an error message. Recommended content:

• ENG: "Incorrect BLIK code was entered. Try again."

• PL: "Podano błędny kod BLIK. Spróbuj ponownie."

Cancelled BLIK code
(ER_TIC_STS)

1. Proceed with the transaction using a canceled BLIK code

The user should receive an error message. Recommended content:

• ENG: "Incorrect BLIK code was entered. Try again."

• PL: "Podano błędny kod BLIK. Spróbuj ponownie."

Used BLIK code
(ER_TIC_USED)

1. Proceed with the transaction using a used BLIK code

The user should receive an error message. Recommended content:

• ENG: "Incorrect BLIK code was entered. Try again."

• PL: "Podano błędny kod BLIK. Spróbuj ponownie."

Insufficient funds
(INSUFFICIENT_FUNDS)

1. Proceed with the transaction without sufficient funds in your account

The user should receive an error message. Recommended content:

• ENG: "Payment failed. Check the reason in the banking application and try again."

• PL: "Płatność nieudana. Sprawdź powód w aplikacji bankowej i spróbuj ponownie"

Exceeding the transaction limit
(LIMIT_EXCEEDED)

1. Proceed with the transaction that exceeds the transaction limit set in the bank.

The user should receive an error message. Recommended content:

• ENG: "Payment failed. Check the reason in the banking application and try again."

• PL: "Płatność nieudana. Sprawdź powód w aplikacji bankowej i spróbuj ponownie"

Rejection due to incorrect PIN
(ER_BAD_PIN)

1. Proceed with the transaction by entering the wrong PIN several times in the banking app (the number of attempts depends on the bank).

The user should receive an error message. Recommended content:

• ENG: "Payment failed. Check the reason in the banking application and try again."

• PL: "Płatność nieudana. Sprawdź powód w aplikacji bankowej i spróbuj ponownie"

Rejection by the user
(USER_DECLINED)

1. Proceed with the transaction by declining it in the banking app.

The user should receive an error message. Recommended content:

• ENG: "Payment rejected in a banking application. Try again."

• PL: "Płatność odrzucona w aplikacji bankowej. Spróbuj ponownie"

User timeout
(USER_TIMEOUT)

1. Proceed with the transaction without confirming it in time on the banking app.

The user should receive an error message. Recommended content:

• ENG: „Payment failed - not confirmed on time in the banking application. Try again.”

• PL: "Płatność nieudana - nie została potwierdzona na czas w aplikacji bankowej. Spróbuj ponownie."

System timeout
(TIMEOUT)

1. Proceed with the transaction, simulating a system timeout.

The user should receive an error message. Recommended content:

• ENG: „Payment failed - not confirmed on time in the banking application. Try again.”

• PL: "Płatność nieudana - nie została potwierdzona na czas w aplikacji bankowej. Spróbuj ponownie."

Mobile app timeout
(AM_TIMEOUT)

1. Proceed with the transaction without confirming it in time on the banking app.

The user should receive an error message. Recommended content:

• ENG: „Payment failed - not confirmed on time in the banking application. Try again.”

• PL: "Płatność nieudana - nie została potwierdzona na czas w aplikacji bankowej. Spróbuj ponownie