#Samsara
1 messages ยท Page 1 of 1 (latest)
Hello ๐
I think my colleague and I are both confused by why you'd want to run a test on live mode connect account?
The previous thread is quite long for me to go back and read everything, can you give me a short summary?
Sure. So as an apple pay requirement for testing, we have to use a live mode account to test. A test mode account won't work.
But for google pay, a test mode connect account is required for payments to go through and not run into an "unexpected developer error" when trying to finalize payment
Which means, that just for testing in local/dev, I had to write custom code on my backend for when I create the client secret, and on the frontend I have to detect the browser/environment to determine which account to use. So there's a lot of extra code I'd like to eliminate since this is only necessary for testing
Ah I see. AFAIK, I don't think we have any plans to alter these flows as such.
I see. Is there any way for me to request a change as part of customer feedback or anything? It'd be hard to test right now, but when I was using the Payment Request Button Element before I was able to use a live mode connect account (in test mode) to test google pay payments. Not sure if the requirements changed or if it was based on the component I was using
Right now I have a working solution but it's not ideal
Sure thing! You can submit a feature request via support form
https://support.stripe.com/?contact=true
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
Awesome! Thanks Hanzo
NP! ๐ Good luck