#peanut-apikey-question

1 messages · Page 1 of 1 (latest)

knotty raven
#

@fallow perch a lot of harm unfortunately if they get the Secret API key. For example they can refund all your existing charges

fallow perch
#

oh ok

#

i guess its seperate than my public api key

#

how can they do that without my id?

knotty raven
#

Correct it's separate. Each account has a pair of API keys. A Secret API key stored securely on your server for the majority of calls and a Publishable API key that is used client-side (where anyone can see it) to collect card details securely

#

the Secret API key is your id. That's how all API requests are authenticated, that's what your code uses to create a Customer, a Refund, respond to a Dispute, etc.

fallow perch
#

i had a dev which i gave my key to sor him to settup the website and he left within a week and im worried what harm he could do

#

ok

#

i thought it was ok to share id?

#

not api key though

knotty raven
#

what do you call "share id"?

#

what's an "id"?

fallow perch
#

account id

knotty raven
#

account ids are not really relevant for a developer

fallow perch
#

can i confirm that if the api ket starts pk_live that its the public one

knotty raven
#

correct pk_live_123 => Publishable API key

fallow perch
#

and there is no way anyone could acess my account or harm me in annyway with it

#

also the test one i assume is publishable

knotty raven
#

pk_test_123 is publishable too yes

#

ultimately, if you hire a developer, you have to trust them 😅

fallow perch
#

thank you man

#

i can work stress free