Why we accept crypto

Card processing fees: 2.9% + $0.30 on a $0.004 product destroys margins

A typical credit card processor charges 2.9% + $0.30 per transaction. At $0.004 per SMS, that overhead is catastrophic. If a customer buys $100 worth of credits in a single transaction, the processor takes $3.20. On a $10 top-up, the fee is $0.59—nearly 6% of the purchase. On a $5 top-up, it exceeds 11%. The fee structure assumes high-value transactions; it punishes the low-ticket, high-frequency pattern that characterizes SMS billing.

Some card processors offer tiered or volume-based rates, but all require integration complexity, PCI compliance overhead, and ongoing disputes with the acquirer about transaction categorization. SMS gateways in particular have historically faced higher decline rates and stricter underwriting because card networks classify them as "high-risk" due to fraud and TCPA liability (47 USC § 227, which prohibits unsolicited telemarketing via automated systems). That risk classification translates into higher base rates: often 3.5% to 4.5% instead of the standard 2.9%, plus additional monthly fees for chargeback reserves.

Cryptocurrency transactions, by contrast, cost us a flat network fee regardless of transaction size. Bitcoin network fees fluctuate but typically run $1–5 per transaction. USDT on TRC-20 costs pennies. Ethereum and Solana are similarly cheap. We amortize that cost across all customers—meaning a $5 top-up bears less than $0.01 in processing cost, and a $100 top-up bears the same absolute fee. The math inverts in our favor, and passes directly to you as lower SMS prices.

Chargeback fraud is real on low-ticket SaaS; crypto is finality

Chargeback fraud occurs when a cardholder disputes a legitimate charge, the bank reverses it, and the merchant loses both the product delivered and the payment received. For SMS gateways, the damage is particularly acute: a customer purchases $50 of credits, sends thousands of messages, and then files a chargeback claiming "unauthorized transaction" or "service not rendered." The bank sides with the cardholder by default (they are the customer of the bank, not you). You lose $50 and must eat the cost of the SMS delivery.

Card processors reserve the right to charge back to merchants for any reason. Even if you win the dispute, you've spent hours collecting evidence, uploading logs, and responding to the bank. A single high-volume chargeback can trigger a "chargeback monitoring" flag that forces you to maintain a chargeback reserve—often 5% to 10% of monthly processing volume, locked up in a reserve account for 6–12 months. One customer making 50 fraudulent $1 purchases can tank your entire reserve threshold.

Blockchain transactions are irreversible. Once confirmed, they cannot be reversed, chargedback, or disputed by a third party. This is not a feature we exploit; it is a security property that eliminates an entire category of fraud. A customer can dispute the quality of service, ask for a refund, or request a credit—and we handle those requests professionally—but they cannot fraudulently reverse payment after services are rendered. This finality allows us to operate without chargeback reserves, dispute workflows, or the overhead of chargeback insurance.

SEPA doesn't work for developers in 100+ countries

SEPA (Single Euro Payments Area) is free to process and carries no fraud risk because transfers are adult-to-adult, not merchant-to-cardholder. However, SEPA only works within the eurozone and a handful of associated countries. If you operate a development team in Indonesia, a startup in Nigeria, or a freelancer in India, SEPA is not an option. You would need to wire funds via SWIFT, which costs $30–50 per transfer, takes 3–7 days, and often requires a local bank relationship that small businesses and international teams do not have.

smsroute serves 149 countries. Our customers include developers in Southeast Asia, Eastern Europe, Latin America, the Middle East, and Africa. A billing system that only accepts SEPA would exclude the majority of our user base. Cryptocurrency, by contrast, works identically in every country where internet access exists. A developer in Mexico, Turkey, or Vietnam can transfer Bitcoin or USDT (TRC-20) with the same ease as a developer in Germany. No bank account required, no currency conversion, no 3-day settlement delays.

This is not ideological. It is geographic pragmatism. The traditional finance rails (cards, SEPA, wire) are built for the 1990s Western banking infrastructure. They do not scale to the modern developer workforce, which is distributed globally. Crypto is the only payment method that works equally well in 149 countries without requiring a banking relationship in any of them.

Why not Lightning Network (yet): liquidity constraints and settlement predictability

The Bitcoin Lightning Network is faster and cheaper than on-chain Bitcoin, with sub-cent transaction costs and near-instant settlement. Theoretically, it is ideal for SMS billing. However, Lightning still suffers from two operational constraints that prevent us from deploying it as a primary payment method.

