We’ve updated the existing detailed GET List response to include custom variables when the includeCustomVariables query parameter is set to true. This change allows merchants to access these variables for internal reconciliation purposes. If the parameter is not specified or set to false, custom variables will not be included.

This enhancement is particularly useful for merchants integrated with FlexPay using the Enterprise with Scheduler integration.

Example Request:

{{APIUrl}}/transactions?responseType=detailed&includeCustomVariables=true

For more details, please refer to the List API documentation.

FlexPay has added a new integrated gateway- Tempus Technologies. Merchants choose Tempus for their technology as well as high-touch support and customizations.

Learn more about gateway capabilities in the API docs.

Merchants using the Adyen payment gateway now have access to an additional field. line_items can be used to include additional pricing and product information referring to a specific line item in the invoice.

See the full list of Adyen API fields here.

Merchants using the Inovio gateway can now use additional fields for better approvals and improved operations.

The card_on_file_flag and trans_rebill_type are used to flag the transaction as merchant-initiated. Doing so is likely to improve the recovery rate and ensures compliance with card network rules. We've also added xtl_order_id mbshp_id_xtl to make it easier to reference transaction with other systems for an order or membership.

See the Inovio API documentation here.

FlexPay has integrated with CardWorks America, allowing merchants using this gateway to recover more failed payments. CardWorks America prides itself with numerous payment innovations and next day funding.

Find the API reference here.

To enhance approval rates and follow card network best practices for stored card-on-file credentials that power merchant-initiated transactions (MIT), we updated our API with a new field. This allows merchants to reference the first customer-initiated transaction in the billing series by sending mitStoredTransactionId. You can find it in our API documentation under Charge or Authorize.

This field is used alongside gateway-specific MIT fields.

Merchants using the gateway BillaPay can now take advantage of FlexPay's highly performant failed payment recovery solution. Billapay is a complete payment gateway inclusive for merchants of every vertical.

See Billapay in the supported gateway list: API docs.

FlexPay has improved the integration into Orbital by Chase Paymentech. Merchants can now send a trace number which can be used to check the status of the transaction if the response is not received due to connectivity issues. Plus, third-party tokens can be accompanied by cardholder information such as address. Finally, sandbox support is now available for testing.

See full details in the documentation here.

Merchants that use the PayRilla payment gateway can now recover failed payments with FlexPay. PayRilla for eCommerce includes interchange rate optimization and advanced developer tools.

Check out our documentation here.

Merchants using Adyen can now recover failed payments on Apple Pay and Google Pay. These payment methods work by saving the customer's credit or debit cards in the virtual wallet and using tokens to send the transaction.

These payment methods are especially important for merchants selling through the native app stores.

See the API documentation here.