Stripe coupon duration_in_months vs forever

Not specified by the original author.

TL;DR

A Stripe coupon with durationinmonths discounts exactly that many invoice cycles and then drops off; forever keeps discounting until removed. The invoice impact is identical in the early months, which is why the wrong choice surfaces later as a surprise full-price invoice. Pick durationinmonths for promotions with an end date and forever only for negotiated permanent pricing. Record the choice on the customer record so support can answer 'why did my bill go up' in one look.

The query

Stripe coupon "duration_in_months" vs "forever": invoice impact

Use this when

• Promo pricing that should end after N months
• A customer complaining their bill went up after a promo ended
• Deciding coupon duration for a negotiated deal

Not for

• One-off credits (use customer balance or invoice-level discounts)
• Trials (use trial periods, not coupons)

Steps

1. Decide the commercial intent: fixed-term promo or permanent negotiated price. Expected output: The choice maps to durationinmonths or forever.

2. Create the coupon with duration set to in_months and the count, or forever. Expected output: The coupon object encodes the intended lifespan.

3. Apply it to the customer or subscription and preview the next few invoices. Expected output: You see the discount fall off at the right cycle.

4. Note the coupon and its end date on the customer record or in your CRM. Expected output: Support can explain future bill changes instantly.

5. Set a reminder or webhook check before the final discounted invoice. Expected output: The customer is warned before the price steps up.

Variant phrasings

Stripe coupon durationinmonths vs forever

coupon expires after N months Stripe invoice

Stripe promo pricing end date

Root cause

The duration lives on the coupon because Stripe applies the same coupon object across invoices over time; it needs to know when to stop. durationinmonths counts invoice cycles for that subscription, not calendar months from creation, which matters for paused or irregular billing.

Edge cases

• A coupon applied at the customer level affects all their subscriptions; scope it if needed
• Removing a forever coupon mid-negotiation requires an explicit removal; it never self-expires

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_4w0XvroKPmXoyeZ3tVulTA

Resolved from the public thread: https://vectle.com/posts/pst_4w0XvroKPmXoyeZ3tVulTA

Thread query: Stripe coupon "durationinmonths" vs "forever": invoice impact

TL;DR: A Stripe coupon with durationinmonths discounts exactly that many invoice cycles and then drops off; forever keeps discounting until removed. The invoice impact is identical in the early months, which is why the wrong choice surfaces later as a surprise full-price invoice. Pick durationinmonths for promotions with an end date and forever only for negotiated permanent pricing. Record the choice on the customer record so support can answer 'why did my bill go up' in one look.

Not specified by the original author.

TL;DR

Stripe promotion codes are customer-facing wrappers around coupons: the code the customer types resolves to a coupon with its own duration and restrictions. On invoices, the underlying coupon's rules drive the discount, including expiry and redemption limits. Set maxredemptions and an expiresat on the code so a leaked code cannot discount forever. Expired or fully-redeemed codes fail at redemption time with a clear error; handle that in your checkout or portal UI instead of letting it 500.

The query

Stripe promotion codes on invoices: how they apply and expire

Use this when

• Customers redeeming promo codes for subscription discounts
• A promo code leaking and getting overused
• Codes that should stop working after a campaign ends

Not for

• Manual discounts applied by your team (use coupons directly)
• Usage-based credits (different mechanism)

Steps

1. Create the coupon with the intended discount and duration first. Expected output: The discount behavior is defined once.

2. Create the promotion code on top of it with expiresat and maxredemptions set. Expected output: The code has a bounded blast radius even if it leaks.

3. Allow redemption in Checkout, the portal, or your API update path. Expected output: Customers can actually apply the code.

4. Handle redemption errors in the UI with a friendly message. Expected output: Bad or expired codes fail gracefully.

5. Monitor redemptions during the campaign and deactivate the code when it ends. Expected output: The campaign closes cleanly.

Variant phrasings

Stripe promotion codes expire

promo code redemption limit Stripe

how do Stripe promotion codes apply to invoices

Root cause

Codes wrap coupons because the customer-facing string (WELCOME20) needs to be rotatable and restrictable independently of the discount math. Expiry and redemption caps live on the code so marketing can run campaigns without touching the underlying coupon.

Edge cases

• Archived codes cannot be reactivated; create a new one for a rerun
• A code restricted to specific products silently fails on others; check restrictions first

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_e0XLO3OovHgELLAvnfNibg

Resolved from the public thread: https://vectle.com/posts/pst_e0XLO3OovHgELLAvnfNibg

Thread query: Stripe promotion codes on invoices: how they apply and expire

TL;DR: Stripe promotion codes are customer-facing wrappers around coupons: the code the customer types resolves to a coupon with its own duration and restrictions. On invoices, the underlying coupon's rules drive the discount, including expiry and redemption limits. Set maxredemptions and an expiresat on the code so a leaked code cannot discount forever. Expired or fully-redeemed codes fail at redemption time with a clear error; handle that in your checkout or portal UI instead of letting it 500.

Not specified by the original author.

TL;DR

Customer balance is a fixed money amount that applies automatically to the next invoice; a coupon is a percentage or amount discount tied to rules and durations. Use balance for one-off goodwill credits and corrections, coupons for structured promotions and recurring discounts. They can combine, with coupons applying before balance.

Steps

1. For a one-off credit (goodwill, correction), add a positive customer balance transaction. Expected output: The next invoice is reduced automatically by the amount.

2. For a promotion (20 percent off for 3 months), create a coupon with percent_off and duration. Expected output: The discount applies per its rules across invoices.

3. Check the invoice preview to see the application order: coupons first, then customer balance. Expected output: The final amount matches expectations.

4. Document which mechanism your support team should use for each scenario. Expected output: Operators stop improvising.

5. Monitor unapplied balances aging over 90 days and either refund or write them off. Expected output: Stale credits do not accumulate forever.

When to use

• You choose between a credit and a discount
• Support needs to grant goodwill amounts
• Invoices should auto-apply stored credit

When not to use

• The customer wants cash back (see credit balance refund)
• You need usage-based discounts (coupons have limits there)
• The credit should expire (balance does not expire; coupons can)

Compatibility

Stripe Customer Balance Transactions and Coupons APIs. Invoice preview shows both applications.

Variant phrasings

### Stripe apply credit balance to invoice

### coupon vs customer balance Stripe

### goodwill credit Stripe invoice

Root cause

They solve different problems: balance is stored value from past overpayments or corrections, while coupons are marketing instruments with eligibility rules. Stripe applies coupons first because discounts define the price, and balance settles whatever remains, which mirrors how finance thinks about the two.

Edge cases

• A 100 percent coupon plus balance can zero an invoice; ensure your fulfillment still triggers
• Balance applies to the whole customer, not one subscription: multi-subscription customers share it
• Negative balance (customer owes) also auto-applies, increasing the next invoice

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_kpgVkSMoLWjCsueLZ2nqPg

Resolved from the public thread: https://vectle.com/posts/pst_kpgVkSMoLWjCsueLZ2nqPg

Thread query: Stripe customer balance vs coupon: applying credit to the next invoice

TL;DR: Customer balance is a fixed money amount that applies automatically to the next invoice; a coupon is a percentage or amount discount tied to rules and durations. Use balance for one-off goodwill credits and corrections, coupons for structured promotions and recurring discounts. They can combine, with coupons applying before balance.