PONALO Connect

For institutions that need the relationship to be true.

Connect is the institutional view of the same platform state. It is desktop-first, permission-bound and built for operators who work queues, not dashboards for their own sake.

PONALO PassportLIVE
Philip Papa Nii Sowah

Philip Papa Nii Sowah

ID 870305 •••• 084 · ZA

5 Mar 1987 · Johannesburg

Verified identity
Links24
Verified18
Needs you3
Standard Bank · ChequeVerified
Old Mutual · Life coverConfirm
SARS · Taxpayer recordVerified
Identity health 84%
PONALO Sovereign
Country packZA · 01
AccessClear
Audit stream

Purpose-bound access. No population query.

Requests today42 · Clear
Home Affairs lookup09:41
Grant eligibility check09:38
Warrant-bound request09:12
100% traceable
PONALO Connect
92

Confidence

Institutional view

+4.2% this week

Open cases7
Attested1 204
Requests18
Confirmation queue18
Consent evidence42
Data quality97
Connector health100
Minimum disclosureEnforced

ONE PLATFORM STATE

Identity graph

BANK
COVER
EMPLOY
STATE
Update onceReflect everywhere
Shared identity infrastructure

What Connect does

Verification is mutual, or it is just an assertion.

An institution can assert a relationship. Only the person can confirm it. Connect makes both halves explicit, and keeps the disagreement visible when there is one.

Relationship attestation

Assert a relationship with role, status, effective dates and provenance.

Confirmation requests

Ask the consumer to confirm — and see the verdict and its timestamp.

Case management

Disputes, corrections, identity mismatch and beneficiary discrepancy queues.

Consent evidence

Purpose, scope, version, grant, expiry and withdrawal, fully auditable.

Minimum disclosure

Connect sees its own relationship, never the person's whole Passport.

Bulk operations

Batch attestation and reconciliation with per-record outcome reporting.

Integration health

Connector status, event throughput, retries and dead-letter visibility.

Reporting

Verification rates, dispute rates, resolution times and data quality.

Operating model

A queue, a decision, a record.

  1. 01

    Ingest

    Relationships arrive

    Via connector, bulk upload or manual attestation, each with provenance.

  2. 02

    Request

    Confirmation is sought

    The person is asked, in their Passport, on the surface they are using.

  3. 03

    Resolve

    Disagreements become cases

    Owned, tracked against SLA, and closed with a documented outcome.

  4. 04

    Evidence

    Everything is provable

    Consent, authority, provenance and the full change history are retained.

Boundary

An institution's participation in a relationship does not entitle it to the person's wider picture.

Connect is scoped to the relationships an institution is party to, under a consent record with a stated purpose. Data minimisation is enforced by policy, not by interface convention.

See the institutional workspace.