#phonicuk - Coupon
1 messages ยท Page 1 of 1 (latest)
HI :wave
Could you share a request ID corresponding to one of these coupon creation requests?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
promo_1KorQpHd51xGsopZ4zkCo1jI
evt_1KorQpHd51xGsopZ3CrckOnc for the creation event - if that's what you're after?
aaah this is what you're asking for: req_lbYguolxnRlTDT
It shows up as expired when I try to add during checkout
in my dashboard it shows as completely valid and doesn't expire for several hours
Hmmm... that coupon was created with an expires_at timestamp of today
aye due to expire at 11:59 PM today, so a little shy of 7 hours from now
Yeah sorry, I'm stuck looking at the actual timestamp numbers on my end ๐
Okay still looking
๐
And I just use a Python function ๐
(datetime.datetime.fromtimestap())
I see this coupon is restricted to first_time_transaction. I'm not exactly sure how that rule is applied during Checkout
Is it possible the interface is considering you a repeat customer?
I'd be impressed if it can do that from an incognito window
True
I'll try one that is set not to be limited to the first-time order just to see what happens though, but otherwise the same settings and an expiration date that's tomorrow instead of today
okay that worked
๐ค
so now I'll make one that's expiration date of tomorrow but limited to first-time customers...
I appreciate the rigorous methodology
that doesn't work
so setting it to first-time customers is the limiting factor
Interesting that it specifically says the code is expired rather than "You've already used this" or words to that effect.
req_lbYguolxnRlTDT - Doesn't work. First time customers, exp date today.
req_cNEvQ3WzCNhcIe - Works. All customers, exp date tomorrow.
req_hj9duL1gpG6RKl - Doesn't work. First time customers, exp date tomorrow.
๐
I am taking note of these and will raise the issue. Just to be clear, what happens if your exp date is today but all customers?
Copy that. I think we've narrowed down where the issue lies.
That should be able to squash all the bugs right there