BLIK
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
Markets | PL |
Processing currencies | PLN |
Consumer currencies | PLN |
Settlement currencies | PLN |
Authentication methods | REDIRECT MULTI_FACTOR |
Authentication timeout | |
Minimum payment amount | 0.01 PLN |
Maximum payment amount | 50,000.00 PLN (can vary by bank) |
Payment instrument | PASSTHROUGH_WALLET |
Recurring payments | No |
Separate captures | No |
Refund | Full - Partial - Multiple |
Refund validity | 13 months |
Disputes | Yes |
Sandbox availability | BLIK sandbox |
Make a BLIK payment
BLIK payments follow our standardized REDIRECT
and MULTI_FACTOR
payment flows. Enabling your consumers to provide the 6-digit BLIK code on your website or in-store for a more seamless experience.
To create a BLIK payment, you'll need to provide the following data at minimum when calling our payment charges API:
Field | Description |
---|---|
paymentMethod | BLIK |
amount.value | The amount to be paid in the smallest units of the currency used. |
amount.currency | PLN |
consumer.name | Full name of the consumer. |
consumer.country | The country where the consumer is shopping. |
consumer.client.ip | The IP of the consumers browser or HTTP client. Required for the MULTI_FACTOR flow. |
consumer.client.userAgent | The user agent of the consumer or HTTP client. Required for the MULTI_FACTOR flow. |
authenticationSettings: REDIRECT settings.returnUrl | Add the URL where the consumer should be redirected after they complete the payment. Required for the REDIRECT flow. |
Request
POST /v1/payment-charges
{
"paymentMethod": "BLIK",
"amount": {
"value": 1000,
"currency": "PLN"
},
"consumer": {
"name": "John Smith",
"country": "PL",
"client": {
"ip": "11.22.22.33",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36"
}
},
"authenticationSettings": [
{
"type": "REDIRECT",
"settings": {
"returnUrl": "https://www.webshop.com/order-results-page"
}
}
]
}
Response
You'll receive our standard payment charge response with the available authentication methods:
{
"id": "charge_bwAETN9BnQemLChVjSzLt",
"paymentMethod": "BLIK",
"paymentMedium": "ECOMMERCE",
"scheduleType": "UNSCHEDULED",
"instrumentId": "instr_K7WokqNcs416KSlLPFo2i",
"currency": "PLN",
"country": "PL",
"status": "AUTHENTICATION_PENDING",
"consumer": {
"name": "John Smith",
"country": "PL",
"client": {
"ip": "11.22.22.33",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36"
}
},
"authenticationMethods": [
{
"details": {
"requestUrl": "https://redirection-target.ppro.com",
"requestMethod": "POST"
},
"type": "REDIRECT"
},
{
"type": "MULTI_FACTOR"
}
],
"authorizations": [
{
"id": "authz_XJjk7r3djaBAJkpKobQYa",
"amount": 1000,
"status": "AUTHENTICATION_PENDING",
"createdAt": "2025-06-21T13:04:45.837Z",
"updatedAt": "2025-06-21T13:04:45.837Z"
}
],
"captures": [],
"refunds": [],
"voids": [],
"createdAt": "2025-06-21T13:04:45.662Z",
"updatedAt": "2025-06-21T13:04:45.837Z",
"_links": {
"authorizations": {
"href": "/v1/payment-charges/charge_bwAETN9BnQemLChVjSzLt/authorizations"
},
"captures": {
"href": "/v1/payment-charges/charge_bwAETN9BnQemLChVjSzLt/captures"
},
"refunds": {
"href": "/v1/payment-charges/charge_bwAETN9BnQemLChVjSzLt/refunds"
},
"voids": {
"href": "/v1/payment-charges/charge_bwAETN9BnQemLChVjSzLt/voids"
}
}
}
Pick the desired authentication method
REDIRECT
- Redirect your consumer to the returned
$.authenticationMethods[?(@.type == "REDIRECT")].details.requestUrl
.
For example, with the value ofhttps://redirection-target.ppro.com/
using the returned$.authenticationMethods[?(@.type == "REDIRECT")].details.requestMethod
HTTP method. - The consumer will be presented with the reference number and instructions to complete the payment.
MULTI_FACTOR
- Ask your consumer for the OTP required to authenticate the payment.
- Issue the following request to
POST /v1/payment-charges/{paymentChargeId}/authorizations
{
"authenticationResult": {
"type": "MULTI_FACTOR",
"details": {
"verificationCode": "124567"
}
}
}
Handling the payment result
REDIRECT
- After the consumer completes the payment, they are redirected to the
returnUrl
specified in the payment charge creation request. - Upon redirect back to your site, retrieve the latest payment status by performing a GET /v1/payment-charges/{paymentChargeId}. Use the returned
status
field to determine and display the final payment outcome to the consumer. - Additionally, webhooks are triggered to notify you of the payment result. This ensures you receive the outcome even if the consumer closes their browser or fails to return to your website.
MULTI_FACTOR
- Check the response from the
POST /v1/payment-charges/{paymentChargeId}/authorizations
and use theStatus
that you received to display the payment outcome to the consumer. - 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_K7WokqNcs416KSlLPFo2i",
"type": "PASSTHROUGH_WALLET"
}
Updated 13 days ago