Page Comparison

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

...

Code Block

breakoutMode	wide
language	js

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

...

Code Block

breakoutMode	wide
language	js

'eventData': {
      'accountNumber': 2233000 / null
      'verified': true / false
      'action': Enum [“apply”|“purchase”|“activation”] / null
      'mfaOptionSelected': Enum [“sms”|“email”|“security_answer”"apply"|"purchase"|"activation"|"retry"] / null
      'widget_session_id': GUID
}

Info
Mandatory: The merchant must call the POST /apply endpoint on a flx-success widget response on the application flow.

...

Scenario Description	“accountnumber”	“verified”	“action”	Implementation
Customer has multiple accounts and chooses to activate an existing account on the account selection screen (pictured below this table).	NULL	FALSE	activation	After the widget ends, the Merchant can open the Flexiti Customer Portal URL (https://my.flexiti.com/index) in a new tab or let the customer perform that action themselves to complete activation.
Customer submits a new application and Flexiti identifies the customer has an existing account. On the account selection screen the customer chooses to continue with the application.	NULL	TRUE or FALSE	apply	After the widget ends, the Merchant must call the /apply endpoint to complete the flow.
Customer submits a new application.	NULL	TRUE or FALSE	apply	After the widget ends, the Merchant must call the /apply endpoint to complete the flow.
Customer submits a new application but cannot proceed with an application due to derogatory status’s on an existing account.	NULL	FALSE	NULL	After the widget ends, the Merchant must inform the customer they cannot proceed with an application.
Customer is performing an application flow and we detect existing account(s) for that customer. Then, the customer chooses to make a purchase with one of those existing accounts.	numeric	FALSE	purchase	Merchant should launch the /init purchase flow with the account number returned.
Customer attempts an application but there is an IT related error.	NULL	FALSE	retry	After the widget ends, the Merchant should display a message that there was an error and either retry the application or return the customer to the previous screen/step.

...

Multiple Account Selection screen in the Flexiti Widget

...

Description	“accountnumber”	“verified”	“action”	Implementation
Customer attempts to make a purchase and completes verification successfully.	numeric	TRUE	purchase	After the widget ends, the Merchant should send the purchase request to the /authorizations endpoint.
Customer attempts to make a purchase and completes verification unsuccessfully.	numeric	FALSE	purchase	After the widget ends, the Merchant should inform the customer that they failed to make a purchase and redirect them back to the checkout to select an alternate payment method.
Customer attempts to make a purchase with an account needing activation and selects activate on the account selection screen.	NULL	FALSE	activation	After the widget ends, the Merchant can open the Flexiti Customer Portal URL (https://my.flexiti.com/index) in a new tab or let the customer perform that action themselves to complete activation.
Merchant sends `personal_information`for a customer performing a purchase who’s account needs activation. They are presented with the account selection screen and choose to continue with a new application.	NULL	FALSE	apply	After the widget ends, the Merchant should redirect the Customer to complete a brand new application.
Customer cannot proceed with a purchase due to derogatory status’s on an existing account.	NULL	FALSE	purchase	After the widget ends, the Merchant must inform the customer they cannot proceed with a purchase.
Customer attempts an application but there is an IT related error.	NULL	FALSE	retry	After the widget ends, the Merchant should display a message that there was an error and either retry the application or return the customer to the previous screen/step.

Versions Compared

Old Version 18

New Version 19

Key

Multiple Account Selection screen in the Flexiti Widget