Patent ID: 12211028

DETAILED DESCRIPTION OF THE INVENTION

It is to be understood that the figures and descriptions of the present invention have been simplified to illustrate elements that are relevant for a clearer comprehension of the present invention, while eliminating, for the purpose of clarity, many other elements found in payment kiosk systems and methods of payment collection. Those of ordinary skill in the art may recognize that other elements and/or steps are desirable and/or required in implementing the present invention. However, because such elements and steps are well known in the art, and because they do not facilitate a better understanding of the present invention, a discussion of such elements and steps is not provided herein. The disclosure herein is directed to all such variations and modifications to such elements and methods known to those skilled in the art.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Although any methods and materials similar or equivalent to those described herein can be used in the practice or testing of the present invention, the preferred methods and materials are described.

As used herein, each of the following terms has the meaning associated with it in this section.

The articles “a” and “an” are used herein to refer to one or to more than one (i.e., to at least one) of the grammatical object of the article. By way of example, “an element” means one element or more than one element.

“About” as used herein when referring to a measurable value such as an amount, a temporal duration, and the like, is meant to encompass variations of ±20%, ±10%, ±5%, ±1%, and ±0.1% from the specified value, as such variations are appropriate.

Ranges: throughout this disclosure, various aspects of the invention can be presented in a range format. It should be understood that the description in range format is merely for convenience and brevity and should not be construed as an inflexible limitation on the scope of the invention. Where appropriate, the description of a range should be considered to have specifically disclosed all the possible subranges as well as individual numerical values within that range. For example, description of a range such as from 1 to 6 should be considered to have specifically disclosed subranges such as from 1 to 3, from 1 to 4, from 1 to 5, from 2 to 4, from 2 to 6, from 3 to 6 etc., as well as individual numbers within that range, for example, 1, 2, 2.7, 3, 4, 5, 5.3, and 6. This applies regardless of the breadth of the range.

Referring now in detail to the drawings, in which like reference numerals indicate like parts or elements throughout the several views, in various embodiments, presented herein is a contactless payment kiosk system and method.

Embodiments of the system and method described herein allows any biller to collect cash payments through self-service kiosk. The biller's mobile software application communicates with a controller, which in certain embodiments is a centralized application program interface (API) running on a remote server to accept cash payments from the kiosk.

FIGS.1A-1Cshow, according to one embodiment, steps for staging a purchase10, presenting and receiving an invoice30, and making payment with confirmation50. With reference to the diagram inFIG.1A, in one embodiment, a purchase is staged beginning with a purchase of financial services12at a mobile device, which is communicated with a financial services broker API14located on a remote server. The financial services provider16will generate an invoice token18, and an invoice based on the token is presented at the mobile device20and in parallel referenced at the collections database22. With reference toFIG.1B, in one embodiment, an invoice is presented and retrieved30. A present invoice token32is generated on a mobile device and transmitted to a kiosk by contactless method34as described in more detail below. A remote server finds the invoice and confirms with the financial service provider36. The financial service provider confirms the product is still valid38and via the remote server asks the kiosk to collect funds40. The kiosk enables the relevant payment device42and instructs the customer to make payment44. With reference toFIG.1C, payment is made and confirmed50according to one embodiment. A kiosk collects payment52, which can be for example cash, coins, checks, cards, and vouchers. The remote server confirms receivables54and the financial services provider finalizes the purchase56. The remote server marks the invoice as paid58, and the kiosk prints, texts or otherwise displays a receipt60. The mobile device confirms payment has been made62.

With reference now toFIG.1D, a method100for payment collection is now described according to one embodiment. An application program interface received a payment transaction instruction from a mobile device102. The payment instruction can for example be generated by an app running on the mobile device. The payment instruction can include data for the intended transaction, such as user account number assigned by the biller, a user password or pin number, an invoice number related to the user account, the amount of money that the user intends to send the biller for the invoice, an account at the financial institution that some or all of the payment should be drawn from, and other preferences such as what form of receipt the user prefers for documenting the transaction outcome.

The application program interface then generates a transaction code and sends the transaction code to the user's mobile device for display on the mobile device screen and sends it to the mobile device104. The transaction code can be for example a quick response code (QR code), an alphanumeric code, a barcode, an image, a video, an audio code, a combination of these code types or other types of codes known in the art. The code is compatible with output options on the user's mobile device, such as a screen display or a speaker.

