US 20140310117A1
`
`(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2014/0310117 A1
`
`Moshal
`(43) Pub. Date:
`Oct. 16, 2014
`
`(54) BILL PAYMENT SYSTEM AND METHOD
`
`Publication Classification
`
`(71) Applicant: GELLINER LIMITED, Douglas (GB)
`
`(72)
`
`Inventor: Martin Paul Moshal, Queens Way Quay
`(GI)
`(73) Assignee: GELLINER LIMITED, Douglas (GB)
`(21‘) Appl. No.:
`14/356,563
`
`(51)
`
`Int. Cl.
`G06Q 20/14
`GIMQ 20/20
`(52) US. Cl.
`G06Q 20/14 (201301): “flag/$01!:
`CPC
`USPC ............................................... 705/23; 705/40
`
`(2006.01)
`(2006.01)
`
`(22) PC” Filed:
`
`(86) PC” No.:
`
`
`
`Vov.12, 2012
`
`PCT/GB2012/052802
`
`(57)
`
`ABSTRACT
`
`§ 371 (0(1).
`(2), (4) Date: Mav 6, 2014
`.
`‘ y
`.
`Related U'S' Appllcatlon Data
`(60) Provisional application No. 61/587416, filed on Jan.
`17, 2012'
`4
`
`(30)
`
`Foreign Application Priority Data
`
`Nov. 10, 2011
`
`(GB) ................................... 11193752
`
`A system and method to use quick response (QR) codes
`encoded with a bill from a merchant, such as, for example‘
`provided by a restaurant, A code scanner (106) can scan a QR
`code that encodes a merchant identification code that identi-
`fies a merchant. A user can select a payment instrument onthe
`code scanner for paying the bill. The code scanner can trans—
`mit to an application server (102) data pertaining to the pay—
`ment instrument. The code scamier can receive from the
`application server status data indicating Whether the bill was
`successfully or unsuccessfully paid.
`
`100
`
`
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 1 of 26
`
`

`

`Patent Application Publication
`
`Oct. 16, 2014 Sheet 1 0f 12
`
`US 2014/0310117 A1
`
`
`
`HGURE1:
`
`
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 2 of 26
`
`

`

`Patent Application Publication
`
`Oct. 16, 2014 Sheet 2 0f 12
`
`US 2014/0310117 A1
`
`E22052
`
`E
`
`“Hg2220
`
`
`228:322822322
`2222222228l.88?an22m2”2%
`
`282%
`
`NNEED—u—
`
`
`
`2520;
`
`
`
`NomiHmewzmmmsgm
`
`HHHU225$2223
`
`
`
`HHUN2222:$2223
`
`
`
`922222522220522
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 3 of 26
`
`
`

`

`Patent Application Publication
`
`Oct. 16, 2014 Sheet 3 0f 12
`
`US 2014/0310117 A1
`
`
`
`FIGURE 3
`
`999
`
`‘
`
`
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 4 of 26
`
`

`

`Patent Application Publication
`
`Oct. 16, 2014 Sheet 4 of 12
`
`US 2014/0310117 A1
`
`User Interface
`
`’
`
`Network
`Interface
`
`Code Scanner
`
`‘ CRPI
`
`162
`
`Scanner App.
`
`154
`
`‘ User Profile
`
`110
`
`Data Storage Device
`
`106
`
`FIGURE 4
`
`
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 5 of 26
`
`

`

`Patent Application Publication
`
`Oct. 16, 2014 Sheet 5 0f 12
`
`US 2014/0310117 A1
`
`User Interface
`
`Processor
`
`CRPI
`
`176
`
`Merchant App
`
`178
`
`Merchant Terminal
`
`Bill Database
`
`180
`
`‘ Data Storage Device
`
`108 ‘
`
`FIGURE 5
`
`
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 6 of 26
`
`

`

`Patent Application Publication
`
`Oct. 16, 2014 Sheet 6 0f 12
`
`US 2014/0310117 A1
`
`User Interface
`
`Network 1
`
`Interface
`
`Merchant
`CRP' 192196
`
`Scanner App
`
`1
`
`94
`
`User Profiles
`
`198
`
`Merchant
`
`ID
`
`Codes
`
`Data Storage Device
`
`Merchant
`
`‘
`
`Profiles
`
`142
`
`Merchant" DB ‘
`
`‘
`
`Application Server
`
`188
`
`102
`
`FIGURE 6
`
`
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 7 of 26
`
`

`

`Patent Application Publication
`
`Oct. 16, 2014 Sheet 7 0f 12
`
`US 2014/0310117 A1
`
`.mu>
`
`:Ewmwoosmomw__5.5mm
`
`NNN_EmEm..2=5twou<
`‘
`
`
`
`EmuEmEm.:Emcmc.
`
`£5qu:5NTED
`
`EmEshmEEmEm.
`
`25%=525%.223”.
`
`
`omkm2250m0cmom._.-
`53mmcozmgfiad._Eccmommvoo_
`\4oE00810250mm.
`
`
`
`
`
`EEEEFE2052\wOn.
`
`
`
`@50010$381cow‘
`
`EwE>mQ
`
`‘EmE>ma
`
`,_Emmmoo:w>502
`
`59:5::5:Emcmfi
`
`
`
`EmaEsoEm
`
`émmmoozwcz>502_4,.1.
`
`
`
`E0233>mam5
`
`
`
`EEmtm-94338033:
`
`25%=595%_mm“_mmN
`
`_hmanor._
`Ema:=5Ems.wwn
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 8 of 26
`
`
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Oct. 16, 2014 Sheet 8 0f 12
`
`US 2014/0310117 A1
`
`802MM
`
`West End Lane NW6
`
`
`
`
`
`Merchant'fiD: 483221
`
`
`WaiterlD: Frank
`
`808 MTablemr 117
`
`‘
`Etemlzed Bill :
`Q llé'chicken
`;
`£ 9.75
`Q 1%‘Chicken
`.£ 3.95
`O 1 Pitta
`E 17.05
`O lPe'ri‘Dips
`£ 0.90
`Q lmed'mm Side
`E 045
`
`‘
`
`Subtotal ‘
`Tax
`-
`812 ”'4" Tara!
`
`£ 18.42
`E. 3.88
`£ 22.10
`
`804
`
`806
`
`810
`
`814
`
`
`
`
`
`Optional Gratuity @ : 10 as
`£ 2.21 '1
`
`818
`816
`
`
`
`820
`.1...
`
`824
`
`@822
`
`
`
`FIGURE 8
`
`
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 9 of 26
`
`

`

`m
`
`Oct. 16, 2014 Sheet 9 0f 12
`
`US 2014/0310117 A1
`
`P.
`
`
`
`
`
` 1m80.-cosmoEEwEEmmomm\é_Am0.8mggkgm.53mm5:828?_,
`
`Loccwomwvoo.__m:_§m::m:2m§\wwfimw
`
`m2mmass:
`
`WQ>COPE—>51
`gammmoosw
`
`“29.:mom‘mmooki
`
`ONm
`
`
`
`
`
`
`
`émmmoozmcs€on_20:33>mam5_..A
`
`
`
`EEmzmé.0mm.Emmmoosm>502_EmmmuozmEmE>mQ>me5_.EmE>mn_._Emm_moosm,::
`
`
`
`
`
`
`
`695::.__£_Emcmfi‘.25%:5055mm,
`
`
`
`‘Ewe3..5mm,_omm‘.vmm
`
`
`
`29.38%J?ammzwi_.55..=3{2208.
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 10 of 26
`
`
`
`
`
`

`

`Patent Application Publication
`
`Oct. 16, 2014 Sheet 10 0f 12
`
`US 2014/0310117 A1
`
`
`
`
`
`.EmEm.mwmuoi
`
`.
`
`
`
`m.E\Ema.:Emcfi
`
`SEwoo.__83h
`
`
`
`onemooT‘muoomacmom._.-MO0:mewE>BQ009‘
`\4woe”mnoo.m0wuoumo._‘muse
`
`
`
`
`
`
`Bawmcowmu=QQ<_gmccmowmooo_.mEEBhE3822\mOa
`
`
`
`‘.4
`
`,.:
`
`Emmmuozmc:>302
`
`_wmo:
`
`QEmwwoosw
`cwE>mm
`
`we,3:.ES_mstzoEmEmuEmu2.9:m...
`:Emcmt.
`
`
`
`
`
`:5.235:285.8:
`
`EOE>ma
`
`
`
`.Ewmmoozw€62
`
`EmE>m.
`
`522.2::5:EmcmF.
`
`_vmor._éwwmooawE959;
` >wiw5_t,.Eszmm:
`
`._Ewwmoo:w::
`25%:5963%ES
`
`
`
`
`
`Eszmq\Euwfi
`
`omor
`
`m8P
`
`
`EmaanEm.
`(”noF‘S.mmDGEn
`
`.bfimgan¥a§mm:
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 11 of 26
`
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Oct. 16, 2014 Sheet 11 0f 12
`
`US 2014/0310117 A1
`
`
`
`”Ems...N...wwOUOLl
`
`2339“Mega;$88:85:22.we:
`
`
`.82NF553858.m.vmr:pmfifimzo.mozao2:0.th
`:02:
`
`
`
`‘\4
`
`
`am:nox001.No:_muoum0cmuw
`
`we:mwmnmfin33«:2an:Emcmfi.
`53mmscamozau<‘_gmccmommuoo.5::thE2055.5won
`E2058VE:r..88m0@886
`
`
`
`mm>oéwmmousm
`
`cmE>ma
`
`mNeF_
`
`w,.E5:95=Emcmt.
`
`wanEzoEmEmu
`
`gfimu:5£55
`
`E0823
`
`
`
`.Emwmouzw€82
`
`EmE>mQ
`
`
`
`E95982235
`
`
`
`fiEmtm¢h._Ewwmou:m::
`
`
`
`_2$59”.‘.
`
`NV:
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 12 of 26
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Oct. 16, 2014 Sheet 12 0f 12
`
`US 2014/0310117 A1
`
`
`
`802
`
`808
`
`”WWW
`1.
`“x T18 Eatery
`, West End Lane NW6 /1
`Merchant 11): 483221
`.1
`Wate ID. FrankM
`- TablemO: 17
`‘
`Itemized Bill:
`Q l‘AChicken
`E 9.75
`.»-~~~
`.
`1
`w l‘AChtcken
`E 3.95
`C}
`_
`‘
`11mm
`O 1 Peri Dips
`C)-. 1medium side ‘
`
`5 7.05
`£ 9.90
`
`£ 0.45
`
`804
`
`806
`
`810
`
`814
`
`
`
`1
`
`
`
`.
`
`.
`
`812
`
`Subtotai
`Tax
`Total
`
`£18.42
`E 3.68
`£ 22.10
`
`.OpfionaIGracuityé): 10%
`E 2.21
`
`
`9mm: Us/
`
`1208
`1
`Tm @1m15% 3
`1202
`M[fimherW1 822
`
`\‘1PayBilfwith eWaHet {
`"
`
`825 flyWith Other. 1
`3 Kywmnmm
`%
`mlfllwfi‘fi
`LV'IWflE.
`
`1204.
`
`
`
`J 1
`
`. Wmmbrwufmm...—
`
`
`
`800
`
`FIGURE 12
`
`
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 13 of 26
`
`

`

`US 2014/0310117 A1
`
`Oct. 16, 2014
`
`BILL PAYMENT SYSTEM AND METHOD
`
`PRIORITY CLAIMS
`
`[0001] This application claims the benefit of GB Applica—
`tion No. 11193752, filed Nov. 10, 2011, and claims the
`benefit of U.S. Provisional Application No. 61/587,416, filed
`Jan. 17, 2012. GB Application 11193752 and U.S. Provi-
`sional Application No. 61/587,416 are incorporated herein by
`reference for all purposes.
`
`BACKGROUND
`
`[0002] Bill payment at establishments such as restaurants,
`refuelling stations and retailers can be tedious and time-con-
`suming. For example, at a restaurant, when a diner is pre-
`sented with a bill at the conclusion of a meal, the diner can
`tender cash or a payment instrument (such as a credit or debit
`card) to a waiter in order to pay the bill. The waiter is then
`required to provide change ifpayment is by cash, or to use a
`point-of-sale (“POS”) terminal if a payment instrument is
`used.
`[0003] A further illustration of the tediousness of bill pay—
`ment occurs where a diner elects to add a discretionary gra-
`tuity (or “tip”) to the bill total as a reward for good service, or
`elects to deduct or alter an optional gratuity is already
`reflected in the bill total. Still further, the diner may wish to
`split the bill total, with or without a gratuity, equally with
`fellow—diners, or the diners may agree that each person pays
`for the items on the bill that each person has consumed.
`[0004] The applicant has appreciated the desirability of a
`simpler process for paying bills than that described above.
`
`Overview
`
`[0005] Example embodiments are described herein. In one
`respect, an example embodiment takes the form of a method
`comprising (i) scanning, using a code scanner, a quick
`response (QR) code that encodes a merchant identification
`code that identifies a merchant; (ii) decoding, using the code
`scanner, the QR code to recover the merchant identification
`code; (iii) displaying, on the code scanner, infonnation per-
`taining to a bill from the merchant; (iv) selecting, using the
`code scanner, a first payment instrument for paying the bill,
`and authorizing the bill for payment; (v) transmitting from the
`code scanner to an application server the merchant identifi—
`cation code, data pertaining to an amount due on the bill, and
`data pertaining to the first payment instrument; and (Vi)
`receiving, at the code scanner from the application server,
`status data indicating whether the bill was successfully or
`unsuccessfully paid.
`[0006]
`In another respect, an example embodiment takes
`he fonn ofa code scamier device comprising: (i) a processor;
`(ii) a scanner configured to scan a quick response (QR) code
`hat encodes a merchant identification code that identifies a
`merchant; (iii) a non-transitory computer-readable data stor-
`age device comprising computer-readable program instruc-
`ions, wherein the program instructions are executable by the
`orocessor to decode the QR code; (iv) a user interface con—
`igured to display bill information and to allow a user to select
`a first payment instrument for paying the bill and to authorize
`a bill for payment; and (v) a network interface; (vi) wherein
`he network interface is configured to transmit, to an applica-
`ion server, the merchant identification code, data pertaining
`0 an amotmt due on the bill, and data pertaining to the first
`3ayment instrument; and (vii) wherein the network interface
`
`
`
`is configured to receive, from the application server, status
`data indicating whether the initial attempt of paying the bill
`was successful or unsuccessful.
`[0007]
`In yet another respect, an example embodiment
`takes the form of a method comprising: (i) receiving, at an
`application server from a first code scanner, a merchant iden—
`tification code that identifies a merchant; (ii) receiving, at the
`application server from the first code scarmer, data pertaining
`to an amount due on a bill from the merchant; (iii) receiving,
`at the application server from the first code scanner, data
`pertaining to a first payment instrument selected for a first
`attempt ofpaying the bill; (iv) determining, at the application
`server, whether processing the data pertaining to the amotmt
`due on the bill and the data pertaining to the first payment
`instrument results in successful or unsuccessful payment of
`the bill; and (v) transmitting, from the application server to
`the first code scanner, first status data indicating Whether the
`attempt of paying the bill was successful or unsuccessful.
`[0008]
`In yet another respect, an example embodiment
`takes the form of an application server system comprising: (i)
`a processor; (ii) a non-transitory computer—readable data stor—
`age device comprising computer-readable program instruc-
`tions; and (iii) a network interface to receive, from a first code
`scanner, (1) a merchant identification code that identifies a
`merchant. (2) data pertaining to an amount due 011 a bill from
`the merchant, and (3) data pertaining to a first payment instru-
`ment selected for an attempt of paying the bill; and (iv)
`wherein the program instructions are executable by the pro—
`ces sor to determine whether processing the data pertaining to
`the amount due on the bill and the data pertaining to the first
`payment instrument results in successful or unsucces sful pay-
`ment of the bill; (v) wherein the program instructions are
`executable by the processor to cause the network interface to
`transmit first status data to the first code scanner; and (vi)
`wherein the first status data indicates whether the attempt of
`paying the bill was successful or unsuccessful.
`[0009]
`In yet another respect, an example embodiment
`takes the form of a method comprising: (i) receiving, at a
`merchant terminal, (1) a bill identification code that identifies
`a bill from a merchant and (2) data pertaining to details ofthe
`bill; and (ii) provisioning a bills database with the bill iden-
`tification code and data pertaining to details of the bill, and
`identifying a status of the bill as unpaid.
`[0010]
`In yet another respect, an example embodiment
`takes the form of a merchant terminal device comprising: (i)
`a processor; (ii) a non-transitory computer—readable data stor—
`age device comprising eomputer—readable program instruc—
`tions; and (iii) a network interface; (iv) wherein the network
`interface is configured to receive (1) a bill identification code
`that identifies a bill from a merchant and (2) data pertaining to
`details of the bill; and (v) wherein the program instructions
`are executable by the processor to provision a bills database
`with the bill identification code and the data pertaining to
`details ofthe bill, and an identification ofa status ofthe bill as
`unpaid.
`In yet another respect, an example embodiment
`[0011]
`takes the form of a method comprising: (i) providing, at a
`point of sale terminal, a bill from a merchant; and (ii) provid-
`ing, at the point of sale terminal, a quick response (QR) code
`that encodes a merchant identification code that identifies the
`merchant.
`
`In yet another respect, an example embodiment
`[0012]
`takes the form of a point of sale terminal device comprising:
`(i) a processor; (ii) a non-transitory computer-readable data
`
`
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 14 of 26
`
`

