Hi @cam5atl,
However, now a plugin I use with WooCommerce conflicts and needs to have the enable compatibility mode to ensure smooth payment processing with HPOS.
The Legacy REST API plugin is itself incompatible with HPOS (High-Performance Order Storage), so perhaps that is the reason you are seeing a warning.
This was already true, even before it was extracted into a stanadalone plugin: the Legacy REST API has never been compatible with HPOS (it is after all legacy code, deprecated now for many years).
If I disable Legacy now, will that cause me problems with payments and subscriptions being processed?
Most up-to-date payment integrations, and plugins like Subscriptions, do not depend on the Legacy REST API.
Additionally, if you are using the latest version of WooCommerce, it will try to warn you if it detects a service using the Legacy REST API: please see this comment for an example of what that looks like.
If you have not being seeing any notices like that (and if you are not using any legacy web hooks, or have not issued any API keys—see this post for a summary of those things) then it is probably safe to simply disable the Legacy API.
I realize there is a lot of information to unpack here … so please don’t hesitate to follow-up if you have further questions.
