BLIK payin

The payer gives a BLIK code from their banking app, then confirms the payment in the app. PLN only.

Use the key of a payin shop; a payout shop key gets 403 method_not_enabled. Rules shared by every method — Authentication, Idempotency, Errors, Webhooks — apply here and are not repeated.

Flow

sequenceDiagram
    participant M as Your server
    participant P as Payer
    participant A as Payments API
    P->>M: BLIK code from the banking app
    M->>M: Save merchant_reference
    M->>A: POST /v2/payins/blik
    A-->>M: 201 payin, requires_action, next_action
    alt next_action.type await_confirmation
        M->>P: Confirm the payment in your banking app
    else next_action.type redirect
        M->>P: Open next_action.redirect.url
    end
    P->>P: Confirms or rejects in the app
    A->>M: Webhook payin.completed or payin.failed, signed
    opt No webhook for a minute
        M->>A: GET /v2/transactions/{transaction_id}
        A-->>M: 200 payin. Poll until final
    end

1. Ask the payer for the BLIK code. Generate merchant_reference and save it with your order.
2. Create the payin: POST /v2/payins/blik. Save id from the response.
3. Read next_action: tell the payer to confirm the payment in the banking app (await_confirmation), or send them to next_action.redirect.url (redirect). Which one comes is set for the shop.
4. Wait for the webhook payin.completed or payin.failed. Verify the signature and act on data.object — the full payin.
5. Fallback: if no webhook has come for a minute, you can start polling the status with GET /v2/transactions/{transaction_id} until it is final. Polling instead of webhooks loads the API and gets 429 rate_limited (R20).

Endpoints

Refunds of BLIK payins return 501 not_supported_yet — see Refunds. The create has its own section below. Reading returns the Payin object.

POST /v2/payins/blik

Creates a payin and waits up to 10 seconds for the payer step, so the response usually carries next_action.

Request

Headers: Authorization: Bearer <payin shop key>, Content-Type: application/json.

curl -X POST https://payments-api.mrcr.io/v2/payins/blik \
  -H "Authorization: Bearer $PAYIN_SHOP_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "merchant_reference": "order-40001",
    "amount": { "value": "120.00", "currency": "PLN" },
    "payer": { "first_name": "Jan", "last_name": "Kowalski", "email": "jan@example.com", "ip_address": "203.0.113.20" },
    "blik": { "code": "777123" }
  }'

Response 201 Created

The Payin object in data. Usually requires_action with next_action; if the payer step is not ready in 10 seconds — processing, and the step comes by the payin.requires_action webhook. A repeat of an earlier call returns the payin in its current status.

{
  "data": {
    "id": "5a1e9d7f-2b6c-4d3a-8f8e-0c7b3d6a9fc5",
    "object": "payin",
    "merchant_reference": "order-40001",
    "method_type": "payin_blik",
    "status": "requires_action",
    "status_details": null,
    "amount": { "value": "120.00", "currency": "PLN" },
    "refunded_amount": { "value": "0.00", "currency": "PLN" },
    "next_action": { "type": "await_confirmation" },
    "created_at": "2026-09-29T09:30:00Z",
    "updated_at": "2026-09-29T09:30:02Z"
  }
}

Errors

No payin is created on any of them.

After a timeout or a dropped connection the payin may or may not exist. Resend the identical request (R4), never with a new reference.

Payer step: confirm the payment

The payin waits in requires_action until the payer confirms or rejects the payment in the banking app. next_action.type is set for the shop:

How to show it in a browser or an app — Payer actions.

The Payin object

Returned by the create and by GET /v2/transactions/{transaction_id}, and sent in webhooks as data.object. It has the common fields of every transaction, with these values and fields for a BLIK payin:

Statuses

stateDiagram-v2
    [*] --> created: POST /v2/payins/blik
    created --> processing
    processing --> requires_action
    requires_action --> completed: The payer confirms
    created --> failed
    processing --> failed
    requires_action --> failed: Declined or rejected
    completed --> [*]
    failed --> [*]

• Only completed and failed are outcomes. A final status never changes.
• requires_action usually comes in the create response; the payin.requires_action webhook comes as well.
• An unknown status is not final — keep waiting (R13).

Decline reasons

status_details.code on a failed BLIK payin. Every decline is final: a new attempt is a new payin with a new merchant_reference and a new BLIK code.

An unknown code: handle it like provider_declined.

Webhooks

Headers, signature check and redelivery — Webhooks.

In the sandbox

blik.code: any six digits. The cents of amount.value select the outcome:

Sandbox keys and fixtures — Sandbox.

Next: Hosted payment form