Bridge
Contact us
Identity & KYCNext

Let people sign in once and share only what you need.

Federated sign-in with consented field sharing.

Next. PediID sign-in is built and on its way to Live. Tell us if you need it, and we'll tell you honestly when it will be ready for you.

Talk to us about PediID sign-in
Illustrative
Why it matters

What it will change.

Every app asks people to prove the same things again: name, date of birth, phone, address. Each copy is another place their data can leak, and another form that loses you sign-ups.

PediID will be a sign-in people carry between apps. They prove who they are once, and when your app asks, they approve which facts to share. Your app receives those facts, graded by how well they are known, and nothing else.

It is designed so integrators can't track people across each other: each app gets its own identifier for the same person. Where a yes or no is enough, such as 'over 18', that is all you receive.

How it works

Step by step.

  1. A person proves who they are once

    Their facts will be verified and graded in PediID, not in every app they use.

  2. Your app asks for what it needs

    You'll register which facts you need and why. Where a yes or no will do, you'll ask for that instead of the value.

  3. They approve the share

    The person will see exactly what you'll receive and approve it, every time the request changes.

  4. You receive graded facts

    Each fact will arrive with how well it is known, under an identifier that is yours alone.

What it will do

Built in, not bolted on.

Standard sign-in flows

Pushed authorisation requests, PKCE, discovery and published keys, so existing sign-in libraries fit.

Predicates, not values

Ask whether someone is over 18 and you'll get a yes or no, not their date of birth.

Consent per field

People will approve each fact they share, and be able to see and withdraw what each app holds.

No tracking across apps

Each integrator will get a different identifier for the same person.

Graded evidence

Facts will arrive with their assurance grade, so you know what was checked.

Refusals by design

Some data will never be collected or shared at all, enforced by what the system doesn't store.

  • Sign in with PediID, sharing only the fields a person consents to
  • PAR, PKCE, discovery and JWKS
  • A different identifier for the same person at each integrator
Use cases

How businesses could use it.

Illustrative businesses, not customers. Figures are made up to show the flow.

A lending app in Lagos · Lenders & BNPL

Sign-up without a form

Most applicants abandon the lender's five-screen sign-up form. The lender only needs a verified name, phone, BVN-backed identity and an over-18 answer to start.

  1. The app will offer 'Continue with PediID' on its first screen
  2. The applicant will approve sharing their name, phone and an over-18 answer
  3. The app will receive those facts, graded, under its own identifier
  4. The application will start with nothing typed

Applicants will start in seconds, and the lender will hold only the facts it asked for.

Illustrative

An event ticketing platform in Abuja · Merchants & e-commerce

Age checks without birthdays

Some events are 18 and over. The platform doesn't want to store anyone's date of birth just to check it.

  1. Checkout will ask PediID one question: over 18?
  2. The buyer will approve the yes or no
  3. The ticket will be issued, and no date of birth will be stored

The platform will check age without holding a single birthday.

Illustrative

A group running a wallet, a marketplace and a savings app · Fintechs & neobanks

One identity across a family of apps

Customers verify separately in each of the group's three apps, and support staff can't tell they are the same person.

  1. Each app will sign people in with PediID
  2. People will verify once and approve what each app receives
  3. Each app will receive its own identifier, so the group decides deliberately whether to link them

People will verify once, and each app will get only what it needs.

Illustrative
What it won't do

Honest limits.

  • It carries no certification.
Who it's for

Built into these products.

Fintechs & neobanks

Launch a full money app without building the plumbing.

Fintechs & neobanks

Questions about PediID sign-in

Is PediID available now?

Not yet. It is built and on its way; tell us if you want to integrate and we'll tell you when.

Does it carry a standards certification?

No. It uses standard sign-in flows so common libraries work, but it carries no certification.

Can we get a person's full record?

No. You receive only the facts you registered for and the person approved, under your own identifier.

Related capabilities

Identity & KYC

Live

Tiered onboarding, limits that rise automatically, graded identity records.

Business verification

Live

KYB for the businesses your customers run.

Accounts

Live

Multi-currency customer accounts with point-in-time balances, liens and statements.

Bridge for Business

Tell us what you're building.

We'll come back with what's live for you today, and what's next.

Talk to usRead the docs