Card payments in retail
POS systems and card terminals that have to keep working, even when the fixed line at the site is down.
IoT and M2M
Connectivity for equipment that cannot wait for an engineer
A POS terminal that cannot take card payments, a sensor that reports nothing, a site without internet: the problem is rarely the SIM card, it is that nobody sees which card went quiet or ended up in a different device. We supply the cards and the management around them in the same portal as everything else.
Multiple networks
Per country, not tied to one operator
Predictable costs
Bundles per group, with caps
Alerting
Outages and silent cards in view
API
Status in your own monitoring
Applications
Where our SIMs are used
Backup internet
A second path at a site, over a different network than the fixed line, that takes over automatically.
Sensors and installations
Meters, charge points, climate and access systems that send little data but have to report reliably.
Vehicles and equipment
Track and trace, on-board computers and equipment that moves across several countries.
What you manage
IoT SIM management: a thousand cards, the same actions
Management works per group instead of per card: a branch, a device type or a project.
Groups and profiles
Bundle cards per site, device type or project, each with its own settings
Activate and block
In bulk, or per card on installation, replacement and disposal
Caps per group
A sensor that suddenly sends gigabytes is capped rather than allowed to run
Outages and silent cards
An alert when a card goes offline or has had no traffic for weeks
Network choice
Multiple networks per country, so a card is not stuck with one coverage footprint
Cut off misuse
If a SIM moves to another device, the IMEI gives it away: blocking or capping can happen automatically
Costs per cost centre
Usage and costs allocated to the branch or project the card belongs to
In your own monitoring
If you already have a NOC, you do not need another portal
Status, usage and events for all cards can be retrieved through the API, and outages arrive as a webhook. That puts the IoT part in the same dashboard as the rest of the infrastructure, while the portal stays available for anyone who does want to use it.
More about the API →- Read card status online, offline, blocked
- Usage per group per period or cost centre
- Apply changes activate, block, replace
- Webhooks outage, threshold, status change
Which equipment is unaccounted for right now?
Tell us how many cards there are and what they sit in, and we will look at what can be managed and capped.