timothyshaw

[trail ridge]

Hello! Yep, it's possible to set up Apple Pay for future use, but you should have a 1:1 relationship between a distinct purchase and showing the Apple Pay sheet and having the customer authenticate.

So, for example, if you want to set up Apple Pay for future use and then use it with a single Subscription, that single Subscription counts as a distinct purchase.

And that works fine.

But if you want to set Apple Pay up for future use and then use it for random purchases after that you'll likely see higher numbers of declines if you're not showing the Apple Pay sheet for each one.

[civic sphinx]

our use case is ride share, so it would be payment intents per ride

[trail ridge]

Yeah, you need to show the Apple Pay sheet for every ride and have the customer confirm the payment for each one.

[civic sphinx]

got it. so the "set up for future use" maybe isn't as useful for us. sounds like less of a card on file and more a per-ride payment option .

the other issue would be if a user incurs incidental charges. say, a cleaning fee if something happens. we may not be able to successfully collect that in the background if they had only used apple pay

[trail ridge]

For a ride share situation Apple Pay should not be stored as a card on file, you should show the Apple Pay sheet each time.

I think the way most people handle the incidentals is to place a hold on the card for an estimated amount with extra padding, then capture what's actually required at the end.