#johnm2023_best-practices

1 messages ¡ Page 1 of 1 (latest)

shadow havenBOT
#

👋 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/1389978743841226993

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

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.

frail phoenix
#

Hm we don't have a cardinfo element

#

Are you referring to the card element that only has card number, expiration, and cvc in it?

faint widget
#

Yes

#

in my situation... we are storing the card token for customer billing for restaurants ... but the name on the card might not be the restaurant, but the owner of the restaurant.

#

will the charge be denied if the name does not match the actual name on the card. Do I need to create a customer object for actual card holder

frail phoenix
#

AFAIK name on card doesn't really matter

#

There's plenty of legacy flows that use the card element and don't pass along name

faint widget
#

Ok... then is it best practices then ?

frail phoenix
#

I don't think we have a recommendation on collecting name

#

The Payment Element doesn't collect it by default either

#

It's really up to you

#

I do recommend using the Payment Element if possible