|
|
|
|
|
by cca
4193 days ago
|
|
(Christian from Stripe here.) Thanks for the clear description. In Stripe's case, this arbitrage won't work. When we refund a bitcoin payment, we refund the USD value of the payment (converted to bitcoin at the time of the refund). The customer does not necessarily receive the same bitcoin amount that they sent. For example:
(1) At the initial time, each bitcoin is worth 100 USD. A Stripe user accepts a 10 USD payment (0.1 bitcoin).
(2) Bitcoin then increase in value to 1,000 USD each. The Stripe user fully refunds the payment. Their customer receives 0.01 bitcoin (10 USD). The Stripe user and their customer both have a net of zero USD in this scenario. We could have implemented refunds in the opposite way: a net of zero BTC and non-zero USD. However, that would have introduced the issue that you describe. |
|
- You have 0.1 BTC and wish to protect against BTC value loss vs USD - You make a payment to your own Stripe account of 0.1 BTC, say 10 USD - After BTCUSD falls, you refund the payment - You receive 10 USD, say 0.2 BTC - End result: you can keep your Bitcoin constant at 10 USD, redeemable into BTC whenever you make the refund request
Of course it would be just as easy to keep the money in USD/your stable currency of choice in the first place and convert when you want BTC; and Stripe won't lose more than BTC conversion fees (unless Stripe decide to hold BTC as a corporation). Out of curiosity, do you have a time limit for refunds?