BLIK is a popular payment method in Poland, embedded in various mobile banking apps. Consumers use their banking app to obtain a secure 6-digit code and authenticate the payment. Learn more about BLIK.

Payment method properties

Make a BLIK payment

We offer BLIK payments through the REDIRECT payment flow, as well as an option for the consumer to provide the 6-digit BLIK code on your website or in-store using the MULTI_FACTOR flow for a more seamless experience.

To create a BLIK payment, you'll need to provide the following data at minimum when calling our /v1/payment-charges API:

Request

POST /v1/payment-charges

{
  "paymentMethod": "BLIK",
  "amount": {
    "value": 1000,
    "currency": "PLN"
  },
  "consumer": {
    "name": "John Smith",
    "country": "PL"
  },
  "authenticationSettings": [
    {
      "type": "REDIRECT",
      "settings": {
        "returnUrl": "https://www.webshop.com/order-results-page"
      }
    },
    {
      "type": "MULTI_FACTOR",
      "settings": {}
    }
  ]
}

Response

You'll receive our standard payment charge response (see potential responses in the API Reference) with the available authentication methods.

{
  "id": "charge_X0O78tadFHrZCbGhkycPk",
  "status": "AUTHENTICATION_PENDING",
  
  // ...
  
  "authenticationMethods": [
    {
      "type": "REDIRECT",
      "details": {
        "requestUrl": "https://redirection-target.ppro.com",
        "requestMethod": "POST"
      }
    },
     {
      "type": "MULTI_FACTOR"
    }, 
  ]
}

Pick the desired authentication method

REDIRECT

1. Redirect your consumer to the returned $.authenticationMethods[?(@.type == "REDIRECT")].details.requestUrl.
   For example, with the value of https://redirection-target.ppro.com/ using the returned $.authenticationMethods[?(@.type == "REDIRECT")].details.requestMethod HTTP method.
2. The consumer will finalize the payment process on the redirected page.

MULTI_FACTOR

1. Ask your consumer for the OTP required to authenticate the payment.
2. Issue the following request to POST /v1/payment-charges/{paymentChargeId}/authorizations

{
  "authenticationResult": {
    "type": "MULTI_FACTOR",
    "details": {
      "verificationCode": "124567"
    }
  }
}

Handling the payment result

REDIRECT

1. Once the consumer has confirmed the payment, they are redirected to the returnUrl provided in the initial payment charge creation request.
2. After the consumer is redirected back to your site, check the payment status by making a GET /v1/payment-charges/{paymentChargeId}. Use the Status that you received to display the payment outcome to the consumer.
3. Webhooks are also sent to inform you of the payment outcome. If the shopper closes the browser and doesn't return to your website, you can rely on webhooks to receive the payment result.

MULTI_FACTOR

1. Check the response from the POST /v1/payment-charges/{paymentChargeId}/authorizations and use the Status that you received to display the payment outcome to the consumer.
2. Webhooks are also sent to inform you of the payment outcome.

Payment instrument

A PASSTHROUGH_WALLET instrument will be created for BLIK, with no additional data provided.

Request

GET /v1/payment-instruments/{instrument-id}

Response

{
    "id": "instr_5ChenWBwW8xARvJ3GccAx",
    "type": "PASSTHROUGH_WALLET"
}