BVN Accounts
Retrieve every bank account tied to a customer's Bank Verification Number (BVN) via the NIBSS iGree Consent Layer. This secure, three-step flow handles OTP generation and delivery entirely through NIBSS, ultimately returning the customer's full demographic profile alongside a detailed list of their linked bank accounts.
Verification Flow
The BVN Accounts flow runs through the NIBSS iGree Consent Layer. To retrieve the linked accounts, three calls must be made in strict sequence. Pass the requestId returned in Step 1 to Steps 2 and 3.
Submit the customer's BVN. NIBSS checks the record and returns the masked phone number and/or email address associated with it.
Save the meta.requestId from the response — it is required to authorize the next two steps.
Using the requestId, specify which masked contact channel (phone or email) should receive the OTP.
NIBSS securely dispatches a one-time passcode directly to the customer. Your server is never exposed to the OTP delivery logic.
Submit the requestId alongside the OTP provided by the customer to complete the consent layer.
On success, the response returns the customer's full demographic profile, NIN, a base64-encoded biometric face image, and a comprehensive array of all bank accounts linked to the BVN (including bank names, account numbers, and account types).
All endpoints require a valid Bearer token. Obtain one from the Access Token endpoint and pass it as Authorization: Bearer <token>.
The data.face_image is a base64 string that can be passed directly as the referenceImage in Face Compare to verify a live selfie against the BVN record. Additionally, the returned accounts array can be used to fuel account aggregation or further KYC checks.