# Setup of SMS OTP
With the Signicat SMS OTP service, you can perform SMS-based user authentication.
Integration with SMS OTP is done similarly to other Signicat's eID methods. This page describes how to set up SMS OTP on the Signicat Dashboard (opens new window)
For more general information on how to integrate with Signicat, see the Quick start guide.
Page contents
# Initial preparations
This set-up guide assumes you have completed the following initial preparations:
- Sign up to the Signicat Dashboard (opens new window).
- In the Signicat Dashboard, set up an organisation, an account and a domain.
Sandbox account
We recommend you create a sandbox account to test our services before implementing them in production.
# Add SMS OTP
To use an ID method, you first need to activate it. In the Signicat Dashboard:
- Go to eID Hub > ID Methods (opens new window).
- Select Add new.
- Choose SMS OTP from the list and save.
SMS OTP should now appear in the list of available ID methods with the status set to "Active".
# Customise SMS service settings
When using the Signicat SMS OTP service to send OTP codes to end-users, your integration inherits the SMS settings configured in the Signicat Communication service.
On the Communication > SMS (opens new window), you can manage the SMS settings for your account. In particular, you can customise:
- SMS sender name
- SMS provider (primary and secondary)
Learn more about the SMS settings below or in the Communication SMS documentation.
# Customise SMS sender name
A custom SMS sender name lets you unify the user experience with your own brand and products. By changing the sender name, you can display your business name to the recipient of the SMS.
By default, the SMS sender name is set to "Signicat". You can change the sender name in one of two ways:
- Global level: Applies to all SMS messages you send. You change the setting on the SMS (opens new window) page in the Signicat Dashboard. For more details, see the Communication > SMS documentation.
- Request level: Overrides the SMS sender name in a specific authentication flow/request. You pass the SMS sender name as a parameter in the authentication request. When employed, this method has precedence above all other options. Find out how to do this for each protocol in the respective guides below.
# Set up a connection with a protocol
To establish a connection between Signicat SMS OTP service and your application, you need to use an authentication protocol, like OpenID Connect (OIDC) or SAML 2.0. We recommend using OIDC, since SAML 2.0 is much more complex to implement on your side and usually requires a federation agent already in place.
Alternatively, you can integrate with Signicat Authentication REST API. You can find more information on the different types in the Authentication protocols section.