Transaction processing platform for facilitating electronic distribution of plural prepaid services

Information

  • Patent Grant
  • 10552824
  • Patent Number
    10,552,824
  • Date Filed
    Friday, April 26, 2019
    11 months ago
  • Date Issued
    Tuesday, February 4, 2020
    a month ago
Abstract
A transaction processing platform capable of facilitating the distribution to consumers of various types of prepaid products is disclosed. The transaction processing platform is configured to interface with one or more providers of such prepaid products in order to facilitate the procurement or activation of the products. The platform includes a conduit interface through which service request messages are received and respectively utilized to generate transaction requests for corresponding types of prepaid services. A supply interface arrangement, operatively coupled to the conduit interface, is configured to route a first of the transaction requests through a first supply interface associated with a first type of prepaid service. The supply interface arrangement also routes a second transaction request through a second supply interface associated with a second type of prepaid service. The platform is also configured to provide supplier response information received through the supply interfaces to the conduit interface.
Description
FIELD OF THE INVENTION

The present invention relates generally to methods and apparatus for effecting payment for goods and services. More particularly, but not exclusively, the present invention is directed to systems and methods for facilitating the electronic activation and distribution of plural prepaid services following receipt of payment at a point-of-sale or other convenient location.


BACKGROUND

There currently exist “pre-paid” telephone cards that allow a customer to purchase a desired amount of long-distance telephone time from a particular telephone service provider. These pre-paid telephone cards are often sold by dealers such as convenience stores or wireless phone stores. Pre-paid telephone cards are also often sold in airports. Vending machines for selling pre-paid telephone cards also have been developed. Each of these pre-paid telephone cards has a specific monetary denomination. For example, a customer could purchase a $10 card, a $20 card, or a $100 card. These pre-paid telephone cards are sold by particular telephone service providers such as AT&T, MCI, Sprint, etc. A customer could, for example, buy a $20 MCI card, which would entitle him or her to $20 worth of long-distance calling service provided by MCI. These cards are referred to as “pre-paid” because the customer purchases the long-distance time before he or she actually places the call. This is in contrast to the more typical post-pay service that most telephone customers use with the telephone in their residence or office. With post-pay service, customers are sent a bill on a periodic basis. The customer pays for calls that have already been made, rather than calls that will be made in the future.


Frequently, the pre-paid telephone cards that are sold by dealers or vending machines are of the “scratch-off” type. After the customer purchases a card, he or she can scratch off a layer of material which reveals a personal identification number (PIN). The layer of scratch-off material hides the PIN from customers browsing in the store who have not purchased the card. After a customer purchases a card and scratches off the layer of material, the customer can then use the card to place a long-distance call. When the customer wishes to place a long-distance call, he or she dials a special number provided by the telephone service provider. The customer then enters the PIN written on the card. The long distance provider automatically debits the charge of the call from an account associated with the PIN.


As an example, a customer could purchase a $10 MCI card. After the customer rubs off the layer of material, a PIN number 129384348764 is revealed. When the customer wishes to place a long-distance call, the customer dials an MCI access number. The customer then enters PIN 129384348764. The long-distance carrier, MCI, identifies the PIN and recognizes that there is $10 worth of credit in this account. If the customer places a call which lasts 5 minutes and costs 4$, MCI will debit the account so that $6 remains. The next time the customer places a call using that PIN number, the system will find that $6 remains in the account associated with that PIN.


One problem with these pre-paid phone cards is that the cards present a major inventory headache for dealers. There is a lot of work and expense associated with maintaining a filled inventory of cards. First, the dealer or vending machine operator has to predict which cards will be in demand and determine how many cards of each denomination to order for each of various providers. The dealer then has to pay for the desired inventory of cards up front, which requires a significant cash outlay. The dealer then has to keep track of how many cards are left in stock for each service provider and of each different monetary denomination, and determine when to order a new batch of cards. All of these costs associated with filled inventory can be time consuming and expensive for dealers.


Another problem is that these pre-paid telephone cards are especially vulnerable to theft, loss, and other inventory “shrinkage.” Because the cards are small, it is easy for a shoplifter to pocket a card unnoticed. Since these cards have a high value to them and are so easy to pocket, dealers which sell these cards are extremely vulnerable to inventory shrinkage.


Vending card machines have been proposed which store personal identification numbers (PINs) in a memory in the machine. A customer can then purchase a pre-paid telephone PIN by inserting cash into the machine. Once the cash has been inserted, a PIN and usage instructions stored within the machine memory are printed upon a blank card that is dispensed to the customer. The machine can replenish its stock of PINs when the memory runs out of PINs or on a periodic basis by accessing a remote store of PINs via a modem.


The problem with these vending machines is that there are still significant costs associated with inventorying the PINs. The PINs are retained in a memory in the machine which has a similar effect to storing cards. Once a PIN has been stored in the memory of a particular machine, that PIN becomes unavailable to be used by any other dealer, even if the PIN is never purchased. Additionally, if the machine were to break, or the memory were to be erased, there is a problem determining who is responsible for paying for the PINs that were contained in the memory. Additionally, decisions must still be made how many PINs to store in memory, what monetary denominations to store in memory, and for which providers to store PINs in memory. Therefore, there are still significant inventory costs associated with storing the PINs in the vending machine. Additionally, these proposed vending machines do not provide consumers the ability to obtain a PIN from the convenience of their homes or offices.


