-
Notifications
You must be signed in to change notification settings - Fork 308
automate bitcoins payins #1963
Comments
It has a bounty: http://freedomsponsors.org/core/issue/16/pre-pay-gittip-with-bitcoin |
Bounty's title says "pre-pay". I don't think you can pre-pay a payout ;) |
@knocte I am sorry, OK, you are right. |
+1 |
+1 from @campadrenalin via [email protected]. |
I don't have any prior experience with Conbase's API, but just from looking at it, I think this would be relatively straightforward to do. Coinbase has a "payment button" API to create buttons, which open an iframe that requests payment. The payment can make the amount editable (which I think makes sense for a payin). The suggested amounts are editable (with configurable suggestions), and the currency can be specified (so there can be a separate button for paying in EUR, GBP, etc.). Downside of everything but USD is that Coinbase doesn't show you how much that will be in USD, so unless you look up the exchange rate yourself, you won't know by how much your Gittip balance will increase until after you pay. Coinbase can be configured to deposit the received payments in USD automatically, for 1% + $0.15 fee. (Deposits happen only once a day, so the $0.15 fee is only charged once for all payins on one day.) After the payment, Coinbase will post the payment information to a callback that you specify. It receives JSON encoded data that describes the order, including the amount of USD, so it can then be used to update the user's Gittip balance. Open issues:
|
Ah, I hadn't seen that PR (it wasn't linked from this ticket before). I do think being able to do a one-off payin in BTC is a different use case from repeated payments (which require a Coinbase account), but I guess repeated payments take priority for Gittip. |
No more bitcoin, closing this. |
More info at gratipay/inside.gratipay.com#201 (comment) |
Please add support for automate bitcoins payins.
Did you help close this issue? Go claim the $15 bounty on Bountysource.
The text was updated successfully, but these errors were encountered: