(19) United States
`a2) Patent Application Publication co) Pub. No.: US 2013/0048717 Al
`(43) Pub. Date: Feb. 28, 2013
`
`Brendell et al.
`
`US 20130048717A1
`
`(54)
`
`(75)
`
`METHODS AND SYSTEMS FOR
`CONTACTLESS PAYMENTS AT A
`MERCHANT
`
`Inventors: Brian Brendell, Springfield, NJ (US);
`I-Hsin Chuang, Brooklyn, NY (US);
`Carlos Korten, Brooklyn, NY (US);
`Nicole Lewis, New York, NY (US)
`
`(73)
`
`Assignee: American Express Travel Related
`Services Company, Inc., New York, NY
`(US)
`
`(21)
`
`Appl. No.: 13/280,938
`
`(22)
`
`Filed:
`
`Oct. 25, 2011
`
`Related U.S. Application Data
`
`(63)
`
`Continuation-in-part of application No. 13/215,145,
`filed on Aug. 22, 2011.
`
`Publication Classification
`
`(51)
`
`Int. Ch.
`(2012.01)
`G0620/32
`(2012.01)
`G060 20/20
`(52) US. CD.
`ceccscsecsssccsesssssssssssssveesssseesesessensessssn 235/380
`(57)
`ABSTRACT
`A coordination server of a contactless payment system may
`receive a total bill of purchases for a customer from a mer-
`chant POSterminal, associate the total bill of purchases with
`a unique identifier of an RFID tag of a check presenter, and
`receive notification that paymentofthe total bill ofpurchases
`is authorized. The coordination server may receive the unique
`identifier and payment information from a contactless-en-
`abled device, and transmit the payment information and the
`total bill to the merchant POS terminal for transmittal to a
`merchant acquirer for completion ofthe transaction under
`business as usual standards. In one embodiment, the coordi-
`nation server transmits the payment information andthetotal
`bill to a merchant acquirer, which then routes the payment
`request
`to an appropriate payment network.
`In another
`embodiment, the coordination server transmits the payment
`information andthetotal bill directly to the appropriate pay-
`ment network.
`
`
`
`Contactless-enabled device 120
`
`Check Presenter 7110
`
`Merchant system 130
`
`Authorization system 140
`
`Payment network 150
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 1 of 25
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 1 of 25
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 1 of 13
`
`US 2013/0048717 Al
`
`
`
`
`
`OL}JaqueselgyOeUD
`
`JUBYoay/y
`
`
`
`
`
`Of|.wa}shsuolezuoUuny
`
`OSLWaISsAsS
`
`
`
`OSLyJomMjouJuUsWAeY
`
`|ainbi4
`
`aaa2D°3oO
`
`Oo
`
`LLaSs
`
`i®2>Oo
`
`oS©°°o
`9N—°N®D©oO—ai°Oo
`
`
`
`
`
`OZ|,2alaappajqeua-ssayjaeju0D
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 2 of 25
`
`
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 2 of 13
`
`US 2013/0048717 Al
`
`
`
`yomjaujuawAede0}
`
`vO
`
`
`
`BdIABpps|qeus-ssajjoe}uoo
`
`B}]0}Su)JOJUaWAed
`
`
`
`eBulsnjIIq
`
`goz
`
`sawojsng
`JaWOIsnDg E02c0Z
`
`
`
`ueBuiaeyJajuasaidwal}shsJUeYQeyy
`au)uMBe}GiayIllq|2}0]&sayeseueb
`IIIq}e}0}Bu}peo7JE}O}SU}JO}signs
`
`
`1Gye}0}saseuoindaulJoy
`
`yoayaeBajyeloossy
`
`saseyaoind
`
`saalAsas10spoob
`
`JUBYOJEWeWO
`
`LOé
`
`Zain6bl4
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`oS©°°o
`9N—°©®D©oO—ai°Oo
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 3 of 25
`
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 3 of 13
`
`US 2013/0048717 Al
`
`
`
`SdIAepps|qeue-ssayjoejucD
`
`
`
`Yul]YOMJOUBSBAISIOI
`
`Be}QIANeu}Woy
`
`ZOE
`
`Jawojsng
`
`
`
`BdIAappajqeus-ssajjoe}uoS
`
`sde}
`
`joBe}QI4yveYM
`
`
`
`Jajuasaidyoeyoou}
`
`LOE
`
`
`
`joJaynuUsp!anbiun
`
`Be}diseu}
`
`€O€E
`
`
`eBuisnjigsawojsno
`
`
`BY}SAJLDO|YIOMJON
`
`juowAedesjiwqnsJawojysna
`
`
`
`ay}Wojsanba
`
`¢ainbi-
`
`
`
`adIAAaPpalqeue-ssayjoe}UuC]
`
`vOe
`
`aaa2D°3oO
`
`Oo
`
`LLaSs
`
`i®2>Oo
`
`oS©°°o
`9N—°s®D©oO—ai°Oo
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 4 of 25
`
`
`
`
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 4 of 13
`
`US 2013/0048717 Al
`
`
`
`9olAappajqeua-ssajjoejuoD
`
`
`
`Yul]YIOMJAUBSAAIBOSI
`
`apodYOsu}Wo
`
`cOr
`
`
`
`
`
`SpodYH&speelJoWOIsSND
`
`
`
`2UJIMJo]UaseldYOSYDaU}Jo
`
`
`
`SdIABPpa|qeua-ssayjoejuoN
`
`LOV
`
`
`BBuisnjIqJawolsns
`
`dU}SO1}200}YIOMISN
`
`jualwAedes}iuugnsJewojsno
`
`au}Wo}senbe
`
`
`
`josaynuep!enbiun
`
`apodYHau}
`
`cor
`
`panbi4
`
`
`
`SOIASPPa|qeua-ssajjoejuog
`
`vor
`
`aaa2D°3oO
`
`Oo
`
`LLaSs
`
`i®2>Oo
`
`oS©°°o
`9N—°ifs)®D©oO—ai°Oo
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 5 of 25
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 5 of 13
`
`US 2013/0048717 Al
`
`
`
`
`
`yore‘UCISIAIPjenbe4]
`
`
`
`
`Ud|}JDajesJSWo}Ssndsoeekosoeaane
`yejo]
`
`
`UOHEULO;UAyenbajuawAedapiaiq
`
`
`EJUNOUWE|[!qJ€}0}JBSWJO60S
`
`€0SEsjunoweayisads10
`junowuejJuawAedpolisepe
`
`
`
`
`SaplAgidJawO}snoyoeg
`
`+—|{sooInappajqeua-ssayjaeju0o
`
`So,Buisn|gje}0}Apia
`junoweBuiuiewiasJosao!Aap
`
`pe|qeus-ssapaejuooAON
`IlpeysHesJosaciAep
`pa|qeue-ssejoeju0aabuls
`
`
`ULMSJOBIa}UISdIASp
`
`
`
`
`
`juswAedsyilugnseaiAep
`
`
`
`
`
`SPIAIP‘UOISIAIPOYIOedS41
`
`
`
`pezilua}!uopeseqjuaWAed
`
`
`
`JO‘Jsl|aseuoind
`
`
`
`
`
`ésjunoweaplaoidsawiojsna
`
`vos
`
`
`
`papiaoidBuisn}sanba
`
`
`
`c0S
`
`
`
`
`
`JsI]eseyoindpeziway
`
`Jedpapiaip
`
`
`
`
`
`sjunowejsanba:juawAed
`
`
`
`
`
`pasoxeseolaapajdiyjnwiwo
`
`20S
`
`gainbi4
`
`ONfLOS
`
`
`
`Jajyuesaidyosus
`
`80S
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`oS©°°o
`9N—°©®D©oO—ai°Oo
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 6 of 25
`
`
`
`
`
`

