BVN Send OTP

Select the verification method and trigger sending the code OTP. This is the second step of the BVN verification Flow for Nigeria.

Endpoint

POST /kyc/nga/bvn/send-otp

Authentication

Type	Location	Name
API Key	Header	x-api-key

Request body

Content-Type: application/json

Parameters

Parameter	Type	Required	Description
sessionId	string	Yes	Session ID obtained from the initiation step.
method	string	Yes	Selected verification method. Possible values: email, phone, phone_1, alternate_phone. The available methods for a specific BVN are those returned by BVN Initiate in data.methods[].

Request example

{
  "sessionId": "5f9b1a2c-3d4e-4f5a-8b6c-7d8e9f0a1b2c",
  "method": "phone"
}

Responses

200 Success

Response parameters

Parameter	Type	Description
serviceResultCode	integer	Code that indicates the overall result of the service execution. See Service Result Code
serviceTime	string	Processing time (milliseconds).
serviceResultLog	string	Descriptive field for the result of the service execution. Includes details when there is an error or exception in the module.
serviceTransactionId	string	Transaction identifier associated with the request processed by the API.
data	object	Object with the OTP send confirmation message. See table below.

Response parameters — data

Parameter	Type	Description
message	string	Confirmation message. Always "OTP sent successfully".

Service Result Code

The serviceResultCode indicates the overall result of the service execution:

serviceResultCode	Description	HTTP code
200	The service execution was successful, the module processed the request correctly.	200

Response example

{
  "serviceResultCode": 200,
  "serviceTime": "800",
  "serviceResultLog": "Success",
  "serviceTransactionId": "896b680c-78c6-5b7f-b20b-6c0256bd66de",
  "data": {
    "message": "OTP sent successfully"
  }
}

400 Bad Request

Error returned with the service envelope (serviceResultCode reflects the HTTP code of the response):

{
  "serviceResultCode": 400,
  "serviceResultLog": "Invalid session or method. Please check the details and try again",
  "serviceTime": "120",
  "serviceTransactionId": "08ac9699-dc9e-4cdc-81d7-264f71838309"
}

502 Bad Gateway

Returned when the service is temporarily unavailable or its response could not be interpreted. The body uses the service envelope with serviceResultCode: 500:

{
  "serviceResultCode": 500,
  "serviceResultLog": "Service temporarily unavailable. Please try again later",
  "serviceTime": "3000",
  "serviceTransactionId": "38de2932-0f2h-7gff-14g0-597h04161632"
}

504 Gateway Timeout

Timeout error, returned with the service envelope:

{
  "serviceResultCode": 504,
  "serviceResultLog": "Request timeout. Please try again",
  "serviceTime": "30000",
  "serviceTransactionId": "48ef3043-1g3i-8hgg-25h1-608i15272743"
}

Authentication errors (401/403) are rejected by the gateway before reaching the service and do not use the envelope serviceResultCode. Platform validation errors use the format application/problem+json. See Error handling for details of the three response forms.