Category
Validate Angolan banking identifiers and detect the issuing bank.
The validation family covers `/api/v1/validate/iban` and `/api/v1/validate/bank-account`. Both routes normalize input, detect the bank from the banking code, and return a generated bank badge image for UI use.
Routes
2 GET
Country scope
Angola
Visual output
Bank badge image
Routes in this family
#| Route | Purpose | Key query |
|---|---|---|
| /api/v1/validate/iban | Validate AO-format IBANs with mod-97 checks and bank lookup. | iban |
| /api/v1/validate/bank-account | Validate 21-digit local account structures and derive the matching IBAN. | account |
GET /api/v1/validate/iban
#Use this route when you already have a full AO IBAN and need normalized parts, bank metadata, and validation flags.
- Check `validation.mod97Valid` and `validation.bankCodeKnown` instead of relying on `isValid` alone when you need granular UI states.
- Use `bank.image` directly in payment summaries or verification cards.
| Parameter | Required | Description |
|---|---|---|
| iban | Yes | AO-format IBAN. The handler trims separators and uppercases the value before checking it. |
cURL usage
200 response
Error response
GET /api/v1/validate/bank-account
#Use this route for local 21-digit account strings when you need structural validation and the matching derived IBAN.
- This is structural validation, not confirmation that the account is active in the banking network.
- Persist the normalized account or derived IBAN rather than the raw input string.
| Parameter | Required | Description |
|---|---|---|
| account | Yes | Local Angolan account string with 21 digits. Non-digit separators are ignored. |
cURL usage
200 response
Error response