Skip to main content

Connect Stripe

Stripe is a billing provider for coupons and for MRR proof points, alongside Paddle, Polar, Lemon Squeezy, Dodo Payments, and RevenueCat. Each product has one coupon connection, even when two products share a Stripe account. Switching providers on a listing replaces that connection and re-imports. Dealpuffin never asks for a secret key, and Stripe is not a way to sign in.

Coupons​

  1. In the Stripe Dashboard, open Developers, then API keys.
  2. Create a restricted key. When Stripe asks how you will be using this key, choose Providing this key to a third-party application, and name it Dealpuffin.
  3. Turn on read for Coupons and Promotion codes.
  4. Copy the key. It starts with rk_live_ or rk_test_.

Open the product from Submit a product and paste the key in Coupons. Dealpuffin checks that the key can read coupons, encrypts it, and runs the first import. You only see a hint of the key after that.

Optional Stripe product ids (prod_…) live on that connection. A coupon limited to those ids can be published only when the ids overlap.

Use a live key for coupons you want real early adopters to redeem. A test key only talks to Stripe test mode.

The key does not create coupons, does not turn promotion codes on at checkout, and does not charge a card. If your payment page does not accept promotion codes, a customer has nowhere to paste one. That switch is in Stripe.

MRR​

Create a restricted key with read on Subscriptions. It can be the same key if that key has both sets of permissions, stored again on the proof-point connection. Choose daily, weekly, or monthly, and whether the listing shows the exact MRR, a band, or hides it. The first read happens when you connect. A band does not put the number on the public listing. See Proof points.

What is stored​

The plaintext key is not stored. A connection keeps an encrypted ciphertext, a nonce, a short hint, and the last sync time. Sync does not publish coupons. See Sync and publish.