Skip to main content

Virgin Mobile eSIM Kiosk Built with Weave

Published: 16/10/2026

Customers know how Virgin Mobile looks and feels from its app. The in-store eSIM kiosk is built so the kiosk feels like that app too — and so the hardware, identity and activation steps behind it work as one service.

Virgin Mobile provides the customer-facing experience; Azimut engineered the middleware and core software behind the kiosk’s digital journey. Customers start at the touchscreen and complete the steps to receive an active eSIM on their phone, without collecting a physical SIM card. The SIM issuance workflow shows how a kiosk brings identity checks, provisioning and activation into one journey.

Virgin Mobile eSIM kiosk in a retail setting

Built with Weave: the app experience, on the kiosk

The Virgin Mobile kiosk is built with Weave, a feature of Azimut SDK that brings an operator’s app experience to self-service kiosks. Weave runs Android, iOS and web apps natively on the kiosk, so customers in store see the same look and journeys they already know, rather than a separate kiosk design that drifts over time.

That matters most for a product like eSIM, where offers and steps change often. When the journey is defined once, the kiosk can follow it instead of waiting for a separate kiosk release.

One JSON API, many device models

Underneath Weave, Azimut SDK sits between the kiosk application and its hardware. The application calls a stable JSON API to request a device operation and receive its outcome. The SDK handles the driver and low-level communication with the attached model, along with device readiness, session lifecycle and health reporting. The hardware runs in a Windows enclave inside the kiosk.

Because the API uses HTTP and JSON, the same contract works from C#, Java, Python, Node.js, or a mobile or web app — see one JSON API for every language. When a deployment introduces another supported model, the device driver can change while the application keeps the same API contract. A model that is new to the catalogue may need a driver added first.

Middleware between the kiosk and the back end

A kiosk journey also has to reach the operator’s systems: product catalogue, identity verification and eSIM provisioning. Azimut middleware sits between the kiosk and those systems and translates each request, whether the system exposes a modern REST API or a legacy SOAP/XML, message-queue or file-based interface. Back-end platforms stay where they are.

Hardware for more than one kind of kiosk

The SDK supports a broad set of device families across self-service projects:

  • Identity and capture: document readers, barcode scanners and biometric scanners.
  • Payments and cash: payment terminals, cash acceptors, cash dispensers and coin devices.
  • Issuance and output: SIM printers, card issuance modules and receipt printers.

A telecom kiosk selects the devices its journey requires. The list describes the SDK’s wider capabilities, not the exact components inside the Virgin Mobile kiosk. Explore the hardware integrations available to application teams.

What this means on the retail floor

For Virgin Mobile’s customers, the kiosk is a familiar, guided eSIM experience. For the teams behind it, Weave keeps the kiosk in step with the app, the SDK keeps the hardware behind one API, and the middleware connects both to the systems required for issuance and activation. For fleet-wide status, diagnostics and staged software releases, Satellite remote device management complements the platform.

See how operators use this on the telecom self-service page, read how Weave works, or talk to our team about your app and the kiosks you want it on.

Try it yourself

Book a demo

See how Azimut SDK works in your self-service environment. We'll walk through your use case, hardware setup, and integration options.

Book a demo