What it is
Payment by QR code or link from a phone through the bank, without a card and with a low merchant fee. Suited to subscriptions and one-off payments in bots.
How we use it
Our subscription-sales bot accepts SBP payments, extends access by itself and keeps the books, with no manual reconciliation.
What it is for
SBP is Russia's instant bank-transfer system: a customer pays from their banking app by phone number or QR code. It matters for businesses selling to customers in Russia; for clients abroad the relevant part of this page is the approach to manual payment confirmation in a bot.
- You sell a subscription or access through a bot, and setting up card acquiring is slow or premature.
- Customers pay by bank transfer, and access should be extended right after the payment is checked.
- Several admins can approve payments, and one payment must never be credited twice.
How we use it
- Subscription-sales bot. The customer picks a plan, the bot shows the payment details and a bank link, the customer pays and sends a receipt screenshot. The receipt goes to every admin with Approve and Deny buttons, and after approval the subscription is extended in the Marzban panel, with bonus days for longer plans.
- Tech Poly VPN. The same flow plus money tracking: confirmation is atomic, the bot reads the payment under a row lock in the database, and a second admin sees who already processed the request and when. If the panel does not answer after payment, the request goes back to pending and the accumulated discount is not burned.
This is a manual check: there is no automatic acquiring in these projects, and a person looks at every payment. We build bots with payments under Telegram and VK bots; connecting a payment system is discussed separately in the audit.
Common problems
- Double confirmation. Two admins press Approve at the same moment, and without a database lock the subscription is extended twice.
- Paid, but no key. The payment is confirmed, but the external system did not answer. The request must roll back to pending, or the customer is left with a payment and no access.
- Payment details in the code. They are better moved into environment settings so they can change without a new release; in one of our bots this is still on the to-do list.
- A person is the bottleneck. At night a receipt waits until an admin wakes up. With a large flow of payments you need a payment system with automatic confirmation.
When you do not need it
If there are many payments and customers will not wait for a manual check, you need a payment system with automatic confirmation. And for a one-off order on a website with no subscription, cash on delivery is simpler, as in our online store.