Apologies for the delay, we have been working hard to track this down.
First, to address some of the concerns that members of our community have expressed, we DO use SSL via a secure certificate directly issued by Thawte (do a Google search for Thawte if that is meaningless to you).
Second, we do NOT have any of your personal information. We don't even track or analyze browsing habits haha.
We obviously need to have your email address for recovery and alert purposes. But that is the extent of any information that we have about our users.
We believe is frank honesty, and to that end, we do not know what occurred. Nothing that we have seen during the course of investigation indicates that there is any sort of active security breach. It possibly looks like a very old breach from a few years ago, from what we are seeing.
None of your financial information has ever been in our possession, which is why we use third party processors that are much bigger operations with larger resources than we have.
We do encourage you to update your recovery email addresses (we suggest dedicated email addresses, they are free from basically any service on the planet) and updating your passwords just in case.
We will continue to investigate and report back. In the meantime, please enjoy the holidays!
Welcome to 2020 Unfortunately in this day and age, everyone is a target. Although we do not see any evidence of an actual data breach, based on feedback from the community, something has obviously happened and we are devoting all of our resources to resolving it ASAP. By design from the ground up from the beginning of this community over a decade ago, we intentionally do not house any of your personal or financial data.
We have multiple layers of security measures in play and even our own internal developers can't get into the system without being granted explicit access by us. But again, something has obviously occurred based in the community's feedback so we are looking at everything from the ground up and will report back ASAP.
Apologies for the inconvenience, and we are devoting all of our resources to tracking down the source of this.
Our host screwed up our certificate. But don't worry, we are working on get it working right now.
In the meantime, everything still working. You'll see some broken links here and there. We are working on a temporary solution while our hosting service fixes this.
If you get that error that the site is not secure, that is true. But since you are not sending sensitive our financial information, there's no much to worry about. This system was not using SSL (secure transfer) for a decade before we decided to go that route last year.
Gift Card Changes The Gift Card Company makes changes to the types of cards they accept and the $5 extra charge often.
They do NOT give us any advance notice or even tell us at all. We don't find out about the changes until we see a blog or get a ticket.
We just redid the page and stopped trying to show amounts and cards. When the gift card people change things, our payment page gets confusing.
The real key to it all is check the payment button BEFORE you go and buy a gift card. That way you know you are getting the correct card for the amount you wish to purchase. Check it every time! The card that worked last week might not work this week!
If you see anything on this page that needs corrections or additions or explained better please put in a support ticket.
Or use crypto! It really is fast and easy to do, and they don't charge the site 40% like the gift card people.
BitCoinCash Not 100% sure but BCH might not be a payment option for a week or two.
BTC LTC ETH will be fine (no one really uses BCH here much)
Twice a year, the Bitcoin Cash (BCH) network hard forks as part of scheduled protocol upgrades. The next BCH hard fork is scheduled for this Thursday, Nov 15, 2018.
Unlike previous BCH hard forks, there is a competing proposal that is not compatible with the published roadmap. Coinbase will monitor the hard fork process and work to minimize customer disruption until the network meets Coinbase security standards.
Coinbase previously announced that we would pause sends and receives on the BCH wallets at Coinbase.com, in our iOS and Android apps, and at Coinbase Pro, Prime, and Custody beginning at 8:00AM PST on Thursday, November 15 (approximately 1 hour before the fork).
Due to recent developments, we have now determined that it will be necessary to also pause all buys, sells, and trading of BCH starting at 8:00AM PST on Thursday on Coinbase.com, in the iOS and Android apps, and on Coinbase Pro and Prime. Accordingly, during the time of the pause, you will not be able to sell or remove your BCH from Coinbase. If you wish to have access to your BCH during the pause, you will need to remove it from the Coinbase platform prior.
Please note that Coinbase has no control over the timing of the fork, and therefore cannot provide specific timing for the items below. We will monitor the fork and communicate with our customers promptly and frequently regarding the status of access to BCH. During the fork, we will take the following steps.
Starting at 8:00AM PST on Thursday, November 15, Coinbase will:
Pause sends (withdrawals) and receives (deposits), as well as buys, sells, and trading of BCH;
Take a snapshot of existing BCH balances;
Monitor the fork for network consensus;
When network conditions stabilize, we will notify customers of the expected date and time to re-enable buys, sells, sends, receives, and trading of BCH
Clear order books and re-enable buys, sells, sends, receives, and trading of BCH; and
If another viable chain exists, customers will have the ability to withdraw funds at a future date. We anticipate this will take at least a few weeks, but may take longer.
