For telcos

SIM-registration identity, reusable for the whole relationship.

Capture a verified identity once at SIM registration and reuse it across the subscriber lifecycle — upgrades, mobile money, and regulatory re-verification — without storing raw biometrics.

Talk to us

Overview

The shift, in one anchor.

SIM registration is a regulatory cost centre done once and thrown away — the identity captured at the point of sale rarely powers anything else. Civic Anchor turns that mandatory step into a reusable asset: a verified identity anchored to the subscriber’s device.

Capture the biometric ceremony once at an authorised service point; reuse the resulting anchor across upgrades, mobile-money KYC, and regulatory re-verification — without retaining raw biometric templates on telco infrastructure. The subscriber relationship rides one verified identity instead of a folder of scanned documents.

Capabilities

What you get.

Regulator-aligned SIM-registration identity at scale
Reusable across the subscriber relationship
Mobile-money KYC against the same anchor
No raw biometric data retained on telco infrastructure

Use cases

Where it runs.

SIM-registration identity

Run the regulator-aligned registration ceremony at the service point; the verified anchor persists with the subscriber.

Mobile-money KYC

Onboard wallets and tiers against the same anchor — no second identity capture.

Reusable across the lifecycle

Upgrades, SIM swaps, and re-verification reuse the existing anchor with the subscriber’s consent.

No biometric liability

Templates stay on the holder’s device — the telco holds no raw biometric database to breach.

Fits your stack

Connects where you already work.

Civic Anchor verification drops into the systems this sector already runs — over REST or tRPC, mTLS-secured, with webhook events on every result.

Dealer / POS onboarding
Subscriber management
Mobile-money & wallet KYC
Number management (HLR)
Regulatory reporting

Integration

One call, a signed answer.

Your system requests a check; the subject approves in their wallet; you receive an HSM-signed, jurisdiction-stamped result over webhook.

Request · POST /api/v1/challenges

POST /api/v1/challenges
Authorization: <mTLS client certificate>

{
  "subject": "did:civicanchor:018e4f2c-…",
  "checks": ["identity", "sim_registration"],
  "purpose": "sim_activation"
}

Webhook · signed result

{
  "challenge_id": "chl_01J2Qe…",
  "status": "verified",
  "subject": "did:civicanchor:018e4f2c-…",
  "jurisdiction": "ZA",
  "checks": { "identity": "pass", "sim_registration": "pass" },
  "signed_by": "hsm:af-south-1"
}

What changes

Before the anchor, and after.

Dimension	Document-based today	With Civic Anchor
SIM registration	Captured once at the point of sale, then discarded	A reusable anchor that rides the whole subscriber relationship
Mobile-money KYC	A second, separate identity capture	The same anchor, re-verified with consent
Biometric liability	Raw templates held on telco infrastructure	Templates on the holder’s device — nothing to breach

Compliance

Built to the regulator, in jurisdiction.

Aligned to SIM-registration regimes (RICA in South Africa, the equivalent framework per market). Live biometric continuity replaces static document checks; no raw biometrics retained on telco systems.

Institution portal

Bring Telcos onto Civic Anchor.

Tell us your market and we’ll map the fastest path to verifying against the anchor — including the regulatory steps in your jurisdiction.

Talk to us All solutions