Page Comparison

The FlexitiSDK will capture these events and it will send the response through the function handlers defined on the Widget instance creation.

window.parent.postMessage({
                'eventType': 'flx-success',
                'eventData': {
                    'accountNumber': 2233000 / null
                    'verified': true / false
					'action': Enum [“apply”|“purchase”|“activation”] / null
                }
            }, '*');

Success

‘eventType': ‘flx-success’: When the widget ends, after performing all the corresponding customer verification steps related to the flow, it will send the eventData JSON object with the following structure:

'eventData': {
      'accountNumber': 2233000 / null
      'verified': true / false
      'action': Enum [“apply”|“purchase”|“activation”] / null
}

...

Customer completes a new application and is presented with the account selection screen and selects “Continue to purchase”.

1. this This is when the multiple account screen is presented for a Customer that has more than one account. Any accounts with a derogatory status will not be presented on the multiple account screen. An example of a derogatory status is Fraud or Charged-Off

1. This action ends the widget returning a valid “accountNumber” (the one chosen by the customer) and the “verified” flag as FALSE since no verification method was performed.

2. After the widget ends, the Merchant must redirect the customer to the page their consider appropriate to start a purchase within their Ecommerce (cart, check out, landing page, etc). The widget would need to be presented again to the Customer to confirm their identity.

PURCHASE SCENARIO #4

...

Customer is performing a purchase and is presented with the account selection screen and selects “Continue to purchase”

1. This is when the multiple account screen is presented for a Customer that has more than one account. Any accounts with a derogatory status will not be presented on the multiple account screen. An example of a derogatory status is Fraud or Charged-Off

2. This action allows the customer to continue with the purchase, performing the corresponding identity verification (happy path).

3. This action ends the widget returning a valid “accountNumber” and the “verified” flag as FALSE or TRUE according to the result of the verification method performed.

4. After the widget ends, the Merchant must call the POST authorization endpoint to complete the flow.

...

: Action = Null

Customer cannot proceed with a purchase due to derogatory status’s on an existing account. “action”=null

...