Advanced CIT Integration

This integration allows you to capture more declined transactions. It requires additional features.


CIT are transactions happening on a checkout page (e.g.: straight sales or initials). Advanced integration requires the implementation of these overall components throughout the frontend and backend.

This integration comprises 2 additional components: the UI Widget, and an async order status update.

Advanced/Standard difference

The UI Widget is the advanced feature that allow direct customer input.

When a transaction is declined by the PSP and sent over to FlexCharge with POST /evaluate, the response will be either APPROVED, DECLINED or CHALLENGE. Unlike the Standard integration, the Advanced integration can rescue transactions that require a CHALLENGE.

CHALLENGE status is returned when the transaction could be rescued by FlexCharge if some additional/corrected information are provided (e.g.: CVV, billing address).

Example of challenge: CVV was incorrect.  
Transaction can be rescued by customer direct input.

Example of challenge: CVV was incorrect.
Transaction can be rescued by customer direct input.

Additional integration steps

Heads up

All steps from the Standard integration must be in place before integrating these additional steps.


7. UI Widget

In addition to SenseJS, this second component must be embedded and invoked on the checkout page.

Embed and invoke the UI Widget to allow customer direct input.


8. Update the order status

When using the UI Widget, you will get a async response. The UI WIdget will be long polling for FlexCharge's response in real time, but the definitive order status must be retrieved on the server side.

This can be done in two ways:

Build your integration

Your integration build will depend on the characteristics of your technical ecosystem.

Unsure what steps you can/need to perform? Let's schedule a call!