#bluetable-checkout-customer

1 messages · Page 1 of 1 (latest)

little mangoBOT
spark needle
#

@dire zodiac it depends on your configuration mostly

#

bluetable-checkout-customer

#

@dire zodiac can you give me a bit more context? You talk about "checkout session" which is for our Checkout product, but you also talk about PaymentElement which is when you do not use Checkout

dire zodiac
#

Sorry for the delay, yes one sec!

#

It's all pretty new to me, so it's super likely I'm describing things wrong. I'm definitely using PaymentElement. I've been trying to figure out webhooks, which I think I set up for checkout.session.complete and payment.intent.succeeeded(etc.)

#

My understanding is that I need to use webhooks to handle any post-payment events?

spark needle
#

All good let's take a step back: Are you writing code on your own website using PaymentIntent and PaymentElement OR are you using our Checkout product

#

they are completely unrelated/separate so knowing which one you use changes everything

dire zodiac
#

I'm coding a React app using the PaymentElement and PaymentIntent!

spark needle
#

Okay, so you are not using Checkout, creating a Checkout Session and you should never listen for checkout.session.completed in that case

#

So now, if you use PaymentElement, you fully control the integration in that case. We (Stripe) don't create anything for you. If you want to create a Customer and save card details for future payments it's totally possible but this is something you fully control. PaymentElement solely focuses on collecting payment method details for a payment

dire zodiac
#

Okay this is great info. So to go about creating a customer object, do I need to create and store that data in my own database, or can I use Stripe customer create and store it in my dashboard? that article might totally have the answer for this

spark needle
dire zodiac
#

Really awesome, thank you so much!