COUNTERFOIL · STORE SETTINGS

Your store's rules.

The rules Counterfoil applies before HOMI's money moves, and how a real store plugs it in. Change them here to see what each one does. Your changes stay in this browser and only drive the What if test below; the shared store keeps HOMI's defaults so every visitor sees the same results.

1 · The rules

Two numbers the store chooses, and four rules it could switch off. Everything else stays on, whatever you choose.

USD
Refunds above it wait for a person, even when everything else checks out.
days
Refunds on older orders wait for a person.

Always on: who owns the order · what data a sender may read · the agent's tool list · catalog price × quantity · the store's currency · repeated or unknown refunds · the refund ledger at the moment of payment.

2 · What if

Pick a request and send its call through the gate twice: with HOMI's defaults and with your rules. No model and no money: the store's records and the gate only.

3 · Who decides held calls

Who
The store manager
Approval
Single use, expires after 30 minutes, bound to the exact call the manager saw; every check runs again before the money moves.
Where
The review step in the store, the evidence review desk, or the approval desk the MCP server opens for Claude Desktop.

4 · Connect

Payment rail
…
Webhooks
…
PayPal REST
Needs a PayPal account. PayPal accounts can't be opened from Türkiye; the gated PayPal REST rail behind the Agent Toolkit's create_refund is ready and tested with a faked HTTP layer.
Your AI agent
Any MCP client (Claude Desktop, Cursor, Claude Code) calls the Agent Toolkit's create_refund(capture_id, amount) through Counterfoil. Add this entry to the client's config; the keys stay in your .env:
{
  "mcpServers": {
    "counterfoil": {
      "command": "/path/to/counterfoil/.venv/bin/python",
      "args": ["/path/to/counterfoil/scripts/counterfoil_mcp.py", "serve",
               "--scenario", "P6-01", "--rail", "braintree"]
    }
  }
}

5 · Your records

Counterfoil decides from the store's own records, never from the customer's e-mail.

In this demo
…
In a real store
Orders and their payments from your order system, return requests from your returns tool, and the sale's line items from Braintree. The gate reads them; it never edits them.