← Back to Home
Partner brief

Agent permissions for L402 and x402 payments.

SatGate signs a receipt when it refuses an agent over a budget, a missing payment or a permission, and when an agent spends from a budget in Control. A partner can check it against SatGate's published keys. Who handed which token to whom is in the owner's SatGate account.

Payment methods keep changing. SatGate’s permissions and receipts work with x402 and L402 today. AgentCore Payments and Pay.sh are planned.

See agent permissions and receipts See how rules and receipts work
Partner questions SatGate answers
Were permissions passed down to this agent before the transaction?
Which route or tool was it, and how much budget was left?
Did the decision happen before value moved or an upstream action executed?
Can a partner, customer, auditor, or fraud team verify the artifact without trusting a dashboard screenshot?

Partner fit

SatGate is useful when a payment method does not want to become the whole governance stack.

A single payment method sees the transaction. Enterprises need proof across tools, APIs, delegations, budgets, denials, and retries. SatGate keeps who handed which token to whom in the owner's account, and gives partners signed receipts they can check.

Payment methods

x402, L402, Stripe, AgentCore Payments, Pay.sh, card, wallet, and ledger teams that need proof around autonomous-agent payment attempts.

API platforms

Marketplaces and API providers that want scoped agent acceptance without inheriting every identity, delegation, or dispute question.

Agent platforms

Runtimes, MCP gateways, and orchestration layers that need one permissions contract across payment methods and unpaid APIs.

Rules and Receipts

The handoff is simple: policy in, receipt out.

1

Permission

The principal or platform passes down a bounded capability: agent, tenant, route/tool, budget, expiry, policy version, and delegation depth.

2

Decision

SatGate enforces policy before the request goes through to the upstream API, MCP tool, or payment method.

3

Receipt

SatGate signs a receipt when it refuses an agent over a budget, a missing payment or a tool permission, and when an agent spends from a budget in Control.

4

Signed receipt

Each receipt is in a verifiable Evidence Pack, checked against the issuer JWKS by the open verifier.

Public proof

Partners should not have to trust a screenshot.

A signed receipt (Evidence Pack) can be checked outside SatGate. Anyone can download it and check the signature with the open-source verifier and SatGate's published keys.

Open verifier See how rules and receipts work
Partner artifacts
Public verifierhttps://github.com/SatGate-io/satgate/tree/main/toolsLive signed receipt (Evidence Pack)https://api.satgate.io/v1/evidence/evid_GrXvKUgtdqNbuQ5lZzqRMpZrOoU2VAnEReceipt schemahttps://satgate.io/.well-known/satgate-receipt.schema.json

Build the payment method. Let SatGate carry agent permissions and evidence across it.

The partner conversation starts with receipts: what the payment method sees, what SatGate proves, and what the ecosystem can verify later.

Talk to SatGate Developer building blocks