#pulpremicks-no-such-token

1 messages ยท Page 1 of 1 (latest)

drowsy silo
#

Hi there! do you have the request ID for the above error?

barren rapids
#

POST /v1/customers/cus_LI2T40kqbfQFlo/sources

#

that what youre looking for?

drowsy silo
#

The req_xxxx for that would be great

barren rapids
#

req_JGQrh88PAIG8cA

drowsy silo
#

Looks like you have mixed up your keys

#

The request is taking place on a different account than where the token was created

#

Are you attempting to clone by chance?

barren rapids
#

ah, we have a staging enviroment which has a test stripe account, I wonder if the key has made it into our production account, Ill have a quick look

#

we basically have a frontend which uses a stripe public key to create a token, this token is sent to the backend. the backend uses the secret key

drowsy silo
#

Yeah in that case you likely just are mixing keys

#

Between the accounts

barren rapids
#

its the same account, just different keys

#

one is publishable, and the other is secret

#

when we did this for test mode, it worked fine

drowsy silo
#

Well no... in this case you are using two different accounts -- your staging and prod.

#

So you are using the publishable from one account and the secret from the other.

barren rapids
#

no, its using the keys from the same account

#

our prod frontend and prod backend

#

one uses a publishab le key and the other a secret key

drowsy silo
#

lol I'm literally looking at the request and the token and they are on different accounts. tok_1KbSP7Ls3MwOPIe4YP0a2SNa is on acct_1DpyaCLs3MwOPIe4 and your failed request (req_JGQrh88PAIG8cA) takes place on acct_1Jf25qFuSqQC7ldV where the token doesn't exist which is why it fails.

barren rapids
#

where can i find the account id on the dashboard?

#

so i know which one is correct and which one isnt

drowsy silo
barren rapids
#

are you able to tell us the account name attatched to acct_1DpyaCLs3MwOPIe4 ?

drowsy silo
#

No I can't share that here as it is sensitive information.

barren rapids
#

acct_1Jf25qFuSqQC7ldV this is our production one

drowsy silo
#

lol the naming of acct_1DpyaCLs3MwOPIe4 indicates it would be your production account but I can pretty clearly see it is your test account

barren rapids
#

were defo getting warmer on this one, this is what im playing with

#

could you give me like the last part of the name? for the account with ID acct_1DpyaCLs3MwOPIe4

drowsy silo
#

I'd recommend deleting that screenshot as it has sensitive info related to your account ID + name.

#

acct_1DpyaCLs3MwOPIe4 is named **** - PROD

#

That should actually be 4 letters in front but discord is adjusting based on syntax

barren rapids
#

got yah, checking thorough rest of keys now

#

weord how its only just become an issue from a key thats possibly from an old stripe account

drowsy silo
#

Yeah this happens more than you would expect ๐Ÿ˜‰

barren rapids
#

tok_1KbSQLLs3MwOPIe4q8vryr3d
req_kYcsIXvChkl2IL

drowsy silo
#

Still different accounts ๐Ÿ™‚

barren rapids
#

is it from acct_1DpyaCLs3MwOPIe4 ?

#

so token is on tok_1KbSQLLs3MwOPIe4q8vryr3d and request is on acct_1Jf25qFuSqQC7ldV?

drowsy silo
#

Token is on le4

#

Yep