#_cho

1 messages · Page 1 of 1 (latest)

teal vectorBOT
#

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.

  • _cho, 51 minutes ago, 5 messages
  • _cho, 21 hours ago, 36 messages
  • _cho, 22 hours ago, 8 messages
shut trellis
#

Can you share the request id?

runic depot
#

"req_QyjwQqH7dsbUJq"

shut trellis
#

Oh you passed the setup intent client secret instead of the setupintent id

runic depot
#

oh

#

It doesn't have to do with this CORS error?

#

Access to fetch at 'https://r.stripe.com/b' from origin 'https://js.stripe.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

runic depot
shut trellis
#

yep

runic depot
#

I used the setupintent Id and it worked thank you!

#

should I be worried about the CORS error? I'm in dev testing this

shut trellis
#

Where are you getting that error?

runic depot
#

I see it in browser console whenever my stripe API requests are sent

#

Everything works as intended, and I validate updates on stripe dashboard, but the CORS errors appear