SMS Authentication Service

0 votes

Hi Duo,

Hope you are doing well! I have a few questions about the SMS Authentication Service update that we received through the OSS Service Notification system.

As a OneSpan Sign account owner/admin, below is the update in regards to the SMS Authentication service which we received recently.

In August 2022, a new directive was put in place by CWTA (Canadian Wireless Telecom Association), obliging Canadian carriers to deprecate shared “branded” short codes. A shared short code is a 5-6 number managed by a service provider, that carries traffic from multiple customers. Carriers are now requiring that if organizations want to add their branding to the message, to obtain their own dedicated ID using a dedicated short code. If organizations wish to remain on the same code, no branding will be allowed.

What do customers need to do?
1.If you do not require branding customization for SMS messages, there is no action required on your part.
2.If you do require branding customization for SMS messages, we recommend you use your own Dedicated Short Code. By doing so, your customers will receive branded SMS messages originating from your organization.

In reference to point #2, can you please elaborate more on what it means?
a. What is a ‘Dedicated Short Code’?
b. How do we obtain a ‘Dedicated Short Code’?
c. How do we apply ‘Dedicated Short Code’ to our existing accounts?
d. How does this impact accounts that are used in multiple regions?

Please advise.

Thank you & Regards,



Reply to: SMS Authentication Service

0 votes

Hi Rajiv,


Thanks for your post! I'd like to add some background information first:
OSS uses Twilio Verify V2.0 as the default SMS service (for SMS authentication). The SMS message received by signers typically looks like this “Your SMS/{branding} verification code is: <passcode>”.  If you have your branding customization for SMS message, the "SMS" part will read your own branding.

However due to the reason described in the communication email, Twilio now disables the friendly name feature for messages sent to Canadian numbers because OSS service shares the short code for multiple brands. That's why in the communication email, OSS suggests you to create your own Twilio account (in which case you have your own dedicated short code) and have the Twilio account ID and Twilio API Key specified in your account settings via Backoffice so that the SMS messages will only go through your Twilio account.



Duo Liang OneSpan Evangelism and Partner Integrations Developer

Reply to: SMS Authentication Service

0 votes

Hi Duo,

At present the passcodes come with header as "TWverfiy". Could you please confirm on the ways to change the header more for the customer specific like 

<<customer>> Contracts.


Best Regards


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off