> ## Documentation Index
> Fetch the complete documentation index at: https://docs.daya.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Tier 1 verification

> Verify a customer with a BVN and a live selfie on a Daya-hosted page

Use the Business API to start a verification session. The customer accepts the notice and completes a live selfie on a Daya-hosted page. Your backend reads the result. You do not need to build a camera screen or upload a selfie.

Migrating from selfie upload? See the [legacy reference](https://docs.daya.co/api-reference/customers/submit-tier1-verification.md) and [cutoff guidance](#hosted-only-cutoff).

## Create a session

### Set up your Business API key

1. Open the [Developer Dashboard](https://dashboard.daya.co/dashboard/keys) and select **Sandbox** or **Production**.
2. Go to **API Keys** and select **Create New Key**.
3. Under **Access → Business**, select **liveness**, **read**, and **write**. Keep the key on your server.

If your existing key already has these permissions, you can keep using it. If it does not, create a new key. Renaming or rotating a key does not add permissions. Keep your current key in place for any other API calls until you switch them over. If you cannot create a key or do not see **liveness**, contact Daya support before switching from selfie upload.

> [!NOTE]
>
> If Create returns `403 Forbidden`, check that the key has Business **liveness** and **write**. If you cannot select the permissions or still get `403`, contact Daya support before switching.

### Start the session

Use a [customer ID](https://docs.daya.co/api-reference/customers/create-customer.md) and a key from the same environment. You also need the customer's 11-digit BVN.

```bash cURL theme={"dark"}
curl --request POST \
  --url 'https://api.daya.co/v1/customers/CUSTOMER_ID/tier1-verification/sessions' \
  --header 'X-Api-Key: YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --header 'Idempotency-Key: YOUR_STABLE_REQUEST_KEY' \
  --data '{"bvn":"CUSTOMER_BVN"}'
```

For sandbox, use `https://api.sandbox.daya.co` and sandbox credentials. Send the BVN as a string. You do not need to send a notice version. Daya selects the current notice and shows it to the customer on the hosted page.

If the response is lost or times out, resend the same request with the **same body and idempotency key**. A new key does not restart verification.

## Send the customer to Daya

A successful [Create request](https://docs.daya.co/api-reference/customers/create-hosted-tier1-session.md) returns `202 Accepted`. Save the response's `id` as the session ID. When `next_action` is `capture`, send the customer to `capture.capture_url` before `capture.expires_at`.

Only the customer being verified should open the link. They must review and accept the notice and complete the selfie on their device. Do not log the BVN or share the capture link with anyone else.

## Read the result

[Get the session status](https://docs.daya.co/api-reference/customers/get-hosted-tier1-session.md) using a key with `business:liveness` and `business:read`. A selfie submission, browser redirect, or temporary status error is not an approval. Use `status` for the result and `next_action` for what to do next.

| Next action | What to do |
| - | - |
| `capture` | Send the customer to the capture link in the response. |
| `wait` | Poll with backoff. If `retry_at` is present, wait until then before polling again. Do not start a new session. |
| `retry` | [Request another capture](https://docs.daya.co/api-reference/customers/retry-hosted-tier1-session.md) on the same session. This does not reset the attempt limit. |
| `update_bank_details` | Call [Update Tier 1 bank account](https://docs.daya.co/api-reference/customers/update-tier1-verification.md), then check the session again. Do not restart the selfie check. |
| `contact_support` | Stop retrying and contact Daya support. Include the session ID, not the BVN or capture link. |
| `none` | No further action is required for the session. |

A `verified` status means Tier 1 identity verification passed. It does not mean a bank account has been created. Follow any remaining action before using the relevant product.

### Receive a webhook

Subscribe to [`customer.verification.approved` and `customer.verification.rejected`](https://docs.daya.co/api-reference/webhooks/events). A rejection event is a signal to read the session status and follow `next_action`, not permission to retry. [Verify the signature](https://docs.daya.co/api-reference/webhooks/verification.md) against the raw request body before processing the event. Deduplicate by event ID. Use the session status to guide recovery: not every capture failure sends a rejection webhook.

## Resume or resolve a conflict

* **Resume an eligible session:** If an older session says `contact_support` and no other action is available, contact Daya support with the session ID. If support confirms the session can be resumed, [resend the original input](https://docs.daya.co/api-reference/customers/resume-hosted-tier1-session.md) on the same session. Keep omitted fields omitted. Resume does not reset the attempt limit.
* **`409 IDENTITY_CONFLICT`:** The BVN is linked to another customer under your merchant. Check the customer record or contact Daya support. Do not retry the same pairing.
* **`409 CONFLICT`:** Check the customer's existing verification and session status before trying another Create. If you need help, share the error code and request ID, if available. Do not include the BVN, API key, or capture link.

## Hosted-only cutoff

Once the policy is active in an environment, legacy `POST /v1/customers/{id}/tier1-verification` returns HTTP `403` with error code `HOSTED_LIVENESS_REQUIRED`. The response points to this guide and the customer-specific hosted creation endpoint; no hosted session is created by that denial. Start with [Create Tier 1 session](https://docs.daya.co/api-reference/customers/create-hosted-tier1-session.md), then follow the returned `next_action`.

This applies to all Business API merchants in that environment, including existing integrations. Until Daya confirms activation for your environment, existing selfie-upload instructions still apply. Existing Tier 1 approvals are not revoked.

* Create, retry and resume require `business:liveness` and `business:write`.
* Status requires `business:liveness` and `business:read`.
* The policy does not add scopes to a key. Create a suitably scoped key in the Developer Dashboard if needed. Contact Daya support if those permissions are unavailable.
* Permanent `POST /v1/onramps` cannot perform inline legacy verification for an unverified customer after cutoff. Complete hosted Tier 1 first, then create the permanent onramp. Existing approved customers can still proceed through the account-creation flow. Do not treat the refusal as an instruction to repeatedly create customers.
* Tier 2, bank-detail updates and existing hosted sessions are unchanged. This is a Business API policy, not a change to native app endpoints or temporary-account verification eligibility.

Keep the original idempotency key and body when a creation response is uncertain. A fresh key does not reset checks, reopen a held case, or bypass a conflict.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.