#fossil_best-practices
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1262499347661062334
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Yes, you would want to create a new Coupon per time period that you want to have a unique expiry. We have a field for when a discount cannot be redeemed anymore and we also have one where you can set a redemption limit if you want to make sure that the person you are sending to can only use it once
https://docs.stripe.com/api/coupons/object#coupon_object-redeem_by
https://docs.stripe.com/api/coupons/create#create_coupon-max_redemptions
So yes, it does sound like creating a lot of codes would probably be the best way to restrict this to just the person that you are sending to.
And Stripe would be fine with this?
Yep, we allow many thousands of coupons to be created on an account
It would probably be around 40k codes per year
I might have to implement some kind of discount system on my own site. Cleaner way of doing this maybe
We don't currently have a limit that I am aware of and am seeing a reference to a user that created 1 million, so that should give you a solid amount of time at 40k per year
Heh. Okay cool. Cheers