No routes appear

Confirm the package is version 0.2 or newer, the route has an @access402.protect(...) decorator, and access402.install(app) runs after route declarations. Verify that ACCESS402_PUBLIC_BASE_URL appears in the installation's authorized URL list and confirm the installation ID and active API key. Start the application, then choose Refresh status in the dashboard.

Configuration fails

An authentication or signature failure is closed by design. Rotate a lost key, confirm the installation belongs to the intended project, and make sure system time is accurate. Do not bypass signature verification.

Route is not protected

Confirm the endpoint has @access402.protect(...) with a valid positive price.
Confirm the synchronized policy appears in the dashboard read-only mirror.
Check the HTTP method and normalized path.
Confirm trusted bypass logic is not accepting the request.
Refresh configuration or restart the process after a prolonged network failure.

Payment fails

Inspect the HTTP status and sanitized Access402 activity detail. Incorrect resource, amount, network, asset, wallet, expired authorization, invalid signature, or exceeded plan allowance are rejected before successful settlement. Repeated idempotency keys return the existing result instead of settling twice.