#yhfs_best-practices

1 messages · Page 1 of 1 (latest)

hollow wharfBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1219956868672393248

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

severe cedarBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

distant ember
#

👋 happy to help

#

sorry I'm thinking this through

#

basically if you want to support Apple Pay there is going to be a tradeoff somewhere

#

Checkout Sessions can't only have wallets, so in all cases both Checkout Sessions (with or without s_f_u) would have cards as a payment option

severe cedarBOT
short fjord
#

I understand that I have to choose s_f_u or Applepay.

#

thank you for your great support!

distant ember
#

you have a couple of options here

#

you can either move to Express Checkout Element for the Apple Pay

#

and then you can also have setup_future_usage for Apple Pay

#

but you will lose the benefits of CheckoutSessions (tax, promotion codes, invoices etc.)

#

and you would have to maintain 2 different webhook flows

short fjord
#

sorry. That was a confusing question.
I would like to allow users to choose between two payment methods: s_f_u card payment and Apple Pay (not necessarily s_f_u).

worn latch
#

don't see how that's possible really unfortunately since they're bundled together as part of the card payment_method_type. It's not granular enough without moving to a more complex integration flow as mentioned