Here is a lighter routine that has worked for me: glance daily, review weekly.

Daily: two numbers, no clicks

For day-to-day motivation you only need two figures: revenue today and revenue this month. Anything more detailed belongs in a weekly review, not in the middle of a coding session.

Put those two numbers somewhere you already look. On a Mac that can be the menu bar or, on newer MacBooks, the notch area. Tools like Notch Revenue show today's and this month's Stripe revenue right in the notch and pop a small confetti when a sync finds a new payment. It syncs at launch and about every two hours, with a manual refresh, so it is a calm glance rather than a stream of alerts.

Use a restricted, read-only key

Whatever tool you pick, do not hand it your full secret key. In Stripe, create a restricted key with read access only to the resources the tool needs, give it a clear name, and store it somewhere safe. Notch Revenue keeps restricted read-only keys in the macOS Keychain and the revenue data stays on your Mac. Never paste a live key into a blog post, an issue tracker or a chat.

Weekly: thirty minutes, one checklist

Once a week, open the real dashboard on purpose:

1. Compare this week's revenue with last week's and note one reason for the change.
2. Check failed payments and refunds.
3. Read new customer emails or support threads.
4. Write down one experiment for next week (pricing page copy, onboarding email, a new directory listing).

Because the daily glance already answers "is anything happening?", the weekly session can focus on "why?".

What to expect

This split will not make revenue grow by itself. What it does is protect focus: you still see each small win, and the deep analysis happens once a week when you are ready for it.

Notch Revenue is a native macOS app for Apple Silicon Macs on macOS 14 or later, priced at US$19.99 one-time with no subscription.

Learn more at notchrevenue.com

I will describe the Stripe Dashboard in general terms, because Stripe updates its interface from time to time. If a label looks slightly different on your screen, look for the closest equivalent; the concepts do not change.

Why not just use the secret key?

Stripe gives every account a publishable key and a secret key. The secret key can do essentially anything the API allows: create charges, issue refunds, change customers, and more. Handing it to a third-party tool that only needs to read your revenue means trusting that tool with far more power than it needs.

A restricted key fixes this. You decide, resource by resource, whether the key gets no access, read access, or write access. If a restricted key leaks, the damage is limited to what you allowed, and you can revoke it without touching your main integration.

Principle of least privilege, applied to payments.

Before you start

• Make sure you are signed in to the right Stripe account. If you run several products, check the account switcher.
• Decide whether you are working in test mode or live mode. Keys are separate for each. A revenue display tool needs a live-mode key to show real revenue, but test mode is a great place to practise.
• Read the tool's documentation to see exactly which resources it needs to read. Good tools list them.

Step 1: Open the API keys area

In the Stripe Dashboard, go to the developers / API keys area. This is where your standard publishable and secret keys are listed, along with any restricted keys you have already made.

Step 2: Start creating a restricted key

Look for the option to create a restricted key. Stripe may ask how you plan to use the key; if so, choose the option that indicates you are giving it to another application or building your own integration, then continue to the permissions screen.

Step 3: Name the key after the tool

Give the key a name that tells future-you exactly where it lives, for example revenue-widget-readonly or bookkeeping-export-2026. One key per tool is the single most useful habit here, because it lets you revoke one tool without breaking the others.

Step 4: Set permissions to read-only

You will see a list of Stripe resources, each with options along the lines of None, Read, and Write.

1. Leave everything at None by default.
2. Set Read only for the resources your tool documents as required. Revenue tools commonly need read access to things like charges, payment intents, or balance-related data, but follow your tool's list rather than guessing.
3. Do not grant Write to anything for a display or reporting tool. If a tool that only shows numbers asks for write access, treat that as a warning sign.

Step 5: Create and copy the key once

Create the key. Stripe will show the key value; restricted keys typically begin with a prefix like rk_live_ or rk_test_. Copy it straight into the tool that needs it.

Important rules:

• Never paste a real key into chat, a forum, a GitHub issue, a screenshot, or a support email. In this guide, any example such as rk_live_XXXXXXXX is a placeholder, not a real key.
• Do not store it in a plain text note. On a Mac, a well-behaved app stores it in the Keychain for you.
• Do not commit it to a repository, even a private one.

Step 6: Paste it into the tool and verify

Open your tool, paste the key, and confirm it can load data. If it shows an error about permissions, go back to the key in the Dashboard and add the specific read permission it mentions. Avoid the temptation to switch everything to Read "just to make it work".

As an example, Notch Revenue is a macOS app that shows today's and this month's Stripe revenue in the MacBook notch. It asks for a restricted read-only key, stores it in the macOS Keychain, and keeps revenue data on your Mac. It syncs at launch and about every two hours, with a manual refresh, so a failed permission shows up quickly the first time you connect.

Step 7: Maintain your keys

Keys are not set-and-forget. A few times a year:

• Review the restricted keys list and delete any for tools you no longer use.
• Rotate keys for tools you still use if you have any doubt about where they have been.
• Check the "last used" information if the Dashboard shows it; an unused key is a key you can remove.
• If you think a key leaked, revoke it immediately and create a new one. Because it was restricted and read-only, the blast radius is small.

Quick checklist

• Correct account and correct mode (test or live)
• Restricted key, not the secret key
• Named after the tool
• Read-only, and only the resources the tool needs
• Pasted directly into the tool, never shared anywhere else
• Reviewed and pruned periodically

For the authoritative list of what each permission covers, see Stripe's own documentation on restricted key permissions. Five minutes of setup here saves you from ever wondering what a third-party tool could do with your account.

Notch Revenue — https://notchrevenue.com