`

`Patent Application Publication
`
`Feb. 28,2013 Sheet 6 of 13
`
`US 2013/0048717 Al
`
`Purchases
`
`
`2 a
`
`dsAwa
`“a
`
`38oW
`
`w_
`
`©n®®O
`
`Figure6
`
`
`
`
`
`HerbChicken$16.75
`
`
`
`Ribeye$22.50
`
`
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 7 of 25
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 7 of 25
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 7 of 13
`
`US 2013/0048717 Al
`
`|
`
`
`
`SOMIONJUaWAEY
`
`|!|queyrda|l||
`NVALo]
`
`Zuissac0igjuawAedg
`
`Jauinboy
`
`2asnbiy
`
`uoneulps00}
`
`JOAIIS
`
`OL
`
`oO
`y
`
`
`
`yomyanJe/N|[25
`
`aaa2D°3oO
`
`Oo
`
`LLaSs
`
`i®2>Oo
`
`oS©°°o
`9N—°©®D©oO—ai°Oo
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 8 of 25
`
`
`
`
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 8 of 13
`
`US 2013/0048717 Al
`
`
`
`SISAPUd-yDEgJUBAA|AY19U10.
`
`
`
`
`
`gounbi4
`
`
`
`
`
`JOAIISJUDWAZeULLAIABO
`
`1210
`
`AyyeAoy
`
`JaNas
`
`
`
`dansasAyeAo)
`
`quawAed
`
`
`
`JBAIIS4uawAdeg
`
`pueAqyeAo7
`
`peppy-anyeA
`
`
`
`
`
`JansasjuawAedgquayuo)
`
`HO
`
`Asoysoday
`
`
`
`J@AI3SUOReUIpPsOO}
`
`aaa2D°3oO
`
`Oo
`
`LLaSs
`
`i®2>Oo
`
`oS©°°o
`9N—°o>)®D©oO—ai°Oo
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 9 of 25
`
`
`
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 9 of 13
`
`US 2013/0048717 Al
`
`c--oeooOorree|Spompen
`wawAeg
`
`gaunbi4
`
`
`
`JasinbayJUeYIW]|
`
`SOdWweYyaalNa,||
`
`L06
`
`quowAed
`
`pueAyjeAot
`
`Pappy-onlen
`
`quaquod
`
`
`
`JONASUOI}EUIPIOOZ
`
`
`
`soquasag4994)
`
`i“
`£06
`
`Oo
`r
`
`2O
`
`
`
`OMISNJEIN|AD
`
`v06
`
`Lea>oO--2Da°°°Oo
`
`a2>Oo
`
`oS©°°o
`woN—°Oo=ooD©a—ar=°oO
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 10 of 25
`
`
`
`
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 10 of 13
`
`US 2013/0048717 Al
`
`LOOL
`
`
`
`yOMI2NAE[NaD
`
`SOdweYyWa)
`
`pueAqjeAo7,,uawAed
`Jaqyuasaidyay
`
`
`
`quaysJPeppy-anjeA
`
`JaAlagUONeUIPIO05€001
`
`
`
`SyIOMaNJuaWwAeYg
`
`O}eunbi4
`
`aaa2D°3oO
`
`LLaSOo
`
`i®2>Oo
`
`oS©°°o
`re)N—3<=®D©oO~ai3Oo
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 11 of 25
`
`
`
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 11 of 13
`
`US 2013/0048717 Al
`
`9011
`
`2——
`
`
`
`SyomyanyuawAed
`
`
`
`SOd}ueyusy,|<+—>suauhed
`
`quawAeg
`
`Aenmayeg
`
`
`
`yAomyan4e)N}]9>
`
`
`COLLCOLL/
`
`LOLL
`
`L)eunbi4
`
`pueAyjeAoj
`
`pappy-anjer
`
`
`
`JaAIVSUOIPeUIPIGOD
`
`quajyuoD
`
`
`
`J9JUSSAIgYIOYD=
`
`Poll
`
`ad1AapUOpayeysul
`
`ddyquawAed»
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`oS©°°o
`re)N—3nNx®D©oO~ai3Oo
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 12 of 25
`
`
`
`
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 12 of 13
`
`US 2013/0048717 Al
`
`LOGL
`
`
`
`SOdsueYyIBW|+>
`
`JOAIBgUO!EUIpPsIOO)
`
`cOCt
`
`\uowAed
`
`pueAjjeAo7
`
`pappy-snjeA
`
`yuajuo0g
`
`cbenbiy
`
`
`
`19]U9S31g49949
`
`aysS!}31qe1
`
`cOcl
`
`vOcL
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`oS©°°o
`re)N—°o2®D©oO~ai3Oo
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 13 of 25
`
`
`
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 13 of 13
`
`US 2013/0048717 Al
`
`AMOWAWNIV
`
`
`
`AYOWSWAYVONOOAS
`
`cle
`
`90e1
`
`SAINGMSIGGYVH
`
`PLE
`
`NOILLVOINNANNIOS
`
`AYNLONYLSVSANI
`
`
`
`OlYOSSADOUd
`
`SC
`I
`
`AOVAYSLNIAVIdSIG OLEL
`B01LINNAVIdSid
`LINNJOVHOLSAAGJOVUOLS
`ATEVAOWAYATaAVAOWSY
`ATEaVAOWSYJOvsySLN|
`TETOver
`OCELFEL
`
`LINNASVYOLS
`
`ccel
`
`SNOLLVOINNWINIOO
`
`
`
`8@ElSHLVdeL“Bis
`
`
`
`9ZELSTVNOIS
`
`SNOILVYIINNWINOSD
`
`
`
`veelAOVAYSALNI
`
`vOel
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`oS©°°o
`re)N—3+=®D©oO~ai3Oo
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 14 of 25
`
`
`
`
`

