#discodanne_unexpected
fast mulchBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1319622225372119132
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
calm grotto
hi there!
how are you accepting payments? Checkout Session, Payment Element, something else?
neon prism
Checkout Session
I just want to know in which cases where we a customer name is not collected. If its expected to not have customername for all customer we can find a workaround. I just think its hard to test an recreate the scenarios in this case.
calm grotto
can you share a PaymentIntent ID (or Checkout Session ID) where you didn't get a customer name?
neon prism
cs_live_b1Z0tetpfbJULP8KvOeVC9TzvIa4qIAuTebAGeFik6GzGtKgCaALIhztAT
calm grotto
I confirm that I don't see an name for that Checkout Session that's using Apple Pay.
and no there are no options to force getting a customer name when creating the Checkout Session.
neon prism
Here is another exmplae cs_live_b1XQeWKrg6fgtERhATNJPYcl11wuD1PMBE77oNzW3zlIHk7lAvGlWv1joY
Looks like its also apple pay.
Is this expected beahaviour for apple pay to not provide you with a customer name?
Would billing_address_collection help us to collect the name?
calm grotto
Is this expected beahaviour for apple pay to not provide you with a customer name?
not sure, will look into this