Connection fails
Confirm the installation ID, use an active installation key, and verify that the WordPress site origin appears in the installation's authorized URL list. Rotate the key if its plaintext value was lost; Access402 does not store recoverable key plaintext.
Rules do not synchronize
Re-test the saved connection, then save the rule again. Payments fail closed when Access402 cannot confirm the authoritative server-side rule. Check WordPress debug logging and Access402 activity without logging the complete API key or signed payment payload.
Settlement is unavailable
Open the activity detail and confirm the recorded mode, network, and failure stage. A 503 verification error can indicate facilitator authentication, network availability, or settlement service failure. Check wallet activity before retrying an uncertain transaction.
A protected URL is public
- Confirm the rule is enabled.
- Test repeated-slash and canonical URL variants.
- For REST routes, confirm the exact namespace and route.
- For media, run the routing check and inspect CDN or static-server behavior.
- Test while logged out or with a WordPress role that is not configured to bypass payment.