`

`US 2013/0048717 Al
`
`Feb. 28, 2013
`
`METHODS AND SYSTEMS FOR
`CONTACTLESS PAYMENTS AT A
`MERCHANT
`
`CROSS REFERENCE TO RELATED
`APPLICATIONS
`
`[0001] This application is a continuation-in-part applica-
`tion of U.S. application Ser. No. 12/758.942, entitled
`
`“METHODS AND SYSTEMS FOR CONTACTLESS PAY-
`MENTS,”which wasfiled on Aug. 23, 2011, and which is
`herebyincorporated byreference inits entirety.
`FIELD
`
`[0002] The present disclosure generallyrelates to contact-
`less paymentsin a retail environment. Moreparticularly, the
`present disclosure relates to methods, systems and computer
`program products for contactless payments at a restaurant
`merchant.
`
`
`
`BACKGROUND OF THE DISCLOSURE
`
`In a typical merchant transaction at a restaurant, a
`[0003]
`consumerreceivesa bill at the end of the dining experience
`and submits a form of payment. The form ofpayment may be
`cash, check, debit card, charge card or credit card. If a debit
`card or credit card is provided by the consumer, an employee
`takes the card to a point-of-sale terminal and processes the
`card to obtain authorization for receiving payment[orthebill.
`The point-of-sale terminal is generally out of sight from the
`consumer and it takes a period of time for the employee to
`process the card. ‘lhe consumer may be concerned that the
`employee is retaining credit card information while out of
`sight.
`Furthermore, it is very common for a group of con-
`[0004]
`sumersto decide to pay for only a portionofthe total bill. The
`restaurant employee may divide the total bill into multiple
`bills for people to pay, though this takes additional time for
`the employee and increases the chance of making a mistake
`on the bill. Alternatively, the restaurant employee may only
`provide a tolal bill, and then process various amounts on
`multiple cards in orderto satisfy payment. Again, dividing
`paymentofa total bill amongst multiple cards increases the
`risk of a mistake.
`[0005]
`Inlight of the foregoing, there exists a need for a
`system, method and/or computer program product that pro-
`vides a consumer the security of maintaining physical pos-
`session ofa credit card, increases efficiency ofa restaurant by
`lowering bill payment wait times, and decreases the chances
`ofa billing mistake when multiple funding sources are used to
`satisfy payment.
`
`SUMMARY
`
`In various embodiments, a contactless payment sys-
`[0006]
`tem for merchant transactions(c.g., a restaurant), comprises
`generating, at the contactless payment system,a total bill of
`purchases associated with a consumer, associating a unique
`identifier of a radio frequencyidentification (RFID) tag with
`the totalbill, transmitting the total bill and associated unique
`identifier to a consumer accessible payment network, and
`receiving payment from the consumerfor satisfaction of the
`total bill. The consumer may submit the payment using a
`contactless-enabled device,
`such as a smartphone for
`example. The contactless-enabled device mayinterrogate the
`RFIDtag to receive the unique identifier and a payment
`
`network link. Furthermore, the contactless-enabled device
`maysubmit a payment transaction request to the payment
`network, where the payment transaction request includes the
`unique identifier and an account identifier. Additionally, the
`payment network receives the payment transaction request
`and locatesthe total bill using the unique identifier as a key. In
`various embodiments, the RFIDtag is replaced with (or used
`in addition to) a QR code.
`
`In various embodiments, a coordination server of a
`[0007]
`contactless payment system performs operations comprising
`receiving, at the coordination server, a total bill of purchases
`for a customer from a merchant point-of-sale terminal, asso-
`ciating the total bill of purchases with a uniqueidentifier of a
`radio frequency identification tag of a check presenter, and
`receiving notification that payment of the total bill of pur-
`chases is authorized. Additionally, the coordination server
`mayactas the primary coordination point for dividing a bill of
`sale and ensuring that all partial payments by customerssat-
`isfy the total outstandingbill. The coordination server may be
`integrated into the merchant point-of-sale terminal, or the
`coordination server may be separate from the merchantpoint-
`of-sale terminal. In other embodiments,
`the coordination
`server may reside at the merchant’s location, or al an issuer
`facility.
`Furthermore, in various embodiments, the coordi-
`[0008]
`nation server receives the unique identifier of the RFID tag
`and payment information from a contactless-enabled device.
`Thetotal bill maybe located using the uniqueidentifier as a
`key, and the coordination server transmits the paymentinfor-
`mation andthe total bill to the merchant point-of-sale termi-
`nal. The merchant point-of-sale terminal may be configured
`to transmit the payment information and the total bill to a
`merchant acquirer for completion of the transaction under
`business as usual standards.
`
`the coordination
`In various other embodiments,
`[0009]
`server receives the unique identifier of the RFID tag and
`payment
`information from a contactless-enabled device,
`locates the total bill using the unique identifier as a key, and
`transmits the payment information and the total bill to a
`merchant acquirer, which then routes the payment request to
`an appropriate payment network. The appropriate payment
`network is selected based on the payment information from
`the contactless-enabled device. In another embodiment, the
`coordination server transmits the payment information and
`the total bill directly to the appropriate payment network.
`
`To help facilitate the contactless merchant transac-
`[0010]
`tion, an exemplary check presenter apparatus may be used.
`‘The check presenter apparatus may include a radio frequency
`identifier (REID) tag with a unique identifier, where the
`unique identifier is associated with a total bill at a coordina-
`tion server. A contactless-cnabled device in proximity to the
`check presenter apparatus mayread the unique identificr from
`the RFID tag, and transmit payment information and the
`unique identifier to facilitate contactless payment ofthe total
`bill. In various embodiments, the check presenter apparatus
`comprises a quick response (QR) code with a unique identi-
`fier, where the unique identifier is associated with a total bill
`at the coordination server. The contactless-enabled device in
`proximity to the check presenter apparatus may read the
`unique identifier from the QR code, and transmit payment
`information and the unique identifier to facilitate contactless
`paymentofthe total bill.
`
`
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 15 of 25
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 15 of 25
`
`