The kiosk can include a scanner or imaging element for receiving the code as input. The user presents the code to a touch-free code input module, such as within a cavity or otherwise in proximity of a scanner, microphone or imaging element (depending on the type of code utilized by the system), and the touch-free code input module receives the code and sends it to the application program interface to reconcile with the transaction code106.

Next, the kiosk can prompt payment from the user, and the user provides a form of payment108. The form of payment can include for example one or more of inserting cash, payment by digital currency, payment card, payment voucher, or payment from a particular account at a financial institution associated with the user.

Finally, the application program interface determines whether the transaction is complete based on reconciling or comparing the received scan generated by the kiosk and the received form of payment110. If there is an error, the user can be alerted by the kiosk and/or their mobile device, and the error can include information regarding the nature of the error and instructions for next steps to fix the error. If there is no error, the system can provide an indication that the transaction is complete, and a receipt (hard copy or digital) can be provided.

Now with reference toFIGS.2A,2B, and2C, a contactless payment kiosk system250and method according to one embodiment can execute the method and algorithms for contactless payment on a computer platform which can include one or more local or remote executable software platforms, mobile device platforms, or a hosted Internet or network program or portal. In one embodiment, only portions of the system are computer operated, and in other embodiments, the entire system is computer operated. Any computing device as would be understood by those skilled in the art may be used with the system, including desktop or mobile devices, laptops, desktops, tablets, smartphones or other wireless digital/cellular phones, or other thin client devices as would be understood by those skilled in the art. The contactless payment kiosk platform is fully integrable for use with any additional platform and data output that may be used for communicating with other platforms, such as for example financial institution platforms, user information platforms, cyber security platforms and payment collection platforms.

For example, the computer operable components of the contactless payment kiosk system may reside entirely on a single computing device or may reside on a central server and run on any number of end-user devices via a communications network. The computing devices may include at least one processor, standard input and output devices, as well as all hardware and software typically found on computing devices for storing data and running programs, and for sending and receiving data over a network, if needed. If a central contactless payment kiosk server is used, it may be one server or, more preferably, a combination of scalable servers, providing functionality as a network mainframe server, a web server, a mail server, and central database server, all maintained and managed by an administrator or operator of the system. The computing devices may also be connected directly or via a network to remote databases, such as for additional storage backup, and to allow for the communication of files, email, software, and any other data formats between two or more computing devices, such as between the contactless payment kiosk system, a user mobile device, biller systems and financial institution platforms. There are no limitations to the number, type or connectivity of the databases utilized by the contactless payment kiosk system. The communications network can be a wide area network and may be any suitable networked system understood by those having ordinary skill in the art, such as, for example, an open, wide area network (e.g., the Internet), an electronic network, an optical network, a wireless network, a physically secure network or virtual private network, and any combinations thereof. The communications network may also include any intermediate nodes, such as gateways, routers, bridges, Internet service provider networks, public-switched telephone networks, proxy servers, firewalls, and the like, such that the communications network may be suitable for the transmission of information items and other data throughout the system.

Further, the communications network may also use standard architecture and protocols as understood by those skilled in the art, such as, for example, a packet switched network for transporting information and packets in accordance with a standard transmission control protocol/Internet protocol (“TCP/IP”). Additionally, the system may utilize any conventional operating platform or combination of platforms (Windows, Mac OS, Unix, Linux, Android, etc.) and may utilize any conventional networking and communications software as would be understood by those skilled in the art.

To protect data, such as sensitive user financial and personal identification data, and to comply with state and federal laws pertaining to protection of financial and personal identification data, an encryption standard may be used to protect files from unauthorized interception over the network. Any encryption standard or authentication method as may be understood by those having ordinary skill in the art may be used at any point in the system of the present invention. For example, encryption may be accomplished by encrypting an output file by using a Secure Socket Layer (SSL) with dual key encryption. Additionally, the system may limit data manipulation, or information access. For example, a system administrator may allow for administration of the contactless payment kiosk platform at one or more levels, such as at an individual reviewer, a review team manager, a quality control review manager, or a system manager. A system administrator may also implement access or use restrictions for users at any level. Such restrictions may include, for example, the assignment of usernames and passwords required for use of the contactless payment kiosk, backend administrative access, associated mobile device apps, or the selection of one or more data types that the subservient user is allowed to view or manipulate.

