AtlasWork, planned itself.

The AI-native, all-in-one work platform. Tasks, projects, CRM, contracts, and analytics in one calm workspace.

  • SOC 2 II
  • ISO 27001
  • HIPAA
  • GDPR

Product

  • Overview
  • PDF tools
  • People & HR
  • Integrations
  • Marketplace
  • Pricing

Resources

  • Guides
  • Docs
  • API reference
  • Support
  • Changelog
  • Status

Company

  • About
  • Careers
  • Press
  • Contact

Legal & trust

  • Trust center
  • Security
  • Privacy
  • Terms
  • DPA
  • GDPR
  • SLA
  • Refunds
Atlas, a product by wrxstack.com·© 2026 wrxstack·All rights reserved
Made in India
Skip to documentation
AtlasDocs
Back to Atlas

Start here

  • Overview

Developer

  • REST API
  • MCP (AI agents)
  • SDKs
  • Quick actions

Connect

  • Connectors
  • Integrations

Reference

  • Keyboard shortcuts
  • Module reference

StripeBilling

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

1

Open the Stripe API keys page

Sign in with the account owner. dashboard.stripe.com/apikeys

Screenshot placeholder
2

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).

Screenshot placeholder
3

Copy the secret

Stripe shows the secret once. Copy it into the Atlas Stripe connector settings page.

Screenshot placeholder
4

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

Screenshot placeholder
5

Run a test event

Click Send test webhook for customer.subscription.created. Atlas should mark the connector Connected.

Screenshot placeholder

Required scopes and permissions

Customers readread_only.customers
Subscriptions readread_only.subscriptions
Invoices readread_only.invoices
Charges readread_only.charges
Events readread_only.events

Setup checklist

  1. Create the provider app in a sandbox or development workspace.
  2. Add the Atlas redirect URL to the provider app configuration.
  3. Copy the client id, client secret, or API key.
  4. Paste the credentials into the Atlas connector settings page.
  5. Click Connect and complete the provider sign-in screen.
  6. 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

  1. Click Disconnect on the Atlas Stripe connector page.
  2. Roll the restricted key in Stripe Developers, API keys.
  3. Delete the Atlas webhook endpoint in Developers, Webhooks.

Ready to connect Stripe?

Paste the credentials you copied above into the live connector page.

Open the connector page