Stripe
Connect Stripe to build dashboards on payments, billing, and revenue using a read-only restricted API key.
Read only access to your Stripe payments, billing, and revenue data. Stripe does not use OAuth here. You create a read-only restricted API key and paste it into Flitch, so Flitch can only read the resources you choose and can never charge customers, issue refunds, or change anything in your account.
Objects
| Object | Fields |
|---|---|
| Customers | Records, email, balance, currency, timestamps |
| Charges | Records, amount, status, customer, timestamps |
| Payment Intents | Records, amount, status, customer, timestamps |
| Invoices | Records, total, status, customer, timestamps |
| Subscriptions | Records, status, plan, customer, timestamps |
| Products | Records, name, active, timestamps |
| Prices | Records, amount, currency, product, timestamps |
| Payouts | Records, amount, status, arrival date, timestamps |
| Balance Transactions | Records, amount, type, fee, net, timestamps |
| Disputes | Records, amount, status, reason, timestamps |
| Credit Notes | Records, total, status, invoice, timestamps |
| Coupons | Records, amount off, percent off, duration, timestamps |
Scopes
Stripe does not use OAuth scopes. Access is controlled by the Read permissions you grant on the restricted key. Grant Read on the resources you want and leave everything else set to None:
Read Customers
Read Charges
Read PaymentIntents
Read Invoices
Read Subscriptions
Read Products
Read Prices
Read Payouts
Read Balance
Read Disputes
Read Credit notes
Read CouponsNo write or delete permissions. To tighten or widen what Flitch reads, edit or recreate the key in Stripe.
Connect
Create a restricted key in Stripe
In Stripe, go to Developers → API keys → Create restricted key. Grant Read on the resources you want (Customers, Charges, Invoices, Subscriptions, Products, Prices, Payouts, Balance, …) and leave every other permission set to None.
Copy the key
Copy the generated key. It starts with rk_ (for example rk_live_…). Use a live key for production data or a test key for test-mode data; each key only sees its own mode's data.
Open Data
In app.flitch.io, open the Data page.
Add Stripe
Top right, click Add, pick Stripe.
Paste the key and test
Paste the key into the Restricted API key field, then test the connection.
Pick objects and save
Tick the resources you want (defaults to all). Set a name. Save.
Each object becomes a dataset.
Refresh
Refresh is off by default. Every dashboard load runs a live query against Stripe. Enable refresh to schedule a background refresh and serve from cache between runs. See Refresh.
Disconnect
- In Flitch: open the connection from the Data page and delete it. Cache cleared.
- In Stripe: delete the restricted key at dashboard.stripe.com/apikeys to immediately cut off access.
Troubleshooting
Authentication failed. The key was deleted or rolled in Stripe. Create a new restricted key and update the connection.
Missing resources. A resource returns nothing if you did not grant it Read on the key. Edit the key in Stripe and add the permission.
No data in one mode. A rk_test_… key only sees test-mode data and a rk_live_… key only sees live data. Use the key for the mode you want to chart.