IndiSell Docs Dashboard →
Messaging & notifications

OTP delivery

Verify every shopper's phone with a one-time code — delivered by the platform by default, or through your own connection-backed methods in the priority order you choose.

Every checkout starts with a one-time code that verifies the shopper's phone. By default these go out on IndiSell's own SMS and WhatsApp accounts — nothing to set up, it just works.

To send from your own number, set up OTP delivery methods — an ordered list of channels, each backed by a saved connection. Codes try your methods top to bottom; the first that delivers wins, and the platform account is always the final safety net.

ℹ️
Find it under Settings → Integrations → OTP Verification. Add a WhatsApp account under Connections first.

How methods work

Each method is one channel backed by one connection:

PartWhatsApp methodSMS method
AccountA WhatsApp connection (Meta / MSG91)An MSG91 connection
TemplateAn approved template, loaded live from the accountYour DLT template ID + variable names
VariablesMap each {{n}} (the code, store name, custom text)The OTP + store variable names

Methods run as a fallback chain in the order you set:

  • Priority — drag the handle (⠿) or use the arrows. The first enabled method that delivers wins.
  • On / off — a switch per method. A disabled method is skipped; if all are off, OTP falls back to the platform account.
  • Resend chips — the shopper's "resend via SMS / WhatsApp" chips still switch channels within your methods.

Add a method

1
Add method

On the OTP page, click + Add method. It opens a dedicated page with a live preview on the right.

2
Pick channel + account

Choose WhatsApp or SMS, then the connection that sends it — the account list is filtered to that channel.

3
Pick the template

For a Meta account the approved templates load in a dropdown. Selecting one auto-fills the variable rows and updates the preview.

4
Map the code

Map {{1}} to the OTP code (authentication templates use exactly one variable). Save — it appears in the methods table.

💡
The template picker warns if a template has more than one body variable — an authentication template should carry exactly one (the code). The copy-code button always carries the code.

SMS methods

An SMS method sends through an MSG91 connection using your DLT-approved template. On the method you set the DLT template ID, sender ID, and the variable names your template uses (the code, and optionally the store name). The MSG91 auth key comes from the connection.

⚠️
India-only rails: OTP SMS and WhatsApp dial +91. International checkouts are verified differently — see Sell internationally.

Delivery order & the platform fallback

  • With no methods configured, OTP uses the platform SMS + WhatsApp accounts — the zero-setup default.
  • With methods configured, IndiSell tries them in order. If all enabled methods fail (a bad template, an expired token), it still falls back to the platform account so a shopper is never stranded at the login step.

This means adding your own methods is always safe: at worst, delivery falls back to the platform.

Legacy setup

Earlier, OTP asked for "your own SMS sender" and "your own WhatsApp account" directly on this page. That's been replaced by connection-backed methods — connect the account once under Connections, then add a method here. Your existing setup keeps working; move it to a method when convenient.