How it works
Intent in. Verified execution out.
You describe what you want. PayAI interprets it, prepares the execution, and waits for your approval — then settles it on Monad with a record you can verify yourself.
How it works
From intent to verified execution
Every action PayAI takes follows the same six stages — whether it is a payment, a trade, or a DeFi interaction.
Describe your intent
Say what you want to accomplish in plain language — a payment, a trade, a schedule. No forms to map your goal onto first.
“Swap 0.1 MON for USDC”
PayAI interprets it
The intent is resolved into structured fields — the action, the assets, the amount, and any constraints you stated.
PayAI prepares the execution
A concrete plan: the route through a supported Monad venue, the quote read live from the chain, and every step the transaction will take.
You review and approve
The full plan is laid out before anything is signed — recipient resolved on-chain, amount checked against your balance, screened before it moves.
Recipient resolved on-chain
Amount and balance checked
Screened before signing
It executes on Monad
One passkey confirmation, or one signature from your connected wallet. What you approved is exactly what is submitted.
The result is verified on-chain
Every execution settles on Monad Mainnet with a transaction hash and a contract event, and the dashboard records what happened.
Ask PayAI
Say what you want. Approve what it prepares.
Ask PayAI turns a sentence into a complete workflow — a payment or a trade. It resolves the recipient or quotes the trade live across Monad DEXs, reads the token off its own contract, checks the amount against your balance, and lays out every field for you to read.
Then it stops. Nothing is signed, sent, or scheduled until you approve it — and what you approve is exactly what you were shown.
Try Ask PayAIPay contributors every Friday.
Prepared workflow
Automation: one execution mode
When an intent repeats on a schedule, the same lifecycle runs on your behalf. You approve the terms once; PayAI executes within them and proves each run on-chain.
One-time setup
Create automationStep 1
Start from a template or from scratch, and set the recipient.
Choose tokenStep 2
MON or any fungible Monad token. Decimals read from the contract.
Choose execution modeStep 3
Wallet Automation keeps funds in your wallet; Reserved Funds sets them aside.
ScheduleStep 4
One-time, daily, weekly, monthly, or a custom interval, in your timezone.
Wallet verificationStep 5
You sign the exact terms once. PayAI can never exceed them.
Repeats on every run
Monad executionStep 6
At each scheduled moment the payment fires on Monad Mainnet.
CompletedStep 7
Settled, recorded, and receipted with a verifiable transaction hash.
Two ways to fund an automation
You choose per automation. Wallet Automation keeps funds in your wallet; Reserved Funds lock them in AutomationVault. Neither mode puts your balance on a PayAI server.
Wallet Automation
Funds stay in your wallet
- You approve a spending allowance once; nothing moves until a run fires.
- Each run pulls only the exact amount due, never more.
- Revoke the approval at any time and the automation simply stops.
- Required for Bulk Payments.
Best when you want to keep custody and flexibility.
Reserved Funds
Execution is guaranteed
- Funds are set aside up front in the AutomationVault contract.
- The reservation is locked to the recipient you chose — it can only pay them.
- A run cannot fail because your balance changed later.
- Refund whatever is unspent, whenever you want.
Best when a payment absolutely must go out on time.
Built for money you cannot afford to lose
Funds never leave your control. Every payment is screened before it sends and approved by you, every run settles on Monad Mainnet with a receipt you can verify, and anything set aside comes back if you cancel.
Your money stays yours
You hold your own funds. PayAI never takes custody, and every payment needs your approval.
Confirmation before execution
Nothing signs itself. A PayAI wallet asks for your passkey on every transaction; a connected wallet asks you to sign. What you approve is what you were shown.
Your wallet, or ours
Create a PayAI wallet from a passkey — no seed phrase, because there is nothing for us to hold — or connect the wallet you already use. Link both to one account.
Every payment is checked
Before anything sends, we make sure it's going to the right place, for the right amount, within your limits.
Cancelled means refunded
Cancel an automation backed by Reserved Funds and what was set aside is released back to you automatically — the same when a schedule finishes its last run.
Arrives in seconds
Payments land almost instantly, any time of day, with a receipt you can always look up.
Nothing to hide
Every payment is recorded permanently, so you can prove it happened whenever you need to.
Something wrong? Report it
Report an issue on any transaction from the dashboard, and the Support Center tracks it — with your history beside it rather than in a separate inbox.
Why PayAI is built on Monad
Automations and AI-triggered payments only feel instant if the chain underneath actually is. Monad's speed and low fees are what make that real, not a future promise.
Fast settlement
Payments and automations confirm in seconds, so a scheduled payout or an AI-triggered send never leaves you waiting.
Low fees
High throughput keeps gas costs low, so frequent and recurring payments stay practical instead of a tax on convenience.
Built for real usage
Wallet Automation and Reserved Funds depend on the same high-volume, repeatable transactions Monad is built to handle.
Public docs, not a private map
A few GET routes are public on purpose. Anything that can move funds stays behind a session in the app. The rest is not a partner API.
Public endpoints
/api/fees
Current platform fee rates.
/api/onchain
Live contract addresses on this deployment.
/api/tokens
Verified Monad token registry.
/api/health
Liveness: network connected or not.
HTTP, documented
The public GET routes and merchant key live in the docs. Session routes that move money are the app backend, not a published SDK.
Verified contracts
PayAIForwarder, PayAITradeExecutor, PaymentExecutor, MerchantRegistry, and AutomationVault are on Monad and linked from the docs.
Idempotent by design
Every execution carries a request id enforced in the app and on-chain, so a retry can never double-pay.
Part of the Monad stack
PayAI plugs into what the ecosystem already uses, so an automation works with the wallet and the name you already have.
Monad Mainnet
Every payment and automation settles on Monad, with sub-second finality and fees low enough for recurring runs.
Nad Name Service
Pay a .nad or .nads name instead of a 42-character address. Resolved on-chain, then re-verified server-side before anything sends.
Any EIP-6963 wallet
MetaMask, Rabby, Backpack, OKX, Coinbase and more are detected automatically — plus WalletConnect for mobile.
Durable scheduling
Automations are indexed and persisted so a due payment survives restarts and fires on time, every time.
Ready to try it?
Connect your wallet and describe your first action in a couple of minutes.
Non-custodial · On-chain execution · Built on Monad