◯ Marutap Log in Join the waitlist
◯ how it works

From “order me a pizza”
to a paid receipt.

Every purchase your agent makes runs the same short loop. Here’s each step — and exactly where your real card is not.

  1. 1

    Connect the card you already have

    Sign up and connect your existing card once — securely, through Stripe. Marutap never stores the number itself. Then drop a Marutap token into whatever agent you run.

  2. 2

    Your agent asks Marutap to pay — it never holds your card

    When your agent wants to buy something, it calls Marutap with the amount and merchant instead of holding any card of yours. Marutap turns that into a pending charge.

  3. 3

    A receipt hits your phone. You approve with one tap

    You see the exact amount and merchant, and approve with your passkey — Face ID, Touch ID, or your device PIN. Nothing is paid until you do.

    Set an auto-approve rule for the small, routine stuff and matching purchases skip this step — still capped, still merchant-locked.

  4. 4

    Marutap issues a single-use card scoped to that purchase

    The moment you approve, the agent gets a one-time card locked to the amount and merchant you just saw. It works for that one purchase and nothing else.

    Scoped to amount + merchant Single-use one charge only Revocable anytime
  5. 5

    It settles — and lands in your ledger

    The charge goes through, you get a receipt, and it joins one ledger across every agent you run. Your real card was never exposed to the agent or the merchant.

Recurring payments, without a card on file

Let your agent set up a subscription — Netflix, your gym, whatever — as a locked mandate instead of a card on file. You approve the cap once.

  • ◯Cancel and they’re done. Kill it from your dashboard and the merchant can never charge you again.
  • ◯Price hikes bounce. A charge above your cap is declined until you approve the new amount.
  • ◯Locked to one merchant. Capped per month and usable nowhere else.

You’re always the kill switch

  • ◯Revoke any agent and every credential it could ever touch stops working — instantly.
  • ◯One ledger, one set of rules across every agent, not a silo per app.
  • ◯A hijacked agent can’t overspend — nothing pays until you tap, and what it gets is scoped to exactly what you approved.
Join the waitlist

More on the guarantees behind this: Security & trust · building an agent? For developers