A system addressing the shortcomings of these prepaid vending approaches is described in U.S. Pat. No. 6,526,130 (the “'130 patent”), which is assigned to the assignee of the present invention. The '130 patent describes a secure system capable of providing PINs for pre-paid goods and services conveniently to customers. The system of the '130 patent advantageously relieves dealers such as convenience stores and vending machine operators from the costs associated with maintaining a filled inventory of pre-paid cards and PINs. In addition, the system allows consumers to select from a wide-range of providers and monetary denominations without requiring the dealer to maintain a large filled inventory of cards or predict which type of cards or PINs to order. Specifically, after a customer purchases a pre-paid amount of a good or service, the customer receives a personal identification number (PIN) capable of being downloaded in real-time over a network such as the Internet. After the customer receives the PIN, the customer can then use this PIN at any convenient time to access the desired good or service. The system of the '130 patent also advantageously enables dealers from having to enter into separate business relationships with each prepaid service provider for which the dealer sells PINs. Similarly, the '130 system obviates the necessity for prepaid service providers to separately contract with each dealer distributing PINs on their behalf. However, an operator of the system of the '130 will typically be required to pay the various prepaid service providers for the PIN-based inventory maintained within the PIN repository of the '130 system, because such inventory needs to be available prior to being requested by a retailer.


In an effort to avoid the financial liability and potential for theft inherent within the conventional distribution of pre-activated PINs through retailers, some prepaid service providers have instead opted to rely upon point-of-sale activation of prepaid cards. When this approach is employed, the accounts associated with a set of prepaid cards (e.g., cards for prepaid telecommunications service) shipped to a retailer are not active and may not be used until authorization has been received from a central computing facility. Each shipped card may be imprinted with an account number or PIN identifying a specific account, or this information may be encoded within a magnetic stripe on the card.


As part of the process of distributing a prepaid card via point-of-sale activation, the retailer may swipe the prepaid card through a point-of-sale terminal so as to read the information encoded on the magnetic strip. Alternatively, this information may be read from the card by a clerk and keyed into the point-of-sale terminal. In either case the data is transmitted, either directly or indirectly, through the public switched telephone network to a central computing facility in the form of an activation request. The data within the activation request is compared to information for the account number or PIN previously stored within a central database of the computing facility. For example, information provided by the point of sale terminal may be compared to the previously stored information to determine if the location of the point of sale terminal matches the location identified by a control code encoded on the card's magnetic strip or otherwise imprinted upon the card. If the computing facility determines that activation request was issued from an authorized point-of-sale terminal, then the PIN or account number associated with the applicable card may be activated. At this point telecommunications or other services may be obtained by using the activated prepaid card in a conventional manner. In addition, the computing facility may return a code or message to the point of sale terminal confirming that the card has been activated and that the prepaid services are so capable of being obtained.


Unfortunately, it is currently not possible for retailers to electronically transact with a single entity for supply of multiple types of prepaid services offered by different prepaid service providers. Moreover, current prepaid service distribution systems have not adequately addressed the financial and security concerns of prepaid service providers while simultaneously affording them the convenience of dealing with only a single distribution entity.


SUMMARY

In summary, the present invention is directed to providing a transaction processing platform capable of facilitating the distribution to consumers of various types of prepaid products. Consistent with the invention, the transaction processing platform may be configured to interface with the systems of one or more providers of such prepaid products in order to facilitate the real-time procurement or activation of the products.


In a particular embodiment the transaction processing platform of the invention includes a conduit interface through which service request messages are received and respectively utilized to generate transaction requests for corresponding types of prepaid services. A supply interface arrangement, operatively coupled to the conduit interface, is configured to route a first of the transaction requests through a first supply interface associated with a first type of prepaid service. The supply interface arrangement also routes a second transaction request through a second supply interface associated with a second type of prepaid service. The platform is also configured to provide supplier response information received through the supply interfaces to the conduit interface.


In another aspect, the present invention pertains to a method for processing requests for prepaid services communicated to a transaction processing platform. The method includes receiving, through a first platform interface, a request for a personal identification number (PIN) generated by a first carrier entity. The method further includes receiving, through a second platform interface, a request for activation of a first prepaid card issued by a second carrier entity. A first transaction request is then routed, based upon the request for the PIN, to a first supply interface associated with the first carrier entity. The method also includes routing, based upon the request for activation, a second transaction request to a second supply interface associated with the second carrier entity.


The present invention also relates to a method for processing transactions involving prepaid services. The method includes receiving, at a first end-user interface device, an identification number associated with a prepaid card wherein the prepaid card is issued by a first carrier entity. The method further includes receiving, at a second end-user interface device, a request for a PIN generated by a second carrier entity. A first service request message is then generated, at the first end-user interface device, based upon the identification number. In addition, a second service request message is then generated, at the second end-user interface device, based upon the request for the PIN. The method further includes communicating the first service request message and the second service request message to a transaction processing platform. A first transaction request is then routed, based upon the first service request message, to a first supply interface. Similarly, a second transaction request is then routed, based upon the second service request message, to a second supply interface wherein the first supply interface is associated with the first carrier entity and the second supply interface is associated with the second carrier entity.


In yet another aspect the present invention is directed to a method for processing transactions involving prepaid services. The method includes generating, in response to a first service request message received through a conduit interface, a first transaction request for a first type of prepaid service provided by a first carrier entity. The method also includes generating, in response to a second service request message received through the conduit interface, a second transaction request for a second type of prepaid service provided by a second carrier entity. The first transaction request is then routed to a first supply interface associated with the first carrier entity and the second transaction request is routed to a second supply interface associated with the second carrier entity. The method also includes providing, based upon supplier activation information received through the first supply interface, a first service activation response to the conduit interface.


The present invention also relates to a method for processing transactions involving prepaid services. The method includes generating, in response to a first service request message received through a conduit interface, a first transaction request for a first type of prepaid service. The method also includes generating, in response to a second service request message received through the conduit interface, a second transaction request for a second type of prepaid service. The first transaction request is then routed to a first supply interface associated with the first type of prepaid service and the second transaction request is routed to a second supply interface associated with the second type of prepaid service. In addition, the method includes providing, based upon supplier activation information received through the first supply interface, a first service activation response to the conduit interface.


The present invention is further directed to a prepaid transaction processing method in which multiple units of one or more prepaid products may be provided pursuant to a single transaction. The method includes generating, in response to an order for prepaid services received through a conduit interface, a first transaction request for a first type of prepaid service. The method further includes generating, in response to the order, a second transaction request for a second type of prepaid service. The first transaction request is routed to a first supply interface associated with the first type of prepaid service. In addition, the second transaction request is routed to a second supply interface associated with the second type of prepaid service. The method further includes providing, based upon supplier activation information received through the first supply interface, a first service activation response to the conduit interface.


In another aspect the present invention is directed to a prepaid transaction processing method in which multiple prepaid product units may be provided pursuant to a single transaction. The method includes generating, in response to an order for prepaid services received through a conduit interface, a first transaction request for multiple units of a product relating to a first type of prepaid service. The first transaction request is routed to a first supply interface associated with the first type of prepaid service. The method also includes providing, to the conduit interface, product information received through the first supply interface in response to the first transaction request.


Additional aspects of the present invention are described below with respect to the appended drawings.





BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the nature of the features of the invention, reference should be made to the following detailed description taken in conjunction with the accompanying drawings, in which:



FIG. 1 is a block diagram representative of a system for electronically distributing prepaid products in accordance with the present invention.



FIG. 2 provides an illustration of the principal functional components of a transaction processing platform configured in accordance with an embodiment of the present invention.



FIG. 3 provides a block diagrammatic representation of an exemplary implementation of a platform front-end and conduit interface included within the transaction processing platform.



FIG. 4 provides a block diagrammatic representation of an exemplary implementation of a real-time supply (RTS) module included within the transaction processing platform.



FIG. 5 depicts an exemplary set of simplified records included within a PIN/POSA database 134 in communication with the transaction processing platform.



FIGS. 6A & 6B depict a flowchart illustrating a method of operating the transaction processing platform in accordance with the present invention.



FIGS. 7A & 7B depict a flowchart representative of the data flow between the conduit interface and the RTS module in connection with obtaining PIN or POSA information from either a PIN based or POSA-based provider, respectively.



FIGS. 8-11 illustratively represent a set of transaction routing tables utilized by the inventive transaction processing platform.



FIG. 12 is a process flow diagram representative of the data flow between the conduit interface and the RTS module in connection with obtaining PIN or POSA information from either a PIN based or POSA-based provider, respectively.





DETAILED DESCRIPTION

The present invention is directed to providing a transaction processing platform designed to facilitate the distribution to consumers of various types of prepaid products capable of being used to obtain goods and services such as, for example, telephone service, gasoline, electricity, dry-cleaning, bus service, subway service, magazines, newspapers, or bundled goods and services. Consistent with the invention, the transaction processing platform is configured to interface with the systems of one or more providers of such prepaid products in order to facilitate the real-time procurement or activation of the products. In exemplary embodiments of the invention these prepaid products may be of a number of different types including, for example, electronically-distributed PINs and prepaid cards requiring activation through point-of-sale application (POSA). In one embodiment, limited amounts of electronically-distributed PINs corresponding to various denominations of plural prepaid services offered by one or more service providers may also be maintained within a database co-located with the transaction processing platform. This permits the transaction processing platform to retrieve PINs from a local repository in certain cases, thus reducing latency by obviating the need to interface with a distal prepaid service provider.


After the customer purchases a pre-paid amount of a good or service, the customer either receives a personal identification number (PIN) or confirmation that a prepaid card purchased at a point-of-sale has been activated. In an exemplary embodiment the PIN or activation confirmation is generally provided by the transaction processing platform to the applicable point-of-sale over a network “on-demand”, meaning that the PIN or POSA activation confirmation is typically downloaded over the network immediately or very soon after receiving a request and payment from the customer. After the customer receives the PIN or POSA activation confirmation, the customer can then use this PIN or the activated prepaid card to access the desired good or service.


Referring to FIG. 1, a block diagram is provided of a system 100 for electronically distributing prepaid products in accordance with the present invention. As shown, the system 100 includes a prepaid transaction processing facility 110 in communication with a plurality of end-user terminals via the public switched telephone network (PSTN) and the Internet. In particular, the PSTN communicatively links a transaction processing platform 112 within the processing facility 110 to a number of point-of-sale (POS) terminals 114. Similarly, plural client terminals 118 may also be communicatively coupled to the transaction processing platform 112 by way of the Internet. It is to be understood that the modes of communication between the transaction processing platform 112 and the terminals 114, 118 may be any of those known in the industry, and as such may alternately comprise private telephone networks or other networks, whether public or private.


The transaction processing platform 112 is also capable of communicating with a plurality of providers of prepaid services relying upon point-of-sale application for activation (“POSA-based providers) 124 and with a plurality of PIN-based prepaid service providers 128 through a real-time-supply (RTS) data network 130. Although it is of course possible that a given carrier (e.g., Cingular) may offer both POSA-based and PIN-based products, for clarity of explanation the POSA-based providers 124 are depicted as being distinct from the PIN-based providers 128. Those skilled in the art will appreciate that the principles of the present invention are not limited to the case represented by FIG. 1, and are equally applicable to embodiments in which one or more suppliers elect to offer multiple different types of prepaid services. It may also be appreciated that the POSA-based providers 124 and PIN-based providers 128 may, in certain embodiments, be representative of vendors to which the applicable carriers have outsourced their PIN supply and POSA activation responsibilities.


In response to a request for a PIN or activation of a prepaid card received from a terminal 114, 118, the transaction processing platform 112 may either obtain a PIN from a PIN-based prepaid service provider 128 or request the applicable POSA-based provider 124 to activate the specified prepaid card. Once an activation response or PIN has been received over the RTS data network 130 from a POSA-based or PIN-based provider 124, 128, the transaction processing platform 112 communicates the PIN or activation response to the requesting terminal 114, 118. In the case of a request for a PIN, the transaction processing platform 112 may alternatively retrieve the requested PIN, if available, from a local PIN database 134 within or proximate the processing facility 110 and send the retrieved PIN to the requesting terminal 114, 118. The supply of PINs within the local PIN database 134 may be replenished at regular intervals or when otherwise necessary through receipt of PINs from the PIN-based providers 128 (or other PIN suppliers) via the RTS data network 130. Alternatively, the local PIN database 134 may be replenished by the providers 128 (or other PIN suppliers) by manual downloading of PINs over another network (not shown) distinct from the RTS data network 130.


Each POS terminal 114 typically comprises a terminal device located at a retail facility that generally allows sales and credit card data to be exchanged between the retail facility and remote processing centers via the PSTN or other communication network. As is described hereinafter, each POS terminal 114 is also disposed to communicate with the transaction processing platform 112 in accordance with the present invention. Exemplary terminal devices capable of functioning as the POS terminals 114 are described in, for example, the above-referenced copending application Ser. No. 10/925,218.


When being utilized to request a PIN or point-of-sale activation of a prepaid card in accordance with the invention, a POS terminal 114 accesses the transaction processing platform 112 by calling a special number, typically a toll-free number. In this regard the POS terminal 114 may be programmed to call the special number when a prepaid phone card to be activated is “swiped” through the terminal 114, or may be simply be configured to call the special number in response to one or more keystrokes. Alternatively, when the POS terminal 114 is connected to a local area network or the like of the retail facility in which it is disposed, a computer or other device also connected to the local area network may instead be programmed to call the transaction processing platform 112.


As shown in FIG. 1, the transaction processing platform 112 may also be accessed via the Internet using the client terminals 118. Accordingly, each client terminal 118 executes a browser program 142 (e.g., Internet Explorer™) capable of permitting the terminal 118 to access the transaction processing platform 112 by entering an appropriate URL within the user interface of the browser program 142. In this way requests for PINs or for activation of prepaid cards may be entered into the browser program 142 and communicated to the transaction processing platform 112. For convenience of expression, the POS terminals 114 and client terminals 118 may be collectively referred to hereinafter as “client terminals”.


Each PIN-based service provider 128 may be any service provider that provides telecommunication services, such as local telephone service, wireless telephone service, long distance, Internet service, or any other telecommunication or other services that may be provided in a prepaid manner through electronic distribution of a PIN. Similarly, each POSA-based service provider 124 may be any service provider capable of providing such services in a prepaid manner through remote activation of a prepaid card dispensed at a point-of-sale. Consistent with the invention, service providers 124, 128 cooperatively work with the transaction processing facility 110 to effect the distribution and activation of PIN-based and POSA-based prepaid products useable to obtain such services.


As is discussed in more detail below, once a PIN has been retrieved from the local PIN database 134 or otherwise obtained from a PIN-based provider 128, the PIN is sent by the transaction processing platform 112 to one of the terminals 114, 118 along with instructions for using the PIN. In the case of telecommunications services, these instructions will generally specify a toll-free access number which the customer is required to dial before placing a call and entering the PIN. Similarly, once a given POSA-based provider 128 has activated an account associated with a prepaid card purchased by a consumer at the location of a terminal 114, 118, an activation response received by the transaction processing platform 112 from such provider 128 is communicated to the applicable terminal 114, 118. This informs the customer that prepaid services associated with the account may be procured in the manner indicated by instructions printed upon the purchased prepaid card.


Turning now to FIG. 2, an illustration is provided of the principal functional components of the transaction processing platform 112. As shown, the transaction processing platform 112 includes a platform front-end 202, a conduit interface 204, a real-time supply (RTS) module 208, and a platform database 212. Each of the functional components of the transaction processing platform 112 may be realized using a combination of software and/or hardware for performing a task or set of tasks. For example, certain of the functional components may include at least a data processor, memory, and computer program code collectively enabling the component to carry out its prescribed tasks. In addition, ones of the functional components may also include input and output devices, short term and long term memory systems, communication devices, or multiple processors. In some implementations certain of the functional components may share common hardware and portions of a software library. It should be understood that the set of functional components of the platform 112 described herein is conceptual in nature, and there may exist a variety of combinations of hardware and software elements capable of executing the tasks of each component.


Platform database 212 includes client terminal records 242, customer records 243, provider records 244, advertising records 245 and routing tables 250. Client terminal records 242 store information concerning the locations of the terminals 114, 118. Client terminal records 242 can store any information specific to each of the terminals 114, 118, such as previous purchase history, payment and account information, and terminal preferences.


Customer records 243 provide information unique to individual customers. For example, customers can access the transaction processing platform 112 through a variety of different conduits, and may provide identifying information. The transaction processing platform 112 can use this information to provide better service to the customer, to target advertising to the customer, or to store payment or credit accounts.


Provider records 244 contain information pertinent to those providers 128 which provide PINs on a substantially real-time basis via the RTS data network 130 and/or which re-supply the local PIN database 134. For example, these records can contain addresses, billing information, and telephone numbers. The provider records 244 may also contain similar information regarding the POSA-based providers 124.


The advertising records 245 contain information about advertising banners and links that can be provided to client terminals 114, 118 as an additional source of revenue.


Routing tables 250 contain information which facilitates the routing of transactional information generated by the conduit interface 204 among various interfaces of the RTS module 208, and are described in further detail below.


As is described below, during operation of the platform 112 the conduit interface 204 receives, via platform front-end 202, service request messages for PINs and activation of prepaid cards from terminals 114, 118 and generates corresponding PIN transaction requests 220 and POSA transaction requests 224, respectively. In the exemplary embodiment the PIN transaction requests 220 and POSA transaction requests 224 are created, and routed to appropriate interfaces of the RTS module 208, by performing various database operations using the information within the routing tables 250. In response to a PIN transaction request 220 received at one of its interfaces, the RTS module 208 may obtain a PIN of the requested type from either the local PIN database 134 or one of the PIN-based prepaid service providers 128. Once the requested PIN has been obtained, the RTS module 208 provides the PIN and any ancillary information to the conduit interface 204 in the form of a PIN response message 230. The information within the PIN response message 230 is then communicated by the conduit interface 204 to the requesting terminal 114, 118 via the platform front-end 202, and the results recorded within the PIN/POSA database 134. Similarly, in response to a POSA transaction request 224, the RTS module 208 issues a request to the applicable POSA-based provider 124 to activate the specified prepaid card. Once an activation response has been received by the RTS module 208 from a POSA-based provider 124, the RTS module 208 provides activation response information 234 (e.g., activation successful or declined) to the conduit interface 204 and records the result within the PIN/POSA database 134. In turn, the conduit interface 204 communicates a corresponding activation response message to the requesting terminal 114, 118 via the platform-front-end.


In an exemplary embodiment the RTS module 208 determines which provider 124, 128 to contact and the appropriate manner in which to interact with such provider 124, 128 for procuring/activating a product item in real time. The RTS module 208 preferably provides a transparent mechanism capable of internally determining the way in which the product will be supplied/activated in real time and of controlling the actual interaction with the providers 124, 128. In the exemplary embodiment the RTS module 208 provides a separate interface for each product type supported by the transaction processing platform 112 (e.g., PIN, POSA). The conduit interface 204 utilizes the one of these interfaces corresponding to the type of product involved in the applicable transaction.


Attention is now directed to FIG. 3, which provides a block diagrammatic representation of an exemplary implementation of the platform front-end 202 and the conduit interface 204. As shown, the platform front-end 202 communicatively couples the platform 112 to the Internet through a firewall 304 and to the PSTN through a PSTN interface 308. A load-balancing switch 312 apportions the PIN/POSA service request messages received from terminals 114 via the PSTN among terminal application servers 316. The load-balancing switch 312 also apportions the PIN/POSA service request messages received from terminals 118 via the Internet among web servers 330.


In the embodiment of FIG. 3 the conduit interface 204 comprises a pair of conduit servers 320 respectively executing upon the terminal application servers 316 and an additional pair of conduit servers 334 respectively executing upon the web servers 330. In other embodiments the conduit interface 204 may also include conduit servers responsive to PIN/POSA service request messages generated by client terminals other than the client terminals 118. For example, other embodiments may contemplate the use of client terminals operative for wireless communication incorporating browsers utilizing the wireless markup language (WML).


Turning now to FIG. 4, an illustration is provided of an exemplary implementation of the RTS module 208 in block diagram form. As shown, the RTS module 208 is comprised of a POSA RTS service module 410 and a PIN RTS service module 420. The POSA RTS service module 410 may be represented as including a POSA supply controller 430 and a plurality of queues 434 for receiving POSA transaction requests destined for the various POSA-based providers 124. The queues 434 also hold POSA response information received from the providers 124. The PIN RTS service module 420 may be similarly represented as including a PIN supply controller 440 and a plurality of queues 444 for receiving PIN transaction requests destined for the various PIN-based providers 128. The queues 444 also hold POSA response information received from the providers 128. Of course, in alternate embodiments the RTS module 208 may include other service modules capable of handling transaction requests for other types of prepaid services (e.g., stored value, replenishment of an existing prepaid account, etc.).


Turning now to FIG. 5, there is depicted an exemplary set of simplified records included within PIN/POSA database 134. In one embodiment the PIN/POSA database 134 stores records 512 relating to PIN-based products, and records 522 relating to POSA-based products, potentially available for purchase by customers. Good/Service field 501 specifies the name of a good or service which is available for pre-paid purchase. For example, PIN-based records 512a-512j and POSA-based records 522a-522f shown in FIG. 5 relate to products providing access to pre-paid cellular service. Records 512k-1 shown in FIG. 5 relate to PIN-based products which provide access to pre-paid gasoline. Other goods and services can be also be included in PIN/POSA database 134 such as electricity, cable service, satellite TV, etc.


Provider field 502 contains the name of the particular good or service provider associated with the record. For example, FIG. 5 shows records for CINGULAR, AIRTOUCH, SPRINT, and MOBIL. Value field 504 specifies the dollar value associated with each record. For example, record 512e provides a customer with $30 of pre-paid cellular service from CINGULAR. For PIN-based records 512, the PIN field 506 specifies the PIN which is provided to the customer and allows access to the good or service. For POSA-based records 522, the PIN field 506 may specify either a PIN, an account number, or some other indicia of the prepaid card to be activated. Rate field 508 specifies a rate associated for each record. For example, for cellular telephone service rate field 508 specifies the calling rate associated with the record. In the exemplary PIN/POSA database 134 shown in FIG. 5, rate field 508 is not used for gasoline records 512k and 5121, since the gasoline rate is determined at the pump.


Expiration field 510 contains an expiration date beyond which the PIN or the equivalent for that record will no longer be valid. PIN status field 516 may be provided to facilitate cost of goods computations for accounting purposes. For example, in one embodiment the PIN status field 516 for a record reflects the status of “AVAILABLE” until the product corresponding to the record is actually sold, at which point the status is changed to “SOLD”. In other embodiments PIN-based records 512 may reflect a status of “SOLD” upon being loaded into the database 134, while the status of POSA-based records 522 may not be transitioned to a status of “SOLD” until activation of the product has actually occurred. A Usability status field 518 indicates whether the PIN or the equivalent associated with a given record 512, 522 is usable “as is” or whether activation of some sort is required to render it usable. In one embodiment a Usability status of “ACTIVE” reflects the former case (i.e., usable “as is”) while a Usability status of “INACTIVE” reflects the latter case.


Other fields may also be added to the database 134 For example, fields relating to batch number, sale price, cost, purchase data, cart type and the like may be included within the database 134 in other embodiments. In addition, certain other fields may be particular to a specific good or service. For example, if gasoline is being sold then there may be a field for “Octane” which specifies the octane level of gasoline being purchased.



FIG. 6 depicts a flowchart 600 illustrating a method of operating the transaction processing platform 112 in accordance with the present invention. Initially, the transaction processing platform 112 receives a request from a customer to begin the process of purchasing a prepaid product (stage 602). Again, in the exemplary embodiment such prepaid products comprise at least PIN-based and POSA-based products capable of being used upon purchase to obtain specified goods and services. In a stage 604, the transaction processing platform 112 determines whether the request to begin pertains to a PIN-based product or a POSA-based product.


In response to receiving a request to begin the process of purchasing a PIN-based product, the transaction processing platform 112 transmits to the requesting terminal 114, 118 a list of products and services offered (stage 606). For example, transaction processing platform could transmit a listing of provider information relating to: 1) cellular telephone service, 2) long-distance telephone service, 3) electricity, 4) gasoline, and so on. The list of products and services transmitted to the requesting terminal 114, 118 could appear upon, for example, a touch-screen (not shown) of such terminal. The customer may then select a good or service of interest, at which point the terminal 114, 118 generates a request for the chosen good or service and transmits it for receipt by the transaction processing platform 112 (stage 608). In stage 610, the transaction processing platform 112 transmits to the terminal 114, 118 a list of providers for the requested good or service. For example, if the customer has requested cellular telephone service, transaction processing platform 112 may transmit a list of: CINGULAR, AIRTOUCH, and SPRINT. The customer then selects one of these offered providers through the user interface of the applicable terminal 114, 118, which results in a request being transmitted to the transaction processing platform 112 for a particular requested provider. For example, the customer could select “AIRTOUCH.”


