AEPS debit disabled or declined: causes, checks

A customer puts a finger on the scanner, you wait a few seconds, and the screen says the transaction was declined. There’s a queue behind them. You need to know quickly whether to try again, change something at your end, or send the customer to their bank.

Here’s the thing: one AEPS transaction passes through several hands. You and your device are at the counter. The Unique Identification Authority of India (UIDAI) checks the Aadhaar fingerprint. The customer’s bank decides what happens to the account. The National Payments Corporation of India (NPCI) runs the network that connects them all. When something goes wrong, your screen may show only your operator software’s own wording, not the original code.

The steps below come from RBI, UIDAI and Government of India documents. Your provider’s own guide has the final word on how its messages are worded. To confirm what SiOnline offers for your location, ask SiOnline support.

What does the message tell you?

Write down the exact message before you touch anything. UIDAI publishes error codes for failed authentication, and your software may show the code, a translation of it, or a sentence of its own.

The table below gives UIDAI’s wording for the codes that matter most when a fingerprint withdrawal fails, as of 17 October 2026 (UIDAI authentication FAQ). The “likely area” column is our plain-language guide. It isn’t UIDAI’s own classification.

UIDAI’s registered devices specification also lists codes for the Registered Device (RD) service, which is the software that runs your scanner (UIDAI Registered Devices specification 2.0).

There’s a catch. UIDAI’s authentication error list uses some of the same numbers for other meanings (740 there is “Missing OTP data”), so ask your provider which list a number on your screen comes from. Your screen may show none of these. If all you see is a general “transaction declined”, you can’t read the cause from it. Ask your provider which of its messages map to which reason.

Cause 1: the fingerprint didn’t match or didn’t capture

This is the quickest check, so do it first.

Check. Look for words like “biometric did not match” or “capture failed”. Then look at the customer’s finger and at the scanner glass.

Fix. UIDAI advises retrying with the finger placed correctly and pressed properly, trying a different finger, and cleaning both the scanner and the fingers (UIDAI authentication FAQ). Authentication can be done with any of the ten fingers, so don’t keep forcing the same one.

If it didn’t work. UIDAI says that if biometric authentication fails again and again, the holder may go to an Aadhaar update centre and get the biometrics updated. The same goes for code 811, where UIDAI’s records hold no biometric data for that Aadhaar number.

UIDAI also says service providers will have alternate processes, including exception handling at the point of presence, for poor fingerprint quality. What your AEPS provider offers is its own matter, so ask it. If the same device fails for several customers, go to Cause 2.

Cause 2: the registered device or its RD service

Check. Does the failure repeat across different customers and different fingers? Does the message mention the device, the capture or a certificate?

What you’ll see if this is the cause. The device times out, or says it isn’t ready or is in use somewhere else.

Fix. UIDAI allows only Registered Devices in the Aadhaar authentication system (UIDAI biometric devices page, last updated 16 July 2026). Device certificates and RD service versions can expire or be replaced by newer ones. A UIDAI letter of 16 April 2025 asks requesting entities to upgrade the RD service of L1 fingerprint devices to the versions it lists (UIDAI letter).

So close any other program that might be using the scanner, and follow the device maker’s own instructions for updating the RD service. Don’t install RD software from a link you don’t know.

If it didn’t work. Ask the device maker or your provider, in writing, whether the RD service version and the certificate are current, and which device they support.

Cause 3: the customer has locked their biometrics

Check. The message says biometrics are locked, or code 330 appears. It’s fine to ask the customer whether they’ve locked them.

What you’ll see if this is the cause. Every fingerprint attempt fails, however clean the finger. UIDAI says that while biometrics are locked, no entity can run biometric-based Aadhaar authentication for that holder. So the lock is doing its job. The lock doesn’t affect OTP-based authentication, but which modes a bank accepts for an AEPS withdrawal is for the bank or your provider to say.

Fix. Only the customer can change this. UIDAI says the holder can lift the lock through the UIDAI website, an enrolment centre, an Aadhaar Seva Kendra or the Aadhaar app, and that a registered mobile number is needed.

A temporary lift lasts only a short time. UIDAI’s regulations, as updated, tie it to a period the Authority specifies, and UIDAI’s FAQ says it is generally 15 minutes or a single authentication transaction (UIDAI regulations, as updated). So the customer should lift the lock just before you retry, not ten minutes earlier while waiting in line.

One firm rule for you: never ask for the customer’s OTP, and never try to lift the lock for them.

If it didn’t work. If the customer has no registered mobile number, UIDAI directs them to the nearest enrolment centre or mobile update end point.

Cause 4: AEPS is switched off at the customer’s bank

Check. The fingerprint was accepted but the transaction still failed, or the message mentions the account, the bank or a limit.

What the official documents say. In a reply to the Rajya Sabha dated 31 July 2024, the Ministry of Home Affairs said NPCI advised member banks to disable AEPS for specific categories of accounts, and to give customers more than one way to turn AEPS debit on or off (Rajya Sabha Starred Question 105). That reply is more than two years old, so check with the bank what applies today.

