IP Library Granted Patent US 12,288,213
Granted Patent B2
US 12,288,213 · App. 17/696,676 · Granted Apr 29, 2025

Systems, methods and computer program products for secure contactless payment transactions

Inventors: Saurabh Banga (Pune, IN); Lalit Manchanda (Haryana, IN)
Assignee: Mastercard International Incorporated
G06Q20/401G06Q20/3276H04W12/03H04W12/66
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,288,213
App. No.
17/696,676
Granted
Apr 29, 2025
Kind
B2
Abstract

The invention provides methods, systems and computer program products for implementing an electronic payment transaction between mobile communication device and a NFC enabled merchant device, both of which are configured to implement a defined communication protocol. The invention implements the required functionality by (i) receiving a request for a trust token from a merchant device, (ii) determining whether the merchant device is trustworthy, (iii) responsive to a determination that the merchant device is trustworthy, generating and transmitting a first displayable trust token to the merchant device, (iv) receiving a second displayable token from the mobile communication device, (v) comparing the received second displayable token against the first displayable token, and generating a merchant device validation message based on the comparison, and (vi) transmitting the merchant validation decision message to the mobile communication device.

Claims (75)

1. A method for implementing an electronic payment transaction between a mobile communication device configured for implementing a defined communication protocol and a merchant device configured to implement the wireless communication protocol, whereby a trust token server ascertains the reliability of the merchant device prior to transmission of payment information from the mobile communication device, the method being implemented by a processor of the trust token server, comprising:

receiving from the merchant device a request for a trust token, wherein the request is originated by the mobile communication device through a contactless communication channel for the electronic payment transaction between the merchant device and the mobile communication device;

determining whether the merchant device is trustworthy, wherein said determination is based on merchant device data associated with the merchant device;

responsive to a determination that the merchant device is trustworthy, generating a first displayable trust token, wherein the first displayable trust token comprises a token that is encrypted using one or more encryption algorithms or encryption keys, wherein the one or more decryption algorithms or decryption keys corresponding to the first displayable trust token are accessible exclusively to the trust token server;

storing a copy of the first displayable trust token in a database coupled with the trust token server;

transmitting the first displayable trust token to the merchant device through a first network communication channel that is different from the contactless communication channel;

receiving a second displayable trust token from the mobile communication device, wherein the second displayable trust token has been imaged by the mobile communication device from a display coupled with the merchant device;

decrypting the copy of the first displayable trust token and the second displayable trust token using the one or more encryption algorithms or encryption keys to extract information associated with each displayable trust token;

comparing information extracted from the second displayable trust token against information extracted from the copy of the first displayable trust token;

generating a merchant device validation decision message based on the comparison, wherein:

the merchant device validation decision message comprises an indication that the merchant device has been validated as being trustworthy, in response to the comparison resulting in a match decision; and

the merchant device validation decision message comprises an indication that the merchant device has not been validated as being trustworthy, in response to the comparison resulting in a non-match decision; and

transmitting the merchant validation decision message to the mobile communication device through a second network communication channel that is different from the first network communication channel, wherein the trust token server is different from the merchant device and the mobile communication device.

2. The method as claimed in claim 1 wherein the defined communication protocol is a near-field-communication (NFC) protocol.

3. The method as claimed in claim 1 , wherein:

responsive to the merchant device validation decision message comprising an indication that the merchant device has been validated, the mobile communication device proceeds to implement a payment transaction through contactless communication between the mobile communication device and the merchant device; and

responsive to the merchant device validation decision message comprising an indication that the merchant device has not been validated, the mobile communication device terminates the contactless communication session between the mobile communication device and the merchant device prior to:

implementing the payment transaction, or

transmitting payor account information to the merchant device.

4. The method of claim 1 , wherein the first displayable trust token is generated and encrypted to include a set of data parameters associated uniquely with the first displayable trust token.

5. The method of claim 1 , wherein:

the first displayable trust token is associated with a defined time-to-live duration; and

generation of the merchant device validation message is based on determining whether the second displayable trust token is received from the mobile communication device within a time-to-live duration that is associated with the first displayable trust token.

