Codes before campaigns
A queue priority from 1 to 10 per account lets OTP traffic leave before marketing when a route is busy.
OTP and transactional SMS
An OTP SMS gateway that sends codes first
Verification codes are worth nothing if they arrive late. Auvia puts OTP traffic ahead of bulk sends, reroutes when a supplier fails and shows what happened to every code.
Priority 1–10 per accountReroute on errorMax 6 sendsSigned receipts
One message, end to end
RequestReceipt
The acknowledgement is sent only after the message is stored. Retransmitted parts are neither sent nor billed twice.
Built for codes
What keeps verification codes fast and traceable
Bursts wait, they do not fail
Outbound pacing per supplier trunk queues a burst instead of rejecting it with a throttling error.
Reroute on supplier errors
Each supplier error code maps to retransmit, reroute or close, with at most 6 sends per message.
Check the number first
HLR/MNP lookup can route on the real operator and stop numbers that do not exist before you pay a supplier.
One code, one send
Duplicate suppression and 24-hour idempotency keys on the HTTP API prevent accidental double sends.
Proof for every code
Delivery receipts over SMPP or signed webhooks, and pipeline timings in the Message Debugger.
FAQ
OTP questions
How does Auvia send OTP traffic before marketing?
Each account has a queue priority from 1 to 10. When a supplier route is busy, higher-priority messages leave first, so verification codes are not stuck behind a campaign.
What happens when the supplier fails an OTP?
Supplier error codes go through the error-code registry: the message is retransmitted, rerouted to another route or supplier, or closed. At most 6 sends per message.
Can the same code be sent twice by mistake?
Duplicate suppression can reject an identical message to the same number that was already accepted, and the HTTP API accepts an Idempotency-Key valid for 24 hours.
How do I know an OTP was delivered?
Every message gets a delivery receipt over SMPP or a signed webhook over HTTP, and the Message Debugger shows each step with its time.
Keep exploring
