Connect Claude to Stripe — without exposing customer data
Ask your AI about revenue, refunds, and churn — while customer emails, names, and card details are stripped out before the model ever sees them.
Your AI shouldn't need your customers' details to answer about them
Point a generic MCP server at Stripe and every charge object the model reads carries a customer email, a name, and card metadata. That’s your customer list, quietly leaving the building in AI context windows.
Waqi sits between your AI and Stripe as a redaction proxy. The model gets amounts, statuses, and timelines; the identifying details in each response are masked mid-pipeline, logged, and never reach the model provider.
Live in minutes, nothing to host
Create a restricted key
In Stripe, create a restricted key with every permission set to Read. It can never move money, refund, or change anything — the strongest look-don’t-touch guarantee Stripe offers.
Get your member link
Every person on the team gets their own protected MCP URL, so the audit log says who asked for what — not just "someone did".
Paste it into Claude or ChatGPT
Add it as a custom connector and ask real questions. Every response is scanned and redacted before it leaves Waqi.
What gets stripped from Stripe responses
- Customer emails on charges and invoices
- Cardholder names and card number fragments
- Phone numbers in customer records and metadata
- API keys or secrets accidentally stored in descriptions
Detection runs on every response, including inside free-text fields. Every call is written to a per-member audit log, and any listed free-text field can be hidden from the model entirely with one click. How Waqi handles data →
Questions teams ask before connecting Stripe
Can Waqi refund, charge, or move money in Stripe?
No. Waqi connects with a restricted key you create with read-only permissions — Stripe itself enforces that it can never write. Waqi’s own pipeline is read-only on top of that.
What exactly does the AI see?
Amounts, currencies, statuses, dates, and product lines — with identifiers replaced by typed placeholders like [EMAIL:a1b2]. Placeholders are stable per value, so "the same customer keeps failing payments" is still answerable without exposing who they are.
Does this work with ChatGPT as well as Claude?
Yes. Waqi is a standard MCP server, so it works with Claude (Settings → Connectors), ChatGPT (custom connectors in developer mode), and any other MCP-capable client. One link works everywhere.
Where does my Stripe key live?
Encrypted with AES-256-GCM before it’s stored, decrypted only for the moment of your own request, and never visible again to anyone — including your team’s admins.
How fast is setup, honestly?
Creating the restricted key takes about two minutes. Adding your link to Claude is another minute. No servers, nothing to install.
Not ready to buy today? Take the Pilot Pack.
The 14-day pilot checklist, the DPA, and the security model — everything you need to evaluate Waqi properly or make the case to your team.