How to connect an AI-built app to Stripe

Short answer: Add your Stripe key to Croft once as a connector. Your app then calls Stripe through Croft, which attaches the key on the way out — so the key never appears in the app’s code, and the app never holds it.

The wrong way to do this is to let the AI paste your Stripe secret key into the app. That’s how keys leak. Croft’s connectors exist precisely so they don’t.

How to do it

1. Add the Stripe connector. In your croft, add a connector for Stripe and paste your key — or just ask your assistant, “connect our Stripe account.” The key is held by Croft, encrypted, and never shown to apps.
2. Ask your assistant to use it. “When someone submits this form, create a Stripe customer and a payment.” Your assistant calls Stripe through Croft’s broker — no vendor SDK, no stored key.
3. Done. Every request goes out with the key attached last, and the broker only ever calls Stripe’s own domain.

Why it’s safe

The app can’t spill a key it never had, and for a team, a sensitive connector like payments can require an admin’s approval before an app or person can use it — with an audit trail of who connected what.

The same pattern works for your CRM, email, Azure DevOps, and 45+ more tools. See connectors → · The developer detail →

More from the blog