#farshidboroomand
worthy valeBOT
Hello! We'll be with you shortly. 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.
- farshidboroomand, 32 minutes ago, 26 messages
buoyant zenith
well if you remove the parameter, as I explained in the other thread:
If you remove it then the card that the customer uses to pay inside Checkout will not be saved to their Customer object in Stripe, and you might be relying on that behaviour.
if your "pay half later" code is based on the idea of charging that saved card, then yes, not saving the card would break it
worthy folio
then is there an alternative way to solve that ?
buoyant zenith
solve what?
worthy folio
This is the issue actually.
1- the apple pay button is not shown which you said setup_future_usage: "off_session" should be removed.
2- If I remove this then the users are not able to pay half and half later.
my question is: is there a way to keep this feature ?
buoyant zenith
no
like that is the tradeoff
the options are
- to keep setup_future_usage and accept that Apple Pay is not available(which is something we want to fix in future and there are plans around it) and allow your 'pay half now half later' feature to work
- remove setup_future_usage and have Apple Pay, but your 'pay half now half later' feature won't be possible
I'm aware it's not a great situation, as I say the restriction on Apple Pay not appearing in this mode for Checkout is something we plan to improve in the future
worthy folio
I see, Thank you I will inform my manager, in case of any specific issue I will ask you. sorry to bother you and I appreciate your time. that would be greate if you do not close the thread.
worthy valeBOT