#Eli P

1 messages · Page 1 of 1 (latest)

jovial valleyBOT
long fox
#

The PaymentIntent isn't created until the customer submits payment. If your use-case is to confirm payment intents server-side with the customer off-session, I recommend just using the Payment Intents API directly

bold lantern
#

I can’t as I need access to automatic stripe tax

#

Can it be confirmed client side outside the stripe url?

long fox
#

So you want the customer to enter their payment method details in Checkout and then actually process their payment separately server-side?

bold lantern
#

No.. I don’t want to use the actual stripe checkout page at all.. only the checkout api to generate the payment intent with stripe tax and customer will pay the payment intent using the regular payment sheet

long fox
#

Oh ok. That behavior was introduced in the latest API version. I think you can use the previous version (2020-08-27) to get around this behavior

#

Although I haven't tested it out

#

You can try it out in test mode

bold lantern
#

I can but I’m gng to have to update to latest version at some point

#

There’s no way to confirm session client side?

long fox
#

Nope

bold lantern
#

Ahh.. that sucks.. ok.. thanks

long fox
#

No prob. You can specify api version per request though

#

Like your default can be the latest version but you can use an older version on specific requests

bold lantern
#

I think that would be begging for bugs, no?

#

What’s the response that would be sent back? The 2020 version?

long fox
#

Yeah

#

Yeah it's not an ideal flow

#

But it will work

bold lantern
#

And that would be overwritten in my db by any syncing I do under the 2022 version so would prob break easily

#

Thanks anyway