Skip to main content
With the wallet product, your customers can hold wallets with you. A customer’s KYC tier decides their limits, and they move up a tier by passing identity checks. Needs the CUSTOMERS feature, with customers:write and kyc:write.

Create a customer

The customer starts at kyc_tier: 0, kyc_status: unverified. Mesh registers them with the bank in the background; until that’s done (usually seconds), a check or a wallet for them answers 409 (code 62): retry shortly.
Don’t send a BVN or NIN here. They go to the checks below, so they’re verified before they’re stored.

Verify them

POST /v1/verifications/{checkType} with the customer’s customer_id:
Most checks answer 200 with the verdict. liveness and address_verify take longer: they answer 202, and you follow with GET /v1/verifications/{verificationId}.

Tiers

The bank decides the tier from the checks, and the customer’s record shows it. Each tier has its own balance, single-transaction and daily limits.

Updating a customer

PATCH /v1/customers/{customerId} changes only the fields you send. Once a customer is verified, their name and date of birth can’t change (422, code 52). For an open business, nothing changes through the API once they reach tier 1 (422, code 55).