ESME

The messaging stack: how an SMS actually gets to a phone

An OTP doesn't jump straight from your server to your customer's screen — it passes through four or five layers. Knowing what each one does is the fastest way to figure out where a delivery problem actually sits.

What is an ESME (External Short Message Entity)?

An ESME is any system outside a mobile operator's network that sends or receives SMS by connecting to an SMSC — a banking app pushing a one-time password, a logistics platform sending delivery updates, or an IVR system collecting survey replies. It's a role, not a product: any outside app sending or receiving SMS counts as one.

Your own backend almost never talks directly to an SMSC — you connect through a platform like Helo's SMS API, and that platform is the ESME on the operator's side.

• Why it matters: you get a simple REST endpoint; the SMPP handshake underneath is your provider's job, not yours.
• Often confused with: the SMSC — an ESME sends into an SMSC, it doesn't run one.

What is SMPP (Short Message Peer-to-Peer)?

SMPP is the open, TCP/IP-based protocol that lets an ESME and an SMSC exchange SMS at volume thousands of messages per second over one persistent connection, instead of one text at a time like a phone. First published in 1997, it was revised in 1999 (v3.4, still what most production traffic runs on) and finalized in 2003 (v5).

• Why it matters: when a vendor talks about "throughput," "TPS" (transactions per second), or "transceiver binds," they're describing their SMPP configuration — and that configuration caps how fast your OTPs go out during a payment spike or flash sale.
• Often confused with: an SMS gateway. SMPP is the protocol; a gateway is the system that speaks it on your behalf.