#bwurtz999 - direct charge
jolly saffron
Hey there, can you share the requests where you create the shared payment method and then the erroring request to confirm the PI?
I suspect there might be a mismatch in the account context
coral widget
The shared payment method creation is in my first message above
$stripe->paymentIntents->confirm(
$pi->id,
[]
);
^this is how I attempt to confirm the PI
jolly saffron
Sure but I mean actual request IDs where you do this -- especially the error
such as req_12345 -- https://stripe.com/docs/api/request_ids
coral widget
oh sorry
jolly saffron
No worries - i should have been more clear
coral widget
Confirm SetupIntent: req_QkUMjyJIgteWbr
Attach PM to Customer: req_vNP6Iwa3ISNyGg
Attempt to Confirm PI:
req_uZ1AgZ5VtjTcKW
strange that I don't see the payment method creation in the logs
wait sorry
ignore the above
use these:
SetupIntent: req_yBAhoLOFWDy1oS
Confirm SetupIntent: req_QkUMjyJIgteWbr
Attach SetupIntent: req_zhv5kKBJPItc7I
Confirm Payment Intent (fails): req_7lEKgTnfHtgqsL
I still don't see a payment method creation in the logs
jolly saffron
Gotcha - that one is here: https://dashboard.stripe.com/test/logs/req_gRpb0qRfS4JoeO
coral widget
I read in the docs that I had to create a cloned payment method to charge a custom across connected accounts. am I doing this right?
to charge a customer*
jolly saffron
Oh, oops
OK yea the setup here is all valid
The only issue is that last request to confirm the PI isn't being done with the account header
coral widget
In the API docs I don't see an option for a connected_account value
jolly saffron
It's the same header as the other requests:
https://stripe.com/docs/api/connected_accounts
It applies to all API calls
coral widget
ohhhh
jolly saffron
So the same thing you did when creating the PI you need to do when confirming