#nicdiblasi_api

1 messages ¡ Page 1 of 1 (latest)

slate wadiBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1253138529710637118

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

late galleon
#

Hi there, you shouldn't use the connected account's API key

hollow spindle
#

Is it possible though

#

?

late galleon
#

You should always use your own API key (aka platform's API key), and specify a stripe_account in the request. By specifying a stripe_account, you are telling Stripe that you want to make an API call on behalf of a connected account. You can refer to this doc to learn more about making API request for connected account (https://stripe.com/docs/connect/authentication)

#

No, it's not possible to create a PaymentIntent with application fee with a connected account's API key.

hollow spindle
#

The reason why we dont want to use our platform key with this new client is because they host their own server on-premise and we dont want to give them access to our api keys which is universal across all our connect accounts

#

So if its possible to allow them to use their own key then we dont have to worry about securely storing/retrieving our api keys for them to use

late galleon
#

Not possible, and you should only use your platform key in your own server.