Connecting Stripe

Connect Stripe and Morevy pulls your payment history itself. There is no file to export, and the key you hand over can only read.

The key you create

Morevy uses a restricted API key: Stripe’s mechanism for granting a tool exactly the access it needs and nothing else. The key can read your payment history. It cannot move money, issue refunds, or change anything in your account, and revoking it in Stripe at any time cuts the connection.

In Stripe:

• Open Developers, then API keys, and choose Create restricted key.

• Name it Morevy.

• Set Read on these resources, and None on everything else: Account, Customers, Charges, Subscriptions, Invoices, Payment Intents, Products, Prices, Refunds, Events, Disputes, Credit Notes.

• Create the key and copy it. It starts with rk_live_.

Caution. Never paste a secret key (sk_live_). It works, but it grants far more than Morevy needs. The restricted key is the right shape: if it were ever exposed, it could only read.

In Morevy

Paste the key into the connect dialog in the thread. Morevy verifies it can read your account, syncs your payment history, and shows you what it pulled for review before anything is computed. The key is stored encrypted and never appears in the conversation.

Note. If Stripe reports a missing permission during a sync, the message names the resource. Edit the key in Stripe, set Read on that resource, and run again.

What connecting does not skip

A synced source is read the same way a file is. You still confirm which rows count as recurring revenue before the close will run, plan durations are still resolved before anything is spread, and every figure still carries its checks and its provenance. Connecting changes how the data arrives, not what is checked.

Prefer not to share a key? Export your payments covers the file route, and Exporting from Stripe shows the exact export to pull.