As described in further detail herein, the payment system may operate as application software, which may be managed by a local or remote computing device. The software may include a software framework or architecture that optimizes ease of use of at least one existing software platform, and that may also extend the capabilities of at least one existing software platform. The application architecture may approximate the actual way users organize and manage electronic files, and thus may organize use activities in a natural, coherent manner while delivering use activities through a simple, consistent, and intuitive interface within each application and across applications. The architecture may also be reusable, providing plug-in capability to any number of applications, without extensive re-programming, which may enable parties outside of the system to create components that plug into the architecture. Thus, software or portals in the architecture may be extensible and new software or portals may be created for the architecture by any party.

The system may provide payment software applications accessible to one or more users, such as different users associated with a single biller or financial institution to perform one or more functions. Such applications may be available at the same location as the user, or at a location remote from the user. Each application may provide a graphical user interface (GUI) for ease of interaction by the user with information resident in the system. A GUI may be specific to a user, set of users, or type of user, or may be the same for all users or a selected subset of users. The system software may also provide a master GUI set that allows a user to select or interact with GUIs of one or more other applications, or that allows a user to simultaneously access a variety of information otherwise available through any portion of the system.

The system software may also be a portal or SaaS that provides, via the GUI, remote access to and from the contactless payment kiosk system. The software may include, for example, a network browser as well as other standard applications. The software may also include the ability, either automatically based upon a user request in another application, or by a user request, to search, or otherwise retrieve particular data from one or more remote points, such as on the Internet or from a limited or restricted database. The software may vary by user type or may be available to only a certain user type, depending on the needs of the system. Users may have some portions, or all of the application software resident on a local computing device, or may simply have linking mechanisms, as understood by those skilled in the art, to link a computing device to the software running on a central server via the communications network, for example. As such, any device having, or having access to, the software may be capable of uploading, or downloading, any information item or data collection item, or informational files to be associated with such files.

Presentation of data through the software may be in any sort and number of selectable formats. For example, a multi-layer format may be used, wherein additional information is available by viewing successively lower layers of presented information. Such layers may be made available by the use of drop-down menus, tabbed folder files, or other layering techniques understood by those skilled in the art or through a novel natural language interface as described herein throughout.

The contactless payment kiosk system software may also include standard reporting mechanisms, such as generating a printable receipt of the transaction, or an electronic results report that can be transmitted to any communicatively connected computing device, such as a generated email message or file attachment. Likewise, particular results of the system transaction can trigger an alert signal, such as the generation of an alert email, text or phone call, to alert a user, biller or person associated with the user or biller. Further embodiments of such mechanisms are described below and according to standards of such systems understood by those skilled in the art.

Embodiments of the system can include payors making remittances to payees, such as tenants making payments to landlords for rent payment. In certain embodiments, the system can dispense cash for applications like check cashing or micro loans. Thus, a biller can in certain embodiments by any entity receiving funds, or in other embodiments may be an entity distributing funds (for example a system partner that needs to dispense cash to a customer for refunds or any other type of compensation). In one embodiment, a contactless transaction system includes a kiosk comprising a token capture module. A controller is configured to communicate with the kiosk and a mobile device, the controller configured to receive a transaction instruction from the mobile device, generate a token for display on the mobile device corresponding to the transaction instruction, send the token to the mobile device, receive code data generated by the kiosk based on the token displayed on the mobile device, receive a transaction confirmation from the kiosk, and determine whether the transaction is complete based on the received code data generated by the kiosk and the transaction confirmation.

As shown inFIG.2A, a contactless payment system can be configured as a cloud system203, where payment services201, an open API202, atm/debit card processors204, API services205, a kiosk such as a smart ATM206, a mobile device and application207, and a desktop device and application208are in communication via the cloud system203.

As shown inFIG.2Ban API can include an open API app217, a 3rdparty API218, an open API219, a cloud API219, a database221, partner balances and access control222, and a kiosk API209. The kiosk API209can further include a kiosk browser210, a clamshell211, a camera agent212, a cash acceptor agent213, a printer agent214, a cash dispenser agent215and a card reader agent216.

