Quoted from ForceFlow:
It seems like either way you look at it, the customer loses, either through restocking fees or increased price. Businesses generally don't want to "eat the cost", and with a smaller business, it's difficult to do that in the first place.
I get that for low value items, it's not that big of a hit. But when you start getting into the hundreds or thousands of dollars, it's a pretty significant sum.
What if you're selling a NIB game, and you get an accidental duplicate order? Whoops, that's at least a $150 loss or more. You can't really pass that along to the customer as a restocking fee. Plus, if you raise your prices to cover that, now you have higher prices than your competitors, which could lead to a decrease in sales.
Definitely not an easy situation for a business owner to be in, but I don't think it's fair to expect the payment processors to do things for free either. There are tangible costs associated with processing payments.
Sounds like Zitt is OK paying the fee on a single transaction when he gets money, but in a refund situation he expects the payment processor to give up their processing cost on what has now become two (or more) transactions they have to deal with.
One of my big projects at work this year was taking a product and making it PCI compliant. There's a lot of ongoing feeding and care that has to be funded to keep things secure for clients and provide things like 100% uptime for payment processing, etc...