In stage 614, transaction processing platform 112 receives the customer's request for the particular provider requested. The transaction processing platform 112 then transmits to the terminal 114, 118 a list of regions for the requested good or service (stage 615). For example, if the customer requested “AIRTOUCH” in stage 614, then transaction processing platform 112 would transmit a list of regions such as “AIRTOUCH NORTHEASTERN U.S.,” or “AIRTOUCH NEW YORK CITY METROPOLITAN REGION,” OR “AIRTOUCH PACIFIC REGION,” etc. In stage 616, transaction processing platform 112 receives the customer's request for a particular region.


In stage 618, transaction processing platform 112 transmits a list of pre-paid monetary denominations offered. For example, if a request for “AIRTOUCH” is received, the operator of the transaction processing platform 112 might offer pre-paid cellular service for AIRTOUCH in the following monetary denominations: $10, $20, $50, and $100. Thus a customer could choose to buy a $50 “virtual” phone card which would provide him or her with $50 of pre-paid cellular service.


The conduit interface 204 of the transaction processing platform 112 can determine what monetary denominations are available by one of the following methods. As a first method, conduit interface 204 checks provider records 244 and looks up the record corresponding to the chosen provider (for example, AIRTOUCH). The conduit interface 204 then checks a field of the provider record to determine which monetary values may be requested from the chosen provider via the RTS module 208. In embodiments in which limited quantities of PINs for certain PIN-based products are obtained in advance from PIN-based providers 128 and locally stored within the PIN/POSA database 134, the conduit interface 204 may also check PIN/POSA database 134 in order to determine what types of monetary denominations have been locally stored.


