Warning: session_start(): open(/tmp/sess_uk63q00q4fv3kt3mrhto0u2is3, O_RDWR) failed: Disk quota exceeded (122) in /home/virtualw/public_html/session.php on line 1

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/virtualw/public_html/session.php:1) in /home/virtualw/public_html/session.php on line 1

Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /home/virtualw/public_html/Archive/IndividualNews.php on line 12
VWN News: Bitcoin shows staying power as online merchants chase digital sparkle
Untitled Document
Not a member yet? Register for full benefits!

Username
Password
 Bitcoin shows staying power as online merchants chase digital sparkle

This story is from the category Business
Printer Friendly Version
Email to a Friend (currently Down)

 

 

Date posted: 28/08/2014

Bitcoin is catching on at U.S. online merchants including Overstock.com and Expedia, as customers use a digital currency that just a few years ago was virtually unknown but is now showing some staying power.

Though sales paid for in bitcoin so far at vendors interviewed for this article have been a fraction of one percent, they expect that as acceptance grows, the online currency will one day be as ubiquitous as the internet.

“Bitcoin isn’t going anywhere; it’s here to stay,” said Michael Gulmann, vice president of global products at Expedia Inc. in Seattle, the largest online travel agent. “We want to be there from the beginning.” Expedia started accepting bitcoin payments for hotel bookings on July 11.

Until recently a niche alternative currency touted by a fervent group of followers, bitcoin has evolved into a software-based payment online system. Bitcoins are stored in a wallet with a unique identification number and companies like Coinbase and Blockchain can hold the currency for the user.

When buying an item from a merchant’s website, a customer simply clicks on the bitcoin option and a pop-in window appears where he can type in his wallet ID number.

Still, broad-based adoption of bitcoin is at least five years away because most consumers still prefer to use credit cards, analysts said.

“Bitcoin is a new way of making payments, but it’s not solving a problem that’s broken,” said George Peabody, payments consultant at Glenbrook Partners in Menlo Park, California. “Retail payments aren’t broken.”

There are also worries about bitcoin’s volatility: its price in U.S. dollars changes every day. On Wednesday, bitcoin was up 0.4 percent at $514.09.

That risk is borne by the consumer and the bitcoin payment processor, such as Coinbase or Bitpay, not the retailer. The vendor doesn’t hold the bitcoin and is paid in U.S. dollars. As soon as a customer pays in bitcoin, the digital currency goes to the payment processor and the processor immediately pays the merchant, for a fee of less than 1 percent.

“We don’t have to deal with the actual holding of the bitcoin: it’s the payment processor that takes the currency risk for us,” said Bernie Han, chief operating officer at Dish Network Corp, in Englewood, Colorado. “That’s what makes it appealing for us and I guess for other merchants as well.”

See the full Story via external site: newsdaily.com



Most recent stories in this category (Business):

14/12/2016: UK: Amazon makes first drone delivery

09/11/2016: GoPro recalls drone after power failure

16/09/2014: Airware’s operating system makes drones simple to build and modify for multiple applications

10/09/2014: Barclays taps vein biometrics in bank fraud fight

28/08/2014: Bitcoin shows staying power as online merchants chase digital sparkle

02/10/2013: Telecommuting can be beneficial for a work/life balance

07/09/2013: Nintendo faces 'path to irrelevance', says Atari founder

14/06/2013: Smart technology makes its way into lighting



Warning: Unknown: open(/tmp/sess_uk63q00q4fv3kt3mrhto0u2is3, O_RDWR) failed: Disk quota exceeded (122) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0