The FlexitiSDK will capture these events and it will send the response through the function handlers defined on the Widget instance creation.
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
window.parent.postMessage({
'eventType': 'flx-success',
'eventData': {
'accountNumber': 2233000 / null
'verified': true / false
'action': Enum [“apply”|“purchase”|“activation”] / null
'mfaOptionSelected: Enum [“sms”|“email”|“security_answer”] / nul
}
}, '*'); |
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:
| Code Block | ||||
|---|---|---|---|---|
| ||||
'eventData': {
'accountNumber': 2233000 / null
'verified': true / false
'action': Enum [“apply”|“purchase”|“activation”] / null
'mfaOptionSelected: Enum [“sms”|“email”|“security_answer”] / nul
} |
| 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 choses 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. |
...