Getting started

Create an account Pilot-scoped

PesaGuard has no public signup. Access is provisioned with the pilot team, because the reconciliation scope — flows, matching keys, retention — is agreed per operation rather than self-served.

What provisioning covers

A tenant. Your organization's data lives in its own tenant boundary, enforced at the database layer.
An M-Pesa (Daraja) flow. The active payment scope: STK Push and PayBill callbacks.
Dashboard users. Named accounts with roles — reviewer, operator, administrator.
A pilot plan. Pricing follows your operation; see pricing for the shape of it.

What we ask before provisioning

Which M-Pesa shortcodes and flows you collect on.
Where your internal records live (Postgres, Sheets or a REST ledger).
Who reviews exceptions, and through which channels they should be reached.
Whether you need Airtel Money or bank rails today — because those are not included, and we would rather say so now than mid-pilot.

Multi-rail is a scoping conversation

Airtel Money, bank transfers and card rails are out of scope for the pilot. If multi-rail support is a hard requirement, it becomes a separate scoping exercise — say so in the first conversation.

Then

Once your tenant exists, create an API key is a conversation, not a form — credentials are issued with explicit scopes and rotation metadata.