Use case

Connect a customer record to a place.

Use an Adrehs code as a consistent customer, merchant or field-visit location reference.

Sierra Leone Adrehs public-service location network
One reusable location layer for Sierra Leone

01

Where Adrehs fits.

Adrehs can evidence where a location is. It is not identity evidence, proof of residence, KYC approval, credit evidence or account ownership.

  1. 01

    Collect the code

    Ask the customer or merchant for an Adrehs location.

  2. 02

    Resolve the place

    Confirm coordinates and administrative context.

  3. 03

    Request confirmation

    Show the resolved location before it is saved.

  4. 04

    Link the record

    Store the location reference under access controls.

  5. 05

    Verify separately

    Perform KYC, risk and compliance checks in authorised systems.

Location in. Better operations out.

Adrehs provides a reliable location handoff. It works alongside the systems that govern the service, transaction or official record.

What your system receives

Usable location data.

Adrehs code
Consistent customer location reference
Coordinates
Precise place
Administrative context
District and chiefdom
Place details
Available address information
Share link
Controlled field-visit handoff

What Adrehs does not replace

Your operational authority.

Identity
Who the customer is
Residence
Whether the person lives there
KYC decision
Risk and compliance approval
Creditworthiness
Affordability and repayment evidence
Account authority
Ownership and permissions

Important: An Adrehs code identifies and resolves a location. It is not proof of identity, ownership, entitlement, service completion or legal status.

Practical value, without overclaiming.

The strongest results come when Adrehs is connected to an existing, well-governed workflow.

01

Cleaner records

Reduce inconsistent free-text location descriptions.

02

Field support

Help authorised agents reach merchant or customer locations.

03

Administrative insight

Analyse service coverage without treating location as identity.

Recommended integration.

Resolve on the server, confirm with the user, store the stable identifiers your workflow needs, and keep sector-sensitive records in the authoritative platform.

01Collect code
02Resolve location
03Link record securely
04Verify identity separately