How does FlexFactor work?
Customer Initiated Transactions
Customer initiated Transactions (CIT) are straight sales (or standalone transactions) where customers initiate payments through a checkout page for products or services they wish to acquire.
In order to rescue these transactions, FlexFactor must be integrated in the checkout as well as in the merchant's back office.
 | 1. The customer is willing to complete a purchase and proceeds to check out to provide their details and payment info. If the payment transaction is accepted, FlexFactor remains invisible. |
 | 2. The payment transaction is declined but, instead of showing a decline message, the failed payment transaction is sent immediately to FlexFactor. |
 | 3. FlexFactor assesses the failed payment transaction. Eligible transactions are confirmed by Flex within a couple of seconds. |
 | 4. The payment transaction is accepted via FlexFactor. The process is frictionless and the customer is unaware that their original payment transaction failed. |
 | 5. The order is completed. The customer receives a merchant-branded email confirming the order. |
 | 6. The customer payment method is charged. This is done by FlexFactor using a smart descriptor feature, ensuring that the merchant's name is displayed on the customer's statement. |
CIT are rescued in real time
Customer will have a quick answer for their payment request.
FlexFactor will provide a definitive status within seconds.
Merchant Initiated Transactions
Merchant Initiated Transactions (MIT) are recurring subscription rebills, that can be rescued by FlexFactor.
In order to rescue these transactions, FlexFactor must be integrated in the merchant's back office.
| 1. The recurring payment transaction is declined, instead of reaching out to the customer, the failed payment transaction is sent to FlexFactor for a period of time. |
| 2. FlexFactor assesses the failed payment transaction. Flex will work on this transaction for a certain amount of days/weeks. |
| 3. The payment transaction is accepted via FlexFactor. Merchant's back office is updated. |
| 4. The customer payment method is charged. This is done by FlexFactor using a smart descriptor feature, ensuring that the merchant's name is displayed on the customer's statement. |
MIT are rescued asynchronously
FlexFactor will work on these transactions in an async way. This duration (days, weeks) is up to your configuration.
Updated 7 months ago