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

'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.

...

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.
Customer is performing a purchase with an account needing activation and is presented with the account selection screen and chooses 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	NULLpurchase	After the widget ends, the Merchant must inform the customer they cannot proceed with a purchase.

...

Versions Compared