CatiPay · On-chain payment inspection
The cat checks
before you pay.
- 01Inspect the destination.
- 02Read the token.
- 03Check the allowance.
- 04Prepare the transaction.
- 05Then sign.
No custody. / No private keys. / No blind signatures.
Position
A payment should not begin with a signature.
It should begin with a read.
CatiPay behaves like a careful cat inspecting a payment before it leaves the desk. Every value on the receipt comes from your wallet, an RPC read, a contract call or a dry run. Nothing is invented.
CatiPay reads
- 01RecipientAddress or ENS, resolved and checksummed.
- 02ChainEthereum, Base, Arbitrum, OP Mainnet, Polygon.
- 03Tokenname(), symbol(), decimals(), totalSupply() via multicall.
- 04AmountparseUnits only. No floating point, ever.
- 05Wallet balanceNative and token balance from the RPC.
- 06Allowanceallowance(owner, spender) with honest thresholds.
- 07Gas requirementestimateGas plus current fee market.
- 08Contract statusBytecode present or externally owned account.
- 09Transaction calldataEncoded, decoded and shown before the wallet opens.
The desk
Six instruments.
One reading order.
Every instrument reads live data through viem with RPC fallbacks. Configure your own keys or use the public endpoints.
- 01
Inspect
Address, ENS and token inspector. Bytecode, balances, metadata.
- 02
Compose
Native or ERC-20 payment with calldata, gas, simulation and verdict.
- 03
Allowance
Read allowance(owner, spender). Approve exact amounts or revoke.
- 04
Decode
Raw calldata to function, arguments, token, recipient and amount.
- 05
Transactions
Hash inspector with receipt, confirmations and decoded input.
- 06
Address book
Labels and notes for addresses, saved on this device only.
Primary flow
From connection to receipt, in the order the cat reads it.
- 01Connect wallet
- 02Enter payment
- 03Read destination
- 04Read token
- 05Check balance
- 06Check allowance
- 07Estimate gas
- 08Simulate
- 09Review calldata
- 10Sign in wallet
- 11Wait for receipt
- 12CatiPay receipt
Security model
01
No custody.
CatiPay never holds funds. It prepares a transaction object and hands it to your wallet.
02
No private keys.
Keys, seed phrases and wallet exports are never requested, read or stored. There is no field for them.
03
No blind signatures.
Target, value, method, calldata, gas and a dry run are on the receipt before the wallet opens.
Verdicts are cautious by design. BLOCKED is used only for technically impossible actions such as an invalid address, an insufficient balance or a failed simulation. Anything uncertain is marked CHECK. CatiPay never calls a transaction safe.