Spend7

Payment rails

The rail decides what can be checked. Behavioural signals, caps, amount anomalies, velocity, apply everywhere. Protocol checks only exist where the protocol gives us something to check against.

x402x402

Payment negotiated over HTTP 402: the server quotes what it wants, the client pays and retries the request with a signed payment payload.

  • · The authorized amount against the maxAmountRequired the server actually quoted
  • · The settlement asset and network against the ones the quote named
  • · Whether the pay-to address has ever been paid by this account before
AP2ap2

Agent Payments Protocol: the user's authority travels with the payment as signed mandates, so a merchant can tell what the human actually approved.

  • · Whether a mandate is present and unexpired at the moment of payment
  • · Whether the cart total stays inside the intent mandate's price ceiling
  • · Whether the merchant is inside the mandate's declared scope
Other railother

Any rail Spend7 has no protocol-level view of: a card-on-file charge an agent triggers, an internal ledger transfer, a bank push.

  • · Spend caps, amount anomaly, velocity, first-seen merchant and category risk still apply