Support

Submit a ticket My tickets Knowledge Base API Reference
Welcome
Login  Sign up
Open navigation

Integration Overview

Before we can start recovering your failed payments, your CRM needs to integrate with FlexPay. There are two methods of doing this; API post (Transaction or Recommendation) or batch file. If the initial transaction is a soft decline, the FlexPay recovery engine will analyze the data sent and derive a next best date, time, and gateway on which to process this transaction to obtain an approval. FlexPay sends this information back to your sales tool, which will generate a new transaction on the assigned date and time and thus increase the potential of recovering a transaction that may otherwise have been lost. 

Let's explore the different integration methods:

Transaction Integration

In this failed payment recovery method, FlexPay acts like a transparent layer between the system of record and the payment gateway. Retry attempts are sent through FlexPay to your native gateway. We analyze your request, as well as the response from the gateway, and return our own enhanced response payload in real-time. If the transaction declines again, our response will include a Retry Date & Time. Every subsequent rebill attempt goes through FlexPay until either the transaction is approved, hard declined, or the AI determines it is not recoverable. 

For step-by-step details, please see FlexPay Transaction Process

For the API reference documents, go to Transaction API reference

Recommendation Integration

In this method, FlexPay doesn't communicate with your payment gateway. Instead, your CRM calls FlexPay via API and provides details of a transaction that has declined on its native gateway. FlexPay analyzes the provided payload and responds immediately with a recommendation on when to retry that transaction in the future.

For step-by-step details, please see FlexPay Recommendation Process

For the API reference documents, go to Recommendation API reference


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.