As an alternative to transmitting a list of offered monetary denominations (stage 618), the customer could alternatively be allowed to simply type in at a keypad a desired amount of service that he or she desires. For example, a message would appear on touch-screen 204 stating “TYPE IN AN AMOUNT OF PRE-PAID SERVICE YOU WISH TO PURCHASE.” The customer could then type in, for example, $50. Transaction processing platform 112 would then determine, based upon the contents of the provider records 244, whether the requested denomination was available from the specified PIN-based provider 128. Alternatively, it could be determined whether PIN database 112 contains any $50 PIN denominations from the requested provider either before or after ascertaining availability of the requested denomination from the applicable PIN-based provider 128. If there are no $50 PINs available from either source, transaction processing platform 112 could, for example, transmit a message stating “THERE ARE NO $50 PINS AVAILABLE. WOULD YOU LIKE TO PURCHASE A $40 PIN OR A $75 PIN?” Alternatively, transaction processing platform 112 could transmit a message stating “THERE ARE NO $50 PINS AVAILABLE FOR AIRTOUCH. HOWEVER, SPRINT AND MCI OFFER $50 PINS FOR CELLULAR TELEPHONE SERVICE. WOULD YOU LIKE TO PURCHASE FROM ONE OF THESE PROVIDERS?”.


The customer can also be given an option to “View Rates.” If the customer chooses this option, then a request to view rates is sent to the transaction processing platform 112. In stage 624, the request is received by transaction processing platform 112. In stage 626, transaction processing platform 112 transmits rate information to the requesting terminal 114, 118. For example, the rate information could specify that a $100 “virtual” pre-paid phone card purchased from AIRTOUCH has a cellular calling rate of $0.35 per minute, and the PIN expires in 6 months. It could also specify that a $50 virtual pre-paid phone card purchased from AIRTOUCH has a cellular calling rate of $0.40 per minute, and the PIN expires in 8 months.


In a stage 630, transaction processing platform 112 receives from the client terminal a service request message specifying the selected provider and one of the available monetary denominations. For example, the customer could select an option to purchase a $50 PIN from AIRTOUCH by touching the appropriate option on touch-screen 204. In stage 634, the transaction processing platform 112 prompts the customer at the client terminal to make payment for the requested PIN. Payment can be made by the customer to the dealer in a number of ways (e.g., cash, credit card, debit card, smart card or any similar method). Once the customer pays the dealer, then the dealer must transfer a portion of the payment to the operator of the transaction processing platform 112. Payment can be apportioned and transferred between the dealer and the operator by a number of methods. Some example methods:


First method “ACH WALLET”: The dealer has a special account set up with the operator of the transaction processing facility 110. The dealer stores money in the account before the PIN is purchased. Immediately before a customer purchases one or more PINs, the dealer pays a portion of the payment to the operator of the transaction processing facility 110 by transferring money from the dealer's account to the operator's account by ACH (automated clearing house) electronic funds transfer. This method of payment is referred to as “ACH wallet.”


Second method “CREDIT ACCOUNT”: The dealer has a credit account with the operator of the transaction processing facility 110. The dealer is allowed a predetermined amount of credit based on the creditworthiness of the dealer. When a customer pays for one or more PINs, a portion of the payment is charged to the dealer's credit account. The dealer is then billed later for the amount charged.


Third method: The dealer simply provides credit card information to the operator of the transaction processing facility 110. When a customer purchases one or more PINs, a portion of the payment is charged to the dealer's credit card.


Fourth method: The customer's credit card information (or debit card, or smart card) is sent directly to the operator of the transaction processing facility 110. The operator of the transaction processing facility 110 then charges the customer's credit card and sends a portion of the payment back to the dealer.


As will be understood by one skilled in the art, the above methods are by example only and there are a multitude of ways that payment can be arranged between the dealer and the operator of the transaction processing facility 110. All of these methods do have one thing in common, however. The PIN is sent by the transaction processing facility 110 immediately after a payment is made (either by cash or credit). This eliminates costs associated with filled inventory; that is, because the PIN is sent right after payment is made, the dealer has no inventory carrying costs. Advantageously, the dealer does not have to predict which cards will be popular over the coming month, and how many cards of each type to order prior to the beginning of such month. Payment for the PIN is charged at the time of each transaction, and thus the dealer has no filled inventory costs.


In embodiments in which limited quantities of PINs are locally stored within the PIN/POSA database 134 and it is determined that a PIN corresponding to the requested denomination and provider exists within the database 134, then once payment has been received and verified (stage 634) the transaction processing platform 112 retrieves such a PIN from the database 134 (stage 640). Once this has occurred, the PIN status field 516 of the applicable record 512 may be marked as “SOLD” and unavailable so that the same PIN will not be sent to another customer.


Once the PIN status field 516 has been appropriately updated, the retrieved PIN and other information is transmitted by the transaction processing platform 112 to the requesting terminal 114, 118 (stage 644). The transaction processing platform 112 also transmits any instructions necessary to use the PIN. For example, the transaction processing platform 112 can transmit a telephone access number which the customer needs to dial before placing a cellular telephone call and entering the PIN. The telephone access number and other instructions will be unique for each provider. These instructions can either be stored in each individual record 512 in the database 134, or the instructions can be stored in provider records 244.


At stage 650, the client terminal 114, 118 prints out a receipt for the customer. The receipt includes the requested PIN(s) purchased by the customer, and any instructions for using the PIN such as a telephone access number. The receipt can also contain advertisements. Although the receipt will typically be printed upon paper, the receipt could alternately be in the form of a plastic card. The transaction processing platform 112 then returns back to stage 602, waiting for the next PIN or POSA transaction request.


Turning now to FIGS. 7 and 12, there are respectively shown a flowchart 700 and process flow diagram 1200 representative of the data flow between the conduit interface 204 and the RTS module 208 in connection with obtaining PIN or POSA information from either a PIN based provider 128 or a POSA-based provider 124, respectively. As mentioned above, the conduit interface 204 receives a service request message for a PIN or activation of a prepaid card received from terminals 114, 118 via front-end 202, and respectively generates corresponding PIN and POSA transaction requests (stage 704). In the case of POSA transaction requests, the card which is the subject of the request may be uniquely identified by specifying the applicable carrier or vendor (DNIS), and the PIN or batch/sequence numbers from the card. This information may be printed upon the card or stored within the magnetic strip on its back.


In the exemplary embodiment the PIN and POSA transaction requests are created and routed to appropriate interfaces of the RTS module 208 by performing various database operations using the information within the routing tables 250. In a stage 708, the process of generating such a transaction request is initiated upon extraction by the conduit interface 204 of a CardTypeID parameter from the received service request message (stage 708). The conduit interface 204 uses the CardTypeID to look up a ProductTypeID and a RegionID parameters from within a Card Types table 800 (FIG. 8) included within the routing tables 250 (stage 712). Next, the conduit interface 204 uses the RegionID parameter to look up a CarrierID parameter within a Regions table 900 (FIG. 9) included within the routing tables 250 (stage 716). In a stage 720, the conduit interface 204 uses the CarrierID parameter to look up an RTSCarrierID parameter in a Carriers table 1000 (FIG. 10) of the routing tables 250.


