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.

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.

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.

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.