MeraOTP
Log in Create account
New MeraOTP for WordPress and WooCommerce is now available. Download the plugin
OTP for WordPress, PHP, Node.js, websites and apps

Add secure OTP without the usual complexity.

Use our ready WordPress plugin or two simple API endpoints to send and verify authentication OTPs. Register, add credit, and start with one automatically generated API key.

Start your verification Get WordPress plugin
  • WordPress-ready
  • India-focused delivery
  • Transparent usage credits
new.meraotp.in/api/v1 / request Secure session
POST/api/v1/otp/send Request accepted
API keyActive
Server IPWhitelisted
TemplateAuthentication OTP
Delivery recordCreated
Single-purpose APIAuthentication OTP, not bulk promotion
Controlled accessOne API key and a simple IP whitelist
Operational clarityDelivery and transaction records
Human supportIntegration and account assistance

Two products, kept clearly separate

Authentication OTP and practical payment tools.

OTP uses simple prepaid credit with no subscription. Payment Tools is optional and uses the same account API key with its own plan limits.

OTP API

Send user-requested authentication OTPs through the MeraOTP DLT route, with one automatic API key, an instant IP whitelist, prepaid billing and delivery records.

Payment Tools

Create UPI QR codes and payment links for your own Paytm Business VPA. Check an order using your Paytm MID and the same MeraOTP API key—no Merchant Key required.

One simple wallet

Add OTP credit and see your rate and estimated OTP capacity before paying. An 18% platform fee or applicable tax is shown separately at checkout.

Purpose-built, not overloaded

The essentials for a dependable OTP operation.

From the first verification request to daily monitoring, MeraOTP keeps authentication delivery understandable for developers and accountable for businesses.

Verified onboarding

Register and verify your account. MeraOTP automatically creates your live OTP workspace and single account API key.

Simple IP whitelist

Every call must come from localhost or a server IP you added. New entries work immediately with no admin approval.

OTP-only templates

A deliberately narrow message flow reduces misuse and keeps product behavior centered on user-requested authentication.

Delivery visibility

Review recipient-masked delivery activity, status information, timestamps, and credit transactions from one dashboard.

Useful notifications

Keep customers informed with account, balance, payment-product, and security notifications through configured email and push channels.

Flexible billing

Add only the OTP credit you need, see the exact rate and estimated OTP capacity, and review the 18% fee or tax before paying.

Register, add credit, send

Your first OTP takes only a few clicks.

Your live workspace and single API key are created automatically. Localhost already works, and hosted server IPs activate instantly.

01

Create and verify

Register your account and confirm your contact details.

02

Add wallet credit

Choose an amount and see your OTP rate, fees and sending capacity before paying.

03

Send your first OTP

Copy the automatically generated key and call the two simple send and verify endpoints.

04

Add your server IP

Localhost needs no setup. Add your backend public IP when you deploy; no admin approval is required.

No-code WordPress setup

Install the plugin. Paste your key. Start verifying.

MeraOTP now works as a native WordPress plugin. Add a mobile verification form with one shortcode, enable optional WooCommerce checkout verification, or use the included PHP functions in your own plugin or theme.

  • API key stays safely on your WordPress server
  • Built-in connection and real OTP tests
  • Automatic outbound-IP discovery for whitelisting
  • Responsive verification form and signed proof
  • WooCommerce classic checkout support
Download plugin ZIP Setup guide
W
MeraOTP for WordPressOTP verification · Connected
1
Connect accountPaste your single MeraOTP API key
Done
2
Whitelist serverUse the IP shown by Test connection
Done
3
Add verification form[meraotp_verify]
Ready
WordPress 6.2+ · PHP 7.4+ · OTP only

Developer-friendly API

One focused request. No messaging maze.

The endpoint accepts only the details needed for an authentication OTP. Keep the key server-side and send requests only from localhost or an IP on your whitelist.

  • JSON request and response
  • Server-generated, hashed and expiring OTPs
  • Idempotent send, verification and status endpoints
  • Actionable access, validation and balance errors
Get API access
cURL · Send authentication OTP 
curl --request POST 'https://new.meraotp.in/api/v1/otp/send' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --header 'Idempotency-Key: login_01JUNIQUEATTEMPT' \
  --data '{
    "mobile": "9876543210",
    "purpose": "login",
    "reference": "login_attempt_123"
  }'