The conduit interface 204 uses the ProductTypeID parameter to determine which interface of the RTS module 208 should receive the applicable PIN or POSA transaction request (stage 728). In the exemplary embodiment the conduit interface 204 calls a method in the RTS module 208 to request a PIN or POSA transaction, and passes it the RTSCarrierID parameter and other parameters defining the transaction request (stage 732). In the exemplary embodiment the following are included among these other parameters defining a POSA transaction request: RequestType, StoreNumber, TerminalID, CardBatchNumber, CardSequenceNumber, Amount, and DNIS. In this regard the request type is a string representing a valid POSA request type. The parameters StoreNumber and TerminalID are strings respectively identifying the store and terminal from which the request originated. In addition, the parameters CardBatchNumber and CardSequenceNumber are strings respectively representing the card batch, and the sequence number in the batch, for the PIN activation being purchased. Finally, Amount is representative of the purchase amount, and DNIS is an input string represent of the dialed number identification service.


Next, the RTS module 208 uses the RTSCarrierID and ProductTypeID parameters to look up RTSVendorID and RTSID parameters in an RTSCarrierVendor table 1100 (FIG. 11) within the routing tables 250 (stage 734). The information inherent within the various parameters included within the transaction request enables the RTS module 208 to attempt to obtain the requested PIN or POSA information from the appropriate provider 124, 128 (stage 736). In the exemplary embodiment the communication over the RTS data network 130 between the RTS module 208 and the applicable provider 124, 128 is effected in accordance with conventional network protocols, such as TCP/IP. The RTS module 208 then determines whether the requested transaction was successful, and responds to the conduit interface 204 with an indication of success or failure of the transaction request (stage 738). If the transaction request is unsuccessful, the conduit interface returns an error message or code to the requesting terminal 114, 118 (stage 742).


If the RTS module 208 is successful in obtaining the requested PIN or POSA transaction information from the specified provider 124, 128, then this information is returned to the conduit interface 204 along with the RTSVendorID for the provider 124, 128 used in the transaction (stage 746). The POSA transaction information may include a POSA response code, an amount indicative of the requested amount, and a string representative of the vendor fulfilling the POSA request for the carrier indicated by the request. The conduit interface 204 may then use the RTSVendorID to look up information relative to the applicable provider 124, 128 from within the provider records 244 (stage 750). The conduit interface 204 then responds to the requesting terminal, via front-end 202, with the requested PIN or activation information (stage 754). As was previously described, in the case of a PIN transaction the requesting terminal then prints the PIN and any required ancillary information. Upon communicating this PIN or activation information to the requesting terminal 114, 118, the conduit interface 204 also updates the appropriate PIN-based record 512 or POSA-based record 522 within the database 134 (step 758).


Although the flowchart 700 and process flow diagram 1200 are directed to the case in which a request for a single product is received by the conduit interface 204, in alternate embodiments a single product order received by the conduit interface 204 may include a request for multiple units of a particular product or requests for one or more units of different products. For example, a terminal 114, 118 may generate an order comprised of a request for several PINs corresponding to a specified denomination (e.g., $50) of prepaid wireless service from a particular PIN-based provider 128 (e.g., Cingular), and additional POSA transaction requests directed to one or more different POSA-based providers 124. In these embodiments the conduit interface 204 is disposed to receive the order from the terminal 114, 118 and extract from it the multiple service request messages of which it is comprised. A PIN or POSA transaction request is then generated on the basis of each of these constituent service request messages. Each such transaction request is routed to an appropriate interface of the RTS module 208 and subsequently processed in the manner described above. If the RTS module 208 is successful in obtaining PIN/POSA transaction information corresponding to each of the transaction requests associated with a given order, then this information is aggregated by the conduit interface 204 and returned to the requesting terminal 114, 118. Otherwise, if one or more of the transaction requests is not successfully processed by the RTS module 208, the conduit interface returns an error message to the requesting terminal 114, 118. That is, in the exemplary embodiment orders for multiple products placed by the terminals 114, 118 are not “partially filled”, and are only completed if all requested prepaid products are available.


In certain implementations an order comprised of requests for multiple units of one or more products may originate from a network node interposed between one or more of the terminals 114, 118. Such a node could, for example, function as a cache for various types of products frequently dispensed by the terminals 114, 118. Those skilled in the art will appreciate that such an arrangement may reduce the latency characterizing operation of those terminals 114, 118 served by the caching network node.


The foregoing description, for purposes of explanation, used specific nomenclature to provide a thorough understanding of the invention. However, it will be apparent to one skilled in the art that the specific details are not required in order to practice the invention. In other instances, well-known circuits and devices are shown in block diagram form in order to avoid unnecessary distraction from the underlying invention. Thus, the foregoing descriptions of specific embodiments of the present invention are presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed, obviously many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the following Claims and their equivalents define the scope of the invention.

Claims
  • 1. A method for processing transactions involving prepaid services performed by a transaction processing platform having a processor and computer program code stored on a non-transitory computer readable memory which, when executed by the processor, causes the transaction processing platform to perform the method comprising: receiving from a client terminal operative for wireless communication, via an interface of the transaction processing platform, a first type of prepaid product purchase request;contacting, subsequent to receiving the first type of prepaid product purchase request, a service provider of the first type of prepaid product purchase request;receiving in real-time, indication of purchase of the first type of prepaid product and a personal identification number associated with the prepaid product; andelectronically distributing the first type of prepaid product to the client terminal, wherein the purchase request is received from the client terminal via electronic communication and the prepaid product is distributed via electronic communication to the client terminal.
  • 2. The method of claim 1 wherein electronic communication comprises wireless communication.
  • 3. The method of claim 1 wherein the transaction processing platform is accessed via a URL associated with the transaction processing platform.
  • 4. The method of claim 2, wherein the client terminal and a provider of the first type of prepaid product interface through a platform database to enable real-time procurement of the first type of prepaid product.
  • 5. The method of claim 4 further comprising: contacting a service provider of the second type of prepaid product request; andelectronically distributing the second type of prepaid product to the client terminal, wherein the client terminal and the service provider of the first type of prepaid product and the service provider of the second type of prepaid product interface through the transaction processing platform to enable real-time procurement of the first type of prepaid product and the second type of prepaid product.
  • 6. The method of claim 2 further comprising: determining advertising to provide to a customer based on information in a customer record associated with the client terminal through a platform database, wherein advertising is provided to the customer through the client terminal.
  • 7. The method of claim 2, further comprising: receiving from the client terminal a second type of prepaid product request, wherein the second type of prepaid product request comprises a second type of prepaid product, wherein the second type of prepaid product request is generated in response to the first type of prepaid product request and electronically delivered to the client terminal.
  • 8. The method of claim 2 wherein the transaction processing platform is accessed via a URL associated with the transaction processing platform.
  • 9. The method of claim 8, wherein the client terminal and a provider of the first type of prepaid product interface through a platform database to enable real-time procurement of the first type of prepaid product.
  • 10. The method of claim 9 further comprising: contacting a service provider of the second type of prepaid product request; andelectronically distributing the second type of prepaid product to the client terminal, wherein the client terminal and the service provider of the first type of prepaid product and the service provider of the second type of prepaid product interface through the transaction processing platform to enable real-time procurement of the first type of prepaid product and the second type of prepaid product.
  • 11. The method of claim 8 further comprising: determining advertising to provide to a customer based on information in a customer record associated with the client terminal through a platform database, wherein advertising is provided to the customer through the client terminal.
  • 12. The method of claim 8, further comprising: receiving from the client terminal a second type of prepaid product request, wherein the second type of prepaid product request comprises a second type of prepaid product, wherein the second type of prepaid product request is generated in response to the first type of prepaid product request and electronically delivered to the client terminal.
  • 13. A method for processing prepaid product transaction requests performed by a transaction processing platform having a processor and computer program code stored on a non-transitory computer readable memory which, when executed by the processor, causes the transaction processing platform to perform the method comprising: receiving a prepaid product transaction request message from a client terminal via an interface of the transaction processing platform;determining an appropriate service provider associated with the prepaid product;routing the transaction request to the appropriate service provider;receiving a response comprising a personal identification number associated with the prepaid product; anddelivering the personal identification number to the client terminal;wherein the client terminal is operative for wireless communication, the request message was received via electronic communication, and the personal identification number is delivered to the client terminal via electronic communication.
  • 14. The method of claim 13 wherein electronic communication comprises wireless communication.
  • 15. The method of claim 13 wherein the transaction processing platform is accessed via a URL associated with the transaction processing platform.
  • 16. The method of claim 14, wherein the client terminal and a provider of the first type of prepaid product interface through a platform database to enable real-time procurement of the first type of prepaid product.
  • 17. The method of claim 16 further comprising: contacting a service provider of the second type of prepaid product request; andelectronically distributing the second type of prepaid product to the client terminal, wherein the client terminal and the service provider of the first type of prepaid product and the service provider of the second type of prepaid product interface through the transaction processing platform to enable real-time procurement of the first type of prepaid product and the second type of prepaid product.
  • 18. The method of claim 14 further comprising: determining advertising to provide to a customer based on information in a customer record associated with the client terminal through a platform database, wherein advertising is provided to the customer through the client terminal.
  • 19. The method of claim 14, further comprising: receiving from the client terminal a second type of prepaid product request, wherein the second type of prepaid product request comprises a second type of prepaid product, wherein the second type of prepaid product request is generated in response to the first type of prepaid product request and electronically delivered to the client terminal.
  • 20. The method of claim 14 wherein the transaction processing platform is accessed via a URL associated with the transaction processing platform.
  • 21. The method of claim 20, wherein the client terminal and a provider of the first type of prepaid product interface through a platform database to enable real-time procurement of the first type of prepaid product.
  • 22. The method of claim 21 further comprising: contacting a service provider of the second type of prepaid product request; andelectronically distributing the second type of prepaid product to the client terminal, wherein the client terminal and the service provider of the first type of prepaid product and the service provider of the second type of prepaid product interface through the transaction processing platform to enable real-time procurement of the first type of prepaid product and the second type of prepaid product.
  • 23. The method of claim 20 further comprising: determining advertising to provide to a customer based on information in a customer record associated with the client terminal through a platform database, wherein advertising is provided to the customer through the client terminal.
  • 24. The method of claim 20, further comprising: receiving from the client terminal a second type of prepaid product request, wherein the second type of prepaid product request comprises a second type of prepaid product, wherein the second type of prepaid product request is generated in response to the first type of prepaid product request and electronically delivered to the client terminal.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority to, U.S. patent application Ser. No. 16/376,708, filed on Apr. 5, 2019, which is a continuation application of, U.S. patent application Ser. No. 12/538,083, filed on Aug. 7, 2009, which is a continuation application of, U.S. patent application Ser. No. 12/338,854, filed on Dec. 18, 2008, which is a continuation application of, U.S. patent application Ser. No. 11/851,337, filed on Sep. 6, 2006, now U.S. Pat. No. 7,477,731, which is a continuation application of, U.S. patent application Ser. No. 11/007,662, filed on Dec. 7, 2004, now U.S. Pat. No. 7,280,644, entitled “Transaction Processing Platform For Facilitating Electronic Distribution Of Plural Prepaid Services,” which is related to application Ser. No. 10/316,603, entitled “System And Method For Distributing Personal Identification Numbers Over A Computer Network”, which is a continuation of application Ser. No. 09/619,392, now U.S. Pat. No. 6,526,130. This application is also related to application Ser. No. 10/925,218, entitled “Method and Apparatus for Receipt Printing and Information Display in a Personal Identification Number Delivery System.” The content of each of these applications is hereby incorporated by reference herein in its entirety for all purposes.

