The order of a deal: what is done, and in what order

The conditions of a transfer are collected on the neighbouring page — each with a link to the Telegram document and a check date. Here they are put in order: what comes earlier, what comes later, and where the deal stops.

The order of the steps is our conclusion from the platform's conditions, not a Telegram document. The conditions themselves are the platform's, and they are quoted verbatim. The conclusion is simple: a condition that is checked before the transfer has to be met before the transfer, or the button will not work.

There is no money side here. No commissions, no sums, no settlement procedure: those are the terms of a particular deal, not a fact about the platform.

What has to be decided before anything else

The object determines the whole order that follows, and the conditions differ from object to object. So the first question is not «when» but «what exactly».

what is being transferred, and how the cases differ
object	what the platform says
a bot	the procedure is described outright: `/mybots` → the bot → «transfer ownership»
a channel, a supergroup	the procedure is described in the protocol documentation; there are five conditions, all checked in advance
an ordinary group	only the capability itself is named, without a procedure or conditions

Preparation: not less than 24 hours

For a channel and a supergroup two conditions are measured in time, and both are counted backwards from the moment of transfer.

Two-factor authentication is on. Verbatim: «PASSWORD_MISSING: You must enable 2FA before executing this operation».
The password was set at least 24 hours ago. Verbatim: «PASSWORD_TOO_FRESH_%d: The password was modified less than 24 hours ago».
The current session was signed in at least 24 hours ago. Verbatim: «SESSION_TOO_FRESH_%d: This session was created less than 24 hours ago».

From which follows the thing both sides should know in advance: the deal cannot be done on the spot. If two-factor authentication is being turned on for the sake of this deal, at least 24 hours pass between the decision and the transfer. That is not our requirement on the parties; it is the platform's own waiting period.

What is checked before the start

None of these conditions is checked «along the way»: either they are met in advance, or the transfer does not go through.

the condition, who meets it, and what happens if it is not met
condition	who	if not met
the recipient has written to the bot at least once	the recipient	the bot cannot be transferred at all
two-factor authentication is on	the sender	«You must enable 2FA before executing this operation»
the password is older than 24 hours	the sender	«The password was modified less than 24 hours ago»
the session is older than 24 hours	the sender	«This session was created less than 24 hours ago»
the parties are mutual contacts	both	«The provided user is not a mutual contact»
the sender is an administrator of the chat	the sender	«You must be an admin in this chat to do this»

The mutual-contact condition is met by both sides: each has to add the other. Adding in one direction is not enough — the platform uses the word «mutual».

The order of the steps

The order is ours, the conditions are the platform's. It is arranged so that each condition is met before it is needed.

The parties agree which object exactly is being transferred. A bot, a channel, a supergroup and an ordinary group are four different cases with different conditions.
The recipient writes to the bot — if a bot is being transferred. Without this step the transfer will not go through: «You can only transfer a bot to users who have interacted with it at least once».
The parties add each other to their contacts — if a channel or a supergroup is being transferred.
The sender turns on two-factor authentication, if it was not on, and waits 24 hours. The same period applies to the session from which the transfer will be made.
The parties check that every condition is met. There are six of them, they are listed above, and all can be checked in advance.
The transfer. For a bot — /mybots, select the bot, «transfer ownership». For a channel and a supergroup — transferring ownership in the app.
It cannot be undone. About a bot the platform says it plainly: «The transfer is permanent». For a channel, no way of undoing it is described in the documents read either.

Where the deal stops

Three places where everything stops not by the parties' will but by the platform's rule. Worth knowing before, not after.

The recipient has not written to the bot. Transferring the bot is unavailable until that happens. One message fixes it — but only the recipient can send it.

The parties are not mutual contacts. It is enough for one side not to have added the other, and the channel cannot be transferred.

The 24 hours have not passed. Neither the password nor the session matures any faster, and the platform names no way of shortening that period.

What happens after the transfer

One thing, and the platform states it verbatim about a bot: «Transferring ownership will give full control of the bot to another user – they will be able to access the bot's messages and even delete it.» Our translation: transferring ownership gives another user full control of the bot — they will be able to read the bot's messages and even delete it.

That is, after step 6 the former owner loses access and the new one gets everything, including the right to delete the object.

What this page does not say

What it costs and how the money is counted. Those are the terms of a deal, not a fact about the platform.
Whether it is safe. We give the platform's rules; everyone assesses the risk for themselves.
How to get around a condition. Two-factor authentication, the waiting periods and mutual contact are Telegram's requirements; we show them, we do not get around them.
What to do in a dispute. Whether Telegram has any procedure for resolving disputes over a transferred object we have not checked — and unchecked is not the same as absent, and we will not pass one off as the other.
What applies on other platforms. Many forbid transferring accounts outright: Ppomppu, for instance, forbids both agency work and renting accounts. This page is about Telegram and cancels no one else's prohibitions.

On method. Every condition on this page is taken from the eleven database records about transferring rights in Telegram — each with a link to the platform's document and a check date. The order of the steps is derived from those conditions and is called our conclusion where it is ours. Nothing has been added from memory: what is not in the database is not here either.