#Samsara
1 messages · Page 1 of 1 (latest)
Hi 👋 can you clarify what limitation you're referring to, I don't recognize it off-hand?
Sure. When we're testing out the google pay integration with the stripe payment element, if we use a live mode connect account when rendering the element, google pay will show up as an option (running ngrok for https), but when we click google pay as option and continue checkout, the modal comes up as normal, and when finalizing the payment within that modal, I get an "unexpected developer error". If I use a test mode created connect account it works. For apple pay to show up and work, I have to be in safari and use a live mode connect account when rendering the payment element
Why are you testing in live mode? That will process real payments and is not considered testing.
Or are you saying it's dependent on how the account was created?
Not testing in live mode. We're testing a live mode created connect account, which is a requirement for apple pay
Do you have a specific example that you can share?
Sure
Well its working as expected, but I can get you a video of trying a live mode account with google pay
This is using a live mode created connect account in test mode
But if we use a test mode created connect account it works. This is a google limitation for testing. So my original question is whether there any plans to change this and allow live mode created connect accounts (in test mode) to work when testing google pay ?
Are there any logged errors in the dev console? Can you share the ID of the Payment Intent that was used for that payment attempt?
I'll run it again, one sec
I do get this DEVELOPER_ERROR in loadPaymentData: Invalid stripe:publishableKey for current environment. Make sure you are using Stripe's test key.
pi_3MYcrWDTwu9XYxBB1NtyaoIu
Still trying to piece together the limitation you're running into.
Are you using one of Google's test cards with this flow for your testing?