[sago]

> the proposed fee patron fee structure of 2.9% + $0.35

The problem was that was per pledge. So if, like me, you support a couple dozen creators at $1-$3 each, you would expect to pay 24 x $.35. But all those payments are charged in one transaction. So they are only paying $.30. It isn't 5c per transaction they were planning to skim, but $8.

[stormbrew]

Part of the change was no longer aggregating the charges but running them through individually. They wouldn't have been pocketing most of the fees.

Which honestly makes it even more baffling an idea.

[nojvek]

I believe the idea was to give the money to creators immediately rather than end of month when they charged everyone.

[stickfigure]

...which is still baffling! The core value of Patreon is microtransaction aggregation. This isn't just "product management screwed up a feature", it's product management doesn't understand their own product at all. Crazy.

It's like designing a fancy new electric car but leaving off the wheels.

[kalleboo]

It's like designing an electric car, but requiring you to use a diesel generator to recharge it.

[Pyxl101]

You're assuming that Patreon will issue all of those charges at once.

However, they talk about that problem in the article. What if a Patreon supporter pledges/makes a subscription on Day 1, then another on Day 2, and a third on Day 3, and so on?

In their original blog post [1], they spoke about how, ideally, they'd issue each of those charges to the supporter immediately; and then begin recurring billing 30 days later after that date. However, if those charges are made on different days, and the anniversaries occur on different days going forward, then they don't have the opportunity to condense them into a single transaction.

Patreon are looking for a solution where someone can create a subscription, be billed for it immediately (i.e. not wait for beginning of next month), and then continue from there with recurring monthly payments. With a naive system each subscription would have its own cadence, preventing transaction consolidation. They also talk about how, if they have a standard monthly billing period, then there are issues with waiting until the next period to make the first charge.

Perhaps they didn't explain this as well as they could have, but it made sense to me. It seems like a "Patreon Wallet" could indeed be a solution to a lot of these problems. Refill your wallet with a single large transaction, then draw funds from it when pledging to support creators.

[1] https://blog.patreon.com/updating-patreons-fee-structure/

[sago]

If I back a new creator, it charges me immediately (I think, at least it seems that way from my billing history), but going forward I'm billed with the rest of my support in one transaction (definitely). I really don't see the problem.