How it works

From request to receipt.

Your agent asks over MCP. Reinpay checks your rules, simulates the payment on Robinhood Chain mainnet, and writes a receipt either way.

Your agent asks over MCP Your rules then a mainnet simulation Payee on your list WAITING FOR YOU
payee · max · budget · repeat · approval · simulation0 sent · 0 waiting · 0 blocked
How it decides

Every request runs the same checks, in the same order.

The first check that fails decides, and the receipt names it. Hard limits block outright. Softer ones hand the payment to you. Only a payment that passes all of them goes on to the simulation.

  1. The payee is on your listSwitched on, and allowed to receive that token. No fuzzy matching on names.else blocked
  2. The amount fits the max per paymentYour max for the token, and the payee's own max if you set one.else blocked
  3. Today's budget has roomCounting what was sent today and what is still waiting for you. Per token, per local calendar day.else blocked
  4. It is not a repeatSame payee, token and amount within 10 minutes looks like a loop.else asks you
  5. It is under your approval lineAbove the line, the payment waits for reinpay approve.else asks you
  6. The simulation matcheseth_simulateV1 on Robinhood Chain mainnet must show exactly one transfer leaving the wallet: that amount, that token, to that payee. The wallet must also cover the network fee.else blocked
After the checks

What happens to each request.

BlockedNothing is signed. The receipt names the rule and why, so the agent can tell you or try something else.
Waiting for youAbove the approval line or a repeat. Run reinpay approve RP-… or reinpay reject RP-….
ReadyInside every rule. It still waits for you unless you turned on autosend and unlocked the wallet.
SentSimulated on mainnet first: exactly one transfer out, that amount of that token, to that payee. Then signed and sent.

Try the same checks in the playground.