#mymo-400-error

1 messages · Page 1 of 1 (latest)

granite vector
#

Hi 👋 is there any more information that you can provide? There isn't enough here for us to infer anything.

gritty summit
#

Hi, I'll try to add as much info as I can: we are building a gateway payment for our woocommerce (wp) platform. We were working on it last week and saw this error starting to appear in the console on every load. We didn't have this issue before, so we rolled back our modifications, but the error is still appearing. Our keys (test) are good and nothing really changed on our side, since we rolled back.

#

I saw on another forum that someone else's having the same error since the end of last week

narrow jungle
#

To be clear this is you writing directly to the Stripe API to make this gateway correct?

gritty summit
#

Yes!

narrow jungle
#

Can you send us a request id (req_123) or event ID (evt_123) for a time you saw this?

#

Awesome!

gritty summit
#

Here's two request id:
req_UMdLCIFOrhag9G
req_6WusfAKQ8u70H0

narrow jungle
#

I see 200s sent back to you on both of those.

#

What is the exact message you see in the console?

gritty summit
narrow jungle
#

And which call is this for?

#

And how are you making it?

gritty summit
#

We are calling those (I removed the account id for the screenshots)

narrow jungle
#

Account id is safe to post here but thanks.

gritty summit
#

good to know ,thanks!

narrow jungle
#

So you are getting that on the PaymentIntent create method?

gritty summit
#

both are loading at the same time, the customer then the paymentintent

#

And we are getting the error even if we remove one or the other

narrow jungle
#

And that breakpoint happens on either of them?

gritty summit
#

yes

narrow jungle
#

And it will specifically point to those calls?

gritty summit
#

I'm not sure I understand the question, but both are called on page load

narrow jungle
#

If you take both of them out, do you still get the 400?

#

I misunderstood your screenshot. I am trying to narrow down what exactly the 400 is from. It looks like it is not either of those calls.

narrow jungle
#

Is that 400 error blocking you? After looking in to this more I found that this 400 may not effect your functionality

gritty summit
#

Sorry, I can't test at the moment. Will do soon.
I don't think the error is affecting anything, but would love to not see it anymore hahah

pastel fox
#

I've flagged it internally

#

it shouldn't impact your integration, those requests are telemetry but we'll get it fixed

gritty summit
#

great, thanks so much!!

pastel fox
#

update - someone is working on a fix