as) United States
`a2) Patent Application Publication co) Pub. No.: US 2014/0310117 Al
`(43) Pub. Date: Oct. 16, 2014
`
`Moshal
`
`US 20140310117A1
`
`BILL PAYMENTSYSTEM AND METHOD
`
`Publication Classification
`
`(34)
`
`(71)
`
`(72)
`
`Applicant: GELLINER LIMITED,Douglas (GB)
`
`Inventor: Martin Paul Moshal, Queens Way Quay
`(Gl)
`
`(73)
`
`Assignee: GELLINER LIMITED,Douglas (GB)
`
`2D
`
`Appl. No.:
`
`14/356,563
`
`(22)
`
`(86)
`
`PCTFiled:
`
` PCT No.:
`
`Nov. 12, 2012
`
`PCT/GB2012/052802
`
`§ 371 (©),
`(2), (4) Date: May 6, 2014
`Related U.S. Application Data
`Provisional application No. 61/587,416, filed on Jan.
`17, 2012.
`
`(60)
`
`(30)
`
`Foreign Application Priority Data
`
`Nov. 10, 2011
`
`(GB) ceeecccseeretescnees 1119375.2
`
`100
`
`(51)
`
`Int. Cl.
`G0620/14
`GO6Q 20/20
`(52) US.CL
`CPC oeecccscces.. GO6Q 20/14 (2013.01): GO6Q 20/208
`(2013.01)
`USPC eccscssssesssssessssssssvsseetiessssseeesseees 705/23; 705/40
`
`(2006.01)
`(2006.01)
`
`(657)
`
`ABSTRACT
`
`A system and method to use quick response (QR) codes
`encoded with a bill from a merchant, such as, for example,
`provided byarestaurant. A code scanner (106) can scan a QR
`cade that encades a merchant identification code that identi-
`fies a merchant. A usercan select a payment instrument onthe
`code scannerfor paying the bill. The code scanner can trans-
`mil to an application server (102) data pertaining to the pay-
`ment instrument. The code scanner can receive from the
`application server status data indicating whether the bill was
`
`
`
`successfully or unsuccessfully paid.
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 1 of 26
`
`

`

`Patent Application Publication
`
`Oct. 16,2014 Sheet 1 of 12
`
`US 2014/0310117 Al
`
`
`
`FIGURE 1.
`
`
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 2 of 26
`
`

`

`Patent Application Publication
`
`Oct. 16,2014 Sheet 2 of 12
`
`US 2014/0310117 Al
`
`
`
`2007-——______________]wensseuisng
`
`
`Ldnbis|gg¢7eS]sdf}ssouisng
`
`_|GoPaes]-Aquno
`[20g
`CF28909Je50410izEy2G]
`CO)rnssauppy
`CO)2207Sseuppy
`:yeI5
`CThtt
`
`JUBUIJAIAI
`
`
`
`dnubisjueYyaayy
`
`P02
`
`2JYNSI
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 3 of 26
`
`
`

`

`Patent Application Publication
`
`Oct. 16,2014 Sheet 3 of 12
`
`US 2014/0310117 Al
`
`
`
`gg
`
`FIGURE3
`
`
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 4 of 26
`
`

