On 09/11/2017 05:56 PM, Stephen Michel wrote:
> On Mon, Sep 11, 2017 at 10:50 AM, Bryan Richter wrote:
>> On 09/11/2017 03:16 PM, Stephen Michel wrote:
>>>  When we reach alpha, maybe it's time to run our first crowdmatch?
>>>  It'll be below our normal minimum, thus we'll be paying much more in
>>>  stripe fees than we'd like, but the point would be to find pain
>>>  points in the process, not recieve significant sums of money.
>> My answer to your question is both "yes" and "no". Yes we should do
>> the first crowdmatch before October 1. But we won't charge any fees.
>> Recall that there are two processes: crowdmatching and payment
>> processing. A crowdmatch transaction updates the amount that a
>> patron "owes" to a project. Separately, we use Stripe to settle up
>> between patrons and projects. This is just another way of saying that
>> donations roll over to the next month if the amount owed isn't enough
>> to minimize fees.
>> This raises an important point: the significance of these numbers needs
>> to be made clear on the website: current pledge value, current amount
>> "owed", and total amount paid to the project to date.
>> Now, should we do special-case payment processing that ignores our
>> promise about maximum fees? I definitely think not. :) Right now we'd
>> be talking about a 30 cent charge on a 6 cent donation. Bleh
> Ah, let me update my verbiage: I meant to propose that we run a crowdmatch for
> all months that people have been pledging with real credit card numbers, then
> run a payout on that total. So it'd be more like a 35 cent charge on a 45 cent
> donation (for me anyway, newly pledged patrons will be closer to what you
> said).

Well, I don't have the machinery to create retroactive crowdmatch
transactions. We have all the data (pledge histories) to do such a
thing, but I don't know it's worth it. Better to move forward.

> With 67 patrons that's just under $25 in fees. So, let's not do that, but
> maybe let's trigger a payout for just a handful of accounts (those of team
> members), to verify that it will work in The Real World (tm), rather than
> running into issues later that might affect people with less stake in the
> project. :)

I don't have the machinery for doing that, either. :) Not a bad idea,

Attachment: signature.asc
Description: OpenPGP digital signature

Dev mailing list

Reply via email to