Skip to main content

NETELLER - Privacy and security design flaw

Yesterday, colleague of mine brought to my notice about a payment system called NETELLER and it's merchant API named NETELLER Direct API V4.

This NETELLER Direct API V4, helps the merchant to collect amount from users. It's simple--same just like early Authorize.net, along with the required amount you collect the user's id and password and post them to their API URL and they'll send you back with success or error codes in XML format.

The major problem with these types of system is security and privacy--you lose both as you're forced to type your username and password in alien web page. If I remember right, this is was the case with Authorize.net and they changed their design to something like PayPal. The PayPal design is somewhat better as you never type or forced to type your username and password in other alien web pages.

The alien merchant web page uses NETELLER Direct API V4 is forced to get user's NETELLER account and password. I'm much sure that the alien website will obviously store such info--but what if they tried to access user's NETELLER account?

The funniest part of this NETELLER design is that they call it more secure and in their security page they advice "Never share your NETELLER Password or Secure ID with anyone. You will never be asked to disclose your password or Secure ID by a NETELLER representative or anyone affiliated with NETELLER."

Beware of NETTELLER!--until they fix their design flaw.

Comments

Popular posts from this blog

Madurai food Vs Nagercoil food

There's huge cry that Madurai idlis are best. Having stayed in Madurai for 7-years, I can give assurance that they're crap. Madurai foods (especially available in hotels) are of poor hygiene and poor in taste. But, I always like the people--they're friendly and helping. My favorite is always Azad Hotel's (Nagercoil, near Tower Junction) chicken kothu parotta . Nagercoil food like aviyal , samba (red) rice , etc are always good and healthy as they're cooked in coconut oil and with high hygiene--even in hotels.

Solved: "Ports" Tab Not Visible in VS Code (WSL2)

None of the solutions I found on Reddit or GitHub worked, and most of the related GitHub issues were locked. So I'm documenting this here for future reference. Problem When using WSL2 in Visual Studio Code, the Ports tab—needed to access your application in Windows browsers like Chrome or Edge—doesn't appear. Even the Ports-related options are missing from the Command Palette. Solution After a lot of trial and error, here's what worked: Run npx serve in the VS Code terminal. It will output a URL such as http://localhost:3000/ . Click the link (or use the Follow Link option). This will open the app in your default browser. You may notice that it opens on a different port (for example, http://localhost:64198 ). At this point, the Ports tab becomes available in VS Code. After this initial trigger, the Ports tab seems to remain available in future VS Code...