battbot_api | Stripe Developers | Page 1

delicate spruceBOT Apr 9, 2024, 2:14 PM

#

👋 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/1227260246611984527

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

late forumBOT Apr 9, 2024, 2:18 PM

#

celest hazel Apr 9, 2024, 2:19 PM

#

hi

shell zephyr Apr 9, 2024, 2:24 PM

#

For Android this should largely be handled for you, but for iOS you do need to configure return url handling: https://docs.stripe.com/payments/accept-a-payment?platform=ios&mobile-ui=payment-element#ios-set-up-return-url

celest hazel Apr 9, 2024, 2:25 PM

#

So it's not clear to me from the documentation what the purpose of this return_url is. I used to encounter this return_url when the payment card required a 3ds check, so the return_url was used when the 3ds check passes and it comes back to the url specified as its value. However, we started using Stripe.js and Android/IOS sdk which was handling the 3ds redirects for us. We no longer had to provide our own implementation of this.

shell zephyr Apr 9, 2024, 2:26 PM

#

For Stripe.js on web, 3ds is handled via modal/overlay and typically does not require a redirect

celest hazel Apr 9, 2024, 2:26 PM

#

so this error only comes up when we use the ios sdk?

#

we don't have this problem at all when using our previous version of Stripe

#

this error only started occuring when we tried to upgrade our server side Stripe version. Then how does the older version of Stripe handle this?

#

Because I saw this error occur also from our web app when using the Stripe.js

#

our logs show this error occured not just from ios devices, but also android devices as well

#

what are we expected to pass for android for this parameter?

sharp inlet Apr 9, 2024, 2:37 PM

#

Hi there 👋 jumping in as my teammate needs to step away. return_url began being required with the API version that enables Dynamic Payment Methods by default:
https://docs.stripe.com/upgrades#2023-08-16

It's now required to support non-card Payment Methods that may require a redirect to a third-party site to complete/authorize the transaction.

celest hazel Apr 9, 2024, 2:38 PM

#

what does it mean by non-card payment methods? what about cards which require 3ds checks? doesn't those also require a redirect?

#

also does Apple Pay and Google Pay count among those payment methods?

#

We only process cards + apple pay and google pay. So what would be the recommended solution for us? I don't know if just passing the payment_method_types as ["card"] will restrict apple pay or not

#

we just want the same behaviour as we had previously with the old Stripe api. Was it just always defaulting to ["card"] as the payment_method_type? We can use that as long as cards + cards with 3ds + apple pay are still supported

sharp inlet Apr 9, 2024, 2:46 PM

#

celest hazel what does it mean by non-card payment methods? what about cards which require 3...

Yes, 3DS requires it as well

sharp inlet Apr 9, 2024, 2:46 PM

#

celest hazel also does Apple Pay and Google Pay count among those payment methods?

No wallets don't

celest hazel Apr 9, 2024, 2:47 PM

#

When we were using the old Stripe API, it supported 3ds fine without us passing this parameter. How was it working then?

sharp inlet Apr 9, 2024, 2:47 PM

#

celest hazel We only process cards + apple pay and google pay. So what would be the recommen...

Apple and Google pay are part of card, so you can do that. The API update entry I linked to also contains instructions for bypassing the requirement:

You can bypass the return_url requirement using automatic_payment_methods[allow_redirects]=never, this will automatically filter payment methods that require redirect even if they are enabled in the Dashboard.

celest hazel Apr 9, 2024, 2:48 PM

#

we do want to support 3ds checks on cards though

#

The documentation synthrider gave me earlier for IOS says I need to pass the url for universal link. What about Android and web apps? I've seen this error for requests originating from those sources as well. But I didn't see anything in their respective documentation about what type of URL we need to pass

sharp inlet Apr 9, 2024, 2:53 PM

#

Universal link setup is only required for iOS. Android supports it by default and it isn't needed for web.

#

How are you confirming your intents, serverside or clientside?

celest hazel Apr 9, 2024, 2:53 PM

#

we have auto confirm on

#

we create the payment intents server side though

sharp inlet Apr 9, 2024, 2:54 PM

#

Can you elaborate on what you're referring to by auto confirm?

celest hazel Apr 9, 2024, 2:54 PM

#

we use the java library
paymentIntentParams.setConfirm(true)

#

we set the confirm flag to true when creating the payment intent

sharp inlet Apr 9, 2024, 2:57 PM

#

Gotcha, so you're doing server-side confirmation, and I suspect letting our SDKs handle the 3DS flow for you. In that case, I believe you can omit the return_url if you either:

pass payment_method_options explicitly declaring what payment method types should be supported (rather than using dynamic payment methods).
or
pass automatic_payment_methods[allow_redirects]=never

#

But let me know if those don't work for you

celest hazel Apr 9, 2024, 2:58 PM

#

would automatic_payment_methods[allow_redirects]=never disable 3ds check?

#

because we usually require 3ds check on our payments

sharp inlet Apr 9, 2024, 2:59 PM

#

I don't believe so, I believe I was mistaken when I said those require a return_url

celest hazel Apr 9, 2024, 3:00 PM

#

ok i'll try it out. Thank you for the help!

#battbot_api