(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2013/0048717 A1
`
` Brendell et al. (43) Pub. Date: Feb. 28, 2013
`
`
`US 20130048717A1
`
`(54) METHODS AND SYSTEMS FOR
`CONTACTLESS PAYMENTS AT A
`
`MERCHANT
`
`(75)
`
`Inventors: Brian Brendell, Springfield, NJ (US),
`l-l-lsin 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)
`9
`’
`S
`
`(2]) App]. No.: 13/280,938
`
`(22)
`
`Filed:
`
`OCt' 25! 2011
`
`Publication Classification
`
`-
`(:1)
`
`‘
`Int. c1.
`(2012.01)
`G06Q 20/32
`(2012.01)
`G06Q 20/20
`(52) US. Cl.
`....................................................... 235/380
`(57)
`ABSTRACT
`a ment 5 stem mav
`A coordination server of a contactless
`p y
`y
`“
`receive a total bill of purchases for a customer from a iner-
`chant POS terminal, associate the total bill of purcha ses with
`a “11.1un identifier Of an RFID tag Of a check 11030111“: and
`receive notification that payment ofthe total bill ofpurchases
`is authorized. The coordination server may receive the unique
`identifier and payment information from a contaetless-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 of the transaction under
`business as usual standards. In one embodiment, the coordi-
`nation server transmits the payment information and the total
`bill to a merchant acquirer, which then routes the payment
`
`Related U S Application Data
`(63) Continuation-in-part of application No. 13/215,145,
`filed on Aug. 22, 2011.
`
`In another
`to an appropriate payment network.
`request
`embodiment, the coordination server transmits the payment
`information and the total bill directly to the appropriate pay-
`merit network.
`
`Check Presenter 110
`
` .
`
`Contactless-enabted devrce 120
`
`Payment network 150
`
`Merchant system 130
`
`Authorization system 140
`
`Google LLC v. RFCyber Corp. / Page 1 of 25
`
`GOOG-1016
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 1 of 25
`
`PGR2022-00003
`Apple EX1016 Page 1
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 1 of 13
`
`US 2013/0048717 A1
`
`
`
`
`
`09‘x525:EoE‘Amn.
`
` 03Emu?
`
`cozmwtocug09E323E2922
`
`035239;xowcoomw.3.E=H.o
`
`
`
`8.5m96-8womco
`
`_.2:9“.
`
`6mm.ooG
`52fo2e9aPla.roCrebV.CFRv.CLLb9ooG
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 2 of 25
`
`PGR2022-00003
`Apple EX1016 Page 2
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 2 of 13
`
`US 2013/0048717 A1
`
`cm9.32Bucmmma
`
`9:£5,92aim
`
`:5=38
`
`x5250:
`
`vow
`
`NmSmE
`
`EmE>mQm2=5:329:83 mom
`xomcom2m_oomm<
`
`:5:39mwmfifimcmm8223.o2809
`$85839:5%EmcoLmEmE0:
`
` 829wEmcee:88:23680530
`NONSN
`
`3:53BEBmzo
`
`"£29:hoEmE>mQ
`
`m.mew::5
`
`83%umfimcmémmzoficou
`
`mow
`
`6mm.ooG
`52fo3e9aPla.roCrebV.CFRv.CLLb9ooG
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 3 of 25
`
`PGR2022-00003
`Apple EX1016 Page 3
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 3 0f 13
`
`US 2013/0048717 A1
`
`
`
`
`
`
`
`
`
`.8vaUmfimcoémmzoflcoomafi5&onan
`
`
`vE:x525:m$2898vavmfimcmémmzoficoo
`mm“DEW.9:So:v692DEW.cmES,
`
`
`momhwEmmmExooso9:
`
`
`
`
`m5@382x5352
`
`mmez:3$9653
`
`93mix3Co65:6298:5
`
`mom
`
`EmE>mam3:55EEBmzo
`
`
`
`9:E0:“8:59
`
`83%umfimcwéwmzoflcoo
`
`.Vom
`
`n930E
`
`6mm.ooG
`52fo4e9aPla.roCrebV.CFRv.CLLb9ooG
`
`Sm
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 4 of 25
`
`PGR2022-00003
`Apple EX1016 Page 4
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 4 of 13
`
`US 2013/0048717 A1
`
`83%8399898980
`
`
`
`x:__{oz/“m:m$289
`
`mvoum09:E9»,
`
`Nov
`
`
`
`29810m$895:85an
`
`
`
`m5:3@535xomgo9:Co
`
`83%60399896980
`
`wow
`
`9:$302{0sz
`
`
`
`mmgm::5$822.6
`
`U8.mEEmE25E:
`
`muoo109:
`
`mow
`
`
`
`EmE>mQm2526.mEBwso
`
`9:E0:3269
`
`
`
`mo_>m_uumfimcmémmzomucoo
`
`vow
`
`vmSmE
`
`6mm.ooG
`52fo5e9aPla.roCrebV.CFRv.CLLb9ooG
`
`
`
`
`
`
`
`
`
`
`
`
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 5 of 25
`
`PGR2022-00003
`Apple EX1016 Page 5
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 5 0f 13
`
`US 2013/0048717 A1
`
`
`
`
`cozoflmwLmEonzobcmEmcohmE>502
`
`
`
`
`
`82556:558comm.
`
`
`
`Fm:8,2838552.
`
`an82%
`
`
`
`mEsoEm$959EwEme
`
`
`
`vmwoxw3032”92:2:Ea:
`
`mom
`
`m9:9”.
`
`.38.
`EcsoEm=5.32$9:5mom
`
`umfimcmémmzoflcoo>502
`
`EsoEmmEEmEm.B303%
`
`
`
`EzoEmEmE>mQ85%m
`
`:560%.meCommoSwU
`
`mom
`
`
`
`mom
`
`
`
`
`
`222v".5536050me:
`
`umuEmtcoummmnE9960.
`
`
`
`.0gm:wwmcoha
`
`
`
`wmuczoEm$305$8053
`
`.vom
`
`
`
`vm_pwcm-mmmzoflcoom_mc_m
`
`
`
`£_>>3093c.8520
`
`
`
`Lmucmmmaxomzo
`
`
`
`8255main“wwzcmL
`
`coszhouE.Ema—umEmE>mQmfiEO
`
`
`
`momwflcsoEm058%L6
`
`
`
`All«$255vm_nm:m-mmm=omEoo
`ww>gm::5Es2220
`
`:086222.03:502
`
`
`
`EmE>mQ3:5383%
`
`
`
`
`
`
`
`6mGooG
`52fO6e9aPla.rOCrebV.CFRv.CLLb9OOG
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 6 of 25
`
`PGR2022-00003
`Apple EX1016 Page 6
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 6 0f 13
`
`US 2013/0048717 Al
`
`N
`
`El'
`
`'
`
`ET
`
`El
`
`{Eh-El
`
`El: E]
`
`El} [51
`
`”.NF
`ea
`13
`E(u
`(DL—
`I)
`cu
`us
`0
`
`m(
`
`601
`
`Purchases
`
`
`Figure6
`
`
`
`
`
`HerbChicken$16.75
`
`
`
`Ribeye$22.50
`
`0 L
`
`
`
`Google LLC v. RFCyber Corp. / Page 7 of 25
`
`GOOG-1016
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 7 of 25
`
`PGR2022-00003
`Apple EX1016 Page 7
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 7 0f 13
`
`US 2013/0048717 A1
`
`_
`
`.|_.v______
`
`FllrIIIIIII_
`_.2336._8..2295.26E8_2.29.2).
`
`
`mcamouoiyawningD<m
`
`
`
`c0_um:_ULOOU
`
`
`
`
`
`v\wonNON._IIIIIIIIII4HH//_829532“555.".n\\.Il.3535Iowa
`
`N9:9“.
`
`6mm.ooG
`52fo8e9aPla.roCrebV.CFRv.CLLb9ooG
`
`x533253:3
`
`
`
`
`
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 8 of 25
`
`PGR2022-00003
`Apple EX1016 Page 8
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 8 0f 13
`
`US 2013/0048717 A1
`
`
`
`
`
`
`
`962mm“Ewe—gum2923..650
`
`m059“.
`
`3:53
`
`Baum
`
`52mm333..
`
`.633EwEuuncmEEtc
`
`Etc
`
`Botmonwz
`
`23:6;
`
`
`
`.5mefine—Finn.
`
`
`
`.6me“5823Emu—Eu
`
`can33>“:
`
`cot—21.3.;
`
`Baum5:25.63
`
`
`
`
`
`
`
`
`
`6mm.ooG
`52fo9e9aPla.roCrebV.CFRv.CLLb9ooG
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 9 of 25
`
`PGR2022-00003
`Apple EX1016 Page 9
`
`

`

`Patent Application Publication
`
`h
`
`e
`
`f
`
`e_
`
`s_350m_2\00.,_ucwuzou\momJauntie;b_EB3153W...won.
`
`€29.22_.2259.6232;x85\
`
`mom
`
`v...025233:3
`
`vow
`
`_L3L1_m
`om.9_otG
`
`1eAmw7m9:9“.P1/7Iwm0Om.lCma0_.W.2Cm_m_v.
`
`C
`
`65120cl4OG0o1
`
`
`
`
`
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 10 of 25
`
`PGR2022-00003
`Apple EX1016 Page 10
`
`

`

`Patent Application Publication
`
`82b.eF
`
`ee
`
`31f0w
`
`US 2013/0048717 A1
`
`ooow
`
`voo_..
`
`
`
`x5332._m_:=mu
`
`
`
`
`
`
`22222cI7”,J5EE;.3535€95
`
`
`
`1cm>2330mo;
`um23:8\3Buu<-o=_m>
`
`t3E83535.53moor
`
`
`
`9:02.52EwE>mm
`
`S2:9“.
`
`6mm.ooG
`52fo11e9aPla.roCrebV.CFRv.CLLb9ooG
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 11 of 25
`
`PGR2022-00003
`Apple EX1016 Page 11
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 11 0f 13
`
`US 2013/0048717 A1
`
`we:
`
`
`
`3:02.32vamp—3mm
`
`we:
`
`EwE>mm
`
`533mm
`
`€0sz53:8
`
`
`
`
`
`
`
`
`dcmE>~n
`
`1cm>216.—
`
`
`
`mom“cm—.955—I52635:35.
`
`8:\.uEwm:oszuBOU
`
`
`
`3.9.2.3.;
`
`ucmucou
`
`:9:9“.
`
`No:mo:
`
`mu_>mu:o3:39:
`
`25Ems—>2.
`
`.lOC.lebV.CFRv.CLLbg0OG
`
`6mm.ooG
`52fO21egaPla.
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 12 of 25
`
`PGR2022-00003
`Apple EX1016 Page 12
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 12 0f 13
`
`US 2013/0048717 A1
`
`SNF
`
`
`
`Now;vomr
`
`E2:9”.
`
`
`
`won.EmceofiI
`
`J:oE>mn_
`
`ucmb.831—
`
`umuu<.m:_u>
`
`“cognac
`
`$5.5m:oszEooo
`
`2:2$33
`
`
`
`BEmmoixumco
`
`momw
`
`.lOC.lebV.CFRv.CLLbg0OG
`
`6mGooG
`52fO31egaPla.
`
`
`
`
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 13 of 25
`
`PGR2022-00003
`Apple EX1016 Page 13
`
`

`

`Patent Application Publication
`
`Feb. 28, 2013 Sheet 13 0f 13
`
`m2SU
`
`17
`
`
`
`._._ZDmw<m0._.m
`
`8.l.9M£9$2;2.Lm30.20.235.200
`\/\VIN?moEmEZ
`
`\\/\2929222200
`
`
`
`mNmrwn_<20_m
`
`Mo7.G
`
`.lOC.lebV.CFRv.CLLbg0OG
`
`6mm.
`52fO41egaPla.
`
`><._n_w_m_ ormr
`womw._._ZD><._n_w_Dm0<umm._.z_
`
`
`
`:2:m0<mObmm>_mom0<w_0._.w
`
`
`m3m<>0_>_mmm.._m_<>O_>_m_m
`m._m<>0_>_mmm0<n_mm:.2_
`9.9or?
`
`0N2INNmF
`
`
`
`>mO_>_m=>_>m<DZOOmw
`
`Nrmr
`
`m>EDv55Dm<I
`
`:9.
`
`ZO_._.<O_ZDS=>_OO
`
`wmszDme/‘muz
`
`vomr
`
`
`
`>m0§m2Z_<_>_
`
`momw
`
`
`
`om?
`
`mmemOOwE
`
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 14 of 25
`
`PGR2022-00003
`Apple EX1016 Page 14
`
`

`

`US 2013/0048717 A1
`
`Feb. 28, 2013
`
`IWETHODS AND SYSTEMS FOR
`CONTACTLESS PAYIWENTS AT A
`MERCHANT
`
`CROSS REFERENCE TO RELATED
`APPLICATIONS
`
`[0001] This application is a continuation-in-part applica-
`tion of US. application Ser. No. 12/758,942, entitled
`
`“METHODS AND SYSTEMS FOR CONTACTLESS PAY-
`MENTS,” which was filed on Aug. 23, 2011, and which is
`hereby incorporated by reference in its entirety.
`FIELD
`
`[0002] The present disclosure generally relates to contact-
`less payments in a retail environment. More particularly, 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]
`consumer receives a 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 temiinal and processes the
`card to obtain authorization for receiving payment for the bill.
`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. The consumer may be concemed that the
`employee is retaining credit card information while out of
`sight.
`Furthermore, it is very common for a group of con-
`[0004]
`sumers to decide to pay for only a portion ofthe 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. Altematively, the restaurant employee may only
`provide a total bill. and then process various amounts on
`multiple cards in order to satisfy payment. Again, dividing
`payment of a total bill amongst multiple cards increases the
`risk of a mistake.
`[0005]
`In light 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 (e.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 frequency identification RFID) tag with
`the total bill, transmitting the total bill and associated unique
`identifier to a consumer accessible payment network, and
`receiving payment from the consumer for 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 may interrogate the
`RFID tag to receive the unique identifier and a payment
`
`network link. Furthermore, the contactless-enabled device
`may submit 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 locates the total bill using the unique identifier as a key. In
`various embodiments, the RFID tag 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 unique identifier 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
`may act as the primary coordination point fordividing a bill of
`sale and ensuring that all partial payments by customers sat—
`isfy the total outstanding bill. The coordination server may be
`integrated into the merchant point—of—sale terminal, or the
`coordination server may be separate from the merchant point—
`of-sale terminal. In other embodiments,
`the coordination
`server may reside at the merchant’s location, or at an issuer
`facility.
`Furthennore, in various embodiments, the coordi-
`[0008]
`nation server receives the unique identifier of the RFID tag
`and payment information from a contactless-enabled device.
`The total bill may be located using the unique identifier as a
`key, and the coordination server transmits the payment infor-
`mation and the total bill to the merchant point—of—sale terrni—
`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
`infomiation 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 infonnation 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 (RFID) tag with a unique identifier, where the
`unique identifier is associated with a total bill at a coordina-
`tion server. A contactless-enabled device in proximity to the
`check presenter apparatus may read the unique identifier from
`the RFID tag, and transmit payment information and the
`unique identifier to facilitate contactless payment of the 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
`payment of the total bill.
`
`
`
`Google LLC v. RFCyber Corp. / Page 15 of 25
`
`GOOG-1016
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 15 of 25
`
`PGR2022-00003
`Apple EX1016 Page 15
`
`

`

`US 2013/0048717 A1
`
`Feb. 28, 2013
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0011] The features and advantages of the present disclo—
`sure will become more apparent from the detailed description
`set forth below when taken 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 number identifies the drawing in which the refer-
`ence number first 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 embodiment of a process of conducting
`contactless payments in a merchant transaction environment
`using an RFID tag;
`[0015]
`FIG. 4 is an embodiment ofa process ofconducting
`contactless payments in a merchant transaction environment
`using a QR code;
`[0016]
`FIG. 5 is a flowchart illustrating an exemplary pro-
`cess of dividing payment ofa payment among multiple eon-
`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 exemplary pro-
`cess of conducting contactless payments in a merchant trans—
`action environment using 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 exemplary pro—
`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
`transaction environment using a payment gateway;
`[0023]
`FIG. 12 is a flowchart illustrating an exemplary
`process of conducting contactless payments in a merchant
`transaction environment using a tablet computer; and
`[0024]
`FIG. 13 is a block diagram ofan exemplary embodi-
`ment of a computer system.
`
`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 herein 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 frequency identification (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
`may be a passive tag that is powered by a nearby reader, such
`as the contactless—enabled device 120. In various embodi—
`ments, the check presenter 110 is a tablet computer operated
`primary by a touch screen, such as an iPad. Authorization
`system 140 may include any entity that offers transaction
`account services, such as 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 13 0 and authorization system 140. Furthermore,
`in various embodiments, payment network 150 may be a part
`ofmerchant system 13 0 or a part ofauthorization system 140.
`Payment network 150 is a central network which commrmi-
`cates with various systems and may communicate with con-
`tactless-enabled devices 120. Payment network 150 may be a
`proprietary network operated by merchant system 130 or
`authorization system 140. Moreover, payment network 150
`may be operated by a third party provider and may be 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, each
`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. The unique identifier also helps the mer-
`chant system 130 track receipt of payment for separate bills.
`[0028] The system 100 may include or interface with any of
`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
`contactles s-enabled devices 120 may include, for example, a
`key ring, tag, card, cell phone, wristwatch or any such fonn
`capable of being presented for interrogation. Moreover, the
`system, computing unit or device discussed herein 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. Furthemiore, 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 typically referred to as a “smart
`card”); a fob having a transponder and an RFID reader; and/or
`near field communication (NFC) technologies. For more
`
`
`
`Google LLC v. RFCyber Corp. / Page 16 of 25
`
`GOOG-1016
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 16 of 25
`
`PGR2022-00003
`Apple EX1016 Page 16
`
`

`

`US 2013/0048717 A1
`
`Feb. 28, 2013
`
`Li.)
`
`information regarding NFC, refer to the following specifica-
`tions all of which arc incorporated by rcfcrcncc hcrcin: ISO/
`IEC 18092/ECMA—340, Near Field Communication Inter—
`face and Protocol—I (NFCIP—I); ISO/IEC 21481/ECMA—352,
`Near Field Communication Interface
`and Protocol—2
`(NFCIP-2); and EMV 4.2 available at http://wwwemvco.
`com/defaultaspx.
`[0029] With reference to FIG. 2, an exemplary method may
`include the following steps. Once a consumer finishes order—
`ing items from a restaurant 201, the total bill of the items
`purchased during the dining experience may be generated by
`a merchant system 202. The merchant system associates an
`RFID tag with the total bill 203, and then loads the total bill
`onto a consumer accessible payment network 204. Each
`RFID tag may have a unique identifier, such as a serial num-
`ber, which is used to associate the RFID tag with the bill. 'Ihe
`check presenter is given to the consumer, who has multiple
`options to pay the total bill. The options include cash, check,
`providing a transaction account card, or submitting payment
`using a contactless-enabled device 205.
`[0030] With reference to FIG. 3, in order to submit payment
`using the contactless-enabled device, the consumer may pro-
`vide account information by “tapping” the contactless-en-
`abled device 120 with check presenter having the RFID tag
`110 (step 301). The “tapping” motion means placing the
`contactless-enabled device 120 in close proximity to the
`RFID tag in order for an RF transponder of the contactless-
`cnablcd dcvicc 120 to communicatc. This may includc physi-
`cally touching the contactless—enabled device 120 to the
`RFID tag, or at least placing the contactless—enabled device
`120 in close enough proximity to enable an interrogation
`signal to power the RFID tag and receive the unique identifier
`and a link to an accessible network (step 302). In various
`embodiments, the contactless-enabled device 120 accesses
`the network using the received link. The unique identifier is
`provided by the contactless-enabled device to the network,
`where the unique identifier is used as a key to locate the
`consumer’s bill (step 303). Once the total bill is retrieved, the
`consumer may submit a payment request to an authorization
`system using the contactless—enabled device 120 (step 304).
`[0031]
`In various embodiments and with reference to FIG.
`4, check presenter 110 includes a Quick Response (QR) code
`in place of, or in addition to, an RFID tag. With the QR code,
`the contactless-enabled device 120 does not need to be an
`RF-enabled device, but instead only needs a camera and the
`appropriate software to “read” the QR code (step 401). The
`QR codc may link the contactlcss-cnablcd dcvicc [20 to a
`website where the appropriate payment may be made to the
`restaurant bill (step 402). A part of the information provided
`by reading the QR code may include a unique identifier asso—
`ciated with the total bill (step 403). In using a QR code to
`generate contactless payments, the merchant system 130 pro-
`vides the total bill to the payment website prior to the con-
`tactless-enabled device 120 linking to the total bill. The pay-
`ment website may be operated by the merchant system 130 or
`by a third party entity. Once the total bill is retrieved, the
`consumer may submit a payment request to an authorization
`system using the contactless-enabled device 120 (step 404).
`[0032]
`In various exemplary embodiments, whether the
`contactless-enabled device 120 accesses the total bill via an
`RFID tag or a QR code, a consumer is able to pay the total bill
`using account information stored on the contactless-enabled
`device 120. Furthermore, the contactless-enabled device 120
`may store multiple accounts which the consumer may select
`
`from to make the payment. In exemplary embodiment, the
`contactless-cnablcd dcvicc 120 is a smart phonc with a
`graphical user interface. Moreover, the consumer accesses
`the total bill and is able to add a tip if desired. The consumer
`selects which account is to be used and then proceeds to
`submit payment similar to an online transaction. For addi-
`tional
`information regarding contactless payments in an
`online transaction, please see U.S. application Ser. No.
`13/215,111, entitled “METHODS AND SYSTEMS FOR
`
`CUNI'AC'I'LESS PAYNIENI'S FOR UNLINE ECOM-
`
`
`
`M ‘RC ‘ CHECKOUT,” filed on Aug. 22, 2011, which is
`incorporated by reference.
`[0033]
`In various embodiments, a check presenter includes
`a smart RFID tag instead of, or in addition to, a passive RFID
`tag. The smart RFID tag may be configured to store one or
`more of a unique identifier, a transaction identifier. and trans-
`action information. The transaction information, for example,
`may include the amount due and merchant information. In the
`various embodiments, this additional information allows a
`consumer to pay the total bill using a financial institution of
`the consumer’s choosing. For example, the consumer can
`provide the information to a personal bank, where the bank
`receives the amount due and the merchant information, along
`with a consumer identifier. Once the consumer is identified
`and verified, the bank may approve the transaction and submit
`payment of the amount due to the merchant of record as
`indicated by the merchant information. Such a transaction has
`additional security in that the consumer’s account number is
`never transmitted during the processing.
`[0034]
`In various embodiments, the mamier in which tie
`contactless-enabled device 120, (having an RF transponder)
`is tappcd corrcsponds to diffcrcnt information on thc contact-
`lcss-cnablcd dcvicc 120. Thc contactless-cnablcd dcvicc 120
`may be “tapped” with an active RFID tag by waving tie
`contactless—enabled device in close proximity, where tie
`waving with a gesture formation is an identifier. For examp e,
`waving the contactles s-enabled device with a gesture forma-
`tion in the form of a circular shape may result in the popula-
`tion of the online transaction fields using a first set of da a.
`Likewise, waving the contactless-enabled device with a ges-
`ture formation in the form of a square yields similar resu ts
`and population ofthe online transaction fields using a second
`set of data. For example, the first set of data may be tie
`account information of the consumer’s American Express
`crcdit card. The second sct of data may bc the account infor-
`mation of the consumer’s Visa credit card.
`In another
`example, the first set of data may contain the consumer’s
`home address as the shipping address, whereas the second set
`of data may contain the consumer‘s work address as the
`shipping address. For more information regarding a gesture
`formation identifier, refer to U.S. patent application Ser. No.
`
`13/168,072, entitled “SYSTEMS AND METHODS FOR
`GES’I’URE-BASED INTERACTION WITH COMPUTER
`SYSTEMS,” filed Jun. 24, 2011, which is hereby incorpo-
`rated by reference.
`[0035]
`In addition to a gesture being an identifier a voice
`activated phrase may also be an identifier. In various embodi—
`ments, a consumer may have to speak a specific phrase into
`the RF device to unlock the ability to initiate a transaction.
`
`Each phrase may be linked to account information. Speaking
`the specific phrase unlocks the contactless-enabled device so
`that the contactless-enabled device and stored information is
`available next time the contactless-enabled device is tapped
`or a QR code accessed. This unlocking phrase increases the
`
`
`
`
`
`Google LLC v. RFCyber Corp. / Page 17 of 25
`
`GOOG-1016
`
`GOOG-1016
`Google LLC v. RFCyber Corp. / Page 17 of 25
`
`PGR2022-00003
`Apple EX1016 Page 17
`
`

`

`US 2013/0048717 A1
`
`Feb. 28, 2013
`
`device security and prevents the eontactless-enabled device
`from transmitting information unintentionally or if an unau-
`thorized reader is attempting to access the information. Fur—
`thermore, the device security may be enhanced by requiring
`that it is the consumer’s voice that speaks the phrase.
`[003 6] As is common with groups ofpeople dining together
`at a restaurant, the total bill may be divided amongst individu-
`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 tag is an active tag. The merchant system 130 or a
`third party entity operating the payment website may be given
`notice that the total bill will be divided among consumers.
`The notice may be given in various ways, including pressing
`a button on the check presenter. The button may be pressed a
`certain number of times, each press indicating the number of
`people splitting the total bill. For example, ifthree consumers
`decide to divide the total bill, then the button is pressed three
`times. Each ofthe three consumers must then tap their respec—
`tive contactless—enabled devices 120 with the check presenter
`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 number of 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 tag. With the passive tag, 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 I20 provide notice to the payment network 150 that at
`least partial payment will 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 amotmts, alternating amotmts (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, etc. In various embodiments, the total bill may
`be divided equally amongst the number ofpayors ora specific
`amount to each payor (step 502). If the total bill is divided
`equally, each payor using their individual contactless—enabled
`devices 120 to submit a payment request using the provided
`information, namely the payor’s equal share