#captions_75309_62523
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. 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.
- captions_75309_62523, 1 hour ago, 44 messages
- captions-subs-addons, 6 days ago, 18 messages
- captions_75309_62523, 6 days ago, 7 messages
Hello! You can listen for the other Checkout Event types listed here: https://docs.stripe.com/api/events/types#event_types-checkout.session.async_payment_failed
That's a link to the first one on the list, but there are four total.
thank you for the link! Can you clarify the difference between session.completed and session.async_payment_succeeeded
Yeah, there's more information about those here: https://docs.stripe.com/payments/checkout/fulfill-orders#delayed-notification
thank you!
Happy to help!
Could you clarify my understanding of the async payment events? it sounds like they deal with "delayed payment methods" which I don't believe we have set up.
What would handle the case of a user trying to check out but not having their payment go through? We do not have any of the payment methods listed in the link you sent: https://docs.stripe.com/payments/checkout/fulfill-orders#delayed-notification
If you don't have any of those payment methods set up you won't get these events.
The async events are for when payment isn't immediate, which is mostly with bank transfers that take a few days.
Ok, so for my use case I'd only be concerned with checkout.session.completed vs .expired?
For example, if someone pays you with an ACH bank transfer, the movement of the funds actually takes several business days, so you aren't paid immediately.
Yeah, if you don't support the async payment methods, you don't need to worry about the async events.
How would I track the case where a user entered an invalid payment method?
We don't provide Events or anything for that. If a customer enters an invalid payment method Checkout will display an error in the UI and they'll be encouraged to provide a valid one.
ok, ty for that clarification!
One more question: we have implemented a per-seat payment plan where a user can adjust the quantity of the product purchased on the subscription. A purchase of an additional "seat" uses the customer portal instead of the checkout. How would I track these upgrade/downgrade purchases/events?
You can use the Subscription-related Events listed here: https://docs.stripe.com/billing/subscriptions/overview#subscription-events
The customer.subscription.updated Event in particular will fire on quantity changes, for example.
Great! If I am using customer.subscription.updated to track customer changes, how would I determine the updates that were made to the subscription?
The *.updated Events have a previous_attributes property so you can see what changed: https://docs.stripe.com/api/events/object#event_object-data-previous_attributes
oh i see, that's perfect. ty!
No problem!