This repository has been archived by the owner on Feb 8, 2018. It is now read-only.
Drop payout fee #1282
Merged
Drop payout fee #1282
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is ready for review. |
|
We still mention the fee in the FAQ. IRC |
|
ht @lukevers |
chadwhitacre
added a commit
that referenced
this pull request
Sep 12, 2013
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It turns out that Balanced isn't actually charging us for payouts(!). Here's my interaction with support:
And the reply:
As a result (and this came up at the lightening talk AMA I did at PyOhio last weekend), we should pass this on to our users and drop the payout fee. I don't think we should worry about refunding, though that would certainly be a thing.