Telegram Bot Payments in Poland: BLIK, Przelewy24, Stripe and Telegram Stars

Before you pay a developer to build a bot, it makes sense to know whether that bot can take real Polish money at all. The short, calm answer is yes – but everything depends on what you sell and which gateway you connect. Here it is, without the jargon.

Which payment methods work

The first thing to understand is that Telegram splits payments into two completely separate worlds. Which one your product belongs to decides everything else.

Physical goods and services – real money. If you sell something that exists outside Telegram (a product shipped by courier, a table booking, a haircut, a consultation, an event ticket), the bot can take ordinary złoty. It does this through an external payment provider – and this is where the methods Polish customers expect come in:

• BLIK – in Poland this is the backbone of online shopping today; for many customers, no BLIK is a reason to abandon the purchase.
• Przelewy24 (P24) – a popular Polish gateway that bundles BLIK, fast bank transfers and cards in one window.
• Cards (Visa / Mastercard) and wallets like Apple Pay / Google Pay – for international customers and anyone who prefers a card.

In practice these Polish methods usually reach the bot through Stripe – a global processor that officially supports both BLIK and Przelewy24 for the Polish market, and is also one of the providers Telegram supports natively. As a result the customer taps “Pay”, picks BLIK, enters the code from their banking app and returns to the chat – all without leaving Telegram.

Digital goods – Telegram Stars only. If you sell something that exists purely inside Telegram or is purely digital (access to a private channel, premium content, features in a mini-app, digital “stickers”), Apple's and Google's store rules force Telegram to route those payments only through its internal currency, Telegram Stars. The customer buys Stars in the app and pays with them. This is a deliberate mobile-platform restriction – there is no workaround that doesn't risk your bot being hidden on phones.

How it actually works

From the customer's side the whole payment happens in one chat window. The bot issues what is called an invoice – a message with the product name, the amount and a “Pay” button. After a tap the customer chooses a method (say, BLIK) and Telegram hands them over to the payment gateway. The customer confirms in their banking app, returns to the chat, and the bot receives a success signal so it can immediately deliver access, a confirmation or a booking code.

An important technical detail: neither Telegram nor the bot itself ever sees or stores your card number. Sensitive data goes only to a certified payment provider (such as Stripe) that meets the PCI-DSS standard. For you as the owner this means fewer obligations around card-data security, because that data never passes through your own server.

With Telegram Stars the flow is even simpler: the customer buys Stars directly inside Telegram (through the built-in App Store or Google Play purchase) and then pays with them in your bot in a single tap, with no card details or address to enter.

What you need as the owner

For the bot to genuinely take physical-world payments you need three pieces. First, the bot itself – the token from BotFather that your developer receives. Second, an account with a payment provider (such as Stripe), registered to your business, with your company details, a bank account for payouts and a verified identity. Third, the link between the two through the BotFather panel, where the provider's key is connected to the bot.

On the formal side in Poland, what matters is that the money lands in a business account and the provider produces a transaction history you reconcile with your bookkeeping. Decide up front how you will issue receipts or invoices and whether cash-register obligations (or an exemption) apply to you – that is a question for your accountant, not your developer. The bot can send a purchase confirmation in the chat, but that does not replace a proper accounting document.

Typical selling scenarios

It is clearest with concrete cases. Local hospitality or services (a table reservation with a deposit, a salon booking, an in-person course) belong to the physical world, so BLIK and P24 through a gateway. A shop with shipped goods also uses a gateway, plus the shipping options and delivery address that Telegram can collect during payment. Online consultations delivered outside Telegram (for example a session on a separate video call) are still a “real-world” service, so a gateway is allowed.

It is different for a private premium-content channel, community access or features inside a mini-app – these are purely digital goods consumed inside Telegram, so Telegram Stars apply. The line can be subtle, which is why it pays to classify each product unambiguously before the developer starts writing code.

Pitfalls: fees, refunds, GDPR

First, fees. Every gateway charges per transaction, rates differ between methods and are updated from time to time – check the chosen provider's current pricing rather than relying on figures you heard somewhere. Telegram Stars carry a separate settlement model imposed by the mobile stores, so the real amount you see in your account can be lower than the price shown to the customer.

Second, refunds and disputes. An EU customer has a right of withdrawal from a distance contract (with exceptions, including for some digital content), so the bot should provide a refund path and you should have terms that describe the rules. Third, GDPR: since you collect data (delivery address, contact details), you need a legal basis, clear information for the customer, and an understanding of where that data flows (Telegram, the payment provider). These are business and legal decisions best settled with your accountant and lawyer before you start selling.