Nigeria BVN Verification

overview the nigeria bvn verification api allows organizations to verify an individual's identity details against the bank verification number (bvn) database in nigeria this api is crucial for financial institutions, telecom companies, and other service providers that require accurate identity verification to comply with kyc (know your customer) and aml (anti money laundering) regulations use case kyc compliance institutions perform bvn checks to comply with know your customer (kyc) regulations, ensuring all customer data is verified and up to date mobile wallet verification fintech companies offering mobile wallet services use the api to confirm user identities before activating their accounts, enhancing security measures fraud prevention by confirming personal details with the bvn database, financial services can detect and prevent fraudulent activities, protecting both the institution and its customers insurance claim processing insurance companies utilize bvn verification to authenticate the identity of claimants, reducing the risk of fraudulent claims api details request body preproduction curl location 'https //api preproduction signzy app/api/v3/global kyc verify/ng/bvn' \\ \ header 'authorization < auth token >' \\ \ header 'content type application/json' \\ \ data raw '{ "firstname" "abu", "lastname" "salim", "middlename" "damu", "dateofbirth" "1968 10 18", "gender" "male", "phonenumber" "8079374852", "identityinformation" { "nationalidnumber" "22253395872" }, "consent" true }' production curl location 'https //api signzy app/api/v3/global kyc verify/ng/bvn' \\ \ header 'authorization < auth token >' \\ \ header 'content type application/json' \\ \ data raw '{ "firstname" "abu", "lastname" "salim", "middlename" "damu", "dateofbirth" "1968 10 18", "gender" "male", "phonenumber" "8079374852", "identityinformation" { "nationalidnumber" "22253395872" }, "consent" true }' request body parameters parameter type description required/optional firstname string first name of the person required lastname string last name of the person required middlename string middle name of the person optional dateofbirth string date of birth of the person in yyyy mm dd format required gender string gender of the person male/female optional phonenumber string phone number associated with the inidividual optional nationalidnumber string 13 digit national id number required consent boolean consent of the end user for verification of his/her data required response { "result" { "verificationresult" { "firstname" true, "middlename" true, "lastname" true, "dateofbirth" true, "gender" true, "phonenumber" true, "nationalidnumber" true } } } response body parameters parameter description data type firstname the api returns a boolean value ("true" for a match found and "false" for no match found) boolean middlename the api returns a boolean value ("true" for a match found and "false" for no match found) boolean lastname the api returns a boolean value ("true" for a match found and "false" for no match found) boolean dateofbirth the api returns a boolean value ("true" for a match found and "false" for no match found) boolean gender the api returns a boolean value ("true" for a match found and "false" for no match found) boolean phonenumber the api returns a boolean value ("true" for a match found and "false" for no match found) boolean nationaidnumber the api returns a boolean value ("true" for a match found and "false" for no match found) boolean error code and response mapping 400 (bad request) { "error" { "name" "error", "message" "bad input and description ", "status" 400, "reason" "validation error", "type" "bad request", "statuscode" 400 } } 401(unauthorized) { "error" { "name" "error", "message" "invalid authentication credentials", "status" 401, "reason" "authentication error", "type" "bad request", "statuscode" 401 } } 403 (forbidden) { "error" { "name" "error", "message" "forbidden", "reason" "error", "type" "bad request", "statuscode" "403" } } 500 (internal server error) { "error" { "name" "error", "message" "internal server error", "status" 500, "reason" "error", "type" "bad request", "statuscode" 500 } } 409(upstream down { "error" { "name" "error", "message" "upstream down", "status" 409, "reason" "error", "type" "bad request", "statuscode" 409 } } field type description name string text displayed on the screen explaining error type reason string reason for the error status number http status code message string error message indicating an upstream error type string error type statuscode number status code representing the error scenario getting help please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better you can reach out to us at we strive to provide prompt and reliable assistance, ensuring your queries are addressed effectively we value your feedback and are committed to making your experience smooth and enjoyable our team is dedicated to assisting you with any needs you may have thank you for choosing our services we look forward to helping you!