`

`Patent Application Publication
`
`Oct. 16,2014 Sheet 4 of 12
`
`US 2014/0310117 Al
`
`User Interface
`
`Processor
`
`Scanner
`
`Scanne
`
`Interface
`
`Code Scanner
`
`— CRPI
`
`162
`
`Scanner App.
`
`(164
`
`~ User Profile
`
`440
`
`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 of 12
`
`US 2014/0310117 Al
`
`User Interface
`
`Processor
`
`Scanner
`
`Network
`Interface
`
`CRP}
`
`176
`
`Merchant App
`
`+178
`
`Bill Database
`
`180
`
`Data Storage Device
`
`Merchant Terminal
`
`108 .
`
`FIGURE 5
`
`
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 6 of 26
`
`

`

`Patent Application Publication
`
`Oct. 16,2014 Sheet 6 of 12
`
`US 2014/0310117 Al
`
`User Profiles
`
`Merchant
`Profiles
`
`142
`
`MerchantDB
`
`Data Storage Device 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 of 12
`
`US 2014/0310117 Al
`
`vis
`ZLZ
`
`|OLL/OSZ802
`JaNaguonesiddy|
`
`apodHoHaposeq
`Jguuedgapo
`SBP09HHUeIS
`
`‘JEUILUJa]JUBYOIaVy/SOd
`
`+--1BPODHOspinodiddoz
`
`SoK
`
`vowed
`
`Zinjssasong-—LEz||
`
`InjssaoonsunAJQON:
`
`
`juawAedAeldsiq
`
`juawAed
`
`-JuawAed
`
`InysssoonsAON
`
`
`
`Jequunujjiqpuisued,
`
`
`
`piedjunowe
`
`
`
`}dwaye-a‘|nssaqgonsun
`
`Zaanols|
`
`eld,IlIGYIEY\|Sez
`
`9¢2
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 8 of 26
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Oct. 16,2014 Sheet 8 of 12
`
`US 2014/0310117 Al
`
`
`
`
`MerchantiD: 483721
`
`
`802 Otay >
`
`
`
`West End Lane NW6
`
`Weiter IO: Frank
`SOB mnsmmpene Table!D: 17
`itemized Bill:
`
`OQ iKChicken £9.75
`CO aKchicken
`£3.95
`© 4+ Pitta
`£7.05
`© 1 Peri Dips
`£ 0.90
`# Lmedium side
`— 0,45
`
`£18.42
`Subtotal
`— 3,68
`Tax
`£ 22.10
`B12 a aetal
`Cptional Gratuity @ : 10 %
`£ 2.21
`
`
`
`804
`
`806
`
`810
`
`814
`
`
`
`820
`
`824 —
`
`Pay with Cther:
`B26 —=
`
`ws CARESS
`
`818
`
`
`
`wea
`
`800
`
`FIGURE 8
`
`
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 9 of 26
`
`

`

`Patent Application Publication
`
`Oct. 16, 2014 Sheet 9 of 12
`
`US 2014/0310117 Al
`
`InjsseoonsunAjON
`}duwia}}e-3,‘nysseoonsun
`
`
`
`
`yuowAedAejdsiq
`
`026
`
`uoHeoynuap!pue
`
`Jequunu
`
`0s6906|8P09YOSpiral|
`
`Janiaguoyeaddy|)|006
`
`
`3}ImyssaconsjuawAedAejdsiq
`quewhed7
`
`|pz6|vee
`286PedNOLENbog
`
`
`
`JBUUBDSspoygJEUILNS]JUBYISIY/SOd
`
`juawAed
`
`
`
`jnysseoonsANON
`
`
`
`Jequinujiiqyusued)
`
`
`
`piedqunowle
`
`6auNSIs|
`
`9¢6
`
`{SHETEPIIIeAStIo
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 10 of 26
`
`
`
`
`
`
`
`

`

`SoAOZOL
`
`ZINgSS399NS
`uawkeg
`
`
`
`Inq,predun,,ayeap
`
`JO}[1gJasIoV/
`
`Patent Application Publication
`
`Oct. 16, 2014 Sheet 10 of 12
`
`US 2014/0310117 Al
`
`
`
`
`
`ZLvodHAapoo0apooeq}|QSOLCOOL}OPOYh)-ULIS1}yooneisapinoig600!
`
`
`‘JOQUINUFron){figPLUSUEL||::SHEIOINGSASHISY
`
`
`
`
`Janjaguoneayddy|JOUUEISBpoy|peunuaJUEYDIAW/SOd
`
`
`
`[~juauikedssacolgWISUIMSUTWoMIKedSSSloLot
`a1qe}/JeyempusuUel
`
`
`
`yuowAeddwaje-2.‘jnysse.onsun-OfOL nAjilon
`jaukedlyzor|ozo1
`
`quewAedAgidsiq Ingssaconsu
`
`OLOL|,|8001—Fsrejap11gpusuIe“MOIADY||900144
`zzo1!|Sob
`
`
`
`
`injssaoonsjuewAedAgjdsiq,
`
`
`ByepjuawAedpusued]
`
`inyssaoonsAor
`
`
`
`
`
`
`
`pedjunouettzep,«OFSUNSI1Dpled,WGHENIgeqy
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 11 of 26
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Oct. 16,2014 Sheet 11 of 12
`
`US 2014/0310117 Al
`
`
`
` _#OSLL24007)cOLL|QpOdHHuess
`
`
`gor1]eseqerepOLLtJUBYOIAWPUSUEL|
`jueyosow}@—JS509WbBpoDaq
`
`
`
`
`janiaguoyeayddy|JAUUBDSapo|eummuayjee/SOd
`
`ayeduayywusued1SpooUOMEIAUSp!sous
`
`
`
`
`uojenyoads47clp>]sajsereyajeondowu0ped
`
`gjge}/Jopemjiwsuel)
`
`juamkedSS830id
`NyssedonsAWON
`Zjnysseoons
`uawAed
`
`}duwaye-as‘jnjssaoonsun
`
`SHEP|IIQAEJASIGg
`juawAedAejdsiq
`
`
`uoqiuBooalZELE
`
`
`
`
`
`
`
`
`yuawAed
`
`jyuawAed
`
`
`
`HG,predun,,ajeaipSZLL
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 12 of 26
`
`
`
`
`
`
`
`
`
`
`

`

