Many modern apps, including PortaPhone, allow users to sign in with a one-time password (OTP) delivered by SMS or email instead of a traditional password. PortaBilling generates and validates OTPs out of the box, but there was no way to brand the emails containing those OTPs. This enhancement enables integration with third-party email platforms, such as Brevo or custom in-house solutions, allowing you to brand emails for OTP verification with your own templates. A middleware application (e.g., a web application that gets EventSender notifications) receives the user details and OTP from PortaBilling and passes them to the email platform. The platform then uses your predefined template to generate and send a branded OTP email to the user.
Owl Telecom offers the PortaPhone app and wants OTP emails to match its brand. The admin creates a custom email template in the external platform, setting the company logo, brand colors, social media links, and other visual elements.
When a user opens PortaPhone and enters their phone number, they receive an email with an OTP that follows the Owl Telecom template. They enter the received code in the app and can use the softphone.
On the backend, PortaBilling generates the OTP and passes it to the external platform via ESPF, which applies the branded template and delivers the email to the user.
Service providers increase brand awareness.
- The account must have a valid email address or phone number configured. Otherwise, OTP delivery via email or SMS will not be possible.
- The IP address of the app requesting the OTP should be specified in the Security.AllowLoginByOTPFrom option on the Configuration web server.
Configuration
Admin should perform the following:
- In PortaBilling:
- On the Configuration web server:
- Define the IP address of the app requesting the OTP in the Security.AllowLoginByOTPFrom.


