#max_unexpected
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/1459105012532646105
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
๐ happy to help
Hi ๐
Thanks!
We don't want to limit to one subscription because sometimes two different subscriptions are needed (one for main product and one for an extra)
Is there another work around?
why not just update the subscription to add the extra products to that
it would be easier to generate one invoice for both
That's a good idea, but I don't manage one of the applications that uses the same stripe account so I can't personally make that fix. Is there something else I could do in the meantime
how are you sending your customers to the Checkout Sessions? from your website or from a payment link?
They are embedable sessions rendered with EmbeddedCheckoutProvider element
what's the return_url you're using?
maybe you're sending the customer back to that page when the payment succeeds which makes them think they haven't subscribed yet
It proceeds to a different page but if it fails it goes back. From what info I have the member is only entering their payment details one time so I don't think this is the case
do you know the customer ID?
is this happening to all customers or just one in particular?
It's happened to a couple. Here is an example one cus_Tka6KtXSGMHeDM
taking a look
Thanks
ok so how are you checking whether the payment succeeded or not on the paymentSuccess page?
Just checking our database to see if the stripe webhook was called
I meant on the frontend
Let me know if you still have any questions on this, but it does look like your site created a second Checkout Session, a minute after your customer paid. Who then appeared to pay again.