When buying a payment-enabled Telegram bot, separately establish who supplies the product and receives new payments after handover. Bot ownership does not automatically transfer a merchant account, provider agreement or legacy payment obligations. Identify the product class, permitted payment mechanism and provider requirements before switching configuration. Use safe tests and allocate responsibility for old orders. A functioning payment button does not establish a permitted route or receipt by the buyer.
Identify the product and entity responsible for supplying it. Digital access, physical goods and services can involve different platform conditions. Telegram publishes separate guidance for physical and digital products, including Stars for the digital model. Apply current guidance to the actual offering rather than assume the old integration remains appropriate.
Map the chain from customer to order, payment mechanism, recipient, delivery and refund. Where an external provider participates, establish whether the existing agreement can move or a new arrangement is needed. Copying seller credentials is not a substitute for properly establishing the buyer's merchant position.
Review legacy orders separately. Redirecting new payments does not determine who handles an earlier refund, dispute or unfulfilled service. Those records may retain their original references and route. The buyer needs to understand that outstanding population before accepting final delivery of the project.
For each product category, record the payment mechanism, present supplier, future supplier, recipient of new proceeds and owner of legacy cases. Add the cutover date and confirming source. If account-transfer eligibility is unknown, keep the row open even where logging into the old account is technically possible.
Record the fulfilment trigger in another row. Identify which verified event allows the bot to supply a product or grant access. A customer's message saying paid should not become provider confirmation on its own. Acceptance checks the relationship between the event and the actual order, not merely the existence of an event handler.
Keep secrets outside the matrix. Reference the configuration and its owner without collecting working credentials, card data or unnecessary customer records in a general handover file. Where investigation needs actual records, establish authority and proportionate disclosure rather than copying a production database indiscriminately.
In an illustrative example, order A is created before cutover using the previous recipient, while order B is created afterwards under the new route. Equal prices do not make their provider references or refund responsibilities identical. Preserve that distinction instead of displaying only one daily turnover figure.
If an old invoice can still be paid later, define its handling through a supported mechanism. Changing a configuration key does not prove that every previously created payment object has become new. Examine the actual behaviour and route documentation. The transition needs a defined boundary and reconciliation method.
Useful recipient evidence connects order configuration, payment confirmation and accounting of that operation. A screenshot from the seller's interface does not replace the buyer's own verification. Conversely, a missing immediate bank credit may reflect the provider's processing cycle rather than misrouting. Check the applicable reports and timing before concluding which event failed.
Pause acceptance if the new recipient is unconfirmed, the plan requires permanent use of the seller's personal merchant identity or the product class is incompatible with the chosen mechanism. Do not fabricate product descriptions to evade platform rules. A successful technical test does not make an otherwise unsupported model permissible.
Needing a new connection does not necessarily make the bot worthless. It may require a separately priced migration stage and revised timetable. Record that dependency as an open deliverable instead of hiding it behind a promise that payments can be enabled later.
If new receipts route to the previous merchant, pause new activity through the supported process and inspect configuration. If payment confirmation exists but delivery does not, match order and event before charging again. For an old-order refund request, use the agreed legacy route and preserve the responsible party link.
Do not restore every former credential simultaneously during a failure. Follow the targeted recovery plan and retain evidence. Seller assistance should have a defined purpose and expiry. Repeating the bot ownership action does not automatically repair a problem in a merchant agreement.
Use the general transaction-stage outline to distinguish bot control from acceptance of the new-payment route. Each result needs its own evidence and authorised reviewer.