If the app store took a 3% chunk and never refunded it regardless of the ongoing status of the transaction, that would put them right in line with other payment processors. It would also still net them billions of dollars, I think!
If the app store took a 3% chunk and never refunded it regardless of the ongoing status of the transaction, that would put them right in line with other payment processors. It would also still net them billions of dollars, I think!
It's uniquely online processors that do not refund fees.
They had refunded fees but iirc it meant they were paying a small fee per refunded transaction (which in a sense subsidizes apps that incur frequent refunds) which they wanted to stop doing.
A quick search showed they started refunding fees in 2012 and stopped in 2017. Here's a discussion from the past couple years: https://news.ycombinator.com/item?id=22371330
It sorta makes sense, since the online processors are usually middlemen that only make money on the fees they themselves charge. I could see their perspective being "we provided the service; that service is not un-provided because the customer returned the item and you sent them a refund... in fact, you used us even more because we had to mediate the refund transaction!"
I think if the fees were just a few percent, I wouldn't have too much trouble accepting that logic, but from Apple, where it's 30%... not so much.
The card issuers don't care quite as much about keeping the fees in a refund scenario, I guess... though I believe you don't get everything back during a refund, regardless.
In fact, you will pay more on the scheme fees to process a refund, as you need to send another message into the scheme's network - often charged per message or per byte etc.
Interchange is not payment scheme revenue - it is just passed through to the issuing bank.
That is primarily an issue for cross-border credit or debit card transactions.
Scheme fees are much lower for domestic transactions as far as I'm aware, though.
Generally, Visa and Mastercard simply charge more per transaction for different cards in the US. For example, rewards cards cost merchants more, which is why many gas stations won't accept them.
Your bank account -> visa/mastercard/discover -> PayPal's merchant bank account -> the person you're paying bank account
PayPal only replaces the ccs when you pay with their wallet. Otherwise they're just orchestrating the money flow (because integrating with the CC companies is a gigantic PITA)
Stripe on the other hand is a credit card processor, and as a merchant you get a Merchant account, the same like Authorize.net who used to be the largest online processor before Stripe.
Back in the day (and I have been out of that market for over a decade) Authorize.net absolutely refunded processing fees on refunds
Auth.net is a gateway/portal that facilitates CC transactions, and while you may be refunded on processing fees for the use of the gateway, someone, somewhere is likely eating the interchange and most likely occurring at the merchant level.
TSYS, Vantiv, PaymentTech are processors. your merchant account is usually with (i think) the acquiring bank that's part of the Visa/MasterCard/Amex/Discover network.
Uniquely those that provide some higher level thing, like PayPal or Stripe. If you have a merchant account, you can get an actual refund for online purchases.
This is for AML, not because of fee refunds.
Something like 5 cents + 1.5% would be a great deal on payment processing, generally. (Apple is a juggernaut and may have been able to negotiate something else, of course.)
That does mean that for a $0.99 app, keeping the fees would still be more than that 3%, at ~$0.07... but not wildly divergent from the 30% amount.
Where the 30% gets really abusive is for things like Codea, the app being talked about in the Twitter thread. It costs $14.99. So it had presumptive fees of ~$0.28, while Apple's keeping $4.50. That's outrageous.
(Also, I see mixed reports on whether credit card refunds refund the processing fees. It might be contract-dependent.)
[1]: https://www.fool.com/the-ascent/research/average-credit-card...
This is new, and in fact PayPal and Stripe enacted this policy only this (or last year if I recall correctly).
Some payment processors like Affirm or Amazon Pay have not changed their policy on this yet.
For example, the default price on Stripe (and many others) is 2.9% plus $0.30. For a business with an average order value of $30, that $0.30 adds a full percent, bringing your fees to nearly 4%.
If you do high enough volume, yes, you can negotiate lower prices.
I'd guess 10-15% is what is actually reasonable. Microsoft has settled for 15% in their store (because nobody was using it so charging 30% is ridiculous).
So much the same as the other stores then.
But the store feature I want to see from Apple is that if you provide the customer referral to your app yourself, Microsoft only takes 5%.
Not GP, but I didn’t read it that way. I read it as Microsoft loss leadering their store to get growth.
You can't attract people to the store with low fees and then raise them later or they'd just leave as soon as you do. Unless you would require them to use Microsoft's store and no other, but then you could just do that from the outset, except that it'd leave you with the same sort of antitrust scrutiny that Apple should be under for doing the same thing.
However, a read of their current policy shows it's no longer the case - so I'll likely get dinged on my next refund.
"Regardless of the type of payment you received, the full amount that the client paid will be refunded to the client by clicking on the refund button at the bottom right-hand corner of the transaction details."
https://support.waveapps.com/hc/en-us/articles/115004056523-...
That doesn't say anything about what the merchant gets charged. Stripe and PayPal also send the full amount to the card holder, so that blurb would apply to them too. The question is whether the merchant ends up with zero or minus the original processing fees after the refund.
We also learned about how credit card thieves test credit cards. We saw hundreds of donation attempts. Stripe had us refund those that went threw, which costed us money in fees. Fortunately we were able to put some quick measures in place to stop them temporarily & then better measures for long term success.
We lowered our online donation limit. Above a certain amount it really is more ideal for a check or some other type of transaction. Though we've had a few people offer to just pay the 3% transaction fee on top of the multiple thousand dollar donation. For those we do a bit more manual process.
For a cost, Stripe also lets you put some additional rules on what type of payments you'll allow & how much info the person has to verify for the payment to be accepted.
Honestly a basic version of this should be free. I shouldn't have to pay extra to say I only accept cards with a CVC number & expiration filled out.
Other business obviously have MUCH higher refund rates (sneaky autobill businesses etc). For these loosing 5% on the refunds matters if they have a lot of refunds, so they'll be very tempted by no costs if you autobill and get caught. They'll just autorenew everyone, autosign up and then be VERY good about refunds to avoid chargebacks. Even if just 30% of customers don't catch a few months you end up with real money.
Of course, CUSTOMERS may hate these players, but stripe I guess is focused on what works for the businesses generating lots of refunds.
The reasonable thing to do is to ramp up the fees based on the number of refunds. You want to push away the crappy billers, but not hammer developers that have the occasional bad release.