Default Message Content
The default verification message sent by Prelude is:12345 is your verification code.We provide this template translated into 31 different locales. Prelude automatically detects the phone number’s locale from its country code and sends the verification message in the appropriate language. We strongly recommend starting the message with the code so it remains readable even when truncated (for example, on a watch or with large font sizes). For instance: “12345 is y…”. This layout has been battle-tested against many alternatives to optimize conversion and automated code detection. We’ve also registered this template worldwide to ensure optimal deliverability and minimize the risk of carrier filtering.
Manually specifying the locale
You can manually specify a custom language for the message by setting theoptions.locale parameter on the POST /v2/verification endpoint.
A BCP-47 formatted locale string with the language the text message will be sent to. If there’s no locale set, the language will be determined by the country code of the phone number. If the language specified doesn’t exist, it defaults to US English.
locale parameter uses the BCP-47 format to specify the language of the message.
The BCP-47 format is a standard for identifying languages and their variants. It is a two-letter language code followed by a dash and a two-letter country code. For example,
en-US is US English and fr-FR is French from France.Supported locales
Locales supported to send verification messages.
Supported locales
Locales supported to send verification messages.
- Arabic (
ar) - Bulgarian (
bg) - Chinese (
zh) - Chinese (Taiwan) (
zh-TW) - Czech (
cs) - Danish (
da) - Dutch (
nl) - English (
en) - French (
fr) - German (
de) - Greek (
el) - Hebrew (
he) - Hungarian (
hu) - Italian (
it) - Japanese (
ja) - Latvian (
lv) - Lithuanian (
lt) - Macedonian (
mk) - Norwegian (
no) - Polish (
pl) - Portuguese (
pt) - Romanian (
ro) - Russian (
ru) - Serbian (
sr) - Slovak (
sk) - Slovenian (
sl) - Spanish (
es) - Swiss German (
de-CH) - Turkish (
tr) - Ukrainian (
uk) - Vietnamese (
vi)
If a locale is not listed above and you need it for your implementation, contact our support team to get it added to the list.
Customization Options
Prelude provides a few options to customize the verification message content sent to your users.These options may not be available on channels other than SMS. Availability depends on the selected .
To find information about branded sender IDs, see the Custom Sender ID documentation.
Brand Suffix
You can add a brand suffix to the verification message from the Prelude dashboard.12345 is your verification code for Acme Inc.
Best practices:
- Avoid setting a brand suffix that includes a link or text that could be interpreted as a link. Carriers may block messages that contain links.
- Do not include any special characters such as emojis. Some carriers may block messages that contain special characters, or you might be charged more for the message.
This feature is subject to prior approval. Contact our support team to enable it on your account free of charge.
Security Suffix
You can add a security suffix that reminds users not to share the verification code with anyone.12345 is your verification code. Do not share it.
This feature is subject to prior approval. Contact our support team to enable it on your account free of charge.
Built-in Templates
For certain use-cases, we provide built-in templates that you can use to send verification messages.PSD2
The Payment Services Directive 2 (PSD2) is a European regulation that aims to make online payments more secure. The Verify API provides a built-in template for sending verification codes for PSD2 transactions.OTP code length
You can set the verification code length either:- Through the Prelude dashboard.
- By setting the
options.code_sizeparameter on thePOST /v2/verificationendpoint.
The length of the verification code sent to your users.
Custom OTP codes
Although Prelude can generate a code for you, you can also generate your own custom OTP. This is useful when:- You use a multi-provider setup where you can attribute which provider converted the user.
- You want to integrate Prelude effortlessly with an existing verification flow.
- You need to use alphanumeric characters in the code (subject to Prelude’s approval).
This feature is subject to prior approval. Contact our support team to enable it on your account free of charge.
options.code_size parameter on the POST /v2/verification endpoint.
How to use custom codes in your verification flow
To use a custom code for your verification flow, set theoptions.custom_code parameter to the code you want to use on the POST /v2/verification endpoint.
The custom code must be a string of 4 to 8 numeric characters.
The custom code you want to use. The code needs to be a string of 4 to 8 numeric characters.
Caveats
To ensure optimal performance:- Send a different custom code for each verification request or retry.
- Always call
POST /v2/verification/checkto verify the code when the user enters it.
Prelude uses the custom code to identify which provider converted the user. If you reuse the same custom code across multiple verification requests, Prelude will not be able to determine which provider converted the user and will not be able to attribute the conversion to a specific provider, which reduces the effectiveness of routing optimization for your account. You can read more about the multi-routing system here.
Alphanumeric custom codes
Prelude supports alphanumeric custom codes.This feature is subject to prior approval. Contact our support team to enable it on your account free of charge.