# Connect Stripe and Polar

> Connect Stripe or Polar with a restricted, read-only key, for one property or several accounts, and see where MRR comes from when a property reports none.

Source: https://lopebase.com/docs/connect-stripe
Updated: 2026-10-08
Open in the app: https://app.lopebase.com/connections

Stripe and Polar both feed MRR, subscriptions, and revenue onto Revenue and Overview. Stripe connects with a restricted key you create yourself; Polar with an organization access token. Neither can move money, refund a charge, or change anything in your account.

## Connect Stripe

1. **Create a restricted key:** Open the connection and use the link to Stripe's key creation page. It pre-fills the key's name and sets Charges, Customers, Subscriptions, and Balance to Read for you. [Open the Stripe connection](https://app.lopebase.com/connections?connect=stripe)
2. **Create the key and copy it:** Press Create key in Stripe, then copy the key. It starts with `rk_live_`, never `sk_live_`; a secret key can do anything in your account, a restricted key only what you set to Read.
3. **Paste it in and pick the property:** Paste the key, then connect it for the right property, or choose **All my properties** if one Stripe account covers more than one.

> **Tip:** Not sure which permissions a dashboard like this needs from Stripe? The [Stripe read-only key builder](https://lopebase.com/tools/stripe-restricted-key) lists the exact ones to set to Read for LopeBase, or for any other tool you connect.

## Connect Polar

1. **Create an organization access token:** In Polar, open Settings and create an access token with the `subscriptions:read` and `orders:read` scopes.
2. **Paste it in:** Paste the token and connect it for the right property, the same way as Stripe.

## Several accounts

If you run more than one product on separate Stripe or Polar accounts, connect each account for the property it belongs to. If you later add a key for a Stripe account that lists a different property's website or business name, LopeBase warns you before saving, with a one-click way to move it to the right property instead.

## Where MRR comes from

When a property's own app does not report MRR itself (through the [LopeBase Adapter](https://lopebase.com/docs/lopebase-adapter)), Overview, dashboards, the weekly email, and your AI agent all take it from that property's connected Stripe or Polar account instead, in its own currency. One-time payments from the last 30 days show on their own, separate from recurring MRR, so neither one hides inside the other.

## Where to go next

- [Revenue](https://lopebase.com/docs/revenue) for what Stripe and Polar feed once connected.
- [Connect your tools](https://lopebase.com/docs/connections) for every other kind of connection.
- [Reconnect a connection](https://lopebase.com/docs/reconnect-a-connection) if a key is later revoked.

## If something goes wrong

### Revenue shows n/a even though Stripe is connected

Check that the key's permissions include Invoices if you expect one-time revenue; a key missing a permission LopeBase needs shows that one number as not reported rather than guessing.

### It warns that this Stripe account belongs to another property

LopeBase checks whose account a key belongs to by its website, business name, or statement descriptor. If it is actually right for this property, confirm that on the warning; if not, use the one-click option to move it to the correct property.

### I pasted a secret key instead of a restricted one

Create a restricted key instead and connect that. Never paste a key starting `sk_live_` into any tool, LopeBase included.

### One Stripe account covers several of my products

Connect it once, then choose **All my properties** so every product on that account is covered without pasting the key again.