This add-on verifies that a customer really owns the phone number or email they provide, using a one-time password (OTP) sent by SMS or email. You can require verification at checkout, login, or registration, and let customers sign in by phone.

Plan: Pro (Beta)   Add-on: Verification   Where: StoreEngine → Settings → Verification 

What You Can Do

• Send a verification code by SMS (Twilio, Vonage, or generic) or by email.
• Require customers to verify before checkout, login, or registration.
• Let customers use their phone number as their login identity.
• Optionally make OTP the only way to sign in (no passwords for customers).
• Reduce fake orders by requiring verified contact at checkout.

Turn On Verification

1. Go to StoreEngine → Add-ons.
2. Toggle on Verification.
3. Configure at StoreEngine → Settings → Verification.

Configure Verification

Identifier Mode

Choose how customers identify themselves:

• Email only — customers are identified and verified by email address.
• Phone only — customers are identified and verified by phone number. This option requires an SMS gateway.
• Phone or email — customers can use either a phone number or an email address.

Default dialing code — the country dialing code applied to phone numbers, entered as digits only (for example, 880).

Verification (Anti-Fake Order)

• Require OTP verification of the customer contact at checkout — customers must verify their phone or email with a code before they can place an order.
• Force OTP for every login & registration — customers sign in only with a code; this disables password sign-in for customers. Staff with admin or manager roles can still use passwords.

OTP Behaviour

SMS Channel

Pick the Active SMS gateway and enter its details. The Generic HTTP gateway lets you connect any SMS provider that accepts an HTTP request.

• Endpoint URL — the provider’s send URL (for example, https://api.example.com/send).
• HTTP Method — the request method, typically POST.
• Body Content-Type — the request body format, such as form.
• Authorization Header (optional) — an auth token if your provider requires one (for example, Bearer xxxx).
• Body Template — the request payload, for example {"to":"{to}","message":"{message}"}.
• SMS message template — the text customers receive, for example Your {store_name} verification code is {code}.

Tokens: {code}, {store_name}.

Email Channel

Email OTP requires no extra setup. Customise the message sent to customers:

• Email subject — the subject line, for example Your {store_name} verification code.
• Email body (HTML) — the HTML content of the verification email. Insert the code with the {code} token.

Tokens: {code}, {store_name}.

Save Your Changes

Click Save Settings at the top right of the page to apply your configuration.

Troubleshooting