So, I need to verify my account by logging with my PayPal verified account before to pay with Bitcoin?

I tried to buy some services from a telecallmart.com (phone number with voicemail). They accept Bitcoin. But in order to pay with Bitcoin, the customer need to make his first payment with PayPal "for verification". They don't realize that Bitcoin payments are irreversible and "friendly fraud" with Bitcoin is impossible. From their TOS:
All users are required to verify their accounts before their orders are provisioned. This is done for security purposes and to help us combat fraud. This is a one time procedure. Users who are PayPal verified are exempt from the rule and require NO manual verification.
So, you need to send them your government issued ID and risking identity theft (they cannot keep your scanned ID safe from hackers - nobody can) if you don't want to use PayPal. Also from their homepage:
NO LONGER do you need to login to PayPal every time you buy or renew products on the site. Just complete the first transaction in PayPal and all future ones will be done on the site ONLY!.
So, it is good news? No need to login to PayPal every time? Only once? Even if you want to use Bitcoin, you still need verified PayPal account (if you don't want to risk identity theft and send your ID over Internet)? I tried to pay with my PayPal account, but it did not worked - PayPal don't allow me to pay with PayPal balance. When I click on "Continue" it is asking me for CC again (and I don't want new CC, I don't want to support the Visa/MasterCard cartel):

Comments

Post a Comment

Popular posts from this blog

[fixed] "Evolution is currently offline due to a network outage."

Evolution is currently offline due to a network outage. Evolution will return to online mode once a network connection is established. If you have this error when updating your system (for example, from Ubuntu 14 to Ubuntu 16), the solution is to run Evolution with this command: evolution --force-online That is usually related to a combination of evolution, dbus, and NetworkManager. With all three installed the idea was that NM would say whether it had a working network or not over dbus. Tools like evolution would ask on dbus about the state of the network and switch to online or offline as networks were hotplugged. This breaks down when the network isn't managed by NM but NM is still running. Such as when /etc/network/interfaces is configured to use ifupdown instead. If NM is running then it won't have any networks under its control and it fails to recognize that the system does actually have a network running outside of its control. It will respond to evolution
Read more

Do not use (only) flash memory (SSD drives, hardware wallets, USB flash drives) for your precious private keys!

Image
Flash memory is not a reliable medium for archives. Especially when there is no regular power. I have personal experience with usb flash drive not powered for weeks - one file became corrupted . (Read more here: Archiving private keys - TLDR version. ) You should always back up on paper and other mediums. Flash memory is prone to failure if it is not powered for weeks or more and if there are ionizing radiation When you write your precious private keys you should use technologies like Parchive and ZFS . And make several copies of your files. It's OK if you use your USB flash drive for another backup, but don't rely on it! Always back up on DVDs (even small files!), paper and online (after encryption with CPU and RAM intensive key derivative function like scrypt). Here is example of using the scrypt utility: $ sudo apt-get install scrypt $ scrypt enc -M 1073741824 -t 200 secret.txt encrypted.scrypt Do not use default values of "-M" and "-t", they
Read more

Archiving private keys - TLDR version

0. Make multiple encrypted copies. On DVDs (they are better than CDs and Blu-Ray discs; DVD+R are better than DVD-R), paper, cloud services like DropBox, OneDrive, Google Drive, e-mail it to yourself and to your friends, use P2P storage services like MaidSafe, Storj and Sia , etc. 1. Use proper font when printing PGP encrypted keys on paper. 2. Flash memory (SSD, USB flash drives, hardware wallets) is less reliable when not powered regularly (i.e. every week). 3. Use error correction methods like Parchive and ZFS. 4. Print on paper or store on digital media only encrypted data. 5. Your encryption software should use CPU/RAM-intensive KDF (i.e. scrypt with secure options - do not use defaults! ). First, encrypt with scrypt and then encrypt it again with PGP (using different password!) in ASCII armor mode before print it (other methods like QR codes may not be reliable as multiple copies of the PGP ASCII armor). Do not use the same password for the PGP because it's easy to brute
Read more
[ad removed]