The Scenario.

Each verification process initiates only upon the definition of a scenario. Within said scenario, all the business logic pertaining to the user's verification requirements is delineated.

The Scenario Object:

Parameter NameDescriptionValidationsDefault ValuesRequired
settingsAn object representing various general settings for the scenario document--yes
nameThe name of the scenarioString - Max chars 60-yes
sticky_channelA boolean value indicating whether this scenario will use the stickiness featureObject-no
sticky_channel_ttlThe time to keep track of the last used channel (days)booleanFALSEno
psd2_compliantPSD2 is the 2nd Payment Services Directive established by the European Banking Authority (EBA). This directive is designed to drive payment innovation and data security by reducing competitive barriers, mandating new security processes and encouraging standardized technology.booleanFALSEno
pin_optionsAn object representing various settings for the PIN CodeObject-no
ttlThe time frame that the PIN code is valid for verification (seconds)int10yes
securityAn object representing various security settingsObject-yes
rate_limitingAn object representing various rate-limiting settingsObject-yes
ipIndicates if rate-limiting applies for an IPbooleanTRUEyes
destinationIndicates if rate-limiting applies for a destination addressbooleanTRUEyes
intervalThe intervals for rate-limiting to apply (minutes)intTRUEyes
max_attemptsMaximum attempts allowed per IP and/or destinationintTRUEyes
block_scoresAn array representing which fraud score results will be automatically blocked for verificationobjectFALSEyes
array_valuesThe values to blockstring - Allowed values: high risk, moderate risk, low risk-True if block_scores array exists
channelsAn array of objects representing the channels used for verificationObject-yes
channelThe name of the channelAccepts: sms, viber, voice, flashcall-One of 4 values is required
fromThe sender of the message (SMS channel)numeric string (max length 16) or alphanumeric string (max length 11)Verifyyes if SMS channel is used
messageThe body of the message (SMS channel)String - must contain @@pin argument once and only onceYour PIN is @@pinyes
flashIndicates if the SMS is a flash SMS (SMS channel)BooleanFALSEno
transcodeIndicates if the message body will be transcoded (SMS channel)BooleanFALSEno
orderDefines the priority orderNumeric1yes
next_event_inTime for the next event in secondsNumeric - min 20 max 60 for all channels except voice (min 60 max 120)30no
sender_info_tracking_idThe ID of the registered Viber Sender (Viber channel)string-yes if Viber channel is used
messageThe body of the message (Viber channel)String - must contain @@pin argument once and only once-yes if Viber channel is used
orderDefines the priority orderNumeric2yes
next_event_inTime for the next event in secondsNumeric - min 20 max 6030no
fromThe sender of the message (voice channel)StringVerifyyes if voice channel is used
messageThe body of the message (voice channel)String - must contain @@pin argument once and only onceYour PIN is @@pinyes if voice channel is used
languageThe language for the message (voice channel)String - Language of the voice message - VALUES: "en-US", "de-DE", "fr-FR", "it-IT", "pt-BR", "es-ES", "es-LA", "en-GB", "el-GR", "bg-BG", "pl-PL", "hu-HU", "sv-SE", "ru-RU"en-USyes if voice channel is used
genderThe gender of the voice (voice channel)String - Gender of the voice - VALUES: "male", "female"maleyes if voice channel is used
repeatNumber of repetitions of the message (voice channel)int1no
dtmf_requiredIndicates whether to start playing the message after a tone is pressed (voice channel)booleanFALSEno

Verification process statuses

StatusDescription
IN PROGRESSVerification is still in progress
COMPLETEDVerification is completed
FAILEDVerification is failed
EXPIREDVerification has expired
CANCELEDVerification has been canceled by the user
FRAUDVerification has been detected as Fraud.

Verification process channel statuses

StatusDescription
NOT ACTIVATEDVerification is still in progress
SENDINGVerification is completed
FAILEDVerification is failed
SENTVerification has expired
SKIPPEDVerification has been canceled by the user

Custom validation rules

If the scenario is not PSD2 compliant, it necessitates that the "@@pin" keyword must be included in the message exactly once.

If the scenario is PSD2 compliant, it mandates that each of the "@@pin," "@@amount," and "@@payee" keywords should be included in the message exactly once.


Fraud scores

Fraud ScoreDescription
high riskThe verification process has been marked with a high risk score. We recommend canceling the verification.
moderate riskThe verification process has been marked with a moderate risk score. We recommend canceling the verification.
low riskThe verification process has been marked with a low risk score. We recommend canceling the verification.
looking goodThe verification process has been marked with a positive score. We recommend proceeding with the verification.

Voice channel gender

male
female


Scenario Features


Sticky Channel:

Dictates whether the last successful channel will be utilized for a specific destination number and the duration of this adherence.

Pin Options:

Specifies the validity period for the verification until it expires.

Security Options:

Imposes rate limits on the number of requests a destination number or IP address can submit within a standard interval.

Fraud Detection:

Furnishes insights into the likelihood of fraud for each verification and permits automatic blocking of certain fraud scores.

Channel Configuration:

Outlines the channels to be employed, their sequence, and the interval between them during the verification process.