#cchambers

1 messages ยท Page 1 of 1 (latest)

rustic martenBOT
keen bison
kindred sinew
#

Hi, yes, I think the one in the screenshot is req_kOdsfKpCTHbDkc

keen bison
#

Okay what are you trying to do here? This is really weird because you would never trigger the payment page confirmation yourself. This would be handled by Stripe

kindred sinew
#

I am running stripe trigger checkout.session.completed in the CLI

#

per the documentation, to test webhook integration

#

so i think Stripe is handling it, and I'm just showing the log tails

#

I agree that it's very weird. Especially since it was working up until 11:21pm EST yesterday ๐Ÿ˜„

keen bison
#

Have you tried running stripe login again?

kindred sinew
#

yes

#

at least 3 times today... I've backtracked all the way to basically creating a new account and starting over

#

re-followed the integration steps [too]. it's an odd one...

When it broke last night, I was trying to change a parameter in the request to use a different email address than the default one -- I don't know if this can cause this issue, but it didn't work when I tried it:

stripe trigger checkout.session.completed --add checkout_session:customer_email="test@email.com"

and then it seemed like after that, this issue popped up.

keen bison
#

I reached out to my colleagues and it looks like this is something we did. We added a new set of requirements for Checkout sessions and haven't updated the CLI trigger actions yet.

kindred sinew
#

Can I tell you, that makes me feel so much better.

#

Thank you for looking in to this, I know you are super busy ๐Ÿ™‡

keen bison
#

We've also raised this internally to get it actioned quickly. Thank you for reporting the issue

kindred sinew
#

I just ran it and it worked, so guessing it was reverted or fixed. Regardless, thanks again.

keen bison
#

Yup we rolled back the change until we update the CLI. Thanks again for raising it and I'm glad we were able to get it resolved quickly