A domain-bound one-time code text puts your website's domain and the code on its own final line, in the form @example.com #123456. The phone only offers that code to a page on that domain, so a lookalike phishing page can't pick it up. Everything above that line is plain text for the human.

That last line is the whole trick. It turns a text from "a number someone might type into the wrong site" into a code tied to the place that asked for it. The format is supported by Apple platforms and by the Web OTP API in Chrome on Android. Support varies by version, so treat autofill as a bonus and keep manual entry.

The template

123456 is your Example code. It expires in 10 minutes. Don't share it.

@example.com #123456

Rules for the line:

  1. It's the last line, with nothing after it.
  2. It starts with @, then the domain, a space, #, then the code.
  3. The domain must match the page that's asking, which for a subdomain means using the exact host you serve the form from.
  4. The code in the line matches the code in the sentence above.

Wording above the line

  • Lead with the code, so it shows in a lock-screen preview.
  • Name your product, because a nameless code text looks like fraud.
  • State the lifetime. Ten minutes is common; shorter is safer.
  • Add a don't-share line. Social engineering is the main way codes are stolen.
  • Skip links and emoji. Both can move a text from one segment to several and invite filtering.

Segment math

At about 120 characters, the example above is one GSM-7 segment, so it costs $0.0075 plus the $0.0045 carrier fee. Add a single emoji and the text switches to Unicode, with a 70-character limit, so the same message becomes two segments. Ready swaps curly quotes and long dashes for plain ones before sending, so those don't change the count.

What the format doesn't do

It doesn't make a code text safe against SIM swaps, and it doesn't stop a person who reads the code to a scammer over the phone. It also doesn't fix delivery. For that, see the notes on SMS OTP and verification sending and pumping fraud protection. For the input side, read SMS code autofill on Android and iOS.

Frequently asked questions

Do I need a separate sender for codes? It helps. Keep verification traffic on its own registered campaign so marketing problems don't slow codes.

Can I localize the text? Yes. Keep the final line exactly as is, in ASCII, and translate only what's above it. If translations use non-GSM characters, expect more segments.

What if my login is in a native app only? Use the platform's own autofill route for that app. The domain-bound line is for the web.

Next step

Write your template, send it to a test phone on iOS and Android, and open your login page to confirm the prompt appears. Then add the template to your sending code so no one edits it by accident.

Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.