Identity Connect DIM Callbacks

The documentation for the identity connect DIM callbacks

By default, identity connect will render blank inputs. A phone number, birthday month, or birthday day may to be passed directly to the module to save the user from having to enter the information themselves. As another default, the module will utilize a verification URL that must be clicked to proceed for the end user. If you would instead prefer to use an OTP, you can leverage a runtime parameter called out below. To do so, pass the information in the dropinConfig object as illustrated below:

dropinConfig: {
    module: 'identity-connect',
    token: token,
    phoneNumber: '5555555555',
    verificationStrategy: 'SMS_OTP',  
    month: 12,
    day: 2, 
    year: 1990
  },

All three date parameters may be passed as either a string or a number, but they will be parsed and validated when the module loads. In the case that an invalid parameter has been passed (input - month: 2, day: 31), the invalid parameter will be treated as if it were not passed at all (output - month: 2, day: undefined).

Within the verification strategy parameter you can choose from two options 'SMS_OTP' or 'SMS_URL'. If verificationStrategy is not provided, it will default to 'SMS_URL'.

onError

The Identity Connect Dropin Module triggers the following onError methods:

  • API_TIMEOUT - this method is triggered when the connection attempt times out after more than 90 seconds.
  • DIM_ERROR - this method is triggered when the Identity Connect module encounters an internal error.
onError(metadata){
    // your code
}

{
    'eventName': '{eventName}',
    'message': '{message}',
    'metadata': {
        // details related to error
    }
}

onEvent

The following onEvent methods are triggered by the Identity Connect DIM:

  • USER_SUBMISSION - this event is triggered when the user submits their information, and the connection process is initiated.
  • LINK_CLICKED - this event is triggered when the link sent to the user's device is clicked.
  • IDENTITY_CONNECTED - this event is triggered when the user successfully connects their identity.
  • IDENTITY_NOT_CONNECTED - this event is triggered when the attempt to connect the user's identity has failed.
onEvent(metadata){
    // your code
}

{
    'eventName': '{eventName}',
    'message': '{message}',
}

To learn more about our debt APIs and 1-click solutions, visit spinwheel.io.