#xaositect_api
1 messages ยท Page 1 of 1 (latest)
๐ 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/1276276711876591737
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi ๐ yes
With Direct Charges the Payment Intent object resides on the Connected Account, rather than on your Platform. Because of that any objects the Payment Intent tries to reference, such as Customer, Payment Method, etc., need to reside on the Connected Account as well since the Connected Account cannot interact with objects on your Platform account.
That's unfortunate for us. And there is no way to "share" a customer
Currently all customers for all our vendors are on our account
So if direct charges are not really feasible, is there any other means to shift the merchant of record business to the connected vendor?
You can create a new Customer on the Connected Account using the details of the Customer that resides on your Platform, but no there isn't a way to let the Connected Account use the Customer object on your Platform account directly.
Destination Charges, and Separate Charges and Transfers, allow you to adjust the settlement merchant via the on_behalf_of parameter:
https://docs.stripe.com/connect/destination-charges?platform=web&ui=stripe-hosted#settlement-merchant
Okay I'll take a little deeper look into separate charges & transfers
Will that also have the same customer constraint?
No, both Destination Charges, and Separate Charges and Transfers, flows create objects on the Platform account, so they'll be able to reference Customer objects that reside on your Platform account.
Okay, thank you, maybe this isn't such a show stopper as I feared.
Happy to help!