` o—The Eatery
`
`_
`
`812
`
`Patent Application Publication
`
`Oct. 16,2014 Sheet 12 of 12
`
`US 2014/0310117 Al
`
`808
`
`artaceceRiseHare
`
`West End Lane NW6 a
`Merchant 1D: 483224
`‘
`Waite’ |0: Frank ee
`« Table (0: 17
`|
`Itemized Bill :
`3) i Chicken
`E 9.75
`oN re
`|
`hw 1% Chicken
`£ 3.35
`> .
`~
`1 Pitta
`OG 1 Pert Dips
`O“Imediumside
`
`— 7.05
`£ 0.90
`£ 0.45
`
`804
`806
`
`810
`
`Subtotal
`£18.42
`Tax
`— 3.68
`Total
`£ 22.19
`Optional Gratuity @: 10 % — 814
`
` 1204
`|oiefofalls
`1202
`|
`tip: (1%} fs25x (13%
`1208
`B24.
`[other — G22
`Spay Bilt with eWalletA
`|
`825 i!Pay with Otherer|
`|
`Seniments
`eetenemneranesar i a
`
`1
`
`Nememistriyinnatetrd
`
`
`=
`
`r
`
`j
`
`{
`
`
`
`800
`
`FIGURE 12
`
`
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 13 of 26
`
`

`

`US 2014/0310117 Al
`
`Oct. 16, 2014
`
`BILL PAYMENT SYSTEM AND METHOD
`
`PRIORITY CLAIMS
`
`[0001] This application claims the benefit of GB Applica-
`tion No. 1119375.2, filed Nov. 10, 2011, and claims the
`benefit of U.S. Provisional Application No. 61/587,416, filed
`Jan. 17, 2012. GB Application 1119375.2 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 andretailers 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 paymentinstrument(such as a credit or debit
`card) to a wailer in order to paythe bill. The waiter is then
`required to provide change if paymentis by cash, or lo use a
`point-of-sale (“POS”) terminal if a payment instrument is
`used.
`[0003] A further illustration of the tediousness ofbill pay-
`ment occurs where a diner elects to add a discretionarygra-
`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 embodimentsare described herein. In one
`respect, an example embodimenttakes 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, information per-
`taining to a bill from the merchant; (iv) selecting, using the
`code scanner, a first payment instrument for paying thebill,
`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 onthebill, 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 formofa code scanner device comprising: (i) a processor;
`Gi) a scanner configured to scan a quick response (QR) code
`hat encodes a merchantidentification code that identifies a
`merchant; (iii) a non-transitory computer-rcadable data stor-
`age device comprising computer-readable program instruc-
`ions, wherein the program instructions are executable bythe
`processor to decode the QR code; (iv) a user interface con-
`figured to displaybill informationandto allow a userto select
`a first payment instrumentfor paying the bill and to authorize
`a bill for payment; and (v) a network interface: (vi) wherein
`he networkinterface is configured to transmit, to an applica-
`ion server, the merchant identification code, data pertaining
`oO an amount due onthe bill, and data pertaining to the first
`payment instrument; and (vii) whercin the network interface
`
`
`
`is configured to receive, from the application server, status
`data indicating whether the initial attempt of paying the bill
`was successlul or unsuccesslul.
`[0007]
`In yet another respect, an cxample embadiment
`takes the form of a method comprising: (i) receiving, at an
`application server froma first code scanner, a merchant iden-
`ification code that identifies a merchant; (41) receiving, al the
`application server from thefirst code scanner, 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 amount
`due on the bill and the data pertaining, to the first payment
`instrumentresults 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 ofan application server system comprising: (i)
`a processor; (11) a non-transitory computer-readable data stor-
`age device comprising computer-readable program instruc-
`tions; and (iii) a network interfaceto receive, froma first code
`scanner, (1) a merchant identification code that identifies a
`merchant, (2) data pertaining to an amount due ona bill from
`the merchant, and (3) data pertainingto a first payment instru-
`ment selected for an attempt of paying the bill; and (iv)
`wherein the program instructions are executable by the pro-
`cessor to determine whether processing the data pertaining to
`the amount due onthe bill and the data pertaining to the first
`payment instrument results in successful or unsuccessful 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 thatidentifies
`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 ofthe 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 computer-readable program instruc-
`ions; and (iti) a network interlace; (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 programinstructions
`are executable bythe processor to provisiona 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 pointofsale terminal, a quick response (QR) cade
`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 Al
`
`Oct. 16, 2014
`
`storage device comprising computer-readable program
`instructions; and (iii) a network interlace; and (iv) wherein
`the program instructions are executable by the processor lo
`provide a bill from a merchant and a quick response (QR)
`code that encodes a merchantidentification code that identi-
`fies the merchant.
`[0013] These as well as other aspects and advantages will
`become apparentto those of ordinaryskill 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 embadiments described in this over-
`view and elsewhere are intended to be examples only and do
`not necessarily limit the scope of the invention.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0014] Example embodiments are described. herein with
`reference to the drawings, in which:
`[0015]
`FIG. 1 isa schematic representation of a system for
`the paymentofbills;
`[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 cade scanner in
`[0018]
`accordance with an example embodiment;
`[0019]
`FIG. 5 isa block diagram of a merchant terminal in
`accordance with an example embodiment;
`[0020]
`FIG. 6 isa block diagramof an application server in
`accordance with an example embodiment;
`[0021]
`FIG. 7 is a flow chart of functions to carry out
`paymentof a bill at a merchant establishment in accordance
`withthefirst embodiment ofthe system of 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 ofa bill al a merchant establishment in accordance
`with a second embodimentof the system of FIG. 1;
`[0024]
`FIG. 10 is a flow chart of functions to carry out
`paymentofa 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
`paymentof 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 scanner application in accordance with an
`example embodiment.
`
`DETAILED DESCRIPTION,
`
`I. Introduction
`
`[0027] This description describes, among other things,
`example embodiments with respect to paying a bill at a mer-
`chant establishment. In this description, the articles “a” or
`an” are used to introduce elements ofthe 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 describedlist of at least 2 termsis 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 ofthose
`elements.
`
`[0028] The following abbreviations or acronymsare used
`in the description:
`[0029] CVC—CardVerification Code;
`[0030]
`FIG.—Figure;
`[0031]
`FIGs.—Figures;
`[0032]
`Inc.—Incorporated;
`[0033] Merchant App—Merchant Terminal Application
`Program;
`PIN—Personal Identification Number;
`[0034]
`[0035] QR—Quick Respanse;
`[0036] ScannerApp Scanner Application Program: and
`[0037] URL—Unilorm Resource Locator.
`
`Tl. Example Architecture
`I'IG. 1 depicts a schematic representation of a sys-
`[0038]
`tem 100 for payment of bills in accordance with example
`embodiments described hercin. 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
`formof a conventional smartphone handset provisioned with
`software for scanning QR codes, a web browser, and a wire-
`less connection to the internet. 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 cxample, 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,
`suchas the iPhoneS, or an iPad sold by Apple Inc., Cupertino,
`Calif., United States. The code scanner 106 does not need to
`bea mobile device, but can be a device that remains attached
`to a stationary internet-enabled device.
`[0039] The merchant terminal 108 cantake the form of a
`conventional smartphone handset provisioned with a web
`browser and a wireless connection to the internet. 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 communication device can be a per-
`sonal digital assistant or a cellular telephone. ‘he merchant
`wireless communication device 108 does not need to be a
`mobile device, but can be a device that remains attached to a
`stationary internet-enabled device.
`[0040] The application server 102, the POS terminal 104,
`the code scanner 106 and the merchant terminal 108 can
`communicate with each other using a communication net-
`work 116. The communication network 116 can comprise a
`wide-area network, such as the internct.
`[0041] Communication between the application server
`102, the code scanner 106 and the merchant terminal 108 can
`befacilitated 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”’) thatis installed
`and executed on the merchant terminal 108. In another
`respect, communication betweenthe 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] Ausercan download a copy ofthe scannerapp from
`a download repository (for example, data storage device 178
`in FIG.4) and install the scannerapp on the code scanner 106.
`
`
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 15 of 26
`
`

