Open navigation

Enterprise Process

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. Let's go over this integration step-by-step.

  1. A merchant attempts to rebill a customer, but the transaction is declined by the gateway.
  2. The merchant schedules to process the retry through FlexPay's API the next day.
  3. FlexPay reviews the transaction details and performs any data cleanup if it determines it will increase the likelihood of success. The transaction is sent directly from FlexPay to the Gateway.
  4. FlexPay receives the response from the Gateway.
  5. If the transaction was not approved and the recovery engine determines the transaction is recoverable, it sends a response back with the best date and time to retry the transaction.
  6. The merchant schedules the transaction and retries on the date and time provided by FlexPay. 
  7. The transaction is resubmitted through FlexPay.

The process continues until there is a successful recovery, a hard decline, or FlexPay no longer considers the transaction recoverable. 

Follow this link to access the API reference page.

Daniel is the author of this solution article.

Did you find it helpful? Yes No

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