#smriti15s-Checkout

1 messages · Page 1 of 1 (latest)

hasty hawk
#

Can you paste me the Checkout Session Id?

#

If you only received payment_intent.processing, that means your PI hasn't been completed. When a PI is completed you should receive payment_intent.succeeded, and that's when the checkout.session.completed will be fired

small sun
#

Sorry, I lost the checkout session id.
Could you please check by charge id, why it is stuck at payment.created and not going forward.

#

There are 2 flows in my application:

  1. Checkout: I am creating checkout session and listening to checkout events. Which are not getting called. In fact the test event is hitting the server.
  2. Stripe elements: I am creating payment intent and listening to payment intent events, which are working fine.
hasty hawk
#

Do you have the request Id that create the Checkout?

small sun
#

cs_test_a1ahQ3ny3lZSzFf3HKoZPsn0P9LEw1FG8yp1gbIpAawc590L6OvOYfrmGY

#

Checkout id

#

"payment_intent"=>"pi_3KGbsKGPMeBm9QN30ElD5vVI",

hasty hawk
#

evt_1KGbsdGPMeBm9QN3VvSMhHcX <- the checkout.session.completed to above PaymentIntent/Checkout Session

small sun
#

Could you please check whether this is created for a connected account or not?

#

I created the checkout session - direct charge on connected account but that is not getting listed there.

hasty hawk
#

The request req_e522Hg3PpPTbJk is created with Destination Charge, which means platform (your account) is the owner of the transaction. You would need a webhook on your Platform to receive the event!

dapper canopyBOT
#

This thread has been archived. If you need help with anything else please ask in #dev-help or contact Stripe Support: https://support.stripe.com/contact