Visa confirms Coinbase wasn’t at fault for overcharging users
Yesterday, we wrote that Coinbase customers were being charged multiple times for past transactions.
While some speculated that the erroneous withdraws were down to a Coinbase engineering issue, Coinbase issued a statement saying it wasn’t liable for the duplicate charges. The blame, instead, rested with Visa for the way it handled a migration of merchant categories for cryptocurrencies, Coinbase said.
While you can https://techcrunch.com/2018/02/15/coinbase-blames-visa-for-glitch-that-overcharged-users/ the basic gist is that Visa refunded and recharged (under a different merchant category) a month of old transactions. Many users saw the recharge come through before the refund processed, making it look like they were double charged. Honestly, the issue was likely exacerbated by existing payment rails — it’s normal for refunds to take multiple days to show up on credit and debit statements.
But here’s where it gets weird — this morning Visa https://thenextweb.com/hardfork/2018/02/16/coinbase-visa-overcharging-cryptocurrrency/ shifting the blame back to Coinbase, telling TNW that “Visa has not made any systems changes that would result in the duplicate transactions cardholders are reporting.” We are also not aware of any other merchants who are experiencing this issue.”
But now it seems that the payment giant has revised its stance, and clarified that it wasn’t Coinbase’s fault.
The following is a joint statement from Visa and Worldpay, which is Coinbase’s payment processor partner. While Coinbase initially distributed the statement on its own blog, we’ve also received the statement directly from Visa.
Over the last two days, some customers who used a credit or debit card at Coinbase may have seen duplicate transactions posted to their cardholder accounts.
This issue was not caused by Coinbase.
Worldpay and Coinbase have been working with Visa and Visa issuing banks to ensure that the duplicate transactions have been reversed and appropriate credits have been posted to cardholder accounts. All reversal transactions have now been issued, and should appear on customers’ credit card and debit card accounts within the next few days. We believe the majority of these reversals have already posted to accounts. If you continue to have problems with your credit or debit card account after this reversal period, including issues relating to card fees or charges, we encourage you to contact your card issuing bank.
We deeply regret any inconvenience this may have caused customers.
While the statement doesn’t give a ton of clarity on the issue, it seems to absolve Coinbase of any blame, which is a win for the startup considering it’s been trying to prove to the world that its engineering and customer service teams can stand up to the challenge of maintaining a reliable financial platform.
Indeed, Coinbase CEO Brian Armstrong hit out at media reports that initially placed the blame for the snafu on Coinbase.
The startup — is valued at $1.6 billion after raising $100 million last year — has endured some challenging periods as it continues to scale its service to accommodate its 10 million-plus registered customers.
Issues over the past year have included muddling prices on Overstock.com, a flash crash, and a general struggle to keep up as cryptocurrencies boomed in 2017. In December, Coinbase launched an internal investigation into suggestions that company insiders profited from knowledge of impending support for Bitcoin Cash.
Note: The author owns a small amount of cryptocurrency.
Jon Russell contributed to this story. He also owns a small amount of cryptocurrency.
Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:
https://techcrunch.com/2018/02/16/visa-coinbase-not-at-fault/
Congratulations @akash24! You have completed some achievement on Steemit and have been rewarded with new badge(s) :
Award for the number of posts published
Click on any badge to view your own Board of Honor on SteemitBoard.
For more information about SteemitBoard, click here
If you no longer want to receive notifications, reply to this comment with the word
STOP