6. A system for implementing an electronic payment transaction between a mobile communication device configured for implementing a defined communication protocol and a merchant device configured to implement the wireless communication protocol, whereby a trust token server ascertains the reliability of the merchant device prior to transmission of payment information from the mobile communication device, wherein the system comprises:

the trust token server comprising a processor and a memory, wherein the processor is configured to:

receive from the merchant device, a request for a trust token, wherein the request is originated by the mobile communication device through a contactless communication channel for the electronic payment transaction between the merchant device and the mobile communication device;

determine whether the merchant device is trustworthy, wherein said determination is based on merchant device data associated with the merchant device;

responsive to a determination that the merchant device is trustworthy, generate a first displayable trust token,

wherein the first displayable trust token comprises a token that is encrypted using one or more encryption algorithms or encryption keys, wherein decryption algorithms or decryption keys corresponding to the first displayable trust token are accessible exclusively to the trust token server;

store a copy of the first displayable trust token in a database coupled with the trust token server;

transmit the first displayable trust token to the merchant device through a first network communication channel that is different from the contactless communication channel;

receive a second displayable trust token from the mobile communication device, wherein the second displayable trust token has been imaged by the mobile communication device from a display coupled with the merchant device;

decrypt the copy of the first displayable trust token and the second displayable trust token using the one or more encryption algorithms or encryption keys to extract information associated with each displayable trust token;

compare information extracted from the second displayable trust token against information extracted from the copy of the first displayable trust token;

generate a merchant device validation decision message based on the comparison, wherein:

the merchant device validation decision message comprises an indication that the merchant device has been validated as being trustworthy, in response to the comparison resulting in a match decision; and

the merchant device validation decision message comprises an indication that the merchant device has not been validated as being trustworthy, in response to the comparison resulting in a non-match decision; and

transmit the merchant validation decision message to the mobile communication device through a second network communication channel that is different from the first network communication channel, wherein the trust token server is different from the merchant device and the mobile communication device.

7. The system as claimed in claim 6 wherein the defined communication protocol is a near-field-communication (NFC) protocol.

8. The system as claimed in claim 6 , wherein:

responsive to the merchant device validation decision message comprising information representing the merchant device as being validated, the mobile communication device proceeds to implement a payment transaction through contactless communication between the mobile communication device and the merchant device; and

responsive to the merchant device validation decision message comprising information representing the merchant device as not being validated, the mobile communication device terminates the contactless communication session between the mobile communication device and the merchant device, prior to:

implementing the payment transaction, or

transmitting payor account information to the merchant device.

9. The system as claimed in claim 6 , wherein the merchant device data includes any one or more of state data, historical data, parameter data, operating system data, device data, application integrity data, and operating system reliability state data corresponding to the merchant device.

10. The system as claimed in claim 6 , wherein one or both of the first displayable trust token and the second displayable trust token comprise any of an optically displayable token, an optically imageable token, a pictogram, icon, image, bar code, optical code, data matrix code, or a quick-response (QR) code.

11. The system as claimed in claim 6 , wherein the first displayable trust token is generated and encrypted to include a set of data parameters associated uniquely with the first displayable trust token.

12. The system as claimed in claim 6 , wherein:

the first displayable trust token is associated with a defined time-to-live duration; and

generation of the merchant device validation message is based on determining whether the second displayable trust token is received from the mobile communication device within a time-to-live duration that is associated with the first displayable trust token.

13. A non-transitory computer readable medium for implementing an electronic payment transaction between a mobile communication device configured for implementing a defined communication protocol and a merchant device configured to implement the wireless communication protocol, whereby a trust token server ascertains the reliability of the merchant device prior to transmission of payment information from the mobile communication device, the non-transitory computer readable medium having a computer readable program code embodied therein, the computer readable program code comprising instructions for:

receiving from the merchant device a request for a trust token, wherein the request is originated by the mobile communication device through a contactless communication channel for the electronic payment transaction between the merchant device and the mobile communication device;

determining whether the merchant device is trustworthy, wherein said determination is based on merchant device data associated with the merchant device;

responsive to a determination that the merchant device is trustworthy, generating a first displayable trust token,

wherein the first displayable trust token comprises a token that is encrypted using one or more encryption algorithms or encryption keys, wherein decryption algorithms or decryption keys corresponding to the first displayable trust token are accessible exclusively to the trust token server;