`

`US 2014/0310117 A1
`
`Oct. 16, 2014
`
`storage device comprising computer—readable program
`instructions; and (iii) a network interface; and (iv) wherein
`the program instructions are executable by the processor to
`provide a bill from a merchant and a quick response (QR)
`code that encodes a merchant identification code that identi-
`fies the merchant.
`[0013] These as well as other aspects and advantages will
`become apparent to those of ordinary skill in the art by read-
`ing the following detailed description. with reference where
`appropriate to the accompanying drawings. Further, it should
`be understood that the embodiments described in this over-
`view and elsewhere are intended to be examples only and do
`not necessarily limit the scope ofthe invention.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0014] Example embodiments are described herein with
`reference to the drawings, in which:
`[0015]
`FIG. 1 is a schematic representation of a system for
`the payment of bills;
`[0016]
`FIG. 2 is a representation of a webpage of a mer-
`chant portal website hosted on an application server in the
`system of FIG. 1;
`[0017]
`FIG. 3 illustrates an example quick response (QR)
`code;
`FIG. 4 is a block diagram of a code scanner in
`[0018]
`accordance with an example embodiment;
`[0019]
`FIG. 5 is a block diagram of a merchant terminal in
`accordance with an example embodiment;
`[0020]
`FIG. 6 is a block diagram ofan application server in
`accordance with an example embodiment;
`[0021]
`FIG. 7 is a flow chart of functions to carry out
`payment of a bill at a merchant establishment in accordance
`with the first embodiment of the system ol'FIG. 1;
`[0022]
`FIG. 8 illustrates an example display provided by a
`scanner application in accordance with an example embodi—
`ment;
`FIG. 9 is a flow chart of functions to carry out
`[0023]
`payment of a bill at a merchant establishment in accordance
`with a second embodiment of the system of FIG. 1;
`[0024]
`FIG. 10 is a flow chart of functions to carry out
`payment of a bill at a merchant establishment in accordance
`with a third embodiment of the system of FIG. 1;
`[0025]
`FIG. 11 is a flow chart of functions to carry out
`payment of a bill at a merchant establishment in accordance
`with a fourth embodiment of the system of FIG. 4; and
`[0026]
`FIG. 12 illustrates a further example display pro-
`vided by the scaimer application in accordance with an
`example embodiment.
`
`DETAIIED DESCRIPTION
`
`I. Introduction
`
`[0027] This description describes, among other things,
`example embodiments with respect to paying a bill at a mcr-
`chant establishment. In this description, the articles “a” or
`an” are used to introduce elements of the example embodi—
`ments. The intent ofusing those articles is that there is one or
`more ofthe elements. The intent ofusing the conjunction “or
`within a described list of at least 2 terms is to indicate that any
`ofthe listed terms or any combination ofthe listed terms. The
`terms “first” and “second” are used to distinguish respective
`elements and are not used to denote a particular order oftho sc
`elements.
`
`[0028] The following abbreviations or acronyms are used
`in the description:
`[0029] CVC4Card Verification Code;
`[0030] FIG.7Figure;
`[0031] FIGs.7Figures;
`[0032]
`Inc .7Incorporated;
`[0033] Merchant AppiMerchant Terminal Application
`Program;
`[0034] PINiPersonal Identification Number;
`[0035] QRiQuick Response;
`[0036]
`Scanner App Scanner Application Program; and
`[0037] URLiUniform Resource Locator.
`
`II. Example Architecture
`FIG. 1 depicts a schematic representation of a sys-
`[0038]
`tem 100 for payment of bills in accordance with example
`embodiments described herein. The system 100 includes an
`application server 102, a POS terminal 104, a code scanner
`106 device configured to scan and decode Quick Response
`(QR) codes which are well known and widely used, and a
`merchant terminal 108. The code scanner 106 can take the
`form of a conventional smartphone handset provisioned with
`software for scanning QR codes, a web browser, and a wire-
`less connection to the intemet. The code scanner 106 can be
`referred to as a “mobile wireless communication device,” a
`“mobile smartphone handset” or, more simply. a “mobile
`smartphone” or “smartphone.” As an example, the mobile
`wireless communication device can be a personal digital
`assistant or a cellular telephone. As another example, the
`mobile wireless communication device can be an iPhone,
`such as the iPhoneS, or an iPad sold by Apple Inc., Cupertino,
`Calif, United States. The code scanner 106 does not need to
`be a mobile device. but can be a device that remains attached
`to a stationary internet-enabled device.
`[0039] The merchant terminal 108 can take the form of a
`conventional smartphone handset provisioned with a web
`browser and a wireless connection to the intemet. The mer-
`chant terminal 108 can be referred to as a “merchant wireless
`communication device”, a “merchant smartphone handset”
`or, more simply, a “merchant smartphone”. As an example,
`the merchant wireless corrm1unication device can be a per—
`sonal digital assistant or a cellular telephone. The merchant
`wireless communication device 108 does not need to be a
`mobile device. but can be a device that remains attached to a
`stationary intemet-enabled device.
`[0040] The application server 102, the POS terminal 104,
`the code scanner 106 and the merchant terminal 108 can
`comrmmicate with each other using a communication net-
`work 116. The communication network 116 can comprise a
`wide-area network, such as the internet.
`[0041] Communication between the application server
`102, the code scanner 106 and the merchant terminal 108 can
`be facilitated by using a server—hosted program (not shown),
`a scanner application program (a ‘scanner app’) that
`is
`installed and executed on the code scanner 106, and a mer—
`chant application program (a “merchant app”) that is installed
`and executed on the merchant terminal 108. In another
`respect, communication between the application server 102
`and code scanner 106 can occur using network interface 152
`(shown in FIG. 4) and network interface 176 (shown in FIG.
`6).
`[0042] A user can download a copy ofthe scanner app from
`a download repository (for example, data storage device 178
`in FIG. 4) and install the scanner app on the code scanner 106.
`
`
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 15 of 26
`
`

`

`US 2014/0310117 A1
`
`Oct. 16, 2014
`
`On, during, or after installation, the scanner app creates a user
`profile 110 on the code scanner 106 and prompts the user to
`manually provide personal attributes such as, the user’s first
`name, the user’s last name, an e-mail address, a physical
`address and particulars of one or more payment instruments
`such as credit cards, debit cards, e-wallets and the like. In
`accordance with at least some example embodiments, the
`user profile 110 (for example, the data in the user profile 110)
`is stored locally on the code scanner 106 and is not passed to
`the application server 102.
`[0043] A merchant can download a copy of the merchant
`app from a download repository (for example, data storage
`device 178 in FIG. 4) and install the merchant app on the
`merchant terminal 108. The application server 102 hosts a
`merchant portal website 120 that enables merchants to regis—
`ter and create individual merchant profiles that are maintained
`by the application server 1 02 in a merchant database 112. The
`merchant portal website 120 can be referred to as a “portal
`website.” Merchant registration and creation of a merchant
`profile in the merchant database 112 can be performed online
`by the merchant portal website 120. A merchant can use a
`merchant computing device 130 including a display for dis-
`playing websites to display merchant portal websites and an
`input device for selecting or entering data onto the merchant
`portal websites.
`[0044]
`FIG. 2 shows an example webpage 200 ofthe mer-
`chant portal website 120. The webpage 200 can display a
`registration form 201 that a merchant can complete in order to
`register with the merchant portal website 120. The webpage
`200 canbe a homepage ofthe merchant portal web site 120. As
`an example, the registration form 201 can include the follow-
`ing fields: a merchant’s business name 202, a merchant’s
`business address 204, and a description of the merchant’s
`business 206. As an example, the business description can be
`a restaurant, a motor vehicle repair shop, a retail store, or
`some other business description. Other examples of fields on
`
`the registration form 201 are possible. Entering data into the
`registration form 201 can occur, for example, by typing data
`or selecting data from a list ol'predeter'mined data.
`[0045] A merchant can, in this mamicr, configure the mer-
`chant for QR-based bill payment, The application server 102
`can assign a unique merchant identification code to each
`merchant business configured in this manner and the mer—
`chant identification code is stored in the merchant’s profile in
`the merchant database 1 12. Additionally or alternatively, each
`merchant identification code can be provided to and stored
`with a QR source that serves QR codes to the POS terminal
`104. For the sake of being brief, a merchant identification
`code can be referred to as an “identification code.”
`[0046]
`In this description the terms ‘user’ and ‘customer’
`are used interchangeably depending on the context. For
`example a user ofthe scanner app on the code scanner 106 can
`also be a customer of the merchant.
`[0047]
`FIG. 3 illustrates an example QR code 999. QR code
`999 can be encoded as a payment QR code.
`[0048] Next, FIG. 4 is a block diagram depicting an
`example embodiment ol'code scanner 106. As shown in FIG.
`4, code scanner 106 includes (i) a processor 150, (ii) a net-
`work interface 152 for transmitting data to and receiving data
`from communication network 116, (iii) a user interface 154,
`(iv) a scanner 156 configured to scan (for example, capture)
`QR codes, and (v) a data storage device 158, all ofwhich can
`be linked together via a system bus or other comicetion
`mechanism 160. Data storage device 158 includes computer-
`
`readable program instructions (CRPI) 162, the scanner app
`164, and a user profile 110. CRPI 162 can include the scanner
`app 164. Data storage device 158 can comprise a non-transi—
`tory com outer-readable storage medium readable by proces-
`
`sor 150. Each computer-readable storage medium described
`herein can comprise volatile and/or non-volatile storage com-
`ponents, such as optical, magnetic, organic or other memory
`or disc storage, which can be integrated in whole or in part
`with a processor.
`[0049] Each processor described herein can comprise one
`or more general purpose processors (for example, INTEL
`single core microprocessors or INTEL multicore micropro—
`cessors) or one or more special purpose processors (for
`example, digital signal processors). Processor 150 is config-
`ured to execute CRPI 162.
`[0050]
`FIG. 5 is a block diagram depicting an example
`embodiment of merchant terminal 108. As shown in FIG. 5,
`merchant terminal 108 includes (i) a processor 166, (ii) a
`network interface 168 for transmitting data to and receiving
`data from communication network 116, (iii) a user interface
`170, (iv) a scanner 171 configured to scan (for example,
`capture) QR codes and (v) a data storage device 172, all of
`which can be linked together via a system bus or other con—
`nection mechanism 174. Data storage device 172 includes
`computer-readable program instructions (CRPI) 176, the
`merchant app 178, and a bill database 180. CRPI 176 can
`include the merchant app 178. Data storage device 172 can
`comprise
`a
`non-transitory
`computer-readable
`storage
`medium readable by processor 166. Processor 166 is config-
`ured to execute CRPI 176.
`[0051] Next, FIG. 6 is a block diagram depicting an
`example embodiment of application server 102. As shown in
`FIG. 6, application server 1 02 can include (i) a processor 182,
`(ii) a network interface 184 for transmitting data to and
`receiving data from communication network 116, (iii) a user
`interface 186, and (iv) a data storage device 188, all of which
`can be linked together via a system bus or other comiection
`mechanism 190. Data storage device 188 can include (i)
`CRPI 192, (ii) the scanner app 194 for downloading to code
`scanners, (iii) the merchant app 196 for downloading to mer-
`chant tenninals, (iv) user profiles 198, (v) merchant website
`identification codes 140 for merchant businesses, and (vi)
`merchant database 112 including merchant profiles 142.
`CRPI 192 can include the scamrer app 194 and merchant app
`196. Data storage device 188 can comprise a non-transitory
`computer-readable storage medium readable by processor
`182. Processor 182 is configured to execute CRPI 192.
`
`III. anmple Operation A
`
`[0052] The system 100 can be used to register and pay a bill
`at a merchant business by use of the code scanner 106. The
`following example describes an application ofthe system 100
`by a user (a diner) at a restaurant who wishes to pay a restau-
`rant bill after completion of a meal. In addition to this par-
`ticular example, the system 100 is also applicable to payment
`ofother types ofbills such as, for example, utility bills, trafiic
`fines, online shopping bills and the like. The merchant (res—
`taurant proprietor or manager) will have already downloaded
`the merchant app 196 from the application server 102,
`installed the merchant app on the merchant terminal 108,
`registered on the portal website 120 and created a merchant
`profile 142 in the merchant database 112. The merchant pro-
`file 142 includes a merchant identification code 140 assigned
`by the application server 102.
`
`
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 16 of 26
`
`

`

`US 2014/0310117 A1
`
`Oct. 16, 2014
`
`
`
`FIG. 7 is a flow chart depicting a set of functions 750
`[0053]
`hat can be carried out
`in accordance with an example
`embodiment. The set of functions 750 can be performed to
`3ay the restaurant bill. The set of functions 750 are shown
`within blocks 700 through 738. A description ofthose blocks
`now follows.
`
`[0054] Upon completion ofthe meal the diner can request a
`gill for payment from a waiter. The waiter can draw up a bill
`hat contains, for example, a name and address of the restau-
`rant, a waiter identification, a table number, a description and
`a corresponding cost of each item consumed during the meal,
`any tax such as sales tax or value-added tax included in the
`Jill, and a total amount due. At block 700 the POS terminal
`104 can provide a payment QR code that encodes the iner-
`chant identification code 140 in the merchant profile 142, a
`gill identification code or number, and all the details con-
`ained in the bill. The payment QR code may be generated by
`he POS terminal 104 or may be served to the POS terminal by
`an external source ofQR codes (not shown). At block 702 the
`waiter or merchant can use the merchant app 178 and the
`scaimer 171 on the merchant terminal 108 to scan the pay—
`ment QR code provided by the POS terminal 104. At block
`704, the merchant app 178 decodes the scanned payment QR
`code to recover the encoded data that it contains, in particular
`the bill identification number and the bill details. At block
`706, the merchant app 178 appends the bill identification
`number and the bill details to the bills database 180 on the
`merchant terminal 108 and marks the status of the bill as
`pending (or unpaid).
`[0055] The bill and the payment QR code can be provided,
`individually or in combination, to the diner. For example, the
`POS tenninal 104 may print a hardcopy of the bill that con-
`tains the payment QR code, or may print the QR code sepa-
`rately to a hardcopy ofthe bill. At block 708, the user can use
`the scanner app 164 and the scanner 156 to scan the payment
`QR code onthehardeopy ofthebillAtblock 710, the scanner
`app 164 decodes the scanned payment QR code to recover the
`encoded data that it contains namely, the merchant identifi—
`cation code, the bill identification number and the bill details.
`At block 712, the scanner app 164 displays a page 800 on the
`user interface 154 with all the bill details, as illustrated in FIG.
`8. At block 714 of FIG. 7 the user can review the bill details
`displayed on page 800 and amend the displayed data, if nec-
`essary. After reviewing and amending the data on page 800,
`the user can select, at block 716, a payment instrument to pay
`the billAt block 718 the user can accept the bill for payment.
`The scanner app then transmits to the application server 102,
`at block 720, the merchant identification code, the bill iden—
`tification number, the amount due and the details ofa payment
`instrument to be used for payment (for example, a credit or
`debit card number, a cardholders name, a card expiry date, a
`CVC, or a PIN, as stored in the user profile 110). Once the
`details ofthe selected payment instrument have been received
`at the application server 102, the particulars of the financial
`transaction (for example, the bill amount, and merchant and
`payment details) are sent to a payment processor (not shown)
`for processing (at block 722).
`[0056] At block 724, the application server 102 can deter-
`mine whether the payment was successful. The payment pro-
`cessor transmits a payment status indicator, for example,
`either successful or unsuccessful. If the payment status is
`successful, the application server 1 02 notifies the scanner app
`164, at block 726, that payment has been successful and the
`displayed page refreshes to indicate that the dincr’s bill has
`
`been paid (block 728). If, on the other hand, the payment
`status is unsuccessful, the application server 102 notifies the
`scanner app 164, at block 730, that payment has been unsuc—
`cessful and the page displayed by the scamier app 164
`refreshes to request the user to select a different payment
`instrument and re-attempt payment (block 732).
`[0057] At block 734, if the payment status indicator is
`successful, the application server 102 can transmit the bill
`identification number and the amount paid by the user to the
`merchant terminal 1 08 for processing. The merchant terminal
`108 provides the received data to the merchant app 178,
`which uses the bill identification code to perform a lookup in
`the bill database 180 and retrieve the corresponding bill
`details (block 73 6). At block 738, the merchant app updates
`the bill details to include the amount paid by the user on that
`bill and to update the status of the bill as paid.
`[0058] As illustrated in FIG. 8, the bill details displayed 011
`page 800 of the user interface 154 of the code scanner 102
`consist of the name and address 802 of the restaurant, the
`merchant identification code 804, a waiter identity or code
`806, a table number 808, and a description and cost 810 of
`each item consumed during the meal, and tax due 812. The
`bill details can also include a service charge 814 that is auto-
`matically added to the amount due. Page 800 also includes
`icons 816. 818, 820 and 822 that provid