#uladzislauchekanau
1 messages · Page 1 of 1 (latest)
Hi there!
Can you share the ID (req_xxx) of the failing API request?
https://support.stripe.com/questions/finding-the-id-for-an-api-request
thanks for sharing, checking...
Could you do a test for me by doing the same request but using the PaymentMethod Id and not the ba_123 (pm_1NVDJdKBaG8UnmrcqkJNxli4)?
yes make sense, because the payment method is created by the platform account
let me check more about this...
Sure, thank you
I'm seeing a mandate attached to the original PaymentMethod, I'm not sure honestly, but I'm affraid that the mandate didn't propagate via the external account... Can you try collecting the PaymentMethod on behalf of the Connected Account acct_1NVA1dGgC7309ZGF from the begining ?
How can I do this?
I have to remove customer from create setup intent payload and just add Stripe-Account header or ?
No keep both (create the customer using the account header too)
But then this customer should be treated as customer of connected account, isn't it?
And not mine
Correct.
But that's incorrect from the domain site then, each connected account is basically my customer
And I still have to create external account for the connected account, which will be missing mandate again I suppose
Yeah I think the issue here that the mandate is collected by the platform account, while the mandate is for use by the Connected Account.
Here the customer object on the connected account, is used only for collecting the payment method in order to be used for the treasary API. You can keep using the platform Account's customer for purchase puposes.
I see, thank you a lot 🙂