#thomross5
1 messages · Page 1 of 1 (latest)
Good question. Looking in to this and will get back to you
Thank you if you need additional information please let me know I've a case that prove it
yes, it uses client side confirmation. You need to build the integration such that you supply a PaymentIntent client_secret when the component loads which the SDK will use to complete the payment , I don't believe you can send the PaymentMethod to the backend for server-side payment(that flow is more of a niche and requires some betas on the web)
great thanks, actually we are doing the same process that you mentioned but for a Subscription. We use a backend endpoint to create the Subscription and the front-end (client-side) uses the ApplePay component to perform the purchase. Do you say that is more secure to make the purchase on the client side?
it's not really about security, it's just that it's how our integrations work, it's more compatible with a wider array of payment methods and makes things like retrying the payment on failure easier
if you're using a Subscription you would use latest_invoice.payment_intent.client_secret and pass that to the frontend like the RN app, when confirmed that pays the Invoice and activates the subscription