For government & customs

Residency, entitlement, and cross-border trader identity.

Anchor residency and clearance for entitlement and enrolment, and issue the trader identity that AfCFTA cross-border trade needs — with data held in-jurisdiction under the country’s own data-protection regulator.

Talk to us

Overview

The shift, in one anchor.

Governments need to verify residency and entitlement without building another central biometric database — and AfCFTA cross-border trade needs a trader identity that crosses borders without surrendering data to any single state. Civic Anchor provides both, with data held in-jurisdiction.

Anchor residency and clearance for entitlement, enrolment, and social programmes; issue the AfCFTA Trader Trust Passport that lets a trader prove origin, business registration, and identity at any border post — cryptographically, without a physical document. Civic Anchor integrates with national ID systems; it never replaces them, and each country’s data stays under its own regulator.

Capabilities

What you get.

Residency and clearance for entitlement and enrolment
Cross-border trader identity for AfCFTA corridors
Data held in-jurisdiction, under the local regulator
Integrates with national ID systems — never replaces them

Use cases

Where it runs.

Residency & entitlement

Anchor residency and clearance for enrolment, grants, and entitlement — verifiable, revocable, consent-bound.

Cross-border trader identity

Issue the AfCFTA Trader Trust Passport: prove origin + business registration + identity at the border.

Lawful access, in jurisdiction

Documented court-order intake; read-API contracts per the jurisdiction’s data-protection law.

Integrates with national ID

Sits alongside national registries — a trust layer over sovereign identity, not a replacement.

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.

National ID & civil registry
Customs & single-window
Social-grant & entitlement systems
Border management
Tax authority

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": ["residency", "trader_passport"],
  "purpose": "border_clearance"
}

Webhook · signed result

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

What changes

Before the anchor, and after.

Dimension	Document-based today	With Civic Anchor
Entitlement	A new central database for every programme	Residency and clearance anchored once, verified on demand
Cross-border trade	Paper documents re-checked at each border post	The AfCFTA Trader Trust Passport, proven cryptographically
Data sovereignty	Data surrendered to whoever runs the system	Held in-jurisdiction under the country’s own regulator

Compliance

Built to the regulator, in jurisdiction.

Data held in-jurisdiction under the country’s own data-protection regulator (POPIA in South Africa, the Data Protection Act in Zimbabwe, and each market’s framework). Civic Anchor integrates with — never replaces — national ID systems.

Institution portal

Bring Government & customs 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