harshilbodara

[eternal haven]

Hello! Do you have the request ID for that error response? It should be in the response headers.

[vast wharf]

request ID means, sorry, I am not getting your point

[eternal haven]

In the dev tools, where you're seeing the error JSON, that's the body of the response. Can you show me the headers of the response?

Under the headers tab there?

[vast wharf]

this is payload

[eternal haven]

Yeah, that request ID there, the one starting with req_, can you paste that here?

[vast wharf]

sure

req_aeyF3AIaOmCdKw

are you here sir?

[eternal haven]

Yep, sorry, things are a bit busy. 🙂

Looking...

[vast wharf]

okay no problem!

[eternal haven]

It looks like something unexpected happened on our end. Are you seeing this every time, or is it intermittent?

[vast wharf]

yes, i see the every time

[eternal haven]

I just realized you shared some sensitive details in your code screenshot, including what looks like an API key. You should roll that key immediately.

And you may want to delete that message/image.

[vast wharf]

I have delete that image

let me know what I need to do?

[eternal haven]

Can you confirm the ephemeral key you're using is correct and matches the mode (test vs. live) and account as the publishable key you're using client-side?

[vast wharf]

okay, let me check

I have checked, and it is everything okay
again I am getting a same error

[eternal haven]

As far as I can tell it's a bug that needs to be investigated further. Have you written in to support about this as the error message instructed?

[vast wharf]

No, I have not added

let me add issue in github!

[eternal haven]

No, I don't think that's the correct approach.