Unverified50% confidenceDecision RuleExact time
The anti-loop guard throws PaymentNotAcceptedError when a retry request carrying a payment-signature returns 402 again, and never pays twice for the same request.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/15/2026
First Seen
Valid until: 1/13/2027
Sources
Related Entities
Related Claims
UnverifiedIn the x402 flow, when the server returns a 402 response, the response body contains payment requirement metadata such as amount, currency, and payee address; the client parses this and automatically completes the payment, then resends the request with a payment proof.65% similarUnverifiedSome users have reported that the credit did not arrive promptly, and logging out and back in often triggers it to be credited.61% similarUnverifiedRetries without idempotency protection lead to problems such as duplicate orders, duplicate emails sent, and duplicate charges.60% similarUnverifiedOn a cache miss, if the tenant's sliding window token budget has been exceeded, the proxy directly returns HTTP 429 without touching the upstream.59% similarUnverifiedMerely cancelling the current response is not enough; callbacks already queued may still be delivering tokens, and the application can assign a unique identifier to each response to reject output from responses that have been superseded.58% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1040797API
curl https://kongchang.com/api/v1/knowledge/claims/1040797MCP
get_claim(id=1040797)