Stripe: setup and configuration
Browse Stripe customers, invoices and subscriptions as provider data.
- Who
- Workspace settings permission is required to manage this connection.
- Where
- SettingsWorkspaceIntegrationsStripe
- Before you start
- You need access to the provider account and its required API or authentication features. Provider charges and plan limits still apply.
What Stripe does
Browse Stripe customers, invoices and subscriptions as provider data.
Set up and verify
- Open Settings > Workspace > Integrations > Add integration > Stripe.
- Create a restricted test Stripe key with read access to customers, invoices and subscriptions, paste it in Stripe restricted key and choose Save connection. Lumenbase discovers and verifies the Stripe account.
- Use Test connection, grant access to the saved resource, and open Stripe in Directory.
Connection

No connected account
Setup
Configuration
| Setting | Where | Default | Applies to |
|---|---|---|---|
| Stripe restricted key | SettingsWorkspaceIntegrationsStripe | Empty | Workspace |
| Connection setup | SettingsWorkspaceIntegrationsStripe | No connection | Workspace |
| Test connection | SettingsWorkspaceIntegrationsStripe | Manual | Workspace |
| Replace credential | SettingsWorkspaceIntegrationsStripe | Existing credential | Workspace |
| Remove local access | SettingsWorkspaceIntegrationsStripe | Not removed | Workspace |
Stripe restricted key: Only rk_test_ restricted test keys with read access to customers, invoices and subscriptions are accepted.
Connection setup: The credential is verified before it is saved for this workspace.
Test connection: Checks the saved authorization without changing provider records.
Replace credential: Keeps the same provider source. A different account requires a new connection.
Remove local access: Stops local reads. Retry token cleanup if removal reports pending cleanup.
Limits
- Only restricted test keys are accepted here. Lumenbase platform billing accounts are rejected.
- This is read-only customer finance data. It does not charge cards, create subscriptions, or turn imported Stripe invoices into Lumenbase invoices.
- Your Lumenbase subscription billing is separate from this integration.
- Saving a credential does not give every workspace member access. Use the resource access control to grant the selected resource to the people who need it.
- Remove local access stops Lumenbase using its saved credential. Revoke the credential at the provider too if it should stop working elsewhere.
Troubleshooting
- Confirm the active Lumenbase workspace and your workspace settings permission. Complete Verify account or Set up 2FA if requested.
- Check the credential, provider account, region and selected resource. A credential for another source cannot repair this connection.
- If the provider rejects access, renew or replace the credential. If the connection changed while you were editing, refresh before trying again.
- Use the page’s test or read controls where offered, then inspect its result. A saved credential alone does not prove data is reaching the intended page.
- For missing shared resources, check both provider access and the explicit resource grants. Load more when the list has another page.
- For a rate limit or temporary provider failure, wait and retry. For cleanup needed, use the cleanup retry instead of adding another connection.
Quick Reference
- Connection settings
- Settings → Workspace → Integrations → Stripe
- Verify
- Check the test result, selected source and intended data view.
Frequently asked questions
What does the Stripe integration do?
Browse Stripe customers, invoices and subscriptions as provider data.
Where do I configure Stripe?
Open Settings > Workspace > Integrations > Stripe. Workspace settings permission is required to manage the connection.
What are the limits of the Stripe integration?
Only restricted test keys are accepted here. Lumenbase platform billing accounts are rejected. This is read-only customer finance data. It does not charge cards, create subscriptions, or turn imported Stripe invoices into Lumenbase invoices. Your Lumenbase subscription billing is separate from this integration. Saving a credential does not give every workspace member access. Use the resource access control to grant the selected resource to the people who need it. Remove local access stops Lumenbase using its saved credential. Revoke the credential at the provider too if it should stop working elsewhere.
Was this article helpful?
