Security

The agent can ask. Only you can say yes.

Reinpay splits the wallet in two: what your agent can do over MCP, and what only you can do in your own terminal.

Who can do what

The agent can ask. Only you can say yes.

The commands that approve payments, change rules or add payees refuse to run without a real terminal, so an agent driving a shell cannot reach them either.

Your agent, over MCP

  • Read the wallet's balances and today's budget left
  • Read the rules and the payee list
  • Ask for a payment, with a memo
  • Read its receipts

You, in your terminal

  • Approve or reject what is waiting
  • Set budgets, max per payment and the approval line
  • Add, remove or switch off payees
  • Turn on sending without asking, for payments inside every rule
Where things are kept

The key stays on your computer.

Everything lives in ~/.reinpay, readable by you only.

keystore.jsonThe key, encrypted with scrypt and AES-256-GCM under your passphrase.
passphrasePresent only while unlocked, and removed on its own when the unlock runs out (12 hours unless you choose). reinpay lock removes it now.
config.jsonYour rules and payees, sealed with your wallet key. If it is changed any other way, nothing is signed until you check it and run reinpay seal.
receipts.jsonEvery request and what happened to it, written atomically.
What Reinpay never does

Short list, on purpose.

Sends your key anywhereThe only network traffic is to the Robinhood Chain RPC.
Lets the agent approveApprove, rules and payees refuse to run without an interactive terminal.
Pays someone off the listNo fuzzy matching on names. Off the list means blocked.
Pays a token contractAn address that answers like a token is refused as a payee, because tokens sent there are usually stuck for good.
Signs a payment it did not simulateApprove rebuilds the payment from your payee list, simulates it, and signs exactly that transaction. The simulation must show one transfer out, to the payee.
Keeps paying when something looks wrongFive blocked requests in ten minutes and the wallet freezes itself, then tells you. reinpay freeze stops everything by hand, and your agent can pull the brake too.
Adds a lookalike payee quietlyA new address that starts and ends like a payee you already have, or like your own wallet, is refused until you type it again in full. That is how address poisoning scams work.
Signs with rules you did not sealBefore anything is signed, the seal on your rules and payees is checked against your wallet key.
Writes a receipt every timeBlocked, waiting or sent, each request has an id and a reason. reinpay verify checks a sent one against the chain.
Signed statementsreinpay statement signs what your agent spent with your wallet key. Anyone can check it against the chain with reinpay statement check.
Signed webhooksEvery webhook notification carries an HMAC signature and a timestamp, so your server can refuse forged or replayed ones.
Open sourceMIT licence. Read every line on GitHub.
Limits of this version

What it cannot check.

DeliveryThe simulation checks what leaves the wallet. It cannot check that a payee delivers what you paid for.
Your computer itselfWhile the wallet is unlocked, a program running as you could read the passphrase. Unlock for short spans, like reinpay unlock --for=30m, and lock when you are done.
Tokens you add are your callReinpay checks that a token is real and verified on Sourcify. It cannot tell you whether it is worth anything.

Set a budget, add a payee, and let your agent ask.