Security at EazyOTP
How API access works, what you should do on your side to keep OTP verification secure, and how to reach us about a security issue. This page describes the controls documented for EazyOTP today; it is not a certification.
API keys and transport
- API requests use HTTPS endpoints on the PingToChat platform.
- Requests are authenticated with an API key that is unique to your account and is part of the request URL. Treat it like a password: call the API only from your server, never from a mobile app or browser code, and keep it out of logs and source control.
- If you think your key has been exposed, contact us straight away.
Details: EazyOTP API documentation.
OTP generation, expiry and verification
- EazyOTP generates the one-time password and returns it in the API response so that your server can verify what the user enters.
- Your application decides how long a code stays valid. The sample WhatsApp authentication template tells users the code is valid for 5 minutes; use a short expiry like this and invalidate a code once it has been used.
- Store only a salted hash or HMAC of the code, limit verification attempts, and rate-limit OTP requests per phone number and per IP address.
- Never send the OTP back to the browser or app, and never write it to logs.
Step-by-step: how to verify OTPs securely on your server.
Webhook security
- When you register a webhook URL, the platform sends your verify token with a hub challenge; your endpoint must check the token and return the challenge.
- Use an HTTPS endpoint, keep the verify token secret, validate every payload and process status updates idempotently (the same status can arrive more than once).
Details: webhook documentation.
Data protection and retention
Account and messaging data is processed on the PingToChat platform operated by Texaavy Infotech Private Limited. Under the PingToChat privacy policy, data is retained while your account is active or as required by law, and you can request deletion at any time. See the EazyOTP privacy policy and the PingToChat privacy policy.
Test safely: each channel has a sandbox limited to one mobile number. Do not use real customer numbers for automated tests.
Platform availability
Delivery depends on mobile operators, WhatsApp and network conditions outside our control, so we do not promise guaranteed delivery. We do not publish uptime figures on this website. For commercial terms, contact our team.
Reporting a security issue
Email [email protected] with the subject “Security”, or message us on WhatsApp (24×7). Please include steps to reproduce and do not access other customers’ data.
WhatsApp Chat – Available 24×7
+1 555 854 2068Chat with us on WhatsApp any time, day or night, for pricing, setup and API questions.