Orca

BLIK Rail Facts

How money moves on this rail, in 12 sourced records: what is final, what can be returned, recalled or refunded, who decides, and what the limits are. A profile belongs to the rulebook, so no reason code list is published on this page.

What the tier labels mean, and how far this page has been checked
Draft
An agent wrote it from published material and nobody has checked it. Use it as a lead to confirm, never on its own as the basis for a retry, a return, a deadline or a compliance decision.
Corroborated
A validator found the same answer in one or more named public sources; the class in brackets says how strong they are. "Secondary sources only" means bank, processor or industry guides and nothing from the operator or regulator. Corroborated does not mean checked against the governing rulebook, so confirm before you act.
Verified
A person checked it against Polski Standard Płatności S.A. (PSP)'s own current text and recorded the edition and date. The strongest tier here, and still reference material, not legal or compliance advice.

On a rail fact, every detail line names the section or instrument it rests on and whether that is a rule, a law, operator guidance, or observed practice.

Products on this rail

A product is built on this rail and has an object of its own: an authorisation, a lifecycle or a code set. Each view below is derived by the build from records already in the corpus; see products.json for the rule.

Recurring transactionA single transaction a merchant starts under a recurring payment the user set up earlier. It is a separate event from the consent itself, may be authorised automatically or only after the user confirms it in the app depending on the model, and is authorised by the issuer like any other BLIK transaction.33 rules, 1 authorisation, 3 states, 0 code sets; 2 draft, 36 corroborated

6 other transaction types hold rules on this rail but no authorisation, lifecycle or code set of their own, so each is a transaction type and not a product: Contactless BLIK (BLIK-C) (29 rules), Cash withdrawal or deposit (30 rules), Code payment to a merchant (32 rules), Phone transfer (P2P) (12 rules), Transfer request (P2P-R) (12 rules), Refund to the user (29 rules).

Known gaps in this build

Not yet covered: BLIK error and response codes: they sit in the Technical Specification for Participants (Annex 3 to the rulebook), which PSP does not publish; the one code on a public PSP page, ER_PAYID_UNHANDLED, is described in the messages fact rather than as a code record; the rulebook annexes (price lists, fees, the Technical Specification and the operating procedures for the settlement guarantee, the settlement timetable, complaints, the acquirer reverse position and fraud risk), which hold the per-transaction limit, code validity, complaint deadlines and the multi-session timetable; NBP's own pages on BLIK oversight and SORBNET3, which answered with a bot challenge; the Payment Services Act and the Settlement Finality Act, which the rulebook names; consumer rights are stated only as far as the rulebook and PSP's pages go; Express Elixir, which carries most phone transfers, is not held as a rail; its rulebook is cited for the P2P leg only; BLIK Płacę Później (deferred payment) and BLIK in Romania and Slovakia are outside this rail.