Billing
Stripe
Read Stripe customers, subscriptions, and invoice events so revenue posture lives next to customer records in Atlas.
What this connector does
- Read Stripe customer, subscription, invoice, and charge metadata.
- Reflect payment status and billing health in Atlas account records.
- Listen for signed webhook events to update account health in near real time.
- Never store full card numbers or raw payment instruments.
Before you begin
- You are an admin on the Stripe account.
- You can create restricted API keys.
- You have a sandbox (test mode) account for first validation.
Get your credentials
Open the Stripe API keys page
Sign in with the account owner. dashboard.stripe.com/apikeys
Create a Restricted key
Click Create restricted key, name it Atlas Connector, and grant only the resources Atlas needs (customers read, subscriptions read, invoices read, charges read, events read).
Copy the secret
Stripe shows the secret once. Copy it into the Atlas Stripe connector settings page.
Create a webhook endpoint
In Developers, Webhooks, add endpoint https://YOUR-ATLAS-HOST/webhooks/stripe and select the events listed below. Copy the signing secret into Atlas. Stripe webhooks
Run a test event
Click Send test webhook for customer.subscription.created. Atlas should mark the connector Connected.
Required scopes and permissions
read_only.customersread_only.subscriptionsread_only.invoicesread_only.chargesread_only.eventsSetup checklist
- Create the provider app in a sandbox or development workspace.
- Add the Atlas redirect URL to the provider app configuration.
- Copy the client id, client secret, or API key.
- Paste the credentials into the Atlas connector settings page.
- Click Connect and complete the provider sign-in screen.
- Run Test connection from the connector page to verify health.
Troubleshooting
No such webhook signing secret
You copied the wrong secret. Open the webhook endpoint in Stripe and click Reveal under Signing secret.
StripeAuthenticationError
The restricted key was revoked or rotated. Generate a new key and update Atlas.
Webhook delivery failed
Check Atlas health page for the connector and confirm the receiver returns a 2xx within 5 seconds.
Webhooks
Atlas validates every event using the Stripe-Signature header and the per-endpoint signing secret.
Events Atlas listens for
- customer.subscription.created
- customer.subscription.updated
- invoice.payment_succeeded
- invoice.payment_failed
- charge.failed
Provider docs: https://stripe.com/docs/webhooks
Disconnect and data deletion
- Click Disconnect on the Atlas Stripe connector page.
- Roll the restricted key in Stripe Developers, API keys.
- Delete the Atlas webhook endpoint in Developers, Webhooks.
Once you have the credentials above, paste them into the live connector page to finish connecting Stripe.
Open the Stripe connector page