Am I the only one thinking that Telegram has failed

the Bot Payment revolution in the past and now trying to catch up with @wallet, @donate and etc?

If you’re looking for simple donations or single one-euro purchases it’s okay, but if you’re going deeper it’s full of limitations…

So my main concern is that Telegram is not ready to be a platform for US, EU, Indian businesses, mainly due to Tax/VAT obligations and other compliances. There’s a known (?) bug that does not allow to pass contact data to payment provider. Indian entrepreneurs are cut off entirely, the rest continue to be less compliant that they may be and should go with workarounds… which usually leads using provider without Telegram’s layer. The payment provider pool theirselves is limited. For worldwide you’re going with Stripe. Proprietary SmartGlocal does not accept new partnerships, probably due to compliance risks. Other options for Russian businesses (which we all know is on the radar of Telegram) is to use YooKassa, but since it’s an “other” provider, payment form simply opens a web view. Decided to go with other payment provider? Good luck explaining what the Telegram Bot is and probably implementing a website for your bot due to ancient compliance requirements. Talking about other countries, minimum payment of $1 may affect some poor markets with unstable currencies. For example, Native YooKassa solutions allows payment as low as $0.01. So what’s the deal with Telegram Payments? Give half-working native UI and tell “pay without leaving the app”? Help developers who have a challenge to create a payment notification webhook? Glad we have webapps that are being pushed really hard and we can wrap any payment provider page into the web view. Gives IP access to properly count VAT/TAX and supports literally any payment provider. I don’t really know how to solve it. Give more room to customize dataflow between provider and bot developer? Somehow securely share addresses, IPs etc? I just want to be open to my users and build trust around privacy. I usually build products I would use myself.

No you’re not alone You’re right Unfortunately it’s for TON sake I think

Стикер

So, I was able to use Shipping Method as a workaround for dynamic VAT in EU with TEDB. There might be similar solution for US. Unfortunately, it may confuse users and harm UX, since there’s no actual shipping of a physical good and bot developers can’t access billing address -> users need to type 5+ new fields. Posting pictures since videos are not available here.

Стикер