#saahil_applepay-address
wild sonnetBOT
đ 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/1489387808685686814
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
safe bronze
For context, I'd like to collect the least possible information from both apple and google pay at checkout time on web for a recurring subscription via Payment Element.
supple basin
@safe bronze someone asked about exactly that yesterday so you're in luck. You need to pass address: 'if_required' instead of never for the other sub-options
See https://docs.stripe.com/js/elements_object/create_payment_element#payment_element_create-options-fields-billingDetails-address
saahil_applepay-address
safe bronze
Other sub options as in the address sub options or the name, phone, email options?
supple basin
hum sorry I think I missed something somewhere
billingDetails: {
name: 'never',
phone: 'never',
email: 'never',
address: 'if_required',
}
}``` I tried this yesterday and it works fine for me(and for the other dev who was asking about it)
Are you saying you get an error with that exact code? Because that doesn't match what I was seeing yesterday when I tested
safe bronze
I read that thread prior to starting this one, and so the above fields are what I tried - sorry I should've mentioned that.
supple basin
yeah I think you should remove name/phone/email really
safe bronze
options={{
layout: 'tabs',
terms: { card: 'never' },
fields: {
billingDetails: {
name: 'never',
phone: 'never',
email: 'never',
address: 'if_required',
}
}
}}
Is what I have currently
supple basin
Like let us collect what we need when it's required, just pass address: 'if_required'
supple basin
likely all of those by default
the alternative is use ExpressCheckoutElement for ApplePay/GooglePay separately from PaymentElement so you can configure each differently
safe bronze
In an ideal world I want none of these fields to be collected
Gotcha, I can look into that if it gets me closer to the end goal
So we'd then have both a PaymentElement and ExpressCheckoutElement simultaneously
supple basin
I think it would work in that case if you separate the two
I still don't like our never/if_required implementation either, it's just too crude when it should be "don't ask or give me anything that isn't required"
safe bronze
100% agree, I'd love the "don't ask or give me anything that isn't required" variant!
supple basin
The problem is basically some payment methods require this info and if you disable it you have to collect it yourself or those won't work. So when you disable those you have to give us a value to confirm you collect it
So in a way you likely should remove all the options if you are fine with us collecting what we believe we need. Collecting postal code/country is quite important for card payments in US/CA/UK for example
safe bronze
The broader context is that we collect zip code for card payments and we want to maintain parity while providing more payment methods.
Yeah exactly
supple basin
PaymentElement collects postal code for you though so why not just let us collect what we need instead of forcing those never?
safe bronze
Yeah we're trying to provide as close to anonymous sign up/purchase as possible.
I don't have a way to redact after the fact either so just trying to rule out all options before I say we can/can't do wallet based payment methods.
I'd settle for nothing but address if thats workable.
supple basin
yeah ExpressCheckoutElement should work for you I think in that case and not collect address so maybe try that? I think it'll always share email and such
You could use https://docs.stripe.com/privacy/redaction afterwards but you still have PII access even if temporary
But also it feels to me that anyone "privacy conscious" would never use one of those wallets. But that might be more my personal position
safe bronze
Yeah that's a fair take and I share that position as well. I just want to limit data collection where I can even if this caters less to the privacy conscious audience.
supple basin
yep that's reasonable. I have to run soon but we'll be back on Monday US time if you have follow up questions!