storing a copy of the first displayable trust token in a database coupled with the trust token server;

transmitting the first displayable trust token to the merchant device through a first network communication channel that is different from the contactless communication channel;

receiving a second displayable trust token from the mobile communication device, wherein the second displayable trust token has been imaged by the mobile communication device from a display coupled with the merchant device;

decrypting the copy of the first displayable trust token and the second displayable trust token using the one or more encryption algorithms or encryption keys to extract information associated with each displayable trust token;

comparing information extracted from the second displayable trust token against information extracted from the copy of the first displayable trust token;

generating a merchant device validation decision message based on the comparison, wherein:

the merchant device validation decision message comprises an indication that the merchant device has been validated as being trustworthy, in response to the comparison resulting in a match decision; and

the merchant device validation decision message comprises an indication that the merchant device has not been validated as being trustworthy, in response to the comparison resulting in a non-match decision; and

transmitting the merchant validation decision message to the mobile communication device through a second network communication channel that is different from the first network communication channel, wherein the trust token server is different from the merchant device and the mobile communication device.

14. The non-transitory computer readable medium of claim 13 , wherein the defined communication protocol is a near-field-communication (NFC) protocol.

15. The non-transitory computer readable medium of claim 13 , wherein:

responsive to the merchant device validation decision message comprising an indication that the merchant device has been validated, the mobile communication device proceeds to implement a payment transaction through contactless communication between the mobile communication device and the merchant device; and

responsive to the merchant device validation decision message comprising an indication that the merchant device has not been validated, the mobile communication device terminates the contactless communication session between the mobile communication device and the merchant device prior to:

implementing the payment transaction, or

transmitting payor account information to the merchant device.

16. The non-transitory computer readable medium of claim 13 , wherein:

the first displayable trust token is associated with a defined time-to-live duration; and

generation of the merchant device validation message is based on determining whether the second displayable trust token is received from the mobile communication device within a time-to-live duration that is associated with the first displayable trust token.

17. The method of claim 1 , wherein the merchant device data includes any one or more of state data, historical data, parameter data, operating system data, device data, application integrity data, and operating system reliability state data corresponding to the merchant device.

