When a payment fails, the reason should be specific enough to fix. Our facilitator never answers with a bare "invalid". Here are the codes you will see most.
MALFORMED_PAYLOAD: the payment header is not valid x402 JSON.MISSING_SIGNATURE / SIGNATURE_MISMATCH: no signature, or it does not recover to the payer. Re-sign with the right key and the token's EIP-712 domain.MALFORMED_AMOUNT: amounts must be integers in base units.AUTHORIZATION_EXPIRED: validBefore has passed. Re-sign with a later time.AUTHORIZATION_EXPIRES_TOO_SOON: inside the 6-second margin. Re-sign further ahead.AUTHORIZATION_NOT_YET_VALID: validAfter is in the future.AUTHORIZATION_ALREADY_USED: the nonce was spent. Generate a fresh one.INSUFFICIENT_FUNDS: fund the wallet, then retry the same authorization.INSUFFICIENT_AMOUNT: signed for less than the price.WRONG_PAYEE, UNSUPPORTED_NETWORK, UNSUPPORTED_ASSET, UNSUPPORTED_SCHEME: the payment does not match the 402.BUDGET_EXCEEDED, AUTHORITY_REVOKED, AUTHORITY_EXPIRED, SPEND_CONFIRMATION_REQUIRED: the wallet owner's spend rules said no.CHAIN_READ_FAILED and SVM_VERIFY_UNREACHABLE mean we could not read the chain. The authorization is untouched; retry shortly. The full machine-readable list with fault and retry flags is at /facilitator/reasons.
The signature does not recover to the from address, usually because the EIP-712 domain (token name, version, chain ID, contract) is wrong.
No. A refused payment never settles, so no USDC moves.
Timing and chain-read errors are retryable; /facilitator/reasons marks each code retryable or not.