Connect
Stripe
Stripe connects with a restricted API key rather than OAuth. You create the key in the Stripe dashboard, choose exactly which resources Modiva may access (read-only is recommended), and paste it into Modiva. Because you scope the key yourself, Modiva can never do more than you allow, and you can revoke it in one click.
Before you start
- A Stripe account (test or live mode).
- A restricted API key created under Developers → API keys → Create restricted key — grant only the permissions you want Modiva to use.
Step-by-step setup
- 1
Create a restricted API key
In the Stripe dashboard open Developers → API keys and click "Create restricted key". Give it a name like "Modiva", then set each resource's permission — choose Read for the resources you only want to report on (Customers, Subscriptions, Invoices, Balance) and Write only where you want Modiva to create records. Create the key and copy the rk_… value; you won't be able to see it again. Use a test-mode key first if you want to try things safely.
- 2
Sign in to Modiva
Log in at modiva.ai and open the Dashboard. You need a Modiva account before you can connect any platform — creating one takes a minute and no credit card is required for the free tier.
The Modiva dashboard — your home for connections, posts and analytics. - 3
Open Connections → New connection
In the left sidebar choose Connections, then click New connection. You'll see the full catalogue of platforms grouped by category (Social, Ads and CRM).
The connection picker. Use the search box or category filter to find your platform. - 4
Paste the restricted key
Click the Stripe card. In the inline form paste the rk_… restricted key and click Connect.
- 5
You're connected
Modiva validates the key against Stripe's API and shows the connection as Connected. If a tool later returns a permission error, edit the restricted key in Stripe to grant that resource and reconnect — the error names exactly which permission is missing.
Permissions Modiva requests
When you connect Stripe, Modiva asks only for the access it needs to run the tools you use. You can revoke it any time from Stripe or by disconnecting in Modiva.
- Read (and, if you allow it, write) customers, products and prices
- Read subscriptions, invoices and payments
- Create checkout sessions (only if you grant write access)
- Read your account balance and payouts
Troubleshooting & FAQ
Why a restricted key instead of OAuth?
A restricted key lets you decide precisely which Stripe resources Modiva can touch, down to read-vs-write per resource, and revoke it independently. It works today with no platform onboarding. Stripe Connect (OAuth) is an option we can add later without changing how the tools work.
Should I use a read-only key?
For reporting and analytics, yes — grant Read on Customers, Subscriptions, Invoices, Payments and Balance and leave everything else at None. Only grant Write on the resources where you want Modiva to create records (for example Checkout Sessions or Customers).
Test mode or live mode?
Either. A test-mode restricted key (rk_test_…) connects the same way and is perfect for trying the tools without touching real money. Swap it for a live key (rk_live_…) when you're ready — just Disconnect and reconnect with the live key.
How do I revoke Modiva's access?
In Stripe open Developers → API keys, find the "Modiva" restricted key and roll or delete it, then Disconnect the connection in Modiva.
Need help with Stripe?
Fin can answer follow-up questions and walk you through any step.
Stripe playbooks
Connected? Put Stripe to work with these free growth playbooks.