#paddy6534
faint orbitBOT
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.
wind mica
We closed a thread after a period of time. Can you summarize your latest state here?
fickle kite
it was about 24 hours ago, I posted two questions. I came back today, saw answers, but I can't reply
both had replies, but I can't replay back
one was this: Hi everyone, I have added the address element with the payment element so that I can collect organization name and address for a subscription. However, it seems that this is only ever stored against the payment in Stripe and therefore does not get shown on the invoice. The invoice only shows the billing and shipping address stored against the customer. So, does that mean i need to perform an extra step to retrieve the payment name and billiing address for the payment and update the user? Additionally I don't seem to be able to add the tax id collection field using payment and address elements. Does the customer have to have an address before this field will show? or can name address and tax id be collected in one go? Thanks.
the other was this: Hello, I am using the address element and I don't seem to be able to turn validation off for the name field. This is what I have
const options = { mode: 'billing', display: {name: 'organization'}, fields: {name: 'always'}, validation: {name: {required: 'never'}} };
why were the threads closed so quickly?
please can you reopen both of the above threads so I can reply?
wind mica
We would recommend to continue in the latest thread (here). Could you summarize the latest question you would want help with?
wheat ferryBOT
This thread has been archived. If you need help with anything else please ask in #dev-help or contact Stripe Support: https://support.stripe.com/contact
lucid barn
@fickle kite hi there
fickle kite
Hi
lucid barn
@fickle kite what's the question we can help with?
lucid barn
let's pick one of them
there was an answer given in both the threads. What's your followup question? happy to help
fickle kite
I want to reply in thread ideally
why do I not get a chance to reply, they are closed too quickly
my reply would be that the docs do not actually say the validation can only be done on name
name is just the example given
I don't get an error, it's just that my settings are ignored and the field validates anyway
lucid barn
can you clarify what exactly you are referring to by 'validation' and the behaviour you're trying to avoid or to add? My understanding is that only the phone number can be marked as optional via that field and the rest of the inputs are required
fickle kite
const options = { mode: 'billing', display: {name: 'organization'}, fields: {name: 'always'}, validation: {name: {required: 'never'}} };
lucid barn
I don't get an error, it's just that my settings are ignored and the field valid...
yep, since name is not supported as something that can be turned off in that object, so we ignore it(I believe if you look at the console, we log about ignored unrecognised params)
fickle kite
where in the docs does it say only phone?
It actually says "By default, the Address Element will enforce preset validation for each field. You can customize the settings by using this option."
lucid barn
can you clarify what exactly you are referring to by 'validation' and the behaviour you're trying to avoid or to add?
I'm a bit lost sorry
lucid barn
It actually says "By default, the Address Element will enforce preset validation...
yeah but only the phone field ;if there were other fields we support customising they'd be in that object and they're not
lucid barn
I want to make name optional
makes sense. I don't think that's possible today.
fickle kite
ok but I think the docs are ambiguous
also maybe you could help with my other question please
I am trying to understand the flow of collecting name and billing address so that it is shown on the invoice
from my understanding the address element associates the name and billing address with the payment rather than the subscription
therefore it doesn't show on the invoice, even though it hs been entered for that purpose (what other purpose is there?
lucid barn
yeah if used in conjunction with the PaymentElement, it adds to the billing_details of the PaymentMethod created
fickle kite
I need to copy this name and address to the customer for it to show on the invoice
lucid barn
for it to appear on the Invocie you need to call the Customer Update API to set address on the Customer object, pulling the vaues from the PaymentMethod
fickle kite
ok fair enough, but the customers name might be different to the billing address name
ie one is their personal name and the other an organisation name
lucid barn
yep, it certainly can, which is why we have these different fields across the different objects
AddressElement+PaymentElement is aimed at collecting the 'billing address' , the address associated with the card being used to pay for example
you can either integrate standalone AddressElement (or your own logic) on a different part of the flow to explicitly collect the customer address(and then you can have a toggle [ ✓ ] to "use as billing" where you then pass the values to defaultValues on the AddressElement on the payment page, for instance) and set that on the Customer object; or you can do the copy I decribed above, with the caveat you mentioned
@fickle kite anything else we can help with?
going to close the thread!
for reference: the way we run Discord(because it's really really busy and this is how we can make it work with our staffing) is that the aim is that you ask a question, we respond in real-time, we have a back-and-forth debugging/clarifying things(exactly like happening above in this thread) and then we close after your issue is resolved. Follow ups can be new independent threads(we have dozens of shift changes a day across timezones and like I said, it's really busy and each person in my team do dozens of threads in a shift, so we can't keep context for everyone, we need to close and move on). It works well usually but I appreciate we don't make the model clear upfront(but that's something we working on). If you need more async help you can also write into https://support.stripe.com/?contact=true for email dev support)
lucid barn
great!