Connect your own Stripe account — your key, your data. One sync pulls customers, subscriptions and invoices into your Elastbiz tables, where dashboards, workflows and AI agents can finally see them next to the rest of your business.
Your revenue lives in Stripe’s dashboard; your customers live in your CRM; your invoices live somewhere else again. Answering “which customers churned last month and what did they owe” means exports and spreadsheets.
One connect call stores your key host-side. One sync call pulls customers, subscriptions and invoices into your own tables. From there it’s rows — query them, chart them, join them to your CRM, let agents read them.
Credentials are written to per-org files on the host — never stored in the database, never echoed back by any endpoint.
POST /api_stripe_sync pulls customers, subscriptions and invoices into your org’s tables. Re-run whenever you want a fresh pull.
Synced data lands as ordinary rows — filter, sort, add columns, join to your own customer records.
Agents answer questions like “who is past due” from your own tables, through the same MCP tools as everything else.
Stripe webhooks are HMAC signature-verified on arrival. Your endpoint, your secret, constant-time compared.
This is your Stripe account talking to your workspace. Elastbiz billing is a separate system — your key is never used for our charges.
The same binary. The same substrate. Move between them with a data export.
We host Stripe at app.elastbiz.com. EU data residency, backups on us.
Docker one-liner. Your Stripe data lands on your disk; secrets stay in per-org host files.
Your Stripe key, your tables, your agents. Connect once, sync when you like.