Device registration flow

Device Registration on the Contis platform is mandatory to enable the customer to use the multi authentication capability provided by the SDK. There are two types of device registration flow available:

  1. Direct Device Registration
  2. Combining an SCA event with Device registration

Both flows require the customer to receive and enter an OTP as a one off event.

These flows are detailed below:

Direct device registration

  • Direct device registration flow is used for registering a customer’s device on the Contis platform.
  • The client calls the RegisterDevice method in the SDK and Contis will send an OTP (see OTP delivery section):
  • The customer enters the OTP on the SDK OTP UI screen. This enables the device to be registered.
  • Important! It will only be possible for Contis to send Push notification for future SCA events directly to the customers mobile device if this RegisterDevice method is used.

Combining an SCA event with Device Registration

If the client has not registered the customer’s device by calling the RegisterDevice method, then any event which requires SCA, will require the DoSCA method to be called and Contis will send an OTP (see OTP delivery section):

  • The customer enters the OTP on the SDK OTP UI screen. This enables the SCA event to be completed and the customer device is , automatically registered on the Contis platform.
  • For example, if a customer makes an SCA qualifying payment through the app on a non-registered device, an OTP will be sent (see OTP delivery section). When the customer enters the OTP, the SCA event is completed and the customer device is registered on the Contis platform.
  • Important! It will not be possible for Contis to send future Push notification authentications directly to the customers mobile device if DoSCA method is used for device registration.

Confirmation email

When a customer device has been successfully registered, there is an option for Contis to email the customer to inform them of the successful registration. This will be set to ‘off’ as the default, unless the client requests it be set to ‘on’.