#simp_code

1 messages ¡ Page 1 of 1 (latest)

midnight loomBOT
proper hearthBOT
#

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.

midnight loomBOT
#

👋 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/1269885067115888710

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

fiery spruce
#

and im getting this error in console
{
"error": {
"message": "The client_secret provided does not match any associated PaymentIntent on this account. Ensure the publishable key used belongs to the same account that created the PaymentIntent.",
"param": "client_secret",
"request_log_url": "https://dashboard.stripe.com/test/logs/req_rGg0Wkt4Vk0re0?t=1722833823",
"type": "invalid_request_error"
}
}

#

when i use test publishable key

languid mango
#

Hi there, it looks like the publishable key that you set on the frontend isn't from the same Stripe account.

#

I'd suggest you double check the keys that you set in frontend and backend, and make sure they are from the same Stripe account.

fiery spruce
#

both live and test publishable key i copied from stripe dashbpoard

#

with live publishable key i can see this page

#

but with test publishable key i can't see the same screen

languid mango
#

Is you backend using the live mode key, but frontend using the test mode key?

fiery spruce
#

no backend and frontend are using same publishable key

#

in backend im generating client secret and from backend i fetch client secret key to frontend

#

if i add live publishable key with test credit cards then i can't test it
but with test publishable key im not getting card details screen

languid mango
#

The API key that you use in backend, is it live mode or test mode?

fiery spruce
#

if its possible can we discuss this google meet

languid mango
#

No, I can only help though chat.

#

If you use a live mode API key in your backend, you should only use live mode API key in frontend.

fiery spruce
fiery spruce
#

i didn't added live mode keys in backend yet

#

can i share you code screenshots ?

#

along with keys

languid mango
#

No, you don't expose your API key here. I'd suggest you double check and make sure correct keys are used in frontend and backend

fiery spruce
#

ok, but your test mode keys are not working with frontend

#

i cross checked multiple times

languid mango
#

Can you share with me the PaymentIntent ID?

fiery spruce
#

pi_3PkJhnAcgj3zVAKU1S6jMcBk

languid mango
#

Ok, the paymentntent was created with the correct API key.

fiery spruce
#

yes sir

#

with test mode

languid mango
#

Do you have any middleware that might change the client_secret before sending it to frontend?

fiery spruce
#

umm yeah im creating client_secret in asp.net backend and passing it to my asp.net api and then fetching it from api to react

languid mango
#

Try passing the raw client_secret to your frontend without modifying it.

fiery spruce
#

oh i pass raw client_secret its showing now

#

like statically i added it

#

but how can i improve it with by passing api parameter

languid mango
#

Looks like your code somehow alter the client_secret before sending it frontend.

#

You should add some logs in your code to figure out which part of the code alters the client_secret.