#AlexKing-APIkey

1 messages · Page 1 of 1 (latest)

boreal terrace
#

Hi @polar tide! It looks like you are using a restricted API key that doesn't have the required permissions. What exactly is your question?

polar tide
#

we have installed run payment with stripe extension in firebase

steel pasture
#

I don't know much about that unfortunately.
But basically however you configure that extension, give it your full secret key sk_test_xxx instead of a restricted key and that should fix it.

#

your guide says

Then, in the Stripe Dashboard:
Create a new restricted key with write access for the "Customers", "Checkout Sessions" and "Customer portal" resources, and read-only access for the "Subscriptions" and "Plans" resources.

which is fine for one use case that guide is for (Billing), but it doesn't work for the mobile integrations, since they use different APIs(and one of those APIs doesn't work with restricted API keys), so that's why you're getting this basically.

seems to me like the guide is outdated perhaps

polar tide
#

where should i place the full secret key?

steel pasture
#

anyway just use your secret key and it will fix it

steel pasture
polar tide
#

firebase is not allowing to place secret key

steel pasture
#

how so?

polar tide
#

???

steel pasture
#

do you get some kind of error from Firebase when trying to use the secret key?

polar tide
#

checking

#

reconfiguring firebase will take 5 mins

#

not working

steel pasture
#

can you expand on "not working"? an error message or a screenshot, perhaps?

polar tide
steel pasture
#

seems ok to me, I'm not sure I follow how that is "not working".

polar tide
#

see the message above mode

#

????

steel pasture
#

maybe you didn't save the change and deploy it? that screenshot looks like you're still using the old API key.

#

I know nothing about Firebase and have never used it sorry, but you probably just need to redeploy the function/app after changing that key.