Skip to content

Identity to decision.
One workflow.

Verify people and businesses, check Ghana Cards with the NIA and screen for risk in one configurable KYC/AML workflow.

Book a demoGet started
  • KYC: document, liveness, face match
  • Ghana Card checks with the NIA
  • KYB: ORC lookup and related parties
  • Sanctions, PEP, adverse media
  • Crypto wallet screening
  • Reason-coded decisions
  • Signed webhooks

Verification shouldn’t need three vendors.

Teams stitch together separate vendors for identity and screening, then reconcile the results by hand.

Today: one applicant, several systemsGeneric example

ID verification vendor

document · selfie

Own contract, API, dashboard and data terms

Screening vendor

sanctions · PEP · media

Own contract, API, dashboard and data terms

Crypto analytics vendor

wallet risk

Own contract, API, dashboard and data terms

Results compared by hand, decisions recorded somewhere else

With Vouch: one session, one record

  1. capture
  2. verify
  3. screen
  4. decide

Capture. Verify.
Screen. Decide.

Vouch runs each session from first screen to final outcome across licensed providers, and keeps the evidence in one place.

  • Capture

    The applicant opens a link and follows your workflow. Consent comes first.

  • Verify

    Every check re-runs on the server. A device-only pass never approves anyone.

  • Screen

    People and businesses screened against licensed data in one pass.

  • Decide

    Written rules, not a black-box score: one outcome with its reason.

Four jobs, one record.

Licensed providers behind one adapter: swap a provider, keep your integration.

Fast-follow before commercial launchPlanned on the roadmap

  • Know the person

    KYC

    One document, chosen by nationality and residency, and a live selfie. Device matches are re-checked on the server.

    • Ghana Card for citizens and residents
    • Passport or national ID for non-resident foreigners
    • Live camera only, no uploads
    • NFC chip reading where supported
    • Fast-followNative iOS and Android SDKs

  • Know the business

    KYB

    Registry lookup at the ORC, and every person behind the business verifies as an individual.

    • ORC lookup by registration number
    • Document list set by entity type
    • Owners at 20% or more (5% in high-risk sectors)
    • Each related party gets their own link
    • One decision for the whole business
    • PlannedPartnerships, NGOs and listed companies
    • PlannedNigeria and Kenya business documents

  • Know the risk

    AML screening

    Sanctions, PEP and adverse media in one pass, for people and businesses. Wallets get their own check.

    • One result, with detail per list
    • Any hit needs a reviewer
    • Wallets scored low, medium or high risk
    • Fast-followAfrica-tuned name matching for Ghanaian and West African variants
    • Fast-followTravel Rule data exchange
    • PlannedWallet clustering and mixer detection

  • Run the review

    Case management

    Every review or block opens a case with each check, its evidence and the audit trail.

    • Assign, decide, record a reason code
    • Read-only auditors, CSV export
    • Server-side roles, two-step sign-in
    • Usage and cost per service
    • Fast-followContinuous risk scoring
    • Fast-followSAR/STR filing in goAML format

Build Custom
Workflows in Minutes.

Choose the steps, their order and the route each applicant takes. Branch on nationality, document or business type.

Required checks stay shared, so every route keeps them.

Try

Workflows

Residents and foreign nationals

IndividualDraft

Steps

Consent

Always first: nothing is captured before the applicant agrees.

Decision

Your policy allows, sends to review or blocks. Flagged results open a case.

Set how strict each check is

Lenient, standard or strict, per check. Standard is the default.

Check
Strictness for sanctions, pep and media

Recommended fuzzy name matching.

Floors that never move

At every level, on every route:

  • A sanctions match always blocks
  • Every Ghana Card is checked against the NIA
  • Liveness failure after all attempts always blocks
  • Every match reported by the device is re-checked server-side

Pay for the checks you run.

Build a package from individual services, each priced per check. A verification costs the checks it ran.

Published, not gated
A published price per check, no sales call. Launch prices are being finalised.
One contract as you grow
Add a service without a new integration.
Enterprise volumes
Custom volumes, quoted directly.
Compare packages

Usage

What you’ve used, what it cost, and the services in your package.

Pick the checks you need. You pay per completed check; turning a service on adds anything it depends on.

Global