Fix. Only the customer’s own bank can say whether AEPS debit is enabled on the account and how to switch it on. Ask the customer to call or visit the bank. Don’t guess at the reason, and don’t promise that a retry will work.

If it didn’t work. If the bank’s message mentions Aadhaar seeding, or anything else you don’t recognise, ask the bank to explain it.

Cause 5: the operator’s status or a network failure

Check. Are other customers failing at your counter too, on more than one device, with the same message? A network problem or a bank outage looks exactly the same. So treat this as a clue about what to ask, not as a finding.

What the RBI directions say. The acquiring bank is the bank that onboards the operator. If the operator has done no transaction for three months, it must carry out the operator’s KYC before enabling further transactions. It must also set operational parameters based on each operator’s risk profile (RBI circular, 27 June 2025, in force from 1 January 2026). RBI’s 2019 circular also lists broken communication links and session time-outs among the reasons a transaction can fail for causes outside the customer’s control.

Fix. Check your internet connection and retry once. If it fails again, ask your provider whether its service or the bank’s is down. Then ask the acquiring bank, in writing, whether your onboarding, KYC or operational parameters have changed. Keep the reply.

A quick example of working through it

Say a customer comes in for a withdrawal and the first attempt fails with a message about the biometric not matching. You wipe the scanner glass, the customer wipes their fingers, and they try a different finger. It fails again. A few minutes later a second customer fails on the same device.

That pattern tells you something. If two different people fail on the same scanner, it’s less likely to be one person’s fingerprint, so you move to Cause 2 and ask your provider about the RD service and the certificate. Then a third customer comes in and the message says biometrics are locked. That’s a different cause, and nothing on your side can fix it. The customer has to lift the lock, and you retry straight after.

This is only an example of the order to check things in. Your own screen and your provider’s guide decide what applies.

What if the account was debited but the transaction wasn’t confirmed?

Don’t hand over cash unless the final screen shows success. If the customer says they got a debit message on their phone, note the time.

RBI’s circular of 20 September 2019 on turn-around time (TAT) for failed transactions covers the Aadhaar Enabled Payment System. For “account debited but transaction confirmation not received at merchant location”, the acquirer is to start a “Credit Adjustment” within T + 5 days, with ₹100 per day as compensation for any delay beyond that. T is the day of the transaction (RBI circular DPSS.CO.PD No.629/02.01.014/2019-20). The compensation is to be paid without waiting for a complaint. A customer who still doesn’t get redress can complain under the Reserve Bank - Integrated Ombudsman Scheme, 2021.

This is an earlier edition of RBI’s framework and may have been changed since, so ask the customer’s bank which timeline applies today. Give the customer the date, time, amount and reference number from your screen to take to the bank’s customer care. Raise the case with your own provider as well.

What to record and who to contact

For every failed transaction, note the date, time, amount, the exact message, the reference number and which device you used. Don’t write down a customer’s full Aadhaar number or an OTP, in a notebook or in a chat.

For a device problem, contact its maker or your provider. For an account problem, the customer contacts their bank. For SiOnline, see support, customer care or the Help Centre. Never share a password or OTP with anyone who contacts you, even if they say they’re from a bank.

Questions counter owners ask

Why is AEPS debit disabled on a customer’s account? NPCI advised banks to disable AEPS for specific categories of accounts, as one of its AEPS security measures (see Cause 4). The reason for a particular account sits with that bank, so the customer needs to ask it.

What if the bank’s message mentions Aadhaar seeding? None of the sources used here explains that message. Ask the bank what it means and whether AEPS debit is switched on for the account.

How long does an AEPS refund take? RBI’s circular of 20 September 2019 gives the acquirer T + 5 days to start a credit adjustment where the account was debited but confirmation wasn’t received. RBI may have revised it, so ask the bank which timeline applies today.

Sources

• UIDAI, Authentication FAQ, last reviewed 9 October 2026; retrieved 17 October 2026.
• UIDAI, Aadhaar Registered Devices Specification 2.0 (Rev 7), January 2022; retrieved 17 October 2026.
• UIDAI, Biometric Devices, last updated 16 July 2026; retrieved 17 October 2026.
• UIDAI, letter F. no. HQ-13021/1/2021-AUTH-I HQ, 16 April 2025; retrieved 17 October 2026.
• UIDAI, Aadhaar (Authentication and Offline Verification) Regulations, 2021, as updated; retrieved 17 October 2026.
• Reserve Bank of India, Harmonisation of Turn Around Time and customer compensation for failed transactions, 20 September 2019; retrieved 17 October 2026.
• Reserve Bank of India, Due Diligence of AePS Touchpoint Operators, 27 June 2025; retrieved 17 October 2026.
• Ministry of Home Affairs, Rajya Sabha Starred Question 105, 31 July 2024; retrieved 17 October 2026.

This page reflects the sources above as of 17 October 2026. Rules, limits and circulars change; confirm them at the source before you act.