#bruuh00
1 messages · Page 1 of 1 (latest)
"id": "cs_test_a1IVmiOF1e813PlaOMNVs8s2dVuRxexA2ME6pg8zfcNlovLi302epcPRo9",
"object": "checkout.session",
The most interesting part is that shipping info is there but it's not saved on the customer itself
this is on the checkout.session event from webhook
On the invoice event ("id": "in_1OJaxmIVliRP2SHyizIQvgyU",
"object": "invoice",)
I do not have any shipping set. This is the event that happened before checkout.session event. (
invoice.payment_succeeded)
and I think I should have had the same customer_shipping as the checkout.session
payload used in the code.
I see the address on the Customer object in the Checkout Session you shared.
yes
look on the customer itself
do you still see it?
I don't/
even if shipping collection is required.
Do you see the shipping_details on the Checkout Session object? https://stripe.com/docs/api/checkout/sessions/object#checkout_session_object-shipping_details-address
yes
but in the end the shipping address does not get saved automatically on my customer object
as it was before
has this been deprecated, or?
before, when I was setting a shipping address:
- if customer in stripe would not have any -> the address would have been saved directly onc ustomer
- if customer had one -> you could see that in any other checkout sessions as pre-filled and user could just update it.
- then I can see all of that in the customer profile session, if i instantiate one - any user can go in their dashboard, see their subscriptions, manage them, change shipping info, etc.
- I don't think Stripe ever pre-fill anything on the Checkout Sessions.
I am not aware of anything changing in this API.
that's how i remember, sorry if I am mistaken
ok, but again - should the shipping address be saved on the customer object
?
once there is an order/checkout instance being succesfully done, with shipping info