Developers

Contracts.

Settlement is the contracts on Monad, not this website. The table is read from the running deployment. PayAIForwarder and PayAITradeExecutor are what your wallet actually pays and trades through. PaymentExecutor is the automation path.

Last updated 20 September 2026

01In production now

Interactive payments go through PayAIForwarder. Interactive trades go through PayAITradeExecutor. PaymentExecutor, AutomationVault, and MerchantRegistry settle automations and the on-chain record. Addresses below are live on this deployment, not a screenshot.

Loading live contract addresses…

Machine-readable: GET /api/onchain and GET /api/automation-config.

02What each live contract does

PayAIForwarder is the interactive-payment path: your wallet pays the forwarder, the forwarder pays the recipient. You sign. The automation agent is not in this path.

PayAITradeExecutor executes interactive trades through allowlisted venues. The model does not pick an arbitrary target.

PaymentExecutor settles automated payments and writes the record (recipient, amount, request id). It enforces replay protection and the agent per-transaction and daily caps. It is not the contract your wallet sends an interactive payment to.

AutomationVault holds a Reserved Funds deposit for one automation. It can pay the committed recipient or refund the depositor — nowhere else.

MerchantRegistry is the payee directory the executor can check against.

03Deployed, not in the app

These exist on Monad. They are not what the live product routes through today. Listed so an explorer search for “PayAI” is not a mystery.

ContractAddressStatus
PayAITradeExecutorV20x920409bed646fFA094b9851867435a74B55Ca40dDeployed and verified. Flag off — Uniswap/Kuru still use V1; Nad.Fun is still direct.
SplitSettlement0xaC98a844E0F9688EA9758Db05c134b8B4BCeAf6FDeployed. SDK action exists. Not a dashboard flow yet.
PayAIForwarder V10x4ce7B3036595eDA699Aebeb47b34fd4bc4F80709Superseded by Forwarder V2. Do not send to this.
PaymentExecutor V10xf723BE809A99A1c29e0205a542aa2aEF80B508AFSuperseded by Executor V2. Existing automations pinned to it still settle here.
AutomationVault V10x87D42314d1BAf2386fB9ff3dF398b543bc64cA47Superseded by Vault V2. Same pin rule as Executor V1.

04Source