#daxen_best-practices
1 messages · Page 1 of 1 (latest)
👋 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/1441398568119173160
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
👋 happy to help
please give me a moment and I will be with you shortly
no the better approach here is https://docs.stripe.com/payments/place-a-hold-on-a-payment-method
because you don't just want to save the payment method but you also want to make sure that the customer can pay the ride
But does this approach require showing the user a maximun amount upfront?
Also, is this hold/authorization flow using Apple Pay and Google Pay fully supported in the native Stripe SDKs for iOS and Android?
I wouldn't say max, but yes
yes
hmmm, so, whats the typical way used in this type of apps when choosing the amount to authorize for the hold
and if i need to present an amount to the user during this authorization, should this be a fare estimate?. Also, I assume that if the authorized amount ends up being lower than the final ride price, I won’t be able to capture more than what was originally authorized
I have seen this approach in Cabify motorcycles, idk if this is the same that you told me to do... but they arent showing any amount
this is more like what you described
you can either cancel the original PI and create a new one, or you can use he incremental authorization if you fit the requirements
So, they are using a SetupIntent, right?
sure let me know if you need any more help