Create a session
Set up your Business API key
- Open the Developer Dashboard and select Sandbox or Production.
- Go to API Keys and select Create New Key.
- Under Access → Business, select liveness, read, and write. Keep the key on your server.
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 and a key from the same environment. You also need the customer’s 11-digit BVN.cURL
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 returns202 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 using a key withbusiness: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.
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 tocustomer.verification.approved and customer.verification.rejected. A rejection event is a signal to read the session status and follow next_action, not permission to retry. Verify the signature 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_supportand no other action is available, contact Daya support with the session ID. If support confirms the session can be resumed, resend the original input 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, legacyPOST /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, 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:livenessandbusiness:write. - Status requires
business:livenessandbusiness: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/onrampscannot 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.