#Michał Wieluński-checkout-webhook

1 messages · Page 1 of 1 (latest)

indigo lagoon
#

Hello 👋
It is unusual if the checkout session was completed after it expired. Also unusual to receive the expiration webhook after it was completed.
Do you have event IDs I can look into?

elder skiff
#

expired: evt_1LZgLDA20eXMxhCTLKeDM0oF

#

completed: evt_1LZgNBA20eXMxhCTcf4Gadrr

indigo lagoon
#

ah okay I see what happened here

  • Session was created
  • Customer used BLIK payment method to pay which required additional action to complete the payment
  • Before that the customer completed the auth, checkout session expired which triggered checkout.session.expired
  • However, checkout expiration may not cancel the payment intent that's already created and is in requires_action state
  • So when customer completed the additional actions to use BLIK, the payment succeeded which then triggered checkout.session.completed
elder skiff
#

So this is expected and we should not treat checkout.session.expired as a final state? I never saw any mention of that in the documentation. I might have missed it, your documentation is huge. Thanks, that should be an easy fix in our application.

gray brook
#

confirming one thing, be a few mins