18. The method of claim 1 , wherein one or both of the first displayable trust token and the second displayable trust token comprise any of an optically displayable token, an optically imageable token, a pictogram, icon, image, bar code, optical code, data matrix code, or a quick-response (QR) code.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 16, 2022
From: BANGA, SAURABH; MANCHANDA, LALIT
To: MASTERCARD INTERNATIONAL INCORPORATED
Reel/Frame 059287/0543 →
Continuity (1)
Related Publication 20230298019A1 · Sep 21, 2023
References Cited (166)
US 6000832A · Franklin · 1999 [cited by applicant]
US 6327578B1 · Linehan · 2001 [cited by applicant]
US 6434238B1 · Chaum et al. · 2002 [cited by applicant]
US 7027773B1 · McMillin · 2006 [cited by applicant]
US 7357309B2 · Ghosh · 2008 [cited by applicant]
US 7657748B2 · Gentry · 2010 [cited by applicant]
US 8720771B2 · MacKinnon · 2014 [cited by applicant]
US 9195984B1 · Spector · 2015 [cited by applicant]
US 9262651B2 · Paulsen · 2016 [cited by applicant]
US 9595030B2 · Ekselius · 2017 [cited by applicant]
US 9674892B1 · Li · 2017 [cited by applicant]
US 9741036B1 · Grassadonia · 2017 [cited by applicant]
US 9774401B1 · Borrill · 2017 [cited by applicant]
US 10496856B2 · Palermo · 2019 [cited by applicant]
US 10706400B1 · Puffer et al. · 2020 [cited by applicant]
US 10902423B2 · Radu et al. · 2021 [cited by applicant]
US 10963871B2 · Safak et al. · 2021 [cited by applicant]
US 11074564B2 · Gurunathan et al. · 2021 [cited by applicant]
US 11080697B2 · Lakka et al. · 2021 [cited by applicant]
US 11080713B2 · Kohli · 2021 [cited by applicant]
US 11093938B2 · Parekh · 2021 [cited by applicant]
US 11107078B2 · Mariappan et al. · 2021 [cited by applicant]
US 11157896B2 · Nwokolo et al. · 2021 [cited by applicant]
US 11301865B2 · Tang · 2022 [cited by applicant]
US 20040019571A1 · Hurwitz · 2004 [cited by applicant]
US 20060049258A1 · Pikivi · 2006 [cited by applicant]
US 20060219776A1 · Finn · 2006 [cited by applicant]
US 20060283960A1 · Top · 2006 [cited by applicant]
US 20070022058A1 · Labrou et al. · 2007 [cited by applicant]
US 20070125840A1 · Law et al. · 2007 [cited by applicant]
US 20080048036A1 · Matsumoto et al. · 2008 [cited by applicant]
US 20080071681A1 · Khalid · 2008 [cited by applicant]
US 20090048971A1 · Hathaway et al. · 2009 [cited by applicant]
US 20090104888A1 · Cox · 2009 [cited by applicant]
US 20100033299A1 · Davis · 2010 [cited by applicant]
US 20110022521A1 · Collinge et al. · 2011 [cited by applicant]
US 20110178884A1 · Teicher et al. · 2011 [cited by applicant]
US 20110184867A1 · Varadarajan · 2011 [cited by applicant]
US 20110215159A1 · Jain · 2011 [cited by applicant]
US 20110238573A1 · Varadarajan · 2011 [cited by applicant]
US 20120036360A1 · Bassu et al. · 2012 [cited by applicant]
US 20120084836A1 · Mahaffey et al. · 2012 [cited by applicant]
US 20120116902A1 · Cardina et al. · 2012 [cited by applicant]
US 20130212025A1 · Tanner · 2013 [cited by applicant]
US 20130262296A1 · Thomas et al. · 2013 [cited by applicant]
US 20130297508A1 · Belamant · 2013 [cited by applicant]
US 20140040139A1 · Brudnicki · 2014 [cited by applicant]
US 20140061302A1 · Hammad · 2014 [cited by applicant]
US 20140138435A1 · Khalid · 2014 [cited by applicant]
US 20140189359A1 · Marien · 2014 [cited by applicant]
US 20140191031A1 · Paulsen · 2014 [cited by applicant]
US 20140258135A1 · Park · 2014 [cited by applicant]
US 20140279556A1 · Priebatsch et al. · 2014 [cited by applicant]
US 20140358777A1 · Gueh · 2014 [cited by applicant]
US 20150032627A1 · Dill et al. · 2015 [cited by applicant]
US 20150032636A1 · Wedekind · 2015 [cited by applicant]
US 20150046339A1 · Wong · 2015 [cited by applicant]
US 20150112870A1 · Nagasundaram et al. · 2015 [cited by applicant]
US 20150137949A1 · Rofougaran et al. · 2015 [cited by applicant]
US 20150142673A1 · Nelsen et al. · 2015 [cited by applicant]
US 20150262180A1 · Hambleton · 2015 [cited by applicant]
US 20150269566A1 · Gaddam et al. · 2015 [cited by applicant]
US 20150294305A1 · Wang · 2015 [cited by applicant]
US 20150302390A1 · Huxham et al. · 2015 [cited by applicant]
US 20150310425A1 · Cacioppo · 2015 [cited by applicant]
US 20160065370A1 · Le Saint · 2016 [cited by applicant]
US 20160071095A1 · Foerster et al. · 2016 [cited by applicant]
US 20160117715A1 · Gross et al. · 2016 [cited by applicant]
US 20160217467A1 · Smets et al. · 2016 [cited by applicant]
US 20160224971A1 · Aabye · 2016 [cited by applicant]
US 20160307186A1 · Noe · 2016 [cited by applicant]
US 20170091758A1 · Kim et al. · 2017 [cited by applicant]
US 20170178090A1 · Sarin · 2017 [cited by applicant]
US 20170330181A1 · Ortiz · 2017 [cited by applicant]
US 20170330184A1 · Sabt · 2017 [cited by applicant]
US 20170344974A1 · Britt · 2017 [cited by applicant]
US 20180005231A1 · Grassadonia et al. · 2018 [cited by applicant]
US 20180047016A1 · Sarin · 2018 [cited by applicant]
US 20180232734A1 · Smets et al. · 2018 [cited by applicant]
US 20180349907A1 · Dixon · 2018 [cited by applicant]
US 20190026716A1 · Anbukkarasu · 2019 [cited by applicant]
US 20190034929A1 · Tang et al. · 2019 [cited by applicant]
US 20190066097A1 · Mackie · 2019 [cited by applicant]
US 20190108462A1 · Deloo · 2019 [cited by applicant]
US 20190075094A1 · Clarke · 2019 [cited by applicant]
US 20190147449A1 · Cole · 2019 [cited by applicant]
US 20190188696A1 · Carpenter et al. · 2019 [cited by applicant]
US 20190205575A1 · Gardiner et al. · 2019 [cited by applicant]
US 20190213585A1 · Patni · 2019 [cited by applicant]
US 20190228408A1 · Sing · 2019 [cited by applicant]
US 20190253434A1 · Biyani et al. · 2019 [cited by applicant]
US 20190318345A1 · Kallugudde · 2019 [cited by applicant]
US 20190362339A1 · Gurunathan et al. · 2019 [cited by applicant]
US 20190392411A1 · Jain et al. · 2019 [cited by applicant]
US 20200009454A1 · Kaiho et al. · 2020 [cited by applicant]
US 20200019961A1 · Silvestre · 2020 [cited by applicant]
US 20200027086A1 · Rao et al. · 2020 [cited by applicant]
US 20200160325A1 · Kim et al. · 2020 [cited by applicant]
US 20200219090A1 · Zarakas et al. · 2020 [cited by applicant]
US 20200265420A1 · Hamdan et al. · 2020 [cited by applicant]
US 20200302441A1 · Collinge et al. · 2020 [cited by applicant]
US 20200410483A1 · Dill et al. · 2020 [cited by applicant]
US 20210012322A1 · Manchanda · 2021 [cited by applicant]
US 20210065156A1 · Kadiwala et al. · 2021 [cited by applicant]
US 20210217005A1 · Mehrhoff et al. · 2021 [cited by applicant]
US 20210287211A1 · Aabye et al. · 2021 [cited by applicant]
US 20220051231A1 · Laracey · 2022 [cited by examiner]
US 20220122081A1 · Wagner et al. · 2022 [cited by applicant]
CN 101192295A · 2008 [cited by applicant]
DE 102011085537A1 · 2013 [cited by applicant]
EP 0919945A2 · 1999 [cited by applicant]
EP 2189934A2 · 2010 [cited by applicant]
EP 2390817A · 2011 [cited by applicant]
EP 3618403A1 · 2020 [cited by applicant]
JP 2008129890A · 2008 [cited by applicant]
JP 2008204248A · 2008 [cited by applicant]
KR 101236544B1 · 2013 [cited by applicant]
KR 1020140008668A · 2014 [cited by applicant]
KR 101502460B1 · 2015 [cited by applicant]
KR 101679783B1 · 2016 [cited by applicant]
KR 20160140216A · 2016 [cited by applicant]
KR 20170058903A · 2017 [cited by applicant]
WO 1997046964A1 · 1997 [cited by applicant]
WO 2001099070A2 · 2001 [cited by applicant]
WO 2003038719A1 · 2003 [cited by applicant]
WO 2008059465A2 · 2008 [cited by applicant]
WO 2010070539A1 · 2010 [cited by applicant]
WO 2010099352A1 · 2010 [cited by applicant]
WO 2010133096A1 · 2010 [cited by applicant]
WO 2013050296A1 · 2013 [cited by applicant]
WO 2013155627A1 · 2013 [cited by applicant]
WO 2016123309A1 · 2016 [cited by applicant]
WO 2016161000A1 · 2016 [cited by applicant]
WO 2017007935A1 · 2017 [cited by applicant]
WO 2018031856A1 · 2018 [cited by applicant]
WO 2019136044A1 · 2019 [cited by applicant]
WO 2019161003A1 · 2019 [cited by applicant]
WO 2020243286A · 2020 [cited by applicant]
PCT International Search Report, Application No. PCT/GB2017/051818, dated Sep. 1, 2017, 2 pp. [cited by applicant]
EP Communication pursuant to Article 94 (3) EPC; 19184252.5, Aug. 25, 2022, pp. 1-7. [cited by applicant]
EP 19187159.9 European Summons to attend oral proceedings pursuant to Rule 115 (1) dated Jul. 29, 2022, pp. 1-10. [cited by applicant]
PCT International Search Report and Written Opinion; PCT/US2020-039521; Oct. 14, 2020. [cited by applicant]
EPO Office Action; EP 19187159.9; Jun. 8, 2021. [cited by applicant]
EPO Search Report; EP 19187159.9; Apr. 17, 2020. [cited by applicant]
Yingjiu, et al.; A Security-Enhanced One-Time Payment Scheme for Credit Card; 14th International Workshop on Research Issues on Data Engineering; Web Services for E-Commerce and E-Government Applications (RIDE'04); IEEE… [cited by applicant]
EMV MasterCard Contactless Transaction Flow, EMV Level 2 Kernels, https://www.level2kernel.com/emv-mastercard-contactless-transaction.html, 2021, pp. 1-3. [cited by applicant]
EMV Overview—Elavon Developer Portal, https://developer.elavon.com/na/docs/viaconex/1.0.0/emv-integration-guide/3_emv_overview, 2022, pp. 1-33. [cited by applicant]
EMV, https://en.wikipedia.org/wiki/EMV, Wikipedia, Jan. 18, 2022 (last edited), pp. 1-26. [cited by applicant]
Tokenization (data security), https://en.wikipedia.org/wiki/Tokenization_(data_security), Wikipedia, Jan. 8, 2022 (last edited), pp. 1-8. [cited by applicant]
EMV Integrated Circuit Card Specifications for Payment Systems, Book 4 Cardholder, Attendant, and Acquirer Interface Requirements, Nov. 2011, pp. 1-154, EMC Version 4.3 Book 4. [cited by applicant]
A Guide to EMV Chip Technology, Nov. 2014, pp. 1-36, Version 2.0, EMVCo, LLC. [cited by applicant]
Field 55: ICC Data, Elavon Developer Portal, https://developer-eu.elavon.com/docs/eisop/field-descriptions/field-55-icc-data, 2021, pp. 1-11. [cited by applicant]
Terminal verification results, https://en.wikipedia.org/wiki/Terminal_verification_results, Wikipedia, Dec. 12, 2021 (last edited), pp. 1-3. [cited by applicant]
Smart card application protocol data unit, https://en.wikipedia.org/wiki/Smart_card_application_protocol_data_unit, Wikipedia, Aug. 24, 2021 (last edited), pp. 1-3. [cited by applicant]
O. Ogundele, et al.; “The Implementation of a Full EMV Smartcard for a Point-of-Sale Transaction,” World Congress on Internet Security (WorldCIS-2012), Guelph, ON, Canada, 2012, pp. 28-35. [cited by applicant]
EMVco Payment Account Reference (Par): A Primer, Version 1.1, Secure Technology Alliance, Apr. 30, 2018, pp. 1-20. [cited by applicant]
PCT/SG2022/050327 Search Report and Written Opinion dated Dec. 23, 2022, pp. 1-20. [cited by applicant]
PCT/US2022/049771 International Search Report and Written Opinion dated Mar. 20, 2023, pp. 1-19. [cited by applicant]
PCT/US2020/0402061 International Search Report and Written Opinion dated Oct. 21, 2020. [cited by applicant]
PCT/US2021/018344 International Search Report and Written Opinion dated May 27, 2021, pp. 1-11. [cited by applicant]
EP 20159634.3 Extended European Search Report dated Jul. 30, 2020, pp. 1-8. [cited by applicant]
PCT/US2021/042321 International Search Report and Written Opinion dated Nov. 11, 2021, pp. 1-11. [cited by applicant]
GB 2012833.6 Search Report dated Jan. 27, 2021, pp. 1-2. [cited by applicant]
PCT International Search Report and Written Opinion; PCT/US2021/047077; Dec. 14, 2021. [cited by applicant]
EP Search Report; EP 21858781.4; Jul. 12, 2024. [cited by applicant]
SG10202204968V Written Opinion dated Jan. 23, 2025, pp. 1-26. [cited by applicant]