Why Telegram asks for an SMS fee when you sign in

First, work out which screen you are on

Three different things wear the same two words. Reading which one is in front of you takes ten seconds and decides everything after it.

Why an app that is free asks for money at the door

The code you usually wait for is an SMS. An SMS is the part of a login that Telegram pays for on every message. Most of that cost is invisible because it is small. In some country and operator combinations it is not small at all.

The official documentation states the rule plainly, and it is worth reading the wording rather than a summary of it:

Two details in that same structure matter more than the sentence. The offer carries a subscription length, a currency and an amount, all set by Telegram at that moment. That is why nobody can quote you a figure in advance. It also carries a support address and a subject line. Being able to write to a human is part of how the gate is meant to work.

What the documentation does not publish is the list. Which countries and operators meet the threshold is not published. Neither is how often the condition is re-evaluated, or whether a number that qualified last month still does. Treat any table of "affected countries" you find, including a confident one, as somebody’s recollection.

What you still control decides what happens next

Read down the left column until a line describes you, then read across. Each row is a different amount of access. Each has its own official next step, and its own limit on what that step can achieve.

What Telegram can send instead of an SMS

The code is not always an SMS, and that is documented rather than observed by luck. When a client asks for a code, the server answers with a delivery type, and the type is chosen on its side. Not every type costs the same, which is the whole point of the list below.

Email is the route that surprises people most, because it is offered to accounts that have no email attached yet. In that case the client asks the reader to confirm an address first, and the code then arrives there. It is also the route that needs no working SIM, and it needs nothing beyond a mailbox the reader can still open. Whether it is offered at all is still the server’s decision, and no setting in the app changes that.

Both images on this page are reconstructions, and that is a deliberate limit. A real SMS-fee screen was not reproduced for this article, so nothing here is presented as a capture of a particular version.

The documented types are a menu the server chooses from. None of them is a setting the reader can switch on, and the client cannot ask for a specific one. That is the whole reason this page is organised around access rather than around instructions.

• A code inside Telegram on a device that is already signed in.
• An SMS to the number the account uses.
• A call that speaks the digits, where the number can receive one.
• A flash call: the phone rings once and the call is dropped, and the application reads the number of the caller as the code.
• A code by email, after the address is confirmed inside the client.

Android, iPhone and a computer: the differences that exist

There is no verified difference between platforms in when the fee appears. The decision is made by the server from the number and its operator, so the same account meets the same gate on every device it is opened on. What differs is where each client puts the controls around it.

iPhone and iPad

A passkey is set up and reviewed from Settings, then Privacy and Security, then Passkeys, and the same path exists on the other platforms. The English search phrase "sms fee skip iphone" suggests an iPhone-only workaround; none is documented, and the gate does not read your model of phone.

Android

The same holds for the Android variant of that phrase. A sideloaded build is not a route either. The payment flow is described as usable only by official clients. A modified client is therefore at best ignored at this step, and at worst a way to hand your session to somebody else.

A computer

Desktop and web clients also offer a QR sign-in, and that route sends no SMS at all. That is why "just sign in on the computer" circulates as a workaround. It is not one for a new account. A QR login is completed by an already signed-in app that scans and accepts it. It needs the same second device an in-app code needs, and it cannot register anybody.

A real gate and a scam ask for the same thing

The asymmetry is the useful part. A genuine gate is trying to sell a subscription, so it is happy to be ignored. A scam is trying to get into the account, so it cannot afford to be ignored. It will always add urgency, a deadline or a threat of deletion.

If the screen stays, or the payment does not go through

A common hope is that the requirement expires if it is ignored, or that a VPN or an older version avoids it. None of that is documented, and this page will not invent a procedure for it. What is documented is the support address the payment screen itself carries, and that is the channel to use.

1. 1

   Step 1. Write down what the screen says

   The duration, the amount and the currency, plus the support address and the subject the screen names. This is the information a support reply needs, and it is the part people forget by the time they write.

   What you should see: A short note with four figures and one address.

2. 2

   Step 2. Write to that address, from an address you can receive mail at

   Use the subject line the screen specifies. Describe the number in international format and what happened, without sending a code, a password or a screenshot of a session.

   What you should see: A sent message with the exact subject the app asked for.

3. 3

   Step 3. While you wait, keep every route you still have

   Do not sign out of a working device, do not wipe the app, and do not change the number. Each of those removes a way in that the gate has not taken away.

   What you should see: The old session still opens, and the number is unchanged.