> ## 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 via Checkout.com

> Set up BLIK payments through Checkout.com in Payrails, and see how Payrails sends the code and the merchant reference.

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

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

Accept [BLIK](https://docs.payrails.com/docs/integrations/payment-methods/blik) payments from customers in Poland with Checkout.com as the payment service provider (PSP). The customer enters their BLIK code at checkout and approves the payment in their banking app. The customer stays on your checkout, with no redirect.

## Supported workflows

<table>
  <thead>
    <tr><th>Workflow</th><th>Supported</th></tr>
  </thead>

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

## Before you begin

Complete these steps before you send your first BLIK payment through Checkout.com:

1. Set up a Checkout.com integration in your workspace. Follow the [Checkout.com integration setup guide](https://docs.payrails.com/docs/integrations/payment-providers/checkout-com.md) if you don't have one yet.
2. Ask Checkout.com support to enable BLIK on your Checkout.com account.
3. In the Payrails Portal, go to **Settings → Integrations**, open your Checkout.com integration, select **BLIK** under **Payment methods**, and save.
4. Add BLIK as a [payment option](https://docs.payrails.com/docs/integrations/payment-methods/set-up-payment-methods.md) in your workflow.

## Request fields for Checkout.com

Send these fields in the authorize request, in addition to the standard [authorize fields](https://docs.payrails.com/reference/authorizeaction.md). **Required** fields must be present for the payment to succeed. Payrails sends **Optional** fields to the PSP when you include them.

| Field | Status | Description |
| - | - | - |
| `meta.shopperInput.blikCode` | Required | The six-digit code from the customer's banking app. Payrails rejects a missing code and any value that isn't exactly six digits. |
| `amount.currency` | Required | BLIK payments are in `PLN`. |
| `meta.customer.name`, `meta.customer.lastName` | Optional | Sent to Checkout.com as the customer name. |
| `meta.customer.email` | Optional | Sent to Checkout.com as the customer email. |

## Authorize a BLIK payment

Call [authorize a payment](https://docs.payrails.com/reference/authorizeaction.md) with `blik` as the `paymentMethodCode`.

```json Authorize request theme={null}
{
  "amount": {
    "value": "50.00",
    "currency": "PLN"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "blik",
      "amount": {
        "value": "50.00",
        "currency": "PLN"
      }
    }
  ],
  "meta": {
    "shopperInput": {
      "blikCode": "123456"
    },
    "customer": {
      "email": "anna.kowalska@example.com",
      "name": "Anna",
      "lastName": "Kowalska"
    }
  }
}
```

The response is pending, with no redirect. The payment stays pending until the customer approves it in their banking app. Confirm the result through [webhook notifications](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) or the execution status before you fulfill the order.

## How Checkout.com handles BLIK

* Payrails processes BLIK through the Checkout.com Payment Setup API, and sends the code to Checkout.com as the partner code.
* Checkout.com sends the final result as a webhook notification after the customer approves or declines in the banking app.
* Checkout.com accepts references of up to 35 characters for BLIK. Payrails shortens the merchant reference to 35 characters on the payment and on refunds.
* Each BLIK payment is a new customer-initiated payment.


## Related topics

- [BLIK](https://docs.payrails.com/docs/integrations/payment-methods/blik.md)
- [Przelewy24 via Checkout.com](https://docs.payrails.com/docs/integrations/payment-methods/przelewy24/checkout-com.md)
- [Bancontact via Checkout.com](https://docs.payrails.com/docs/integrations/payment-methods/bancontact/checkout-com.md)


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