Thanks Eric. This well-captures what we hope to do. Please drop me a message at christian@stripe.com -- I'd love to talk about how our projects can work together.
The article's main concern is that "decline of religiosity has probably led to increased loneliness". The loneliness concern doesn't seem to resonate with the commenters here, so I dug in to the article's footnoted…
It's a good question. We want Bitcoin acceptance to be straightforward for our users, so we deal with a failed confirmation on our side. We do not debit the user.
(I work at Stripe.) We love the PaymentProtocol, and we have an integration internally. Because the protocol is fairly new, we want to gauge demand from our users before exposing the extra infrastructure.
(Christian from Stripe here.) We credit USD to our user's account when we see a transaction that we believe will become confirmed. The time-delay between when the customer pushes the transaction and when we notify our…
(As an aside, Stripe prices bitcoin payments at 0.5% rather than 3%.) I don't follow your description of Case 1. On Dec 18, to use the timing from your example, you have two options: (a) keep the $380 object (b)…
If you were using your testmode keys, then we would not generate a valid bitcoin address (to avoid all kinds of confusion). It must be the case that these were your livemode keys. If you're able to reproduce an…
(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…
(Christian from Stripe here.) Our users tend to want unified behavior across payments of all different types. Of course, it's possible to filter by payment type in the API, dashboard, and data exports. To the original…
Thanks Eric. This well-captures what we hope to do. Please drop me a message at christian@stripe.com -- I'd love to talk about how our projects can work together.
The article's main concern is that "decline of religiosity has probably led to increased loneliness". The loneliness concern doesn't seem to resonate with the commenters here, so I dug in to the article's footnoted…
It's a good question. We want Bitcoin acceptance to be straightforward for our users, so we deal with a failed confirmation on our side. We do not debit the user.
(I work at Stripe.) We love the PaymentProtocol, and we have an integration internally. Because the protocol is fairly new, we want to gauge demand from our users before exposing the extra infrastructure.
(Christian from Stripe here.) We credit USD to our user's account when we see a transaction that we believe will become confirmed. The time-delay between when the customer pushes the transaction and when we notify our…
(As an aside, Stripe prices bitcoin payments at 0.5% rather than 3%.) I don't follow your description of Case 1. On Dec 18, to use the timing from your example, you have two options: (a) keep the $380 object (b)…
If you were using your testmode keys, then we would not generate a valid bitcoin address (to avoid all kinds of confusion). It must be the case that these were your livemode keys. If you're able to reproduce an…
(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…
(Christian from Stripe here.) Our users tend to want unified behavior across payments of all different types. Of course, it's possible to filter by payment type in the API, dashboard, and data exports. To the original…