You can accept payments from Telegram users via Telegram Bots.
Note: This article is intended for bot developers. If you're looking for a general overview of Telegram Payments, check out the Telegram blog.
Also, visit the MTProto payment documentation for a technical overview of payments from the user's perspective.
From the user's perspective the payments system is completely seamless. Merchant bots can send specially formatted invoice messages to users. Such invoice messages feature a photo and description of the product along with a prominent Pay button. Tapping this button opens a special payment interface in the Telegram app. In this interface, users are prompted for additional details like shipping info, phone number, or email address.
Once they've entered all the necessary info, it is forwarded to the merchant bot. The bot can offer several shipping options for physical goods based on the address. When ready, users can enter their credit card info or choose one of their saved cards — and pay for the product. Telegram also supports Apple Pay and Android Pay. Once the transaction is done, the merchant bot sends a receipt message that contains payment details along with shipping and delivery information.
Telegram does not process payments from users and instead relies on different payment providers around the world. It is the payment providers that handle and store all sensitive information, like credit card details. Neither Telegram nor the bot developers have access to it. For the moment we support payments from more than 200 countries via the the following payment providers:
More providers are coming.
Telegram does not charge any commission for using the Payments API. Note though, that most payment providers will have their own commissions. For example, Stripe in the US charges 2.9% + 30¢ per successful card charge (see the Stripe website for more details on pricing).
Telegram does not impose any limits on what products or services your bot can offer. But please note that you must comply with the rules of the payments provider you choose in our system. E.g., Stripe has a special page for prohibited businesses – you may want to consult that one before you start selling harvested organs.
Special Note: Due to Apple's limitations, bot developers are currently not allowed to accept payments for digital goods and virtual services from iOS users.
Telegram acts as a messenger between the paying user, the bot developer, and their chosen payment system. The user sends their credit card details directly to the payment system. Then the payment system's response and the shipping details entered by the user are passed to the bot developer so that they can process the order.
Since Telegram doesn‘t process the payments, we don’t store and can‘t access any sensitive data. Due to this structure, it is impossible for Telegram to handle complaints or cashbacks – any disputed payments are the responsibility of the bot developers, payment providers, and banks that participated in the exchange.
Now let‘s look at payments via Telegram’s Bot API in more detail. To start accepting payments, you need a Telegram bot, obviously. Have a chat with BotFather to create a bot if you haven't got one already.
Now you have a merchant bot that wants to offer goods or services to Telegram users. Let's call it
@merchantbot in this document. First stop is to choose and connect a payment provider. At the moment, you can use Stripe for bot payments. We will be connecting more providers in the coming months, so watch out for announcements on the @BotNews channel.
/mybots command in the chat with BotFather and choose the
@merchantbot that will be offering goods or services. Go to Bot Settings > Payments. Choose a provider, and you will be redirected to the relevant bot. Enter the required details so that the payments provider is connected successfully, go back to the chat with Botfather. The message will now show available providers. Each will have a name, a token, and the date the provider was connected. You will use the token when working with the Bot API.
While you‘re still developing and testing payments for your bot, use the “Stripe TEST MODE” provider. When in this mode, you can make payments without actually billing any accounts. Real cards can’t be used in test mode, but you can use test cards like
4242 4242 4242 4242 (full list here). You can switch between test mode and live mode as many times as you want, but please see the live checklist before you go live.
Please note that when your merchant bot is working in test mode, it will only be able to send invoices to those Telegram users that are mutual contacts with the account of the bot's creator. So make sure that those who will help you test the payments functionality are in your contacts list.
The user contacts
@merchantbot and requests to purchase something. The bot forms an invoice message with a description of the goods or service, amount to be paid, as well as requested shipping info.
Use the sendInvoice method to do this. The provider_token parameter is where you put the token value that you've obtained earlier via Botfather. It is possible for one merchant bot to use several different tokens for different users or different goods and services.
An invoice message with a pay button can only be sent to a private chat with the user. Groups and channels are not supported. The resulting invoice message will look like this:
The user specifies shipping information or other info requested by the bot. This could be the user's full name, an email address, a phone number in international format, or a full postal address for delivery.
If a shipping address was requested and you included the parameter is_flexible, the Bot API will send an Update with a shipping_query field to the bot. The bot must respond using answerShippingQuery either with a list of possible delivery options and the relevant delivery prices, or with an error (for example, if delivery to the specified address is not possible).
The user selects a delivery option from the list (the overall amount to be paid may change at this point) and proceeds to checkout.
The user enters their payment information and presses the final pay button. At this moment the Bot API sends an Update with the field pre_checkout_query to the bot that contains all the available information about the order. Your bot must reply using answerPrecheckoutQuery within 10 seconds after receiving this update or the transaction is canceled.
The bot may return an error if it can‘t process the order for any reason. We highly recommend specifying a reason for failure to complete the order in human readable form (e.g. "Sorry, we’re all out of rubber ducks! Would you be interested in a steel bear instead?"). Telegram will display this reason to the user.
In case the bot confirms the order, Telegram requests the payment provider to complete the transaction. If the payment information was entered correctly and the payment goes through, the API will send a receipt message of the type successful_payment from the user. Once your bot receives this message, it should proceed with delivering the goods or services purchased by the user.
For the user, the Invoice message in the UI becomes a Receipt — they can open this receipt at any time and see all the details of the transaction:
Going Viral: Deep Linking
Note the arrow button on the right of the receipt message on the screenshot above. This quick forwarding button allows the user to select multiple friends, groups, or channels and send the message to them immediately. Thanks to this button, your goods and services can spread virally — the resulting message will have a button that leads users to your bot and asks it to create a similar invoice.
For the quick forwarding button to work correctly, all your invoice messages must contain a start_parameter for creating a new invoice. More info on Deep Linking »
Once you‘ve tested everything and confirmed that your payments implementation works, you’re ready to switch to LIVE MODE. To do this, go to BotFather > /mybots > select
@merchantbot > Bot Settings / Payments and enable Stripe LIVE MODE. You will get a token that has the string
:LIVE: in the middle, e.g.
123:LIVE:XXXX. Do not give this token to any third parties!
Before your merchant bot goes into live mode, please ensure the following:
Telegram payments currently support the currencies listed below (here's a JSON version in case you need it).
If you're using Stripe as the payments provider, supported currencies may vary depending on the country you have specified in your Stripe account (more info).
The minimum and maximum amounts for each of the currencies roughly correspond to the limit of
US$ 1-10000. The amount must be expressed in 8 digits or less, so the maximum value will be correspondingly lower for some lower-value currencies like the Serbian dinar. Note that for each currency except USD these limits depend on exchange rates and may change over time (plan ahead for this when you implement limits in your code).
|Code||Title||Min amount||Max amount|
|AED||United Arab Emirates Dirham||AED 3.67||AED 36,730.28|
|AMD||Armenian Dram||483.68 AMD||4,836,894.70 AMD|
|ARS||Argentine Peso||ARS 68,47||ARS 684.716,97|
|AZN||Azerbaijani Manat||1,69 AZN||16 979,70 AZN|
|BAM||Bosnia & Herzegovina Convertible Mark||1,75 BAM||17.563,52 BAM|
|BDT||Bangladeshi Taka||BDT 84.82||BDT 848,204.20|
|BGN||Bulgarian Lev||1,75 BGN||17 594,46 BGN|
|BOB||Bolivian Boliviano||BOB 6,90||BOB 69.017,35|
|BRL||Brazilian Real||R$ 5,42||R$ 54.272,99|
|CHF||Swiss Franc||0.96 CHF||9'622.70 CHF|
|CLP||Chilean Peso||CLP 804||CLP 8.043.001|
|CNY||Chinese Renminbi Yuan||CN¥7.13||CN¥71,372.98|
|COP||Colombian Peso||COP 3.719,67||COP 37.196.700,00|
|CRC||Costa Rican Colón||CRC569,25||CRC5.692.566,70|
|CZK||Czech Koruna||24,24 CZK||242 484,98 CZK|
|DKK||Danish Krone||6,71 DKK||67181,00 DKK|
|DZD||Algerian Dinar||DZD 128.51||DZD 1,285,149.99|
|EGP||Egyptian Pound||EGP 15.84||EGP 158,405.97|
|EUR||Euro||0,90 €||9 014,02 €|
|GEL||Georgian Lari||3,19 GEL||31 949,64 GEL|
|HKD||Hong Kong Dollar||HK$7.75||HK$77,514.50|
|HNL||Honduran Lempira||HNL 24.96||HNL 249,649.72|
|HRK||Croatian Kuna||6,84 HRK||68.445,03 HRK|
|HUF||Hungarian Forint||313,09 HUF||3 130 910,34 HUF|
|ILS||Israeli New Sheqel||₪ 3.50||₪ 35,029.50|
|ISK||Icelandic Króna||136 ISK||1.361.198 ISK|
|KGS||Kyrgyzstani Som||73-76 KGS||737 677-96 KGS|
|KRW||South Korean Won||₩1,237||₩12,374,896|
|KZT||Kazakhstani Tenge||KZT411-86||KZT4 118 626-90|
|LBP||Lebanese Pound||LBP 1,508.37||LBP 15,083,756.00|
|LKR||Sri Lankan Rupee||LKR 186.16||LKR 1,861,672.10|
|MAD||Moroccan Dirham||MAD 9.81||MAD 98,129.94|
|MDL||Moldovan Leu||17.46 MDL||174,668.07 MDL|
|MNT||Mongolian Tögrög||MNT2 811,24||MNT28 112 426,63|
|MVR||Maldivian Rufiyaa||15.44 MVR||154,497.83 MVR|
|NIO||Nicaraguan Córdoba||NIO 33.85||NIO 338,504.01|
|NOK||Norwegian Krone||NOK 9,74||NOK 97 466,99|
|NZD||New Zealand Dollar||NZ$1.61||NZ$16,191.95|
|PAB||Panamanian Balboa||PAB 0.99||PAB 9,995.73|
|PEN||Peruvian Nuevo Sol||PEN 3.43||PEN 34,384.99|
|PLN||Polish Złoty||4,01 PLN||40 128,50 PLN|
|PYG||Paraguayan Guaraní||PYG 6.644||PYG 66.449.048|
|QAR||Qatari Riyal||QAR 3.64||QAR 36,409.87|
|RON||Romanian Leu||4,36 RON||43.685,99 RON|
|RSD||Serbian Dinar||105,99 RSD||1.059.902,91 RSD|
|RUB||Russian Ruble||70,60 RUB||706 098,02 RUB|
|SAR||Saudi Riyal||SAR 3.75||SAR 37,575.24|
|SEK||Swedish Krona||9,43 SEK||94.375,00 SEK|
|TJS||Tajikistani Somoni||10;24 TJS||102 426;87 TJS|
|TRY||Turkish Lira||6,82 TRY||68.263,06 TRY|
|TTD||Trinidad and Tobago Dollar||TTD6.75||TTD67,536.24|
|TWD||New Taiwan Dollar||NT$30.02||NT$300,220.03|
|UAH||Ukrainian Hryvnia||26,84UAH||268 427,36UAH|
|USD||United States Dollar||$1.00||$10,000.00|
|UYU||Uruguayan Peso||UYU 43,19||UYU 431.951,15|
|UZS||Uzbekistani Som||10 129,99 UZS||101 299 997,35 UZS|
|VND||Vietnamese Đồng||23.281 ₫||232.815.000 ₫|
|YER||Yemeni Rial||YER 250.35||YER 2,503,502.61|
|ZAR||South African Rand||ZAR 17.60||ZAR 176,064.70|