KYC, collections, and portfolio risk — built on real addresses.
1 in 3 KYC applications in Ghana stall on address verification alone. Banking Suite turns a hex code into a verified, fraud-checked, auditable location — for onboarding, collections, and risk.
WHY THIS EXISTS
A bank can't lend against an address it can't verify — or find again to collect.
Most Ghanaian customers don't have a formal street address to put on a KYC form. What they have is a landmark, a neighbourhood, or a GhanaPost GPS code — and no easy way for a bank to turn that into something it can trust, audit, and revisit months later when a loan needs collecting.
Banking Suite is that layer: verification that resolves to a real hex cell instead of a free-text field, collections tooling that remembers where a borrower actually is, and risk analysis that shows exposure by geography instead of one blended number.
HOW IT WORKS
Verify once. Locate again. See the whole book.
01 — Verify
Verify a customer's address
Submit a GPS fix, manual coordinates, a hex code, or a GhanaPost GPS code with a signed consent token. We run a fail-closed fraud/spoof check, resolve it to a hex cell, and score confidence — high, medium, or low.
02 — Track
Register for collections
Once verified, register a borrower's home and work zones (consent-gated, same token). Field agents later query where and when to find them — with automatic "customer has moved" detection.
03 — Manage risk
See your loan book by zone
Upload up to 10,000 loans at once. We bucket them into hex zones and surface exposure and delinquency rate per zone, so concentration risk is visible before it becomes a write-off.
WHAT'S INCLUDED
Six pieces, one API.
KYC address verification
Four ways to submit a location — GPS fix, manual coordinates, hex code, or GhanaPost GPS code. Every verification resolves to a real hex cell and a reverse-geocoded address, not just a coordinate pair.
Fraud detection, fail-closed
Every KYC call runs through spoof/fraud checks before it's accepted — if the fraud detector is unavailable, the call fails rather than silently skipping the check.
Consent-token replay protection
Consent tokens are hashed and enforced unique at the database level, so the same consent can't be replayed across verifications.
Collections & move detection
Registered home/work zones feed a locate endpoint for field agents — complete with recommended AM/PM visit windows and a Maps link — and flag when a customer's latest verified location has drifted from where they're registered.
Portfolio risk by geography
Bulk-upload a loan book and see exposure and delinquency rate grouped by hex zone — low, medium, or high risk — instead of a single portfolio-wide number.
Signed certificates
A successful verification can issue a signed certificate anyone can check — the same certificate system behind AfriHex's standalone Address Verify product.
CONSENT & AUDIT, NOT AN AFTERTHOUGHT
Every verification and every collections registration requires an explicit consent token — hashed and enforced unique in the database, so the same consent can never be replayed. The fraud check is fail-closed: if it can't run, the call is rejected rather than silently waved through.
Every KYC record is persisted with its resolution method, confidence, and risk signals — an auditable trail your compliance team can point to, not a black box.
Provisioned per institution.
Banking Suite isn't a self-serve plan — access is set up per bank or lender, with its own API key and rate limits. Tell us what you're onboarding or collecting on, and we'll get you set up.
Talk to us about access