Contis API service notifies the consumer about OTP setting. The client must integrate the call back URL in the Contis API service so that consumer can receive the OTP on the mobile device.
Example of Token OTP notification parameters
Parameters | Type | Description | Default value |
NotificationType | string | Three-digit unique identifier of notification. Numeric value “055” denotes the Authorisation notification. | Blank |
CardID | integer | Unique identifier of the card. | |
OTPCode | string | Unique 6-character, time-limited, one-time-use password sent to the registered mobile number. | |
OTPCodeExpiry | string | The date and time of expiry of the OTP in the format yyyyMMddHHmmss. | |
Mobile | integer | Mobile Number of the consumer. | Blank |
string | Email Address of consumer. | Blank | |
NotificationPreference Type | integer | Look up value that indicates the preference for medium of transmission of the notification. Value “ 1 ” = “ SMS ” and value “ 2 ” = “ Email ” . |
1 or 2 |
DeviceType | string | Device type For Example 01 – Mobile Phone 02 – Tablet 03 – Watch 04 – Mobile Phone or Tablet 05 – Personal Computer |
|
TokenRequestorCode | string | Token requestor code For Example ‘APLPAY’ OR ‘GGLPAY’ OR ‘SAMPAY‘ |
Example of Token OTP notification
The table shows an example of an Token OTP notification sent to the consumer.
Parameter name | Value |
NotificationType | 055 |
CardID | 1402 |
OTPCode | 1122 |
OTPCodeExpiry | 20180927213756 |
Mobile | 919824561785 |
xyz@contis.com | |
NotificationPreferenceType | 1 |
DeviceType | 1 |
TokenRequestorCode | APLPAY |
To Generate the Security Hash
Hash sequence : NotificationType&CardID&OTPCode&OTPCodeExpiry&Mobile&Email&NotificationPreferenceType&DeviceType&TokenRequestorCode