Free tool 5 · Who Approved This Payment?

How to answer "who approved this payment?" in one line, without rebuilding your wallet stack, even if your agent signs with a single hot key today.

…and who carries the cost when it's wrong. Two minutes, seven questions. Five ways an agent payment goes wrong, and for each one: what stops it, what you can prove afterwards, and who carries the cost today. Then design the receipt that closes the gaps.

Nothing you enter leaves your browser.

Step 1 · The loss map · about 60 seconds

Seven questions, one tap each. Five ways an agent payment goes wrong, and for each one: what stops it, what you can prove afterwards, and who carries the cost today.

1. Whose money does the agent spend?

2. How does it pay?

3. Where does the spend limit live? (pick all that apply)

Only in the prompt / instructionsIn our agent codeIn our wallet provider's policiesOnchain (spend permission, Safe module, session key)Card issuer controls (spend limit, merchant lock)The seller or facilitator checks itNo limit

4. Can the agent (or someone who hijacks it) change that limit?

YesOnly our team, through a deployOnly the user, by signingDon't know

5. What do you keep after each payment?

Nothing beyond the chainApp logsSigned or hash-chained receipts we holdThe same, plus a copy held by someone else

6. Does each payment carry a reference to the user's request or approval?

NoAn internal ID in our databaseA signed grant or mandate attached to the payment

7. Do your terms say who pays when the agent pays wrong?

Yes, clearlySomewhere, vaguelyNo / don't know

A person approves payments above: NeverYour own threshold for a person to step in.

Already know your gaps? .

Want a second pair of eyes on one real workflow?

This tool checks who approves each payment, where each limit lives and who carries the cost from what you typed. It can't see your code, keys, contracts or production traffic. If the result shows gaps, send me one real workflow. In my free 48-hour integration review I go through it end to end and send you a written report: fit, dependencies, permission risks, acceptance tests and a build or don't-build-yet call.

Answer the seven questions first. The review then takes one payment workflow and writes down who approves what, where each limit really lives, how it can move the wrong money, and the tests that prove it's fixed.

Request the free 48-hour review

Contact: Shilpa Goel, [email protected]

This is an engineering checklist, not a security audit, legal, compliance or investment advice.