Skip to main content
POST
Create a Tier 1 session
Start a session for an existing customer. Access requires the liveness permission on a Business API key. Set up your API key, then follow the guide to send the customer to capture and read the result.

Authentication and parameters

string
required
Business API key with business:liveness and business:write.
string
required
A stable key for this Create request. If the result is uncertain, reuse the same key and request body.
string
required
Customer ID (UUID).

Request body

string
required
The customer’s 11-digit Bank Verification Number.
string
Omit this field for new integrations. Daya selects the current notice, which the customer accepts on the hosted page. Existing callers can continue sending the current version.
string
The customer’s phone number. Required if you send bank_account.
object
Optional Nigerian bank account belonging to the customer. Include account_number and bank_code together with phone_number.

Response

202 Accepted returns a session, not an approval. Save id and follow next_action. When it is capture, the response includes capture.capture_url and capture.expires_at. Get the session status to check the result. A 404 Not Found can mean the customer is not active or is not available to your merchant. A 409 IDENTITY_CONFLICT means a different customer under the same merchant already owns the BVN. A plain 409 CONFLICT requires checking the customer’s existing verification or session before trying again.