DuckHunter

[fresh comet]

Hello! If you're using direct charges we strongly recommend Standard accounts, as you pointed out. If you make direct charges on accounts without Dashboards it's going to be extremely difficult to handle things like refunds, disputes, and so on.

[true copper]

In my case I'd like to have direct charges, but the platform will handle refunds, disputes, etc.

It's a little bit backwards, but ultimately that's why I was looking into this. If I setup webhooks and API calls in my own platform to handle disputes and refunds could this potentially work?

[fresh comet]

It can technically work, but it's a huge amount of work and, again, is not recommended.

Your platform would need to cover negative balances for the connected accounts, Radar isn't compatible with this approach, it's very hard to get good metrics, Stripe email receipts probably won't work the way you want, and you might see unexpected fee behavior.

[true copper]

So if I went with standard accounts and direct payments, would there still be a way to have the platform handle refunds and disputes?

Or does that come back to the same issue

[fresh comet]

If you want your platform to be liable for and handle refunds and disputes you should use destination charges with Express or Custom accounts. See here for more details: https://stripe.com/docs/connect/accounts

[true copper]

Alright. So based on that, direct payments are not necessarily recommended if the platform is liable for refunds and disputes

[fresh comet]

Yes.

[west meteor]

You may be confusing "direct payments" and "direct charges" - they are not the same thing - what do you mean by "direct payments"?

"Destination charges" do pay directly to the connected account - but in a way that allows the platform to handle refunds and other exceptions

[wanton sun]

directly to the connected account
A transfer is automatically created to the connected account, but the payment intent exists on the platform

[west meteor]

Which is what (a) moves the funds to the connected account and (b) allows platform to manage the exceptions, no? Above, the OP kept using the phrase "direct payments", and Rubeus used the phrase "direct charges" - which is why I tried to clarify for the OP

[true copper]

I meant Direct Charges. Thanks for clarifying.

I think I've got all the info I need. Thanks everyone for the info.

Actually, I do have another question. I noticed that Stripe used to have a "Paper Checks" beta where customers could send checks to a lockbox service to pay for invoices.

I can't seem to find any info related to this anymore? Is this beta gone?

For example, this link now returns a 404 and I see no info about the beta in the docs or on the website anymore https://stripe.com/docs/invoicing/paper-check-payment

[wanton sun]

Ah, for help with that you should reach out to support: https://support.stripe.com/contact

[true copper]

I haven't signed up for it yet: is it still available to sign up for it via contacting support?

Or is it completely end of life

[wanton sun]

You can ask support about it and see what they can do for you

[true copper]

Alright, thanks!

[true copper]

Just a heads up, chat support still thinks this program is available. I was directed to apply for the program on the payment method page and sent this link (which returns 404) https://stripe.com/docs/invoicing/paper-check-payment

I'm being escalated though, but either way I thought I would let you know.

[wanton sun]

Appreciate the heads up 👍