#Simon_WS-express-apple-pay
1 messages · Page 1 of 1 (latest)
Hey, sure that's possible
I guess it's entirely dependent on your integration. But you'd just have a single button on the product page that creates the PI and invokes the Apple Pay UI
How would I then be able to obtain what shipping/address details the customer selected or input via Apple Pay to link to the new order in the integration? Our current workflow includes the final callback from Stripe to confirm payment ststus (eg completed) but I am not sure that this includes all of the address details
in addition to this - would it be recommended to migrate from Card Elements to Payment Elements (https://stripe.com/docs/payments/payment-element/migration), or would this not be necessary to support Apple Pay Express Checkout via Payment Request (https://stripe.com/docs/stripe-js/elements/payment-request-button)
That part of the integration would be exactly the same: https://stripe.com/docs/stripe-js/elements/payment-request-button?html-or-react=html#html-js-collecting-shipping-info
It's not necessary, but it would simplify your integration (as the Payment Element handles Apple Pay for you)
but with the additional "Collect Shipping Information" option?
Thanks ynnoj - last question about Card Elements vs Payment Elements...
Looking at https://stripe.com/docs/payments/payment-card-element-comparison it would be beneficial for us to migrate to use Payment Elements - however, in the Features Table it is flagged that "Finalize payments on the server" (https://stripe.com/docs/payments/accept-a-payment-synchronously) is not supported in Payment Elements - I am not 100% sure I undertand what this feature is and if we are using this, but suspect that we are! - We currently have a callback endpoint for the Payment Intent results which includes details such as whether the payment was processed - would this still occur with Payment Elements or would we need to look at setting up and using Stripe Webhooks instead?
Can you share a Payment Intent ID? I can see to see if you're using synchronous confirmation
Nope, you're doing client-side confirmation: https://dashboard.stripe.com/logs/req_lHF2piiJVxzyFY
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
The confirmation_method: 'manual' parameter would be passed in that API call otherwise
Sorry, what do you mean by "nope" in this context?
no, as in we are not using "Finalize payments on the server" (synchronous payments)
Yep, you're not using server-side confirmation
Thanks for confirming and for your help on this - so, in theory we should be able to move to Payment Elements from Card Elements without too much impact
Yes, although you may need to reconfigure your flow a little as the Payment Element requires a client_secret from the PI for initialisation. See: https://stripe.com/docs/payments/payment-element/migration
thanks
Np!