[ecspike]

Chip + Signature depends on the venue which makes it really annoying.

Went to a new city, one place out of the four I visited required a signature, the rest were fine with tap to pay/chip+Pin. Some places are fine until some arbitrary limit, etc. The place that made me sign? The purchases were $5-$6.

[rswail]

Chip + Signature is a dumb USian thing because merchants didn't want to change their readers to have a secure PIN pad.

Contactless has different floor limits than Contact (chip). For example, in AU, the limit for contactless without PIN is ~AUD100. In the UK, I believe its GBP30.

If you tap for a payment over that limit, the reader will ask for the PIN.

The primary difference is that if a customer uses contactless/contact and PIN, then the risk of the transaction is passed to the network/issuer, instead of the merchant.

[oakesm9]

The UK has a limit of £100 for contactless cards, with a requirement to insert and enter your PIN after a few successive taps. Apple Pay and Google pay technically don’t have the PIN requirement as they’re authenticated and technically don’t have a limit, but in practice most shops still have a £100 limit.

[disruptiveink]

It depends on the POS configuration/support of CDCVM (Consumer Device Cardholder Verification Method). If it doesn't support it, Apple Pay/Google Pay is just a regular EMV contactless card from the POS's perspective, so the regular limits apply.

On some POSes, you can get a hint of when the POS either doesn't understand CDCVM or isn't configured to verify it when you tap with Apple Pay/Google Wallet and you get back a "Cardholder Device Not Verified" on the receipt.

Obviously ultimately, even with CDCVM support, it's up to how things are configured, but in the UK at least, every single POS I've seen that returns "Cardholder Device Verified" will let transactions through the same way as if you did Chip+PIN.

[PlutoIsAPlanet]

> but in practice most shops still have a £100 limit.

I've not found this to be the case anymore, sometimes the terminal will display a limit or the merchant will believe the limit applies to phones, but no limit is technically enforced.

[ldrndll]

In my experience few merchants limit Apple Pay to the contactless limit (Tesco being a notable exception) but many of the times I’ve used Apple Pay for larger purchases the person helping me has been surprised that it worked.

[sksksk]

I once paid for a car with Apple Pay (it was far over the £100 limit)

[rmccue]

> with a requirement to insert and enter your PIN after a few successive taps

Specifically, I believe this was due to Strong Customer Authentication laws in the EU: https://www.visa.co.uk/partner-with-us/payment-technology/st...

[shawabawa3]

> but in practice most shops still have a £100 limit

Not true, although shop keepers will often say it won't work, right up until I tap and it works

[JumpCrisscross]

> Chip + Signature is a dumb USian thing because merchants didn't want to change their readers to have a secure PIN pad

Americans don't want to punch in a PIN. We have more cards per capita and are habituated to the convenience of a swipe. (Unlike much to the world, our fraud risk sits almost entirely on the merchant side.)

Contactless had no hope with a PIN. Merchants catered to that despite higher cost and risk.

[messe]

> Contactless had no hope with a PIN

I’m not sure if it’s true for all EU countries and banks, but in general you don’t put in your PIN every time with contactless. The card usually works for a number of transactions without a PIN, often up to a certain limit, after which it asks you to insert it again.

[JumpCrisscross]

> in general you don’t put in your PIN every time with contactless

As an American, I never get prompted in Europe for a PIN. Even for large transactions. That matches a swipe's convenience.

[djxfade]

I believe this is controlled by your issuer. So your card issuer probably don't require PIN after n amount of swipes.

[matthewdgreen]

It is arbitrary and random. Some machines will ask for it and others won’t. Some automated machines will refuse US cards altogether. Wait til you’re at a tollbooth entering the Autoroute trying to use all your US cards, and none of them are accepted.

[neilalexander]

> Americans don't want to punch in a PIN. We have more cards per capita and are habituated to the convenience of a swipe.

When Chip + PIN was introduced in the UK in 2003, people were widely concerned about the potential for inconvenience (entering a PIN takes longer than a swipe, the transaction might take longer to be processed, you might forget the PIN altogether).

In reality, fear outweighed the reality, the world carried on as usual and people adapted very quickly. It's now just totally normal here to enter a PIN and the average British person would feel far more inconvenienced if asked to sign for a transaction instead (which has become such a rare event here that the average person would be completely taken by surprise if asked to do so).

[rswail]

Unlike most of the world, where when a Chip+PIN or contactless payment is made, where the risk is transferred from the merchant to the acquirer/issuer.

That was the whole point of moving to EMV, it removes the fraud risk from the merchant.

That's different to the charge-back risk, which is where the customer disputes the transaction itself.

[JumpCrisscross]

> where when a Chip+PIN or contactless payment is made, where the risk is transferred from the merchant to the acquirer/issuer

In parts of the world where the consumer's bank bears the risk, and there is in imbalance between commercial and consumer banking, there is a powerful group--consumer banks--to apply pressure.

