#anone-payments-dotnet

1 messages · Page 1 of 1 (latest)

inner swiftBOT
cedar bluff
rare crown
#

Hi there 👋 did you have a specific question about the error? It's expected for you to run into, as upgrading the version of the stripe-dotnet library you're using changing the API version that you're using. Version 43.0.0 of that library updated the API version that the library is pinned to, to be 2023-10-16
https://github.com/stripe/stripe-dotnet/releases/tag/v43.0.0

Which means you're now using an API version that is requiring you to provide a return_url, as it's after version 2023-08-16 where that change was introduced:
https://stripe.com/docs/upgrades#2023-08-16

cedar bluff
#

What's this url is for? The current flow we are using with stripe element does not do any redirection

rare crown
#

It's to support the change to Dynamic Payment Methods, where Payment Method support can be determined dynamically based on details about the payment and customer location. If you're not using any redirect payment methods, did the advice in the last half of the error message, about how to not accept redirect-based payment methods, help you avoid encountering the error? Or are you continuing to encounter the error after implementing that suggestion?

cedar bluff
#

I now receive this error "You may only specify one of these parameters: automatic_payment_methods, confirmation_method."

rare crown
#

Well that's frustrating, can you share the IDs (req_) of those two requests?

cedar bluff
#

req_eFhnngIAIBCu6V

#

req_RvO4NEC2W5lcVL

#

req_amzAvep2fxpU7Q

rare crown
#

Thank you, taking a closer look!

cedar bluff
#

Thanks!

rare crown
inner swiftBOT
grizzled wing
#

anone-payments-donet