Stripe
Create a restricted key in Stripe with read access only, paste it once, and we read your revenue on our server. The key is not stored.
Connect in three steps
Create a restricted key
In the Stripe dashboard open Developers → API keys and choose Create restricted key. Use a restricted key, never your secret key.
Make it read-only
Give it read access to Charges, Subscriptions and Invoices. Leave everything else on None.
Paste it and verify
Paste the key (it starts with rk_live_ or rk_test_) and press Verify. We check your revenue on our server and never store the key.
What buyers see
- MRR and revenue over the last 28 days, marked as read from Stripe.
- A signed summary, so the numbers cannot be edited.
Troubleshooting
"Use a restricted key starting with rk_live_ or rk_test_"
You pasted a different kind of key. Create a restricted key as in step 1.
Verification fails with a permission error
Check the key has read access to Charges, Subscriptions and Invoices.
My revenue shows $0
Stripe returned no payments. A connected account with no revenue still counts as a linked source.
Related
- How verification works · What the Verified badge needs, which connections count, what buyers see, and what stays seller-reported.
- What we read, keep and delete · What each integration lets AppAcquire read, what we keep, what we discard, and how to remove it.
- RevenueCat · Verify a subscription app by pasting its RevenueCat Verified page link. No API key, and it works before the first sale.
Still stuck? Contact us and we will help.