As shown inFIG.2C, the system can include a mobile device250, a network260, a kiosk device270, and a financial service provider280. The mobile device250can include a display251configured to display code data, a speaker252configured to produce a sound encoding code data, a transceiver configured to communicate with the kiosk device, and a network device254configured to communicate with the network260. In some embodiments, an external input255is further included. The network260can include a remote server261and a database262.

The kiosk device270can include a network device271configured to communicate with the network260, a controller272, a display273, a transceiver274configured to communicate with the mobile device250, a payment module275, a token capture module276, and a code input module277including a microphone278and/or and imaging device279.

In some embodiments, the controller272can be configured to receive payment transaction instructions from the mobile device250, generate a transaction code for display on the mobile device250corresponding to the payment transaction instructions, send the transaction code to the mobile device250, receive code data generated by the kiosk of the transaction code displayed on the mobile device250, receive a payment confirmation from the kiosk270, and determine whether the transaction is complete based on the received code data generated by the kiosk270and the payment confirmation.

In some aspects of the present invention, software executing the instructions provided herein may be stored on a non-transitory computer-readable medium, wherein the software performs some or all of the steps of the present invention when executed on a processor.

Aspects of the invention relate to algorithms executed in computer software. Though certain embodiments may be described as written in particular programming languages, or executed on particular operating systems or computing platforms, it is understood that the system and method of the present invention is not limited to any particular computing language, platform, or combination thereof. Software executing the algorithms described herein may be written in any programming language known in the art, compiled or interpreted, including but not limited to C, C++, C#, Objective-C, Java, JavaScript, MATLAB, Python, PHP, Perl, Ruby, or Visual Basic. It is further understood that elements of the present invention may be executed on any acceptable computing platform, including but not limited to a server, a cloud instance, a workstation, a thin client, a mobile device, an embedded microcontroller, a television, or any other suitable computing device known in the art.

Parts of this invention are described as software running on a computing device. Though software described herein may be disclosed as operating on one particular computing device (e.g. a dedicated server or a workstation), it is understood in the art that software is intrinsically portable and that most software running on a dedicated server may also be run, for the purposes of the present invention, on any of a wide range of devices including desktop or mobile devices, laptops, tablets, smartphones, watches, wearable electronics or other wireless digital/cellular phones, televisions, cloud instances, embedded microcontrollers, thin client devices, or any other suitable computing device known in the art.

Similarly, parts of this invention are described as communicating over a variety of wireless or wired computer networks. For the purposes of this invention, the words “network”, “networked”, and “networking” are understood to encompass wired Ethernet, fiber optic connections, wireless connections including any of the various 802.11 standards, cellular WAN infrastructures such as 3G, 4G/LTE, or 5G networks, Bluetooth®, Bluetooth® Low Energy (BLE) or Zigbee® communication links, or any other method by which one electronic device is capable of communicating with another. In some embodiments, elements of the networked portion of the invention may be implemented over a Virtual Private Network (VPN).

FIG.3and the following discussion are intended to provide a brief, general description of a suitable computing environment in which the invention may be implemented. While the invention is described above in the general context of program modules that execute in conjunction with an application program that runs on an operating system on a computer, those skilled in the art will recognize that the invention may also be implemented in combination with other program modules.

Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

FIG.3depicts an illustrative computer architecture for a computer300for practicing the various embodiments of the invention. The computer architecture shown inFIG.3illustrates a conventional personal computer, including a central processing unit350(“CPU”), a system memory305, including a random-access memory310(“RAM”) and a read-only memory (“ROM”)315, and a system bus335that couples the system memory305to the CPU350. A basic input/output system containing the basic routines that help to transfer information between elements within the computer, such as during startup, is stored in the ROM315. The computer300further includes a storage device320for storing an operating system325, application/program330, and data.

The storage device320is connected to the CPU350through a storage controller (not shown) connected to the bus335. The storage device320and its associated computer-readable media, provide non-volatile storage for the computer300. Although the description of computer-readable media contained herein refers to a storage device, such as a hard disk or CD-ROM drive, it should be appreciated by those skilled in the art that computer-readable media can be any available media that can be accessed by the computer300.

By way of example, and not to be limiting, computer-readable media may comprise computer storage media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, DVD, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information, and which can be accessed by the computer.

According to various embodiments of the invention, the computer300may operate in a networked environment using logical connections to remote computers through a network340, such as TCP/IP network such as the Internet or an intranet. The computer300may connect to the network340through a network interface unit345connected to the bus335. It should be appreciated that the network interface unit345may also be utilized to connect to other types of networks and remote computer systems.