Sometimes that results in fewer consumer protections. In most: indirect pressure on merchants. (I can think of no country with an imbalance in favor of commercial banking with a strong consumer sector.) This state describes most of the world: optimized for cost reduction.

> That was the whole point of moving to EMV, it removes the fraud risk from the merchant

Who bears fraud risk varies.

In America, it was always the merchants. They have limited leverage over Visa and Mastercard. With the banks neutral and a valid competitor in American Express, there was nobody who wanted to anger consumers by taking away their swipes. (If you're that merchant, you're cash only.) So they optimized for purchasing convenience.

Australia is a cost optimizer. America a convenience optimizer.

[rswail]

I'd argue the opposite. In the US, the merchants had too much power to delay the introduction of Chip+PIN readers.

The fraud of magstripes was huge, because there was literally no security. Anyone could create a magstripe. Customers using credit cards in the US are protected by legislation against that fraud.

The whole point of EMV was to remove the capability of fraud by replicating the magstripe. It meant that the transaction could correctly tell between "card present" and "card not present" transactions. So the risk of card-present transactions is dramatically lowered, independent of who is responsible for the fraud.

It is to both the merchants and the banks benefit to reduce/remove fraud. The banks offloaded it to the merchants in the US (as they did in other countries), but the introduction of EMV was "sold" to the merchants in the rest of the world by the banks saying they would take on the risk of fraud for "card present" transactions.

The banks were never "neutral" in the US. Visa/MC were both bank consortiums.

America is not a "convenience optimizer" its a "changing consumer behavior is hard so lets not do it" optimizer.

[JumpCrisscross]

> In the US, the merchants had too much power to delay the introduction of Chip+PIN readers

Merchants had more power, but the ultimate deciders were consumers, who have not only a choice in merchants but a choice in cards.

> the risk of card-present transactions is dramatically lowered, independent of who is responsible for the fraud

Nobody cares if business goes down more than the fraud costs.

> Visa/MC were both bank consortiums

This is wrong. American Express is bank-like because it owns its own credit book. Visa and MasterCard are payment processors. They are publicly traded and not bank consortiums. This is crucial to understanding the power dynamic: the payment processors do not take diktats from the banks.

> America is not a "convenience optimizer" its a "changing consumer behavior is hard so lets not do it" optimizer

Sure. Friction avoided for not being worth the trouble is optimising for convenience.

I can personally tell you that had a card gone chip + PIN mandatory, I’d have dropped it, and if a merchant started requiring special payment requirements I’d expect compensation for the trouble. Many merchants, notably Starbucks, did this, but it could never go mainstream. And unlike countries where consumer banks were incentivised to lobby for reforms, that political will to override the public’s preferences couldn’t exist here.

[CaptainZapp]

Funnily enough my card doesn't work contactless with PIN. I need to shove it into the chip reader to make it work.

Which, thinking about it, is exactly how it should be.

The closed circuit of chip reader and pin was always touted as super secure. Then suddenly, you could pay contactless with most cards regardless of the amount and enter the PIN. Too me this always seemed to subvert the "super secure" chip & PIN authentication.

It's a small "hardship", really. On small amounts contactless works just dandy and having to present the physical card to the chip reader for larger amounts makes me actually feel better.

[Nursie]

> Too me this always seemed to subvert the "super secure" chip & PIN authentication.

Chip and Pin usually implies offline PIN. The terminal supplies the PIN, after a one-way transform of some sort IIRC* to the chip on the card, which then verifies it locally against a stored version of that same hash or whatever.

With contactless you're doing online PIN. The terminal applies a transform and some sort of asymmetric key encryption to the PIN, and this gets sent to your bank. There's nothing any less secure here.

(* I wrote an EMV 'kernel' a long, long time ago, in about 2002, and some more PIN block processing code about 8 years back. So it's been a while!)

[rswail]

Chip + PIN is basically the EMV standard for cards with chips on them (and the small set of connectors for when the card is inserted in a reader).

There is very little difference in the process when using NFC, except that the power to the chip in the card is via the NFC field.

There are some changes to the business rules around processing contactless payments. Although the same floor limits for asking for the PIN for contact and contactless are pretty much the same these days.

[Nursie]

> Chip + PIN is basically the EMV standard for cards with chips on them

Worse than that, it's a marketing name :)

Or it was in the UK. Strictly speaking the cards contain a customer verification method list that gives the terminal the info about whether and in what priority order it should process PIN offline, online, signature or other methods. This method allows american cards to function elsewhere in the world, depending on the terminal risk profile, and euro cards which usually would require a PIN to function in PIN-less US terminals.

> There is very little difference in the process when using NFC, except that the power to the chip in the card is via the NFC field.

Sure, but in contactless EMV there is no user interaction part of the process, so 'offline PIN' is not a possibility. This is because the transaction process would have to halt while the user entered their PIN and continue afterwards. So I'm pretty sure that for contactless transactions there is no offline PIN CVM. The process is also going to be slightly different in that the card/phone doesn't stick around for any post-transaction issuer scripts, and IIRC from the short time I worked on a contactless product, there is only a single application-cryptogram generation phase compared to the two in a chip transaction, though I can't remember the significance of that now!

Or can I ... the second Gen AC phase is where the card signs off on the bank's authorisation of a transaction, if the transaction has gone online. Strictly your chip card can still decline a transaction even if the bank says it's OK. This is missing in contactless flow because, again, it would require the transaction to pause and take longer than a quick wave.

[rswail]

Not entirely true. I've done a contactless payment that was interrupted at the reader and my PIN requested before the transaction was processed.

I didn't need to re-present the card to the reader. It processed the rest of the transaction after the PIN was entered.

[CaptainZapp]

Thanks to both of you for the comprehensive and interesting answers to my potentially "dumb" question.

It's this what makes HN still an outstanding resource and community.

Thanks!

[connordoner]

Out of curiosity, what sort of language would such a kernel be written in?

[rswail]

Whatever the card reader supports. What EMV call a "kernel" is not what a Linux person would call a "kernel". EMV don't really care, what they care about is that the protocols are followed and that the CHD (Card Holder Data) is protected and that the transactions are properly encrypted at rest and in transit.

So you could write it in Visual Basic if you wanted, but your PCI auditor might have a problem with that. :)

