<metaproperty="description"content="Telegram Bot Payments are a free and open platform that allows sellers to accept payments for goods and services from Telegram…">
<metaproperty="og:description"content="Telegram Bot Payments are a free and open platform that allows sellers to accept payments for goods and services from Telegram…">
<p><strong>Telegram Bot Payments</strong> are a free and open platform that allows sellers to accept payments for goods and services from Telegram users. Telegram doesn't collect payment information and takes <strong>no commission</strong>.</p>
<p><strong>Note:</strong> This article is intended for bot developers and store owners. If you're looking for a general overview of Telegram Payments, check out the <ahref="https://telegram.org/blog/payments-2-0-scheduled-voice-chats#payments-2-0">Telegram blog</a>.</p>
<p>If you are new to Telegram bots and would like to learn how to create and set up a bot, please consult our <ahref="https://core.telegram.org/bots"><strong>Introduction to Bots</strong></a> and <ahref="/bots/faq"><strong>Bot FAQ</strong></a>.</p>
<p><ahref="https://telegram.org/blog/payments-2-0-scheduled-voice-chats">Payments 2.0</a> were added in April 2021 with <ahref="/bots/api">Bot API v.5.2</a>. New features:</p>
<ul>
<li>Send invoices to <strong>any chat</strong>, including to groups and channels.</li>
<li>Create invoices that can be <strong>forwarded</strong> and used by <strong>multiple buyers</strong> to order things.</li>
<li>Use <ahref="/bots/inline">inline mode</a> to help users show your goods and services to their friends and communities.</li>
<li>Allow <strong>tips</strong> from users with preset and custom amounts.</li>
<li>Accept payments from users on mobile or <strong>desktop apps</strong>.</li>
<li>Try <ahref="https://t.me/shopbot">@ShopBot</a> to create a test invoice – or start a message with <code>@ShopBot ...</code> in any chat for an <strong>inline invoice</strong>.</li>
<li>Check out <ahref="https://t.me/teststore">Demo Shop</a> for an example of a <ahref="https://telegram.org/tour/channels">Telegram Channel</a> used as <strong>virtual storefront</strong>.</li>
<divclass="blog_video_player_wrap"style="max-width: 400px; margin: 20px auto 20px;">
<videoclass="blog_video_player tl_blog_vid_autoplay"onclick="videoTogglePlay(this)"autoplayloopcontrolsmutedposter="/file/464001377/1/0o3vSvY22g8.123356/deb4ed6951d780f7b7"style="max-width: 400px;"title="If your pizza place can't deliver a clone army, you're buying pizza from the wrong shop."alt="Video: Ordering a pizza through a Telegram channel">
<p>Users need to update to <strong>Telegram 7.7</strong> or higher to use <strong>Payments 2.0</strong> (for <ahref="https://desktop.telegram.org">Telegram Desktop</a>, <strong>2.7.2</strong> or higher). Older <em>mobile</em> apps released after <ahref="https://telegram.org/blog/payments">May 2017</a> support basic payments in chats with bots.</p>
<p>You create a <strong>bot</strong> that offers goods and services to Telegram users. Merchant bots can send specially formatted <strong>invoice messages</strong> to users, groups or channels. If your bot supports <ahref="/bots/inline">inline mode</a>, users can also send invoices to other chats <em>via the bot</em>, including to one-on-one chats with other users.</p>
<divclass="blog_video_player_wrap"style="max-width: 400px; margin: 20px auto 20px;">
<videoclass="blog_video_player tl_blog_vid_autoplay"onclick="videoTogglePlay(this)"autoplayloopcontrolsmutedposter="/file/464001361/2/0tUACjLHgog.102443/ba08e6374676fd1918"style="max-width: 400px;"alt="Video: Paying for goods via an inline invoice">
<p>Invoice messages feature a <strong>photo</strong> and <strong>description</strong> of the product along with a prominent <strong>Pay</strong> button. Tapping this button opens a special payment interface in the Telegram app. In this interface, users can choose a <strong>tip amount</strong> (if allowed by the merchant) and enter additional details like shipping info, phone number, or email address.</p>
<p>The bot can offer several shipping options for physical goods based on the delivery address. When ready, users enter their credit card info or choose a saved card — and pay for the product. Telegram also supports <em>Apple Pay</em> and <em>Google Pay</em>. Once the transaction is done, the merchant bot can send a <strong>receipt message</strong> with payment details, shipping and delivery information.</p>
<blockquote>
<p><ahref="#the-payments-api">Detailed information</a> and <ahref="#step-by-step-process">step-by-step instructions</a> are available below.</p>
<p>Telegram does <strong>not</strong> process payments from users and instead relies on different <strong>payment providers</strong> 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.</p>
<p>For the moment we support payments from more than <strong>200 countries</strong> via the the following payment providers:</p>
<p>If you work for a company that provides services similar to standalone accounts in <ahref="https://stripe.com/connect">Stripe Connect</a>, please let us know via <ahref="https://t.me/botsupport">@BotSupport</a> (include the hashtag <code>#paymentsprovider</code> in your message).</p>
<p>To start accepting payments, you need a <strong>Telegram bot</strong>. Use <ahref="https://t.me/botfather">BotFather</a> to create a bot if you don't have one already.</p>
<p>Now you have a merchant bot that can offer goods or services to Telegram users. Let's call it <code>@merchantbot</code> in this document. The first stop is to choose and <strong>connect a payment provider</strong>, you can find the <ahref="#supported-payment-providers">list of supported providers</a> above.</p>
<li>Use the <code>/mybots</code> command in the chat with <ahref="https://t.me/botfather">BotFather</a> and choose the <code>@merchantbot</code> that will be offering goods or services.</li>
<li>Go to <em>Bot Settings > Payments</em>.</li>
<li>Choose a provider, and you will be redirected to the relevant bot.</li>
<li>Enter the required details so that the payments provider is connected successfully, go back to the chat with Botfather.</li>
<li>The message will now show available providers. Each will have a name, a <strong>token</strong>, and the date the provider was connected.</li>
<li>You will use the <strong>token</strong> when working with the Bot API.</li>
<p>You will find the necessary methods for building your payment implementation in the <ahref="https://core.telegram.org/bots/api#payments">Payments Section of the Bot API Manual</a>.</p>
<h4><aclass="anchor"name="testing-payments-the-39stripe-test-mode-39-provider"href="#testing-payments-the-39stripe-test-mode-39-provider"><iclass="anchor-icon"></i></a>Testing Payments: the 'Stripe TEST MODE' Provider</h4>
<p>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 <code>4242 4242 4242 4242</code> (<ahref="https://stripe.com/docs/testing#cards">full list here</a>). You can switch between test mode and live mode as many times as you want, but please see the <ahref="#going-live">live checklist</a><strong>before</strong> you go live.</p>
<p>The user contacts <code>@merchantbot</code> and requests to purchase something. The bot forms an invoice message with a description of the goods or service, amount to be paid, and requested shipping info. There are two ways of creating an invoice:</p>
<p>Use the <ahref="/bots/api#sendinvoice">sendInvoice</a> method to generate an invoice and send it to a chat. The <em>provider_token</em> parameter is where you put the <em>token</em> value that you've <ahref="#getting-a-token">obtained earlier via Botfather</a>. It is possible for one merchant bot to use several different tokens for different users or different goods and services.</p>
<p>As of <ahref="#introducing-payments-2-0">Payments 2.0</a>, invoice messages with a pay button can be sent to <strong>chats of any type</strong>: private chats with the user, groups, or channels. The resulting invoice message will look like this:</p>
<p>If <code>@merchantbot</code> supports <ahref="/bots/inline">inline mode</a>, you can use <ahref="/bots/api#inputinvoicemessagecontent">inputInvoiceMessageContent</a> to allow users to share invoices for your goods and services to their one-on-one chats with friends, or to their groups and channels. These invoices will have a <strong>Pay button</strong> that can be used multiple times.</p>
<p>As of <ahref="#introducing-payments-2-0">Payments 2.0</a> there are two ways for handling <strong>forwarded copies</strong> of your invoices, controlled by the parameter <em>start_parameter</em> in the <ahref="/bots/api#sendinvoice">sendInvoice</a> method.</p>
<ul>
<li><strong>A. Multi-chat invoice.</strong> Forwarded copies show a <strong>Pay button</strong>, which multiple users can press and attempt to pay for the goods or services. <ahref="#b-inline-invoice">Inline invoices</a> are always multi-chat invoices.</li>
<li><strong>B. Single-chat invoice.</strong> Invoice can only be paid from the chat to which it was sent, <em>forwarded copies</em> show a <strong>URL button</strong> with a deep link to the bot. The deep link can be used to generate a similar invoice in the chat with the bot, to show an error message, or for other purposes. <ahref="/bots#deep-linking">More info on Deep Linking »</a></li>
</ul>
<p>If a <em>single-chat invoice</em> is sent to the chat with <code>@merchantbot</code>, it can only be paid <strong>once</strong>. If a <em>single-chat invoice</em> is sent to any other chat, it can be paid <strong>many times</strong> by many users.</p>
<blockquote>
<p>To get a better understanding of how this works, try toggling the <em>“Pay from Forwards”</em> parameter when creating invoices with our demo <ahref="https://t.me/shopbot">@ShopBot</a>.</p>
</blockquote>
<p>Regardless of whether or not the <strong>Pay</strong> button is available in an invoice, the merchant bot always has the power to decide whether or not to accept new payments for a particular invoice.</p>
<p>If the <em>max_tip_amount</em> parameter is set to above <code>0</code>, users can add a tip to their payment. You can use the parameter <em>suggested_tip_amounts</em> to suggest particular amounts that you feel will be relevant for the invoice.</p>
<h4><aclass="anchor"name="4-shipping-info-and-other-details-optional-step"href="#4-shipping-info-and-other-details-optional-step"><iclass="anchor-icon"></i></a>4. Shipping info and other details (optional step)</h4>
<p> 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.</p>
<h4><aclass="anchor"name="5-offer-delivery-options-based-on-shipping-address-optional-step"href="#5-offer-delivery-options-based-on-shipping-address-optional-step"><iclass="anchor-icon"></i></a>5. Offer delivery options based on shipping address (optional step)</h4>
<p>If a shipping address was requested and you included the parameter <em>is_flexible</em>, the Bot API will send an <ahref="/bots/api#update">Update</a> with a <em>shipping_query</em> field to the bot. The bot must respond using <ahref="/bots/api#answershippingquery">answerShippingQuery</a> 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).</p>
<p><strong>Tip:</strong> It is recommended that the merchant bot confirms availability of the goods/services at this step – to let the user know in case they are no longer available. This is especially important if you are using <ahref="#2-choose-forwarding-behavior">multi-chat</a>, <ahref="#2-choose-forwarding-behavior">inline</a> or <ahref="#2-choose-forwarding-behavior">single-chat, multi-use</a> invoices.</p>
<p>The user enters their payment information and presses the final pay button. At this moment the Bot API sends an <ahref="/bots/api#update">Update</a> with the field <em>pre_checkout_query</em> to the bot that contains all the available information about the order. Your bot must reply using <ahref="/bots/api#answerprecheckoutquery">answerPrecheckoutQuery</a> within <strong>10 seconds</strong> after receiving this update or the transaction is canceled.</p>
<p>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. <em>"Sorry, we're all out of rubber ducks! Would you be interested in a cast iron bear instead?"</em>). Telegram will display this reason to the user.</p>
<blockquote>
<p><strong>Warning:</strong> As of <ahref="#introducing-payments-2-0">Payments 2.0</a>, it is critical to make sure your bot <strong>only</strong> accepts multiple payments when the order can be processed correctly. This is especially important if you are using <ahref="#2-choose-forwarding-behavior">multi-chat</a>, <ahref="#2-choose-forwarding-behavior">inline</a> or <ahref="#2-choose-forwarding-behavior">single-chat, multi-use</a> invoices.</p>
<p>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 <ahref="/bots/api#message"><em>successful_payment</em></a> from the user. Once your bot receives this message, it should proceed with delivering the goods or services purchased by the user.</p>
<p>If the invoice message was sent in the chat with <code>@merchantbot</code>, it becomes a Receipt in the UI for the user — they can open this receipt at any time and see all the details of the transaction:</p>
<p>If the message was sent to any other chat, the <strong>Pay button</strong> remains and can be used again. It is up to the merchant bot whether to actually accept multiple payments.</p>
<p>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 <code>@merchantbot</code>> Bot Settings / Payments and enable Stripe LIVE MODE. You will get a token that has the string <code>:LIVE:</code> in the middle, e.g. <code>123:LIVE:XXXX</code>. Do not give this token to any third parties!</p>
<p>Before your merchant bot goes into live mode, please ensure the following:</p>
<li>We highly recommend turning on <ahref="https://telegram.org/faq#q-how-does-2-step-verification-work">2-step verification</a> for the Telegram account that controls your bot. </li>
<li>You as the bot owner have <strong>full responsibility</strong> in case any conflicts or disputes arise. You must be prepared to correctly process disputes and chargebacks (in the case of Stripe, see <ahref="https://stripe.com/docs/disputes">here</a> and <ahref="https://stripe.com/docs/disputes/faq">here</a>).</li>
<li>To prevent any misunderstandings and possible legal issues, make sure your bot can respond to a /terms command (or offers a similarly easy way of accessing your Terms and Conditions). Your Terms and Conditions should be written in a clear way and easy to understand for your users. The users must confirm that they have read and agree to your terms before they make the purchase.</li>
<li>Your bot must provide support for its customers, either by responding to a /support command or by some other clearly communicated means. Users must have a clear way of contacting you about their purchases and you must process their support requests in a timely fashion. You must notify your users that Telegram support or <ahref="https://t.me/botsupport">bot support</a> will not able to help them with purchases made via your bot.</li>
<li>Make sure that your server hardware and software is stable. Use backups to make sure that you don't lose data about your users' payments.</li>
<li>Make sure that you have completed the live checklist for your selected <strong>payments provider</strong> as well as this one. </li>
<h4><aclass="anchor"name="how-do-i-join-as-a-payment-provider"href="#how-do-i-join-as-a-payment-provider"><iclass="anchor-icon"></i></a>How do I join as a payment provider?</h4>
<p>If you work for a company that provides services similar to standalone accounts in <ahref="https://stripe.com/connect">Stripe Connect</a>, please let us know via <ahref="https://t.me/botsupport">@BotSupport</a> (kindly include the hashtag <code>#paymentsprovider</code> in your message).</p>
<h4><aclass="anchor"name="how-much-do-you-charge"href="#how-much-do-you-charge"><iclass="anchor-icon"></i></a>How much do you charge?</h4>
<p>Telegram does <strong>not</strong> 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 <ahref="https://stripe.com/pricing">Stripe website</a> for more details on pricing).</p>
<h4><aclass="anchor"name="do-i-need-a-bot-to-accept-payments"href="#do-i-need-a-bot-to-accept-payments"><iclass="anchor-icon"></i></a>Do I need a bot to accept payments?</h4>
<p>Yes. If you are not a developer, you will need to either hire someone to make a bot for you (recommended), or use a bot created by a third-party company. We advise extreme caution when using services of bots that process payments for you – Telegram doesn't maintain any such bots and doesn't endorse any of the third-party bots offering these services.</p>
<h4><aclass="anchor"name="what-can-my-bot-sell"href="#what-can-my-bot-sell"><iclass="anchor-icon"></i></a>What can my bot sell?</h4>
<p>Telegram does not impose any limits on what products or services your bot can offer. But please note that you <strong>must</strong> comply with the rules of the payments provider you choose in our system. E.g., Stripe has a special page for <ahref="https://stripe.com/us/prohibited-businesses">prohibited businesses</a>– you may want to consult that one before you start selling harvested organs.</p>
<p><strong>Special Note:</strong> Due to Apple's limitations, bot developers are currently not allowed to accept payments for digital goods and virtual services from <strong>iOS users</strong>.</p>
<h4><aclass="anchor"name="how-are-disputes-handled"href="#how-are-disputes-handled"><iclass="anchor-icon"></i></a>How are disputes handled?</h4>
<p>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.</p>
<p>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.</p>
<h4><aclass="anchor"name="how-do-i-support-payments-in-my-third-party-app-that-uses-the-te"href="#how-do-i-support-payments-in-my-third-party-app-that-uses-the-te"><iclass="anchor-icon"></i></a>How do I support payments in my third-party app that uses the Telegram API?</h4>
<p>You are welcome to study the <ahref="/api/payments">MTProto payment documentation</a>.</p>
<p>Telegram payments currently support the currencies listed below (here's a <ahref="https://core.telegram.org/bots/payments/currencies.json">JSON version</a> in case you need it).</p>
<p>If you're using Stripe as the payments provider, supported currencies may vary depending on the country you have specified in your Stripe account (<ahref="https://support.stripe.com/questions/which-currencies-does-stripe-support">more info</a>).</p>
<p>The minimum and maximum amounts for each of the currencies roughly correspond to the limit of <code>US$ 1-10000</code>. The amount must be expressed in 12 digits or less, so the maximum value will be correspondingly lower for some lower-value currencies. 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).</p>
