#Lorey-connect-dispute
sweet locust
My guess is you're using direct charges:
For payments created on Standard accounts using direct charges, those accounts are responsible for disputes and any funds are withdrawn from their balance – not the platform.
https://stripe.com/docs/disputes/connect
stone pendant
Yes that is correct. Is this not the right way if we want to handle certain fees through our platform account?
I'm not sure how to quickly find a disputed charge, but this happens rarely. We just don't want our client to have to pay for these fees
sweet locust
Is this not the right way if we want to handle certain fees through our platform account?
Well you shouldn't let dispute fees dictate how you handle Connect charges. Generally there's more factors involved: https://stripe.com/docs/connect/charges
stone pendant
Wait so a destination charge might be a better fit for us?
Is the difference between a direct and destination charge that the destination charge will be automatically transferred?
sweet locust
The link above outlines the key differences
sweet locust
Destination charges, the transactions are generally processed on your platform as opposed to the connected account with direct charges
stone pendant
Can we create destination charge with subscriptions?
Ah nvm
found it
I think i'll be able to figure this out. Thanks for the insight @sweet locust
Ok so,
I think destination charges are suited better for us. However currently we're running all our service subscriptions through subscriptions created directly on the Connect account and charging through direct charges. Is it possible for us to migrate existing subscriptions to a destination charge type strategy? We'd having to move all the subscriptions to our platform account i suppose
obsidian wagon
there's no direct/automatic way to migrate them no, you'd have to re-create Products/Prices on the platform and manually re-create the subscriptions. No exact docs but https://stripe.com/docs/security/data-migrations/imports#working-with-subscriptions talks about approaches for creating a subscription on a Stripe account to match the billing cycle of an existing subscription elsewhere to make it more seamless for the customer. Not a trivial thing overall
stone pendant
Our platform handles mostly iDeal payments. Which require a mandate. Which i think is stored in the PaymentMethod associated with the Customer. These Customer/PaymentMethod's aren't bound to the Stripe Connect Account as far i can see. Is this correct? Or do we need to require all customers to re-setup their PaymentIntent's when migrating the Subscriptions?
obsidian wagon
ah that could be a nightmare yes
the SEPA Debit mandate would be associated with the connected account yes, so payments initiated by the platform will fail. Realistically it's easer to set up new subscriptions.
if it were me I'd probably do something like start using Destination Subscriptions on new users going forward and keep your legacy ones on Direct.
You could also explore other options for disputes like manually re-imbursing the accounts outside of Stripe or something ,or taking a lower application fee on their payments so that can cover the costs easier, but that doesn't seem like a great idea. Overall it's hard to unwind if you've built this with Direct Charges and already gone live
stone pendant
I see, is there no way for Stripe to help us with migrating Mandates?
obsidian wagon
there might be, you could ask https://support.stripe.com/?contact=true