#jeffreyb_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/1396712842236792852
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- jeffreyb_best-practices, 2 days ago, 15 messages
Example: req_eIMPBPypX4lQo3
I dont see that as an option in the GPay sheet
Yeap I just saw that Google Pay has specific 3DS cards. We don't have a 3155 equivalent card for Google Pay. If your goal is to test the 3155 flow, I would suggest doing it without Google Pay.
We're just worried that it might cause a bunch of errors when we release in prod where customers set up 3DS with google pay, but fails when we start charging it when off_session is true.
It is definitely possible that a payment method from Google Pay may require 3DS auth for a future payment. So your application needs to be ready to handle this.