The computer300may also include an input/output controller355for receiving and processing input from a plurality of input/output devices360, including a keyboard, a mouse, a touchscreen, a camera, a microphone, a controller, a joystick, or other type of input device. Similarly, the input/output controller355may provide output to a display screen, a printer, a speaker, or other type of output device. The computer300can connect to the input/output device360via a wired connection including, but not limited to, fiber optic, ethernet, or copper wire or wireless means including, but not limited to, Bluetooth, Near-Field Communication (NFC), infrared, or other suitable wired or wireless connections.

As mentioned briefly above, a plurality of program modules and data files may be stored in the storage device320and RAM310of the computer300, including an operating system325suitable for controlling the operation of a networked computer. The storage device320and RAM310may also store one or more applications/programs330. In particular, the storage device320and RAM310may store an application/program330for providing a variety of functionalities to a user. For instance, the application/program330may comprise many types of programs such as a word processing application, a spreadsheet application, a desktop publishing application, a database application, a gaming application, internet browsing application, electronic mail application, messaging application, and the like. According to an embodiment of the present invention, the application/program330comprises a multiple functionality software application for providing word processing functionality, slide presentation functionality, spreadsheet functionality, database functionality and the like.

The computer300in some embodiments can include a variety of sensors365for monitoring the environment surrounding and the environment internal to the computer300. These sensors365can include a Global Positioning System (GPS) sensor, a photosensitive sensor, a gyroscope, a magnetometer, thermometer, a proximity sensor, an accelerometer, a microphone, biometric sensor, barometer, humidity sensor, radiation sensor, or any other suitable sensor.

EXPERIMENTAL EXAMPLES

The invention is now described with reference to the following Examples. These Examples are provided for the purpose of illustration only and the invention should in no way be construed as being limited to these Examples, but rather should be construed to encompass any and all variations which become evident as a result of the teaching provided herein.

Without further description, it is believed that one of ordinary skill in the art can, using the preceding description and the following illustrative examples, make and utilize the present invention and practice the claimed methods. The following working examples therefore, specifically point out the preferred embodiments of the present invention, and are not to be construed as limiting in any way the remainder of the disclosure.

With reference now toFIGS.4A-4D, according to one embodiment for money transfer and bill payment, a customer launches the cell phone app and logs in (Step 1). A customer is presented with the transactions he/she made before (Step 2). The screen shows that the customer sent money to Mexico and paid a cable bill. The customer can choose to make the payment again by clicking on an item in the “Payment history” box. Or the customer can make a new payment by clicking on the Products button to bring up the menu of services offered (Step 3). Next, the customer chooses the payment amount (Step 4). In the example below, the customer is sending $50 to Mexico. The payment appears in the shopping cart (Step 5). Next, the customer walks up to the kiosk and brings up the QR code by clicking on the QR code icon on the cell phone app (Step 6). The QR code reader on the kiosk reads the QR code on the cell phone app (Step 7), the kiosk prompts the customer to put cash in (Step 8), and the customer puts the cash into the kiosk (Step 9). Now, the transaction is complete (Step 10). The customer has a text receipt as well as the paper receipt from the kiosk. With reference now toFIGS.4E and4F, according to one embodiment for check cashing, a customer launches a cell phone app and takes a picture of the check (Step 1). The customer submits the check for verification. The check is reviewed by an automated system or by a human being (Step 2). If the check is approved, the customer gets the message shown on the phone. Next, the customer walks up to the kiosk to scan the QR code (Step 3). The customer is prompted to insert the check into the kiosk (Step 4). The customer then inserts the check into the kiosk (step 5). The software verifies the scanned check is the same check the customer got approved from the cell phone app. If the scanned check at the kiosk is the same check the customer submitted with his/her cell phone app, cash is dispensed (Step 6). If not, the check is rejected. Now the transaction is complete (Step 7). The customer gets a text receipt as well as the paper receipt from the kiosk.

The disclosures of each and every patent, patent application, and publication cited herein are hereby incorporated herein by reference in their entirety. While this invention has been disclosed with reference to specific embodiments, it is apparent that other embodiments and variations of this invention may be devised by others skilled in the art without departing from the true spirit and scope of the invention.