Use managed Verify for OTP and trust flows

Verification should read like a managed trust workflow. AfriRoute owns OTP generation, expiry, retry limits, and delivery fallback; your app starts a challenge, checks the code, then creates its own session.

Docs mode

Reference and guide

Keep the task clear, the example nearby, and the next step obvious.

Back: OTP Verification Next: Payments

Recommended developer flow

Start a managed verification challenge, store only the returned verification identifier, collect the user code, and check it through AfriRoute Verify from your backend.

Use SMS docs only for normal messaging. Do not teach customers to build custom OTP storage, retry limits, or session tokens in public quickstarts.

Verify helper calls

afriroute.verify.start({ phone, channel })

afriroute.verify.check({ verificationId, code })

Design rule

Explain the user journey plainly: start verification, check the code, handle invalid code or expiry, then direct developers to the errors page for exact troubleshooting patterns.

Keep verification start and code check as separate backend steps.

Make expiry, retry, and invalid-code states explicit in the docs.

Use messaging for notifications, not as a replacement for managed OTP infrastructure.

Test in sandbox SMS integrations Verification errors

OTP Verification

Payments

Verification

Managed OTP and confirmation flows

Use AfriRoute Verify for OTP workflows. AfriRoute owns code generation, expiration, rate limits, delivery fallback, and verification status; your app owns the final user session.

Endpoint

SDK helper: afriroute.verify.start

Start

const verification = await afriroute.verify.start({
  phone: "+251900000000",
  channel: "sms",
  fallbackChannel: "voice"
});

Quick links

OTP with SMS Verification errors Security guidance

Ask the assistant

How do I send OTP?