So perhaps you could give me an idea of the performance difference between “guest” and “customer” records.
If a customer object is being created for each guest user, that results in a minimum of one additional API request per order that’s processed. If you have a high volume site, that could add up to many additional requests. Stripe’s API is efficient, so that’s not a serious concern but it’s worth considering.
Ideally, when a purchase is made on our site, it would do a customer look-up in Stripe and if it found a customer with the exact same name and e-mail address, then it would associate the new purchase with that customer record
That would require an API request to Stripe which increases the checkout process time. There is also the concern of associating a Stripe customer ID based on parameters entered by a customer and how that could be abused by a bad actor.
We’re taking a look at adding a new option where the merchant can configure if they want to use “guests” or have the plugin create a customer ID during checkout.
Kind Regards