Integrations / Stripe
Stripe
Stripe payment processing platform for charges, customers, subscriptions, and invoicing
API key
Indexes
Actions
Events
What Telara does
Capability matrix
Before you connect
Prerequisites
A Stripe account.
Permission to create a restricted or secret key.
Vendor setup
Get the credential
1
Open Developers → API keys
In the Stripe Dashboard, open Developers → API keys.
2
Create a restricted key when you can
Prefer a restricted key with only the access you want Telara to have. Paste it in Settings → Integrations → Stripe.
In Telara
Connect in Telara
API key
Stripe secret API key (sk_live_... or sk_test_...)
In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.
Fields Telara asks for
- API key
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Customer | Partial — not every record the vendor holds is synced |
| Invoice | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Customer | Up to 1 hour | Removed records disappear when Telara next reconciles that resource |
| Invoice | Up to 1 hour | Removed records disappear when Telara next reconciles that resource |
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
Excluded from semantic search: Customer, Invoice.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty
Known limitations
Test mode and live mode are different keys. Connecting test mode will not show live customers.
Restricted keys that omit the objects you care about connect successfully and then look empty.