timothyshaw

[midnight temple]

Hi 👋 let's do one question at a time. What's up?

[errant nest]

We are looking to implement one or both of these features, to try and collect payment from our users in a single payment intent rather than multiple. Use case is ride share service, so we authorize for the ride fare up front, but they may incur additional fees during the ride. We are also interested in increasing the amount for the tip the user may leave for the driver.

First question is whether there's any information on increased decline rates when requesting these on a payment intent? For example if we started requesting the ability to overcapture and use incremental authorization on all our payments, would that seem odd to the card networks, or seems like a legitimate use case?

basically, whether there is any known connection between requesting these payment extensions and the success rate of authorizing / capturing the payment.

[midnight temple]

We don't have a lot of context on auth rates. We're web developers that are here to answer developer integration questions. Our support folks might be a better place to ask this type of question: https://support.stripe.com/contact

[errant nest]

got it. second question might be in the same vein then 🤔

We have a large % of users paying with Apple Pay. It seems to me that Apple Pay should generally work with these payment extension features, but wanted to see if there are any known issues with it.

And also on Apple Pay, was hoping to confirm whether these features can generally be captured successfully off of a single Apple Pay token (i.e. user confirms in apple pay sheet once, then can continue using incremental auth multiple times, or attempt overcapture)

[midnight temple]

I believe those are only available for regular card payments, as opposed to wallet payments

[errant nest]

i see. i couldn't find anywhere in the documentation that specifies apple pay wouldn't work. also on Apple's side they seem to support these flows (authorize & then capture higher amount)

[midnight temple]

I could be wrong. Apologies for the vagueness. The server is really busy and this could reasonably be solved by testing. Do you have a test integration set up?

[errant nest]

yes, no problem. we can continue poking at it on our side. thanks for your time.