> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# BLIK

> Accept BLIK payments in Poland, where customers enter a six-digit code from their banking app at checkout and approve the payment in the app.

<picture noZoom>
  ![BLIK logo](https://assets.payrails.io/img/logos/blik/logo-full-bleed.svg)
</picture>

BLIK is a widely used online payment method in Poland. The customer gets a six-digit code from their banking app, enters it at checkout and approves the payment in the banking app. A BLIK code is valid for a short time, so the customer needs to approve the payment soon after they enter it.

Payrails processes BLIK through two payment service providers (PSPs). The flow is the same with each one, but the request checks differ. Pick a PSP below for its setup steps and request examples.

## How a BLIK payment works

BLIK is a code payment method with no redirect:

1. The customer selects BLIK at checkout and enters the six-digit code from their banking app.
2. You send the code to Payrails in `meta.shopperInput.blikCode` with the authorize request.
3. The bank asks the customer to approve the payment in their banking app.
4. Payrails receives the final result from the PSP and updates the payment.

Each payment is single-use: the customer approves every payment with a new code. Payrails captures BLIK payments immediately, so a successful payment is final. To return funds, [refund the payment](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md).

## Supported currencies and countries

BLIK supports PLN (Polish złoty) as its only presentment currency.

BLIK is available to customers based in:

<table>
  <thead>
    <tr><th>Regions</th><th>Countries</th></tr>
  </thead>

  <tbody>
    <tr><td>**Europe**</td><td>🇵🇱 Poland</td></tr>
  </tbody>
</table>

## Integrate BLIK

Choose the PSP that processes BLIK for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

> [card]
>
> Checkout.com logo
>
> Checkout.comBLIK via Checkout.com
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/blik/checkout-com.md)

> [card]
>
> Stripe logo
>
> StripeBLIK via Stripe
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/blik/stripe.md)

## Check PSPs

<table>
  <thead>
    <tr><th>Workflow</th><th>[Checkout.com](https://docs.payrails.com/docs/integrations/payment-methods/blik/checkout-com.md)</th><th>[Stripe](https://docs.payrails.com/docs/integrations/payment-methods/blik/stripe.md)</th></tr>
  </thead>

  <tbody>
    <tr><td>Payrails SDK</td><td>✔</td><td>✔</td></tr>
    <tr><td>Payrails API</td><td>✔</td><td>✔</td></tr>
    <tr><td>[Delayed / Manual Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✖</td><td>✖</td></tr>
    <tr><td>[Instant Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✔</td><td>✔</td></tr>
    <tr><td>[Cancel / Void](https://docs.payrails.com/docs/orchestration/payment-acceptance/cancel-a-payment.md)</td><td>✖</td><td>✖</td></tr>
    <tr><td>[Refund / Reverse](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md)</td><td>✔</td><td>✔</td></tr>
    <tr><td>[Save Instruments](https://docs.payrails.com/docs/resources/manage-instruments.md)</td><td>✖</td><td>✖</td></tr>
    <tr><td>[Merchant Initiated Transaction (MIT)](https://docs.payrails.com/docs/resources/payments/authorization-flags.md)</td><td>✖</td><td>✖</td></tr>
  </tbody>
</table>

## Ways to integrate BLIK

* **Payrails SDK:** the [Web SDK](https://docs.payrails.com/docs/sdks/web.md) shows BLIK when your workflow returns it as a payment option.
* **Payrails API:** call [lookup payment options](https://docs.payrails.com/docs/orchestration/payment-acceptance/lookup-payment-options.md), then authorize with `blik` as the `paymentMethodCode` and the customer's code in `meta.shopperInput.blikCode`.

In both cases, confirm the final result through [webhook notifications](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) or the execution status before you fulfill the order.


## Related topics

- [BLIK via Stripe](https://docs.payrails.com/docs/integrations/payment-methods/blik/stripe.md)
- [BLIK via Checkout.com](https://docs.payrails.com/docs/integrations/payment-methods/blik/checkout-com.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.