Payments & POS: A2P SMS and mobile data

Terminal profiles tested against the acquirer host.

Unicom Americas – Mobile Business team

In figures

Terminal estates depend on first-transaction success; profiles are tested against the acquirer's host before rollout, not after.
ISO 8583 frames an authorization as a message type such as an 0100 request and an 0110 response, with a system trace audit number and a retrieval reference number that make a retry safe.
A terminal that loses its link mid-transaction must either store and forward or reverse cleanly; a blind resend is how a customer gets charged twice.
EMV and PCI DSS shape the terminal, not the SIM: the mobile network carries encrypted traffic to the acquirer host, and the acquirer's certification decides what may connect.
2G and 3G sunsets force terminal refreshes, so the module's bands and the operator's retirement date belong in the purchase decision, not in the deployment plan.

This page is not legal advice.

Scenarios

SmartPOS and mPOS

Countertop and mobile terminals for acquirers and terminal fleets, with authorization traffic prioritized over everything else on the profile. An mPOS reader paired to a phone and a SmartPOS with its own SIM are different designs: the first borrows the phone's link and inherits its coverage, the second needs a profile that comes up when the shop opens. Both care about the same moment, the customer standing at the counter. Keep firmware, logs and app updates off the authorization path, and cap the time a terminal may wait before it offers the offline floor limit.

Unattended vending and cabinets

Vending machines and power-bank cabinets report stock, cash and health on narrow, always-on links. The traffic is small but the failure is visible: a cabinet that cannot authorize a rental is a cabinet that earns nothing. Vendors often speak a telemetry standard such as EVA-DTS alongside their own protocol, and the gateway or the terminal has to bridge it to the operator's platform. Design for the site, not the device: a machine in a basement needs a different antenna and a longer reconnect budget than one beside a window.

Kiosks and digital signage

Self-service kiosks and signage with payment modules, managed as one estate with remote profile control. A kiosk is a small computer with a screen, a payment module and sometimes a camera, so its traffic is software updates and playback rather than transactions. Keep the payment module on its own profile or its own APN where the acquirer requires it, and schedule content downloads outside trading hours. A signage screen that reboots into an empty page after a link drop is a support call; cache the last playlist locally and make the player tolerate a missing network.

The link to the acquirer host

Most terminal connectivity is an outbound, encrypted session to a host that the acquirer controls. The terminal initiates, the host answers, and no inbound port is opened on the terminal. Where the acquirer requires a fixed source address, the private APN provides it; where it requires an IPsec tunnel, the router or the terminal terminates it. Keepalives hold the session across NAT, and the reconnect backoff should be short at first and then lengthen, so a host outage does not produce a reconnect storm from thousands of terminals at once.

Fleet operations and replacement

A terminal estate is replaced slowly and unevenly: some units are five years old, some arrived last month, and the estate inventory is usually wrong. Record the ICCID, IMEI and terminal serial against the merchant and the site, so a replacement can be matched to the unit it replaces. Use remote profile management where the hardware supports it, stage firmware by cohort, and keep one spare per region rather than one per merchant. A recall that depends on a spreadsheet of unknown age is the failure mode to design against.

Who buys this

Authorization traffic on private APNs with a defined source range.
Estate health beside transaction data, so a silent terminal shows up.
A replacement path that does not require a site visit.

Data reality

Indicative device profiles compiled from public research. Confirm the profile for your hardware at quote time.

Profile	MB/mo	RAT	SIM
Fixed POS or mPOS terminal	20–80	Cat-1 bis	multi-IMSI, SGP.32, local profile
Android SmartPOS	100–500	Cat-4	multi-IMSI, SGP.32, local profile
Kiosk, vending machine or power-bank cabinet	10–1000	Cat-1, Cat-4	multi-IMSI
Digital signage	1000–20000	Cat-4	data SIM

Device admission

Terminals name their acquirer and markets at quote time.
Estates with fixed-address requirements name the range and the tunnel type.
Legacy 2G or 3G units name the refresh date before a plan is proposed.

RAT

Bearer	Note
LTE Cat-1 and Cat-M1	Authorization and telemetry default; Cat-M1 where the operator has deployed it.
LTE Cat-4	Android SmartPOS and kiosks with content downloads.
2G fallback	Legacy terminals only, where still in service; check the sunset tracker.

Product bundle

Wholesale data & eSIM

Wholesale mobile data, eSIM & IoT SIMs

Authorization-grade data profiles with private APNs into the acquirer, plus per-terminal reporting; see mobile data and eSIM. Estate-wide eSIM control for terminal fleets across markets, with a replacement profile ready before a unit is swapped.

Learn more

FAQ

Do you handle the acquirer certification?

No. Certification stays between you and the acquirer; we carry the authorized traffic on tested profiles. What we can do is test the path end to end before rollout, so the first real transaction is not the test.

How are vending cabinets connected?

On narrow always-on links reporting stock and health; payment modules ride the same profile. Where the machine speaks its own telemetry protocol, a gateway bridges it to the operator platform.

What about ATM or amusement machines?

ATMs are scoped case by case; amusement and gaming terminals are outside this page. Both carry obligations beyond connectivity, and the operator's own certification comes first.

What happens when the link drops mid-transaction?

The terminal either completes against its offline floor limit or reverses cleanly, depending on the acquirer's rules. The dangerous path is the blind retry: the same authorization sent twice because the first response never arrived.

Does a terminal need a static IP address?

Usually not. The terminal opens an outbound session to the host, which works behind NAT. A fixed source address or an allow-listed range is a requirement of some acquirers, and the private APN is where it is provided.

Wholesale mobile data, eSIM & IoT SIMs

Payments & POS: A2P SMS and mobile data

In figures