`

`US 2014/0310117 Al
`
`Oct. 16, 2014
`
`readable program instructions (CRPI) 162, the scanner app
`164, anda userprofile 110. CRPI 162 can include the scanner
`app 164. Data storage device 158 can comprise a non-transi-
`tory computer-readable storage mediumreadable byproces-
`
`sor 150. Each computer-readable storage mediumdescribed
`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 ane
`or more general purpose processors (lor 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 embodimentof application server 102. As shown in
`FIG.6, application server 102 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 connection
`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 terminals, (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 scanner 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.
`
`On,during, orafter installation, the scanner app creates a user
`profile 110 on the code scanner 106 and promptsthe user Lo
`manually provide personalaltribules such as, the user’s [irst
`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
`userprofile 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 copyof 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 merchantsto regis-
`ler and create individual merchantprofiles that are maintained
`by the application server 102 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 of the mer-
`chant portal website 120. The webpage 200 can display a
`registration form 201 that a merchant can complete in orderto
`register with the merchant portal website 120. The webpage
`200 can bea homepageofthe merchant portal website 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
`someotherbusiness description. Other examplesof 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 of predetermined data.
`[0045] A merchant can, in this manner, 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 merchantdatabase 112. 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’
`[0052] The system 100 canbe used to register and pay a bill
`are used interchangeably depending on the context. For
`at a merchant business byuse of the code scanner 106. The
`examplea user ofthe scannerapp onthe code scanner 106 can
`following example describes an application ofthe system 100
`also be a customer of the merchant.
`by a user(a diner) at a restaurant who wishes to paya restau-
`
`[0047] FIG.3illustrates an example QR code 999. QR code
`rant bill after completion of a meal. In addition to this par-
`999 can be encoded as a payment QR code.
`ticular example, the system 100 is alsa applicable to payment
`[0048] Next, FIG. 4 is a block diagram depicting an
`ofother types ofbills such as, for example,utility bills, traffic
`example embodiment of code scanner 106. As shown in FIG.
`fines, online shopping bills and the like, The merchant(res-
`4, code scanner 106 includes (i) a processor 150, (ii) a net-
`taurant proprietor or manager) will have already downloaded
`work interface 152 for transmitting data to and receiving data
`the merchant app 196 from the application server 102,
`from communication network 116, (iii) a user interface 154,
`installed the merchant app on the merchant terminal 108,
`(iv) a scanner 156 configured to scan (for example, capture)
`registered on the portal website 120 and created a merchant
`QRcodes, and (v) a data storage device 158, all ofwhich can
`profile 142 in the merchant database 112. The merchant pro-
`be linked together via a system bus or other connection
`file 142 includes a merchantidentification code 140 assigned
`mechanism 160. Data storage device 158 includes computer-
`by the application server 102.
`
`TH. Fxample Operation A
`
`
`
`
`
`GOOG-1005
`Google LLC v. RFCyber Corp. / Page 16 of 26
`
`

