This repository has been archived by the owner on Feb 8, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 308
go over payday numbers and make sure it is right #37
Comments
Having a history page (#43) will help with this. |
See also #47 for the bank side of this. |
chadwhitacre
added a commit
that referenced
this issue
Jun 13, 2012
I screwed up the pricing. Samurai charges $0.10 if you have your own merchant account, but we're using one of theirs, so the cost is $0.30 per transaction. #37
Good info on https://www.mymerchantoffice.com/. This is FirstData's portal, and they are the holder of the merchant account we were using with Samurai and are transferring to Braintree (#58). |
Last payday was a cluster huck. Punting to next week so we can get through a payday with Stripe. |
chadwhitacre
added a commit
that referenced
this issue
Jun 22, 2012
When a user tips an unclaimed account we create an entry in the participants table for the tippee, with claimed_time set to NULL. Tippers by definition must have claimed their account, so we can ignore unclaimed accounts in the outer payday loop. This will help the numbers line up better between the output of the payday script and the stats page. (#37)
chadwhitacre
added a commit
that referenced
this issue
Jun 22, 2012
The dollar figures on the stats page didn't take into account whether tips were claimed or not. So it would read $52.88 instead of $27.44. #37
Got through two with Stripe, $30.08 and now $110.08. I didn't capture the full logs last week, but I was careful to this week. Got some good data to go through now. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Now that we've had our first real payday we should make sure the numbers really really all line up.
The text was updated successfully, but these errors were encountered: