For banks & financial institutions

Onboard and re-verify without re-collecting documents.

Run FICA/KYC onboarding against a credential the customer already holds, screen against sanctions and PEP lists continuously, and price credit and trade reputation on biometric ground-truth.

Talk to us

Overview

The shift, in one anchor.

Document-based KYC is slow, repeated at every institution, and a standing fraud surface — every bank re-collects the same ID, proof of address, and selfie, then stores copies it must protect. Civic Anchor replaces that with a one-time, biometric-anchored credential the customer already holds.

At onboarding, the customer presents their credential and approves the check; the bank receives a signed, jurisdiction-stamped confirmation in seconds — no document upload, no shared biometric database, and a tamper-evident record for the regulator. The same anchor then powers continuous AML, sanctions, and PEP screening, and prices credit and trade reputation on biometric ground-truth no bureau can match.

Capabilities

What you get.

FICA / KYC onboarding in seconds, consent-bound
AML, sanctions, and PEP screening as a continuous overlay
Re-verification without re-collecting documents
Trade-finance reputation scored per trader over time

Use cases

Where it runs.

FICA / KYC onboarding

Verify a new customer against a held residency credential in seconds — consent-bound, audit-logged, no document re-collection.

Continuous AML & sanctions

Screen the verified subject against sanctions, PEP, and watchlists as a standing overlay, not a point-in-time check.

Trade-finance reputation

Price exporter/importer risk on a per-trader reputation index built from real, signed verification history.

Frictionless re-verification

Periodic re-KYC and step-up checks run against the same anchor — no customer re-submission.

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.

Core banking
Card & payment switches
AML & sanctions screening
Credit bureaus
Loan origination

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", "fica_kyc", "sanctions"],
  "purpose": "account_onboarding"
}

Webhook · signed result

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

What changes

Before the anchor, and after.

Dimension	Document-based today	With Civic Anchor
Onboarding	Days — manual document capture and FICA review	Seconds — a signed confirmation against a held credential
Documents stored	ID, proof of address, and selfie copied and guarded at every branch	None — no upload, no shared biometric store
AML & sanctions	A point-in-time check at onboarding	A continuous overlay on the verified subject

Compliance

Built to the regulator, in jurisdiction.

Aligned to FICA and POPIA in South Africa, and to each market’s framework as the network expands. Civic Anchor acts as an Operator under written agreements; raw biometric data is never stored.

Institution portal

Bring Banks & financial institutions 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