`

`US 2014/0310117 Al
`
`Oct. 16, 2014
`
`
`
`[0053] FIG.7isa flow chart depicting, a set of functions 750 been paid (block 728). If, on the other hand, the payment
`
`
`hat can be carried oul
`in accordance with an example
`status is unsuccessful, the application server 102 notifies the
`embodiment. he set of [unctions 750 can be performed to
`scammer app 164, al block 730, thal payment has been unsuc-
`pay the restaurant bill. The set of functions 750 are shown
`cessful and the page displayed by the scanner app 164
`within blocks 700 through 738. A description ofthose blocks
`refreshes to request the user to select a different payment
`now follows.
`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 bythe user to the
`merchant terminal 108 for processing. The merchant terminal
`108 provides the received dala 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 736). At block 738, the merchant app updates
`the bill details to include the amount paid bythe user onthat
`bill and to update the statusofthe bill as paid.
`[0058]
`Asillustrated in FIG.8, the bill details displayed on
`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 $12. ‘lhe
`bill details can also include a service charge 814thatis auto-
`matically added to the amount due. Page 800 also includes
`icons 816, 818, 820 and 822 that provide the user with an
`option to add a service charge to the amount dueonthebill if
`not already includedin the bill total, or to alter the amount of
`a service charge if already included. Icons 816, 818 and 820
`relate to predefined service charge amountsas a percentage of
`the bill total, for example, 10%, 12.5% and 15% respectively,
`while icon 822 relates to a free-form entry field for service
`charge amounts that are different to the predefined service
`charge amounts.
`[0059]
`Page 800 also displays icons 824 and 826that allow
`the user to select a payment instrument to use to pay the
`merchant’s bill. Icon 824 can be used to select an e-wallet
`with whichto pay, while icon 826 can be used to select a debit
`card or a credit card with which to pay the bill. If the user
`profile 110 in the code scanner 106 contains details of more
`than one payment instrument, the user can be prompted to
`select a preferred payment instrument from a drop-downlist
`displayed in the scanner app 164.
`
`[0054] Upon completion ofthe mealthe diner can request a
`bill for payment from a waiter. The waiter can drawup a bill
`hat contains, for example, a name and addressof 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
`bill, and a total amount due. At block 700 the POS terminal
`104 can provide a payment QR code that encodes the mer-
`chant identification code 140 in the merchant profile 142, a
`bill identification code or number, and all the details con-
`ainedin the bill. The payment QR code maybe generated by
`he POSterminal 104 or maybe servedto the POSterminal by
`an external source ofQR codes (not shown). At block 702 the
`waiter or merchant can use the merchant app 178 and the
`scanner 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 encodeddata that it contains, in particular
`the bill identification number and the bill details. At block
`706, the merchant app 178 appends the bill identification
`numberand 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]
`‘Uhe bill and the payment QR code canbe provided,
`individually or in combination, to the diner. For example, the
`POS terminal 104 may print a hardcopy ofthe bill that con-
`tains the payment QR code, or mayprint the QR code sepa-
`rately to a hardcopyofthe bill. At block 708, the user can use
`the scanner app 164 and the scanner 156 to scan the payment
`QRcode onthe hardcopyofthe bill. At black 710, the scanner
`app 164 decades the scanned payment QR cadeto recover the
`encoded data that it contains namely, the merchant identili-
`cation code,the bill identification numberandthe bill details.
`At block 712,the scanner app 164 displays a page 800 onthe
`userinterface 154 withall 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 amendthe 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
`FIG. 9 is a flow chart that depicts a set offunctions
`[0060]
`950 that can be carried out in accordance with an alternative
`the bill. At block 718 the user can acceptthe bill for payment.
`The scanner app then transmits to the