Connect Stripe

Create a restricted read-only key in Stripe and connect it to goalmrr. Secret keys are refused.

View as Markdown

In the Stripe dashboard, create a restricted key (rk_live_… or, for a test account, rk_test_…) with read access only on Balance, balance transactions and subscriptions. Paste it on the Revenue page of goalmrr.

goalmrr refuses a secret key (sk_). Stripe does not offer a way to list every permission on a restricted key, and goalmrr does not try a write to find out. It accepts the restricted-key shape and then checks three reads: Balance, one balance transaction and one subscription. If one of those reads is forbidden, the key is refused and nothing is stored. A test-mode key is accepted and labelled test.

The key is stored encrypted and is never shown again, except its last four characters. One Stripe account connects to one workspace. Your revenue refreshes every hour. A number counts as fresh for 48 hours after the last successful read; after that the page says when it was last verified. Disconnecting destroys the key. The numbers already read stay until you remove the connection, which deletes them.

goalmrr reads totals only: charges and refunds per month and currency, monthly recurring revenue from active subscriptions, and how many subscriptions are active. It does not read customer names, email addresses or card numbers. Yearly prices count as one twelfth of a month. See payment providers for the other five.