Recurring charges - incorrectly coded for Authorize.net

There is an issue in Keap’s ecommerce system that needs to be addressed. It is growing in urgency because Mastercard has stated they will start issuing fines to non-compliant merchants in November 2024.

Please see this article: Knowledge Article Detail Page - Anet | Authorize.net Support Center

In particular, note this quoted section:

What do I need to do to be compliant?

For those merchants who are storing their customer payment data outside of their Authorize.net account, please see our API Reference and Developer Guides for more information on how you can update your integration for COF mandate compliance. Please work with your 3rd party service provider and/or developer to direct them to this documentation as needed.

Keap is storing our customer payment info and interacting with Authorize.net through their API . That means Keap must make changes in your ecommerce system code to be compatible with this mandate.

Many Keap customers will receive monetary damages from Mastercard if this issue is not addressed soon.

Please ensure a knowledgeable ecommerce developer in Keap investigates this quickly.