BVN verification
Verify a customer's BVN to raise their KYC tier, which raises how much their wallets can hold and move each day.
Start a verification
POST/compliance/bvn-verification
| Body | Type | Description |
|---|---|---|
customerRefrequired | string | The customer to verify. |
If the provider already has the customer's consent, the BVN is verified immediately. Otherwise the verification is pending and the response carries a consentUrl to send the customer to.
201 Created
{
"message": "BVN verification initiated - awaiting consent",
"status": "OK",
"BvnVerification": {
"customerRef": "cust_1001",
"status": "pending",
"consentUrl": "https://…"
},
"tierChanged": false,
"sweeps": []
}| Status | Meaning |
|---|---|
201 | Verification started or completed. |
404 | No customer for this customerRef. |
422 | The customer has no BVN on file, or it isn't 11 digits. |
curl -X POST "https://usetreasurywire.com/api/v1/compliance/bvn-verification" \
-H "Authorization: Bearer $TREASURYWIRE_KEY" \
-H "Content-Type: application/json" \
-d '{
"customerRef": "cust_1001"
}'Get the latest verification
GET/compliance/bvn-verification/{customerRef}
Returns the customer's most recent attempt. Its status is pending, verified or failed (with a failureReason).
| Status | Meaning |
|---|---|
200 | Verification returned. |
404 | No verification for this customerRef. |
curl -X GET "https://usetreasurywire.com/api/v1/compliance/bvn-verification/cust_1001" \
-H "Authorization: Bearer $TREASURYWIRE_KEY"Re-check a pending verification
POST/compliance/bvn-verification/{customerRef}/poll
Asks the provider for the current status of a pending verification. When it has become verified, the customer's tier is raised and tierChanged is true.
Response
{
"message": "Successful",
"status": "OK",
"BvnVerification": {
"customerRef": "cust_1001",
"status": "verified"
},
"tierChanged": true,
"sweeps": []
}curl -X POST "https://usetreasurywire.com/api/v1/compliance/bvn-verification/cust_1001/poll" \
-H "Authorization: Bearer $TREASURYWIRE_KEY"