Last week there was a story in the New York Times about Sberbank, Russia's largest retail bank, intending to roll out new ATMs that will have built-in lie detectors  as a way to prevent customer credit card fraud.

According to the Times, "Consumers with no previous relationship with the bank could talk to the machine to apply for a credit card, with no human intervention required on the bank’s end."

The ATM will scan a person's passport, take their fingerprints as well as perform a 3-D scan of the person's face. Next, the ATM will ask a series of questions concerning the person's employment or debts, and voice-analysis software will then indicate whether the person is being truthful or not. The software is said to detect "nervousness or emotional distress" which might mean the person is "dissembling." The bank will use the information gathered, along with other information including the person's credit history, to decide whether they get a credit card.

Sberbank, which has the Russian government as its majority owner, says it will follow all applicable privacy laws.

According to the Times article, credit approval by ATM already is a "fact of financial life in Turkey."

In 2009, I blogged about the largest retail bank in South Africa, Absa, rolling out ATMs that will pepper spray a person if they try to tamper with it in some way
 
I wonder how long it will take before a lie-detecting, pepper spraying ATM is deployed somewhere.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
Vertical
A plate of spaghetti made from code
Shira Inbar
DarkBlue1

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less
{"imageShortcodeIds":["31996907"]}