chhotisherpa_best-practices

[fast river]

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

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

[spiral whale]

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

• chhotisherpa_webhooks, 5 days ago, 44 messages

[glad fulcrum]

Not if you don't want to accept payment methods that require customer to leave the app to authenticate

see this section: https://docs.stripe.com/payments/accept-a-payment?platform=react-native&mobile-ui=payment-sheet#react-native-set-up-return-url

[fading topaz]

What should I do about the console warning I receive when making a payment through my app?

[fallow juniper]

Have you tried providing a return URL to your initiPaymentSheet call?

Ah, nevermind just read the rest of the thread. I think it is fine to populate that variable with the URL of some landing page of yours if you want to get rid of the warning.

The thing that generates the warning doesn't have the context that you don't actually use the redirect