A requirement as this SDK reads it: the fields FeeTerms is
narrowed from, plus whatever else the scheme attached, carried through
untouched because the backend matches a payment by deep-equalling what it
quoted.
Deliberately not PaymentRequirements from @x402/core. These named fields
are the ones this SDK actually depends on, so they can only move in an x402
major that breaks us anyway — stating them here changes nothing about that.
What it does change is everything else: an x402 release that adds, renames
or retypes a field we never read stays their business, instead of rippling
into our published types and the types of everyone who depends on us.
A requirement as this SDK reads it: the fields FeeTerms is narrowed from, plus whatever else the scheme attached, carried through untouched because the backend matches a payment by deep-equalling what it quoted.
Deliberately not
PaymentRequirementsfrom@x402/core. These named fields are the ones this SDK actually depends on, so they can only move in an x402 major that breaks us anyway — stating them here changes nothing about that. What it does change is everything else: an x402 release that adds, renames or retypes a field we never read stays their business, instead of rippling into our published types and the types of everyone who depends on us.