Skip to content

See it work

Six minutes, and one of them
is a payment being refused.

The interesting part of this product is what it will not do. Here is the order to look at it in, whether or not you sign in.

The walkthrough

Six things to look at, in order.

Each one takes under a minute. The figures below are the ones on screen.

  1. Sign in with Google

    An account and a wallet are created in the same step. There is no seed phrase, no extension, and no network to choose.

    What it showsSomebody who has never held a wallet can reach a working account.

  2. Read a spender's rules

    Open Spenders. Each spender’s allowance, cap per payment, payments per period and approved services are written in dollars and service names. When you create a team, you are added as its first spender at $1,000 a month and up to $250 a payment.

    What it showsThe rules are legible before anything is spent, not buried in a setting.

  3. Ask the assistant to pay

    Type one line to Nini. Code reads the amount, the assistant picks a service from the registered list, and you confirm the draft. It never sees an address, and its output has no field an address could go in.

    What it showsA hallucinated recipient is unrepresentable rather than filtered.

  4. Watch a payment over its cap get refused

    Ask to pay $420 when your cap for one payment is $250. Before anything is sent, the screen says the payment is held by your rules, in amber, and that no money has left the account. The arithmetic is shown so the refusal can be checked rather than trusted.

    What it showsA refusal is a first-class outcome, not an error state.

  5. Name a service the account does not know

    Ask it to pay something that is not on the list. The name is looked up, nothing is found, and there is no address to pay.

    What it showsThe same refusal happens on chain: an unregistered id reverts rather than resolving to the zero address.

  6. Send the refusal to the owner

    Press Ask for approval, and the refused payment becomes a request on the owner’s Approvals screen, carrying the rule that caught it and the amount it went over by. The owner approves or declines it there.

    What it showsBlocking and asking are separate steps, because a call that refuses by reverting erases its own record.

    Not yetNothing tells the owner by email or push yet: a request waits on Approvals until they open it. An agent’s refused payment is not filed as a request; it stops there.