RBI Authentication Rules 2026: Easy Guide for WooCommerce

RBI authentication rules for WooCommerce: two keys and a phone confirming a rupee payment (TechBella Solutions)

If your WooCommerce store sells to customers in India, a new set of payment rules has been in force since April 2026. The Reserve Bank of India’s directions on authentication change how banks verify online payments, and store owners often hear about them only when a customer complains about a failed payment.

This guide to RBI authentication rules for WooCommerce stores explains what the RBI authentication rules say according to published summaries, who carries the duties and what you can do on your side. We could not read the original notification on the RBI site during our research, so we rely on two professional summaries and mark the points where they disagree.

PointWhat the summaries say
Issued and effectiveIssued 25 September 2025, compliance from 1 April 2026
Core ruleTwo factors of authentication unless exempted, with risk-based checks
Overseas card paymentsIssuers to validate non-recurring cross-border card-not-present payments by 1 October 2026
MerchantsDuties fall on banks, issuers and providers, and merchants see the effect through the gateway
A summary of the RBI authentication directions from two published summaries. Read the RBI notification for the exact text.

What the RBI authentication directions are

The Reserve Bank issued the Authentication Mechanisms for Digital Payment Transactions Directions, 2025 on 25 September 2025, and they apply from 1 April 2026, according to a KPMG summary and a Probe42 regulatory update. They cover domestic digital payments handled by banks and non-bank payment providers.

The core idea is that a digital payment needs at least two factors of authentication unless it is exempted. The factors are something the customer knows, something they have and something they are. Examples in the summaries include a PIN, an SMS code, a software token and a biometric. Probe42 says the RBI authentication rules do not force one specific factor, and that they allow alternatives beyond a text code.

What the summaries disagree on

The two summaries differ on one important detail. KPMG says at least one factor must be dynamic, meaning unique to each transaction, for digital payments other than card-present ones. Probe42 lists a dynamic factor as a core principle without that card-present carve-out. We cannot settle this from secondary sources, so treat it as a question for your payment provider and read the RBI text before you rely on either version.

Neither summary lists the exemptions in detail. Both say exceptions exist, including for certain cross-border transactions, but the specifics sit in the notification itself.

Risk-based checks and the October 2026 date

The summaries say issuers are expected to look at behavioural and contextual signals, such as device data, transaction history and location, and apply extra checks to risky payments. They also describe a rule for cross-border card-not-present payments: by 1 October 2026, card issuers must put in place a way to validate non-recurring overseas payments when a foreign merchant or acquirer asks for authentication.

If your store sells internationally, this is the part to watch. Some customers with Indian cards who buy from overseas stores may see extra authentication steps or declines. A store based in India that sells in rupees is mostly dealing with the domestic rules.

Who carries the duties under the RBI authentication rules

The duties fall on banks, card issuers and payment providers. Neither summary imposes obligations directly on merchants. That is good news, but it does not mean the rules are invisible. Your customers feel them at the payment step, and your orders show the effect as a different mix of successful, failed and abandoned payments.

Our practical reading is that merchants see the rules through their gateway’s flow and through issuers’ behaviour. Confirm details with your gateway before changing anything on your site.

What the RBI authentication rules mean for a store using CCAvenue

With a redirect or hosted payment page, the authentication step takes place on the gateway and bank side, not inside WooCommerce. Your store receives the result after the customer finishes. The free CCAvenue plugin for WooCommerce, which supports the India region and the classic checkout, simply passes the customer to that page and records the outcome.

The plugin cannot change how a bank authenticates, and it does not need to. What it should do is handle the result cleanly, which means the order status should update correctly after a success, a failure or a cancel. We explain the technical flow in our guide to CCAvenue payment methods and the CCAvenue plugin comparison.

Five steps for store owners

1. Check your payment mix

Compare the share of successful, failed and cancelled orders before and after April 2026. Use the same weeks and the same payment method. A rise in failed orders from mobile is a signal worth following up.

2. Keep your checkout simple and clear

If a payment needs an extra step, customers need a clear page to come back to. Make sure your thank-you and failed-payment pages explain what happened and what to do next. Our HPOS guide and WooCommerce 11 guide help you keep the store platform itself current, which matters for gateway compatibility.

3. Ask your gateway three questions

Ask whether the gateway supports the authentication methods banks now use, how it reports declined payments with a reason and whether it has guidance for international customers. Keep the answers in writing.

4. Test with your gateway’s sandbox

Use the sandbox mode to test the whole order flow, including a failed payment and a cancelled payment. Do not test with real cards on a live account.

5. Prepare your support replies

Write a short answer for customers whose payment was declined. Mention that the bank may ask for extra approval, that the customer can try again or use another method, and that the store never sees full card details.

Questions customers will ask

Shoppers rarely read regulation. They ask why they were asked for a code, why a code arrived late or why a payment failed after they approved it. Give your team one friendly answer for each and avoid blaming the bank, the gateway or the customer. A calm answer keeps the sale.

