(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2014/0074723 A1
`Kamat
`(43) Pub. Date:
`Mar. 13, 2014
`
`US 20140074723A1
`
`(54) COMMUNICATING PAYMENTS
`
`Publication Classification
`
`(71) Applicant: Shreyas Kamat, Draper, UT (US)
`
`(72) Inventor: Shreyas Kamat, Draper, UT (US)
`
`(21) Appl. No.: 14/024,425
`
`(22) Filed:
`
`Sep. 11, 2013
`
`Related U.S. Application Data
`(60) Provisional application No. 61/700,214, filed on Sep.
`12, 2012.
`
`(2006.01)
`
`51) Int. C.
`(51) G06O20/20
`(52) U.S. Cl.
`CPC .................................... G06O20/202 (2013.01)
`USPC ............................................... 705/71; 705/21
`ABSTRACT
`(57)
`For communicating payments, a mobile device reads a point
`of-sale code from a point-of-sale device. A clearing house
`generates a payment authorization comprising an authoriza
`tion code and a transaction amount. The clearing house com
`municates the payment authorization through the mobile
`device to the point-of-sale device. The point-of-sale device
`completes the transaction in response to receiving the pay
`ment authorization.
`
`100a
`
`
`
`Clearing House
`30
`
`Point-Of-Sale
`Device
`20
`
`Petitioner Kiosoft Exhibit 1006
`1
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 1 of 19
`
`US 2014/0074723 A1
`
`100a
`
`
`
`Clearing House
`30
`
`Point-of-Sale
`Device
`20
`
`FIG. 1A
`
`Petitioner Kiosoft Exhibit 1006
`2
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 2 of 19
`
`US 2014/0074723 A1
`
`1OOb
`
`
`
`Clearing House
`30
`
`Point-of-Sale
`Device
`20
`
`FIG. 1B
`
`Petitioner Kiosoft Exhibit 1006
`3
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 3 of 19
`
`US 2014/0074723 A1
`
`
`
`1OOC
`Y
`
`Clearing House
`30
`
`10
`
`Point-of-Sale
`Device
`20
`
`FIG. 1C
`
`Petitioner Kiosoft Exhibit 1006
`4
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 4 of 19
`
`US 2014/0074723 A1
`
`
`
`1OOd
`\
`
`Clearing House
`30
`
`10a
`
`10a
`
`FIG. 1D
`
`Petitioner Kiosoft Exhibit 1006
`5
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 5 of 19
`
`US 2014/0074723 A1
`
`
`
`10
`
`210
`
`Flaca Cola
`Vege Chips
`Gorda Chips
`Massive Chocolate
`| Dark Chocolate
`| Milk Chocolate
`
`FIG. 2A
`
`Petitioner Kiosoft Exhibit 1006
`6
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 6 of 19
`
`US 2014/0074723 A1
`
`250
`
`
`
`10
`
`Slim Cola
`Flaca Cola
`Vege Chips
`Gorda Chips
`Massive Chocolate
`Dark ChoColate
`Milk Chocolate
`Gum
`Total
`
`FIG. 2B
`
`Petitioner Kiosoft Exhibit 1006
`7
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 7 of 19
`
`US 2014/0074723 A1
`
`
`
`10
`
`240
`
`Slim Cola
`Flaca Cola
`Vege Chips
`I Gorda Chips
`Massive Chocolate
`Dark Chocolate
`MilK Chocolate
`Gum
`Total
`
`A
`
`w
`w
`
`Buy Another tem
`Get 20% OFF
`
`42
`
`260
`
`FIG. 2C
`
`Petitioner Kiosoft Exhibit 1006
`8
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 8 of 19
`
`US 2014/0074723 A1
`
`
`
`10
`
`240
`
`210
`
`240
`
`Slim Cola
`Flaca Cola
`Vege Chips
`Gorda Chips
`Massive Chocolate
`Dark ChoCOlate
`Milk Chocolate
`Gum
`Total
`
`Calories 420
`Grams Fat 26
`
`260
`
`FIG. 2D
`
`Petitioner Kiosoft Exhibit 1006
`9
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 9 of 19
`
`US 2014/0074723 A1
`
`205
`
`820
`
`
`
`
`
`Merchant Code
`840
`Address
`845
`Unit Code
`850
`Register Code
`855.
`Time Stamp
`860
`
`FIG. 3A
`
`Point-Of-Sale Code
`205
`ACCount Alias
`815
`
`FIG. 3B
`
`Petitioner Kiosoft Exhibit 1006
`10
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 10 of 19
`
`US 2014/0074723 A1
`
`210
`
`213
`
`
`
`
`
`Point-of-Sale Code
`205
`items
`240
`Prices
`250
`Item Descriptions
`241
`Special Offers
`42
`Nutrition information
`44
`ACCount Alias
`815.
`
`FIG. 3C
`
`Point-Of-Sale Code
`205
`Items
`240
`Prices
`250
`Special Offers
`42
`ACCount Alias
`815.
`Transaction ID
`890
`
`FIG. 3D
`
`Petitioner Kiosoft Exhibit 1006
`11
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 11 of 19
`
`US 2014/0074723 A1
`
`215
`
`800
`
`
`
`
`
`Point-Of-Sale Code
`205
`Authorization Code
`890
`Transaction Amount
`870
`items
`240
`Prices
`250
`Time Stamp
`860
`
`FIG. 3E
`
`ACCount D
`805
`Payment Information
`810
`ACCount Alias
`815
`Transaction Records
`830
`
`FIG. 3F
`
`Petitioner Kiosoft Exhibit 1006
`12
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 12 of 19
`
`US 2014/0074723 A1
`
`875
`
`270
`
`
`
`
`
`Point-of-Sale LOCations
`295
`Purchase Menus
`210
`Price Comparisons
`265
`
`FIG. 3G
`
`Item Inventory
`275
`Item Inventory
`275
`Inventory Report
`276
`Inventory Alert
`277
`
`FIG. 3H
`
`Petitioner Kiosoft Exhibit 1006
`13
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 13 of 19
`
`US 2014/0074723 A1
`
`Processor
`305
`
`Communication
`Hardware
`315
`
`Computer
`105
`
`FIG. 4
`
`
`
`Generation
`Module
`225
`
`Transmission
`Module
`230
`
`Payment
`Apparatus
`200
`
`FIG. 5
`
`Petitioner Kiosoft Exhibit 1006
`14
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 14 of 19
`
`US 2014/0074723 A1
`
`20
`
`
`
`Wending
`Machine
`Hardware
`450
`
`Keypad
`Interface
`410
`
`Vending
`Machine
`Controller
`415
`
`Computer
`Interface
`420
`
`Slave
`Computer
`425
`
`Wireless
`Transceiver
`455.
`
`FIG.
`
`Petitioner Kiosoft Exhibit 1006
`15
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 15 of 19
`
`US 2014/0074723 A1
`
`501
`
`
`
`670
`
`675
`
`Receive Point-Of-Sale
`Code
`
`Generate Payment
`Authorization
`
`68O
`
`Communicate Payment
`Authorization
`
`685
`
`Complete Transaction
`
`FIG. 7
`
`Petitioner Kiosoft Exhibit 1006
`16
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 16 of 19
`
`US 2014/0074723 A1
`
`500
`
`
`
`505
`
`510
`
`515
`
`Receive Point-of-Sale
`COde
`
`Upload Point-of-Sale
`COde
`
`DOWnload Purchase
`Menu
`
`517
`
`Download Special Offer?
`Nutrition information
`
`
`
`520
`
`Receive Selection
`
`525
`
`530
`
`Generate Payment
`Authorization
`
`Communicate Payment
`Authorization
`
`535
`
`Complete Transaction
`
`FIG. 8
`
`Petitioner Kiosoft Exhibit 1006
`17
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 17 of 19
`
`US 2014/0074723 A1
`
`
`
`
`
`
`
`605
`
`610
`
`Receiving Location
`Information
`
`
`
`Communicating POS
`Device Locations and
`Purchase Menus
`
`615
`
`Receiving Trial Purchase
`Item Selection
`
`620
`
`Communicating Price
`Comparisons
`
`End
`
`Petitioner Kiosoft Exhibit 1006
`18
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 18 of 19
`
`US 2014/0074723 A1
`
`650
`Y
`
`655
`
`
`
`660
`
`Receive Payment
`Authorization
`
`Communicate Payment
`Authorization to Clearing
`House
`
`665
`
`Transfer Transaction
`Amount from ACCOUnt
`
`End
`
`Petitioner Kiosoft Exhibit 1006
`19
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 19 of 19
`
`US 2014/0074723 A1
`
`670
`Y
`
`
`
`
`
`675
`
`Generate Inventory
`
`
`
`
`
`685
`
`Communicate inventory
`Alert
`
`End
`
`FIG 11
`
`Petitioner Kiosoft Exhibit 1006
`20
`
`

`

`US 2014/0074723 A1
`
`Mar. 13, 2014
`
`COMMUNICATING PAYMENTS
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`0001. This application claims priority to Provisional
`Patent Application No. 61/700,214 entitled “COMMUNI
`CATING PAYMENTS’ and filed on Sep. 12, 2012 for Shre
`yas Kamat, which is incorporated herein by reference.
`
`BACKGROUND
`
`0002 1. Field
`0003. The subject matter disclosed herein relates to pay
`ments and more particularly relates to communicating pay
`mentS.
`0004 2. Description of the Related Art
`0005 Electronic payments are increasingly popular.
`Unfortunately, many point-of-sale devices have no access to
`a network through which to complete a transaction.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`0006. In order that the advantages of the embodiments of
`the invention will be readily understood, a more particular
`description of the embodiments briefly described above will
`be rendered by reference to specific embodiments that are
`illustrated in the appended drawings. Understanding that
`these drawings depict only some embodiments and are not
`therefore to be considered to be limiting of scope, the embodi
`ments will be described and explained with additional speci
`ficity and detail through the use of the accompanying draw
`ings, in which:
`0007 FIGS. 1A-D are schematic block diagrams illustrat
`ing embodiments of payment systems;
`0008 FIGS. 2A-D are drawings illustrating embodiments
`of purchase menus:
`0009 FIGS. 3A-Hare schematic block drawings illustrat
`ing embodiments of data stores;
`0010 FIG. 4 is a schematic block diagram illustrating one
`embodiment of the computer;
`0011
`FIG. 5 is a schematic block diagram illustrating one
`embodiment of a payment apparatus;
`0012 FIG. 6 is a schematic block diagram illustrating one
`embodiment of a point-of-sale device;
`0013 FIG. 7 is a schematic flow chart diagram illustrating
`one embodiment of a payment communication method;
`0014 FIG. 8 is a schematic flow chart diagram illustrating
`one alternate embodiment of a payment communication
`method;
`0015 FIG.9 is a schematic flow chart diagram illustrating
`one embodiment of a point-of-sale device location method;
`0016 FIG. 10 is a schematic flow chart diagram illustrat
`ing one embodiment of a payment transfer method; and
`0017 FIG. 11 is a schematic flow chart diagram illustrat
`ing one embodiment of an inventory method.
`
`DETAILED DESCRIPTION OF THE INVENTION
`0018 Reference throughout this specification to “one
`embodiment,” “an embodiment, or similar language means
`that a particular feature, structure, or characteristic described
`in connection with the embodiment is included in at least one
`embodiment. Thus, appearances of the phrases "in one
`embodiment,” “in an embodiment, and similar language
`throughout this specification may, but do not necessarily, all
`refer to the same embodiment, but mean “one or more but not
`
`all embodiments' unless expressly specified otherwise. The
`terms “including.” “comprising.” “having and variations
`thereof mean “including but not limited to unless expressly
`specified otherwise. An enumerated listing of items does not
`imply that any or all of the items are mutually exclusive
`and/or mutually inclusive, unless expressly specified other
`wise. The terms “a,” “an and “the also refer to “one or
`more' unless expressly specified otherwise.
`0019. Furthermore, the described features, advantages,
`and characteristics of the embodiments may be combined in
`any suitable manner. One skilled in the relevant art will rec
`ognize that the embodiments may be practiced without one or
`more of the specific features or advantages of a particular
`embodiment. In other instances, additional features and
`advantages may be recognized in certain embodiments that
`may not be present in all embodiments.
`0020. These features and advantages of the embodiments
`will become more fully apparent from the following descrip
`tion and appended claims, or may be learned by the practice
`of embodiments as set forth hereinafter. As will be appreci
`ated by one skilled in the art, aspects of the present invention
`may be embodied as a system, method, and/or computer
`program product. Accordingly, aspects of the present inven
`tion may take the form of an entirely hardware embodiment,
`an entirely software embodiment (including firmware, resi
`dent Software, micro-code, etc.) or an embodiment combin
`ing Software and hardware aspects that may all generally be
`referred to herein as a “circuit,” “module.” or “system. Fur
`thermore, aspects of the present invention may take the form
`of a computer program product embodied in one or more
`computer readable medium(s) having computer readable pro
`gram code embodied thereon.
`0021 Many of the functional units described in this speci
`fication have been labeled as modules, in order to more par
`ticularly emphasize their implementation independence. For
`example, a module may be implemented as a hardware circuit
`comprising custom VLSI circuits orgate arrays, off-the-shelf
`semiconductors such as logic chips, transistors, or other dis
`crete components. A module may also be implemented in
`programmable hardware devices such as field programmable
`gate arrays, programmable array logic, programmable logic
`devices or the like.
`0022 Modules may also be implemented in software for
`execution by various types of processors. An identified mod
`ule of computer readable program code may, for instance,
`comprise one or more physical or logical blocks of computer
`instructions which may, for instance, be organized as an
`object, procedure, or function. Nevertheless, the executables
`of an identified module need not be physically located
`together, but may comprise disparate instructions stored in
`different locations which, when joined logically together,
`comprise the module and achieve the stated purpose for the
`module.
`0023 Indeed, a module of computer readable program
`code may be a single instruction, or many instructions, and
`may even be distributed over several different code segments,
`among different programs, and across several memory
`devices. Similarly, operational data may be identified and
`illustrated herein within modules, and may be embodied in
`any Suitable form and organized within any suitable type of
`data structure. The operational data may be collected as a
`single data set, or may be distributed over different locations
`including over different storage devices, and may exist, at
`least partially, merely as electronic signals on a system or
`
`Petitioner Kiosoft Exhibit 1006
`21
`
`

`

`US 2014/0074723 A1
`
`Mar. 13, 2014
`
`network. Where a module or portions of a module are imple
`mented in Software, the computer readable program code may
`be stored and/or propagated on in one or more computer
`readable medium(s).
`0024. The computer readable medium may be a tangible,
`non-transitory computer readable storage medium storing the
`computer readable program code. The computer readable
`storage medium may be, for example, but not limited to, an
`electronic, magnetic, optical, electromagnetic, infrared, holo
`graphic, micromechanical, or semiconductor system, appa
`ratus, or device, or any suitable combination of the foregoing.
`0025 More specific examples of the computer readable
`storage medium may include but are not limited to a portable
`computer diskette, a hard disk, a random access memory
`(RAM), a read-only memory (ROM), an erasable program
`mable read-only memory (EPROM or Flash memory), a por
`table compact disc read-only memory (CD-ROM), a digital
`Versatile disc (DVD), an optical storage device, a magnetic
`storage device, a holographic storage medium, a microme
`chanical storage device, or any Suitable combination of the
`foregoing. In the context of this document, a computer read
`able storage medium may be any tangible medium that can
`contain, and/or store computer readable program code foruse
`by and/or in connection with an instruction execution system,
`apparatus, or device.
`0026. The computer readable medium may also be a com
`puter readable signal medium. A computer readable signal
`medium may include a propagated data signal with computer
`readable program code embodied therein, for example, in
`baseband or as part of a carrier wave. Such a propagated
`signal may take any of a variety of forms, including, but not
`limited to, electrical, electro-magnetic, magnetic, optical, or
`any Suitable combination thereof. A computer readable signal
`medium may be any computer readable medium that is not a
`computer readable storage medium and that can communi
`cate, propagate, or transport computer readable program code
`for use by or in connection with an instruction execution
`system, apparatus, or device. Computer readable program
`code embodied on a computer readable signal medium may
`be transmitted using any appropriate medium, including but
`not limited to wireline, optical fiber, Radio Frequency (RF),
`or the like, or any Suitable combination of the foregoing
`0027. In one embodiment, the computer readable medium
`may comprise a combination of one or more computer read
`able storage mediums and one or more computer readable
`signal mediums. For example, computer readable program
`code may be both propagated as an electro-magnetic signal
`through a fiber optic cable for execution by a processor and
`stored on RAM storage device for execution by the processor.
`0028 Computer readable program code for carrying out
`operations for aspects of the present invention may be written
`in any combination of one or more programming languages,
`including an object oriented programming language Such as
`Java, Smalltalk, C++, PHP or the like and conventional pro
`cedural programming languages, such as the “C” program
`ming language or similar programming languages. The com
`puter readable program code may execute entirely on the
`user's computer, partly on the user's computer, as a stand
`alone software package, partly on the user's computer and
`partly on a remote computer or entirely on the remote com
`puter or server. In the latter scenario, the remote computer
`may be connected to the user's computer through any type of
`network, including a local area network (LAN) or a wide area
`
`network (WAN), or the connection may be made to an exter
`nal computer (for example, through the Internet using an
`Internet Service Provider).
`0029. The computer program product may be shared,
`simultaneously serving multiple customers in a flexible, auto
`mated fashion. The computer program product may be stan
`dardized, requiring little customization and Scalable, provid
`ing capacity on demand in a pay-as-you-go model.
`0030 The computer program product may be stored on a
`shared file system accessible from one or more servers. The
`computer program product may be executed via transactions
`that contain data and server processing requests that use Cen
`tral Processor Unit (CPU) units on the accessed server. CPU
`units may be units of time such as minutes, seconds, hours on
`the central processor of the server. Additionally the accessed
`server may make requests of other servers that require CPU
`units. CPU units are an example that represents but one mea
`surement of use. Other measurements of use include but are
`not limited to network bandwidth, memory usage, storage
`usage, packet transfers, complete transactions etc.
`0031 When multiple customers use the same computer
`program product via shared execution, transactions are dif
`ferentiated by the parameters included in the transactions that
`identify the unique customer and the type of service for that
`customer. All of the CPU units and other measurements of use
`that are used for the services for each customer are recorded.
`When the number of transactions to any one server reaches a
`number that begins to affect the performance of that server,
`other servers are accessed to increase the capacity and to
`share the workload Likewise when other measurements of
`use Such as network bandwidth, memory usage, storage
`usage, etc. approach a capacity so as to affect performance,
`additional network bandwidth, memory usage, storage etc.
`are added to share the workload.
`0032. The measurements of use used for each service and
`customer are sent to a collecting server that Sums the mea
`Surements of use for each customer for each service that was
`processed anywhere in the network of servers that provide the
`shared execution of the computer program product. The
`Summed measurements of use units are periodically multi
`plied by unit costs and the resulting total computer program
`product service costs are alternatively sent to the customer
`and or indicated on a web site accessed by the customer which
`then remits payment to the service provider.
`0033. In one embodiment, the service provider requests
`payment directly from a customer account at a banking or
`financial institution. In another embodiment, if the service
`provider is also a customer of the customer that uses the
`computer program product, the payment owed to the service
`provider is reconciled to the payment owed by the service
`provider to minimize the transfer of payments.
`0034. The computer program product may be integrated
`into a client, server and network environment by providing
`for the computer program product to coexist with applica
`tions, operating systems and network operating systems soft
`ware and then installing the computer program product on the
`clients and servers in the environment where the computer
`program product will function.
`0035. In one embodiment software is identified on the
`clients and servers including the network operating system
`where the computer program product will be deployed that
`are required by the computer program productor that work in
`conjunction with the computer program product. This
`
`Petitioner Kiosoft Exhibit 1006
`22
`
`

`

`US 2014/0074723 A1
`
`Mar. 13, 2014
`
`includes the network operating system that is software that
`enhances a basic operating system by adding networking
`features.
`0036. In one embodiment, software applications and ver
`sion numbers are identified and compared to the list of soft
`ware applications and version numbers that have been tested
`to work with the computer program product. Those Software
`applications that are missing or that do not match the correct
`version will be upgraded with the correct version numbers.
`Program instructions that pass parameters from the computer
`program product to the Software applications will be checked
`to ensure the parameter lists match the parameter lists
`required by the computer program product. Conversely
`parameters passed by the Software applications to the com
`puter program product will be checked to ensure the param
`eters match the parameters required by the computer program
`product. The client and server operating systems including
`the network operating systems will be identified and com
`pared to the list of operating systems, version numbers and
`network software that have been tested to work with the
`computer program product. Those operating systems, version
`numbers and network software that do not match the list of
`tested operating systems and version numbers will be
`upgraded on the clients and servers to the required level.
`0037. In response to determining that the software where
`the computer program product is to be deployed, is at the
`correct version level that has been tested to work with the
`computer program product, the integration is completed by
`installing the computer program product on the clients and
`SWCS.
`0038 Aspects of the embodiments are described below
`with reference to schematic flowchart diagrams and/or sche
`matic block diagrams of methods, apparatuses, systems, and
`computer program products according to embodiments of the
`invention. It will be understood that each block of the sche
`matic flowchart diagrams and/or schematic block diagrams,
`and combinations of blocks in the schematic flowchart dia
`grams and/or schematic block diagrams, can be implemented
`by computer readable program code. The computer readable
`program code may be provided to a processor of a general
`purpose computer, special purpose computer, sequencer, or
`other programmable data processing apparatus to produce a
`machine, such that the instructions, which execute via the
`processor of the computer or other programmable data pro
`cessing apparatus, create means for implementing the func
`tions/acts specified in the schematic flowchart diagrams and/
`or schematic block diagrams block or blocks.
`0039. The computer readable program code may also be
`stored in a computer readable medium that can direct a com
`puter, other programmable data processing apparatus, or
`other devices to function in a particular manner, Such that the
`instructions stored in the computer readable medium produce
`an article of manufacture including instructions which imple
`ment the function/act specified in the schematic flowchart
`diagrams and/or schematic block diagrams block or blocks.
`0040. The computer readable program code may also be
`loaded onto a computer, other programmable data processing
`apparatus, or other devices to cause a series of operational
`steps to be performed on the computer, other programmable
`apparatus or other devices to produce a computer imple
`mented process Such that the program code which executed
`on the computer or other programmable apparatus provide
`processes for implementing the functions/acts specified in the
`flowchart and/or block diagram block or blocks.
`
`0041. The schematic flowchart diagrams and/or schematic
`block diagrams in the Figures illustrate the architecture, func
`tionality, and operation of possible implementations of appa
`ratuses, systems, methods and computer program products
`according to various embodiments of the present invention. In
`this regard, each block in the schematic flowchart diagrams
`and/or schematic block diagrams may represent a module,
`segment, or portion of code, which comprises one or more
`executable instructions of the program code for implement
`ing the specified logical function(s).
`0042. It should also be noted that, in some alternative
`implementations, the functions noted in the block may occur
`out of the order noted in the Figures. For example, two blocks
`shown in Succession may, in fact, be executed Substantially
`concurrently, or the blocks may sometimes be executed in the
`reverse order, depending upon the functionality involved.
`Other steps and methods may be conceived that are equivalent
`in function, logic, or effect to one or more blocks, or portions
`thereof, of the illustrated Figures.
`0043 Although various arrow types and line types may be
`employed in the flowchart and/or block diagrams, they are
`understood not to limit the scope of the corresponding
`embodiments. Indeed, some arrows or other connectors may
`be used to indicate only the logical flow of the depicted
`embodiment. For instance, an arrow may indicate a waiting or
`monitoring period of unspecified duration between enumer
`ated steps of the depicted embodiment. It will also be noted
`that each block of the block diagrams and/or flowchart dia
`grams, and combinations of blocks in the block diagrams
`and/or flowchart diagrams, can be implemented by special
`purpose hardware-based systems that perform the specified
`functions or acts, or combinations of special purpose hard
`ware and computer readable program code.
`0044) The description of elements in each figure may refer
`to elements of proceeding figures. Like numbers refer to like
`elements in all figures, including alternate embodiments of
`like elements.
`0045 FIGS. 1A-D are schematic block diagrams illustrat
`ing embodiments of payment systems 100. The system 100a
`depicted in FIG. 1A includes a mobile device 10, a point-of
`sale device 20, and a clearing house 30.
`0046. In the depicted embodiment, the point-of-sale
`device 20 is not in communication with the network 12. Thus
`the point-of-sale device 20 may be unable to communicate
`payment information, receive payment confirmations, verify
`the validity of a payment account, and the like. In the past,
`such point-of-sale devices 20 would be unable to receive
`electronic payments. However, the increasing popularity of
`electronic payments would put Such a point-of-sale device 20
`at a distinct competitive advantage.
`0047. The embodiments described herein securely com
`municate payments between the mobile device 10 and the
`point-of-sale device 20 and/or another mobile device 10. In
`addition, the payments may be verifiable. The point-of-sale
`device 20 is thus able to receive electronic payments even if
`the point-of-sale device 20 is not connected to the network 12.
`The point-of-sale device 20 may be a vending machine, a food
`Vendor kiosk, a transit kiosk, a service kiosk, a parking kiosk,
`a ticket kiosk, a rental kiosk, a fuel kiosk, and the like.
`0048. The mobile device 10 may be a mobile telephone, a
`tablet computer, an eyeglass computer, a wearable computer,
`a payment fob, or the like. The mobile device 10 may com
`municate over a network connection 24 through the network
`12 with the clearing house 30. The network 12 may be a
`
`Petitioner Kiosoft Exhibit 1006
`23
`
`

`

`US 2014/0074723 A1
`
`Mar. 13, 2014
`
`cellular telephone network, a wide-area network, a local area
`network, a wireless network, the Internet, a BLUETOOTHR)
`network, or combinations thereof.
`0049. The mobile device 10 may communicate with the
`point-of-sale device 20 through short range communications
`14. In one embodiment, the short range communications 14
`maybe optical communications. For example, one of the
`mobile device or the point-of-sale device 20 may display a
`point-of-sale code encoded as a graphic while the other scans
`the graphic. Alternatively, the short range communications 14
`may be infrared communications. In one embodiment, the
`short range communications 14 conform to a near field com
`munication (NFC) protocol including but are not limited to
`ISO/IEC 1809.
`0050. The clearing house 30 may be embodied in one or
`more servers. In one embodiment, the clearing house 30
`maintains a user account associated with the mobile device
`10. The user account may account information for obtaining
`funds and/or an account balance. However, the account infor
`mation is never communicated outside of the clearing house
`3O.
`0051. In one embodiment, the mobile device 10 receives
`the point-of-sale code from the point-of-sale device 20 over
`the short range communications 14. The mobile device 10
`may further communicate the point-of-sale code to the clear
`ing house 30. The point-of-sale code may be encrypted. The
`clearing house 30 may generate a payment authorization. The
`payment authorization may be encrypted. The payment
`authorization may be communicated through the mobile
`device 10 and the short range communications 14 to the
`point-of-sale device 20. Upon receipt of the payment autho
`rization, the point-of-sale device 20 may complete the trans
`action. For example, the point-of-sale device 20 may deliver
`an item Such as food, fuel, service, and the like.
`0052. The system 100b depicted in FIG. 1B further
`includes a transmission device 40. In one embodiment, the
`transmission device 40 downloads payment authorizations
`from the point-of-sale device 20. The transmission device 40
`may be a mobile computer, a tablet computer, a mobile tele
`phone, a custom device, and the like. The transmission device
`40 may receive the payment authorizations over a communi
`cation link 16. The communication link 16 may be a universal
`serial bus (USB) connection, NFC protocol communications,
`a BLUETOOTHR) connection, or the like. The transmission
`device 40 may communicate the payment authorizations
`through a network connection 24 over the network 12 to the
`clearing house 30. In one embodiment, the transmission
`device 40 must provide a secure key in order to receive the
`payment authorizations. In a certain embodiment, the pay
`ment authorizations are encrypted.
`0053. In the system 100c depicted in FIG. 1C, the point
`of-sale device 20 may have a network connection 24 with the
`network 12. The point-of-sale device 20 may communicate
`the payment authorizations over the network 12 to the clear
`ing house 30. In one embodiment, the point-of-sale device 20
`encrypts the payment authorizations with a secure key for
`transmission to the clearing house 30.
`0054) In the system 100d depicted in FIG. 1D, a first
`mobile device 10a may make a payment to a second mobile
`device 10b. In one embodiment, the first mobile device 10a
`receives the point-of-sale code from the second mobile device
`10b over the short range communications 14. The first mobile
`device 10a may further communicate the point-of-sale code
`to the clearing house 30. The point-of-sale code may be
`
`encrypted. The clearing house 30 may generate the payment
`authorization. The payment authorization may be encrypted.
`The payment authorization may be communicated through
`the first mobile device 10a and the short range communica
`tions 14 to the second mobile device 10b.
`0055 FIGS. 2A-D are drawings illustrating embodiments
`of purchase menus 210 displayed on mobile devices 10. As
`depicted in FIG. 2A, the purchase menu 210 may display a
`plurality of items 240. In addition, the purchase menu 210
`may display a plurality of corresponding prices 250. The user
`may select an item 240 and the corresponding price 250. In
`one embodiment, the user may select a plurality of items 240
`and prices 250. In a certain embodiment, the user may activate
`a select button 260 to initiate a transaction. The purchase
`menu 210 may also display purchase totals, contract terms,
`and the like.
`0056 FIG. 2B depicts the purchase menu 210 with mul
`tiple items 240 selected and a total displayed. FIG.2C depicts
`the purchase menu 210 with a s