Questions, answered.

A payment layer that lets your AI agent buy things with a single-use card you approve — using the card you already have, without ever handing the agent your real number.

No. You connect the card you already have. There’s no new credit line, no new wallet, and no balance to top up. See the comparison.

Any MCP-capable runtime — Claude or otherwise. Marutap is yours, not tied to a single app. Builders can start on the developers page.

No. You approve purchases from a web page on your phone, confirmed with a passkey.

Never. On approval it receives a single-use card scoped to that one purchase — not your real number. More on the security page.

It can only ask to pay. Nothing moves until you tap approve, and what it gets is scoped to exactly what you approved — so it can’t quietly overspend.

Yes. Purchases can be reversed through the merchant; agents can record the order reference so a refund routes correctly. See our refund policy.

Purchases are handled in the currency the agent requests (USD today); the single-use card is issued to match. We’re expanding coverage over time.

By default, yes — that’s the point. You can set auto-approve rules for the small, routine stuff (e.g. under a cap at an allowlisted merchant), and everything else still waits for your tap.

An agent sets one up as a capped, merchant-locked mandate — never a card on file. You approve the cap once; a price hike above it bounces until you approve the new amount.

Kill it from your dashboard and the merchant can never charge you again — no dark-pattern cancel flow can stop you.

The core product is free, with no per-transaction fee. A Pro tier with richer controls is coming later. See pricing.

No passwords. Accounts are passkey-only, so there’s nothing to phish or reuse. If you lose your device, you recover through an emailed link.

Your spending — amounts, merchants, approvals — so you get one ledger and one set of rules. Your card number is vaulted by Stripe, not stored by us. Details in our privacy policy.