Never expose an API key in browser or mobile client code. HTTPS only

Clear, safer OTP copy

A message users can recognise and trust.

The fixed authentication copy identifies the verification purpose, gives a short validity window, clearly tells the recipient never to share the code, and ends with the registered Codegully signature.

  • Use the fixed, registered Codegully signature.
  • State the exact authentication purpose and validity period.
  • Never add promotions, shortened links, or requests to reveal the OTP.
  • Match the exact content approved by your telecom/DLT provider where applicable.
See template and DLT guidance
OTP
VM-YRBRNDTransactional message
Your OTP for verification is 123456. This OTP is valid for 10 minutes. Do not share it with anyone.
Codegully
Authentication OTPNow
The production template must match the DLT-approved wording, variable position, Codegully signature, sender header, and Fast2SMS template ID exactly.

Compliance is part of the integration—not a footnote.

Businesses sending OTP or other bulk communications in India may have Principal Entity, header, content-template, consent, and transmission obligations under TRAI's TCCCPR framework. MeraOTP does not replace those responsibilities.

Review the checklist

Straightforward access

No OTP plans. Just prepaid usage.

Your OTP rate is based on the amount of wallet credit you add. There is no OTP subscription or monthly fee.

Every verified account receives an API key automatically. OTP usage deducts the displayed per-OTP rate only after a provider accepts the request.

Prepaid OTP rates

An 18% platform fee or applicable tax is added to the payment total
Credit addedMonthly feeRate per accepted OTP
₹100–499₹0₹0.89
₹500–999₹0₹0.79
₹1,000–1,999₹0₹0.69
₹2,000–4,999₹0₹0.59
₹5,000–9,999₹0₹0.49

Designed for real authentication moments

One API, across the journeys where identity matters.

01

Sign-in verification

Confirm a user's possession of their mobile number during a passwordless or step-up sign-in.

02

Account recovery

Add a time-bound confirmation step before permitting sensitive password or account recovery actions.

03

High-risk actions

Request an additional authentication factor before profile, device, or security-setting changes.

04

Mobile verification

Verify a submitted Indian mobile number before it becomes a trusted contact point in your product.

A control room for your OTP service

See the activity that matters. Act on it quickly.

The customer dashboard brings access, balance, API, delivery, verification, and payment information into a single operational view.

Masked delivery records Credit balance visibility API key controls Current OTP rate and capacity Payment transactions Support access
Open customer login
Operations overviewAccount protected
API STATUSActive
DOMAINVerified
IP RULEEnforced
AUTH_OTP98••••••10Accepted
AUTH_OTP97••••••42Delivered
AUTH_OTP99••••••84Delivered
AUTH_OTP96••••••31Accepted

Frequently asked questions

Useful answers before you integrate.

Does MeraOTP remove my DLT or telecom compliance obligations?
No. TRAI states that businesses sending OTP, transactional, service, or commercial bulk communications may need to complete applicable Principal Entity, header, content-template, consent, and transmission requirements. Your obligations depend on your route and use case; review the MeraOTP compliance checklist and confirm requirements with your telecom/DLT provider.
Can I use the API for promotional or bulk marketing messages?
No. The product is intended for user-requested authentication OTPs. Promotional messaging, unsolicited communication, phishing, deceptive content, and attempts to bypass operator or regulatory controls are prohibited.
Why do I need to add my server IP address?
It reduces unauthorised use. The backend server IP is checked on every call. Localhost and 127.0.0.1 work automatically, and hosted IPs you add become active immediately.
Should I call the OTP API directly from my website or mobile app?
No. Call MeraOTP from your own backend so the API key never appears in browser code, mobile application bundles, public repositories, analytics, or client-side logs.
Does OTP require a monthly plan?
No. OTP is prepaid. The amount you add determines the rate, and the billing screen shows the credit, 18% fee or applicable tax, total payable, selected rate, and estimated OTP count before checkout.
Is every OTP guaranteed to reach the recipient instantly?
No messaging provider can guarantee every delivery or delivery time. Results depend on recipient network availability, handset state, operator filtering, route and template approval, congestion, and accurate request data. MeraOTP provides status records so you can handle outcomes appropriately.

Ready when your product is

Build a better OTP journey.

Create an account, add wallet credit and start sending. Your single API key and localhost access are automatic; hosted IPs activate as soon as you add them.

Create account Talk to support