#cw

1 messages · Page 1 of 1 (latest)

green hareBOT
lusty hatch
#

Hi @fluid bramble

fluid bramble
lusty hatch
#

Okay

#

one min

#

request-id: req_fdSeiPOb67YjgC

#

should i roll my pk_test api key

#

and use a new one?

#

could that be the issue?

fluid bramble
#

I'm taking a look here

#

The reason being is that this payment intent, pi_3MS7HkDntWnWeWvu0HliLVlM was created on
acct_1GirvbDntWnWeWvu. However, you're truing to confirm the payment intent with this,
acct_1IKM7hKrEzRlezT4 account' API key.

#

No need to roll your API key, that is not the issue.

lusty hatch
#

there is no pi_3MS7HkDntWnWeWvu0HliLVlM anywhere in the code

#

the code fetches pi from account from sk key

#

am i overlooking something?

fluid bramble
#

That is coming from your code, and you can confirm this here: https://dashboard.stripe.com/test/logs/iar_fdSeiPOb67YjgC. The issue is that you're creating and trying to confirm the Payment Intent with two different API keys. I'd recommend that you debug this and make sure that you're using the same API key for making these calls.

lusty hatch
#

i can't access that log that you sent me.

#

No request log found with the specified ID.
The log may have passed its retention period.

fluid bramble
#

It's the request id you shared earlier, it's likely that have logged into to your other account.

lusty hatch
#

very confused

#

let me look at the code one more time. developer handed off code and told me to replace SK and PK in .env. That's the only place that has any API keys.

fluid bramble
#

Where did you get this?

request-id: req_fdSeiPOb67YjgC

lusty hatch
fluid bramble
#

There are different API keys. One is Publishable API key and the other is the Secret API key. This request you've shared is using a Publishable Key by your frontend code. When the payment intent was created, on your backend, you used a Secret API key, https://stripe.com/docs/keys#obtain-api-keys

lusty hatch
#

yes - both are from the same account as far as i know

fluid bramble
#

It is not.

lusty hatch
#

hm. i will review the backend line by line. i tried searching for the developer's secret key and i couldn't find anything.
if it's there and you are right, there will be a problem 😄

#

thanks anyway for the help