Geniepay
Get in touch

[ Agentic payment authorization ]

Your agent can spend.
Not go on a rogue shopping spree.

Agents pay for things now — per request, in stablecoins, without a human in the loop. Geniepay is the gate before the signature: it checks where the amount and the recipient came from, whether the spend fits the task, and whether the budget allows it. Then it lets the wallet sign, or refuses and records why.

Built on trust.band. Works with x402, AP2 and any wallet that exposes a signing step.

Get in touch

Provenance-gated spending

A recipient address that arrived inside a web page or a tool result is not the same as one you typed. Geniepay knows the difference, and a policy can refuse the first while allowing the second — even when the two are byte-identical.

Task-scoped spending authority

Instead of a burner wallet, a burner capability: spending authority minted for one task, capped, and revoked the moment the task ends. No separate wallet, no residual balance, nothing to trace back.

Budgets that stop, and a record you can show

Per-session, per-agent and per-client spend caps that halt rather than warn. Every authorization and refusal lands in a hash-chained log that names the rule that decided and where each value came from.

How it works

One adapter, at the signing step.

Geniepay is an x402 adapter. It sits between the agent's payment request and the wallet's signature, the one step any wallet that signs already exposes. That is why it works with any wallet and any agent framework, and why it never holds funds.

Download it, connect it to the signing step, done. Free to use.

An agent sends a payment request; Geniepay checks it at the signing step; if allowed the wallet signs and the rail settles, if refused the decision is recorded. Rules come from trust.band.Your agentany frameworkpayment requestamount · recipient · taskGeniepayx402 adapter at the signing stepwhere the amount and recipient came fromwhether the spend fits the taskwhether the budget allows itallowedYour walletsignsx402AP2, any railrefusedrecorded: rule, and whytrust.band: your rules

Where it sits

The wallet holds the money. Geniepay holds the rules.

Payments are the solved part. The unsolved part is trust: proving who an agent acts for, what it may spend, and what it actually did. Geniepay is that half. It plugs into whichever wallet or rail you already use, and it never holds funds.

The gate is trust.band, measured on the AgentDojo banking suite at 0 of 144 attacks succeeding. Next: a Geniepay adapter for x402 that gates the signing step with provenance, budgets and a tool lockfile.

trust.band

The trust layer for agent commerce.

trust.band enforces what an agent may do. Geniepay applies that to money: which recipients, how much, for which task, with a record of every authorization and refusal. If you are building on x402 or AP2, we would like to hear from you.

Get in touch