#monove
1 messages · Page 1 of 1 (latest)
we're using our platform public key
That payment intent was created on a connected account - you need to use the platform API key and also set the stripe-account header client-side
ok and what about now https://dashboard.stripe.com/test/logs/req_18L0NnEttpDpHJ
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
the payment mmethod was created using on_behalf_of but I was clearly told this would be stored on the platform account, not the connected account
YOu created that PaymentMethod using the stripe-account header server-side
can i get a log for that?
This is the request ID for that - req_d0JrT9De6pOZfv
and it was done on account
acct_1MF26n2aA6B7Coa3
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
thats the one i just did
and experiencing the same issue
That one seems to be working fine though? The request was successful and the setupt intent was confirmed
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Are you cloning payment methods to your connected accounts? If you're using on_behalf_of you shouldn't be using the payment method that's been cloned to the connected account at all - you should use the one that's created on the platform
that made it sound like you could
trying to abstract a little in our code and not store every nuanced setting
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Hmm... I think maybe the initial question got misinterpretted in that last thread
You mention "Direct charge" - what is your end goal here? To do payments on the platform? Or payments on your conencted ccounts?
to store the card to our platform and make direct charges on a card as needed whenever customemrs want to order food from a particular connected account
part of what steered that conversation was my hope that we'd be able to limit the number of 3DS auth screens
ie if the customer is paying for an order the first time on a particular card, it would be annoying from them to have to go through 2 auths. First to store their card, then to use it. This is our existing flow.
we do direct charges to connected accounts as per stripes instruction
Got it! So if your intention is to create payment intents on your connected accounts then your requests for Payment Intent creation are wrong - if you look at req_zhnYMy3YEeSm2q it's being done on the platform account
You need to switch that code to make the intent on your connected account
and i need to clone the payment method to the connected account first?
Yup!
req_qptHEJmjGxxaU1
was that done properly?
then we got this when trying to handle next steps: https://dashboard.stripe.com/test/logs/req_up2ptfg03Djpmx?t=1691081328
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
If the paymetn intent was made on the connected account you HAVE to keep using the stripe-account header to do anything with it
that latest get request failed because you don't have the stripe account header set on the request
that latest request was made using javascript
how do i do onBehalfOf for handleNextSteps
I already sent you that link earlier - https://stripe.com/docs/connect/authentication#adding-the-connected-account-id-to-a-client-side-application
You'd set it when you initialize stripe