I built an OTP-number router because failed SMS activations were eating my money

Hey IH! I want to share a tool I just shipped publicly: LumenOTP, a virtual-number platform for one-time SMS verification.

The problem I kept hitting: every time I needed to verify an account — testing signup flows, onboarding new tools, QA work I'd buy a number from an SMS provider, and a decent chunk of those activations just failed. The code never arrived, and the provider kept the money. Multiply that by dozens of attempts and it gets annoying fast.

So I stopped buying numbers one at a time and built a router instead.

How LumenOTP works:

1. You request a number for the app/service you need.

2. LumenOTP routes that request across multiple providers and picks the best available one.

3. If a number fails to receive the code, it automatically retries with the next provider.

4. If the activation ends up canceled or failed, you get an automatic refund — you never have to file a claim.

What else is in the box:

• Built-in wallet: top up once, pay per activation, transparent pricing. No subscriptions.

• Telegram client: request, receive, and refund numbers without leaving your chat. The web dashboard covers everything else.

• Coverage: numbers for popular apps and services across a long list of countries.

• Multi-account friendly: it started as an internal QA tool, so batch workflows were a day-one requirement.

On the roadmap: USD and crypto payment options, plus a public API for automated workflows.

The honest numbers so far: this was an internal tool for months before it became a product, so the "launch" is really about polishing, documentation, and getting feedback from people who aren't me. I'm particularly interested in:

• Which apps/services you'd want covered first?

• Do you prefer managing this from a web dashboard, Telegram, or an API?

Product page: indiehackers.com/product/lumenotp

Site: lumenotp.com

Happy to answer anything about the routing logic or the refund system in the comments.