IRCTC Authorised Principal Service Provider +91 91091 35959 · 24 hours, 7 days
SiOnline Technomart
Banking

What is BHIM Aadhaar Pay?

BHIM Aadhaar Pay

BHIM Aadhaar Pay enables a participating merchant to receive payment from a customer through Aadhaar authentication under the supported banking arrangement. It is a purchase-payment use case, not simply another name for withdrawing cash at an AEPS counter. The merchant’s acquiring-bank setup and the customer’s applicable account conditions matter.

Definition and naming: see official sources
In this explanation

What is the customer doing?

The customer is paying a merchant for a purchase or service through the supported Aadhaar-based payment arrangement. The intended direction of the transaction is the important distinction: money is being paid to the merchant, rather than the merchant handing the customer cash from a withdrawal.

RBI’s published payment-infrastructure guidance describes certified biometric scanner devices facilitating Aadhaar authentication for merchant payment acceptance through BHIM Aadhaar Pay. RBI also includes BHIM Aadhaar Pay in its payment-system overview.

A retailer should identify the actual transaction type before asking the customer to authenticate anything. The customer needs to understand what amount and purpose are being authorised.

Who is involved in the payment?

ParticipantRelevant role
CustomerAuthorises the intended payment through the supported process
Customer’s bankHolds the relevant account and handles the banking side
MerchantAccepts the payment under its enabled arrangement
Acquiring bankProvides the merchant-side arrangement
Aadhaar authentication systemSupports identity authentication for the request

The shop and the bank are different participants. A merchant’s access to a payment facility does not make the shop a bank or give it control over the customer’s account rules.

How is this different from AEPS cash withdrawal?

In a cash-withdrawal interaction, the customer’s purpose is to receive cash through the supported banking service. In a merchant payment, the customer’s purpose is to pay for something.

Both may involve Aadhaar-related banking infrastructure, but that shared context does not make the customer’s authorisation interchangeable. A retailer must not describe a merchant payment as a balance enquiry or ask for authentication without explaining the transaction.

Our AEPS explanation covers the banking-counter context. Keep it separate from this purchase-payment explanation when discussing a customer’s receipt or complaint.

Does every biometric scanner support the service?

No such conclusion follows merely from owning a scanner. The service needs the appropriate merchant-side arrangement. RBI’s cited description specifically identifies certified biometric scanner devices facilitating Aadhaar authentication for merchant payment acceptance.

Confirm the actual requirements with the acquiring bank or authorised provider. Device certification, software compatibility, merchant onboarding and service activation are related but separate checks.

Do not promise that buying a device automatically enables BHIM Aadhaar Pay, or that every existing AEPS retailer account includes it. Service availability must be established for the specific merchant arrangement.

An example at a small shop

Illustrative example: A customer wants to pay for a purchase using an Aadhaar-based merchant-payment facility. The shopkeeper first confirms that the facility is enabled, explains the purchase amount and obtains the customer’s informed participation in the official process.

After the request, the shopkeeper reads the actual transaction result and supplies the appropriate record. They do not treat a successful fingerprint capture alone as proof that the bank payment was completed.

If the response is unclear, the shopkeeper checks the original transaction before submitting another payment. The customer should not be asked to authenticate repeated attempts without knowing which previous attempt may already have succeeded.

Questions about BHIM Aadhaar Pay

Is it a way to withdraw money from any shop?

The merchant-payment purpose is different from cash withdrawal. Use the correctly enabled service for the customer’s intended transaction.

Does Aadhaar authentication alone confirm payment?

No. Identity authentication and the bank-payment outcome are separate parts of the process. Read the transaction result.

Does SiOnline automatically provide this to every retailer?

Do not assume so. Ask about the actual supported service and bank arrangement. A glossary explanation does not establish availability on an individual account.

Who should investigate an incorrect debit?

Use the responsible bank or payment provider’s official complaint process with the actual reference, amount and status. A retailer cannot decide the outcome simply from the product name.

Sources and editorial notes

Checked 12 November 2026

This explanation uses the following published sources. Check the responsible authority’s current guidance before acting on a requirement.

  1. Published payment-infrastructure guidance

    Supports the linked explanation above. Provider-specific examples and dated guidance are identified in the article.

  2. Payment-system overview

    Supports the linked explanation above. Provider-specific examples and dated guidance are identified in the article.

Written by the SiOnline Team. Read our editorial approach or report a correction.

Explore digital services for your shop.

Tell us which services you want to add to your counter. We can explain current SiOnline access and requirements; the relevant bank, operator or authority controls its own service decisions.

  • No payment to send an enquiry
  • Check requirements and charges before you commit
  • Get guidance for your shop’s service needs
Explore retailer registration
Need help with an existing SiOnline service?Contact supportPrefer to call? +91 91091 35959

Ask about service access

Tell us a little about your counter. Fields marked * are required.

Service enquiry

No payment required. This is an enquiry, not a completed registration.