#joe-elements-paylater

1 messages · Page 1 of 1 (latest)

fallen rampart
#

Hey @slate pawn! Sorry but I don't understand what you mean. You're using multiple words that are usually in conflicts like element Fields, checkout, etc

Let's take a step back: Do you use Stripe Checkout?

slate pawn
#

I do.

#

I create Stripe CC fields on checkout via JS e..g var cardNumber = elements.create('cardNumber');

fallen rampart
#

Cool, so you use the CardElement with split fields

#

now move away from that and use the PaymentElement

#

@weak cradle does that make sense?

#

ugh sorry bad auto-complete

#

@slate pawn does that make sense?

slate pawn
#

It does. I found docs and trying it out

fallen rampart
#

Awesome

slate pawn
#

So I will need to create PaymentIntent for every anon user on checkout?

fallen rampart
#

I wasn't sure with pay later you wanted but PaymentElement lets you accept all of them

#

And yes

wet frost
#

As a User: PaymentIntent is a cost-free state machine to track the process of a payment. Unused PaymentIntent cost you nothing, so creating "extra" ones in anticipation of an anon user won't harm anything. Stripe's fees don't happen until a payment is actually taken, at the end of the PaymentIntent process.