#hillct-customer-names
1 messages · Page 1 of 1 (latest)
So one thing to note is that the name of the customer and the name on, say, a card might just be different so updating it may just make the name on the payment method inaccurate
Well, the problem I'm solving for is, we have support personnel who need to lookup purchases for users who may not be loggd in, or don't know heir account credentials. We have the purchaser name as entered at the time of the purchase, in the invoice metadata, but that metadata isn't searchable in the Stripe Dashboard, so I figured we could populate the Nam field in customer record, such hat name would be searchable from the dashboard
@desert island the name on the card itself is separate from the customer's name
For example you could have a customer called John with a card with the name "Mary" on it
I understand that. I'm just trying to come up with the best approach. I have customers authenticating with heir Zoom (video conferencing) accounts, which often has names that don' remotely relate to the person't actual name, making i unsuitable for Stripe Customer Name (for support purposes)
you can safely update customer.name if you receive more info later or they edit it or whatever (and you might even have to)
In our case, we have purchases being made on behalf of a customer (event attendee), by their administrative staff, so there's no telling what they'd enter as the customer name as specifically prompted for...
In any case, thanks for the feedback. Ultimately, I can just prioritize the potential source fields and just hope i get something logical from one of them
the approach you specified above sounds fine IMO, but just keep in mind that if you're generating payments (thus invoices/receipts) with this name, the invoice might not be correct
'correct' in what sense? It's the name the purchaser provided, one way or another
rephrasing: you won't be able to re-issue those. It's a pitfall, it doesn't sound like itll be a problem for you
in hat we can't update the name as it appears on an invoice, once finalized. Yeah. I doubt that'll be an issue
in that...
ok. Thanks. Have a good afternoon (morning?)
Evening.