Repository navigation
fix(mpp): enforce configured spend limits - #14
Open
mercadosclaro-eng wants to merge 3 commits into
Open
mercadosclaro-eng wants to merge 3 commits into
mercadosclaro-eng wants to merge 3 commits into
Conversation
Apply the owner's daily and per-transaction limits to explicit MPP and automatic MPP fallback paths.
Validate each MPP challenge against the configured owner limits before creating a credential.
Add a shared limit check with tests for per-transaction, daily remaining, and allowed payments.
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
1 participant
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.
Configured daily and per-transaction spend limits currently protect x402 payments, but explicit MPP payments and automatic x402-to-MPP fallback can create credentials without checking those owner limits.
This change adds one shared pre-credential limit check and wires it into the MPP HTTP, serve, and MCP paths. It uses the existing payment history so both protocols follow the same configured limits.
Validation: