#whothey

1 messages · Page 1 of 1 (latest)

short helmBOT
plush ginkgo
#

Hi there. One moment

#

I'm not a React Native expert, so I can pull in a colleague if this suggestion doesn't end up working for you, but Apple Pay supports separate auth and capture: https://support.stripe.com/questions/using-authorization-and-capture-with-apple-pay. So, you should be able to create the Payment Intent with 'manual' capture then actually capture the funds server-side after confirmation (once you're ready): https://stripe.com/docs/payments/place-a-hold-on-a-payment-method

Place a hold on a payment method

Separate authorization and capture to create a charge now, but capture funds later.

fast turret
#

Our intention was not to authorize the customer's payment method until the order is successfully created on our end. As I understood the authorization would be still kicked in the client upon confirmApplePay 🤔

#

In summary: we still want to use Apple Pay for some of the orders, but want to create the auth and eventually capture it in the server, rather than authorizing in the client

plush ginkgo
#

Gotcha

#

Let me see if I can pull in someone with more React Native knowledge

uneven jolt