docs(x402): clarify the payment signature is reusable until balance runs out#2618
Open
MQ37 wants to merge 1 commit into
Open
docs(x402): clarify the payment signature is reusable until balance runs out#2618MQ37 wants to merge 1 commit into
MQ37 wants to merge 1 commit into
Conversation
Contributor
|
✅ Preview for this PR (commit |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
The x402 page doesn't state that the signed
PAYMENT-SIGNATUREcan be reused across calls. A reader following the direct-API steps may assume each call needs a fresh signature and a new on-chain settlement.Solution
:::notein the direct-API section: the samePAYMENT-SIGNATUREstays valid while the prepaid balance lasts; resend it on every call with no re-signing or new settlement, and only sign again when the API returns402(balance exhausted) — the manual equivalent of whatmcpcdoes automatically on the MCP path.