Work for applicants of any nationality.

  • Identity verification

    Document authenticity, liveness and face match for the Ghana Card, passports and national ID cards.

    A package holds at least one service, and every other service builds on this one.

  • Sanctions, PEP and adverse media

    Screens every applicant and business name against licensed watchlists.

    Billed per completed check

  • Crypto wallet screening

    Risk-scores submitted wallet and blockchain addresses.

    Billed per completed check

Ghana

Country-specific registries.

  • NIA Ghana Card check

    Biometric match against the NIA registry.

    Included with identity verification: every Ghana Card is checked against the NIA.

  • Business verification (KYB)

    ORC registry lookup, business documents and verification of related parties.

    Billed per completed check

3 services selected

Live portal view · Usage → Package. Try it: services add what they depend on.

Integrate once.
Hear back when it’s decided.

Create a session, hand the applicant to the SDK, act on a signed webhook.

API
Bearer keys, idempotent POSTs, one error envelope
SDK
Hosted web capture: live camera, consent first
Webhook
Signed with HMAC-SHA256, retried for 24 hours

Fast-follow Native iOS and Android SDKs, and a sandbox. The API contract is in draft.

  1. API
  2. SDK
  3. Webhook
POST /v1/sessions
Authorization: Bearer <api_key>
Idempotency-Key: onboarding-4821
Content-Type: application/json

{
  "applicant": {
    "type": "individual",
    "external_reference": "cust_4821"
  }
}
Create a session201 Created
  1. API
  2. SDK
  3. Webhook
// Illustrative: interface not final.
// capture_url holds a short-lived token;
// your API key never reaches the device.

Vouch.capture({
  captureUrl: session.capture_url,
  onComplete: () => showPending(),
  onExit: () => showRetry(),
});
Web capture SDKconsent → document → selfie
  1. API
  2. SDK
  3. Webhook
POST /webhooks/vouch
X-Vouch-Signature: sha256=<hmac>

{
  "event": "decision.created",
  "session_id": "ses_01J9X3K2Q7",
  "data": {
    "outcome": "review",
    "reason_code": "REVIEW_PEP_MATCH"
  }
}
Signed decisionreview
Case

Cases

KM

Kwame Mensah

Allow

Individualcas_01J9X3P5D4View session

3 passed1 failedof 4 checks
Print report
Nationality
Ghana
Document
Ghana Card
Reference
NPT-10230
Case opened
21 Oct 2026, 12:02

Progress

  1. Session started

    21 Oct 2026, 12:00

  2. Consent given

    21 Oct 2026, 12:00

  3. Checks run

    21 Oct 2026, 12:02

  4. Policy decision

    PEP match

    21 Oct 2026, 12:02

  5. Reviewer assigned

    21 Oct 2026, 12:09

  6. Final decision

    21 Oct 2026, 12:31

Closed

Triggered reasons

  • PEP matchREVIEW_PEP_MATCH

Checks

  • DocumentPassed

  • Liveness and face matchPassed

    Liveness98%
    Face match94% · threshold 80%

    Provider scores · placeholder until the biometric provider is chosen

  • NIA Ghana CardPassed

  • Sanctions, PEP and adverse mediaFailed

    PEP match

    PEP: Kwame MensahModerate match

    PEP register (sample)

Evidence

Opening an item is recorded in the audit trail.

  • Ghana Card, front
  • Ghana Card, back
  • Live selfie
  • NIA registry response
  • Screening report

Final decision

AllowVerified by reviewer

Checked against the national gazette: a different person with the same name. The NIA confirms the applicant’s identity.

By Kwame Boateng

Audit trail

  1. Session created

    Vouch ·

  2. Consent recorded

    Applicant ·

  3. Checks completed

    Vouch ·

  4. Decision made by policy · PEP match

    Policy engine ·

  5. Case opened

    Vouch ·

  6. Case assigned

    Kwame Boateng ·

  7. Decision recorded · Verified by reviewer

    Kwame Boateng ·

Live portal view · Case cas_01J9X3P5D4 (Reviewer clears PEP)

Every outcome explains itself.

Written rules, evaluated in order. The outcome carries its most serious reason; the case keeps them all.

Bring every check into one decision.

Tell us how you onboard today. We’ll show you the same flow on Vouch.

Book a demoGet started