#Austin_Rowe - PaymentIntent Client Secrets

1 messages · Page 1 of 1 (latest)

jade badger
#

Hello! No, you should never store the client secret. You can store the PaymentIntent ID and then retrieve the client secret from the API when needed.

torn terrace
#

I tried to retrieve the payment intent and it said one didn't exist with the id I passed in, but I can see the payment intent with that id in the dashboard so I know it exists

#

This is with Connect btw, idk if that changes things

jade badger
torn terrace
#

req_M1Ne1K573undLQ

#

If you want I can give you the acct_id that the payment was directed to as well

jade badger
#

No need, looking...

torn terrace
#

Ok, thanks

jade badger
#

The reason you got the missing error is because that PaymentIntent exists on a connected account, but you made that API call on your platform account.

torn terrace
#

Is it possible to make api calls via a connected account? That seems a bit sketchy haha

#

Or is there some other way to retrieve the intent?

jade badger
#

Yeah, you did so when you created that PaymentIntent.

torn terrace
#

I'll check it out!

#

So I can pass in the connected account id in the same way as when I created the payment intent, correct?

jade badger
#

Yep, then you should be able to retrieve the PaymentIntent.

torn terrace
#

Perfect, I'll try it out! Thanks @jade badger

jade badger
#

Happy to help!

torn terrace
#

Worked as needed! Thanks again