CONTACTLESS WIRELESS TRANSACTION PROCESSING SYSTEM
A wireless transaction processing system that includes a seller account and a buyer account with the buyer having an Internet enabled device that can access the wireless transaction processing system. The wireless transaction processing system, through the Internet enabled device of the buyer enables full processing of transactions without the need for physical cards or an established sales environment. Additionally, the system allows for the direct promotion of products and services to consumers by any entity.
This is a Continuation application claiming the benefit of priority of the co-pending U.S. Utility Non-Provisional patent application Ser. No. 13/467,935, with a filing date May 9, 2012, which application is itself a Continuation-In-Part application claiming the benefit of priority of the co-pending U.S. Utility Non-Provisional patent application Ser. No. 13/090,191, with a filing date Apr. 19, 2011, which application is itself a Continuation-In-Part application claiming the benefit of priority of the co-pending U.S. Utility Non-Provisional patent application Ser. No. 13/024,276, with a filing date of Feb. 9, 2011, the entire disclosures of all applications are expressly incorporated by reference in their entirety herein.
BACKGROUND OF THE INVENTION1. Field of the Invention
This invention relates to wireless transaction processing system and, more particularly, to contactless transaction processing system using wireless mobile Internet devices.
2. Description of Related Art
Conventional wireless transaction or payment processing systems using wireless devices (such as handheld devices) have been known for a number of years. Most of the conventional wireless transaction or payment-processing systems using wireless devices are vendor-centric. That is, the entire system is designed and implemented with the view that the retailer is the “hub” or the focal point of the payment processing systems for transactions, and most (if not all) functionality to access the conventional wireless transaction or payment-processing systems is initiated by the merchant or the vendor.
Most vendor or merchant-centric systems are based on a retail business-model, which requires a retailer or merchant and a consumer with at least one card account (credit cards, debit cards, etc.). Conventional systems that are used in a retail environment suffer from obvious disadvantages in that they require the retailers or merchants to obtain additional, dedicated specialty wireless hardware or equipment to perform or execute wireless transaction or payment processing. Further, most of the retail or merchant dedicated hardware used for execution of wireless transactions require custom configuration and installation, which further add to the overall cost of providing wireless transaction processing service at the retail or merchant establishment.
Other obvious disadvantages of the conventional wireless transaction or payment processing systems using wireless devices is that they require wireless communication between the handheld device and the dedicated, specialty wireless hardware or equipment at the retail or merchant location. In most cases, wireless communication between any two entities introduces the possibility of interception (by a third party) of that which is wirelessly communicated between the two entities (e.g., the wireless handheld device and the dedicated wireless hardware at the retail or merchant location). With conventional systems, the communication between the handheld device and the merchant specialty equipment include confidential personal information, which further jeopardizes the overall identity and security of the users. Further, the mobile Internet devices must somehow be configured to sync and function or work with the specialty equipment, which makes the mobile Internet device even more vulnerable to identify theft. Additionally, conventional systems developed (e.g., Near Field Communication—NFC) require specialized hardware to be installed either onto or within the wireless device (e.g., mobile phone) for full implementation of conventional wireless transaction or payment processing systems. Still other disadvantages of some conventional wireless transaction processing systems is that they aim to eliminate the use of encryption technology, which further enhances interception of wireless exchange of information between two entities by a third party.
Finally, the merchant or vendor-centric systems or retail business-models mentioned above do not accommodate entity-to-entity direct transactions where both entities are non-retailers or non-merchants (e.g., both entities may, for example, be individual persons).
Accordingly, in light of the current state of the art and the drawbacks to current wireless transaction processing systems mentioned above, a need exists for wireless transaction processing system that would be consumer-centric where the entities such as retailers or consumers (e.g., the mobile devices used) are not required to obtain additional, dedicated specialty wireless hardware or equipment to perform or execute wireless transaction or payment processing. Further, even if such transactions are accomplished wirelessly using additional wireless equipment, no personal or private confidential information is exchanged. Additionally, a need exists for a consumer-centric wireless transaction processing system where information exchanged is encrypted for security. Furthermore, a need exists for a consumer-centric wireless transaction processing system that would enable personal, direct transactions between individuals without requiring credit cards, involvement of retailers or merchants, or the involvement of fund transferring institutions. Finally, a need exists for integration of most types of transactions, including, but not limited to, most cashless transactions, payment, purchasing, and direct fund transfer between entities within a single system accessed by an Internet enabled mobile device.
BRIEF SUMMARY OF THE INVENTIONAn exemplary optional aspect of the present invention provides a wireless transaction processing system, comprising:
a remote transaction module (RTM);
a RTM database that includes RTM item data for a product or service;
a RTM item ID associated with the RTM item data for the product or service;
the RTM item ID used in a variety of media, enabling access to and retrieval of the RTM item data associated with the product or service from one or more servers of WTPS, to display content of the RTM item data on the mobile device.
Another exemplary optional aspect of the present invention provides a wireless transaction processing system, wherein:
the displayed content of the RTM item data includes various controls for selection and transaction processes for the product or service, including further recommendations related to the selected product or service.
Another exemplary optional aspect of the present invention provides a remote transaction (RT) system, comprising:
a RT database that includes RT item data for a product or service;
a RT item ID associated with the RT item data for the product or service;
the RT item ID used in a variety of media, enabling access to and retrieval of the RTM item data associated with the product or service from one or more servers of RT, to display content of the RT item data on the mobile device.
Another exemplary optional aspect of the present invention provides a RT system, wherein:
the displayed content of the RT item data includes various controls for selection and transaction processes for the product or service, including further recommendations related to the selected product or service.
Another exemplary optional aspect of the present invention provides a wireless transaction processing system (WTPS), comprising:
a loyalty module (LM);
a LM database that includes LM item data for a promotion or reward;
a LM item ID associated with the LM item data for the promotion or reward;
the LM item ID used in a variety of media, enabling access to and retrieval of the LM item data associated with the promotion or reward from one or more servers of WTPS, to display content of the LM item data on the mobile device.
Another exemplary optional aspect of the present invention provides a loyalty system, comprising:
a loyalty database that includes loyalty item data for a promotion or reward;
a loyalty item ID associated with the loyalty item data for the promotion or reward;
the loyalty item ID used in a variety of media, enabling access to and retrieval of the loyalty item data associated with the promotion or reward from one or more servers of loyalty system, to display content of the loyalty item data on the mobile device.
Another exemplary optional aspect of the present invention provides a system, comprising:
an integration between a loyalty system and a remote transaction system that allows for immediate purchase or redemption of at least one item presented through the loyalty system.
Another exemplary optional aspect of the present invention provides a wireless transaction processing system (WTPS), comprising:
a unified commerce architecture for multi-platform transactions and communications between disparate and distinct entities.
Another exemplary optional aspect of the present invention provides WTPS, wherein:
the unified commerce architecture includes one or more multi-configurable devices, enabling multi-platform transactions and communications between disparate and distinct entities.
Such stated advantages of the invention are only examples and should not be construed as limiting the present invention. These and other features, aspects, and advantages of the invention will be apparent to those skilled in the art from the following detailed description of preferred non-limiting exemplary embodiments, taken together with the drawings and the claims that follow.
It is to be understood that the drawings are to be used for the purposes of exemplary illustration only and not as a definition of the limits of the invention. Throughout the disclosure, the word “exemplary” is used exclusively to mean “serving as an example, instance, or illustration.” Any embodiment described as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.
Referring to the drawings in which like reference character(s) present corresponding part(s) throughout:
FIGS. 7A to 7C-2 are non-limiting, exemplary illustrations of loyalties in accordance with the present invention; and
The detailed description set forth below in connection with the appended drawings is intended as a description of presently preferred embodiments of the invention and is not intended to represent the only forms in which the present invention may be constructed and or utilized.
For purposes of illustration, programs and other executable program components are illustrated herein as discrete blocks, although it is recognized that such programs and components may reside at various times in different storage components, and are executed by the data processor(s) of the computers. Further, each block within a flowchart may represent both method function(s), operation(s), or act(s) and one or more elements for performing the method function(s), operation(s), or act(s). Each block may comprise of one or more protocol(s) for execution of one or more function(s), operation(s), or act(s). In addition, depending upon the implementation, the corresponding one or more elements may be configured in hardware, software, firmware, or combinations thereof.
This disclosure defines the term “product” or “products” as good(s) and or service(s) (virtual or real) provided by an entity. Accordingly, a “product” for a manufactures may for example, be an article, whereas a “product” for an attorney or an accountant may be the service provided.
This disclosure defines a seller as one or more entity that promotes (e.g., using coupons), exchanges, or sells product(s). Non-limiting examples of a seller may include, for example, a vendor, retailer, merchant, wholesaler, dealer, resellers or value added resellers or VARs, professional entities such as accountants, attorneys, landlords with rental property, etc.
This disclosure defines a buyer as one or more entity that may be involved in a transaction with a seller. Non-limiting examples of a buyer may include, for example, a purchaser of a product or service, consumer, purchasing entity such as a corporation, a tenant, etc.
Further, in certain instances (depending on the context used) the term “user” or “end user” may refer to buyer, seller, or both. In addition, a seller may become a buyer or vice versa. For example, a merchant is a seller, but a merchant may buy from their respective vendor and hence, the merchant becomes a buyer. As another example, a buyer may sell a product, which makes the buyer a merchant.
It should further be noted that a transactional environment may generally be defined as one where any expenditure of funds or money (direct or indirect) is exchanged between entities and may involve purchase for goods and or services.
A seller may have a physically existing real world “brick-and-mortar” location or presence, and or have an online or virtual presence (or remote presence). It should further be noted that there are instances where a seller may have a physical, online, and or remote presence. For example, a bookstore may have an online presence, have a physically existing presence in a physically existing geographic location such as in a city, and have a remote presence such as placement of an ad in TV commercials, magazine or others' website or on a billboard ad in another state or country.
Throughout the disclosure terms such as bank, merchant bank, buyer bank, third party processors, credit-issuing entities, and so on generally refer to any entity (generally a financial institution) that may handle various types of transactions (virtual, real, or electronic funds). In general, any reference to a financial intuition should be interpreted as any entity that issues or authorizes a payment account (virtual, real, or electronic, and issuing or acquiring). Therefore, the phrase “credit issuing bank” or “credit issuing entity” should not be limited to those institutions that issue lines of credit, but may include any entity that issues any form of payment account. It is well known that a financial entity may be a merchant bank to a seller at the same time that the same financial entity is also a buyer bank to a buyer and further, the same financial entity may or may not also function as a third party processor for the seller. Of course, the financial entities may also be completely separate entities or, alternatively, may be a division or a subsidiary of a larger financial entity. Accordingly, it is only for clarity and better understanding of the invention that in some instances the disclosure may distinguish a financial entity in drawings and description as non-limiting, exemplary “acquiring merchant bank” or “credit issuing bank” and so on even though these terms may or may not refer to the same entity throughout.
It should further be noted that communication protocols must be established between the consumer-centric contactless wireless transaction processing system (WTPS) of the present invention and other entities to enable WTPS systems (servers, computers, etc.) and systems of other entities to communicate. Establishment of communication protocols between entities (any entity) are well known and routinely executed to enable secure, appropriate authorized access to servers and computers of the entities involved for various transactions, commensurate with previously established agreements between the entities. The communications protocols may be implemented in variety of well known manners, non-limiting example of which may include exchange or use of various Application Programming Interface (API) modules and or Software Development and or Software Development Kits (SDK) approved by entities involved.
For the purposes of this disclosure, the interchangeable terms such as loyalty or loyalties, loyalty program, loyalty system, and so on are defined as a system used by entities to encourage and entice transactions. Non-limiting examples of loyalty programs may include rewards (e.g., membership clubs, buyer discount programs, etc.) and or promotions (e.g., coupons, etc.).
The present invention provides a wireless transaction processing system (WTPS), comprising a unified commerce architecture for multi-platform transactions and communications between disparate and distinct entities. The unified commerce architecture includes one or more multi-configurable devices, enabling multi-platform transactions and communications between those disparate and distinct entities.
The present invention provides a consumer-centric contactless wireless transaction processing system (WTPS) using wireless mobile Internet devices. The consumer-centric contactless transaction processing system of the present invention using wireless mobile Internet devices obviates the mandatory requirement for the entities such as retailers to obtain additional, dedicated specialty wireless hardware or equipment to perform or execute wireless transaction or payment processing. Further, even if such transactions are done wirelessly using specialty equipment, no personal or private confidential information is exchanged when using the wireless transaction processing system of the present invention during the transaction process. Additionally, the consumer-centric contactless wireless transaction processing system of the present invention exchanges information using encryption and other well-known methodologies for security. Furthermore, the wireless transaction processing system of the present invention enables personal, direct transactions between individuals. Finally, contactless transaction processing system using wireless mobile Internet devices of the present invention integrates most types of transactions, including, but not limited to, cashless transactions, remote transactions, payments, purchasing, loyalty based transactions, recurring payments, virtual funds, or direct fund transfer (real or virtual, including electronics) between entities within a single system accessed by a mobile device.
As further illustrated, the WTPS 100 of the present invention includes one or more buyer 106 that is associated with the WTPS 100, and communicatively associated therewith via Internet or a network 104 using a mobile Internet device 108. In this exemplary instance, the buyer 106 is a registered member of the WTPS 100, with the buyer having at least one Internet enabled device 108 that can access the WTPS 100 via the Internet or network 104.
As a non-limiting example, with the WTPS 100 of the present invention, a buyer 106 that is a member of the WTPS 100 may walk into a convenient store 102 that is also a member of the WTPS 100 without carrying any cash or credit cards, purchase the desired products of the seller 102, and complete a transaction for purchase of the products using the mobile Internet enabled device 108. The seller 102 is not required to have any specialty equipment, and no confidential information is exchanged between the seller 102 and the member buyer 106.
As yet another non-limiting example, with the WTPS 100 of the present invention, a first individual member may directly transfer funds to a second individual member anywhere at any time for immediate use (depending on the banking institutional policies) by the second individual member using the mobile Internet device 108, and without accessing their respective bank accounts, or requirement of any specialty equipment. Further examples of other functionalities of WTPS 100 are detailed below.
The WTPS account creation process requires seller and buyer identification information (referenced as 123 and 125), non-limiting, non-exhaustive list of examples of which are exemplarily illustrated in
After creating an account, end-users are assigned with a WTPS member ID that fully identifies each registered user, equipment, etc, which may be represented by a variety of means, non-limiting example of which may include alpha-numeric characters, image, signal (wired or wireless), or others. That is, during account creation process, the buyer 106 and seller 102 WTPS account(s) is created with a unique WTPS ID that the WTPS may reference during any transaction process. The unique WTPS ID referenced by WTPS may reference the information that is exemplary illustrated in
It should further be noted that the account creation process described in relation to
As with individual account creation, the creation of an account through a third party entity (e.g., a VAR) would also generate unique WPTS ID for the individual end-user internally referencing the third party entity within the WTPS. In other words, WTPS provides the mechanism to always uniquely identify an account, whether directly registered or through a third party entity, and further, provides the mechanism to actually identify the third party entity itself. The identification of the third party entity itself is through the other data 127 and 129 indicated in
Accordingly, there are at least two methods for an end-user to create an account with WTPS, direct or indirect (e.g., via a VAR, for example). If an end-user account is created by a reseller (e.g., VAR) either through direct entry through WTPS website, then the reseller enters identifying information 123 listed in
In general, a transaction begins with generation of a transaction data 202 (detailed below) that includes a WTPS ID of the seller 102 being presented by the seller 102 to the perspective buyer 106. The transaction data 202 (which includes the seller WTPS ID) only has information that is non-confidential and not private, and may be represented by a variety of different ways that are detailed below, non-limiting examples of which may include a QR code, a Wireless Data Transmission, an NFC transmission, a Coded Image, or other method of data representation. The seller WTPS ID is created at the time of registration for the seller either by direct registration or by reseller creation. The WTPS ID indicates the database entry and file in the WTPS system. By logging into the merchant portal through the associated WTPS website, the seller is able to access various account tools (shown in
It should be noted that the CCATP may be alternately downloaded and provided by the third party processor for the seller. It should be further noted, that the CCATP facilitates the generation of the transaction data image (e.g., a QR code) at the terminal level. At no time during the transaction process is the terminal required to connect with an external server in order to begin the transaction process. The CCATP program for generating a terminal level transaction data image is similar to well known QR generators, which are readily available standalone open-source software, with the addition of routine Application Programming Interface to enable installation within the CCATP terminal. Nonetheless, after downloading the CCATP, the seller follows a series of installation steps including the entry of WTPS seller ID into the terminal application. The CCATP, at the time of transaction, once the buyer or seller has selected to use WTPS as a payment method will generate a data image (e.g., a QR code) representative of, but not limited to, the saved WTPS merchant ID, dollar amount, and merchant transactional reference ID. This data image (i.e., the transaction data 202) is what is received by and processed by the buyer at the start of the WTPS transaction process.
After logging into the WTPS, end-users (buyers, sellers, reseller, etc.) access their respective WTPS user account web portal.
As with most conventional online banking account schemes, a user (in this example, a buyer 106) may access their online account after login through any Internet enabled device. A WTPS user account (e.g., buyer, seller, etc.) includes typical information about user account details, such as transaction histories, account contact information and settings, account options, and other typical, well-known tools such as a help center, other services, and so on, the creation and uses of which are very well-known and similar to most online banking websites, as illustrated in
As illustrated in
Non-limiting examples of tool modules that are specialized for particular class of accounts may include delete or add payment account toot module, which is available to buyer accounts. The delete or add payment account toot module for the buyer account enables the buyer to add or delete a payment account. As another example of specialized tool module, access remote transaction module is a specialized tool module that is reserved for seller accounts (remote transaction module is detailed below). As a further example of a specialized tool module, edit, delete, or add resold user account module is a specialized tool module that is only available for reseller accounts, which enables the reseller accounts to modify user accounts. The reseller accounts further include the sales system for add-on WTPS services specialized tool module, which is used by reseller accounts for selling to end users additional services and account add-ons that WTPS offers.
As indicated above, there are tool modules within WTPS that may be universal to all classified account types, but depending on the type of the account classification, each has access to various aspect of that module. For example, the access Loyalty module is available to both buyer and seller accounts; however, where a seller account will access the Loyalty module to create (or modify) Loyalties (detailed below), the buyer account will access the loyalty module to merely redeems them. As another example, the Feedback/Complaints/Reviews module may be considered universal, but each account type will have different types of functions for reviews. For example an end-user (e.g., buyer) can search through list of merchants based on merchant rating and review level, but another end-user (e.g., merchant) cannot search consumers (e.g., buyers) based on review and rating levels. As yet another example of universal tool modules with specialized access privileges, the Disable or Cancel service tool module allows the buyer to cancel WTPS service or disable the WTPS app within their mobile internet device 108. On the other hand, although not illustrated, seller and reseller accounts may cancel their WTPS service. As a further example, the Review Transactions and Generate Reports module enables a buyer account to review and generate buyer transactions (such as purchases), a seller account to review and generate seller transactions (purchases, and sales), and the reseller account to review and generate reseller transaction (such as reviewing transaction history for resold accounts). As yet another example, the Fraud Management module may enable buyer accounts to submit claims of suspected fraud or chargebacks, etc., seller account to respond to claims of fraud or chargebacks, and reseller accounts to moderate the claims of fraud or chargebacks of resold accounts. As a final example, the Accounting module may enable seller accounts to manage accounts payable, while reseller accounts would manage accounts receivable and payable.
As illustrated in
The WTPS 100 provides an independent “hub” for transactions and communications between many diverse entities. Accordingly, the WTPS 100 illustrated in
In the exemplary embodiment illustrated in
The overall transaction system illustrated in
As stated above, after a buyer 106 becomes a registered member of the WTPS 100 (e.g., via the WTPS website), a mobile app (or a mobile application) of the wireless transaction processing system is downloaded to the mobile Internet device 108 (such as a mobile phone) of the buyer 106, where the buyer 106 and the mobile Internet device 108 are associated and enabled to communicate via 115 with the WTPS 100. It should be noted that the WTPS app may readily be downloaded into a mobile internet device 108 without prior registration, after which, the end-user may easily register with the WTPS via the mobile app. The registration with the WTPS 100 enables the buyer 106 to associate any issued credit accounts from any one or more credit issuing entities 103 via communication 123 with the WTPS account of the buyer 106. The wireless transaction processing system application for the mobile device (hereinafter referred to as “WTPS app”) may be launched via the mobile Internet device 108 to enable a user (e.g., buyer 106) access to the WTPS user account. As illustrated, the buyer 106 may select the desired items from the exemplary convenience store or seller 102 for purchase (e.g., a bag of groceries), with the registered seller 102 generating a transaction data 202 (which includes the seller 102 WTPS ID, but no private or confidential information) for the buyer 106 for the selected goods and or services.
When a registered buyer 106 makes a purchase from the registered seller 102 using the mobile Internet device 108, that information is communicated via 115 to the WTPS 100, which, in turn, may optionally communicate the information via communication 121 to the optional third party processor 227. Regardless, either WTPS 100 or the third party processor 227 forward a request (indicated by communication 111/113) to the credit/debit card network 105 regarding the purchase amount, and the credit/debit card network 105 determines the balance of credited amount available for use by the buyer 106, and reports back to the WTPS 100 (or optionally, the third party processor 227) via communication 111/113. Thereafter, based upon the availability of credit, the transaction is either approved or denied by WTPS 100 (or optionally, the third party processor 227), with results reported (via communications 115 and 117) from the WTPS 100 to the buyer 106 and or seller 102 or to seller 102 via communication 119 by the third party processor 227. It should be noted that in some instances WTPS 100 may handle all reporting. That is, instead of the third party processor 227 reporting the authorization results directly to the seller 102 via communication 119 that the buyer 106 is approved (or denied credit), the third party processor 227 may instead handle all work and simply report the authorization results to the WTPS 100 via communication 121 for distribution by WTPS 100 via communications 115 and 117 to respective buyer 106 and seller 102. After the transaction is complete, the credit account of the buyer 106 is debited by the purchase amount and the account of the seller 102 is credited by the same amount, and the respective accounts of the buyer 106 and seller 102 are updated in all entities involved in the transaction.
As further illustrated in
Assuming an access code (or pin) is correctly entered, the access protocol 208, through the operational functional act 210 provides the WTPS platform 140 with the consumer or buyer 106 identification information (buyer WTPS ID or buyer-ID) and buyer physical location via a typical GPS system. The WTPS platform 140 received that information via the operational functional act 212, and upon verification via the operational functional act 214 approves access to the WTPS app 190 to launch a main screen or main page at the operational functional act 216 on the I/O module 160 of the mobile Internet device 108.
In general, the WTPS system includes a GPS Positioning Log. At the time of the transaction, the WTPS saves a record of the GPS data for users, cross-referencing time with the GPS location and a generated WTPS transaction reference ID number (detailed below). This accumulated data is used as a security measure (detailed below) to ensure that the users are making the actual purchase in case of later transaction issues. Additionally, the GPS record for the transaction may be used to determine applicable merchant or transaction fees.
As illustrated in
As detailed in the exemplary flowchart of
If the WTPS 100 determines that the access code is not an emergency access code, then WTPS 100 determines if the access code is an authorized access code at the operational functional act 440. If it is determined that the access code is an authorization access code, then the WTPS 100 determines if WTPS user account is active (at the operational functional act 226), for example, has the account be canceled, mobile Internet device reported as stolen or lost, and so on. The determinations in the operational functional acts 224 and 226 may be accomplished by numerous methods, a non-limiting example of which may including the use of relational data base systems that easily compare the stored registration information of users (e.g., sellers and buyers) and their device information with incoming information via the operational functional act 210 (
As further illustrate in
Referring back to
The present invention provides capabilities that enable a user to access the abovementioned functionalities in a variety of manner. As illustrated in
Alternatively, the user may first select any of the above mentioned specific actions or functions, for example, from the main page or start screen 216, the user may select start of a transaction (operational function act 232 of
As indicated above, the settings operational functional act 230 may be accessed via the main screen 216 (
As further indicated above, the preview history operational functional act 236 may be accessed via the main screen 216 (
As further indicated above, the start transaction operational functional act 232 may be accessed via the main screen 216 (
As illustrated in
It should be noted that the seller 102 may transmit the transaction data 202 by any means, non-limiting, non-exhaustive listing of examples of which may include data packets and bar codes (e.g., QR codes), file download, screen shot, or to the seller mobile Internet device using traditional mobile protocols such as Short Message Service (SMS), Multimedia Message Service (MMS), or e-mail, etc. Therefore, the examples provided in the flowcharts of
Referring to
Non-limiting, non-exhaustive listing of examples of machine readable coded-data image of data 202 associated with seller 102 and its goods and or services may include well-known barcodes, Quick Response (or QR) codes, or other types of codes, including the actual numerical value of the codes, an image of which may be printed on a receipt or displayed on a website page and captured by a camera. A QR code is a very well known matrix (or two dimensional) barcode, which is a machine-readable representation of data. Both QR code generator applications and QR code reader applications for wireless devices are also well-known and can easily be downloaded from a vast variety of web sources (mostly free of charge), similar to the manner of downloading a free Portable Document File (PDF) generator and reader. In fact, most mobile Internet devices 108 such as mobile phones may have a QR code reader application pre-installed.
Referring back to
As indicated above,
Non-limiting, non-exhaustive listing of examples of information that may be included in the transaction data 202 associated with the seller 102 are numerous and may include, among others such as the seller 102 WTPS ID, the transaction types (e.g., online, physical, remote or loyalty, (either virtual or real) transaction), seller information such as business name, GPS location of business, physical address of the business, merchant service provider information (if needed), e-commerce information, website address (e.g., domain name for online merchant for online transactions), account information (in relation to the account created when the seller 102 registered to become a member of the WTPS 100), and so on. Other non-limiting, non-exhaustive listing of examples of information that may be included in the data 202 associated with the seller 102 products may include information about an item being sold, including, but not limited to, for example, item (or service) serial number, price, and or any information that is printed on a typical or detailed receipt (e.g., invoice) of a transaction when the seller 102 inputs the item information into a typical cash register (or point-of-sale system) and prints a receipt or when a purchase is made online and a confirmation page is displayed on a webpage.
Regardless of how the transaction data 202 is transmitted and received, the received transaction data 202 is processed, enabling the transaction data 202 to be displayed by the I/O module 170 of the mobile Internet device 108 in accordance with the operational functional act 298 (
As further illustrated in
Referring back to
As stated above, upon confirmation of data by the operational functional act 207, and generation of the WTPS transaction reference ID at the operational functional act 430, the confirmed data, WTPS transaction reference ID, and buyer information (e.g., buyer GPS) is transmitted via the operational functional act 209, and received by the WTPS platform 140 by the operational functional act 211. As indicated above, the WTPS system includes a GPS Positioning Log. At this point of the transaction, the WTPS saves a record of the GPS data for the transaction, cross-referencing time with the GPS location and a generated WTPS transaction reference ID number (generated by both the mobile Internet device and WTPS platform). This accumulated data is used as a security measure to ensure that the users are making the actual purchase in case of later transaction issues. Additionally, the GPS record for the transaction can be used to determine applicable merchant fees. It should be noted that the physical location of a seller 102 (such as a merchant) may not be required to be transmitted since the seller location may form a part of the seller 102 WTPS ID, when the seller 102 registers with the WTPS, providing the location of the business.
The received data, reference ID, and buyer information by the WTPS platform 140 (including buyer 106 GPS) via the operational functional act 211 is then processed by the operational functional acts 213 and 215. The process at 213 may include simply verifying the transaction data 202 transmitted by the seller 102. In this embodiment, it may also include verifying that the seller 102 is a legitimate member of the WTPS system 100 by checking the instant received information at operational functional act 211 against stored registration information of the seller 102, similar to the manner illustrated in
The operational functional act 215 determines the seller location and mobile location of the buyer. Upon the determinations at the operational functional acts 213 and 215, at the operational functional act 432, the WTPS determines if the WTPS transaction reference ID is valid. The validity of the WTPS transaction reference ID may be determined by a variety of methods, which may depend upon the algorithm used to generate the reference IDs. As a non-limiting example, if the WTPS transaction reference ID is generated as a sequential number, and the WTPS platform determines that the transaction reference ID is out of sequence, then the entire transaction is simply denied, and the WTPS user account holder is notified. This scenario is likely if the original mobile Internet device has been cloned, hijacked, counter-fitted or intercepted. For example, the WTPS of the original mobile device may have generated WTPS transaction reference ID with a sequence number 0005 for a particular transaction, with the next subsequent number to be 0006. As stated above, the WTPS transaction reference ID is a unique identifier associated with and generated by the WTPS app 190 of the particular mobile Internet device. Therefore, the cloned mobile Internet device will commence its WTPS transaction reference ID at a number (or other identifier) when the original phone was cloned, which may have been at sequence number 0003. In such an exemplary instance, the sequence of the WTPS transaction reference ID for the original mobile Internet device is at 0006, but the WTPS app of the cloned mobile Internet device will generate the WTPS transaction reference ID starting at the sequence 0004 (which has already been used once by the original mobile Internet device). This is similar to two individuals writing checks from the same account, but the check number sequences do not match. The user of the original checks is on check number 0110, with check numbers 0100 to 0109 already cleared, and the other user using copied checks that start with copied check number 0107 writes a check with check number 0107 or 0108.
It should be noted that the use of GPS or similar location identifier systems to access and use the WTPS 100 of the present invention is intended to register and log that the consumer was at a particular location for purchase of goods and services from a seller. As an optional process and as illustrated in
As further indicated in the operational functional act 217, if WTPS system 100 determines that the buyer 106 is in the same physical location as the seller 102 or that the transaction is an online transaction (operational functional act 702), then at the operational functional act 704 the WTPS system 100 commences validation protocol 704. That is, all verified information is processed and validated by the operational functional act 704. Thereafter, at the operational functional act 225, the WTPS 100 commences authorization of the transaction. In other words, as indicated by the flowchart of
It should be noted that the authorization protocol may be accomplished by a third party processor 227, such as a bank or any other convention entity that processes credit, debit, or bank transactions. That is, information (such as buyer ID, buyer location information, and transaction data 202) that is to be verified may be verified by the operational functional act 704 of the WTPS 100 as illustrated, and a third party 227 executes authorization of transaction (or credit approval/denial) once verification by WTPS 100 has been completed. The authorization of the transaction by the third party 227 is then received by WTPS 100 through the operational fictional act 229, and transmitted via the operational functional act 221.
Non-limiting examples of verification and then authorization may include verifying availability of funds in the selected account of the buyer for the selected transactions, limits or restrictions placed on the buyer account, or any other information that would cause termination or approval of the purchase, similar to the conventional manner that a credit card account of a buyer is verified and then authorized (e.g., approved or denied) for a particular transaction.
As an added security measure, the present invention further provides an optional travel itinerary module (
The GUI for a travel itinerary is part of the travel itinerary module of the WTPS app, and may be accessed in a variety of manner, such as the selection of operational functional act 238 (
As illustrated, the member payer accesses the wireless transaction processing system by the mobile Internet device 108 as described above in relation to
As further illustrated, the WTPS 140 received the transmitted information at the operational functional act 308, with WTPS 100 verifying member payee information at the operational functional act 310, including checking the WTPS transaction reference ID. If WTPS transaction reference ID is not valid, the entire procedure is denied and the process terminated at the operational functional act 219, otherwise, the WTPS 100 further executes validation and authorization protocols for the transaction (assuming the WTPS transaction reference ID is valid) at the operational functional act 312, and transmits results via the operational functional act 314 to payer and the payee. As further illustrated, the payer receives the validation and authorization at the operational functional act 316, where WTPS app 190 displays the results to the payer via the operational functional act 318.
As illustrated in
Referring back to
Referring to
The received information from the payer is checked by the WTPS server against the WTPS customer database to verify available funds in payer WTPS virtual account. If or once the funds are available, then WTPS platform transmits a notice to the payee WTPS mobile app on the mobile Internet device to inform of and accept the proposed virtual fund transfer. It should be noted that the payee does not initiate the disclosed transaction. Once the payee accepts the transfer, the payee transmits an acceptance to the WTPS server to continue the process. Since it is a virtual currency that is being transferred (and not real dollars), the payee must be a participant and actual accept the virtual currency. If the payee denies the transfer, then a notice is transmitted to WTPS server to notify the payer mobile Internet device and terminate the transfer.
If the payee accepts the transfer, the WTPS server transmits the payer WTPS bank account to commence transfer of virtual funds to payee WTPS bank account. The transfer may or may not include an Automated Clearing House (ACH) service registered to an account with WTPS for fund transfer purposes between banking institutions. If the transfer is completed within the same bank then the process is internal to the bank's system and does not require an ACH transfer.
Once the transfer has been completed, the payee WTPS bank account transmits a confirmation to the WTPS server that the payer WTPS bank account has been credited and the payee WTPS bank account has been debited. The WTPS server updates the WTPS database for the newly adjusted balances of the payee and the payer, and notices are transmitted to the payer and the payee mobile Internet devices that the virtual money has been transferred and that the transferred funds are available to the payee.
It should be noted that if the payer does not have sufficient funds available in their WTPS virtual account, then they must first choose a credit account from the WTPS registered accounts and add virtual money to their virtual account from that credit or debit card account or from a reload purchase from a third party outside funding company (similar to the processing illustrated and described in relation to
As has been described above, the WTPS 100 is a separate entity that functions as a “hub” between consumers (buyers 106 and sellers 102), credit issuing entities 103, card networks 105, and the optional third party processors 227 for processing cashless transactions. As described below, the present invention provides another embodiment wherein the WTPS 100 is integrated within an existing credit issuing entity and or a third party processor, rather than functioning as a standalone platform.
As illustrated in
As illustrated in
When a buyer 106 makes a purchase from the seller 102 using the mobile Internet device 108, transaction data 202, including buyer 106 information (e.g., GPS location, etc. as shown and described above in relations to
It should be noted that with this embodiment, a seller 102 need not bank with the credit issuing entity and therefore, need not have any account associated (or registered) with the WTPS 400. Additionally, the integration of WTPS 400 with the issuing entity 103 would enable the issuing entity 103 to instantaneously be cognizant of the available balance and credit amount for each user 106 without using the credit/debit card network 105 since all transactions for buyer 106 are through the buyer account associated with WTPS 400 of the credit issuing entity 103. In other words, the credit issuing entity 103 no longer needs to communicate with the credit/debit card network 105 to determine the availability of funds and total amount credited to the consumer since the account of the buyer with the credit issuing entity 103. This eliminates the dependents or the need for the credit/debit card network 105, which speeds up the transactions, and lowers overall transaction costs.
With the WTPS 400 the seller 102 need not be a registered member of the WTPS 400 associated with the credit issuing entity 103, but must still be a member of an instance of WTPS in order to initiate the WTPS transaction therefore, only the buyer 106 is required to have an account with the specific credit issuing entity 103 that includes an integrated WTPS 400. The account setup and the registration requirements and methods and online access to features of WTPS 400 associated with the buyer account may be governed by the credit issuing entity 103 within which the WTPS 400 is integrated.
As best illustrated in
As illustrated in
As illustrated in
The description and the illustration in
A benefit of the entire WTPS in accordance with the present invention is that WTPS provides a mechanism to track various consumer activities, which may later be used by various entities to provide targeted advertisement to consumers based on consumer activity. As has been described above in relation to
As with WTPS 100 and WTPS 400, the WTPS 500 includes a plurality of servers that provide a hub for communications and cashless transactions between diverse entities. As illustrated in
When a buyer 106 makes a purchase from the seller 102 using the mobile Internet device 108, the received transaction data 202, including buyer 106 information (e.g., GPS location, etc. as shown and described above in relations to
The financial entity 514 encrypts and transmits authorization via 508 with either approving or denying the transaction back to the WTPS 500 for forwarding (511) to the acquiring merchant bank 516. The acquiring merchant bank 516 is the holder of the account of the merchant (the seller account), which enables the registered seller 102 to accept credit card payments for transactions. The acquiring merchant bank 516 may take the role of a third party processor 227 in the event that the seller 102 wishes to process a non-WTPS transaction. The authorization from the financial entity 514 may include information that notifies the acquiring merchant bank 516 (via 508) that a buyer account is to be debited and the seller account (with the acquiring merchant bank 516) is to be credited and that the financial entity 514 is authorizing by approving or denying such transaction. Accordingly, in this instance where WTPS 500 is involved, the acquiring merchant bank 516 does not function as a third party processor 227 since the financial entity 514 of the buyer 106 authorizes a transaction. Thereafter, the acquiring merchant bank 516 transmits (via 510) the authorization to seller system, notifying the seller system of the authorization denial or approval of transaction. Upon completion of the transaction, the seller account is credited and the buyer account is debited in accordance with the transaction data. Finally, the WTPS 500 transmits (via 512) the authorization to for denial or approval of the transaction to the registered mobile Internet device 108 of the buyer 106.
The primary transaction architecture with WTPS 530 of
WTPS 530 of
In
The transaction architecture with WTPS 540 of
In a closed loop architecture environment (as illustrated in
The transaction architecture with WTPS 550 of
In this embodiment of direct approval system transactions occur between four distinct entities. This four point direct approval system architecture is similar to a closed loop environment however the WTPS 550 takes the place of a merchant POS server, and a merchant proprietary credit account may not exist. WTPS 550 interacts with multiple third party issuing banks to provide direct approval for the bank's own proprietary credit accounts. These proprietary credit accounts are similar in essence to current conventional credit card accounts however they do not rely upon the outside credit card networks or third-party processors to process and generate approvals. Approvals are achieved by direct data connection to the issuing banks for those credit accounts and the WTPS 550 notifies the merchant directly of the approval or denial using the direct and previously established connection made by the merchant's POS or credit card authorization terminal at the start of the transaction process.
The transaction architecture with WTPS 560 of
In this embodiment of direct approval system transactions occur between five distinct entities. This five point direct approval system architecture is similar as in
Registered sellers that are a member (or subscriber) of RT may upload and save item data related to their products (or items) into an RT database, with the RT providing sellers with unique, individual identification associated with each item (i.e., product or service) and or the seller. A listed “item” is an “entry” made as a data that may be an entry for a product or a service and hence, the term “item” should not be construed as an article or product. The identification (RT item ID and or RT seller ID, detailed below) may be in a machine-readable representation (e.g., a QR code) that may be transmitted or displayed by the seller on a variety of media for retrieval by a buyer (for example, buyer using any of the WTPS apps mentioned above on a mobile Internet device).
As a very specific non-limiting example for better understanding of the RT, a seller with different types of artwork for example, may register with RT and upload item data related to each artwork. That is, for each individual artwork, the seller uploads all relevant information for that particular artwork onto the RT servers. Non-limiting, non-exhaustive listing of item data for each individual artwork may include, for example, price, the artist information related to that artwork (e.g., historical data related to the artist), availability (in terms of quantity, date, etc.), seller information such as shipping, discounts, recommendations, etc. Once all data is uploaded for each item (e.g., product or service), upon saving the uploaded information, the seller receives a unique item ID (RT item ID) associated with each individually uploaded and saved data.
It should be noted that once one or more items are entered, the seller is provided with an option to add recommended items. The recommended items (products) may simply be just an entry that is selected to be associated with another entry. For example, a seller may have three artworks, with the third entry associated with the second entry as a further recommendation. The recommendation option is a part of item data that is entered and saved. In other words, upon entry of a third item, the data for that item may point to the second item and when buyer views the second item, they will see the third item as a recommendation. It should be noted that a seller may choose to optionally recommend products from another seller account.
The item ID representation may be in a form of a QR code or any other code such as a bar code or image representation (of item ID) that may be easily displayed within any media such as video, a news paper classified/wanted ads sections or an art magazine. Any individual with a device that is capable of reading the RT item ID (e.g., within a QR code) may simply scan the code to retrieve an item data from the RT database that includes all data related to the item (which in the case of the above example, would be a particular artwork). The displayed RT item data on the user device also provides the capability for the purchase of the product associated with the RT item data. With RT, there is no requirement for a seller to have a storefront or website to sell listed items and more importantly, all that a seller is required to do is to advertise the item ID (e.g., within a QR code) on any media to advertise the sale of a listed item (i.e., a product or a service). The item ID may be placed on any type of media—from simple flyers to pass onto the neighbors to exclusive and pricey art magazines or any website. Further, since the item ID (e.g., illustrated within a QR code) does not take too much space, the cost of the print ad to the seller of the listed item is substantially reduced. This is especially true if the seller places the QR code within a flyer of another business that sends out flyers.
The RT may also be used to catalog data item (i.e., products), which facilitates the searching for that item by WTPS consumers. The RT catalog feature (if enabled as a result of subscription by a seller) allows sellers to advertise a single RT seller ID (e.g., a RT seller QR code) that would provide users access to all listed items of that seller with RT database. Therefore, instead of advertising multiple individual RT item IDs (e.g., multiple RT item QR codes) for each item entry (product or service), the seller merely advertises a single RT seller ID, allowing access to all RT item entries related to the seller. It should be noted that a seller may have a single entry in the RT database and still enable the catalog feature (by subscription or payment). The benefit of enabling the catalog feature for sellers (even if they only have a single entry (product) is that the catalog feature provides the buyers with enhanced searching capabilities to find desired products of a seller.
An example of a catalog feature (with multiple listed items) is a restaurant menu, wherein each item on the menu will have its own individual item ID (as described above), but the entire menu for that restaurant may be classified as a catalog, providing the restaurant a RT seller QR code. Upon scanning the restaurant RT seller QR code, buyers will have access to the menu and individual menu items from which to select, with each individual menu item having its individual RT item ID. It should be noted that in RT catalog environment the individual QR codes for each RT item is not displayed (as a result of receiving the RT seller QR code). Individual item data is listed in summary format where the user has the option of viewing the individual complete details of each item, where multiple items selected and combined into a single transaction. With RT, the seller does not need or require a restaurant, a storefront, or website to sell a food and more importantly, all that an RT seller is required to do is to advertise the RT seller ID (e.g., within a QR code) on any media to advertise the sale of a plurality of items within the RT database. It should be noted that buyers (whether or not registered with RT/WTPS) are never taken outside the WTPS when the RT seller ID and or RT item ID are received by their mobile Internet device, but the RT item data or RT catalog data is retrieved from the RT database.
As illustrated in
As illustrated in
The RT item datasheet 602 (
As further indicated above in relation to
As stated above, in the remote transaction system or module as part of the WTPS, merchants (once logged into the merchant portal and having accessed the merchant tools area) are able to enter in products to be available within the RT/WTPS system for immediate and direct purchase. Each item has its own entry and identifying data code, which may be used by buyers to conduct immediate transactions without the seller needing an online or physical store or the buyer visiting the online or physical store.
As detailed in relation to
Therefore, after the merchant subscribes to the RT catalog feature of WTPS, the merchant may enter in one or multiple items into the merchant product/service database, one item at a time as described above or by uploading a spreadsheet data formatted to cooperate with the online merchant database. The individual item data provided includes but is not limited to product (or service) id, name of product, description of product, price, optional choices for product (size, color, etc), item category, shipping options, product image, recommended additional sale items associated with product. Each product has an RT item ID available for individual use, which may or may not be disabled, depending on the merchant's individual settings.
The merchant generates a RT seller ID to identify themselves and their product catalog within the WTPS Merchant Product/Services Database (if enabled). The merchant may either save the RPMQRC as an image file for later media use or print directly from the merchant tools section of the WTPS website.
When a consumer scans the RT seller ID using the WTPS Mobile Application, the application loads with the merchant's product catalog displaying summarized product data for each item originally entered. This data may include but is not limited to image, item category, product name, short description, price, etc. At this stage, the consumer makes their selection choice and is able to review more details about a selected item (via the RT item template 670) and, if desired, complete a transaction for either that chosen item or add multiple selections together for a larger transaction encompassing multiple product choices from the merchant product catalog. During the initial transaction process, as individual items are committed to the transaction, the application displays referenced recommended items that were originally entered into the product database for that product for each item as they are chosen.
When a consumer scans the RT merchant catalog ID without using the WTPS application, the mobile browser opens to a secure mobile WTPS web page with the merchant's catalog information displayed, informing the consumer that they must download and install the WTPS application in order to view the remote catalog for that merchant. An abbreviated initial registration is conducted through the mobile web page, requesting information including but not limited to full name, address, phone number, e-mail address, desired user name and password, security access code (pin code). Upon installation, and attempted purchase from the merchant catalog, the consumer will be prompted to enter in a credit card number for the transaction through a mobile web environment. Non-limiting examples of a mobile web environment may include, a mobile browser window, an inline “web view” portal within the WTPS application, and others.
Once the initial transaction is completed, if the consumer was not originally a member of WTPS, they are offered a tutorial link where they can receive an automated tour of WTPS highlighting the key features, settings, and benefits. If they elect not to view it, they are instructed they can look any time at the help menu to view later.
Regardless of whether the consumer is a member of RT/WTPS, any mobile app capable of reading the RT item ID may retrieve the individual RT datasheet and display on a mobile Internet device, enabling the consumer to view and select various options in relation to the product or service being viewed. That is, the consumer views details of the product or service associated with the received RT item ID.
As illustrated in
As further illustrated in
As stated above in relation to
As further illustrated in
As illustrated in
As illustrated in
It should be noted that it may be optionally available for a buyer using the WTPS application to cancel or return/refund an undelivered and incomplete transaction. To clarify, in the time period between when an RT transaction has been ordered and the final shipment has been received, it may be possible for a buyer to stop the order, pending seller approval, terms and conditions of the transaction. In this process, the buyer 106 will retrieve the translation detail from the account history section of WTPS app, upon viewing the details page for the particular transaction, the buyer 106 is presented with the option (if available), to select to cancel, refund, or return an order. This option will be presented within the GUI of the transaction details page. Once buyer 106 has elected to terminate (e.g., cancel, refund, etc.) transaction, the seller 102 is notified that the buyer wishes to terminate the transaction.
As further illustrated in
As illustrated, the loyalty system of the present invention further provides a My Loyalty section, which is a centralized location where the consumer may select to save loyalties (rewards and or promotions), add loyalties to a reserved loyalty cart for immediate use, save and retrieve loyalty rewards (e.g., retrieving a loyalty reward card of a store), and view a history of loyalties redeemed. The My Loyalty Cart enables users to search and retrieve various loyalty promotions and add them to their My Loyalty Cart ready for use during a checkout. For example, consumers may first search loyalty promotions and retrieve coupons for the products that they wish to purchase. As they review the retrieved coupons, they simply select to add them on the My Loyalty Cart (similar to an e-commerce “Shopping Cart Wish list”). Accordingly, My Loyalty Cart may have five or six “coupons” related to different products. At the point of sale (or at the checkout), the consumers simply retrieve the appropriate coupons from the My Loyalty Cart, and apply the specifically selected coupons from the cart against the products being purchased. Therefore, instead of searching and retrieving thousands of coupons, the consumer quickly access a selected number of coupons saved and stored to the My Loyalty Cart. To access My Loyalty Cart, the consumer simply selects the My Loyalty button, and then, selects My Loyalty Cart. It should be noted that during “checkout,” the consumer may further retrieve My Loyalty Rewards related to the specific merchant in addition to retrieving the selected promotions from the My Loyalty Cart to receive any discounts or promotions agreed by the merchant. For example, the My Loyalty Rewards may include a membership club card associated with a merchant that automatically provides discounts for its members. It should be noted that optionally, the My Loyalty Rewards information may automatically be loaded onto the mobile Internet device as soon as the consumer is within a store that includes loyalty rewards saved within the mobile Internet device of a consumer. Alternatively, the WTPS system may check to determine if a consumer is a loyalty reward member of that merchant and automatically offer the rewards membership to the consumer if they are near the merchant.
As further illustrated, the present invention also provides the option to consumers to receive loyalty information (rewards/promotions) via their optionally available WTPS internal email account. As with any email system, the WTPS email account of users enables users to receive emails and messages. Non-limiting examples of which may include WTPS information and updates, WTPS account information, merchant announcements or any other messages related to loyalties, enabling them to view individual offers. Additionally, consumers may elect to forward outside email/message correspondence from third party shopping environments to the WTPS email account in order to have all shopping correspondence in one location.
Loyalty system of the present invention further includes a program settings for consumers to set the types of promotions/rewards they wish to receive (via GPS push, email, or others). Non-limiting examples of settings may include category and subcategory of desired offers of products, desired business or locations, desired format and type of correspondence, activating or deactivating push notifications, enabling/disabling alerts, etc.
As illustrated, the merchant selects Manage Loyalty from within the merchant tool section, where they may select to edit loyalty, add new loyalty, or view loyalty related information (e.g., reports, statics, etc.).
The addition of a new loyalty (promotion or rewards) includes Loyalty item datasheet 702 (
It should be reiterated that within WTPS platform, all modules (standalone or otherwise) are integrated and may work together to share options and data offering new features and benefits not available as separate modules. The combination of the remote transaction module (
As illustrated in
Consumers who have an installed and registered WTPS mobile application receive loyalty promotions and rewards pushed to their mobile device based on their GPS coordinates and saved preferences. Merchants will have previously entered in loyalty promotions and rewards through the merchant tools section of the merchant portal and indicated during their creation where and when these promotions or rewards will be distributed. As part of the loyalty creation process, merchants were given the option of associating remote transaction products with the newly created loyalties. If the merchant elected to associate remote transaction products with a loyalty then whenever that loyalty is displayed, a link allowing display and instant purchase of those remote transaction products will be displayed on the loyalty as it is pushed.
As further illustrated in
As indicated in operational functional acts 838, in the event that there is not an existing loyalty that the merchant wishes to use, the merchant may elect to create a new loyalty. At that point, the currently opened product is saved to the product database (generating an RT item ID) and the merchant is optionally directed to the create new loyalty screen with the previously viewed product (its RT item ID) automatically associated with that loyalty. As further indicated in the operational functional act 840, if the merchant had chosen to associate an existing loyalty with the previously viewed product then after making their selections, the merchant would have simply pressed save to commit the product entry to the product database.
It should be noted that due to the combination of RT and Loyalty as a combined or integrated feature of WTPS, consumers may elect through the loyalty function of the WTPS to search for only loyalties that are offered by merchants that have an associated RT item or catalog. Additionally, consumers can also optionally elect to search for a list of merchants that have existing loyalties associated with an RT item or catalog.
Although the invention has been described in considerable detail in language specific to structural features and or method acts, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary preferred forms of implementing the claimed invention. Stated otherwise, it is to be understood that the phraseology and terminology employed herein, as well as the abstract, are for the purpose of description and should not be regarded as limiting. Therefore, while exemplary illustrative embodiments of the invention have been described, numerous variations and alternative embodiments will occur to those skilled in the art. For example, WTPS is capable of being installed directly onto a phone's internal SIM or micro-SD card memory and made available through the phone's internal menu. It is through this method that WTPS may be used with non-smartphone (e.g., feature phones), and other similar devices. Further, the WTPS can be restructured using a menu driven interface and using manual entry of related ID codes (e.g., within QR codes) for the system usage. The WTPS can be installed on non-smart mobile devices (e.g., feature phones) using the method. Further any data (e.g., RT item ID, seller ID, consumer ID, etc.) may be generally directly printed adjacent the representation of that data. For example, if the data is a seller ID, then the actual seller ID value may be printed adjacent its representation (non-limiting example of which may be a QR code). The actual or direct data (e.g., seller ID) is provided in case the user cannot or has no means of receiving a representation (e.g., a QR code) of the data. For example, a user may not have a QR code reader installed on their mobile Internet device at which point, the user may simply enter in the RT item ID manually. Such variations and alternate embodiments are contemplated, and can be made without departing from the spirit and scope of the invention.
It should further be noted that throughout the entire disclosure, the labels such as left, right, front, back, top, bottom, forward, reverse, clockwise, counter clockwise, up, down, or other similar terms such as upper, lower, aft, fore, vertical, horizontal, oblique, proximal, distal, parallel, perpendicular, transverse, longitudinal, etc. have been used for convenience purposes only and are not intended to imply any particular fixed direction or orientation. Instead, they are used to reflect relative locations and/or directions/orientations between various portions of an object.
In addition, reference to “first,” “second,” “third,” and etc. members throughout the disclosure (and in particular, claims) is not used to show a serial or numerical limitation but instead is used to distinguish or identify the various members of the group.
In addition, any element in a claim that does not explicitly state “means for” performing a specified function, or “step for” performing a specific function, is not to be interpreted as a “means” or “step” clause as specified in 35 U.S.C. Section 112, Paragraph 6. In particular, the use of “step of,” “act of,” “operation of,” or “operational act of” in the claims herein is not intended to invoke the provisions of 35 U.S.C. 112, Paragraph 6.
Claims
1. A wireless transaction processing system (WTPS), comprising:
- a merchant network enabled computing machine with a merchant established account associated with WTPS computing platform;
- the merchant network enabled computing machine accessing one or more computing machines associated with WTPS computing platform to access merchant tool modules of the WTPS to enter data related to products for product promotions and product sales, including storage of the data within a product data storage module of the WTPS computing platform;
- with the data accessible by consumer network enabled computing machines with a consumer established account associated with WTPS computing platform in both passive and active modes of operations;
- with passive mode operations the consumer network enabled computing machines passively receives notifications as a result of the WTPS computing platform pushing the data representing products onto the consumer account associated with WTPS computing platform; and
- with active mode operations the consumer network enabled computing machines actively retrieving data representing products from the WTPS computing platform;
- with the consumer account including configurable preferences for receiving the pushed data related to specific types of products commensurate with the configurations set within the consumer account;
- with the consumer network enabled computing machine receiving preferred pushed data of products available for immediate, direct purchase without redirection to another webpage for the purchase and with the direct transaction completed without providing consumer account information considered confidential to the merchant network enabled computing machine.
2. The wireless transaction processing system (WTPS) as set forth in claim 1, wherein:
- the consumer network enabled computing machine stores the pushed data within a consumer storage module within the consumer account associated with the WTPS computing platform for retrieval; and
- where consumer network enabled computing machine can share the pushed data with other consumer network enabled computing machines.
3. The wireless transaction processing system (WTPS) as set forth in claim 1, wherein:
- the consumer network enabled computing machine can share the pushed data onto third party computing systems for display.
4. The wireless transaction processing system (WTPS) as set forth in claim 3, wherein:
- the display of the pushed data is comprised of one of a product image and related product information, and text.
5. The wireless transaction processing system (WTPS) as set forth in claim 4, wherein:
- accessing full product details and purchasing of product is enabled when consumer network enabled computing machine is associated with WTPS computing platform.
6. A mobile transaction module, comprising:
- a merchant network enabled computing machine with a merchant established account associated with wireless transaction processing system (WTPS) computing platform;
- the merchant network enabled computing machine accessing one or more computing machines associated with WTPS computing platform to access merchant tool modules of the WTPS to enter data related to products for product promotions and product sales, including storage of the entered data within a product data storage module of the WTPS computing platform;
- WTPS computing platform generating a unique product identifier associated with the entered data;
- the merchant network enabled computing machine retrieving the unique product identifier generated from WTPS computing platform, and with the merchant network enabled computing machine displaying the unique product identifier within one or more medium;
- consumer network enabled computing machine with a consumer established account associated with WTPS computing platform retrieving the entered data through the unique product identifier displayed within one or more medium; and
- the consumer network enabled computing machine directly conducting transaction in relation to the retrieved data resulting in direct purchase of product without redirection to another webpage for the purchase and without providing consumer account information considered confidential to the merchant network enabled computing machine.
7. A computer program product for transaction, the computer program product comprising a non-transitory computer-readable medium having computer program instructions stored therein for causing one or more computers to perform operations of:
- establishing account associated with wireless transaction processing system (WTPS) computing platform for a non-merchant network enabled computing machine;
- the non-merchant network enabled computing machine accessing one or more computing machines associated with WTPS computing platform to access merchant tool modules of the WTPS to enter data related to products for product promotions and product sales, including storage of the data within a product data storage module of the WTPS computing platform;
- WTPS computing platform generating a unique product identifier associated with the entered data;
- the non-merchant network enabled computing machine receiving the unique product identifier generated from WTPS computing platform, and with the non-merchant network enabled computing machine displaying the unique product identifier within one or more medium;
- consumer network enabled computing machine with a consumer established account associated with WTPS computing platform retrieving the data through the unique product identifier displayed within one or more medium;
- with the consumer network enabled computing machine directly conducting transaction in relation to the retrieved data associated with the unique product identifier resulting in direct purchase of product without redirection to another webpage for the purchase and without providing consumer account information considered confidential to the merchant network enabled computing machine.
8. A point of sale (POS) system, comprising:
- a POS credit card authorization machine (CCAM) associated with a wireless transaction processing system (WTPS) computing platform;
- WTPS computing platform generating a WTPS merchant ID for the associated POS CCAM;
- with the POS CCAM with the WTPS merchant ID independently generating a transaction data of a transaction at a POS CCAM level: without the POS CCAM communicating with an external computing device, and without input of consumer information into POS CCAM for the transaction;
- with the transaction completed when the POS CCAM receives authorization for the transaction.
9. The point of sale (POS) system as set forth in claim 8, where:
- the POS CCAM is associated with the WTPS computing platform using a WTPS merchant account that includes an associated merchant account and POS CCAM identification information.
10. The point of sale (POS) system as set forth in claim 9, where:
- the transaction data includes at least:
- the POS CCAM identification information at which the transaction is processed.
11. The point of sale (POS) system as set forth in claim 10, where:
- the transaction data is received by a consumer network enabled computing machine that is associated with WTPS computing platform without the consumer network enabled computing machine providing consumer account information considered confidential;
- the received transaction data is processed by the consumer network enabled computing machine and after confirmation, the confirmed transaction data is communicated with WTPS computing platform;
- the WTPS computing platform receiving the confirmed transaction data, forwards one of an authorization and denial of transaction to POS CCAM based on a predetermined set of criteria.
12. A method for generating a transaction data at a point of sale (POS), comprising:
- establishing a wireless transaction processing system (WTPS) merchant account, which includes a merchant account and separate and individual identification information for each POS Credit Card Authorization Machine (CCAM) that is associated with the WTPS merchant account;
- generating a separate and individual WTPS merchant ID for each POS CCAM that is associated with the WTPS merchant account;
- associating the generated WTPS merchant ID with the corresponding POS CCAM;
- where the POS CCAM with the corresponding WTPS merchant ID functions in a standalone mode and independently generates the transaction data of a transaction at a POS CCAM level without communication with an external computing device and without input of consumer information into POS CCAM for the transaction;
- with the transaction completed when the POS CCAM receives authorization for the transaction.
13. The method for generating a transaction data at a point of sale (POS) as set forth in claim 12, where:
- the transaction data includes at least:
- the identification information of the POS CCAM at which the transaction is processed.
14. A method for generating a transaction data at a point of sale (POS) Credit Card Authorization Machine (CCAM), comprising:
- establishing a wireless transaction processing system (WTPS) merchant account with WTPS computing platform using a merchant network enabled computing machine;
- during establishing of the WTPS merchant account, entering POS CCAM data for each separate and individual POS CCAM, including storage of the POS CCAM data within a data storage module of the WTPS computing platform;
- WTPS computing platform generating a separate and individual WTPS merchant ID for each corresponding POS CCAM data of POS CCAM;
- associating the generated WTPS merchant ID with a corresponding POS CCAM;
- where the POS CCAM with the corresponding WTPS merchant ID independently generates a transaction data of a transaction at the corresponding POS CCAM level without communication with an external computing device and without input of consumer information into POS CCAM for the transaction;
- with the transaction completed when the POS CCAM receives authorization for the transaction.
15. The method for generating a transaction data at a point of sale (POS) computing terminal as set forth in claim 14, where:
- an individual POS CCAM data includes identification information of a separate and individual POS CCAM.
16. A computer program product for a point of sale (POS) Credit Card Authorization Machine (CCAM), the computer program product comprising a non-transitory computer-readable medium having computer program instructions stored therein for causing a POS CCAM to perform operations of:
- independently generating a transaction data of a transaction at the POS CCAM without the POS CCAM communicating with an external computing device, and without input of consumer information into POS CCAM for the transaction;
- with the generated transaction data including at least the identification information of the POS CCAM at which the transaction is processed.
17. A wireless transaction processing system (WTPS), comprising:
- a merchant network enabled computing machine associated with a WTPS computing platform to establish a WTPS merchant account;
- a consumer network enabled computing machine associated with WTPS computing platform to establish a WTPS consumer account;
- a transaction data for a transaction is generated by the merchant network enabled computing machine for selected products without input of consumer information, with the transaction data having no information considered confidential;
- the consumer network enabled computing machine receives the transaction data without providing consumer information considered confidential to the merchant network enabled computing machine;
- upon confirmation of the received transaction data, a transaction reference ID is dynamically generated by the consumer network enabled computing machine, with the transaction reference ID associated with the transaction;
- the consumer network enabled computing machine transmits data that includes the transaction data with the transaction reference ID and location data of both the consumer network enabled computing machine and location of merchant to the WTPS computing platform for validation of WTPS consumer account and consumer location, a WTPS merchant account and the merchant location, transaction reference ID, and transaction data;
- where WTPS computing platform receives the transmitted data from the consumer network enabled computing machine for verification.
18. The wireless transaction processing system (WTPS) as set forth in claim 17, where:
- if the location data of the consumer network enabled computing machine and location of merchant are determined to be different, based on a set of predetermined criteria, the WTPS computing platform generates an alert notification for denial of transaction.
19. The wireless transaction processing system (WTPS) as set forth in claim 17, where:
- if another consumer network enabled computing machine transmits the same data, then based on a set of predetermined criteria, the WTPS computing platform generates an alert notification for denial of transaction.
20. The wireless transaction processing system (WTPS) as set forth in claim 17, where:
- WTPS computing platform determines if one of a first access code and a second access code is entered for accessing a WTPS account, and based on a predetermined set of criteria, varies level of authorized access to the WTPS account.
21. The wireless transaction processing system (WTPS) as set forth in claim 20, where:
- the second access code is an emergency code, limiting access to the WTPS account, including execution of emergency activation protocols.
22. A computer program product for transaction, the computer program product comprising a non-transitory computer-readable medium having computer program instructions stored therein for causing one or more computers to perform operations of:
- transforming a network enabled computing machine into a merchant network enabled computing machine;
- accessing one or more computing machines that are associated with wireless transaction processing system (WTPS) computing platform to access merchant tool modules of the WTPS to enter data related to products, including storage of the data within a product data storage module of the WTPS computing platform;
- generating unique product identifier associated with the entered data;
- providing the unique product identifier to the network enabled computing machine to enable direct transaction in relation to retrieved data associated with the unique product identifier resulting in direct purchase of product without redirection to another site for the transaction and without providing consumer account information considered confidential to the merchant network enabled computing machine.
23. A wireless transaction possessing system (WTPS), comprising:
- a first consumer network enabled computing machine associated with a WTPS computing platform;
- the first consumer network enabled computing machine accessing one or more computing machines associated with WTPS computing platform to access tool modules of the WTPS to enter data related to products, including storage of the data within a product data storage module of the WTPS computing platform;
- WTPS computing platform generating a unique product identifier associated with the entered data;
- the first consumer network enabled computing machine receiving the unique product identifier generated by the WTPS computing platform;
- a second consumer network enabled computing machine associated with WTPS computing platform receiving the unique product identifier from the first consumer network enabled computing machine and conducting direct transaction with the first consumer network enabled computing machine in relation to retrieved data associated with the unique product identifier resulting in direct purchase of product without redirection to another webpage for the transaction and without providing consumer account information considered confidential to the merchant network enabled computing machine without providing consumer account information considered confidential to the first consumer network enabled computing machine.
24. The wireless transaction possessing system as set forth in claim 23, where:
- the direct transaction is a direct transfer of funds between the first consumer network enabled computing machine and the second consumer network enabled computing machine.
25. A direct fund transfer system, comprising:
- a payee account and payee mobile network enabled computing machine associated with a wireless transaction processing system (WTPS) computing platform;
- a payer account and payer mobile network enabled computing machine associated with the (WTPS) computing platform;
- payee identification information is internally retrieved by the payer mobile network enabled computing machine or manual entered into the payer mobile network enabled computing machine with funds for transfer to payee and upon confirmation, a transaction reference ID is dynamically generated by the payer mobile network enabled computing machine, with the transaction reference ID associated with a transaction data;
- the payer mobile network enabled computing machine transmits the transaction data with the transaction reference ID to the wireless transaction processing system for validation of payer account, payee account, and transaction reference ID and upon validation authorizes transfer of funds, crediting the payee account associated with the WTPS computing platform and debiting the payer account associated with the WTPS computing platform, and displaying results in payer and payee mobile network enable computing machines.
26. The direct fund transfer system as set forth in claim 25, where:
- the credited payee account includes credited funds for immediate, instantaneous expenditure in any purchasing environment, including use of the credited funds with a physical existing vendor.
27. The direct fund transfer system as set forth in claim 25, wherein:
- the funds transferred are one of real and virtual funds.
28. A method for disabling a wireless transaction processing system (WTPS) mobile application residing on a storage module of a network enabled mobile computing machine, comprising:
- accessing an established WTPS account associated with the network enabled mobile computing machine using a network enable computing machine;
- disabling the WTPS mobile application from the storage module of the network enabled mobile computing machine using the network enable computing machine to thereby block access to the WTPS account.
29. A wireless transaction processing system, comprising:
- servers that provide a hub for communications and cashless transactions between diverse entities;
- a third party processor server;
- at least one buyer account and a buyer mobile network enabled device selected and associated with the wireless transaction processing system;
- a seller account and a seller machine selected and associated with the wireless transaction processing system;
- the seller machine generates a transaction data, which has a machine-readable representation, for selected products for a transaction: without input of buyer information, without communicating with the wireless transaction processing system; and with the generated transaction data having no information considered confidential;
- the buyer mobile network enabled device directly receives and captures the transaction data, and upon confirmation, a transaction reference ID is dynamically generated by the buyer mobile network enabled device, with the transaction reference ID associated with the transaction;
- the buyer mobile network enabled device transmits the transaction data with the transaction reference ID and instantaneous location information of the buyer mobile network enabled device to the contactless wireless transaction processing system for validation of buyer account and buyer location, the seller account and the seller location, transaction reference ID, and transaction data;
- with the third party process server authorizing the transaction after validation by the contactless wireless transaction processing system; and
- with the seller account credited and the buyer account debited in accordance with the transaction data.
30. The wireless transaction processing system as set forth in claim 29, wherein:
- the received machine-readable representation of the data is one of a non-transitory wireless signal and a data image.
31. The wireless transaction processing system as set forth in claim 29, where:
- the buyer mobile network enabled device initiates disbursement protocols that enable receipt and capture of transaction data, including: purchase, direct transfer, and bill-payment.
32. The wireless transaction processing system as set forth in claim 29, where:
- machine readable representation of data further provides an Item identification to validate the products.
33. A transaction system, comprising:
- an integrated contactless wireless transaction processing system that is integrated with a credit issuing entity;
- at least one buyer account and a buyer mobile network enabled device selected and associated with the integrated contactless wireless transaction processing system of the credit issuing entity;
- a seller account and a seller machine selected and associated with the integrated contactless wireless transaction processing system of the credit issuing entity;
- the seller machine generates a transaction data, which has a machine-readable representation, for selected products for a transaction: without input of buyer information, without communicating with the integrated contactless wireless transaction processing system of the credit issuing entity; and with the generated transaction data having no information considered confidential;
- the buyer mobile network enabled device directly receives and captures the transaction data, and upon confirmation, a transaction reference ID is dynamically generated by the buyer mobile network enabled device, with the transaction reference ID associated with the transaction;
- the buyer mobile network enabled device transmits the transaction data with the transaction reference ID and instantaneous location information of the buyer mobile network enabled device to the integrated contactless wireless transaction processing system of the credit issuing entity for validation of buyer account and buyer location, the seller account and the seller location, transaction reference ID, and transaction data;
- with the credit issuing entity authorizing the transaction after validation by the wireless transaction processing system of the credit issuing entity; and
- with the authorization communicated with a merchant service provider of seller account, with the seller account credited and the buyer account debited in accordance with the transaction data directly by the credit issuing entity.
34. A computer program product for wireless transaction processing system for purchasing, the computer program product comprising a non-transitory computer-readable medium having computer program instructions stored therein for causing one or more computers to perform operations of:
- generating a transaction data for selected products for a transaction: without input of buyer information, without communicating with an external commuting device; and with the generated transaction data having no information considered confidential;
- receiving the transaction data associated with a registered seller account, and upon confirmation, generating a transaction reference ID associated with the transaction;
- transmitting the transaction data and the transaction reference ID with current location information of a buyer network enabled device associated with a buyer account associated with wireless transaction processing system;
- validating buyer account and buyer location, the registered seller account and seller location, transaction reference ID, and transaction data;
- authorizing the transaction after validation; and
- communicating authorization with a merchant service provider of the seller account, with the seller account credited and the buyer account debited in accordance with the transaction data.
35. A transaction system, comprising:
- a payee account and payee network enabled computing machine associated with a wireless transaction processing system (WTPS) computing platform;
- a payer account and payer network enabled computing machine associated with the (WTPS) computing platform;
- payee identification information is internally retrieved by the payer network enabled computing machine or manually entered into the payer network enabled computing machine with virtual funds for transfer to payee to conduct a transaction, and upon confirmation, a transaction reference ID is dynamically generated by the payer network enabled computing machine, with the transaction reference ID associated with a transaction data;
- the payer mobile network enabled computing machine transmits the transaction data with the transaction reference ID to the wireless transaction processing system for validation of payer account, payee account, and transaction reference ID and upon validation authorizes transfer of virtual funds, crediting the payee account associated with the WTPS computing platform and debiting the payer account associated with the WTPS computing platform, and displaying results in payer and payee mobile internet device.
36. A method for generating a transaction data at a point of sale (POS), comprising:
- establishing a wireless transaction processing system (WTPS) merchant account, which includes a merchant account and separate and individual identification information for each POS Server that is associated with the WTPS merchant account;
- generating a separate and individual WTPS merchant ID for each POS Server that is associated with the WTPS merchant account;
- associating the generated WTPS merchant ID with the corresponding POS Server;
- where the POS Server with the corresponding WTPS merchant ID functions in a standalone mode and independently generates the transaction data of a transaction at a POS Server level without communication with an external computing device and without input of consumer information into POS Server for the transaction;
- with the transaction completed when the POS Server receives authorization for the transaction.
37. The method for generating a transaction data at a point of sale (POS) as set forth in claim 36, where:
- the transaction data includes at least:
- the identification information of the POS Server at which the transaction is processed.
38. A method for generating a transaction data at a point of sale (POS) Server, comprising:
- establishing a wireless transaction processing system (WTPS) merchant account with WTPS computing platform using a merchant network enabled computing machine;
- during establishing of the WTPS merchant account, entering POS Server data for each separate and individual POS Server, including storage of the POS Server data within a data storage module of the WTPS computing platform;
- WTPS computing platform generating a separate and individual WTPS merchant ID for each corresponding POS Server data of POS Server;
- associating the generated WTPS merchant ID with a corresponding POS Server;
- where the POS Server with the corresponding WTPS merchant ID independently generates a transaction data of a transaction at the corresponding POS Server level without communication with an external computing device and without input of consumer information into POS Server for the transaction;
- with the transaction completed when the POS Server receives authorization for the transaction.
39. The method for generating a transaction data at a point of sale (POS) computing terminal as set forth in claim 38, where:
- an individual POS Server data includes identification information of a separate and individual POS Server.
40. A computer program product for a point of sale (POS) Server, the computer program product comprising a non-transitory computer-readable medium having computer program instructions stored therein for causing a POS Server to perform operations of:
- independently generating a transaction data of a transaction at the POS Server without the POS Server communicating with an external computing device, and without input of consumer information into POS Server for the transaction;
- with the generated transaction data including at least the identification information of the POS Server at which the transaction is processed.
Type: Application
Filed: Jan 17, 2014
Publication Date: Jul 23, 2015
Applicant: TYCOON UNLIMITED, INC. (Vernon, CA)
Inventors: Arthur Torossian (Glendale, CA), David Maxwell (Los Angele, CA)
Application Number: 14/158,671
