#Demodian - Direct Charges
1 messages · Page 1 of 1 (latest)
Hello! No, there is not. Direct charges exist on exactly one of your connected accounts.
will there be something compatible in the future to afford us, as a platform, protection from charge-backs?
I can't really comment on future product/functionality, but I can say this is something we're thinking about.
we have situations where there's up to three hands in the pot when receiving a payment through us (not counting our application fee)
an artist, their agent, and the event promoter
i could lump the agent and promoter in with our application fee, but we don't want to afford them the same protection we need
What kind of connect accounts do those parties have?
well, the way we originally did this, was it was a normal transaction to us via the charge api, and then we would transfer to the others. I'm not seeing an easy way to do that with the direct payment method
we would have each user connect to our platform, and we could calculate and distribute funds afterwards
is it possible to use the stripe_account setting with transfers as well?
Direct charges are only recommended for Standard connected accounts, and the payment lives on the connected account, not your platform, which doesn't sound at all compatible with what you're describing.
okay. I figured I'd ask, as we just got through migrating to PaymentIntents and Direct Payments to safeguard our current business model for event ticket processing. Was trying to see if it could be somehow migrated back to the original marketplace environment
You may want to write in to support with details about your use case and see what they suggest: https://support.stripe.com/contact
I wasn't seeing anything in the specs, so I wanted to ask if there were future plans or not. I will check to see how we can deal with small adjustments in the old business model, and maybe break the methods down into small pieces
This chat is focused on developers with technical questions, not business/liability issues. 🙂