#mubezzz_api

1 messages ยท Page 1 of 1 (latest)

tough driftBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1417949589943750707

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

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.

lone ravine
#

Hello, it looks like that API call succeeded. Are you saying that that call errors out occastionally? Or that the client secret doesn't seem to make it to your client even though the call is succeeding?

jaunty dust
#

Hello, it is successful but the payment form is not displaying

#

THis is what I see. I do not see an option to add payment info

lone ravine
#

Gotcha, that can be a number of things. First, have you double checked that your server is properly passing the client secret to your frontend? Like if you try to log it on your frontend does it print what you expect? And have you checked the developer console to see if any errors are being thrown?

jaunty dust
#

I see all 200's in the deverloper console. Let me check if the server is properly passing the client secret

jaunty dust
#

Hi, I'm still checking. Just wanted to update you

tough driftBOT
jaunty dust
#

yes, I see that the client Secret is being passed properly

#

Are there any other common errors?

tidal cedar
#

Hi there, stepping in for Pompey

#

Is there somewhere I can visit to reproduce the issue?

jaunty dust
#

would the url to the website help?

#

Hi!

tidal cedar
#

Yes

#

If I can visit your site to reproduce that would be great

jaunty dust
#

Here you go ๐Ÿ™‚

tidal cedar
#

Do I need to do anything or should Payment Element render on load?

jaunty dust
#

please give me a couple of mins before you try. Deployment is almost done with updated code

tidal cedar
#

Okay yeah when I click "Continue to payment" nothing happens

#

But let me know when you are ready

jaunty dust
#

You need to complete the form and recaptcha then form will load

tidal cedar
#

That doesn't seem to be the case

jaunty dust
#

You're ready to go

tidal cedar
#

Okay looking

jaunty dust
#

Thanks!

tidal cedar
#

While I'm looking can you also show me your client-side Payment Element code?

jaunty dust
#

yes, one moment please

#

StripeWrapperComponent calls the PaymentElementComponent

tidal cedar
#

You are saying this works fine in development?

jaunty dust
#

Yes

tough driftBOT
jaunty dust
#

I've been able to make many mock payments in dev

tidal cedar
#

Have you double checked your Publishable Key?

#

And ensured it is updated to your livemode key?

jaunty dust
#

this is the key that begins with pk_live?

tidal cedar
#

Yes

jaunty dust
#

One moment. I will double check

tidal cedar
#

Yeah I think that is the issue... when you load the site you will see an error in console for index.mjs:144 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'match') which is being thrown from code triggered by loadStripe and the error is from var isTestKey = pk.match(/^pk_test/); which is indicating your pk is undefined here.

#

So basically Stripe.JS is never getting properly loaded here

jaunty dust
#

I'm making some changes and should be able to update you in abotu 5 mins if thats ok

#

I see the same error but I'm using the live pk. The correct key is in the env file

#

But I'm still facing the same issue and not sure why I'm getting that error

shy lichen
#

Hi there - taking over for bismarck here

jaunty dust
#

Hi

shy lichen
#

Just taking stock of the issue and thinking about where to go nexst

jaunty dust
#

ok thank you!

shy lichen
#

just to be sure - the dev and production sites are using the exact same code, same react versions, etc?

jaunty dust
#

yes, correct

#

I need to log off. I will continue to try tomorrow/. thanks