Spain
Mexico
Brazil
Poland
Taiwan
Philippines
South Korea
The essentials
- The PLN 19.99 purchase was a pilot reported by the operator.
- Automatic checkout still relied on prior user authorization.
- Do not read the pilot as availability at every shop and bank.
What happened in the pilot
On 9 September 2026, BLIK reported a pilot in which an AI agent watched for an out-of-stock hand cream at Your KAYA and bought it when the selected version returned. The purchase cost PLN 19.99. According to the operator’s announcement, Juo supplied the chat environment and PayU processed the payment. The publication date is confirmed; the transaction’s exact day is not specified.
The important detail is the sequence of permission. The user first confirmed an instruction through a six-digit BLIK code and authorization in the banking app. No further action was needed when the purchase finished. This is a specific pilot described by its participants, rather than evidence that the feature is already available throughout online retail or every participating bank.
From recommending to carrying out a purchase
A conventional shopping assistant finds an option and leaves the final button to a person. The distinction here is that an earlier decision can be carried out later. Our interpretation is that the crucial consumer decision moves toward the instruction: which item may be bought, under what conditions, and for how long? Convenient execution makes that first agreement more important, not less.
Consider a hypothetical instruction to buy one item for no more than PLN 20. Does that amount include delivery? Is another scent acceptable if the chosen one is unavailable? Does the instruction expire after a week? These are proposed questions for evaluating a service, not claims about settings offered by this pilot. They turn a vague request into a decision a person can review.
A pilot is not a reason to share a code
The story is not an invitation to send a BLIK code to someone claiming to be an AI assistant in a message. BLIK’s general security guidance warns against giving codes to other people and tells users to check transaction details in the banking app. A familiar-looking social account can also be misleading. The reported pilot used an authorized payment process.
A useful check is to read the actual screen: is this the legitimate bank or merchant flow, does the permission match the purchase you requested, and are the amount and recipient correct? If something is unclear, pause before approving and use your bank’s official support route. An impressive technology label does not answer those questions on your behalf.
What to look for next
The demonstration raises practical questions for future products: where can a user cancel an outstanding instruction, how is the maximum amount displayed, and can the order history be matched to a record of consent? Those are editorial evaluation criteria. The announcement alone does not establish that every one of these controls is generally available, or specify a public rollout timetable.
The interesting part of PLN 19.99 is therefore the timing of the decision. Before celebrating a purchase that finishes by itself, ask whether the original instruction is understandable and reviewable. For now, read the report as an operator-described pilot, keep its claims separate from independent testing, and check formal bank or service announcements before assuming you can use the same feature.
Official sources
An explanation of financial mechanics based on official sources. Hypothetical calculations are not actual trading results or forecasts.
