API & onboarding
Share the endpoint, non-secret error message, request time, and your intended authentication flow. Never send your API key, password, or OTP.
Contact MeraOTP
Get the right help, with less back-and-forth.
Contact the support team for onboarding, integration, account, billing, compliance, or suspected abuse questions. Include a non-secret reference so we can investigate efficiently.
Choose a support path
Tell us what you are trying to resolve.
Access & verification
Write from your registered email and include the account name and the verification stage you are on.
Email account supportPayment & refund
Include the order or transaction reference, amount, date, and a redacted payment-status record.
Email billing supportReport a vulnerability
Describe the issue and affected area without including live credentials, OTPs, or unrelated personal data.
Send a security reportReport suspicious OTPs
Include the sender header, exact time and timezone, message copy, and a masked recipient number.
Send an abuse reportData request or grievance
Write from your registered email, identify the account, and describe the privacy request concisely.
Contact privacy supportDirect contact
Support built around useful context.
Support is available Monday to Saturday, 10:00–19:00 IST, excluding applicable holidays. Response time depends on severity, verification needs, and provider involvement.
For an immediate threat to life or safety, contact the appropriate emergency or law-enforcement authority first.
Emailsupport@meraotp.in
Developer support emailmonu.giri.work@gmail.com
Developer support WhatsApp+91 76690 06847
Websitenew.meraotp.in
Support hoursMonday–Saturday, 10:00–19:00 IST
Postal addressMeraOTP, India
Before you send
Protect secrets and shorten the investigation.
Safe to include
Registered account email, internal ticket ID, MeraOTP transaction/delivery reference, timestamp and timezone, endpoint, and redacted screenshots.
Never include
Your password, live API key, OTP, UPI PIN, CVV, full card or bank-login credentials, or unrelated recipient data.
For delivery issues
Wait for a final status where appropriate, avoid unbounded retries, and include the masked recipient plus exact request time.
For legal notices
Use the subject “Legal Notice” and include the sender's identity, authority, account, factual basis, and requested action.
Self-service resources
Many answers are already documented.
Review the service terms, privacy practices, refund rules, acceptable use requirements, and DLT checklist before contacting support.