HTTP statuses
| Status | Meaning |
|---|---|
200–299 | The resource or adapter operation succeeded. |
400 | The request or policy is invalid. |
401 | Installation or user authentication failed. |
402 | Payment is required; inspect the x402 challenge. |
403 | The authenticated identity is not allowed to perform the operation. |
404 | The installation, route, policy, or endpoint was not found. |
409 | The operation conflicts with current state or an idempotency record. |
429 | An account, platform, or rate limit was reached. |
503 | Verification or settlement could not be confirmed. The system failed closed. |
Payment validation errors
Access402 rejects incorrect resource URLs, amounts, networks, USDC assets, receiving wallets, invalid signatures, expired authorizations, disabled rules, unknown installations, and exceeded plan limits.
When final settlement status is uncertain, check wallet and Access402 activity before retrying with a new payment authorization.
Safe logging
Log request IDs, installation IDs, sanitized stage and code, resource identity, mode, and transaction hash when available. Never log installation API keys, CDP credentials, private keys, full authorization payloads, or bearer tokens.