The FlexitiSDK will capture these events and it will send the response through the function handlers defined on the Widget instance creation.
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
'eventData': {
'accountNumber': 2233000 / null
'verified': true / false
'action': Enum [“apply”|“purchase”|“activation”] / null
} |
| Info |
|---|
Mandatory: The merchant must call the POST /apply endpoint on a flx-success widget response on the application flow. |
...
Based on the application or purchase flow, there will be certain actions (“action” data) that the customer can choose which will be returned through the “flx-success” event. The Merchant can then determine the next step for the customer depending on these scenarios.
Application Scenarios
...
Scenario Description | “accountnumber” | “verified” | “action” | Implementation |
|---|---|---|---|---|
Customer has multiple accounts and chooses to activate an existing account on the account selection screen ( |
...
Where a Customer has more than one account, an account selection screen (multiple account selection screen below) is presented to the Customer with a call to action. If the customer chooses an account requiring activation, the customer will be informed to activate their account via Flexiti’s online account servicing tool, the Customer Portal (https://my.flexiti.com/index).
...
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 selects “Continue with application” |
...
This action allows the customer to continue with a new application and perform the corresponding identity verification steps.
...
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 |
...
This action allows the customer to continue with a new application and perform the corresponding identity verification steps (happy path).
...
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 |
...
This is when a customer has an account with a derogatory status which will prevent them from continuing with the application flow. An example of a derogatory status is Fraud or Charged-Off.
...
. | 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 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. |
...
Multiple Account Selection screen in the Flexiti Widget
Purchase Scenarios
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 |
...
Purchase Scenarios
...
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 (“Continue to activate“ button) |
...
Where a Customer attempts to make a purchase with an account needing activation, an account selection screen (multiple account selection screen below) is presented to the Customer with a call to action. If the customer chooses an account requiring activation, the customer will be informed to activate their account via Flexiti’s online account servicing tool, the Customer Portal (https://my.flexiti.com/index).
...
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 is performing a purchase with an account needing activation and is presented with the account selection screen and selects “Continue with application” |
...
This action allows the customer to start with a new application before making the purchase.
...
NULL | FALSE | apply | After the widget ends, the Merchant should redirect the Customer to complete a brand |
...
PURCHASE SCENARIO #3: Action = Purchase
...
new application |
...
. |
...
Customer |
...
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.
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: Action = Null
...
cannot proceed with a purchase due to derogatory status’s on an existing account. |
...
This is when a customer has an account with a derogatory status which will prevent them from continuing with the purchase flow. An example of a derogatory status is Fraud or Charged-Off.
...
NULL | FALSE | NULL | After the widget ends, the Merchant must inform the customer they cannot proceed with a purchase. |