We’ve introduced Inline Retry, a treatment that quietly retries eligible failed payments in real time so you can recover more approvals, get access to cash sooner, and send fewer payments into longer recovery flows.

When a transaction fails with a treatable soft decline (for example, temporary issuer or network issues), Revaly now automatically checks eligibility, may adjust how the payment is sent based on the failure reason, performs a single immediate retry on the first eligible attempt in the series, and then returns one final response to your system as it does today.

We’ve introduced a new Invoice Reconciliation report to give you greater visibility into how your FlexPay fees connect to the recovered transactions. It’s designed to clarify billing by showing gross recovery, refunds that reduce your billable total and the resulting net recovery.

If your system sends refunds to FlexPay via API, those will appear directly in the report, automatically discounted from your fees. If you share refunds manually, they won’t be reflected in the report itself, but they’ll still be applied to your invoice.

You can view data by week or month, depending on your selected date range, drill down to specific days, and even zoom in at the transaction level when needed. If anything looks off or needs clarification, please contact the team, and we'll happily walk through the details or apply adjustments.

📖 Read the full documentation

We've added new configuration options to give you more control over how FlexPay handles failed payments on Stripe subscriptions:

Include failed payments at subscription creation
By default, FlexPay only processes failed rebill attempts. If you'd like FlexPay to also handle failures that occur when a subscription is first created, enable this setting in your integration.

Calculate the cancellation delay from invoice creation
The default behavior calculates the cancellation delay from the moment a hard decline is received. You can now choose to calculate this delay based on the invoice creation timestamp instead—useful for subscription models with delayed processing logic.

Read more about it in the Stripe configuration documentation.

We’ve rolled out major updates to the FlexPay Client Portal, introducing a new dashboard that gives you a clearer understanding of how recovered payments contribute to your business over time by highlighting the revenue impact of customer retention. You’ll also notice a simplified navigation menu and a new report that helps you break down transactions by currency.

Here are the docs for the major new reports:

Dashboard

Recovered Customer Retention

Transactions by Currency

Merchants using FlexPay alongside the payment orchestrator MassPay now have additional fields available.

Merchants can send customer_id as a gateway-specific field, which represents a reference number for the customer within MassPay. Note that using this value will overwrite thecustomer_reference_id when sending the payload to MassPay.

Furthermore, processor_id_external is now passed back to the merchant as a gateway specific response field. This represents the transaction ID created by the external processor.

Find MassPay details under supported gateways.

FlexPay is now integrated with Payrix. Part of Worldpay platforms, Payrix is known for embedded financial services, especially for SMEs.

See Payrix in the gateway API reference.

We’ve completed the migration of all Client Portal users to the new Multi-Factor Authentication (MFA) system. This enhancement strengthens account protection with a second layer of authentication. To log into the portal, a authentication app like Microsoft Authenticator is required in addition to the password. This update also adds self-service tools like forgotten password.

For detailed instructions on the setup process, refer to our User Account Setup Guide.

FlexPay’s Account Updater functionality now supports a broader range of payment gateways, helping merchants recover more by automatically updating expired or replaced card details.

Newly supported gateways include: Adyen, Cardworks America, Inovio, Paysafe, WorldPay Litle v11, NMI Direct, PayRilla, BillaPay and Apexx.

This expansion enables a higher recovery rate for merchants recovering non-tokenized credit cards on these gateways.

Our integration with Paysafe now has the field externalInitialTransactionId to pass on the Card Scheme Transaction Id. This is a reference to the initial payment transaction in the recurring plan that was not processed through Paysafe.

See our full Paysafe API documentation here. Search for the field name in the Paysafe documentation to get more details on the recurring plan setup.

We added a small user experience enhancement on the Integration page. For convenience, when generating an API key users can now use the a button to the right of the key to copy it. See full instruction documented here.