#pseudo-googlepay-issue

1 messages · Page 1 of 1 (latest)

junior orchidBOT
#

Hello! We'll be with you shortly. 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.

long light
#

Hi 👋

Can you share the Payment Intent ID that you are attempting to confirm?

#

Also can you describe the specific steps you are taking to arrive at this state?

lofty wharf
#

Sure thing

#

PaymentIntent: pi_3OKqMLEbpWpbwB0V1NUYkYeq

#

Steps from a user user perspective: select amount, click GooglePay, enter contact info, click continue, error

long light
#

Okay, and from the JavaScript perspective?

#

What functions are being called to confirm this payment intent?

lofty wharf
#

Steps from a code perspective: select amount, create payment intent, click google pay, update payment intent, element.fetchUpdate, continue to google pay prompt

#

paymentRequest?.on('paymentmethod', async (ev: any) => {
const { paymentIntent, error: confirmError } =
await stripe!.confirmCardPayment(
clientSecret,
{ payment_method: ev.paymentMethod.id },
{ handleActions: false }
);

long light
#

So do you upate the payment intent after you return the client_secret to the front-end?

lofty wharf
#

Correct

#

We would be unable to render any of the elements without a valid client secret, correct?

long light
lofty wharf
#

Aha, yes we do that

long light
#

Hmmm... do you have a staging front-end I can test with?

lofty wharf
#

PaymentRequestButtonElement has an onClick handler that updates the PaymentIntent on the server and then calls element.fetchUpdates on a success

#

Yes, stand by

long light
#

In my console I can see Invalid stripe:ublishableKey for current environment. This is coming from pay.js which is Google Pay

lofty wharf
#

Is that something that I can view or is that something specific to your access level?

#

Second question, what does that mean?

long light
#
  1. This was just me visiting the site you shared, no special access required
  2. No idea, it's not a Stripe error. Are you using your test publishable key pk_test_XXXXX?
lofty wharf
#

I don't see that in my browser, nor in my phone debugging console? Interesting

As far as I'm aware I am using the correct test keys

long light
#

The error I am seeing is

Uh oh, something went wrong
Unexpected developer error, please try again later.

#

This is loaded within the GooglePay modal window ( which means it is entirely coming from Google).

#

Where is the error message you shared showing up?

lofty wharf
#

This is interesting because I was fully able to complete a payment with another connect account

long light
#

You mean without the issue?

#

No error anywhere?

lofty wharf
#

Yes

Double checking

#

Yes I was able to fully complete the transaction on another account

junior orchidBOT
lofty wharf
#

Is it perhaps because the payment domain isn't registered correctly?

long light
#

I don't suppose it's possible to see this with un-minified JavaScript?

lofty wharf
#

I apologize but no

#

not within the next couple of hours at least 🙂

wicked oracle
#

pseudo-googlepay-issue

lofty wharf
#

Is there a specific question I could answer?

wicked oracle
#

Not really right now we have no clue what's going on sorry. Next step is to do an extremely simple repro without any minified code or complex update. Like on that account does a simple GooglePay integration work?

lofty wharf
#

Hmm

wicked oracle
#

I also don't get that weird key error my colleague gets so it's likely a red herring

#

Can you share the account id(s) of both accounts the one where it works and the one where it doesn't?

lofty wharf
#

yes

wicked oracle
#

Also is it a Test mode only issue or does it happen in production/Live mode?

lofty wharf
#

Doesn't work: acct_1OCRCZEbpWpbwB0V

Works: acct_1LsyZgJ0cyL6jtyw

lofty wharf
#

Have not promoted this account to full live testing yet due to this issue 😄

#

Got clearance to unbunble the JS, let me see if I can make that happen

wicked oracle
#

Okay so I think it's just a normal edge-case. acct_1LsyZgJ0cyL6jtyw which works is connected to your platform in Test mode only. acct_1OCRCZEbpWpbwB0V that does not work is connected in Live mode only

Google Pay has a weird limitation where you can't do Test mode transactions in Test mode if you only have a Live mode connection

#

So I'm confident it's just "normal" and you got worried because of this

lofty wharf
#

Alright, and whats your extension so i can forward it to the client tomorrow? 😄 (kidding!)

#

Thank you for your help and the deep dive into this

#

Appreciate it, have a good evening

wicked oracle
#

Sure thing! Sorry it can be tricky to debug those and the only way would be to try a real transaction in production which is forbidden by our ToS in theory so that makes it tough 😦

#

Might be worth buying the product for yourself/your client just to quickly confirm Live mode works as expected