adam-rak-error | Stripe Developers | Page 1

dry shardBOT Mar 28, 2023, 5:52 PM

#

near carbon Mar 28, 2023, 5:54 PM

#

adam-rak-error

#

Hey @craggy wedge ! This feels more like an account support question to me unfortunately. But rak_dispute_read basically mean making sure you have Read permissions on the Disputes resource on your Restricted API key

craggy wedge Mar 28, 2023, 5:56 PM

#

Okay we have turned that on

#

Did something change on the V1/charges endpoint? We have never previously needed this permission before and are unsure why this was triggered.

near carbon Mar 28, 2023, 6:00 PM

#

I'm not sure. Sorry this is quite a cryptic report right now. Do you have an exact and specific request id req_123 I can look at?

craggy wedge Mar 28, 2023, 6:02 PM

#

Sorry about that. Here is a request ID for the failed charge: req_1QYrXtAnU9AR8L

#

Weirdly, we turned that permission on and now it has resulted in a successful charge: req_CYcwgPieFCWJ4r

#

However, we are still concerned as to why this problem happened in the first place as we have never needed to set that permission previously.

near carbon Mar 28, 2023, 6:11 PM

#

what does "we turned that permission on" means

#

like what exactly did you do?

#

Can you show me a clear example where your old RAK worked fine for this too?

craggy wedge Mar 28, 2023, 6:11 PM

#

Went to the api key-> Hit Edit -> Changed "Dispute" from "none" to "read" via the Stripe Dashboard

near carbon Mar 28, 2023, 6:12 PM

#

okay so you did not have that permission before and now you do?

#

I looked at the past 7 days and I don't see you use a Restricted API key to create a Charge in the past 7 days (other than the 401 you shared and now the one 200 that worked after the change)

craggy wedge Mar 28, 2023, 6:14 PM

#

Here is a specific request ID from last week hitting the same endpoint: req_3DniOdQCmS0iQm

near carbon Mar 28, 2023, 6:14 PM

#

that one does not use a Restricted API key though. It uses your official Secret API key sk_live_123 not rk_live_123

craggy wedge Mar 28, 2023, 6:15 PM

#

Okay that is good to know!

#

That makes sense. We didn't realize that we were using the Secret API key before.

near carbon Mar 28, 2023, 6:15 PM

#

And the reason why you need Dispute Read is because you're on an 8 years old API version and at the time the Charge API returned the associated Dispute straight in the API

#

Really you shouldn't be switching to a Restricted API key without a good reason. They come with a lot of limitations

#

if you were using a Secret API key, just stick with a Secret API key

craggy wedge Mar 28, 2023, 6:17 PM

#

Okay, how do we know what key is being used? Can you point me to a screenshot or documentation where we can see this information? (sorry I'm a bit of a noob)

near carbon Mar 28, 2023, 6:18 PM

#

Have you talked to other people at your company deeply familiar with the Stripe integration?

#

That would likely be a lot safer honestly

craggy wedge Mar 28, 2023, 6:20 PM

#

Sorry I meant if there was a way to see it directly in the Stripe Dashboard. I can see now that I can go to the "API Keys" section and then view the request logs for each key. That was what I was looking for.

near carbon Mar 28, 2023, 6:21 PM

#

gotcha

craggy wedge Mar 28, 2023, 6:25 PM

#

Thank you for your help @near carbon, this is my first request. Promise I will get better 😁

#adam-rak-error