First, liquidity. Lightning requires nodes to maintain channel balances on both sides of a payment path. If a customer wants to send $100 via Lightning and our node lacks sufficient liquidity on their side of the channel, the payment fails. This is solvable at scale (we can open channels with multiple routing nodes, pre-fund them, and rebalance regularly), but it adds operational overhead and requires capital allocation that we have not yet justified against the cost savings of on-chain transactions.

Second, settlement certainty. On-chain transactions (Bitcoin, Ethereum, USDT) confirm at predictable intervals: Bitcoin every 10 minutes, Ethereum every 12 seconds, USDT (TRC-20) every 3 seconds. We know exactly when a customer's balance is final and available for SMS delivery. Lightning channels settle instantly in principle, but they also require us to trust the channel partner's view of channel state. At current volumes, the complexity is not worth the marginal speed gain. We revisit this every quarter.

We do not rule out Lightning in the future. As channel liquidity improves and more wallets support Lightning natively, we may support it as an optional payment method for customers who prefer it. For now, we stick with on-chain transactions and Bitcoin, which offer simplicity, universality, and predictable settlement.

Privacy angle: your payment rail is separate from your message data

When you pay smsroute via cryptocurrency, your payment history is pseudonymous by default. The blockchain records your transaction, but it is keyed to a wallet address, not your name or email. smsroute receives the payment and credits your account, but we do not collect your payment method, billing address, tax ID, or identity verification unless you explicitly choose to provide it.

This is not about hiding from regulators. We comply fully with applicable law: GDPR (Article 4(11) on personal data), PECR (Regulation 22(3) on electronic marketing preferences), TCPA (47 USC § 227 on consent and Do-Not-Call requirements), UWG § 7 (German law on unfair competition), UU 27/2022 (Italian digital regulations), RA 11934 (Philippines cybercrime), and LGPD (Law 13.709/2018 in Brazil). All of these require us to verify consent, respect opt-outs, and maintain audit trails. We do that.

The privacy benefit is separation of concerns. Your payment history is not tied to your SMS content, recipient lists, or delivery logs. A payment processor like Stripe or PayPal collects both: they see what you bought (SMS credits), who you sent messages to (if they subpoena us), and your financial profile. Cryptocurrency decouples the two. We know you sent SMS; we know you have an account; but we do not tie your payment identity to your message identity. This is particularly valuable for journalists, NGOs, political campaigns, and whistleblower networks that use SMS for sensitive coordination.

We take data minimization seriously. We do not retain payment details longer than necessary for accounting and tax compliance. We do not share customer lists with payment processors. We do not build customer profiles for sale. Crypto billing is one architectural choice that reinforces that commitment.

Frequently asked questions

Do you accept stablecoins other than USDT?

We currently support USDT on TRC-20 (Tron) as our primary stablecoin because it offers the fastest settlement, lowest fees, and broadest liquidity across exchanges we use. We evaluate other stablecoins (USDC, BUSD) periodically, but have not integrated them due to network congestion or withdrawal constraints at our processing partners. If you have a specific stablecoin requirement, contact support.

What is the minimum top-up amount?

The minimum top-up is $5 USD equivalent in any supported cryptocurrency (Bitcoin, USDT, Ethereum, Litecoin, Monero, or Solana). At current rates, this typically translates to a small fraction of a coin. Once credited to your account, you can send SMS from $0.004 per message across 149 countries.

Is there KYC (Know Your Customer) required to sign up?

No. smsroute does not require KYC, AML verification, or identity documents at signup. You provide an email, set a password, and begin purchasing SMS credits immediately. This is only possible because we accept crypto and operate without legacy banking rails.

Can I use a credit card or SEPA bank transfer?

No. smsroute accepts cryptocurrency only: Bitcoin, USDT (TRC-20), Ethereum, Litecoin, Monero, and Solana. We do not support credit cards, debit cards, bank wires, SEPA transfers, or PayPal. This constraint is intentional and explained in our billing philosophy.

What happens if I send crypto to the wrong address?

Blockchain transactions are irreversible. If you send funds to an incorrect address, they are lost permanently. Always verify the deposit address shown in your dashboard before sending. We cannot recover misdirected funds. Copy-paste the address directly from the smsroute UI to avoid manual entry errors.

How long does a crypto deposit take to credit my account?

Deposit confirmation depends on network conditions and the blockchain used. Bitcoin typically confirms within 10–30 minutes; USDT (TRC-20) within 1–2 minutes; Ethereum 2–5 minutes. Once we detect the required confirmations (usually 1–3 blocks), credits are applied instantly to your account balance. You can monitor your deposit status in the smsroute dashboard.