> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/commerce-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/commerce-api/payments/supported-payment-methods/blik.md).

# BLIK

BLIK transactions accounted for 75% of e-commerce volume and a 60% market share of all e-commerce in Poland for 2021. BLIK boasts over 10.1 million active users and is continuing to grow.

BLIK lets shoppers pay for online purchases directly from their preferred bank account. After choosing BLIK at checkout, shoppers are directed to BLIK's system to provide their BLIK code that authenticates and confirms payment directly from their banking app.

Contact your Customer Success Manager and sign a BLIK addendum if you want to use BLIK..

## How to configure

How you configure BLIK depends on whether you're using [DigitalRiver.js with Elements](/commerce-api/payments/payments-solutions/digitalriver.js.md) or[ Drop-in payments](/commerce-api/payments/payments-solutions/drop-in.md). 

| DigitalRiver.js with Elements                                                                                     | Drop-in payments                                                                                                     |
| ----------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| [Configuring BLIK](/commerce-api/payments/payments-solutions/digitalriver.js/payment-methods/configuring-blik.md) | [Drop-in Payments Integration Guide](/commerce-api/payments/payments-solutions/drop-in/drop-in-integration-guide.md) |

## How it works

BLIK uses a [redirect then submit (RTS) payment flow](/commerce-api/payments/building-your-workflows/flows-by-payment-type.md#redirect-then-submit-rts-payment-flow).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digitalriver.com/commerce-api/payments/supported-payment-methods/blik.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.