Skip to main content

Tap-to-Verify: The Next Generation of Payment Card Verification

MRC Vegas 2026
Peyton Chen, Vivian Mak, Jason Gregory
Mar 17, 2026
Presentations
At its core, tap-to-verify is a simple yet powerful solution. It leverages existing NFC (near field communication) technology in EMV-enabled cards, and the NFC readers built into mobile phones (the same ones used for Apple Pay/Google Pay transactions), to read and verify a consumer’s card. The verification occurs through a $0 authentication submitted to the card issuer, using the card data read directly from the phone’s NFC chip. While mobile devices have previously been used as payment terminals (e.g., a farmer’s market vendor accepting tap-to-pay), they have not been used in reverse—where a merchant leverages a customer’s phone to prove the customer truly possesses the card they’re attempting to use. Until now, card scan has been the main “proof of payment” challenge available for combating chargebacks and assessing risk on questionable transactions. However, card scan relies on machine vision, which is increasingly undermined by generative AI’s ability to create convincing synthetic images. This motivated the need for a non-visual, deterministic way to prove card ownership. Tap-to-verify solves this with a straightforward secure card fingerprint comparison: verifying that the card tapped on the phone is the same card used in the card-not-present (CNP) transaction, via a $0 authentication. The resulting transaction is still processed as CNP—but this opens the door to discussions of a potential third category of transactions that sit between card-present (CP) and CNP.

Some content is hidden, to be able to see it login here Login

Tagged:
Blue-tinted background of a man watching a webinar

Host a Webinar with the MRC

Help the MRC community stay current on relevant fraud, payments, and law enforcement topics.
Submit a Request

Publish Your Document with the MRC

Feature your case studies, surveys, and whitepapers in the MRC Resource Center.
Submit Your Document
/Related Resources/Default/DefaultMarkup(3,67) : error : Cannot get the member i_datasource.Heading for a null object.