Reference 1 of 3

What we do with your Stripe key

This page exists because connecting a payment key to someone else's service is the largest thing we ask of you. So here is the whole surface, not a summary of it.

The three calls we make

We read a subscription, to see what it is on today. We create a coupon, when the offer you configured needs one. And we write that coupon — or a pause — onto the subscription. That is the entire set.

What is absent

There is no code path in this service that calls charges, payouts, transfers, customers, payment intents, balance, invoices, refunds or prices. Not restricted by policy — absent. Two Stripe resources are reachable from our code and those are the two above.

The key itself

We require a restricted key. A key that does not start with rk_ is refused when you paste it, with the same message from both of the two functions that can write one. The key is encrypted before it is stored, with a passphrase kept in a separate secret store, and exactly one server-side function can decrypt it. No screen in the product will show it back to you, in either form.

The scope is yours to set

The scope of the key is yours to set in Stripe. We ask for read and write on Subscriptions and Coupons. If you grant less, Stripe refuses the call and we record the refusal rather than working around it.