#maks-auth-capture

1 messages · Page 1 of 1 (latest)

burnt tulip
#

Hey there, yes you capture on the server, but no you can still confirm client-side to complete the authorization. You don't need the server-side confirmation flow for this.

#

Webhooks are recommended regardless

#

But that mostly depends on how you are triggering the capture.

mossy plaza
#

So the idea is to pre-authorize the card, then do some async thing that can take a couple minutes and if that that async thing is successful, capture the payment

burnt tulip
#

Yep makes sense. So webhooks are recommended to handle reconciliation after capture

mossy plaza
#

Okay, I think I need to better understand the difference between confirm and capture and reconciliation, will have to dive back into docs

burnt tulip
#

Confirm will trigger the bank authorization for the card. Capture will actually complete the charge and move funds into your Stripe Account. Reconciliation is you updating your database and provisioning your product, etc.

#

If you don't set capture_method: manual when you create your PaymentIntent then we both confirm and capture in one step when you call confirmCardPayment

#

However, by setting capture_method: manual this allows you to split these steps up and then capture the charge within 7 days via a request from your server

mossy plaza
#

Oh, okay, got it. So I can still use confirmCardPayment on the client side, which will let me re-collect the CVC for saved cards, but the capture won't trigger until I make an independent capture call with that paymentIntent on the server. So in my case, I'll wait for that async thing to happen on the server, and then call capture.

burnt tulip
#

Yep exactly

mossy plaza
#

Great, this was super helpful, thank you so much.