Back to blog
How to create a Stripe restricted key for MRRdue
Step-by-step setup for a read-only restricted key. MRRdue imports billing metadata without permission to charge cards or edit subscriptions.
MRRdue connects with a Stripe restricted API key, not your full secret key. Restricted keys let you grant only the read scopes the product needs, which is a better default for any billing-adjacent tool.
Create the key in Stripe
In the Stripe Dashboard, go to Developers, then API keys, then Restricted keys. Create a new key and enable read access for Customers, Subscriptions, Invoices, Products, and Prices.
Leave write permissions off. MRRdue never creates charges, issues refunds, edits customers, or changes subscription items on your behalf.
Connect in MRRdue
Copy the key (it starts with rk_test_ or rk_live_) and paste it on the onboarding page. MRRdue verifies the key, encrypts it at rest, and runs a first sync of the last 90 days.
Use test mode keys while you explore. Switch to a live restricted key when you are ready to work real failed-payment cases.
What happens next
After the first sync, open the dashboard to see MRR movement, retention risk, and the failed-payments queue. Use Sync now when you want a manual refresh; webhooks and scheduled jobs handle ongoing updates in production.
If you disconnect Stripe, MRRdue removes the stored key. Your Stripe account is unchanged.
See your own recoverable revenue
Explore the demo dashboard or estimate recoverable dollars with the free calculator. No Stripe connection required to start.