1. Agreement and definitions
These Terms of Service form a binding agreement between you or the organisation you represent ("Customer", "you", or "your") and MeraOTP ("MeraOTP", "we", "us", or "our"), the operator of the service available at new.meraotp.in.
"Service" means the MeraOTP website, customer dashboard, APIs, OTP delivery features, Payment Tools, reports, notifications, plans, credits, documentation, and related support. "Recipient" means the person whose mobile number receives an OTP initiated through your application. "Payment Tools" means the separate feature used to create UPI payment intents for your own configured business VPA and request Paytm order-status checks. "Customer Data" means information you or your users submit to the Service.
If you use the Service for a company or another legal person, you represent that you have authority to bind that organisation. If you do not agree to these Terms, do not use the Service.
2. Eligibility, account information, and verification
- You must be at least 18 years old and legally capable of entering a contract.
- You must provide complete, current, and accurate registration, billing, contact, business, domain, and integration information.
- You are responsible for activity under your account and for keeping passwords, OTPs, API keys, recovery details, and authorised-user access confidential.
- You must promptly update information that changes and notify us at support@meraotp.in if you suspect unauthorised access.
We may request identity, address, business, domain-control, application, tax, or other documents reasonably necessary for onboarding, fraud prevention, regulatory compliance, payment review, or account recovery. We may approve, reject, limit, or request more information for an account. Submission does not guarantee production approval.
You may not create accounts using false details, impersonate another person or entity, conceal beneficial ownership, resell account access without written permission, or create replacement accounts to evade a restriction.
3. Service scope and licence
Subject to these Terms and payment of applicable charges, MeraOTP grants you a limited, revocable, non-exclusive, non-transferable right to access the Service. The prepaid OTP API may be used solely for legitimate, user-requested authentication OTPs for your approved application. Payment Tools is independently subscribed and may be used only with a Paytm Business VPA, MID, brand, orders, and funds that you are authorised to operate.
Payment Tools creates UPI intent data and asks Paytm for order status using credentials you supply. MeraOTP is not the merchant of record for your customer transactions, does not receive or settle those funds, does not guarantee that a payer completes a payment, and does not replace Paytm onboarding, KYC, reconciliation, refund, tax, consumer-protection, or dispute obligations. You must confirm settlement in your own authorised merchant account before delivering irreversible value.
MeraOTP is not an emergency service, identity provider, bank, telecom operator, legal adviser, or a substitute for your own authentication, fraud, consent, privacy, security, or regulatory programme. You remain responsible for your product, users, authentication decisions, data, notices, and legal compliance.
We may add, change, deprecate, or discontinue features to improve safety, reliability, legal compliance, or product operation. Where reasonably practicable, we will provide notice of a material change that adversely affects active paid use.
4. Lawful use and messaging compliance
You may use the Service only for lawful, transactional OTP authentication and in accordance with our Acceptable Use Policy. You are responsible for determining and meeting every obligation applicable to you, your business, content, recipients, sender route, and industry.
For communications sent in India, this may include requirements under the Telecom Commercial Communications Customer Preference Regulations, 2018 (TCCCPR), including the 2025 and 2026 amendments, current TRAI directions, telecom service-provider codes of practice, and DLT processes. TRAI's sender guidance states that businesses sending OTP, transactional, service, or commercial bulk communications may need Principal Entity registration, an assigned header, registered content templates, transmission of relevant identifiers, and consent records where applicable. See our DLT and Compliance page.
You must obtain and preserve all legally required permissions and notices before providing a recipient number, honour withdrawal or preference rights where applicable, and use only a sender identity and content you are authorised to use. MeraOTP access does not waive or replace operator, DLT, regulatory, or statutory requirements.
5. Integration and security duties
You must implement the Service securely and follow current documentation. In particular, you agree to:
- call the API from trusted server-side infrastructure and never embed an API key in client-side JavaScript, a mobile application, a public repository, or other public material;
- use HTTPS, strong access controls, secret rotation, input validation, logging controls, and reasonable rate limits;
- use truthful domain or app labels, send production requests only from your allowlisted server IPs, and keep that allowlist current;
- use the OTP generated by MeraOTP only for the matching authentication request, enforce appropriate application/session controls, and never submit or attempt to select a custom OTP;
- avoid storing plaintext OTPs or exposing them in URLs, analytics, browser logs, support tickets, or unnecessary application logs; and
- promptly revoke or rotate credentials and contact us if a key, account, or integration may be compromised.
Localhost access is intended for development only. It does not authorise production traffic from an unverified source or relieve you from safeguarding credentials.
6. Customer Data and recipient information
You retain ownership of Customer Data. You grant MeraOTP and its service providers a limited right to process Customer Data only as needed to provide, secure, support, meter, troubleshoot, and legally operate the Service.
You represent that you have a lawful basis and all necessary authority to provide Customer Data, including recipient mobile numbers, to us. You must not submit sensitive personal data, financial credentials, government identity numbers, passwords, or content that is unnecessary for OTP delivery.
Our processing practices are described in the Privacy Policy. We may aggregate or de-identify operational information so it no longer reasonably identifies a person and use it to protect and improve the Service.
7. Plans, credits, payments, and taxes
Platform plans
OTP has no recurring plan. The wallet top-up amount determines the displayed per-OTP rate, and accepted production OTP requests deduct that rate from available credit. The checkout separately displays the wallet credit, applicable 18% platform fee or tax, and total payable.
Payment Tools remains a separate fixed-duration product. Its fees are debited from available MeraOTP wallet credit and its optional auto-renewal can be changed on the Payment Tools page.
OTP usage credits
OTP usage is charged separately at the rate shown for your account. Wallet credit may also pay eligible plan fees. Credit is a prepaid contractual right to use eligible MeraOTP features; it is not money held for your end customers, a bank deposit, electronic money, or transferable property and cannot be withdrawn as cash. Funds paid by an end customer to your UPI VPA do not enter the MeraOTP wallet.
Payments
You authorise the selected payment provider to process the total shown at checkout. You are responsible for applicable taxes, gateway charges, bank charges, and accurate billing information. We may correct pricing or display errors before activation and will provide the option to accept the corrected amount or cancel an affected unfulfilled order.
Payment, refund, cancellation, duplicate-charge, and failed-transaction rules are in the Refund and Cancellation Policy. A chargeback raised without first contacting support may lead to temporary restriction while the payment is investigated.
8. OTP delivery and Service availability
An API acceptance or transaction identifier confirms that a request was accepted for processing; it is not a guarantee that the recipient received, read, or acted on the OTP. Delivery and timing can be affected by carrier and aggregator systems, DLT or template checks, spam controls, number status, handset state, congestion, maintenance, internet failures, force majeure, and request accuracy.
Unless a separately signed service-level agreement says otherwise, the Service is provided on an "as available" basis without a guaranteed uptime, latency, delivery rate, or response time. We may conduct maintenance, apply rate limits, pause affected routes, or reject traffic to protect recipients, customers, or the Service.
You are responsible for designing a safe fallback and retry experience. Automated retries must be bounded and must not repeatedly message a recipient who did not request a new OTP.
9. Review, restriction, and suspension
We may investigate, throttle, reject, quarantine, suspend, or terminate access when reasonably necessary to:
- prevent suspected fraud, abuse, spam, phishing, account takeover, security threats, or harm to recipients;
- respond to a telecom provider, payment provider, court, regulator, or lawful government request;
- address false verification information, compromised credentials, excessive failures, unusual traffic, chargebacks, or overdue amounts;
- enforce these Terms or protect MeraOTP, our providers, customers, or the public; or
- comply with law or an operator/DLT rule.
Where appropriate and lawful, we will provide notice and a reasonable opportunity to respond. We may act without advance notice when delay could increase risk, violate law, impair a network, or compromise an investigation.
10. Intellectual property and feedback
MeraOTP and its licensors own the Service, software, interfaces, documentation, designs, trade names, logos, and related intellectual property, excluding Customer Data. No rights are granted except the limited access right in these Terms.
You may not copy, sell, sublicense, reverse engineer, probe, scrape, interfere with, or create a competing service from protected elements of the Service except to the limited extent a restriction is prohibited by applicable law. If you voluntarily submit feedback, you grant us a worldwide, perpetual, royalty-free right to use it without identifying you or disclosing your confidential information.
11. Confidential information
Each party may receive non-public information that a reasonable person would understand to be confidential. The receiving party will protect it with reasonable care and use it only for the agreement. This obligation does not cover information that is public without breach, independently developed, lawfully received without restriction, or rightfully known before disclosure.
A party may disclose confidential information when legally required, and will provide advance notice where lawful and reasonably practicable.
12. Disclaimers and limitation of liability
To the maximum extent permitted by law, the Service is provided "as is" and "as available". MeraOTP disclaims implied warranties of merchantability, fitness for a particular purpose, non-infringement, uninterrupted operation, and guaranteed message delivery. Nothing in these Terms excludes a warranty or right that cannot lawfully be excluded.
To the maximum extent permitted by law, neither party will be liable for indirect, incidental, special, exemplary, punitive, or consequential loss; loss of profits, revenue, goodwill, data, or business opportunity; or the cost of substitute services, even if advised of the possibility.
To the maximum extent permitted by law, MeraOTP's aggregate liability arising from the Service will not exceed the amount you paid directly to MeraOTP for the affected Service during the three months immediately before the event giving rise to the claim. This limit does not apply where liability cannot be limited under applicable law, or to fraud or wilful misconduct proven against MeraOTP.
Your indemnity
You will defend and indemnify MeraOTP and its personnel against third-party claims, penalties, losses, and reasonable costs arising from your Customer Data, recipients, product, unlawful messages, breach of these Terms, infringement, or failure to obtain a required permission, registration, template, header, or consent, except to the extent caused by MeraOTP's proven breach or misconduct.
13. Term, cancellation, and account closure
These Terms apply while you access the Service. You may stop using it and request account closure by contacting support. Closing an account does not automatically create a refund and does not cancel amounts already due.
We may terminate an account for material or repeated breach, unlawful activity, serious security risk, non-payment, required provider action, or where continued service is no longer legally or technically possible. Where feasible, we may allow a reasonable period to export available account records before closure, except where access is restricted for security or legal reasons.
After closure, we may delete or de-identify account information subject to our Privacy Policy, while retaining records reasonably required for tax, accounting, fraud prevention, security, dispute, telecom, or other legal purposes. Provisions intended by their nature to survive—including payment, intellectual property, confidentiality, disclaimers, liability, indemnity, and dispute terms—will survive.
14. Governing law and disputes
These Terms are governed by the laws of India, without regard to conflict-of-law rules. Before filing a formal claim, each party will attempt in good faith for 30 days to resolve the dispute through written notice describing the issue and requested resolution.
Subject to any mandatory consumer forum, statutory remedy, or other jurisdiction that cannot be waived, courts of competent jurisdiction in New Delhi, India will have exclusive jurisdiction.
If part of these Terms is unenforceable, it will be limited to the minimum extent necessary and the remaining provisions will continue. Failure to enforce a provision is not a waiver. You may not assign this agreement without our written consent; we may assign it as part of a reorganisation, financing, merger, acquisition, or transfer of the Service.
15. Changes to these Terms
We may update these Terms to reflect legal, security, provider, or product changes. The effective date above identifies the current version. If a change materially reduces rights for an active paid Customer, we will use reasonable means to provide notice before it takes effect. Continued use after the effective date constitutes acceptance; if you do not agree, you must stop using the Service.
16. Notices and contact
Questions or formal notices about these Terms may be sent to support@meraotp.in with the subject “Legal Notice”, or by post to MeraOTP, India. We may send operational or legal notices to the email address registered to your account.