#joel-k_api

1 messages · Page 1 of 1 (latest)

earnest pecanBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1314294710080372837

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

fluid pecan
#

Hi 👋

This Payment Intent is being created on the Connected Account so all the objects related to it need to exist on the Connected Account.

short turret
#

Is that a difference in functionality compared to the charges API? My understanding is that that API allowed all the objects to be held by the platform account and simply shared with the connected account via a token.

#

It sounds like what I need to do is clone the customer and their payment method to the connected account prior to making a request to payment intents, is that correct?

fluid pecan
#

My understanding is that that API allowed all the objects to be held by the platform account and simply shared with the connected account via a token.

No, that has never been true as far as I know

#

I can review an example request if you have it

#

But that has been the same error that has always been returned for direct charges with Payment Methods on the platform since I started at Stripe 3+ years ago

short turret
#

I don't have access to our prod logs unfortunately. But the flow that we have with charges is basically making a request to the tokens API using the platform's secret key, the payment method in question, and the Stripe-account flag set to the connected account's ID. That token then gets passed to the charges API in the the source field. That's been working in prod, but it fails in staging. Here's a request ID that's failing in test mode. (req_umO66mbdrzCig8).

fluid pecan
#

a request to the tokens API using the platform's secret key, the payment method in question, and the Stripe-account flag set to the connected account's ID.

By including the Stripe Account header with the connected account's ID, you create the Token on the Connected Account

#

You are creating a Charge on acct_1CoepGJMDKccxs3K but trying to pay it with a token that belongs to acct_1CoephI3BAdSl33X

#

That won't work

earnest pecanBOT
short turret
fluid pecan
#

Ok. So it seems like cloning customers and payment methods into the connected account is necessary to make payment intents work.

I don't think that is what you were doing before, based on the requests you shared. It looks like you were creating payment methods (Tokens) directly on the connected accounts. That approach will still work

short turret
#

Yes. I'm asking to figure out what I need to do to make payment intents work given what you've told me.

fluid pecan
#

And what I am saying is that you don't

#

But what you are describing does not match what I am seeing in the requests

#

In the requests you shared

  • You make the Token with the Stripe Account header
  • You make th Charge with the Stripe Account header
#

That will still work with Payment Methods and Payment Intents

spring belfry
#

Hi there 👋 jumping in as my teammate needs to step away soon. If you're initially creating your Payment Methods on your Platform account, but want to use them with Payment Intents that you're creating on your Connected Accounts (Direct Charges), then yes, you first have to clone the Payment Method to the Connected Account where you want to use it.

short turret
spring belfry
short turret
#

Thank you kindly.