Earlier quoted context omitted.
Its not just a communication problem, it's a pattern. You guys did the same thing last year when you stopped returning fees on refunds. I couldn't believe my eyes when I read that you weren't returning fees anymore. I get not returning the flat 0.30 transaction fee, but not returning the % fees smacks of being more worried about the corporate bottom line than customers. Many processors refund the % fees, and there's…
Which payment processor would you recommend now? Edit: See also https://news.ycombinator.com/item?id=16772655
For example, these guys: https://www.netcompaysystem.com
And many of these processors will give you gross deposit which is the only way to make things easy for an accountant. The net fees model Stripe uses is a nightmare for reconciliation at any sort of scale.
This isn't to say I've abandoned Stripe entirely -- there are some cases where it makes sense, when you're actually using some of the advanced features and API, not just a straightforward card charge.
I just completed a Stripe Connect integration that handles millions a month for several clients... but even there you run into half baked/stapled on feelings when you try to produce a full featured process that works at scale. For example, there's no straightforward way to provide a batch report for a Stripe Connect client -- the charge ID's don't match up with the platform account, and the only way to fully map which charges/refunds/chargebacks are in a given deposit for the client account is to link them up by amount and date/time....