Name Enquiry
Overview
The Name Enquiry endpoint retrieves the registered account name for a given account number and bank code.
Important
Always perform name enquiry before initiating transfers to ensure funds reach the intended recipient.
Endpoint
GET /waas/Transaction/nameEnquiry
Request Parameters
Required Headers
| Header | Value |
|---|---|
Authorization | Bearer <access_token> |
Ocp-Apim-Subscription-Key | Your access subscription key |
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
accountNo | string | Yes | Beneficiary account number |
bankCode | string | Yes | Bank-specific code (see Bank Codes table) |
Bank Codes
| Bank | Bank Code |
|---|---|
| Access Bank | 044 |
| GTBank | 058 |
| Zenith Bank | 057 |
| First Bank | 011 |
| UBA | 033 |
| Fidelity Bank | 070 |
| FCMB | 214 |
Request Example
curl -X GET "https://api-sandbox.accessbankplc.com/waas/Transaction/nameEnquiry?accountNo=0702334455&bankCode=044" \
-H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
Response
Success Response
{
"succeeded": true,
"code": "200",
"message": "successful request",
"data": {
"accountNumber": "0702334455",
"accountName": "JOHN DOE",
"bankCode": "044"
},
"pageMeta": {},
"errors": {}
}
Error Handling
| Code | Message | Cause |
|---|---|---|
31 | Invalid account number | Account doesn't exist |
400 | Bad Request | Missing or invalid parameters |
Best Practices
- Always verify before transfers
- Display name to user for confirmation
- Cache results (5 minutes) to reduce API calls
- Handle errors gracefully with user-friendly messages
Next Step
After name verification, choose the appropriate transfer operation:
- Wallet-to-Wallet Transfer — between wallets in the same ecosystem
- Wallet to Access Bank — to any Access Bank account
- Wallet to Other Bank — to accounts in other Nigerian banks