As far as I understand it EMV has L1 and L2 "kernels", then there is an "L3" that is acquirer specific.

When a device is "PCI-PADSS" certified, the L1/L2 kernels are what are tested.

When a merchant is PCI-DSS audited, it is a combination of the PCI-PADSS certification for the device, as well as the L3 layer and other business processing rules around handling the CHD (Card Holder Data). The L3 is supplied by the merchant's acquirer (often with the terminal itself) and the acquirer has had the device validated as part of their PCI audit.

EMV L1 Kernel: The "app" that understands the EMV protocol and data exchanges ("APDUs") between the reader and the card. The equivalent of the PHY chip and ethernet frame handler in ethernet.

EMV L2 Kernel: The "app" that understands the EMV business rules and processing of transaction. The equivalent would be the IP layer in networking land.

EMV L3 Kernel: The specific "acquirer" rules, eg, there is a BIN (Bank Identification Number) accept/deny list that an acquirer will accept. It also has other rules about limits etc that the acquirer imposes. The equivalent would be IPTables in Linux.

[Nursie]

PCI-PTS is another one we were concerned with as a terminal vendors, which involved a bunch of stuff around tamper-proofing and tamper-evidence, as well as vetting the cryptographic algorithms in use, some level of source code security evaluation etc. Complicated old business.

I was very proud when my security library, including implementations of all sorts of ANSI X.9 standards, derived-unique-keys-per-transaction, a keystore that was destroyed on tamper, secure program code update mechanisms etc etc passed certification, on a device with 128k of SRAM and 256k of program memory.

Shame it never made it to market. Stupid unicorn company taking on tens of millions in debt and then exploding... still, I got a few trips to China out of it.

[Nursie]

So the 'kernel' I wrote was not the one running on the card. 'In the Industry' (which sounds so pretentious!) the core of the EMV logic that runs on a terminal is often referred to as the kernel. It's not much like a real OS kernel!

The kernel I wrote in about 2002/3 was in C and allowed a PC using a dumb reader (with secure PIN pad) to run the transaction, on Windows, Linux or (shudder) Unixware at the time.

Years later in 2014 when I worked on a terminal product the company had bought in a third party kernel, also written in C to run on an embedded MIPs board. There was a platform SDK and a custom gcc variant to build bare-metal executables. You bootstrapped the kernel by passing it a malloc implementation and a couple of hooks to other things like accelerated crypto functions etc, and it provided an API to run the transaction.

I also worked briefly on a contactless terminal product in 2012, which IIRC was C and C++ (old-skool C-like C++) on a proprietary OS of some sort, and they were moving to embedded linux on ARM at the time.

(edit - See also rswall's parallel answer, it's very good. I wrote an EMV L2 kernel in that parlance, and interacted with another.)

[KyeRussell]

Those “22 trillion devices that run Java” have to come from somewhere :)

[rswail]

There's basically no difference in the "security" of using the card physical contacts to power/communicate with the on-card chip vs using NFC for the same thing.

What is secure is not about the communications, it's about what information is exchanged, how the dynamic CVV is generated and used, how the PIN is validated in a Chip+PIN environment.

The PIN pad, where you enter the PIN is just as secure using the contacts or contactless. The PIN doesn't leave the PIN pad in the clear.

[feygeubdjvf]

> Chip + Signature is a dumb USian thing because merchants didn't want to change their readers to have a secure PIN pad.

there's a write up on this that i cannot find. the reason was actually that some criminal organization with ties to lots of political pacs had their money cow being fraud (or money laundering) on gas stations. so they forced gas stations to never update the pins for this very specific reason.

[ThePowerOfFuet]

>If you tap for a payment over that limit, the reader will ask for the PIN.

This is country-dependent; while this is the case in Spain, it's not the case in France, where the terminal will insist the card be inserted and the PIN entered.