`

`US 2013/0048717 Al
`
`Feb. 28, 2013
`
`BRIFF DESCRIPTION OF THE DRAWINGS
`
`[0011] The features and advantages of the present disclo-
`sure will become more apparentfrom the detailed description
`set forth below whentaken in conjunction with the drawings,
`in which like reference numbers indicate identical or func-
`tionally similar elements. Additionally, the left-most digit of
`a reference numberidentifies the drawing in which the refer-
`ence numberfirst appears.
`[0012]
`FIG. 1 is an overview of an exemplary system for
`conducting contactless payments in a merchant transaction
`environment;
`[0013]
`FIG. 2 is a flowchart illustrating one exemplary
`process of conducting contactless payments in a merchant
`transaction environment;
`[0014] FIG.3 is an embodimentofa process of conducting
`contactless payments in a merchant transaction environment
`using an RFID tag;
`[0015]
`[TIG. 4 is an embodimentof a process of conducting
`contactless payments in a merchant transaction environment
`using a QR code;
`[0016]
`FIG. 5 isa flowchart illustrating an exemplarypro-
`cess of dividing payment of a payment among multiple con-
`tactless-enabled devices in a merchant transaction environ-
`ment;
`FIG. 6 illustrates an exemplary embodiment of
`[0017]
`facilitating itemized selection of purchases using QR codes;
`[0018]
`FIG. 7 is a flowchart illustrating an exemplarypro-
`cess of conducting contactless payments in a merchant trans-
`action environmentusing a coordination server with payment
`processor:
`[0019]
`FIG.8 illustrates an exemplary embodiment of a
`coordination server;
`[0020]
`FIG. 9 is a flowchart illustrating an exemplarypro-
`cess of conducting contactless payments in a merchant trans-
`action environment using a coordination server;
`[0021]
`FIG. 10 is a flowchart illustrating an exemplary
`process of conducting contactless payments in a merchant
`transaction environment using a coordination server for rout-
`ing payment:
`[0022]
`FIG. 11 is a flowchart illustrating an exemplary
`process of conducting contactless payments in a merchant
`transaclion environment using a payment galeway;
`[0023]
`FIG. 12 is a flowchart illustrating an exemplary
`process of conducting contactless payments in a merchant
`transaclion environmentusing a tablet computer; and
`[0024] FIG.13 isa block diagram ofan exemplary embodi-
`ment of a compuler sysiem.
`
`DETAILED DESCRIPTION
`
`In various embodiments, a system, method and/or
`[0025]
`computer program product for conducting a contactless mer-
`chant transaction is disclosed. Although these exemplary
`embodiments may be used in different merchant environ-
`ments, the embodiments discussed hercin will be described as
`an example with respect to a restaurant environment, though
`not limited to such. FIG. 1 is an overview of an exemplary
`system 100 for conducting a contactless restaurant transac-
`tion. In various embodiments, system 100 comprises a check
`presenter having a radio frequencyidentification (RFID) tag
`110, a contactless-enabled device 120 having consumer
`information, a merchant system 130, and an authorization
`system 140. The check presenter with RFID tag 110 may be
`a standard check presenter, typically a small black bi-fold
`
`holder, which includes an RFID tag. Furthermore, the RFID
`tag may be internal to the check presenter 110 or may be
`removably coupled to the check presenter 110. The RFID tag
`maybe a passivetag that is powered by a nearbyreader, such
`as the contactless-enabled device 120. In various embodi-
`ments, the check presenter 110 is a tablet computer operated
`primary bya touch screen, such as an iPad. Authorization
`system 140 may include anyentity that offers transaction
`account services, suchas a financial institution.
`[0026]
`In various embodiments, system 100 further com-
`prises a payment network 150. The payment network 150
`facilitates receiving payment authorization from one or more
`authorization systems 140, and providing notifications to
`merchant system 130. In various embodiments, payment net-
`work 150 may be a stand-alone network separate from mer-
`chant system 130 and authorization system 140. Furthermore,
`in various embodiments, payment network 150 maybe a part
`ofmerchant system 130 ora part ofauthorization system 140.
`Payment network 150 is a central network which communi-
`cates with various systems and may communicate with con-
`tactless-enabled devices 120. Payment network 150 maybea
`proprietary network operated by merchant system 130 or
`authorization system 140. Moreover, payment network 150
`maybe operated by a third party provider and maybe asso-
`ciated with multiple merchant systems 130 and/or multiple
`authorization systems 140.
`[0027] Merchant system 130 may comprise any type of
`hardware and/or software (e.g., a computer server) config-
`ured or configurable to generate and/or display an invoice for
`services provided or goods purchased. In various embodi-
`ments, merchant system 130 generates the total bill at the end
`of a meal in a restaurant. In exemplary embodiments, cach
`check presenter with RFID tag 110 has a unique identifier.
`The merchant system 130 then associates the total bill with
`the unique identifier of the RFID tag 110. Merchant system
`130 loads the total bill and unique identifier onto a network
`accessible by the consumer. The accessible network may be a
`website operated by the merchant system 130 or a website
`operated by a third party. The merchant system 130 may load
`the total bill to the appropriate check presenter using the
`unique identifier. ‘he unique identifier also helps the mer-
`chant system 130 track receipt of payment for separatebills.
`[0028] Thesystem 100 mayincludeorinterface with anyof
`the foregoing accounts or devices, a contactless-enabled
`device 120 (e.g., an RF device) and RFID tag in communica-
`tion with the contactless-enabled device 120 (which may
`include a fob), or communications between an initiator and a
`target enabled by near field communications (NFC). Typical
`contactless-enabled devices 120 may include, for example, a
`key ring, tag, card, cell phone, wristwatch or any such form
`capable of being presented for interrogation. Moreover, the
`system, computing unit or device discussed herem may
`include a “pervasive computing device,” which may include a
`traditionally non-computerized device that is embedded with
`a computing unit. Examples may include watches, Internet
`enabled kitchen appliances, restaurant tables embedded with
`RF readers, wallets or purses with imbedded transponders,
`etc. Furthermore,a device or financial transaction instrument
`may have electronic and communications functionality
`enabled, for example, by: a network of electronic circuitry
`that is printed or otherwise incorporated onto or within the
`transaction instrument (and typicallyreferred to as a “smart
`card”); a fob having a transponder and an RFID reader; and/or
`near field communication (NI'C) technologies. for more
`
`
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 16 of 25
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 16 of 25
`
`

`

`US 2013/0048717 Al
`
`Feb. 28, 2013
`
`Go
`
`from to make the payment. In exemplary embodiment, the
`information regarding NFC,refer to the following specifica-
`contactless-enabled device 120 is a smart phone with a
`tions all of which are incorporated by reference herein: ISO/
`IEC 18092/ECMA-340, Near Field Communication Inter-
`graphical user interface. Moreover, the consumer accesses
`the total bill and is able to add a tip if desired. The consumer
`face and Protocol-1 (NFCIP-1); ISO/IEC 21481/ECMA-352,
`Near Field Communication Interface
`and Protocol-2
`selects which account is to be used and then proceeds to
`submit payment similar to an online transaction. For addi-
`(NFCIP-2);, and EMV4.2 available at hitp:/Awww.emveo.
`tional
`information regarding contactless payments in an
`com/defaull.aspx.
`online transaction, please see U.S. application Ser. No.
`[0029] With reference to FIG. 2, an exemplary method may
`13/215,111, entitled “METHODS AND SYSTEMS FOR
`include the following steps. Once a consumerfinishes order-
`
`CONTACTLESS PAYMENTS FOR ONLINE ECOM-
`
`ing items from a restaurant 201, the total bill of the items
`
`
`MERCE CIIECKOUT,” filed on Aug. 22, 2011, which is
`purchased during the dining experience maybe generated by
`incorporated byreference.
`a merchant system 202. The merchant system associates an
`RFID tag with the total bill 203, and then loadsthetotal bill
`[0033]
`In various embodiments, a check presenter includes
`onto a consumer accessible payment network 204. Each
`asmart RFIDtag instead of, or in addition to, a passive RFID
`RFID tag may have a unique identifier, such as a serial num-
`tag. The smart RFID tag maybe configured to store one or
`ber, whichis used to associate the RFID tag withthe bill. The
`more of a uniqueidentifier, a transaction identifier, and trans-
`check presenter is given to the consumer, who has multiple
`action information. The transaction information, for example,
`options to pay the total bill. The options include cash, check,
`mayinclude the amount due and merchant information. Inthe
`various embodiments, this additional information allows a
`providing a transaction account card, or submitting payment
`consumerto paythe total bill using a financial institution of
`using a contactless-enabled device 205.
`the consumer’s choosing. For example, the consumer can
`[0030] With reference to FIG.3, in order to submit payment
`provide the information to a personal bank, where the bank
`using the contactless-enabled device, the consumer maypro-
`receives the amount due and the merchant information, along
`vide account information by “tapping” the contactless-en-
`with a consumeridentifier. Once the consumeris identified
`abled device 120 with check presenter having the RFID tag
`and verified, the bank mayapprove the transaction and submit
`110 (step 301). The “tapping” motion means placing the
`payment of the amount due to the merchant of record as
`contactless-enabled device 120 in close proximity to the
`indicated by the merchant information. Such a transaction has
`RFID tag in order for an RF transponderof the contactless-
`additional security in that the consumer’s account numberis
`enabled device 120 to communicate. This may include physi-
`never transmitted during, the processing.
`cally touching the contactless-enabled device 120 to the
`RFIDtag, orat least placing the contactless-enabled device
`[0034]
`In various embodiments, the manner in which the
`120 in close enough proximity to enable an interrogation
`contactless-enabled device 120, (having an RF transponder)
`signal to power the RFID tag and receive the uniqueidentifier
`is tapped correspondsto different information on the contact-
`less-cnabled device 120. The contactless-cnabled device 120
`and a link to an accessible network (slep 302). In various
`embodiments, the contactless-enabled device 120 accesses
`maybe “tapped” with an active RFID tag by waving the
`the network using the received link. The unique identifier is
`contactless-enabled device in close proximity, where the
`provided by the contactless-enabled device to the network,
`waving with a gesture formationis an identifier. For example,
`where the unique identifier is used as a key to locate the
`waving the contactless-enabled device with a gesture forma-
`consumer’s bill (step 303). Once the total bill is retrieved, the
`tion in the form ofacircular shape mayresult in the popula-
`consumer may submit a payment request to an authorization
`tion of the online transactionfields using a first set of data.
`system using the contactless-enabled device 120 (step 304).
`Likewise, waving the contactless-enabled device with a ges-
`ture formation in the form of a square yields similar results
`[0031]
`In various embodiments and with reference to FIG.
`4, check presenter 110 includes a Quick Response (QR) code
`and population ofthe online transactionfields using a second
`in place of, or in addition to, an RFID tag. With the QR code,
`set of data. For example. the first set of data may be the
`the contactless-enabled device 120 does not need to be an
`account information of the consumer’s American Express
`credit card. The secondset of data may be the account infor-
`RI'-enabled device, but instead only needs a camera and the
`mation of the consumer’s Visa credit card.
`In another
`appropriate software to “read” the QR code (step 401). The
`example, the first set of data may contain the consumer’s
`QR code may link the contactless-enabled device 120 to a
`homeaddress as the shipping address, whereas the second set
`website where the appropriate payment may be madeto the
`of data may contain the consumer’s work address as the
`restaurant bill (step 402). A part of the information provided
`shipping, address. For more information regarding a gesture
`byreading the QR code mayinclude a uniqueidentifier asso-
`formationidentifier, refer to U.S. patent application Ser. No.
`ciated with the total bill (step 403). In using a QR code to
`
`13/168,072, entitled “SYSTEMS AND METHODS FOR
`generate contactless payments, the merchant system 130 pro-
`GESTURE-BASED INTERACTION WITH COMPUTER
`vides the total bill to the payment website prior to the con-
`tactless-enabled device 120 linking to the total bill. The pay-
`SYSTEMS,” filed Jun. 24, 2011, which is hereby incorpo-
`ment website may be operated by the merchant system 130 or
`rated by reference.
`bya third party entity. Once the total bill is retrieved, the
`[0035]
`In addition to a gesture being an identifier a voice
`consumer may submit a payment request to an authorization
`activated phrase mayalso be an identifier. In various embodi-
`system using the contactless-enabled device 120 (step 404).
`ments, a consumer may haveto speak a specific phrase into
`[0032]
`In various exemplary embodiments, whether the
`the RF device to unlock the ability to initiate a transaction.
`
`contactless-enabled device 120 accesses the total bill via an
`Eachphrase may belinked to accountinformation. Speaking
`RFID tag or a QR code, a consumeris able to pay the total bill
`the specific phrase unlocks the contactless-enabled device so
`that the contactless-enabled device and stored informationis
`using account information stored on the contactless-enabled
`device 120. Furthermore, the contactless-enabled device 120
`available next time the contactless-enabled device is tapped
`may store multiple accounts which the consumer mayselect
`or a QR code accessed. This unlocking phrase increases the
`
`
`
`
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 17 of 25
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 17 of 25
`
`

`

`US 2013/0048717 Al
`
`Feb. 28, 2013
`
`device security and prevents the contactless-enabled device
`from transmitting information unintentionallyor if an unau-
`thorized reader is attempting to access the information. Fur-
`thermore, the device security may be enhanced byrequiring
`that it is the consumer’s voice that speaks the phrase.
`[0036] As iscommonwith groupsofpeople dining together
`ata restaurant, the total bill may be divided amongstindividu-
`als or sub-groups of people. As stated earlier, dividing the
`total bill takes additional time and presents the opportunity
`for a mistake to be made. In accordance with various exem-
`plary embodiments and with reference to FIG. 5, one or more
`contactless-enabled devices 120 may be used to help divide
`the total bill in any way desired (step 501). One such embodi-
`ment involves multiple contactless-enabled devices 120 each
`tapping the check presenter having the RFID tag 110, where
`the RFID tagis an active tag. The merchant system 130 ora
`third party entity operating the payment website may be piven
`notice that the total bill will be divided among consumers.
`‘The notice maybe given in various ways, including pressing
`a button on the check presenter. ‘The button maybe pressed a
`certain numberof times, each press indicating the number of
`people splitting the total bill. For example, ifthree consumers
`decide to divide the total bill, then the buttonis pressed three
`times. Eachofthe three consumers mustthentap their respec-
`tive contactless-enabled devices 120 with the checkpresenter
`with RFID tag 110. In various embodiments, the three con-
`tactless-enabled devices 120 of the consumers are tapped
`within a certain amount of time, such as one minute. If the
`indicated numberof contactless-enabled devices are not pre-
`sented within the specified amount of time, the payment
`transaction may be cancelled and the payment process
`restarted. In various embodiments, the notice of multiple
`payors may be given to the merchant system 130 by double
`tapping the RFID tag 110.
`[0037]
`Similarly, various embodiments involve multiple
`contactless-enabled devices 120 each tapping the check pre-
`senter having the RFID tag 110, where the RFID tag is a
`passive tap. With the passive tap, multiple contactless-en-
`abled devices 120 may individually interrogate and read the
`passive tag. The contactless-enabled devices 120 may then
`interact with the payment network 150 to coordinate payment
`of the total bill using multiple funding sources. In various
`embodiments, each of the multiple contactless-enabled
`devices 120 provide noticeto the payment network 150thatat
`least partial paymentwill be provide from a financial account
`associated with each of the multiple contactless-enabled
`devices 120.
`
`Furthermore, the total bill may be divided using
`[0038]
`profile information about each consumer, randomly gener-
`ated amounts,alternating amounts(e.g., different person pays
`a different percentage each time they attend the particular
`restaurant or a different restaurant with a similar group of
`people). escalating amounts, decreasing amounts, by a for-
`mula, by rules, ctc. In various embodiments, the total bill may
`be divided equally amongst the numberofpayors or a specific
`amount to each payor(step 502). If the total bill is divided
`equally, each payorusingtheir individual contactless-enabled
`devices 120 to submit a payment request using the provided
`information, namely the payor’s equal share ofthetotal bill
`and a merchantidentifier (step 503). If the total bill is divided
`byspecific amounts to each payor, the division may take place
`at one or more contactle