#kev3200-auth-capture

1 messages ยท Page 1 of 1 (latest)

buoyant nexus
#

Hello ๐Ÿ‘‹
looking into it

ember moat
#

We had thought about just over-authing an arbitrary amount above the customer's order's cost, in case of upcharges, but that doesn't seem like a best practice

buoyant nexus
#

Yup that's one way to go about it. An alternative is to cancel the previous authorization and create a new one with a bigger amount.

ember moat
#

I also noticed payment intents could have multiple charges, is it possible to add a charge to a payment intent after capture?

#

And per the two options you mentioned, would the second be considered "best practice" for this kind of situation?

buoyant nexus
#

I also noticed payment intents could have multiple charges, is it possible to add a charge to a payment intent after capture?
I'm not sure about this of the top of my head. I'd suggest trying it out in test mode

And per the two options you mentioned, would the second be considered "best practice" for this kind of situation?
Yup it is

ember moat
#

In order to create a new bigger amount payment intent, would I need to save the charge method info between cancel and creation?

#

We are using Stripe Terminal, which would make this harder to implement

#

as wedo not want to save customer info on kiosk

buoyant nexus
#

Ah I see. Looking

#

Yeah I don't see another way to create a new auth without storing the payment method in some way

#

It will allow you to increase the authorized amount on a confirmed PaymentIntent before you capture it

iron nova
ember moat
#

oohh ok more options to investigate. Thank you for the help. I'll reach back out if I have more questions

ember moat
#

at least not explicitly from our end