Frequently asked questions

An intent-based payment application on Monad. You state what the recipient should receive; the app works out which asset you spend, the route, and the transaction, and you approve it in your own wallet.

No. It is a payment app. Routing is machinery underneath. The interface says “Pay”, not “Swap”.

Any compatible token on Monad can be discovered and used when your balance and a real execution path support the operation. A discovered token with no liquidity cannot be converted, though a direct transfer may still work. Discovery is not a claim of safety, liquidity or tradability.

Yes. Gas is always paid in native MON through your own injected wallet. There is no sponsored, ERC-20 or account-abstracted gas path. If you hold no MON, the app tells you before you start.

No. Intent Pay imposes no minimum transfer amount, and the Monad network does not either. Any amount that is representable in the token's decimals can be sent. Two real constraints can still stop a very small payment: your wallet must hold enough MON to pay the network fee for every step, and if the payment needs a conversion, a route with enough liquidity must exist. Neither is a minimum amount — the app tells you which one applies. AUSD is a small-value asset, not a payment minimum.

The usual cause is the network fee, not the amount. A swap payment is several on-chain transactions (approve, swap, and sometimes unwrap and deliver), and each charges its own fee in MON. The app adds them up and checks your MON balance covers the total before you confirm. If it does not, it says so explicitly and does not submit anything. A token-only payment within a single transaction needs less.

No. It is not a gasless product, and it does not claim to be.

No service fee is currently charged. Service-fee collection is planned and, if added, would be displayed before you authorize a payment.

No. Intent Pay is Monad-only. It is not a bridge and does not claim cross-chain delivery.

After the transaction confirms, the app verifies the recipient's on-chain transfer from the receipt against the minimum the transaction enforced. Success is only shown after that verification. An unprovable delivery is shown as unverified, never as success.

No. A deterministic, offline parser interprets the request, and deterministic validation plus the signing guard govern execution. The AI can only fill gaps and can never supply a price, route, address or transaction.

The app selects the best available route among the quotes it evaluated, weighing output, network cost, price impact and execution feasibility. It does not claim to find the globally optimal route, and it never silently chooses a route that materially differs from the one you reviewed.

Through the transaction itself: every swap carries an on-chain minimum output (or maximum input), a route above the price-impact ceiling is blocked before signing, and a stale quote is refused and the calldata rebuilt. The app reports MEV-protected submission as unavailable on Monad rather than showing a cosmetic badge.

No. The app never holds your keys, never signs on your behalf, and cannot bypass wallet authorization. It prepares a transaction; your wallet approves it.

A clearly labelled mode that uses deterministic sample data so the flow can be explored without a wallet. It never produces a transaction hash and never claims a real transaction.

Yes. Intent Pay has successfully processed a real-wallet payment on Monad mainnet: the transaction was confirmed on-chain and the intended recipient received the payment. This demonstrates the ability to execute a real payment using its on-chain payment flow. Availability for a given payment still depends on the connected wallet, the token, and an executable route.

See the /docs/litepaper. It describes the implementation as built, including its current limits.