Account title fetch is the process of retrieving the registered name, or "title", of a bank account from its account number before a payment is sent. The sender's bank sends a lookup request to the recipient's bank, usually through the national payment switch, and displays the account holder's name so the payer can confirm it is the person or business they intend to pay. Once the payer accepts, the transfer goes ahead.
The term is widely used in Pakistan, where banking apps fetch the title over the 1LINK interbank switch and the State Bank of Pakistan's Raast instant payment system. Similar checks exist elsewhere under other names: name enquiry in Nigeria, beneficiary name lookup in India, Verification of Payee (VoP) in the euro area and Confirmation of Payee in the United Kingdom. All aim to cut misdirected payments and fraud on fast, irreversible transfers.
Account title fetch in plain terms
Imagine posting a parcel and the post office, before taking it, reads out the name of the person who lives at the address on the label. If the name is not the friend expected, the sender can stop and check the address instead of losing the parcel.
Title fetch does the same for money. Account numbers are long and easy to mistype, and fraudsters sometimes send fake bank details. Showing the real account name at the moment of payment gives the sender one last chance to notice something is wrong, before the money leaves and can no longer be pulled back.
How the lookup works
- The payer enters the recipient's account number or IBAN, and sometimes selects the recipient's bank.
- The sending bank sends a name enquiry message through the switch or directly via an API.
- The beneficiary bank checks its core banking system and returns the account title, or a result such as "account not found".
- The sending app shows the name, and the payer confirms or cancels.
- If confirmed, the payment is sent over the relevant rail, often an instant payment system.
The whole check takes a second or two. It is free to the customer in most systems because it reduces costly errors and complaints for the banks themselves.
Title fetch compared with name-matching schemes
There are two broad designs. In a title fetch, the bank returns the full registered name and the payer judges whether it is right. In a name-matching scheme, the payer types the name they expect, and the recipient's bank compares it and returns only a result.
| System | Where | What the payer sees |
|---|---|---|
| Title fetch | Pakistan (1LINK, Raast) | The registered account name |
| Beneficiary name lookup | India (RTGS and NEFT since April 2025; built into UPI) | The registered account name |
| Confirmation of Payee | United Kingdom (since 2020) | Match, close match with the actual name, no match, or unavailable |
| Verification of Payee | Euro area (mandatory from 9 October 2025) | Match, close match, no match, or check not possible |
India's Reserve Bank required all direct and sub-members of RTGS and NEFT to offer free beneficiary name lookup by 1 April 2025, bringing the feature already familiar from the Unified Payments Interface (UPI) to traditional transfers. In the EU, the Instant Payments Regulation made payee verification mandatory for euro credit transfers, both instant and standard, from 9 October 2025. In the UK, Confirmation of Payee began with the largest banking groups in 2020 and was later extended across most firms sending Faster Payments.
Uses beyond retail transfers
- Fraud prevention. A name check is a key defence against authorised push payment fraud and invoice redirection, where a fraudster supplies their own account details.
- Payouts and payroll. Businesses verify recipient accounts before bulk disbursements, and payout aggregators use name lookups to reduce returns.
- Onboarding. Fintech apps check that a linked bank account belongs to the same person who passed Know Your Customer (KYC) checks, a mismatch that can point to a mule account.
- Cross-border payments. Remittance providers use local name enquiry services to confirm the receiving account before paying out, which reduces beneficiary-account mismatches.
Limitations and privacy concerns
Title fetch only confirms that the account exists and whose name it is in. It cannot tell the payer whether the person is honest. A fraudster who opens an account in a plausible name, or who uses a mule account in the victim's expected name, can still pass the check. Business names also cause confusion when the registered title differs from the trading name.
Returning a full name raises data privacy questions. Anyone who knows or guesses an account number can learn the owner's name, and automated tools could test many numbers in a row. Systems manage this with rate limits, logging, partial masking of names, and in match-based designs by never disclosing the name unless it is close to what the payer typed. Banks must also keep their account titles accurate, since a fetch is only as good as the data in the recipient bank's records.