#emd
devout merlin
thick merlin
Hi, can you share the request id where this is occurring and another id for when it works? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
fair perch
ok here's a subscription/checkout session: evt_1MofwQDyl4lnF0w3SMfEVg18
and here's a setup one that didn't work: evt_1Mock1Dyl4lnF0w3oGLV1A1a
@thick merlin
here's the request for the lst one: req_FOu4cYrwcnWpgL
finding the request for the first one is too hard, but it's similar (except subscription instead of setup)
thick merlin
Thank you, give me some time please to review these ids please.
I was under the impression that the billing address collected in Checkout, https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-billing_address_collection does not automatically gets saved to the customer's billing address. You'd need to update the customer, https://stripe.com/docs/api/customers/update#update_customer-address's address explicitly was my understanding. Let me test this on my end.
Yeah, that looks accurate. There is a parameter that you can specify to save the billing address: https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-customer_update-address
Describes whether Checkout saves the billing address onto customer.address
Can you try this? The Subscription mode customer has many events so it's hard to detangle here. However, if you could try creating a Checkout Session for both modes with the above parameter, it should now save the address.