#beltranc

1 messages · Page 1 of 1 (latest)

sinful iglooBOT
fickle egret
#

Hi there!

coarse ingot
#

Hi 😀

fickle egret
#

Where/when exactly do you see this error? Can you share a PaymentIntent ID (pi_xxx) where you saw this?

coarse ingot
#

It happens for every payment intent I try, do you want me to share a prod payment intent?

#

There is no error on the payment intent itself as it says "Incomplete"

fickle egret
#

I need to see an example, either test mode or live mode.

coarse ingot
#

pi_3NYGQNFLk5Br0gSU0V1FYnic

fickle egret
#

Sorry for the delay

#

This PaymentIntent has status: "requires_payment_method"

#

So it's missing a step in teh integration

#

There was an error authenticating your request, please try again.
Where/when exactly do you see this error?

coarse ingot
#

I see it on the frontend, i'm using the confirmPlatformPayPayment Stripe function with the PlatformPay component

#

it's built-in and automatically generated by either Google Pay or Stripe as I have no way to catch the error

haughty valve
#

Hi! I'm taking over from my colleague. Please, give me a moment to catch up.

#

Could you please share a snippet of code that's calling the failing method.

coarse ingot
#

Hi, thanks

#

const { error } = await confirmPlatformPayPayment(clientSecret, { googlePay: { testEnv: false, merchantName: "My Merchant", merchantCountryCode: "ES", currencyCode: "EUR", billingAddressConfig: { format: PlatformPay.BillingAddressFormat.Full, isPhoneNumberRequired: false, isRequired: false, }, }, });

#

The error shows as an alert, and the function doesn't resolve until I click "Cancel" on the alert

haughty valve
#

I see. Could you also please make a screen recording of the issue?

sinful iglooBOT
coarse ingot
#

As you can see in the video, the first alert is caused by either Google Pay or Stripe, while the alert in Spanish is handled by my app since the "Cancel" action is treated as an error by the confirmPlatformPayPayment function

ebon igloo
#

seems strange! unfortuantely we don't know much about debugging this. I'd try reaching out to Google, this seems like some problem in the process for go live on their side, which we know very little about

#

might also be an issue in how your apk is signed or something

coarse ingot
#

If it's an error on Google's side, wouldn't Stripe handle it since it's the Gateway provider?

ebon igloo
#

that logic doesn't make sense to me (we process the payment token that is generated from the Google Pay wallet, and it's the Google integration that creates it), but ok.

#

the only resources I and my team have is to point you towards Google's going live documentation, as usually problems like this are down to not having done that, or issues in that process. We have almost no other experience here, and we don't actually know what it is that Google's process looks like from your side or what they/you do. I'd go back and check with them and maybe try the process again and double check things like your app is signed with the keys from the corect Play account, not sure.

coarse ingot
#

the alert itself is presented by Stripe's component though, right?

ebon igloo
#

not sure what your point is

coarse ingot
#

That if Stripe is presenting the alert it would mean that Stripe is handling the underlying Google Pay error in that form

ebon igloo
#

I'm telling you all that we know about how to fix this error unfortunately, I know it's not a lot and not too helpful but it's all I have.