#arabtoaster

1 messages · Page 1 of 1 (latest)

delicate wraithBOT
smoky plinth
#

Hi, taking a look here

split ore
#

thanks 🙂

smoky plinth
split ore
#

And if we needed to charge for incidentals in the future? would that be possible since we won't be doing that in the user interface?

smoky plinth
#

I'm unsure what this question means, can you help clarify?

split ore
#

yes, so sometimes need to charge for incidentals like damage and with CCs we charge the card on file directly when these occur through our backend and not through the app. Would we be able to do the same with apple pay?

#

I'm not sure if this changes anything that this is for a mobile app experience and not web

smoky plinth
split ore
#

Right but this is for apple pay on a mobile app. It's unclear that we can store apple pay the same was as Credit Cards and charge it for future use the same way

smoky plinth
#

Apple Pay and is essentially a card payment, so it would work the same way.

split ore
#

so would I not need to present the apple pay modal again for each charge or change to payment?

#

we're trying to get clarification on these specific use cases because we got different answers in previous attempts of asking

#

if i set up apple pay for future use would the 3 scenarios I asked about all be covered or would i need to present the sheet again?

smoky plinth
#

If you set it up for future payments, I do not believe so : https://stripe.com/docs/payments/payment-methods/integration-options#support-wallets and https://stripe.com/docs/payments/save-during-payment?platform=web#web-create-payment-intent.

Specifically, the following. If they can't be saved during payments, it won't display.

Some payment methods can’t be saved during payments. You can still enable these payment methods for other use cases, they just won’t be displayed to customers as an option when setting up future payments.

split ore
#

Okay, thanks. We were told if we used apple pay in this way we would end up with declines from apple pay because we aren't presenting the sheet as well as changing the price after the sheet was presented. But if we were to show the sheet at the beginning of these transactions, there wouldn't be an issue is that correct?

smoky plinth
#

That is my understanding. Like I mentioned earlier, if you update the amount, you'd need to display in the wallet modal

split ore
#

the documentation you provided around presenting it again was for web. is there something different I would need to do for an iOS app? I don't see mention of it in the documentation

smoky plinth
split ore
#

Right, there's no mention of a function to fetch updates to a payment like what you provided for web

smoky plinth
#

Ah, let me confirm with a teammate. I'm not as comfortable with iOS.

#

Thank you for your patience here.

#

I was able to confirm and it looks like it doesn't work at all for the Apple Pay modal. You cannot update it. Even for the Payment Sheet you'll need to destroy the Payment Sheet and re-create it. @split ore