| Not a bad idea. There were other issues as well that contributed to the decision, namely: - Legality: there are specific regulations around how employees can be paid. These stem, historically, from companies paying employees in coupons only redeemable at other company stores (think: railroad workers paid in coupons for the general store owned by the railroad. - Reversibility: What happens if the payroll needs to be reversed? With bitcoin you can't. This is important for cases of fraud (e.g. stolen credentials), user error (e.g. mistyping hours worked), or bugs on our end. - Anti-money laundering: We needed to be reasonably sure you weren't laundering money. In case you were, having a bank account makes tracing the money much easier. Coin tumblers and the like make obfuscation and cleaning dirty money trivial. - User adoption and education: How many people really want this feature versus others in the pipeline? If we ship it, what load does this put on our support team to handle calls about bitcoin? About losing their private key? These are a subset. There are many concerns. I hear you about employees taking that money and buying it anyway, but we did have additional concerns to think about. We weren't against crypto, but it wasn't a good fit for our platform, userbase, size, priorities, etc. |