Customer Initiated Transactions
The FlexCharge service needs to receive the customer's activity fingerprinting (SenseJS transmission), and a copy of all processed transactions (Transmit API). This is for all transactions, both accepted and declined transactions. This data is needed to build customer profiles.
Each failed payment transaction also needs to trigger real-time our eligibility process (Evaluate API), which returns whether that failed transaction is eligible for our service or not. Eligible transactions are returned with an Order Session Key, which needs to be used to activate the FlexCharge user interface (UI Widget).
Successful transactions are confirmed via a Webhook or via the Outcome API.
Find your integration type
To complete your integration with FlexCharge you may not need to perform all of the steps above. Simplified integration options are available for merchants who work with gateways and/or processors who are integrated with FlexCharge.
Find the integration type that is best suited to you:
|I'm a merchant, my PSP and GW are not integrated with FlexCharge||Merchant direct integration|
This is a direct full integration.
|I'm a merchant, my PSP or GW are integrated with FlexCharge||Merchant integration via partner|
This is a simplified integration option for merchants that work with Processors or Gateways that have integrated with FlexCharge.
|I'm a PSP/GW Partner, integrating centrally for hosted fields and API merchants||Partner backend integration|
This is a central FlexCharge / Partner integration to simplify the integration effort of hosted fields and API merchants willing to use the FlexCharge service.
|I'm a PSP/GW Partner, integrating centrally for iFrame merchants||Partner front/backend integration|
This is a central FlexCharge integration to simplify the integration effort of iFrame merchants willing to use the FlexCharge service.
You can reduce the effort required to integrate your code with the FlexCharge API by using our postman collection.
Updated about 2 months ago