#stripe_dev-token

1 messages · Page 1 of 1 (latest)

inner tree
#

That normally means you are using different Stripe Account than the Account on which the token belongs to

#

If you can provide a request id, we can take a closer look

edgy prism
#

how do I get the request id

inner tree
edgy prism
#

ok, let me run a test really quick and provide that to you

#

I found one from earlier today "req_uvkrDf8gbxe7cw"

inner tree
#

The request is on acct_1BF1eHH7SAwUFK9I, while the token is created on acct_1IiLyBDwX05yKJRE They are completely different accounts

edgy prism
#

Is that a connect account?

inner tree
#

I don't see them connect to each other

edgy prism
#

I don't see either one of those accounts in my stripe dashboard

cerulean magnet
#

@edgy prism i'd suggest verifying that you're using the correct pk key in your application

#

it's possible that the public key on your application is not the key from your account that you want to test on

edgy prism
#

Just to be clear, the PK is used on the client side to generate the token, correct?

cerulean magnet
#

yep

edgy prism
#

and then the secret key is used in the APIs on the server side

cerulean magnet
#

that's right

#

both keys should be your account's, so i guess you would probably want to check both keys for completeness

edgy prism
#

Its breaking on the first step of storing customers. I have the correct secret key and the PK

#

?

#

@cerulean magnet For the above scenario. I am assuming I should be using my PK and SK to store credit cards, correct?

cerulean magnet
#

can you share your account id too?

edgy prism
#

where do I find it?

#

NVM - acct_1BF1eHH7SAwUFK9I

#

So it looks like the request is being made on the right account

#

but the token is being created on a different account, which as far as I can tell I cannot find in my dashboard

cerulean magnet
#

on the application which you're using to create the token, check what is the public key being used

edgy prism
#

unfortunately, I am not working on the client side. There is another developer that is working on that. But, you think he is using the wrong PK possibly?

cerulean magnet
#

it's possible, yes

edgy prism
#

I just want to make sure that is where the discrepancy is, so I can talk to him tomorrow and sort this out on his end

cerulean magnet
#

it's likely that's the issue, but you can easily verify that if you can access the page where the token is being created

#

if you look at the source code, it should include the public key e.g. pk_test_123

edgy prism
#

Does it show the PK in the request body in stripe logs somewhere?

cerulean magnet
#

if we look at that particular token - tok_1K6HhGDwX05yKJRE1h7PQYr4, it's being created by a different account i.e. using a different public key than yours

#

since we mentioned the account id and you don't recognize it

edgy prism
#

gotcha

#

where can I see in stripe dashboard the token and the PK being used to generate that?

#

for tok_1K6HhGDwX05yKJRE1h7PQYr4

cerulean magnet
#

probably in the logs as well. But since you don't have access to that particular account, you wouldn't be able to see the relevant logs

edgy prism
#

ok

#

I just tested the credit card save with the tok_amex test token

#

that passed

#

but that will not have a PK because I just tested it via Postman and it is a test token, correct?

cerulean magnet
#

you made a request to create a customer with the tok_amex token, so yes, that particular API call doesn't make use of a public key. It uses a secret key

edgy prism
#

ok

cerulean magnet
#

on a side note, you shouldn't be using tokens

#

Tokens and Charges are deprecated. You should use PaymentIntents and PaymentMethods

edgy prism
#

ok, so how do I save the credit card on my platform and let the connect accounts use it, and make the connect account responsible for the fees.

cerulean magnet
#

it's a bit difficult to find