#maufcost-test-request
boreal shard
Let me see if I can find one
verbal meteor
Thanks!
boreal shard
There you go: req_sSi2DYwhp6Qsr8
I thought at first that Xcode or metro were caching my stripe production keys (which happened before), but I've already recompiled my entire program and it still uses the production keys (even though I've already switched them to the test ones)
verbal meteor
So that request is from your backend
Where you are using your live key
But then you are using your test publishable key in your React Native front end.
You need those keys to match
So you want to swap out your backend secret key from your live to test API key
Ah wait sorry
Your clientside is using your live key as well
boreal shard
I believe one or the other is caching their respective production key since the intent is not confirmed
verbal meteor
Actually yeah what I see above is the case. See: https://dashboard.stripe.com/test/logs/req_tR6fNChLKFddtp
That is the error request
So yeah, you are confirming with test publishable key but your backend is using your live key. So possible that your backend has the live key cached as you stated.
boreal shard
Jeez. How the heck is node caching this if even removed the keys from my virtual env and I'm just using a plain string since I started getting this error? haha
Maybe if I generate some new keys....
verbal meteor
Yeah I'm not sure why node would be caching here but that is definitely what you will need to investigate!
boreal shard
Alright. Thanks, bismarck!