#martin-dev - coupons
1 messages · Page 1 of 1 (latest)
Coupons are currently designed to work with Products. That's just how they were designed. I don't know that I have a good answer as to why
I'll definitely file this feedback though
It's a relatively common ask
Ah I got a better reason for you from someone:
The reasoning is that a successful PaymentIntent represents a past money movement. If we introduce $0 amounts, then merchants will have to figure out if a successful PaymentIntent really means money has moved. In addition, states like requires_payment_method are not useful since you don't need a payment method for $0!```
Thank you for the response!
Coupons are currently designed to work with Products.
Hmm, yeah, that's kind of what I thought. The "no $0 payments" reason makes sense too.
We store our own products, but want to use Stripe's coupon system. It seems like it's totally possible (just manually calculate the amount), but I'm wondering if it's wise to do so...
It feels a bit weird to use a system built for Stripe Products when we're not using Stripe Products.
This may not fit your use-case, but we do have an orders API you can use for one time payments with products
Otherwise, manually calculating discounts with PaymentIntents should work fine
Okay, thank you for the suggestion!