WooCommerce compatibility
Treat login security as an account-flow decision.
Awthy keeps WooCommerce compatibility evidence explicit so customer-account protection does not quietly become checkout risk.
Flows Awthy tracks before stronger claims
| WooCommerce flow | Compatibility boundary |
|---|---|
| My Account login | WooCommerce login, dashboard, lost-password, and account-security endpoint behavior need fixture-backed browser evidence. |
| Checkout boundaries | Checkout login prompts, order-pay, deposit links, and payment-link extensions are payment-sensitive and are not step-up targets by default. |
| Saved payment methods | Payment-method add, delete, and default actions need gateway fixtures and hook proof before any blocking behavior is considered. |
Custom-login boundary
Stores with custom login builders, custom checkout flows, membership portals, deposits, subscriptions, or payment-link extensions should test those routes directly before publishing stricter customer requirements.
Awthy can document the expected account-security path, but it does not claim universal compatibility with every custom WooCommerce login or payment extension.
Help for this page
Awthy keeps WooCommerce compatibility evidence explicit so customer-account protection does not quietly become checkout risk.
Why this matters
WooCommerce login, dashboard, lost-password, and account-security endpoint behavior need fixture-backed browser evidence.