Why You’re Not Receiving OTPs During Bank Transactions but Still Paying for SMS Alerts: A Comprehensive Guide

Why You’re Not Receiving OTPs During Bank Transactions but Still Paying for SMS Alerts: A Comprehensive Guide

Have you ever experienced the frustration of not receiving an One-Time Password (OTP) during bank transactions, only to find out that your bank is still charging you for SMS alerts? This situation can be confusing and anxiety-inducing. In this article, we will delve into the reasons behind this discrepancy and provide a comprehensive guide to resolving the issue.

The Basics: Understanding OTPs, SMS Alerts, and Bank Transaction Processes

Before we explore the problem, it is important to understand the roles of OTPs and SMS alerts in bank transactions:

OTP (One-Time Password): An OTP is a temporary password that is sent to your registered mobile number. It is used to verify your identity during certain secure actions, such as online banking transactions or account access. SMS Alerts: SMS alerts are notifications sent to your mobile number to alert you about various activities, such as transactions, account balance changes, and more.

Understanding the Issue

The problem you're encountering can be due to a mismatch in the registered mobile number for alerts and the mobile number used for OTP verification. Here are the possible scenarios:

Incorrect or outdated registered mobile number for alerts. Mismatch in the mobile number you use for OTP verification and the one registered for alerts. Loss or change of the registered mobile number for alerts without informing the bank.

Reasons for Not Receiving OTPs and Still Paying for SMS Alerts

When you are not receiving OTPs during bank transactions but your bank is still charging you for SMS alerts, it could be because:

Incorrectly registered mobile number: If your registered mobile number for alerts does not match the one currently in use, you will not receive OTPs. Mobile number changes: If you have changed your mobile number but haven't updated your registered number with your bank, you will receive alerts but not OTPs. Piton issue with your bank's system: There could be a technical issue with your bank's system that is causing this discrepancy.

How to Resolve the Issue

Here are the steps you should take to resolve the issue:

1. Verify Your Registered Number with the Bank

Visit your nearest branch or contact your bank's customer service:

Inform them about the problem you are facing. Request to verify the mobile number registered for alerts. If the number is incorrect or outdated, ask to re-register the correct number.

2. Re-register Your Mobile Number

If the registered number is incorrect or outdated, follow these steps to re-register your mobile number:

Contact your bank through the official app, website, or a branch. Provide your current valid mobile number. Follow the prompts to complete the re-registration process. Verify the OTP sent to your new number to confirm it.

3. Understand the Months of Charges

Your bank may inform you about the months during which charges were made for the incorrect mobile number. Here are steps to understand and address those charges:

Review your bank statement for detailed transaction history. Keep records of all correspondence with your bank regarding the issue. Petition for a refund of any incorrect charges incurred.

Precautions and Best Practices

To avoid such issues in the future, follow these best practices:

Update your mobile number with your bank promptly if you change your phone or phone number. Verify your registered mobile number regularly to ensure it is accurate. Keep a record of all interactions with your bank regarding any updates or changes to your account information.

Conclusion

In conclusion, not receiving OTPs during bank transactions but still paying for SMS alerts can be a perplexing situation. However, by verifying your registered mobile number, re-registering it correctly, and understanding the months of charges, you can resolve the issue and ensure more secure and seamless banking transactions.