Intent Pay
An intent-based payment layer for Monad. You state what the recipient should receive; Intent Pay determines which asset you spend, the route, and the transaction — then you approve it in your own wallet.
The complete design: problem, approach, architecture, execution, limits and roadmap.
The payment journey from intent to verified onchain status.
The layered system: intent, routing, construction, execution, verification.
The signing guard, on-chain output bounds and honest capability reporting.
What is built and verified, what is in progress, and what is planned.
Direct answers about tokens, gas, fees, safety and network support.
Repository layout, commands, routes and configuration.
The idea in one paragraph
A payment is a statement about an outcome: this recipient receives this token, worth this amount. Everything else — which of your balances to spend, how much of it, the conversion route, the slippage bound, the calldata, the receipt check — is machinery the user should not have to reason about. Intent Pay keeps the user's mental model a payment rather than a trade, while being completely honest about what that machinery can and cannot currently do on Monad.
At a glance
- Network: Monad mainnet, chain id 143.
- Simplicity on top: a single-page, Web2-style payment composer plus an optional natural-language intent bar.
- Routing underneath: live Uniswap V3 routing on Monad, exact-output and exact-input, every fee tier quoted.
- Discovery: tokens resolve by symbol, name or contract address from real Monad chain state — not a fixed allow-list.
- Gas: always paid in native MON through your own injected wallet. There is no sponsored or ERC-20 gas path.
- Execution: one prepared transaction, protected by an on-chain minimum output and a signing guard that rebuilds it from fresh data.