PlumHelp
Help · Workspace settings

Stripe: subscriptions as licenses

Connect Stripe with a read-only key, and Plum records each subscription as a license, with its changes and cancellations as revenue events, so billed revenue and the ARR walk agree. Plum never writes to Stripe.

Owners, admins and revops

Connecting

  1. In Stripe, open Developers, then API keys, and choose Create restricted key.
  2. Give it Read access to Customers, Subscriptions, Products and Prices. Leave everything else at None.
  3. Create the key and copy it. It starts with rk_live_ (or rk_test_ for Stripe's test mode).
  4. In Plum, open Integrations, paste the key under Stripe, and select Connect Stripe. Plum checks the key with Stripe before saving it.
  5. Select Sync now to bring your subscriptions in.

Plum refuses a secret key (sk_live_ or sk_test_). A secret key can change and charge anything in your Stripe account, and Plum only reads. The key is stored encrypted, and nobody can read it back; disconnecting deletes it.

Plum syncs once a day on its own, and whenever you select Sync now. Changes are recorded under the name of the person who connected Stripe, and the change history shows them. If that person stops being an owner, admin or revops member, the sync stops until someone connects Stripe again.

What Plum reads

  • Every subscription, whatever its status, with its prices, quantities and discounts.
  • The customer on each subscription: name and email address.
  • Your product names, to match each price to an offer in your offer library.

How a subscription becomes a license

  • The license's monthly amount (MRR) is each price times its quantity, turned into a month: a yearly price counts a twelfth, a quarterly price a third, a weekly price 52 twelfths, a daily price 365 twelfths.
  • A discount that lasts forever comes off. A coupon that runs out, once or for some months, doesn't: it is a temporary price, not the recurring one.
  • Usage-based (metered) prices count as zero. Only what the customer has committed to counts.
  • Tiered prices have no single unit price, so they count as zero too. The sync says which subscriptions had them.
  • Each price is matched to an offer by its Stripe product, then by the product's name. A price with no matching offer still counts toward the license's amount.

Which account it goes to

  • The account Plum created for that Stripe customer before, if there is one.
  • Else the account with the domain of the customer's email address. A public mailbox, such as gmail.com, never matches.
  • Else the account with the same name.
  • Else Plum creates an account for the customer.

Changes, cancellations and trials

New subscription
Recorded as a license from the day it started paying. Past due counts as active.
Price or quantity change
The license changes from the day of the sync, and the difference is booked as expansion or contraction.
Cancelled
The license ends on the day the subscription ended, and the churn is booked.
Set to cancel later
The license ends on that date, and stays live until then.
In a trial
Not recorded yet. It shows as upcoming, and is recorded once the trial ends and the customer pays.
Incomplete, unpaid or paused
Not recorded, and shown in the sync's summary. One already recorded stays until it is cancelled.

What is skipped

  • Subscriptions in another currency than your workspace's.
  • Subscriptions cancelled before Plum first read them.
  • Subscriptions whose license someone renewed, ended or deleted in Plum. Plum leaves what a person did alone.

After each sync, Integrations shows how many subscriptions were recorded, changed, ended or skipped, and why, with the first few listed.

Plum only reads from Stripe. It never creates, changes or cancels anything there, and never charges anyone. Running the sync again with nothing new in Stripe changes nothing in Plum.

Related