Where this fits with your other compliance work

Authentication sits next to other duties, such as tax and data protection. For India-based stores we recommend reading our PayGlocal vs CCAvenue comparison if you also sell overseas, and our WordPress security guide for the protections around your own site.

When to bring in a developer

If failed payments rise and you cannot tell whether the cause is the bank step, the gateway or your site, ask a developer to review the gateway logs and order notes. Our website maintenance team can trace a payment from checkout to the final order status.

A worked example of reading your orders

Imagine a store with 400 orders in March and 400 in May. In March, 78 were failed or cancelled, which is 19.5%. In May, 96 were failed or cancelled, which is 24%. That rise could come from many causes, including a stock problem, a price change, a slow site or the new authentication rules. The way to find out is to look at the details.

Open a sample of failed orders and read the order notes written by the payment plugin. Group them by reason: declined by the bank, cancelled by the customer, payment page closed or timeout. If most are cancelled by the customer at the authentication step, the checkout message and support reply are your best fix. If most are declines, talk to your gateway. If many are timeouts, talk to your host.

This example uses made-up numbers only to show the method. Use your own data and avoid reading too much into a single month.

Things you should not do

Do not store card numbers or one-time codes anywhere on your own site, even for convenience. Do not ask customers to send a code by email or chat, because that is exactly what fraudsters do. Do not tell customers that a payment will always go through, and do not promise a refund timeline you do not control. If a customer says they approved a payment and were charged but have no order, check your gateway dashboard before you answer, because the order may be waiting for the status update.

Keeping the store ready for change

Rules like these keep moving, so build a habit of checking official sources every quarter. Subscribe to your gateway’s notices, ask your bank about changes and review your payment plugin’s update notes before each WooCommerce upgrade. A store that tests on a staging copy before every update seldom has a surprise at checkout, and that is worth more than any single rule.

Questions to ask your gateway

When you write to your payment gateway, keep the message short and specific. Ask how they describe the authentication changes to merchants, whether any settings on your account need review, how declined payments are reported and whether international cards are treated differently. Ask for answers by email, and keep them with your payment records. A written answer from the gateway is worth more than a dozen blog posts, ours included, because the gateway knows your account.

Keeping your records tidy

Keep a dated folder with the gateway’s emails, your test results and any notes about changes to your checkout. If a bank, an auditor or a customer asks what you did when the rules changed, you can show them in minutes. Store the folder somewhere safe, limit access to the people who need it and leave out keys and card data.

RBI authentication rules: a quick summary

The RBI authentication rules, in force since April 2026, ask for two factors of authentication on domestic digital payments unless exempted, with risk-based checks by issuers. The duties fall on banks, issuers and providers, and WooCommerce stores feel the RBI authentication rules through their gateway’s payment flow. Track your payment mix, keep your checkout pages clear, ask your gateway three questions and test in sandbox mode. Read the RBI notification for the exact text.

Key takeaways on rbi authentication rules

  • The RBI authentication rules apply to banks, issuers and payment providers, and stores feel them through the payment flow.
  • The RBI authentication rules ask for two factors unless a payment is exempted.
  • Check your payment mix before and after April 2026, because the RBI authentication rules can change the balance of paid, failed and abandoned orders.
  • Ask your gateway in writing how it applies the RBI authentication rules to your account.
  • Test failed and cancelled payments in sandbox mode, since the RBI authentication rules add steps customers may abandon.
  • Keep support replies ready, because shoppers will ask why they were asked to approve a payment.
  • Read the RBI notification for the exact wording of the RBI authentication rules, and treat secondary summaries as a guide only.
  • Review the RBI authentication rules each quarter, because the details around cross-border payments continue to develop.

Selling in India with CCAvenue?

The free CCAvenue plugin for WooCommerce supports the India region with the classic checkout. Pro adds the UAE region and Blocks checkout. Both are independent plugins and need your own CCAvenue merchant account.

See free vs Pro

Frequently Asked Questions

Do the RBI authentication rules apply to my WooCommerce store?

They apply to banks, issuers and payment providers, not directly to merchants, according to published summaries. You feel them through your gateway’s payment flow and issuer behaviour.

Is an SMS code still allowed?

The summaries say the RBI authentication rules do not force one factor and allow alternatives, so an SMS code can still be one factor. Which method a customer sees depends on their bank.

Do the rules affect international sales?

A cross-border card-not-present validation requirement for issuers is dated 1 October 2026 in one summary. Customers with Indian cards may see extra checks on overseas purchases.

Where can I read the official text?

On the Reserve Bank of India website under its notifications. Your payment gateway can also tell you how it handles the rules.

Share This Article:

Start a project

Having a project idea in mind?

Tell us what you are building. A few lines about your goals are enough to start.

  • What you want to achieve
  • Your current website or setup
  • Deadlines and a rough budget