Skip to main content
Accept 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

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 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 in your workflow.

Request fields for Checkout.com

Send these fields in the authorize request, in addition to the standard authorize fields. Payrails checks Required fields and returns an error when one is missing. Fields required by the PSP pass the Payrails checks but the PSP can decline the payment without them.

Authorize a BLIK payment

Call authorize a payment with blik as the paymentMethodCode.
Authorize request
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 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.
  • Payrails doesn’t save the BLIK payment method at Checkout.com, so Save Instruments and MIT aren’t available.
Last modified on October 2, 2026