{ "corpus": "orca-product", "format_version": "1", "built": "2026-09-26", "snapshot": "2026-09-20", "commit": "019924ac64ee0aa0742b8f02a04488a83633385d", "license": { "name": "Creative Commons Attribution 4.0 International (CC BY 4.0)", "spdx": "CC-BY-4.0", "url": "https://creativecommons.org/licenses/by/4.0/", "attribution": "Data from Orca (https://qstve.com/orca/), CC BY 4.0. Snapshot 2026-09-20.", "notice": "Reference material about published payment rules. Not legal, compliance or financial advice. Orca cites rulebooks by section and edition and does not reproduce them; rights in the cited documents stay with their authors." }, "uid": "blik:txn.recurring", "rail": "blik", "page": "../../../blik/recurring.html", "product": { "uid": "blik:txn.recurring", "id": "txn.recurring", "slug": "recurring", "rail": "blik", "rail_name": "BLIK", "governing_authority": "Polski Standard Płatności S.A. (PSP)", "snapshot": "2026-09-19", "page": "blik/recurring.html", "file": "data/products/blik/recurring.json", "name": "Recurring transaction", "anchor": "an authorisation of its own, a lifecycle of its own (3 states)", "transaction_type": { "uid": "blik:txn.recurring", "name": "Recurring transaction", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "summary": "A 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.", "effective_since": "Unknown: the rulebook edition read does not say when each provision took effect", "effective_note": "Drafted 2026-09-19 from the BLIK rulebook editions approved on 15 April 2026. The rulebook prints no effective date and PSP publishes no rule change notices that were found, so when this provision first applied is [Unverified].", "source_edition": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved by the PSP Management Board on 15 April 2026, read 2026-09-19; the multi-session edition of the same date was compared by text and matches for the sections cited unless the record says otherwise", "directions": [ "debit" ], "account_types": [ "any" ], "sources": [ { "uid": "blik:src.blik-recurring-payments-introduction", "name": "BLIK Recurring Payments: Introduction", "url": "https://www.blik.com/lp/reccuring-payments/Introduction.141951041.html", "source_class": "authoritative_primary", "edition": "undated live page as read 2026-09-19", "section": "Recurring Payment and Recurring Transaction; implementation models" }, { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§2 (definition of Akceptant a, second indent)" } ] }, "counts": { "rules": 33, "mandates": 1, "states": 3, "code_sets": 0, "reason_codes": 0, "roles": 7, "members": 38 }, "trust": { "members": 38, "by_status": { "draft": 2, "corroborated": 36, "verified": 0, "superseded": 0 }, "strongest_source_class": "authoritative_primary" }, "roles": [ { "uid": "blik:role.acquirer", "name": "Acquirer (Agent Rozliczeniowy)", "kind": "institution", "via": [ "binds" ] }, { "uid": "blik:role.issuer", "name": "Issuer (Wydawca)", "kind": "institution", "via": [ "binds" ] }, { "uid": "blik:role.mastercard-cooperating-scheme", "name": "Mastercard, the Cooperating Scheme (Schemat Współpracujący)", "kind": "operator", "via": [ "binds" ] }, { "uid": "blik:role.merchant", "name": "Merchant or acceptant (Akceptant)", "kind": "party", "via": [ "given_to", "binds" ] }, { "uid": "blik:role.psp", "name": "Polski Standard Płatności S.A. (PSP), operator", "kind": "operator", "via": [ "binds" ] }, { "uid": "blik:role.settlement-entity", "name": "Settlement entity (Podmiot Rozrachunkowy)", "kind": "institution", "via": [ "binds" ] }, { "uid": "blik:role.user", "name": "User (Użytkownik)", "kind": "party", "via": [ "given_by" ] } ], "mandates": [ { "uid": "blik:mandate.recurring-payment", "name": "BLIK recurring payment (Płatność powtarzalna BLIK)", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "summary": "The user's standing consent, started at the merchant and confirmed in the banking app, for that merchant to start later BLIK transactions from the user's account: automatically for a fixed amount and frequency (model A), with confirmation each time (model M), or automatically with variable amounts (model O). The user sees and cancels it in the app; it stays with the bank where it was set up.", "form": "electronic: requested at the merchant's checkout, usually with a BLIK code, and confirmed by the user in the issuer's mobile banking app; identified by a PAYID alias of up to 64 characters", "scope": [ "recurring", "standing" ], "constraints": null, "governed_by": [ { "uid": "blik:rule.recurring-models", "name": "Recurring payment models A, M and O" }, { "uid": "blik:rule.recurring-retry-72-hours", "name": "Recurring transaction short of funds: 72 hours of bank retries" }, { "uid": "blik:rule.recurring-flags", "name": "Recurring payment flags and the one public BLIK error code" }, { "uid": "blik:rule.issuer-decides-authorisation", "name": "The issuer decides; an acquirer's no-confirmation hint is only advice" } ], "revoked_via": [ { "uid": "blik:rule.recurring-cancel-in-banking-app", "name": "Recurring payment: the user sees and cancels it in the bank app" } ], "evidenced_by": [ { "uid": "blik:rule.recurring-consent-in-banking-app", "name": "Recurring payment: consent started at the merchant, confirmed in the bank app" } ], "disputed_via": [ { "uid": "blik:exc.complaint", "name": "Complaint (reklamacja)", "shared": true } ], "given_by": [ { "uid": "blik:role.user", "name": "User (Użytkownik)", "note": null } ], "given_to": [ { "uid": "blik:role.merchant", "name": "Merchant or acceptant (Akceptant)", "note": null } ], "sources": [] } ], "states": [ { "uid": "blik:state.recurring-payment-active", "name": "BLIK recurring payment: active", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 3 named sources, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "summary": "The user has confirmed the merchant's invitation in their banking app, so the bank now keeps the recurring payment on its list and the merchant may start recurring transactions under it: charged automatically in models A and O, or put to the user for confirmation each time in model M. It lasts until its expiry date (required in model A, at most 10 years ahead) or, in models M and O, until cancelled if no date was set. It exists only at the bank where it was confirmed; moving bank means setting it up again.", "terminal": false, "money_moved": "no", "visible_as": null, "precedes": [ { "uid": "blik:state.recurring-payment-deleted-by-user", "name": "BLIK recurring payment: deleted by the user" }, { "uid": "blik:state.recurring-payment-expired", "name": "BLIK recurring payment: past its expiry date" } ], "sources": [ { "uid": "blik:src.blik-recurring-payments-introduction", "name": "BLIK Recurring Payments: Introduction", "url": "https://www.blik.com/lp/reccuring-payments/Introduction.141951041.html", "source_class": "authoritative_primary", "edition": "undated live page as read 2026-09-19", "section": "Recurring Payment; implementation models table (expiration row)" }, { "uid": "blik:src.blik-recurring-payments-model-a", "name": "BLIK Recurring Payments: Model A", "url": "https://www.blik.com/lp/reccuring-payments/Model-A.141951045.html", "source_class": "authoritative_primary", "edition": "undated live page as read 2026-09-19", "section": "how it works; invitation data (alias expiration date)" }, { "uid": "blik:src.blik-faq", "name": "BLIK FAQ (blik.com/faq)", "url": "https://www.blik.com/faq", "source_class": "public_primary", "edition": "live page as read 2026-09-19", "section": "recurring payment questions (starting, details of stored recurring payments, changing bank)" } ] }, { "uid": "blik:state.recurring-payment-deleted-by-user", "name": "BLIK recurring payment: deleted by the user", "status": "draft", "stored_status": "draft", "source_class": null, "confidence": "medium", "tier": { "k": "draft", "label": "Draft, unchecked", "say": "An agent wrote this from published material and nobody has checked it. Treat it as a lead to confirm, not an answer, before acting on any retry, deadline or rate." }, "summary": "The user has removed the recurring payment from the list in their banking app, which is how BLIK lets a user give it up. The merchant can no longer charge through it. Removing it ends the BLIK consent only: whether the user's contract with the merchant ends too is for the merchant's own terms.", "terminal": true, "money_moved": "no", "visible_as": null, "precedes": [], "sources": [ { "uid": "blik:src.blik-recurring-payments-introduction", "name": "BLIK Recurring Payments: Introduction", "url": "https://www.blik.com/lp/reccuring-payments/Introduction.141951041.html", "source_class": "authoritative_primary", "edition": "undated live page as read 2026-09-19", "section": "Recurring Payment" }, { "uid": "blik:src.blik-faq", "name": "BLIK FAQ (blik.com/faq)", "url": "https://www.blik.com/faq", "source_class": "public_primary", "edition": "live page as read 2026-09-19", "section": "recurring payment questions (giving up a recurring payment)" } ] }, { "uid": "blik:state.recurring-payment-expired", "name": "BLIK recurring payment: past its expiry date", "status": "draft", "stored_status": "draft", "source_class": null, "confidence": "low", "tier": { "k": "draft", "label": "Draft, unchecked", "say": "An agent wrote this from published material and nobody has checked it. Treat it as a lead to confirm, not an answer, before acting on any retry, deadline or rate." }, "summary": "The recurring payment has reached the expiry date set when it was created. In model A that date is compulsory and at most 10 years out, and automatic charges run only until it; in models M and O a date is optional, so a recurring payment without one never reaches this state. After it, the merchant needs a new recurring payment confirmed by the user.", "terminal": true, "money_moved": "no", "visible_as": null, "precedes": [], "sources": [ { "uid": "blik:src.blik-recurring-payments-introduction", "name": "BLIK Recurring Payments: Introduction", "url": "https://www.blik.com/lp/reccuring-payments/Introduction.141951041.html", "source_class": "authoritative_primary", "edition": "undated live page as read 2026-09-19", "section": "implementation models table (expiration row)" }, { "uid": "blik:src.blik-recurring-payments-model-a", "name": "BLIK Recurring Payments: Model A", "url": "https://www.blik.com/lp/reccuring-payments/Model-A.141951045.html", "source_class": "authoritative_primary", "edition": "undated live page as read 2026-09-19", "section": "how it works; invitation data (alias expiration date)" } ] } ], "code_sets": [], "reason_codes": [], "rules": [ { "uid": "blik:rule.order-entry-and-irrevocable-authorisation", "name": "When a BLIK order is in and when it can no longer be withdrawn", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "high", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "A BLIK transaction order counts as entered into PSP's system as soon as the BLIK code and the transaction data reach PSP. Once the issuer authorises it, the authorisation is irrevocable: neither a participant nor anyone else can withdraw the order. By authorising a transaction that goes to clearing, the issuer takes on the duty to pay the acquirer, or Mastercard for BLIK-C, through the BLIK system; for a transfer to the user's account the duty runs the other way, from the acquirer to the issuer. Issuer and acquirer must both keep a durable record of every authorisation decision.", "facet": "finality", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§12.1 to §12.3" } ] }, { "uid": "blik:rule.settlement-order-irrevocable", "name": "The settlement order is entered and fixed at positive authorisation", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "high", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "The moment PSP's system registers the issuer's positive authorisation is the moment the settlement order enters the BLIK system; for an indirect participant, the order counts as entered by the direct participant that settles for it. From then on the settlement order cannot be revoked. The payment orders PSP later places in SORBNET3 on participants' behalf have the effect of settlement orders under the Settlement Finality Act (article 1 point 12), which is what protects them in an insolvency.", "facet": "finality", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§29.2 to §29.4; §31.3" } ] }, { "uid": "blik:rule.net-clearing", "name": "Net clearing of BLIK transactions, fees included", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "high", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 2 named sources, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "PSP clears BLIK mobile transactions in net amounts: for each issuer one net obligation to the BLIK system, for each acquirer and for Mastercard one net claim, all after the fees due to issuers, acquirers and Mastercard, which PSP sets in Annex 2. Orders are handled first in, first out, so transactions are cleared in the order they entered. In the single-session edition PSP clears on every business day and settlement data sets and files are produced on business days; the multi-session edition leaves the business day wording out of those sentences and puts the timing in its session timetable.", "facet": "settlement", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§3.4; §11.1; §16.2; §29.5; §29.8; §29.9; §31.7" }, { "uid": "blik:src.psp-blik-rulebook-multi-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, multi-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin-1", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, multi-session model; PDF of 56 pages, 1,467,481 bytes, SHA-256 c0cf1775f7db393f0df1a713cf9bff8df393426ed5cef8a4f6f5e7c214a990ae", "section": "§16.2; §29.5; §29.9" } ] }, { "uid": "blik:rule.sessions-multi-session-edition", "name": "Clearing and settlement sessions, multi-session model", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "For participants in the multi-session model, several clearing sessions are grouped into settlement sessions that settle together in SORBNET3, and the timetable of both sits in the non-public operating procedure for clearing and settlement. Transactions authorised on a Polish public holiday go into the settlement session processed on the next business day. The duties to publish, check and correct settlement files are as in the single-session model.", "facet": "settlement", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-multi-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, multi-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin-1", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, multi-session model; PDF of 56 pages, 1,467,481 bytes, SHA-256 c0cf1775f7db393f0df1a713cf9bff8df393426ed5cef8a4f6f5e7c214a990ae", "section": "§2 (definition of Sesja Rozrachunkowa PSP); §29.6; §29.7; §29.9 to §29.12" } ] }, { "uid": "blik:rule.sessions-single-session-edition", "name": "Clearing sessions, single-session model", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "high", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "For participants in the single-session model, each PSP clearing session ends at midnight (24:00). Transactions authorised on a Polish public holiday go into the session cleared on the next business day. PSP publishes each participant's settlement and reconciliation files promptly after the session closes; the participant must check them and report discrepancies at once, and PSP regenerates the files if needed. BLIK-C refunds are the exception: they join a session only when Mastercard reports them.", "facet": "settlement", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§29.5 to §29.7; §29.9 to §29.13" } ] }, { "uid": "blik:rule.settlement-entity", "name": "Every participant settles through a settlement entity", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "A participant either is itself a settlement entity, with its SORBNET3 account linked to BLIK as an external system, or names another settlement entity to receive what clearing owes it. A settlement entity that settles for another participant must credit that participant's account after the run with the amount of its position. An indirect participant uses the account of a direct issuer that has agreed to pass on its settlement orders.", "facet": "settlement", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§4.1 f to h; §4.3; §31.2" } ] }, { "uid": "blik:rule.settlement-guarantee", "name": "Settlement guarantee among issuers", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "high", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "If an issuer lacks funds on its NBP account in the main settlement run, or in a first reserve run held after technical errors, every BLIK order in that run is withdrawn and the run does not settle. PSP blocks the short issuer (and with it the secured acquirers and indirect participants that settle through it) and tells NBP. The other issuers stand behind the shortfall: PSP recomputes settlement with their obligations raised by a formula in a non-public procedure and settles in a reserve run. If that also fails, nothing settles through SORBNET3; issuers instead pay acquirers, Mastercard and each other bilaterally on PSP's instructions, and NBP is told. The issuer that caused it must promptly repay the others with statutory interest.", "facet": "settlement", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§3.10; §7.2 e, f; §31.11 to §31.16" } ] }, { "uid": "blik:rule.sorbnet3-settlement-run", "name": "Settlement in SORBNET3 through PSP's auxiliary account", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "high", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "BLIK settles in central bank money in NBP's SORBNET3 system, with BLIK attached as an external system under SORBNET3's settlement procedure A. From PSP's clearing data PSP enters one net debit order per issuer (covering the indirect participants it settles for, and for a securing issuer its secured acquirers), then, in the same session, credits each acquirer and Mastercard with single orders from PSP's auxiliary account at NBP. Settlement is one run, completes within one business day except when the guarantee forces bilateral settlement, happens Monday to Friday except Polish public holidays, and leaves the auxiliary account at zero before and after. Issuers must manage liquidity on their NBP accounts so the run can settle.", "facet": "settlement", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§2 (definition of Rachunek Pomocniczy PSP, Rozrachunek); §7.2 a, g; §31.1; §31.4 to §31.10" } ] }, { "uid": "blik:rule.continuous-operation", "name": "The scheme runs around the clock", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "high", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "The BLIK scheme works every day of the year, around the clock, apart from planned technical breaks, and users may start transactions whenever it is running. For registering a transaction the date and time of PSP's system count. Settlement is different: it runs only on Polish business days.", "facet": "hours", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" }, { "uid": "blik:txn.p2p", "name": "Phone transfer (P2P)" }, { "uid": "blik:txn.p2p-request", "name": "Transfer request (P2P-R)" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§3.1; §3.3; §15; §31.5" } ] }, { "uid": "blik:rule.one-time-code-validity", "name": "How long a one-time BLIK code lives", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 4 named sources, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "The rulebook leaves a one-time code's validity to the non-public Technical Specification. PSP's own FAQ tells users a code is valid for 2 minutes; Stripe also says 2 minutes and Adyen 120 seconds. A code serves one transaction only, and PSP generates and manages codes centrally.", "facet": "hours", "rests_on": "guidance", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§2 (definition of Kod Jednorazowy); §6 i" }, { "uid": "blik:src.blik-faq", "name": "BLIK FAQ (blik.com/faq)", "url": "https://www.blik.com/faq", "source_class": "public_primary", "edition": "live page as read 2026-09-19", "section": "is BLIK safe" }, { "uid": "blik:src.stripe-blik", "name": "Stripe Docs: BLIK payments", "url": "https://docs.stripe.com/payments/blik", "source_class": "secondary", "edition": "live page as read 2026-09-19", "section": "overview" }, { "uid": "blik:src.adyen-blik", "name": "Adyen Docs: BLIK", "url": "https://docs.adyen.com/payment-methods/blik", "source_class": "secondary", "edition": "live page as read 2026-09-19", "section": "shopper flow, BLIK with code" } ] }, { "uid": "blik:rule.issuer-set-limits", "name": "Each bank sets its users' BLIK limits", "status": "corroborated", "stored_status": "corroborated", "source_class": "public_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (public primary)", "say": "A validator compared this with 1 named source, the strongest being an operator or regulator publication. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "Amount and count limits for BLIK are set by each bank for its own users, including limits for contactless BLIK; whether recurring transactions count toward them also depends on the bank.", "facet": "limits", "rests_on": "guidance", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" }, { "uid": "blik:txn.p2p", "name": "Phone transfer (P2P)" }, { "uid": "blik:txn.p2p-request", "name": "Transfer request (P2P-R)" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.blik-faq", "name": "BLIK FAQ (blik.com/faq)", "url": "https://www.blik.com/faq", "source_class": "public_primary", "edition": "live page as read 2026-09-19", "section": "whether BLIK works the same in every bank; contactless limits; recurring payment limits" } ] }, { "uid": "blik:rule.per-transaction-limit-unpublished", "name": "Scheme per-transaction limit: set, but not public", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "To contain operational risk, a participant may send for authorisation only transactions up to the single-transaction limit the Technical Specification sets, and PSP's system rejects a larger one with an error code. The figure and the code are in the non-public specification.", "facet": "limits", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [], "part_of": [ "blik:exc.decline" ], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§13; §14.1" } ] }, { "uid": "blik:rule.complaint-ticket-process", "name": "Complaints run from participant to PSP through a ticket system", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "Complaints and other reports about BLIK go from a participant to PSP through PSP's ticket system, or by e-mail or another agreed channel when the ticket system is down. PSP investigates. It charges a complaint fee from Annex 1 to the participant whose failure caused the event, or to the filer when nobody was at fault, and waives it in cases the complaints procedure lists. For a BLIK-C complaint handled with Mastercard, PSP also collects Mastercard's fee from the issuer or passes on a fee Mastercard pays. The detailed steps, required documents and deadlines are in a non-public operating procedure. PSP keeps complaints for 6 years from the end of the year they close.", "facet": "return", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [], "part_of": [ "blik:exc.complaint" ], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§6 f, n; §9.1 to §9.4; §9.8; §24.3" } ] }, { "uid": "blik:rule.declined-authorisation-never-settles", "name": "A declined transaction never settles", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "A settlement order exists only once PSP registers a positive authorisation from the issuer, so a transaction the issuer declines, or PSP rejects before authorisation, never enters clearing and moves no money. BLIK has no return message for a settled payment; money goes back through a separate refund, a cancellation or correction, or a complaint.", "facet": "return", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [], "part_of": [ "blik:exc.decline" ], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§11.3 f; §14; §29.2" } ] }, { "uid": "blik:rule.cancellation-or-correction-13-months", "name": "Cancellation or correction within 13 months", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "high", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "After the issuer has authorised a mobile transaction, PSP or the acquirer may cancel it when a technical error occurred. A mobile transaction can be cancelled or corrected for 13 months from the day it was authorised. Corrections of amounts under complaint are made by PSP under the non-public complaints procedure. There is no recall by the user.", "facet": "recall", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [], "part_of": [ "blik:exc.cancellation-correction" ], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§10; §12.4; §12.5" } ] }, { "uid": "blik:rule.bad-faith-and-crime-liability", "name": "Who answers for bad-faith, criminal or intruder transactions", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "high", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "The acquirer answers to other participants and PSP for BLIK transactions that it or its merchant put into PSP's system in bad faith or through a crime, including unauthorised acts of third parties in the acquirer's or merchant's systems. The issuer answers in the same way for such transactions put in by itself or its users, including intrusions into its systems or its mobile app. Every participant must work to reduce users' and other participants' exposure to crime, and answers for subcontractors as for itself.", "facet": "liability", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§7.4; §8.2 to §8.4" } ] }, { "uid": "blik:rule.complaint-alert-threshold", "name": "Alert when complaints pass 3 percent", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "high", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "PSP alerts a participant when complaints about mobile transactions for reasons on that participant's side exceed 3 percent of its BLIK transactions of the last 30 days, and number at least 50. Other alerts cover a ready settlement report, a guarantee run caused by an issuer's shortfall, and events the Technical Specification lists.", "facet": "liability", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [ { "kind": "limit", "text": "more than 3 percent of the participant's BLIK transactions over 30 days, at least 50 complaints" } ], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§20" } ] }, { "uid": "blik:rule.complaint-fault-pays", "name": "In a complaint the party at fault pays, PSP decides doubt, silence means fault", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "high", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "When a complaint carries a concrete claim by a user, institutional user, merchant or participant that arose because PSP or a participant broke its obligations, that party bears the cost of the claim. PSP tells the participants involved who caused the event and the account into which that participant must transfer the claimed amount. PSP resolves any doubt over who is responsible. A participant that does not answer a complaint within the deadline in the complaints procedure is treated as accepting that it was at fault.", "facet": "liability", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [], "part_of": [ "blik:exc.complaint" ], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§9.5 to §9.7" } ] }, { "uid": "blik:rule.disputes-over-goods-outside-scheme", "name": "Goods and services disputes stay between user and merchant", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "high", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "PSP and each participant answer only for their own failure to follow the participation agreement or the rulebook. None of them answers for whether the merchant delivered, or delivered what was agreed; such claims are settled directly between the user and the merchant. Whatever PSP does as a result of a complaint leaves that relationship untouched and is no proof that the user took part in the transaction or received anything from it.", "facet": "liability", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§8.1; §9.9" } ] }, { "uid": "blik:rule.unauthorised-transaction-reporting", "name": "Issuers report unauthorised transactions within two business days", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "high", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "Each issuer must run a procedure to monitor unauthorised BLIK transactions, meaning transactions started by someone not entitled to, and report each case it identifies to PSP within two business days. It must also warn users about the risks of paying online and with mobile apps. PSP reports unauthorised transactions to NBP and other authorities as the law requires.", "facet": "liability", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" }, { "uid": "blik:txn.p2p", "name": "Phone transfer (P2P)" }, { "uid": "blik:txn.p2p-request", "name": "Transfer request (P2P-R)" } ], "parameters": [ { "kind": "time_window", "text": "within 2 business days of identifying the case" } ], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§7.2 o, p; §24.4" } ] }, { "uid": "blik:rule.issuer-is-users-payment-service-provider", "name": "The issuer is the user's payment service provider", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "The BLIK scheme is a payment scheme under the Payment Services Act of 19 August 2011 and the BLIK system a payment system under the Settlement Finality Act of 24 August 2001, both run by PSP. Toward the user, the payment service (making the payment instrument available and executing transactions) is the issuer's; the acquirer only takes part as an intermediary. The user's statutory rights therefore run against the issuer [Inference: the Act itself was not read].", "facet": "consumer-law", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" }, { "uid": "blik:txn.p2p", "name": "Phone transfer (P2P)" }, { "uid": "blik:txn.p2p-request", "name": "Transfer request (P2P-R)" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§1.1; §3.11; §28.1" } ] }, { "uid": "blik:rule.user-complains-to-own-bank", "name": "Users complain to their own bank", "status": "corroborated", "stored_status": "corroborated", "source_class": "public_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (public primary)", "say": "A validator compared this with 1 named source, the strongest being an operator or regulator publication. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "PSP tells users to complain about a BLIK transaction, including contactless and recurring ones, to the bank whose app they used, since that bank holds the transaction details and can act. PSP itself deals only with participants.", "facet": "consumer-law", "rests_on": "guidance", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" }, { "uid": "blik:txn.p2p", "name": "Phone transfer (P2P)" }, { "uid": "blik:txn.p2p-request", "name": "Transfer request (P2P-R)" } ], "parameters": [], "part_of": [ "blik:exc.complaint" ], "sources": [ { "uid": "blik:src.blik-faq", "name": "BLIK FAQ (blik.com/faq)", "url": "https://www.blik.com/faq", "source_class": "public_primary", "edition": "live page as read 2026-09-19", "section": "where to complain" } ] }, { "uid": "blik:rule.authorisation-flows", "name": "Four ways a BLIK authorisation travels", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 2 named sources, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "Issuers authorise every BLIK transaction with a BLIK code. With a code PSP generated, the issuer asks PSP for it on the user's request, the user types it into the acceptance device, the acquirer sends it with the transaction data to PSP, and PSP finds the mobile account and issuer and asks for authorisation. With a code the acceptance device shows, the user pulls it into the app, the issuer registers it with PSP, and the rest runs the same way. With an alias, a standing code the issuer registered, the acceptance device obtains the alias as the Technical Specification sets. For BLIK-C, PSP obtains a Mastercard token for the alias, the phone passes it to the terminal, Mastercard's tokenisation system forwards it to PSP, and the answer goes back through Mastercard. In every flow the issuer's accept or reject goes back to PSP and then to the acceptance device. Adyen's BLIK OneClick, paying without a code at a shop the user saved as trusted in the bank app, appears to use the alias flow [Inference].", "facet": "messages", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§7.2 j, l, m; §11.2 to §11.6" }, { "uid": "blik:src.adyen-blik", "name": "Adyen Docs: BLIK", "url": "https://docs.adyen.com/payment-methods/blik", "source_class": "secondary", "edition": "live page as read 2026-09-19", "section": "BLIK OneClick" } ] }, { "uid": "blik:rule.message-standards-technical-specification", "name": "Message formats and error codes live in the Technical Specification", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "PSP sets the technical standards for the scheme and for communication with participants and Mastercard, checks each transaction against the Technical Specification for Participants, and tells a participant when its messages do not conform. Message formats, error codes, code validity and the transaction limit are in that specification, Annex 3 to the rulebook, which PSP does not publish. Participants must report doubts about a transaction to PSP at once, in the way the specification sets.", "facet": "messages", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" }, { "uid": "blik:txn.p2p", "name": "Phone transfer (P2P)" }, { "uid": "blik:txn.p2p-request", "name": "Transfer request (P2P-R)" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§2 (definition of Specyfikacja Techniczna dla Uczestników); §5.1 g, h, m; §6 b, c; §22; list of annexes" } ] }, { "uid": "blik:rule.recurring-flags", "name": "Recurring payment flags and the one public BLIK error code", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "A merchant can send refuseNoPayId set to true so BLIK rejects the transaction when the user's bank does not support recurring payments, and handle the error. Without that flag, and with such a bank, a set-up carried on a transaction above zero is shown to the user as a plain payment without the recurring invitation, while a zero-amount set-up is rejected by BLIK with error code ER_PAYID_UNHANDLED and never reaches the bank. The NODELAY flag (models A and O) skips the 72 hour retry period. Every acquirer must support both flags.", "facet": "messages", "rests_on": "rule", "via": "both", "also_applies_to": [], "parameters": [], "part_of": [ "blik:exc.decline" ], "sources": [ { "uid": "blik:src.blik-recurring-payments-introduction", "name": "BLIK Recurring Payments: Introduction", "url": "https://www.blik.com/lp/reccuring-payments/Introduction.141951041.html", "source_class": "authoritative_primary", "edition": "undated live page as read 2026-09-19", "section": "refuseNoPayID mechanism; NODELAY flag" } ] }, { "uid": "blik:rule.recurring-models", "name": "Recurring payment models A, M and O", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 2 named sources, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "PSP offers three models. In model A later transactions go through without the user confirming, for a fixed amount at a fixed frequency until an expiry the merchant must set, at most 10 years ahead; only one automatic transaction per frequency period is allowed, and a charge with another amount, or a second one in the same period, needs the user's confirmation in the app. In model M the user confirms every recurring transaction, and amounts and frequency may vary; the consent may run to a date or until cancelled. In model O transactions go through without confirmation even though amount and frequency may vary; it too may run to a date or until cancelled. Not every bank supports recurring payments, and merchants must say which do.", "facet": "messages", "rests_on": "rule", "via": "both", "also_applies_to": [], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.blik-recurring-payments-introduction", "name": "BLIK Recurring Payments: Introduction", "url": "https://www.blik.com/lp/reccuring-payments/Introduction.141951041.html", "source_class": "authoritative_primary", "edition": "undated live page as read 2026-09-19", "section": "implementation models; supporting banks management" }, { "uid": "blik:src.blik-recurring-payments-model-a", "name": "BLIK Recurring Payments: Model A", "url": "https://www.blik.com/lp/reccuring-payments/Model-A.141951045.html", "source_class": "authoritative_primary", "edition": "undated live page as read 2026-09-19", "section": "how it works; frequency; invitation data" } ] }, { "uid": "blik:rule.participant-duties", "name": "What issuers and acquirers must do", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "Issuers: give users the app or another code-based function and authenticate them in it; get one-time codes from PSP, and register with PSP the mobile accounts and any codes they create themselves; authorise only on a code PSP issued or registered; update a mobile account's status at once, for example when a user leaves; and keep sanctioned persons out. Acquirers: tag each merchant with an ISO merchant category code and offer BLIK only to merchants that act lawfully and ethically, are not on sanctions lists and do not use the BLIK mark misleadingly. Everyone: run BLIK and connect to it as the Technical Specification sets, submit to tests and audits, follow anti money laundering law, and promote BLIK with its mark. Securing issuers, secured acquirers and indirect participants carry extra account and funding duties, and each category must offer the functions Annex 5 marks mandatory for it.", "facet": "participants", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" }, { "uid": "blik:txn.p2p", "name": "Phone transfer (P2P)" }, { "uid": "blik:txn.p2p-request", "name": "Transfer request (P2P-R)" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§7.1; §7.2 h to n, q, r; §27.5" } ] }, { "uid": "blik:rule.issuer-decides-authorisation", "name": "The issuer decides; an acquirer's no-confirmation hint is only advice", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "Whether a BLIK transaction can go ahead is the issuer's decision. At an acquirer's request PSP may let it send issuers a recommendation to authorise without asking the user to confirm in the app; the issuer may ignore it, and the acquirer using it must put measures in place against unauthorised transactions.", "facet": "decision-points", "rests_on": "rule", "via": "both", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [], "part_of": [ "blik:exc.decline" ], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§11.3 e; §11.7" } ] }, { "uid": "blik:rule.psp-fraud-and-gambling-rejection", "name": "PSP rejects on fraud monitoring and blocks illegal gambling domains", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "PSP's system itself stops two kinds of transaction before the issuer decides. It rejects one when PSP's monitoring shows the participant would refuse it because fraud is likely. It halts, and never sends to the issuer, a payment for a service offered through a domain on Poland's register of domains offering gambling unlawfully; that block does not relieve participants of their own legal duties on gambling payments. PSP monitors BLIK transactions for rule breaches, unauthorised use and fraud under the Payment Services Act, alongside the participants' own monitoring.", "facet": "decision-points", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" } ], "parameters": [], "part_of": [ "blik:exc.decline" ], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§5.1 q; §5.2; §14.2 to §14.4" } ] }, { "uid": "blik:rule.recurring-retry-72-hours", "name": "Recurring transaction short of funds: 72 hours of bank retries", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 2 named sources, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "When a recurring transaction cannot be authorised because funds are short or a limit is exceeded, the bank has the next 72 hours to tell the user why and ask for funds or a limit change, and tries again to authorise; if the problem remains it declines. In models A and O the merchant can skip that period with the NODELAY flag, and the transaction is marked unsuccessful at once; the merchant may then retry manually, and PSP recommends leaving 24 hours between attempts. PSP's FAQ adds that a recurring payment not made for lack of funds may be retried by the bank or the merchant.", "facet": "decision-points", "rests_on": "guidance", "via": "both", "also_applies_to": [], "parameters": [], "part_of": [ "blik:exc.decline" ], "sources": [ { "uid": "blik:src.blik-recurring-payments-introduction", "name": "BLIK Recurring Payments: Introduction", "url": "https://www.blik.com/lp/reccuring-payments/Introduction.141951041.html", "source_class": "authoritative_primary", "edition": "undated live page as read 2026-09-19", "section": "unsuccessful recurring transactions; NODELAY flag" }, { "uid": "blik:src.blik-faq", "name": "BLIK FAQ (blik.com/faq)", "url": "https://www.blik.com/faq", "source_class": "public_primary", "edition": "live page as read 2026-09-19", "section": "no money on the account when a recurring payment is due" } ] }, { "uid": "blik:rule.temporary-block", "name": "PSP may block a participant temporarily", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 1 named source, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "PSP may cut a participant off from BLIK for a time on three kinds of ground. Conduct: a breach of PSP's security rules, behaviour that endangers BLIK's continuity, or a finding PSP asked it to fix still open after the deadline. Faulty traffic: messages in a format the Technical Specification does not allow, or messages BLIK does not expect at that stage of a transaction. Failure at scale: no timely answer to any authorisation request sent in the last 15 minutes, or refusals making up half or more of its authorisation answers where neither the user nor PSP caused them. Once the participant e-mails PSP that the cause is removed, the block is lifted.", "facet": "decision-points", "rests_on": "rule", "via": "applies_to", "also_applies_to": [ { "uid": "blik:txn.code-payment", "name": "Code payment to a merchant" }, { "uid": "blik:txn.cash", "name": "Cash withdrawal or deposit" }, { "uid": "blik:txn.refund-to-user", "name": "Refund to the user" }, { "uid": "blik:txn.blik-c", "name": "Contactless BLIK (BLIK-C)" }, { "uid": "blik:txn.p2p", "name": "Phone transfer (P2P)" }, { "uid": "blik:txn.p2p-request", "name": "Transfer request (P2P-R)" } ], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§21" } ] }, { "uid": "blik:rule.recurring-cancel-in-banking-app", "name": "Recurring payment: the user sees and cancels it in the bank app", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 2 named sources, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "The user can see every recurring payment in the banking app, including whether it charges automatically or needs confirmation, and can cancel one by deleting it there. Deleting it stops BLIK charges but does not necessarily end the user's contract with the merchant. A recurring payment does not move with the user to another bank; it has to be set up again there.", "facet": null, "rests_on": "guidance", "via": "both", "also_applies_to": [], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.blik-recurring-payments-introduction", "name": "BLIK Recurring Payments: Introduction", "url": "https://www.blik.com/lp/reccuring-payments/Introduction.141951041.html", "source_class": "authoritative_primary", "edition": "undated live page as read 2026-09-19", "section": "Recurring Payment" }, { "uid": "blik:src.blik-faq", "name": "BLIK FAQ (blik.com/faq)", "url": "https://www.blik.com/faq", "source_class": "public_primary", "edition": "live page as read 2026-09-19", "section": "recurring payment questions" } ] }, { "uid": "blik:rule.recurring-consent-in-banking-app", "name": "Recurring payment: consent started at the merchant, confirmed in the bank app", "status": "corroborated", "stored_status": "corroborated", "source_class": "authoritative_primary", "confidence": "medium", "tier": { "k": "cor", "label": "Corroborated (authoritative primary)", "say": "A validator compared this with 3 named sources, the strongest being a publication of Polski Standard Płatności S.A. (PSP) itself. It is not verified: no person has checked it against the current rulebook edition." }, "statement": "A BLIK recurring payment is the user's consent for a merchant to start later transactions. The user starts it in the merchant's site or app, typically by choosing BLIK recurring payment and entering a BLIK code, and confirms it in the banking app, which shows the merchant, amount, frequency and expiry. Setting it up charges nothing by itself; each later charge is a separate recurring transaction, though the first charge may be taken at set-up. The rulebook's definition of a merchant already covers one that starts a BLIK transaction under authority the user gave it earlier.", "facet": null, "rests_on": "rule", "via": "both", "also_applies_to": [], "parameters": [], "part_of": [], "sources": [ { "uid": "blik:src.blik-recurring-payments-introduction", "name": "BLIK Recurring Payments: Introduction", "url": "https://www.blik.com/lp/reccuring-payments/Introduction.141951041.html", "source_class": "authoritative_primary", "edition": "undated live page as read 2026-09-19", "section": "Recurring Payment and Recurring Transaction" }, { "uid": "blik:src.blik-recurring-payments-model-a", "name": "BLIK Recurring Payments: Model A", "url": "https://www.blik.com/lp/reccuring-payments/Model-A.141951045.html", "source_class": "authoritative_primary", "edition": "undated live page as read 2026-09-19", "section": "how it works; information displayed in the banking app" }, { "uid": "blik:src.psp-blik-rulebook-single-session-2026-04-15", "name": "Regulamin Systemu Płatności Mobilnych BLIK, single-session edition approved 15 April 2026", "url": "https://www.blik.com/download/pobierz/regulamin", "source_class": "authoritative_primary", "edition": "approved by the PSP Management Board on 15 April 2026, single-session model; PDF of 56 pages, 1,467,405 bytes, SHA-256 b78d88aadc111c33442ce3504e245a332d2f1b3f2a69b30ab6deb46b05a6be57", "section": "§2 (definition of Akceptant a, second indent)" } ] } ], "inherited": [ { "facet": "refund", "label": "Refund", "question": "Can the payer get the money back, and on what right?", "fact_uid": "blik:refund", "fact_name": "How does a merchant refund a BLIK payment?" } ], "differs": [ { "facet": "finality", "label": "Finality", "fact_uid": "blik:finality", "fact_name": "When is a BLIK payment final, and can it be undone?", "rules": [ { "uid": "blik:rule.order-entry-and-irrevocable-authorisation", "name": "When a BLIK order is in and when it can no longer be withdrawn" }, { "uid": "blik:rule.settlement-order-irrevocable", "name": "The settlement order is entered and fixed at positive authorisation" }, { "uid": "blik:rule.cancellation-or-correction-13-months", "name": "Cancellation or correction within 13 months" } ] }, { "facet": "settlement", "label": "Settlement", "fact_uid": "blik:settlement", "fact_name": "How and when do BLIK participants settle with each other?", "rules": [ { "uid": "blik:rule.net-clearing", "name": "Net clearing of BLIK transactions, fees included" }, { "uid": "blik:rule.sorbnet3-settlement-run", "name": "Settlement in SORBNET3 through PSP's auxiliary account" }, { "uid": "blik:rule.sessions-single-session-edition", "name": "Clearing sessions, single-session model" }, { "uid": "blik:rule.sessions-multi-session-edition", "name": "Clearing and settlement sessions, multi-session model" }, { "uid": "blik:rule.settlement-guarantee", "name": "Settlement guarantee among issuers" }, { "uid": "blik:rule.settlement-entity", "name": "Every participant settles through a settlement entity" } ] }, { "facet": "hours", "label": "Hours", "fact_uid": "blik:hours", "fact_name": "When can BLIK be used, and how long do codes and approvals last?", "rules": [ { "uid": "blik:rule.continuous-operation", "name": "The scheme runs around the clock" }, { "uid": "blik:rule.one-time-code-validity", "name": "How long a one-time BLIK code lives" } ] }, { "facet": "limits", "label": "Limits", "fact_uid": "blik:limits", "fact_name": "What amount limits apply to a BLIK payment?", "rules": [ { "uid": "blik:rule.per-transaction-limit-unpublished", "name": "Scheme per-transaction limit: set, but not public" }, { "uid": "blik:rule.issuer-set-limits", "name": "Each bank sets its users' BLIK limits" }, { "uid": "blik:rule.psp-fraud-and-gambling-rejection", "name": "PSP rejects on fraud monitoring and blocks illegal gambling domains" } ] }, { "facet": "return", "label": "Return", "fact_uid": "blik:return", "fact_name": "Can a BLIK payment be sent back?", "rules": [ { "uid": "blik:rule.declined-authorisation-never-settles", "name": "A declined transaction never settles" }, { "uid": "blik:rule.complaint-ticket-process", "name": "Complaints run from participant to PSP through a ticket system" } ] }, { "facet": "recall", "label": "Recall", "fact_uid": "blik:recall", "fact_name": "Can a BLIK payment be cancelled or recalled after it is sent?", "rules": [ { "uid": "blik:rule.order-entry-and-irrevocable-authorisation", "name": "When a BLIK order is in and when it can no longer be withdrawn" }, { "uid": "blik:rule.cancellation-or-correction-13-months", "name": "Cancellation or correction within 13 months" } ] }, { "facet": "refund", "label": "Refund", "fact_uid": "blik:refund", "fact_name": "How does a merchant refund a BLIK payment?", "rules": [ { "uid": "blik:rule.disputes-over-goods-outside-scheme", "name": "Goods and services disputes stay between user and merchant" }, { "uid": "blik:rule.user-complains-to-own-bank", "name": "Users complain to their own bank" } ] }, { "facet": "liability", "label": "Liability", "fact_uid": "blik:liability", "fact_name": "Who bears the loss on a BLIK payment that goes wrong?", "rules": [ { "uid": "blik:rule.bad-faith-and-crime-liability", "name": "Who answers for bad-faith, criminal or intruder transactions" }, { "uid": "blik:rule.complaint-fault-pays", "name": "In a complaint the party at fault pays, PSP decides doubt, silence means fault" }, { "uid": "blik:rule.disputes-over-goods-outside-scheme", "name": "Goods and services disputes stay between user and merchant" }, { "uid": "blik:rule.unauthorised-transaction-reporting", "name": "Issuers report unauthorised transactions within two business days" }, { "uid": "blik:rule.complaint-alert-threshold", "name": "Alert when complaints pass 3 percent" }, { "uid": "blik:rule.settlement-guarantee", "name": "Settlement guarantee among issuers" } ] }, { "facet": "consumer-law", "label": "Consumer law", "fact_uid": "blik:consumer-law", "fact_name": "How does BLIK relate to consumer protection law?", "rules": [ { "uid": "blik:rule.issuer-is-users-payment-service-provider", "name": "The issuer is the user's payment service provider" }, { "uid": "blik:rule.user-complains-to-own-bank", "name": "Users complain to their own bank" }, { "uid": "blik:rule.recurring-consent-in-banking-app", "name": "Recurring payment: consent started at the merchant, confirmed in the bank app" }, { "uid": "blik:rule.recurring-cancel-in-banking-app", "name": "Recurring payment: the user sees and cancels it in the bank app" } ] }, { "facet": "messages", "label": "Messages", "fact_uid": "blik:messages", "fact_name": "Which messages carry a BLIK payment and its outcome?", "rules": [ { "uid": "blik:rule.authorisation-flows", "name": "Four ways a BLIK authorisation travels" }, { "uid": "blik:rule.message-standards-technical-specification", "name": "Message formats and error codes live in the Technical Specification" }, { "uid": "blik:rule.recurring-models", "name": "Recurring payment models A, M and O" }, { "uid": "blik:rule.recurring-flags", "name": "Recurring payment flags and the one public BLIK error code" } ] }, { "facet": "participants", "label": "Participants", "fact_uid": "blik:participants", "fact_name": "Who takes part in BLIK, and in what roles?", "rules": [ { "uid": "blik:rule.participant-duties", "name": "What issuers and acquirers must do" } ] }, { "facet": "decision-points", "label": "Human decision points", "fact_uid": "blik:decision-points", "fact_name": "Where do BLIK's rules leave a decision to a person or an institution?", "rules": [ { "uid": "blik:rule.issuer-decides-authorisation", "name": "The issuer decides; an acquirer's no-confirmation hint is only advice" }, { "uid": "blik:rule.psp-fraud-and-gambling-rejection", "name": "PSP rejects on fraud monitoring and blocks illegal gambling domains" }, { "uid": "blik:rule.complaint-fault-pays", "name": "In a complaint the party at fault pays, PSP decides doubt, silence means fault" }, { "uid": "blik:rule.temporary-block", "name": "PSP may block a participant temporarily" }, { "uid": "blik:rule.recurring-retry-72-hours", "name": "Recurring transaction short of funds: 72 hours of bank retries" } ] } ], "exceptions": [ { "uid": "blik:exc.cancellation-correction", "name": "Cancellation or correction", "shared": true, "via": [ { "from": "blik:rule.cancellation-or-correction-13-months", "type": "part_of" } ] }, { "uid": "blik:exc.complaint", "name": "Complaint (reklamacja)", "shared": true, "via": [ { "from": "blik:mandate.recurring-payment", "type": "disputed_via" }, { "from": "blik:rule.complaint-fault-pays", "type": "part_of" }, { "from": "blik:rule.complaint-ticket-process", "type": "part_of" }, { "from": "blik:rule.user-complains-to-own-bank", "type": "part_of" } ] }, { "uid": "blik:exc.decline", "name": "Decline or rejection", "shared": true, "via": [ { "from": "blik:rule.declined-authorisation-never-settles", "type": "part_of" }, { "from": "blik:rule.issuer-decides-authorisation", "type": "part_of" }, { "from": "blik:rule.per-transaction-limit-unpublished", "type": "part_of" }, { "from": "blik:rule.psp-fraud-and-gambling-rejection", "type": "part_of" }, { "from": "blik:rule.recurring-flags", "type": "part_of" }, { "from": "blik:rule.recurring-retry-72-hours", "type": "part_of" } ] } ] } }