US Referenced Citations (296)
Number Name Date Kind
4359631 Lockwood et al. Nov 1982 A
4567359 Lockwood Jan 1986 A
RE32115 Lockwood et al. Apr 1986 E
4694397 Grant et al. Sep 1987 A
4951196 Jackson Aug 1990 A
5220501 Lawlor et al. Jun 1993 A
5291017 Wang et al. Mar 1994 A
5309355 Lockwood May 1994 A
5350906 Brody et al. Sep 1994 A
5468958 Franzen et al. Nov 1995 A
5477038 Levine et al. Dec 1995 A
5500514 Veeneman et al. Mar 1996 A
5534683 Rankl et al. Jul 1996 A
5557516 Hogan Sep 1996 A
5569917 Buttrill, Jr. et al. Oct 1996 A
5576951 Lockwood Nov 1996 A
5577100 McGregor et al. Nov 1996 A
5577109 Stimson et al. Nov 1996 A
5578808 Taylor Nov 1996 A
5621787 McKoy et al. Apr 1997 A
5645434 Leung Jul 1997 A
5650604 Marcous et al. Jul 1997 A
5689100 Carrithers et al. Nov 1997 A
5693941 Barlow et al. Dec 1997 A
5696908 Muehlberger et al. Dec 1997 A
5701301 Weisser, Jr. Dec 1997 A
5714755 Wells et al. Feb 1998 A
5722067 Fougnies et al. Feb 1998 A
5744787 Teicher Apr 1998 A
5748737 Daggar May 1998 A
5763878 Franzen Jun 1998 A
5778313 Fougnies Jul 1998 A
5796832 Kawan Aug 1998 A
5812773 Morin Sep 1998 A
5826185 Wise et al. Oct 1998 A
5828740 Khuc et al. Oct 1998 A
5845259 West et al. Dec 1998 A
5854975 Fougnies et al. Dec 1998 A
5868236 Rademacher Feb 1999 A
5884292 Baker et al. Mar 1999 A
5892827 Beach et al. Apr 1999 A
5897625 Gustin et al. Apr 1999 A
5903633 Lorsch May 1999 A
5915007 Klapka Jun 1999 A
5920847 Kolling et al. Jul 1999 A
5937396 Konya Aug 1999 A
5943424 Berger et al. Aug 1999 A
5945653 Walker et al. Aug 1999 A
5953398 Hill Sep 1999 A
5969318 Mackenthun Oct 1999 A
5984180 Albrecht Nov 1999 A
5991380 Bruno et al. Nov 1999 A
5991381 Bouanaka et al. Nov 1999 A
5991413 Arditti et al. Nov 1999 A
5991749 Morrill, Jr. Nov 1999 A
5991809 Kriegsman Nov 1999 A
6000608 Dorf Dec 1999 A
6012048 Gustin et al. Jan 2000 A
6035025 Hanson Mar 2000 A
6044360 Picciallo Mar 2000 A
6049774 Roy Apr 2000 A
6058300 Hanson May 2000 A
6064990 Goldsmith May 2000 A
6081791 Clark Jun 2000 A
6081840 Zhao Jun 2000 A
6157823 Fougnies et al. Dec 2000 A
6169975 White et al. Jan 2001 B1
6182138 Aoki Jan 2001 B1
6185545 Resnick et al. Feb 2001 B1
6188752 Lesley Feb 2001 B1
6191699 Sawada Feb 2001 B1
6209032 Dutcher et al. Mar 2001 B1
6264104 Jenkins et al. Jul 2001 B1
6269343 Pallakoff Jul 2001 B1
6289319 Lockwood Sep 2001 B1
6289320 Drummond et al. Sep 2001 B1
6294780 Wells et al. Sep 2001 B1
6299062 Hwang Oct 2001 B1
6315195 Ramachandran Nov 2001 B1
6317754 Peng Nov 2001 B1
6320947 Joyce et al. Nov 2001 B1
6327363 Henderson et al. Dec 2001 B1
6330978 Molano et al. Dec 2001 B1
6386457 Sorie May 2002 B1
6453162 Gentry Sep 2002 B1
6467684 Fite et al. Oct 2002 B2
6502191 Smith Dec 2002 B1
6510983 Horowitz et al. Jan 2003 B2
6526130 Paschini Feb 2003 B1
6526275 Calvert Feb 2003 B1
6574617 Immerman et al. Jun 2003 B1
6581827 Welton Jun 2003 B2
6596990 Kasten et al. Jul 2003 B2
6615189 Phillips et al. Sep 2003 B1
6628766 Hollis et al. Sep 2003 B1
6651885 Arias Nov 2003 B1
6742023 Fanning et al. May 2004 B1
6759899 Lennartson et al. Jul 2004 B2
6827260 Stoutenburg et al. Dec 2004 B2
6829596 Frazee Dec 2004 B1
6842749 Zara et al. Jan 2005 B2
6910053 Pauly et al. Jun 2005 B1
6934529 Bagoren et al. Aug 2005 B2
6941285 Sarcanin Sep 2005 B2
6965667 Trabandt et al. Nov 2005 B2
6973172 Bitove et al. Dec 2005 B1
7003499 Arditti et al. Feb 2006 B2
7006993 Cheong et al. Feb 2006 B1
7014108 Sorenson et al. Mar 2006 B2
7031693 Öhrström et al. Apr 2006 B2
7083084 Graves et al. Aug 2006 B2
7089209 Kolls Aug 2006 B1
7092916 Diveley et al. Aug 2006 B2
7093761 Smith et al. Aug 2006 B2
7103575 Linehan Sep 2006 B1
7106843 Gainsboro et al. Sep 2006 B1
7118030 Phillips et al. Oct 2006 B2
7127426 Coyle Oct 2006 B1
7131578 Paschini et al. Nov 2006 B2
7131582 Welton Nov 2006 B2
7181416 Arias Feb 2007 B2
7191939 Beck et al. Mar 2007 B2
7197662 Bullen et al. Mar 2007 B2
7209890 Peon et al. Apr 2007 B1
7210620 Jones May 2007 B2
7212976 Scheer May 2007 B2
7216091 Blandina et al. May 2007 B1
7248855 Joyce et al. Jul 2007 B2
7255268 Dentlinger Aug 2007 B2
7260557 Chavez Aug 2007 B2
7268901 Brewster et al. Sep 2007 B2
7280644 Tamari Oct 2007 B2
7280645 Allen et al. Oct 2007 B1
7308087 Joyce et al. Dec 2007 B2
7325722 Hosnedl et al. Feb 2008 B2
7333955 Graves et al. Feb 2008 B2
7363265 Horgan Apr 2008 B2
7401049 Hobbs et al. Jul 2008 B2
7413117 Caven et al. Aug 2008 B2
7433212 Igarashi et al. Oct 2008 B2
7440922 Kempkes et al. Oct 2008 B1
7454200 Cai et al. Nov 2008 B2
7477731 Tamari Jan 2009 B2
7483858 Foran et al. Jan 2009 B2
7522716 Paschini Apr 2009 B2
7529563 Pitroda May 2009 B1
7562051 Donner Jul 2009 B1
7574376 Berman et al. Aug 2009 B1
7577613 Tramontano et al. Aug 2009 B2
7578439 Graves et al. Aug 2009 B2
7580859 Economy et al. Aug 2009 B2
7580892 Blosser et al. Aug 2009 B1
7581674 Cohen et al. Sep 2009 B2
7594855 Meyerhofer Sep 2009 B2
7607574 Kingsborough et al. Oct 2009 B2
7613284 New Nov 2009 B2
7614549 Hogg et al. Nov 2009 B2
7617152 Chai et al. Nov 2009 B2
7630926 Chakiris et al. Dec 2009 B2
7647627 Maida-Smith et al. Jan 2010 B2
7669758 Erikson Mar 2010 B2
7676030 New et al. Mar 2010 B2
7698231 Clinesmith et al. Apr 2010 B2
7707113 DiMartino et al. Apr 2010 B1
7739162 Pettay et al. Jun 2010 B1
7740170 Singh et al. Jun 2010 B2
7822640 Arthur et al. Oct 2010 B2
7865432 Doran et al. Jan 2011 B2
7890422 Hirka et al. Feb 2011 B1
7891563 Oder, II et al. Feb 2011 B2
7909242 Paschini et al. Mar 2011 B2
7925531 Cunningham et al. Apr 2011 B1
7945238 Baker et al. May 2011 B2
7945512 Scipioni et al. May 2011 B2
7966496 Ellmore Jun 2011 B2
8041338 Chen et al. Oct 2011 B2
8041642 Lenard et al. Oct 2011 B2
8086530 Resnick et al. Dec 2011 B2
8090792 Dubnicki et al. Jan 2012 B2
8135640 Bayne Mar 2012 B2
8195565 Bishop et al. Jun 2012 B2
8271343 Schorr et al. Sep 2012 B2
8297498 Vriheas et al. Oct 2012 B2
8306912 Galit Nov 2012 B2
8321270 Antonucci Nov 2012 B2
8355982 Hazel et al. Jan 2013 B2
8359239 Cook et al. Jan 2013 B1
8452880 Jain May 2013 B2
8458016 Medina, III et al. Jun 2013 B1
8472594 New et al. Jun 2013 B2
8479980 Paschini et al. Jul 2013 B2
8594286 New et al. Nov 2013 B2
8595074 Sharma et al. Nov 2013 B2
8603316 Cohen Dec 2013 B2
8626617 Bhatt Jan 2014 B1
8762236 Shirey et al. Jun 2014 B1
8768817 Takeo et al. Jul 2014 B2
9031880 Bishop et al. May 2015 B2
20010027446 Metcalfe Oct 2001 A1
20010037291 Allen, II Nov 2001 A1
20010042784 Fite Nov 2001 A1
20020010659 Cruse et al. Jan 2002 A1
20020046122 Barber et al. Apr 2002 A1
20020077973 Ronchi Jun 2002 A1
20020099667 Diamandis Jul 2002 A1
20020116280 Boies et al. Aug 2002 A1
20020128938 Schofield et al. Sep 2002 A1
20020152124 Guzman et al. Oct 2002 A1
20020152175 Armstrong et al. Oct 2002 A1
20020156696 Teicher Oct 2002 A1
20020161650 Buchanan et al. Oct 2002 A1
20020165820 Anvekar et al. Nov 2002 A1
20020174034 Au et al. Nov 2002 A1
20030046231 Wu Mar 2003 A1
20030046249 Wu Mar 2003 A1
20030050041 Wu Mar 2003 A1
20030083946 Nishiyama May 2003 A1
20030110104 King et al. Jun 2003 A1
20030126075 Mascavage, III et al. Jul 2003 A1
20030144910 Flaherty et al. Jul 2003 A1
20030177028 Cooper et al. Sep 2003 A1
20030200179 Kwan Oct 2003 A1
20030236755 Dagelet, Jr. Dec 2003 A1
20040011866 Saad Jan 2004 A1
20040031847 Sorenson Feb 2004 A1
20040049598 Tucker et al. Mar 2004 A1
20040078332 Ferguson et al. Apr 2004 A1
20040086098 Craft May 2004 A1
20040088250 Bartter et al. May 2004 A1
20040128508 Wheeler et al. Jul 2004 A1
20040153410 Nootebos et al. Aug 2004 A1
20040185827 Parks Sep 2004 A1
20040205023 Hafer et al. Oct 2004 A1
20040210489 Jackson et al. Oct 2004 A1
20040215560 Amalraj et al. Oct 2004 A1
20040230489 Goldthwaite et al. Nov 2004 A1
20040254891 Blinn et al. Dec 2004 A1
20050008132 Paschini et al. Jan 2005 A1
20050010452 Lusen Jan 2005 A1
20050038714 Bonet et al. Feb 2005 A1
20050038718 Barnes et al. Feb 2005 A1
20050192893 Keeling et al. Sep 2005 A1
20050199706 Beck Sep 2005 A1
20050229003 Paschini et al. Oct 2005 A1
20060026073 Kenny, Jr. et al. Feb 2006 A1
20060043171 New et al. Mar 2006 A1
20060045244 New Mar 2006 A1
20060064344 Lidow Mar 2006 A1
20060074783 Agarwal et al. Apr 2006 A1
20060074799 Averyt et al. Apr 2006 A1
20060078100 Risafi et al. Apr 2006 A1
20060129419 Flaxer et al. Jun 2006 A1
20060184613 Stienessen Aug 2006 A1
20060242087 Naehr et al. Oct 2006 A1
20060248017 Koka et al. Nov 2006 A1
20060253335 Keena et al. Nov 2006 A1
20070023504 Blankenship et al. Feb 2007 A1
20070073586 Dev et al. Mar 2007 A1
20070198437 Eisner et al. Aug 2007 A1
20070276765 Hazel et al. Nov 2007 A1
20080040284 Hazel et al. Feb 2008 A1
20080059302 Fordyce, III et al. Mar 2008 A1
20080059379 Ramaci et al. Mar 2008 A1
20080147546 Weichselbaumer et al. Jun 2008 A1
20080147552 Morsillo et al. Jun 2008 A1
20080162360 Bantz et al. Jul 2008 A1
20080177655 Zalik Jul 2008 A1
20080189214 Mueller et al. Aug 2008 A1
20080195499 Meredith et al. Aug 2008 A1
20080223920 Duke Sep 2008 A9
20080255992 Lin Oct 2008 A1
20080270253 Huang Oct 2008 A1
20090106160 Skowronek Apr 2009 A1
20090254441 Ahlers et al. Oct 2009 A1
20100036743 Tamari et al. Feb 2010 A1
20100114731 Kingston et al. May 2010 A1
20100114773 Skowronek May 2010 A1
20100299195 Nix et al. Nov 2010 A1
20100299221 Paschini et al. Nov 2010 A1
20100299733 Paschini et al. Nov 2010 A1
20110035446 Goermer et al. Feb 2011 A1
20110041006 Fowler Feb 2011 A1
20110125645 Benkert et al. May 2011 A1
20110226620 Tadayoni-Rebek et al. Sep 2011 A1
20120265681 Ross Oct 2012 A1
20120317028 Ansari Dec 2012 A1
20130013510 Ansari Jan 2013 A1
20130018783 Ansari Jan 2013 A1
20130036019 Tamari et al. Feb 2013 A1
20130054470 Campos et al. Feb 2013 A1
20130066735 Llach Mar 2013 A1
20130091060 Kundu Apr 2013 A1
20130036048 Campos et al. Aug 2013 A1
20130304642 Campos Nov 2013 A1
20140019352 Shrivastava Jan 2014 A1
20140214656 Williams et al. Jul 2014 A1
Foreign Referenced Citations (35)
Number Date Country
4017264 Dec 1991 DE
0863537 Sep 1998 EP
1286317 Feb 2003 EP
1829352 Sep 2007 EP
1829354 Sep 2007 EP
2521999 Nov 2012 EP
2215897 Sep 1989 GB
2287565 Sep 1995 GB
5225221 Sep 1993 JP
10155040 Jun 1998 JP
10174009 Jun 1998 JP
11259576 Sep 1999 JP
2003016368 Jan 2003 JP
20020020773 Mar 2002 KR
9641462 Dec 1996 WO
9746961 Dec 1997 WO
9847112 Oct 1998 WO
0111857 Feb 2001 WO
0116905 Mar 2001 WO
03071386 Aug 2003 WO
03083792 Oct 2003 WO
2004107280 Dec 2004 WO
2004107280 Dec 2004 WO
2006062832 Jun 2006 WO
2006062832 Jun 2006 WO
2006062842 Jun 2006 WO
2006062842 Jun 2006 WO
2011085241 Jul 2011 WO
2011159571 Dec 2011 WO
2011159579 Dec 2011 WO
2011159579 Dec 2011 WO
2012027664 Mar 2012 WO
2012166790 Dec 2012 WO
2013123438 Aug 2013 WO
2014107594 Jul 2014 WO
Non-Patent Literature Citations (50)
Entry
AFX-Asia, Company News, “Tata Hydro-Electric Q2 to Sept net profit 265.8 min rupees vs 212.4,” Oct. 28, 1999, pp. 1-2, AFX News Limited.
Ameritech Corp., “Ameritech debuts its prepaid cellular,” Abstract, RCR Radio Communications Report 15, No. 31, Ref. 7, Aug. 5, 1996, 1 page, Ameritech & ATM, PINS, or Prepaid Cards, 1994-1997, Lexis/Nexis Database.
Ameritech Corp., et al., “Ameritech in Prepaid Card Venture,” Abstract, American Banker CLX, No. 205, Ref. 9, Oct. 24, 1995, 1 page, Ameritech & ATM, PINs, or Prepaid Cards, 1994-1997, Lexis/Nexis Database.
Ameritech Corp., “Phone Cards Meet ATMs,” Abstract, Bank Technology News 8, No. 12, Ref. 8, Dec. 1995, 2 pages, Ameritech & ATM, PINs, or Prepaid Cards, 1994-1997, Lexis/Nexis Database.
Beach, Kirk W., et al., U.S. Pat. No. 5,892,827, Abstract, Ref. 7, Apr. 6, 1999, 1 page, Catalina Marketing International, Inc., 1994-1997, Lexis/Nexis Database.
Bernkopf, Mark, “Electronic Cash and Monetary Policy,” http://ojphi.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/viewFile/465/822, May 6, 1996, pp. 1-6, vol. 1, No. 1, First Monday.
Browne, F. X., et al., “Payments Technologies, Financial Innovation, and Laissez-Faire Banking,” The Cato Journal, http://www.cato.org/pubs/journal/cj15n1-6.html, Spring/Summer 1995, 12 pages, vol. 15, No. 1, Cato Institute.
Business Wire entitled “The Winners Edge.com Announces Purchase Agreement,” Nov. 1, 1999, pp. 1-2, West.
Business Wire entitled “Easy Wireless Unveils Its New Internet Powered Accessory Express Kiosk Station,” Feb. 25, 2000, pp. 1-2, West.
Business Wire entitled “Easy Wireless Unveils Its Revolutionary Pre-Paid PIN Dispensing Kiosk,” Feb. 28, 2000, pp. 1-2, West.
“Card Briefs: Sprint is Using EDS for Phone-Card Plan,” Abstract, The American Banker, Section: Credit/Debit/ATMs: p. 19, Mar. 13, 1995, 1 page, Ref. 4, EDS (Electronic Data Systems), 1994-1997, Lexis/Nexis Database.
“Codax Activation System,” http://www.carkleen.co.nz/Products/Codax, Car Kleen—Leaders in Vehicle Wash Technology, 2 pages. (no date is available).
Congressional Budget Office Study entitled “Emerging Electronic Methods for Making Retail Payments,” Jun. 1996, 63 pages, The Congress of the United States.
Derfler, Jr., Frank J., et al., “How Networks Work,” Bestseller Edition, 1996, 69 pages, Ziff-Davis Press, an imprint of Macmillan Computer Publishing, USA.
Piskora, Beth, “EDS' inroads into ATMs give banks pause,” abstract, American Banker, Jun. 29, 1995, 1 page, vol. 18, No. 1, Ref. 8, EDS (Electronic Data Systems), 1994-1995, Lexis/Nexis Database.
Q Comm International, Inc. product information entitled, “Q Comm's Qxpress System; on-Demand Retail Phone Cards,” http://web.archive.org/web/20000302140250/www.qcomm.com/products/ondemand.asp, Mar. 2000, 2 pages.
Smart Card Alliance Report PT-03002, “Contactless Payment and the Retail Point of Sale: Applications, Technologies and Transaction Models,” Mar. 2003, pp. 1-50.
Splendore, Maurizio, et al., “A new ion ejection method employing an asymmetric trapping field to improve the mass scanning performance of an electrodynamic ion trap,” International Journal of Mass Spectrometry, 1999, pp. 129-143, vol. 190/191, Elsevier Science B.V.
Ter Maat, Mike, “The economics of e-cash,” IEEE Spectrum, Feb. 1997, pp. 68-73, IEEE.
“The future of money: hearing before the Subcommittee on Domestic and International Monetary Policy of the Committee on Banking and Financial Services, House of Representatives, One Hundred Fourth Congress, first session,” The Future of Money, Part 4, http://www.archive.org/stream/futureofmoneyhea04unit/futureofmoneyhea04unit_djvu.txt, Jun. 11, 1996, 5 pages.
“US West Launches Christmas Prepaid Calling Card With Card Pioneer Innovative Telecom;—Sixty Minute Holiday Card Available Now—,” Abstract, PR Newswire, Dec. 5, 1997, 1 page, Section: Financial News, Ref. 1, Inovative Telecom, 1994-1997, Lexis/Nexis Database.
“VENDAPIN Model 5004 Four Selection Cellular and IP, Phone Calling Card, Lottery or Admissions Ticket Printer Vending Machine with Optional Two Selection Cellular Phone Dispenser Console,” http://www.vendapin.com/5008.html, Apr. 3, 2000, pp. 1-4, VENDAPIN.
Visa press release entitled “Visa Unveils Next Generation Electronic Payments and Services,” http://corporate.visa.com/newsroom/press-releases/press1124.jsp, May 11, 2011, 3 pages.
Filing receipt and specification for provisional patent application entitled “System for Processing, Activating and Redeeming Value Added Prepaid Cards,” by Teri Llach, filed Jan. 8, 2010 as U.S. Appl. No. 61/293,413.
Cover sheet and specification for provisional patent application entitled “System and Method for Electronic Prepaid Account Replenishment,” by Miles Paschini, et al., filed May 28, 2003 as U.S. Appl. No. 60/473,685.
Filing receipt and specification for patent application entitled “Transaction Processing Platform for Facilitating Electronic Distribution of Plural Prepaid Services,” by Roni Dolev Tamari, et al., filed Dec. 18, 2008 as U.S. Appl. No. 12/338,854.
Filing receipt and specification for provisional patent application entitled “Efficient Stored-Value Card Transactions,” by Ansar Ansari, filed Jun. 14, 2010 as U.S. Appl. No. 61/354,469.
Filing receipt and specification for provisional patent application entitled “Efficient Stored-Value Card Transactions,” by Ansar Ansari, filed Jun. 30, 2010 as U.S. Appl. No. 61/360,327.
Filing receipt and specification for provisional patent application entitled “Efficient Stored-Value Card Transactions,” by Ansar Ansari, filed Jun. 14, 2010 as U.S. Appl. No. 61/354,470.
Filing receipt and specification for provisional patent application entitled “System and Method for Configuring Risk Tolerance in Transaction Cards,” by Arindam Kundu, filed Jun. 14, 2010 as U.S. Appl. No. 61/354,474.
Filing receipt and specification for provisional patent application entitled “System and Method for Configuring Risk Tolerance in Transaction Cards,” by Arindam Kundu, filed Jun. 30, 2010 as U.S. Appl. No. 61/360,326.
Filing receipt and specification for provisional patent application entitled “Prepaid Card with Savings Feature,” by Kellie D. Harper, filed Aug. 27, 2010 as U.S. Appl. No. 61/377,800.
Filing receipt and specification for provisional patent application entitled “System for Payment via Electronic Wallet,” by Tomas Ariel Campos, et al., filed May 31, 2011 as U.S. Appl. No. 61/491,791.
Filing receipt and specification for provisional patent application entitled “System for Payment via Electronic Wallet,” by Tomas Ariel Campos, et al., filed May 31, 2011 as U.S. Appl. No. 61/491,813.
Filing receipt and specification for provisional patent application entitled System for Manging CVV Information in Electronic Wallet, by Tushar Vaish, filed Jan. 3, 2013 as U.S. Appl. No. 61/748,679.
Filing receipt and specification for provisional patent application entitled “System and Method for Providing a Security Code,” by Tushar Vaish, et al., filed Mar. 15, 2013 as U.S. Appl. No. 61/799,500.
Filing receipt and specification for provisional patent application entitled “System, Method, and Apparatus for Creating and Distributing a Transaction Credit,” by Ansar Ansari, filed Jun. 13, 2011 as U.S. Appl. No. 61/496,397.
Filing receipt and specification for provisional patent application entitled “System, Method, and Apparatus for Creating and Distributing a Transaction Credit,” by Ansar Ansari, filed Jun. 13, 2011 as U.S. Appl. No. 61/496,404.
Filing receipt and specification for provisional patent application entitled “Stored-Value Card Transactions Systems and Methods,” by Ansar Ansari, et al., filed Aug. 31, 2011 as U.S. Appl. No. 61/529,813.
Filing receipt and specification for provisional patent application entitled “Universal Interactive eGift Registration Button aka The Digital Sticker,” by Tomas Adel Campos, filed Feb. 15, 2012 as U.S. Appl. No. 61/599,249.
Filing receipt and specification for provisional patent application entitled “Universal Interactive eGift Registration Button aka The Digital Sticker,” by Tomas Adel Campos, filed Feb. 22, 2012 as U.S. Appl. No. 61/601,911.
Filing receipt and specification for provisional patent application entitled “eWallet with QR Code,” by Tomas Ariel Campos, filed Apr. 4, 2012 as U.S. Appl. No. 61/620,173.
Filing receipt and specification for provisional patent application entitled “Endless Endcap,” by Tomas Ariel Campos, filed Nov. 20, 2012 as U.S. Appl. No. 61/728,597.
Filing receipt and specification for provisional patent application entitled “System and Method for Using QR Codes in Conjunction with Electronic Stored-Value Cards,” by Tomas Ariel Campos, et al., filed Mar. 15, 2013 as U.S. Appl. No. 61/800,704.
Filing receipt and specification for provisional patent application entitled “Systems and Methods for Proxy Card and/or Wallet Redemption Card Transactions,” by Tushar Vaish, et al., filed Mar. 11, 2013 as U.S. Appl. No. 61/776,594.
Filing receipt and specification for provisional patent application entitled “Systems and Methods for Proxy Card and/or Wallet Redemption Card Transactions,” by Pranav Sheth, et al., filed Mar. 13, 2013 as U.S. Appl. No. 61/779,334.
Filing receipt and specification for provisional patent application entitled “Client Directed Pre-Paid Card,” by J. DuWayne Milner, filed Mar. 14, 2013 as U.S. Appl. No. 61/781,667.
Filing receipt and specification for provisional patent application entitled “Mimicking Post-Paid User Experience with Stored-Value Card Accounts,” by Richard Gotlieb, filed Oct. 26, 2015 as U.S. Appl. No. 62/246,126.
Foreign communication from a related counterpart application—International Search Report and Written Opinion, PCT/US2011/020570, dated Mar. 7, 2011, 11 pages.
Foreign communication from a related counterpart application—International Preliminary Report on Patentability, PCT/US2011/020570, dated Jul. 10, 2012, 8 pages.
Related Publications (1)
Number Date Country
20190251550 A1 Aug 2019 US
Continuations (5)
Number Date Country
Parent 16376708 Apr 2019 US
Child 16395786 US
Parent 12538083 Aug 2009 US
Child 16376708 US
Parent 12338854 Dec 2008 US
Child 12538083 US
Parent 11851337 Sep 2007 US
Child 12338854 US
Parent 11007662 Dec 2004 US
Child 11851337 US