Bank Verification

Two related things happen under bank verification:

1. Bank identification — checking that a bank name/ID is one AdeyVerify recognizes, against a curated directory of Ethiopian banks (source: INTERNAL_DIRECTORY).
2. Account holder-name resolution (optional) — when you also supply an account number, AdeyVerify additionally resolves the account holder's name via a third-party lookup (source: THIRD_PARTY_PROVIDER).

Identify a bankCopy Anchor Link

curl -X POST https://your-api/api/v1/verify/banks \
  -H "Authorization: Bearer av_test_..." \
  -H "Content-Type: application/json" \
  -d '{"bank": "Commercial Bank of Ethiopia"}'

Resolve an account holder's nameCopy Anchor Link

Add bankAccount to the same endpoint, or use the dedicated endpoint that requires it:

curl -X POST https://your-api/api/v1/verify/bank-accounts \
  -H "Authorization: Bearer av_test_..." \
  -H "Content-Type: application/json" \
  -d '{"bank": "Commercial Bank of Ethiopia", "bankAccount": "1000123456789"}'

{
  "status": "VERIFIED",
  "source": "THIRD_PARTY_PROVIDER",
  "bank": { "name": "Commercial Bank of Ethiopia", "institutionId": "231402", "isSupported": true },
  "accountHolderName": "JOHN DOE",
  "errors": []
}

Not every bank supports name resolutionCopy Anchor Link

Not every bank in the directory has a third-party lookup available. When it doesn't, you get status: "REQUIRES_REVIEW" with a clear message — never a guess or a silently wrong result.

Status valuesCopy Anchor Link

See the full request/response schema and try it live: POST /verify/banks, POST /verify/bank-accounts, GET /verify/banks/directory.