1
User enters the mobile number
On the business portal, the end user types their mobile number into the first field.
← Back to NexCode
Playable verification demo
NexCode in action
A video-style animation showing the full OTP flow.
The business portal collects the final customer’s mobile number, NexCode generates and sends the OTP, the customer enters it back into the portal, and NexCode returns a simple verification result to the business.
Your portal
B-number only
OTP generation
SMS / WhatsApp / RCS
YES / NO response
NexCode verification flow
00:00 / 00:20
Scene 1 · Customer data
Your portal
Mobile number
+39 333 123 4567
OTP code
— — — — — —
Request OTP
NexCode
Generate · Send · Verify
NexCode
B-number
OTP
YES
✓ VERIFIED: YES
The customer enters their mobile number
Your portal does not generate OTPs. It only collects the B-number and asks NexCode to verify ownership.
01 / 05
Playing
The full flow, step by step
The business customer does not need to build its own OTP engine. NexCode manages generation, delivery and verification, while the customer portal stays very simple and receives only the final verification result.
2
The portal sends the B-number to NexCode
The company system passes only the mobile number and the OTP request to NexCode.
3
NexCode generates the OTP
The code is created according to the parameters agreed with the business customer, such as code length, validity and channel logic.
4
NexCode sends the OTP to the user
The OTP is delivered through SMS, WhatsApp or RCS.
5
User enters the OTP on the business portal
The end user inserts the received code into the second field.
6
NexCode validates and answers YES or NO
The business receives a simple result confirming whether the user really controls that mobile number.
Request OTP
POST /otp/request
{
"msisdn": "+393331234567",
"customer_id": "retailer-001",
"channel": "sms"
}
Response:
{
"request_id": "req_41a8",
"status": "accepted"
}
Verify OTP
POST /otp/verify
{
"request_id": "req_41a8",
"otp": "847392"
}
Response:
{
"verified": true
}
No OTP engine to build
The customer only needs a simple web form and an integration with NexCode APIs.
Easy for non-technical businesses
Ideal for smaller organizations that need phone verification without complex infrastructure.
Flexible delivery
Choose the best channel for the use case: SMS, WhatsApp or RCS.
Simple result
NexCode answers with a clear verification outcome, so the business can approve or reject the request immediately.
Use NexCode as a plug-in verification layer
Keep your portal simple: collect the number, collect the OTP, and let NexCode handle generation, delivery and verification.