Quri

Stripe

Last updated 2026-06-14

What this unlocks

Connect Stripe with a read-only restricted key and Quri reads your succeeded charges — revenue, charge volume, and trends — so it answers money questions and alerts you to a drop early. Charges are currency-normalized, with zero- and three-decimal currencies handled correctly. Quri reads only and never moves money; any refund action is guarded, off by default, and prepare-confirm-audit — never automatic.

Connect it in Quri

  1. Open /app/connect in Quri and choose Stripe from the list of sources.
  2. Paste a restricted key that starts with rk_live_ — never your full secret key (sk_live_).
  3. Save the connection; Quri encrypts the key and scopes it to your workspace.
  4. Wait for the first sync — your succeeded Stripe charges appear in Quri once it completes.

Get your credentials

  1. Sign in to the Stripe Dashboard and go to Developers, then API keys.
  2. Click Create restricted key and name it something clear like "Quri read-only".
  3. Set the Charges resource to Read, leave everything else at None, and create the key.
  4. Copy the restricted key (it starts with rk_live_) and paste it into Quri — do not use a Standard or Secret key.

Access Quri reads with

  • Charges: Read on a restricted key — the single permission Quri needs to read revenue.
  • Every other resource stays None, so the key cannot create charges, read customers, or trigger payouts.
  • Never use a full-access secret key (sk_live_). If a restricted read key ever leaked, all it could do is read charges — that is the whole point of using one.

Troubleshooting

Should I just paste my secret key to get started faster?
No. Create a restricted key (rk_live_) with Charges set to Read and nothing else. A full secret key (sk_live_) can move money and read everything — Quri only needs to read charges, so granting more is risk with no upside.
Quri connects but reads no revenue, or returns a permissions error.
Your restricted key is probably missing Charges: Read. Edit the key under Developers, API keys, set the Charges resource to Read, save, and reconnect. Also confirm it is a live key (rk_live_), not a test key (rk_test_).
Can Quri refund or charge through Stripe once connected?
No. With a Charges: Read restricted key Quri cannot write anything to Stripe at all. Any refund capability is a separate, opt-in guarded action that is off by default and always prepare-then-confirm with a full audit log — it never fires automatically. (Provider path confirmed 2026-06-14 against docs.stripe.com/keys/restricted-api-keys.)

Related guides