#geeky-mechanic_api

1 messages · Page 1 of 1 (latest)

keen ferryBOT
pliant ridgeBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

keen ferryBOT
#

👋 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/1234638480467034113

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

dusty python
#

Here is the checkout.session.completed id : evt_1PB2njAfoReX6TchyuzjOk1E

warm musk
#

Sorry, so the issue is you're not seeing specific event types generated, correct? If so, how are you creating those events? Are they being triggered through the Stripe CLI?

dusty python
# warm musk Sorry, so the issue is you're not seeing specific event types generated, correct...

Yep, specifically the ones tied to the checkout session. Let me pretty up the latter message. These were the generated events. However i was expecting a checkout.session.async_payment_succeeded as well which still hasn't fired since 6:35

Today

charge.updated
A CAD 862.31 payment for ch_3PB2nhAfoReX6Tch0DQ7rYue was updated
6:36:01 PM

checkout.session.completed
A Checkout Session was completed
6:35:59 PM

payment_intent.succeeded
The payment pi_3PB2nhAfoReX6Tch0cmOUNXW for CAD 862.31 has succeeded
6:35:59 PM

charge.succeeded
ch_3PB2nhAfoReX6Tch0DQ7rYue was charged CAD 862.31
6:35:59 PM

payment_intent.created
A new payment pi_3PB2nhAfoReX6Tch0cmOUNXW for CAD 862.31 was created
6:35:57 PM
dusty python
#

But I did add the listener
stripe listen --forward-to http://localhost:5001/payment/webhook/checkout --events=checkout.session.completed,checkout.session.async_payment_succeeded,checkout.session.async_payment_failed

warm musk
#

Right, so using the 4242 test payment method, you'll get the normal card payment events (e.g. not checkout.session.async_payment_succeeded, or checkout.session.async_payment_failed)

#

I'm not sure what/if we give you to test asynchronous payment method workflows. Let me dig a minute and circle back

dusty python
#

Hmmm, can I trigger this event for a specific checkout session? I need some data stored in the session for other tasks such as transfers

warm musk
dusty python
#

I guess the structure follows the JSON? so for a session object it would be session.id={desired id} ?

warm musk
#

I believe so. Is that working for you? I can try to create the command on my end here in a minute once the server calms down.

dusty python
#

Let me try that

#

I'm not sure about the syntax of the flag, what is the resource?

#

Tried this :
$ stripe trigger checkout.session.async_payment_succeeded --override session:id=cs_test_a1GPVZlHuaTlOrKtusBPC9koTZdDKgrL8ND9YDEhXWlweyYX57GlZHVdnw

#

didn't have the right id

warm musk
#

What did you get as a result?

dusty python
#

evt_1PB3jUAfoReX6TchGp5icCrv

#

This was the id : cs_test_a1y3LZ7YBkKT0PBHDWrw1mJDZShqUNrz7PkdW1qCY18IfvAoBZ5SiUnTaX

#

$ stripe trigger checkout.session.async_payment_succeeded --override --help Invalid value for override flag (--help). The override flag requires a value to set (--override fixtureName:path.to.param=value).

warm musk
#

Wait, hold on, let's back up a second. Why do you need to use an existing Checkout Session ID instead of letting CLI create a new one?