danhowardmws

[sonic lion]

👋 happy to help

but how should we supply the name when it is a 'guest' checkout and we don't have a logged in user?
if you don't require a customer name then you 'd have to account for that in the fraud risk

[lunar thicket]

We do collect the customer's name during our checkout process (even for guest checkout). But I can't see how to supply it to Stripe.

[sonic lion]

you describe the way in your question

[lunar thicket]

You mean we have to create a Stripe Customer? (https://stripe.com/docs/api/customers/create)

But then if the same person uses our shop again and does another 'guest' checkout then won't we have a duplicate customer in Stripe?

[lunar thicket]

Can't we just set a 'customer name' for the one single transaction? (without linking it to a separate Customer object)?

[severe fable]

Hey! Taking over for my colleague. Let me catch up.

[severe fable]

No you need to create a Customer object using the API reference you shared, and then create a PaymentIntent with that customer Id.

[lunar thicket]

OK, so a new Customer for every guest checkout?

[severe fable]

Not necessary, you can keep track of your customers (by email or something else) and use existing Stripe Customer object

[lunar thicket]

1. Search for existing Customer by email
2. If we have an existing Customer, check the name matches, update it if it doesn't.
3. If we don't have an existing Customer, create one.
4. Finally create the PaymentIntent

[severe fable]

Yes that could a good flow

[lunar thicket]

Hmm, it doesn't seem very good to me. Just having an optional customer_name field on the PaymentIntent would be better I think than having those 4 steps. But if that is what we have to do then that is what we will do.

Thanks for your help.