
A recurring payment is convenient precisely because it asks you to make fewer decisions each month. That convenience also makes the initial decision unusually important. UPI AutoPay is not simply a reminder that a bill is due: it is an electronic mandate, created through a UPI-enabled payment journey, that tells participating payment institutions to execute recurring debits within the terms you approve. Understanding the merchant, amount, frequency, validity and management controls before authorising that instruction makes the difference between useful automation and a forgotten debit.
This guide explains the mechanism in plain language, distinguishes registration from later execution, describes the notifications and authentication rules currently published by NPCI and RBI, and offers a practical way to review mandates. It is educational information, not a recommendation to use any financial product. Individual app screens, bank rules and merchant conditions may differ; the final mandate screen and your bank’s current instructions govern your particular payment.
1. What a UPI AutoPay mandate actually is
NPCI describes UPI AutoPay as a mandate registered by a user to enable automated debits for recurring payments. In everyday terms, a user gives a payment instruction for a defined purpose, usually to a named merchant, with an amount or maximum amount, a recurrence pattern and a validity period. The bank and payment participants can then process eligible future executions without asking the user to enter a UPI PIN afresh for every ordinary recurring debit below the applicable threshold. The mandate is therefore more than a stored card number or a calendar reminder: it is standing authority with details that matter.
Common examples include a mobile or electricity bill, an OTT subscription, an insurance premium, a mutual-fund subscription, a loan repayment or an EMI collection. The exact payment type and its rules matter. A fixed monthly subscription and a variable utility bill do not have the same amount pattern; a one-time payment is not a recurring mandate at all. The name “AutoPay” does not tell you whether a particular merchant will use a fixed amount, a variable amount capped at a stated maximum, or a particular execution date. Read the specific request rather than relying on the feature name.
Every successfully registered mandate has a Unique Mandate Number (UMN), according to NPCI’s consolidated UPI circular. That identifier is useful when matching an app entry or notification to a later bank message or complaint. Preserve the merchant name, amount, date, and UMN shown in the notice. Those details help distinguish two subscriptions with similar names and make it easier to describe which instruction you mean if something goes wrong.
2. The creation journey: what is being approved
A typical journey begins on a merchant’s website or app, or in a UPI application. The merchant asks the customer to set up a recurring payment, and the user is directed to a UPI app to review the request. NPCI’s published AutoPay guidance says the user checks the mandate information and authorises registration using the UPI PIN. Exact screens vary between apps and merchants, but the information should let the user identify who will collect, what amount or limit applies, how often execution can occur, which account is linked, and when the mandate starts and ends.
Pause before authorising if the merchant identity is unfamiliar, the purpose does not match what you intended to buy, the amount is different from the offer, or the validity period is unexpectedly long. A successful one-time setup can enable repeated debits, so a quick “approve” tap is not equivalent to confirming one ordinary payment. For variable mandates, pay particular attention to any maximum amount; for fixed mandates, check the recurring sum itself. Check whether the offer is a free trial that converts to paid service and when that conversion occurs. Those commercial terms come from the merchant, not from UPI’s payment rail.
The user’s UPI PIN is part of the authorisation flow. NPCI’s UPI guidance states that the app does not store or read the PIN and that a bank’s customer support will never ask for it. Enter it only in the trusted UPI app’s own authorisation screen. Do not share it with a caller, merchant representative, support agent or person claiming to help cancel a mandate. A legitimate support conversation may ask for a transaction reference or mandate identifier, but not for the PIN or an OTP as a way to “reverse” a debit.
3. A mandate has boundaries, not just a price
Amount is only one dimension of the instruction. A useful review also considers the recurrence interval, start and end dates, the selected bank account, the merchant, the reason for debit and any maximum value. A mandate with an annual validity period can still generate many monthly debits; a low amount can add up over time; and a variable mandate can change with a bill, provided the debit stays within what was authorised. The user should understand the repeat pattern and the outer boundary, not only the first payment.
NPCI’s consolidated circular says every UPI mandate must specify its validity period. It also calls for fixed-amount or variable-amount mandates; for a variable-amount mandate, the remitter bank must provide a facility for the user to specify a maximum value for any recurring transaction. The circular separately states that the user should be able to modify the validity period, and that the merchant should provide a way to modify the amount. Availability and presentation of these functions may be implemented differently in each payment app or merchant interface, so look for the current controls rather than assuming a setting exists in one particular place.
There may also be a distinction between the value that the user sees for one execution and a larger outer mandate limit. A request might show a fixed amount, or show that the amount can vary up to a ceiling. The maximum is not automatically a prediction of the next debit; it is a boundary the mandate may permit. Conversely, a currently small bill does not prove that the future amount will remain the same. When the merchant changes a price or plan, check whether the change is covered by the existing instruction or whether a new consent is required under the merchant’s process.
4. First payment and subsequent payments are different
Authentication rules distinguish setting up the instruction from using it later. NPCI’s consolidated circular says the first UPI AutoPay transaction is subject to Additional Factor of Authentication (AFA). The first transaction and mandate registration may be combined when execution follows within five minutes of registration, subject to the applicable transaction limit and merchant category. After that, eligible subsequent recurring debits may not require a fresh user AFA for each execution when they remain within the applicable threshold; executions above that threshold require AFA. This is why a user can be asked for a UPI PIN when creating a mandate and not asked to enter it on an ordinary later debit.
That difference is not a loophole and does not mean a mandate is “unsecured.” The initial act is the user’s explicit approval of a standing instruction, while the later payment is checked against that approved mandate and the applicable rules. But it also means users should treat the registration screen with care: the fact that a later debit might not prompt for a PIN does not make it a surprise if it is within a correctly authorised mandate. The user should keep the original confirmation and subsequent notices so the authorisation can be compared with each execution.
NPCI’s current public guidance and consolidated circular distinguish the general ₹15,000 threshold from a ₹1,00,000 threshold for specified categories. The larger threshold applies to eligible credit-card bill payments, mutual-fund subscriptions and insurance payments, with the applicable merchant category code (MCC) relevant to the treatment. It is not a blanket ₹1,00,000 rule for every UPI AutoPay debit. If a recurring transaction exceeds the relevant threshold, the circular says AFA is required. Banks and apps implement the flow; users should not assume that a category label alone proves that a specific merchant or transaction qualifies for the higher limit.
5. What the threshold does—and does not—mean
A threshold for a recurring payment without a fresh AFA is not the same thing as a promise that all payments below it will always succeed, nor is it a universal cap on every UPI payment. It is one element in a framework for recurring transactions. The merchant must have a valid mandate, the execution must correspond to the instruction, and the bank/payment participants must apply the relevant checks. A payment can fail for ordinary reasons such as insufficient funds, a bank or network issue, a disabled account, an expired mandate or a mismatch with the instruction.
The NPCI circular says subsequent recurring UPI AutoPay transactions up to the ordinary ₹15,000 threshold do not need user AFA, while the specified ₹1,00,000 categories use that higher threshold as per the applicable MCC. Amounts beyond the defined applicable threshold require AFA. RBI’s 12 December 2023 circular explains the increase from ₹15,000 to ₹1,00,000 per transaction specifically for subscriptions to mutual funds, insurance-premium payments and credit-card bill payments, effective immediately on issue. The rule is category-specific; it should not be paraphrased as “all subscriptions have a one-lakh limit.”
When an app asks for an extra authentication step on a debit, read the amount and transaction description rather than treating the prompt as proof of fraud or proof of safety. A prompt can be expected for a threshold-crossing execution or another required step, but you should still confirm the merchant and purpose. If the transaction shown does not match the mandate you remember, stop and check the mandate in the UPI app or with your bank through its official channel. Never approve a request simply because a caller tells you that the prompt is needed to cancel or refund an earlier payment.
6. Pre-debit notices and the useful time they create
For ordinary scheduled UPI AutoPay executions, NPCI’s consolidated circular requires a pre-debit notification at least 24 hours before the actual charge or debit. The notice should identify the merchant, amount, debit date and time, UMN and reason for debit; the circular also says the user should be able to choose among available delivery modes such as SMS or email. NPCI’s consumer-facing AutoPay page describes the same advance notice as a way to help users maintain sufficient funds. A post-debit notification should also provide the merchant, amount, date and time, UMN, reason and grievance-redressal details.
The purpose of advance notice is practical: it gives the customer a chance to recognise the debit and check that the account is funded. It is not a guarantee that every message reaches every device or that reading the notice is a condition for the debit. Keep bank transaction alerts enabled where available, and compare the notice with the mandate’s merchant and terms. If you see an unfamiliar name, the payee may use a corporate or payment-processor description that differs from the brand you remember; confirm through the merchant’s official app or your bank rather than clicking an unexpected link in an SMS.
There are explicit exceptions. NPCI’s consolidated circular exempts mandates for auto-replenishment of NETC FASTag, UPI Lite auto top-up and National Common Mobility Card (NCMC) from the pre-debit notice requirement. NPCI’s AutoPay page also notes the waiver for FASTag and RuPay NCMC auto-replenishment. RBI’s August 2024 circular explains that FASTag and NCMC top-ups occur when a balance falls below a customer-set threshold and may not have fixed periodicity; that auto-replenishment is exempt from pre-debit notification, while other e-mandate instructions continue to apply. Do not mistake a valid exception for the general rule for subscriptions or bills.
7. Pause, resume, modify and revoke: choose the right control
Pausing and revoking are different. A pause stops or opts out of an execution for a period or particular occurrence, while a revoke ends the mandate. An unpause or resume makes a paused instruction active again. Modification changes a permitted attribute such as amount or validity period. NPCI’s AutoPay consumer page lists modify, revoke, pause and unpause controls in UPI apps. Its consolidated circular requires banks to offer a way to opt out of an individual execution or revoke; it also assigns pause/revoke functions to UPI apps, with an exception in the cited clause for Loan Payments and EMI Collection categories.
The circular separately requires merchant platforms to support pause, and says a merchant-side revocation request should be sent through the UPI AutoPay channel rather than merely deleting the mandate at the merchant end. It also says withdrawal through a merchant platform does not require UPI AFA validation. Because the rules refer to several participants and categories, a single app screen may not expose every operation for every type of mandate. If a control is unavailable, do not assume the instruction has been cancelled; contact the merchant through its authenticated channel and the issuing bank/UPI app support path to confirm the status.
Choose a pause when you want to stop a near-term execution but may resume later, and revoke when you want the mandate to end. But the exact effect of a pause—whether it skips one payment or lasts until an explicit resume—depends on the screen and mandate flow. Read the confirmation carefully and retain it. A “cancel subscription” action on a merchant website may cancel the service without proving that the linked payment mandate has been revoked; a “revoke mandate” action may stop payment authorization without ending the contract or subscription itself. Often both sides need separate attention.
8. Interoperability and moving between apps
Interoperability matters because users change phones, UPI apps and service providers. NPCI describes UPI AutoPay interoperability as a way to help recurring payments continue even when a user switches UPI apps or a merchant changes its acquiring bank. Its published description says a user can view active mandates across UPI apps and choose to port active mandates using UPI PIN authentication. The goal is continuity, but the feature should not be read as a promise that every mandate automatically appears in every app or is moved without the user’s action.
When changing apps, check whether the new app shows the mandate and whether its status is active, paused or revoked. Compare the merchant, account and schedule with your records. If it is missing, do not create a second mandate just because the service’s next payment is approaching; first check the original app and ask the merchant or bank whether an existing instruction remains in force. Duplicate mandates can lead to repeated charges if both are active. Conversely, do not assume that uninstalling the old app cancels a mandate; an app is an interface to the payment system, not the instruction itself.
NPCI also describes MyUPI as a place to view UPI activity and AutoPay mandates across UPI apps, with support for mandate lifecycle actions such as pause, resume and revoke by redirecting to the respective UPI app through which the mandate was created. The site describes access through participating bank/NPCI/DigiSaathi websites or supported UPI apps, with different authentication journeys and feature availability. This is a published product description; availability may depend on a supported channel and may change. Use NPCI’s current page to confirm access and do not enter an OTP or PIN on a link received from an unknown sender.
9. A simple monthly mandate review
A short review can make a long list manageable. Start with the active mandate list in the UPI app or bank channel. For each item, ask: do I recognise the merchant; do I still use the service; does the amount or maximum make sense; is the frequency expected; is the validity date appropriate; is this the correct linked account; and is there a pause or cancellation already requested? The review is not a substitute for reading the original terms, but it can uncover a forgotten trial, a duplicate setup or a service that ended without its payment instruction being closed.
Match entries across sources. A merchant may appear under a legal company name rather than its consumer brand, and a bank statement may use a short descriptor. Compare the amount, date, UMN and service account before declaring that two entries are duplicates. If a charge seems incorrect, save the relevant notice, transaction reference, screenshot of the mandate’s status and merchant correspondence. Do not share sensitive authentication values in an email or complaint. Use the bank’s official app, website or published telephone number to raise a query.
Keep a concise personal record of key terms: merchant, purpose, amount or maximum, frequency, start/end dates and where to manage it. This can be a secure note or a simple list kept privately. Avoid storing UPI PINs, OTPs or full account credentials in an ordinary document. If you rely on a shared device, ensure that the phone itself and notifications are protected. The goal is not to make everyone maintain a complex spreadsheet; it is to make the important boundary visible when an unfamiliar notice arrives.
10. Common misunderstandings
“I entered a PIN once, so the payment must be one time.” Not necessarily. On a recurring mandate, the first PIN authorises the mandate and its defined future executions. Read whether the screen says payment, mandate, subscription or recurring instruction. “I cancelled the subscription, so the debit must be impossible.” That may stop service renewal, but the payment mandate status should be checked separately. “I removed the app, so the mandate ended.” Uninstalling an app does not itself confirm revocation. “The recurring amount is below ₹15,000, so no further check can occur.” The threshold concerns AFA treatment; other validation, failure or merchant processes still apply.
Another common misunderstanding is that every notice is a demand for immediate payment. A pre-debit notice is information about a scheduled execution. Read it and use the official app if you need to manage the mandate. A genuine payment-support flow should not require disclosing your UPI PIN or letting another person control your screen. Likewise, a message about “reversing AutoPay” is not proof that the sender is your bank. Never scan an unknown QR code or approve a collect request to receive a refund; a QR or collect authorisation can request money from you rather than return money to you.
Finally, “the app showed a green tick” and “the merchant delivered the service” are separate outcomes. A successful mandate registration means the instruction was recorded, not that every future debit will succeed or the underlying service will be satisfactory. A failed execution does not necessarily mean the mandate disappeared. Review the actual transaction and mandate status, then use the merchant or bank’s official complaint process if the problem remains.
11. If a debit is unexpected or a mandate cannot be changed
First identify whether the entry is a mandate registration, pre-debit notice, actual debit, failed execution or a merchant billing adjustment. Record the date, amount, merchant description and UMN if provided. Check the relevant UPI app and bank statement, not just the notification preview. If you recognise the merchant but no longer want future debits, use the appropriate pause or revoke control and save the on-screen result. If the app reports a failed operation, the mandate may still be active; verify its status before relying on the attempted action.
For a disputed debit, contact the bank and merchant using their verified official contact routes and provide the transaction reference requested by their process. Ask what was authorised and what steps are available for dispute resolution. A user should not send their PIN, full credentials, OTP or remote-access permission to someone who claims to investigate the payment. If a caller claims urgency, end the call and independently contact the official support channel. These steps are general safety guidance, not a guarantee of a particular refund or complaint outcome.
Keep the evidence that distinguishes the case: the original mandate confirmation, notice, bank debit message, merchant subscription status and any pause/revoke acknowledgement. A merchant’s account page may show “cancelled” while the payment system still shows an active mandate, or vice versa, because they represent different records. If your UPI app and bank provide different status information, ask the bank or app provider which system holds the current mandate state and whether the instruction remains eligible to execute. Avoid repeated cancellation attempts that may create confusion until you know which status is current.
12. What merchants and platforms are responsible for
AutoPay is a network of participants: merchant, payee-side payment service provider, payer-side UPI application provider, remitter bank and other participants. NPCI’s consolidated circular assigns duties across them. For example, the circular describes the minimum information in the pre-debit notice, user facilities to pause or revoke, the merchant’s responsibility to support pause and the channelled handling of merchant-initiated revocation. This is why a user may need to start from one interface while the final state is reflected through another participant.
NPCI also notes that merchant category matters for the higher AFA threshold. That classification is not a judgment about whether the expense is important or affordable. It is a payment-rule attribute applied in the transaction system. A consumer cannot infer the applicable MCC merely from a merchant’s marketing language. If an execution is above the usual threshold and a UPI PIN prompt appears, review the exact transaction context; if there is a discrepancy, stop and ask the bank through its official channel.
Operational requirements can be revised by NPCI or RBI, and apps update their user interfaces over time. This guide reflects publicly available official pages and circulars reviewed on 14 November 2026. Where the website’s current user-facing instructions differ from a general explanation here, use the live instruction from the relevant bank, NPCI or UPI app and request clarification. A broad consumer explainer cannot replace the mandate’s own terms or a bank’s investigation of an individual transaction.
13. A decision checklist before you approve
Before authorising a new recurring instruction, pause long enough to answer a handful of questions. Is the merchant the company you meant to pay? Is the payment for the service or bill you selected? Is the amount fixed or variable, and what is the maximum per execution? How often can it recur, and how long is the mandate valid? Which linked account will be debited? How can it be paused or revoked, and is that control available in the merchant account, UPI app, or both? Is a trial converting to paid service, and on what date?
If any answer is missing or conflicts with the offer you saw, do not approve until you can verify it in the official app or with the merchant. Check a merchant website by typing its known address or using its official app, rather than following a suspicious short link. Confirm the final screen before entering the UPI PIN. Keep the resulting confirmation and note the UMN, if shown. These small actions are especially useful for a family account, an annual renewal, or a variable bill that may change from month to month.
After approval, make a quick note for your future self: “This is the electricity bill, variable up to the shown cap, monthly, linked to the chosen account; manage it in the UPI app.” A sentence like that is more helpful than a generic reminder saying only “AutoPay.” It helps you decide whether a later bank message is expected. It also helps distinguish a legitimate recurring bill from a similarly named merchant or an old subscription you thought you had cancelled.
14. A checklist after a payment notice
When a pre-debit message arrives, identify the merchant, amount, scheduled date, reason and UMN. Compare them with the mandate record. If the amount is variable, compare it with the allowed maximum; if it is fixed, compare it with the amount you approved. Confirm whether the notice is expected and whether the linked service remains active. Use the app’s pause or revoke option only after reading what it will do; retain the resulting confirmation. If the notice is for an auto-replenishment exception such as FASTag or NCMC, remember that the usual advance-notice expectation may not apply.
When a post-debit notice arrives, match the transaction to the prior mandate and bank statement. If there is a problem, take a screenshot of the displayed facts without exposing private credentials, and use the bank or merchant’s official support route. Never reply to a suspicious message with an OTP or PIN. If someone contacts you to “help” after you report a problem, verify their identity independently. A legitimate dispute can take time; a caller’s promise to reverse a payment does not prove that a reversal has been initiated.
If you do not recognise the debit, treat it as a concrete transaction to investigate, not as proof of fraud before checking the details. A billing descriptor can differ from the consumer-facing brand. At the same time, do not dismiss an unfamiliar debit merely because a service you once used had a recurring payment. Confirm the source through your bank and the service provider; then decide what request to make under their processes. Recording facts accurately makes an investigation more effective and avoids sharing more personal information than needed.
15. Why automation should still be reviewed
Automation shifts effort from every payment date to the moment of authorisation and occasional review. That is a sensible trade for predictable obligations, but it makes status visibility important. A person may change a phone, bank account, subscription tier or preferred UPI app. A merchant can change its name or acquiring arrangement. A previously paused mandate may be unpaused. A service may end while the payment instruction remains active. None of these possibilities means that AutoPay is inherently unsafe; they explain why the active-mandate list is worth checking from time to time.
Reviewing a list is also a way to make household spending more legible. It can reveal which recurring charges belong to a shared service, who manages the related account and which instructions should be ended after a plan changes. If two people are responsible for the same bill, agree which person owns the mandate rather than creating overlapping instructions on separate UPI IDs. This is ordinary household coordination, not an additional payment-system feature. The bank and merchant records remain the authoritative sources for the actual mandate and service status.
A useful review need not become a monthly audit of every small expense. Choose a cadence that fits the number and importance of your recurring payments. At minimum, review when a trial starts charging, a plan changes, a bank account or UPI app changes, a payment notice is unfamiliar, or you stop using a service. The main aim is to keep the authorisation aligned with what you still intend to pay for. If you cannot establish the current state, ask the bank or merchant directly rather than relying on an old screenshot or memory.
16. How to read claims about AutoPay limits
Online explanations often compress several different rules into one number. A statement such as “AutoPay supports ₹1 lakh” is incomplete unless it identifies the covered payment types and whether the number concerns an AFA exemption threshold or a transaction limit. RBI’s December 2023 circular increased the no-AFA threshold for subsequent e-mandate transactions in three categories: mutual-fund subscriptions, insurance premiums and credit-card bill payments. NPCI’s related circular applies the higher limit to eligible merchant category codes. For other categories, the stated threshold remains ₹15,000 in the cited framework.
Similarly, “no PIN for recurring debits” is too broad. First transactions are authenticated with AFA, and larger subsequent executions above the applicable threshold require AFA. A bank may also have its own procedures for exceptions, failure, account restrictions or security checks. The relevant amount, MCC and execution stage all matter. The user’s approving screen and the bank’s current records should be consulted for an individual payment.
When comparing two sources, prefer the current official circular or NPCI product page over a blog that repeats an old threshold. Check the publication date and whether it refers to UPI, cards or prepaid instruments; RBI’s recurring mandate framework covers several instrument types, while this article focuses on UPI. A rule for card mandates does not automatically describe a UPI mandate. A precise description is more useful than an attractive headline with an old or overgeneralised number.
17. Keeping records without exposing secrets
Useful evidence is usually ordinary transaction detail: merchant, amount, date, UMN, status and the wording of a mandate confirmation. Keep these in a place protected by your device or account security. Do not include the UPI PIN, OTP, password or recovery code in a note. If you need to share a screenshot with a bank, redact unrelated account details and notifications where the bank’s process permits. Share only the information requested through the bank’s authenticated channel.
For a recurring debit dispute, a clean timeline helps: when the mandate was created, what the approved terms showed, when a pre-debit notice arrived, whether you attempted a pause or revocation, what confirmation appeared, and when the actual debit posted. The timeline does not decide the dispute, but it makes the issue easier to explain. Keep original messages where possible, because a cropped screenshot may omit the date or sender that helps establish its context.
Do not rely on a merchant-side email alone as evidence that the UPI mandate has been revoked. Save the UPI app’s confirmation too, then verify that the mandate shows its new status. If the app does not supply a clear confirmation, contact the app provider or bank to check. A control tap is not the same as a successful state change; it is the confirmation on the screen or bank record that matters.
18. A practical summary
UPI AutoPay is a standing payment instruction with a specific merchant, amount or maximum, recurrence and validity period. Registration and first execution involve authentication; eligible later transactions may execute without fresh AFA within category-specific thresholds. Ordinary scheduled debits should generate a pre-debit notice at least 24 hours ahead, while defined auto-replenishment cases are exempt. Users have tools to modify, pause, resume or revoke, but the specific controls and mandate categories affect how those actions work.
For a new mandate, verify the merchant, purpose, amount, maximum, recurrence, linked account, validity and cancellation path before approving. For an existing mandate, compare notices with its UMN and saved terms, and verify the resulting status after a pause or revocation. For a disputed debit, use official bank and merchant support, retain transaction evidence, and never disclose a PIN or OTP to a person who contacts you. The final authority for your own instruction is its actual current record—not a generic description, an old app screenshot or a phone call.
Sources and scope
- NPCI, UPI AutoPay for Recurring Payments — product description, common use cases, management controls and pre-debit notification information; reviewed 14 November 2026.
- NPCI, UPI Consolidated Circular (UPI/CC/01) — mandate definitions, notifications, authentication, pause/revoke and related operating requirements; reviewed 14 November 2026.
- NPCI, UPI AutoPay Interoperability — interoperability, cross-app mandate view and porting description; reviewed 14 November 2026.
- NPCI, MyUPI — published mandate-management routes and channel limitations; reviewed 14 November 2026.
- NPCI, UPI — UPI PIN safety information and general UPI overview; reviewed 14 November 2026.
- Reserve Bank of India, RBI/2023-2024/88, “Processing of e-mandates for recurring transactions,” 12 December 2023 — higher AFA exemption threshold for specified subsequent recurring categories.
- Reserve Bank of India, “Processing of e-mandates for recurring transactions,” 22 August 2024 — FASTag and NCMC auto-replenishment notification exemption.
This content is a collection of ancient history,books and various articles and collection of library and news and other post ; all details may not be the same. Readers are requested to verify the information themselves. Readers are not allowed to take any disciplinary action; content is only for educational purposes. If readers do not agree about the contents, they may send a personal comment to my personal email ID: achary.purna@gmail.com
