Nexa SMS — frequently asked questions

Nexa SMS is a carrier-partnership SMS panel. Partners connect numbers or an API endpoint, receive inbound OTP and verification messages in real time, and are paid a per-message share that settles through the dashboard — most often the same day it is requested.

Partner cards currently run from $0.0122 to $0.0254 per received, billable SMS depending on the destination tier. Accounts sustaining 50,000+ messages a day move to the VIP card, which adds a further 22% on top. Use the payout estimator on this page for a realistic figure.

Your balance updates as each message is billed, not at the end of a cycle. Withdrawals go out in USDT (TRC20 or ERC20), by bank wire or through a regional rail; requests placed before 18:00 UTC are normally paid the same working day. The minimum payout is $50.

Yes — a plain HTTP/JSON REST API with signed HMAC webhooks. A sandbox key is issued alongside your credentials so you can integrate before your first live message.

More than 190 destinations, with the deepest coverage across the UK, EEA, GCC, North America and South Asia, and growing capacity in West Africa and LATAM. If a route is missing, our carrier desk will usually source it within 48 hours.

Most applications are reviewed the same working day. Once approved, your panel login, API key and API key are sent to your email and WhatsApp at the same time.

No. There is no minimum commitment and no contract lock-in. Solo agents running a few hundred messages a day use the same panel and the same rate card as teams running six figures — volume only changes which tier you sit on, not whether you are accepted.

It is a free public tool on this site. Choose a 30-minute or 24-hour window, optionally filter by sender ID or by text inside the message body, and see which senders are currently landing, with the destination country and receive time. Recipient numbers are always masked in the public feed; approved partners see their own complete traffic inside the panel.

Every message passes automated screening for spoofed sender IDs, duplicate submissions and grey routing before it is billed. Traffic that fails screening is not billable. The screening protects route reputation, which is what keeps your rate stable over time.

USDT on TRC20 or ERC20, international bank wire, and several regional payment rails. You choose your default method during onboarding and can change it at any time from the panel.

Yes. The panel exports a per-message statement for any date range in CSV, so you can reconcile independently rather than relying on a summary figure.

Yes. Nothing stops you keeping your existing setup live while you test ours — most partners run both side by side for a week, compare the numbers, then move the traffic across once they are satisfied.

The gateway runs across redundant nodes with automatic failover, and monitoring is independent of the gateway itself. If a route degrades, affected partners are notified on the WhatsApp and Teams channels before most of them notice it in their own dashboards.

Email, Microsoft Teams and WhatsApp are all staffed 24/7, and there is a contact form on the site. Written matters — contracts, statements, disputes — are best sent by email so there is a record.