How it works

From organization to automated transaction

How MoMo Assistant is structured, how a transaction actually moves through it, and what each piece — Organizations, Stations, SIMs, Runtime V2 — is responsible for.

The automation lifecycle

What happens, in order, from onboarding a station to a synced, audited transaction.

Onboard your organization

Create your organization and define your stations, agents, and the operating policies Runtime V2 will enforce.

Register devices and SIMs

Enroll trusted devices and bind SIMs to them through the Device Trust Engine and SIM Trust before either can transact.

Automate USSD workflows

Runtime V2 executes the USSD sequence — dialing, navigating menus, entering amounts — at consistent, predictable timing.

Agent confirms

Before anything commits, the agent sees and confirms the transaction. Automation removes the retyping, not the decision.

Sync and audit

Transaction metadata and station configuration sync to the cloud; the security-relevant event is written to the audit log. The PIN never makes either trip.

Architecture

Four concepts, one hierarchy: Organizations own Stations, Stations own SIMs and devices, and every automated action runs through Runtime V2.

Organizations

The top-level business entity. Owns every station beneath it, sets the policies Runtime V2 enforces, and is the single place audit history rolls up to.

Stations

A physical point of operation — its own agents, its own devices, its own SIMs — reporting up to the organization it belongs to.

SIMs

Each SIM is bound to the device it's enrolled on through SIM Trust, keeping multi-SIM stations' lines independently trusted rather than pooled.

Runtime V2

The execution engine every automated USSD sequence runs through — the same engine regardless of station or SIM, so behavior stays consistent.

USSD Runtime

Runtime V2 dials and navigates USSD menus with consistent timing, so the same sequence behaves the same way on every run — no more, no less than what the organization's policy allows it to automate.

Cloud Sync

Station configuration and transaction metadata sync across devices so a station's setup isn't tied to a single phone. Mobile Money PINs are excluded from sync entirely — they stay on the device that holds them.

Ready to see the runtime in action?

Download the beta and run your first automated sequence, or request a walkthrough with your team.

Download Beta Request Demo