Ask PayAI

A request that is missing something — an amount, a token, who it's for — gets one short question back. PayAI never guesses an amount or a recipient.

You don't have to send one message per payment. Write everything you want done in one request and PayAI builds a single plan with every action in the order you wrote it.

Ways to write it

“Send it” means exactly what the swap returned — not an estimate and not your whole balance. The amount is read from the confirmed swap before the payment is built. “Each” is written out per recipient, so “20 USDC each to three people” is three payments of 20 USDC, shown that way in the review.

How many? A plan can hold up to 500 actions. Long requests — a payroll list pasted in one message, for example — are planned the same way; the review shows a progress count and a scrolling list instead of a card the length of the plan.

The review

Before anything runs you see every action, numbered in the order it will run: what moves, how much, and to whom — with the full address each .nad name or payee resolved to, pinned for this plan. One action reads like a payment confirmation; several read as a numbered list. Cancel or edit at this point and nothing has been sent.

One approval covers the whole plan. With a PayAI Wallet, tapping Approve opens one passkey prompt, and every action in the plan runs on it. You are not asked again for each step.

• The approval signs only that plan's transactions — never anything else in PayAI, which still asks for your passkey every time.
• It is capped to the plan's own number of transactions (each action plus any token approval it needs) and expires after 10 minutes.
• It is wiped the moment the plan finishes, fails or is cancelled.
• Cancelling the passkey prompt approves nothing and sends nothing.

Quotes don't stop you either: a clean, low-risk quote goes straight on. A quote that carries a warning — high price impact, an amount that changed — still stops and is shown to you to accept or decline before anything is signed. Swaps stay protected by the slippage limit shown in the review, which the transaction enforces on-chain.

1. In order. Actions run in the order you wrote them. Each one is quoted, built, signed and confirmed on Monad before the next one starts.
2. Checked before signing. Every transaction is built by PayAI for the plan you approved and checked against it — the contract it calls, the amounts, the recipient, the network. A transaction that doesn't match is refused before your wallet sees it.
3. Confirmed, not assumed. A step counts as done only when its transaction is confirmed on-chain. The receipt shows the real amounts, fees and transaction hash.
4. A failure stops the rest. If a step fails, the steps after it don't start. Steps that already completed stay completed — nothing is reversed or repeated.
5. Pick up where it stopped. When it is safe, the plan offers Continue, which picks up at the step that didn't finish. It is never offered while a transaction may still be in flight, so nothing is sent twice.

Attach a picture instead of typing: a wallet's QR code, a payment request QR, or (where enabled) an invoice or a screenshot of payment instructions. PayAI reads the payment out of it, turns it into an ordinary request and shows it to you — the image is never an approval, and nothing runs until you review and approve the plan.

Full details — what can be read, how a caption combines with the image, and the safety rules — are on Visual intent.

Some on-chain actions run through the PayAI SDK, a layer that only lets each action call the contract it was reviewed for:

These are matched by fixed rules — the language model never chooses a protocol, a contract or an amount. How each one is checked, its fees and limits: PayAI SDK.

PayAI's own engine reads every request first. Clearly written sends, swaps and multi-action plans — including “each” and “then” — are turned into a plan by PayAI's deterministic grammar, and balances, history, token lookups and facts about PayAI are answered the same way. None of that leaves PayAI.

Open-ended wording uses a language model. When a request isn't in a form the engine can read on its own — “twenty bucks of USDC”, “sell about a third of my MON”, most buy/sell and scheduling requests — the text is sent to a language model from Anthropic to work out the action, amount, token and recipient. Reading an invoice image works the same way. The model only fills in those fields: it can't approve, sign or pick a contract, and everything it returns goes through the same checks and your review. If the model is unavailable, the engine answers on its own or asks you to rephrase.

• Payments in a plan are MON or USDC. Swaps in a plan are MON ⇄ USDC. Other tokens are traded on their own — see Trading.
• “Send it” works after a swap to USDC. MON received from a swap can't be passed to the next step yet.
• Amounts must be exact. “Half of it”, “the rest” or “all” between steps aren't supported yet.
• A scheduled or recurring payment goes in its own message; it can't be combined with other actions yet.
• Up to 500 actions per plan.
• Staking, bridging and other DeFi protocols aren't available yet — PayAI says so rather than guessing.

More on the signing model: Security.