Patent Grant
10121217
The invention relates generally to electronic commerce, and more particularly, to electronic payment systems.
Healthcare providers (e.g., hospitals, physician offices, and the like) provide products and/or services to patients. In many cases, the price is not pre-determined, and a third party must ascertain the price. Some providers will require that the consumer pay or secure funds on an estimate (e.g., estimated patient responsibility) at the point of service. The third party (e.g., estimator, health plan) will calculate the price after the products and/or services are provided, with the understanding that the currency secured via an estimate will need to be adjusted and settled at a later date once the price is finalized (e.g., medical claim is processed by the health plan).
In particular, consumer payments to healthcare providers are moving away from predictable fixed dollar co-payment amounts to unknown percentage-based amounts. This change is due to the shift away from co-pay based health insurance plans to co-insurance based plans, which pay a percentage of the negotiated rate (usually after a deductible). Under these plans, healthcare providers do not know what to charge patients at the time of checkout. Claims need to be processed by the health plan to determine the patients' financial responsibility. Doctors are unable to collect any funds up front and therefore must bill the patient later. These payments become more difficult to collect.
Because the final transaction amount is not known until after the claim has been adjudicated, and since the adjudication process can take a significant amount of time (up to, or even exceeding, ninety days), it is necessary to hold funds for this entire amount of time. Additionally, the final amount is determined by the payer and/or issuer (not the provider or acquirer), further complicating the transaction process.
Principles of the invention provide techniques for processing uncertain transaction amounts in a payment system. An exemplary embodiment of a method (which can be computer-implemented), according to one aspect of the invention, for processing uncertain transaction amounts in a payment network configured to facilitate transactions between multiple issuers and multiple acquirers, includes the step of facilitating a first one of the acquirers receiving, via the payment network configured to facilitate the transactions between the multiple issuers and the multiple acquirers, an authorization response flagged with a flag. The flag indicates that clearing of a first one of the transactions, associated with the authorization response, is to be suspended. The first transaction initially has an uncertain amount, and the first transaction is associated with a first payment account of a first user; the first payment account in turn is associated with a first one of the issuers. Other steps include awaiting subsequent determination of a final certain amount for the first transaction, and, upon determination of the final certain amount, facilitating the first one of the acquirers proceeding with clearing the first transaction, based on the final certain amount. The steps of facilitating the authorization response, awaiting the final certain amount, and facilitating the clearing, are repeated for at least a second one of the acquirers and at least a second one of the transactions. The second transaction is associated with a second payment account of a second user, and the second payment account is in turn associated with a second one of the issuers. The steps are carried out by an operator of the payment network configured to facilitate the transactions between the multiple issuers and the multiple acquirers, and the flag is understandable to the first and second issuers and the first and second acquirers.
One or more embodiments of the invention or elements thereof can be implemented in the form of a computer product including a computer usable medium with computer usable program code for performing the method steps indicated. Furthermore, one or more embodiments of the invention or elements thereof can be implemented in the form of a system (or apparatus) including a memory and at least one processor that is coupled to the memory and operative to perform exemplary method steps. Yet further, in another aspect, one or more embodiments of the invention or elements thereof can be implemented in the form of means for carrying out one or more of the method steps described herein; the means can include hardware module(s), software module(s), or a combination of hardware and software modules.
One or more embodiments of the invention can provide substantial beneficial technical effects; for example, increased transactional efficiencies at the point of interaction and a reduction of post-service manual operations.
These and other features and advantages of the invention will become apparent from the following detailed description of illustrative embodiments thereof, which is to be read in connection with the accompanying drawings.
One or more embodiments of the invention provide a system and method which secure payment assurance for healthcare providers (or other merchants) at the point of service, by providing a “long running transaction” (suspended clearing with delayed settlement), as well as integration with various third party constituents (e.g., health plans, third party administrators, estimators, and the like) to enable one or more of:
Attention should now be given to
The ICs 104, 114 can contain processing units 106, 116 and memory units 108, 118. Preferably, the ICs 104, 114 can also include one or more of control logic, a timer, and input/output ports. Such elements are well known in the IC art and are not separately illustrated. One or both of the ICs 104, 114 can also include a co-processor, again, well-known and not separately illustrated. The control logic can provide, in conjunction with processing units 106, 116, the control necessary to handle communications between memory unit 108, 118 and the input/output ports. The timer can provide a timing reference signal from processing units 106, 116 and the control logic. The co-processor could provide the ability to perform complex computations in real time, such as those required by cryptographic algorithms.
The memory portions or units 108, 118 may include different types of memory, such as volatile and non-volatile memory and read-only and programmable memory. The memory units can store transaction card data such as, e.g., a user's primary account number (“PAN”) and/or personal identification number (“PIN”). The memory portions or units 108, 118 can store the operating system of the cards 102, 112. The operating system loads and executes applications and provides file management or other basic card services to the applications. One operating system that can be used to implement the invention is the MULTOS® operating system licensed by StepNexus Inc. Alternatively, JAVA CARD™-based operating systems, based on JAVA CARD™ technology (licensed by Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, Calif. 95054 USA), or proprietary operating systems available from a number of vendors, could be employed. Preferably, the operating system is stored in read-only memory (“ROM”) within memory portion 108, 118. In an alternate embodiment, flash memory or other non-volatile and/or volatile types of memory may also be used in the memory units 108, 118.
In addition to the basic services provided by the operating system, memory portions 108, 118 may also include one or more applications. At present, one possible standard to which such applications may conform is the EMV payment standard set forth by EMVCo, LLC (http://www.emvco.com). It will be appreciated that, strictly speaking, the EMV standard defines the behavior of a terminal; however, the card can be configured to conform to such EMV-compliant terminal behavior and in this sense is itself EMV-compliant. It will also be appreciated that applications in accordance with the invention can be configured in a variety of different ways.
In some instances, implementations may conform to appropriate healthcare payment card standards set forth by the Workgroup for Electronic Data Interchange, www.wedi.org. In some cases, implementations conform to pertinent ISO standards, such as ISO 8583. Individual entities or groups may develop specifications within this standard. Some messages (for example, authorization request and response) are defined within ISO 8583, while the flag mentioned below, given the teachings herein, may be implemented by the skilled artisan, for example, as part of a specification conforming to the ISO 8583 standard.
As noted, cards 102, 112 are examples of a variety of payment devices that can be employed with techniques of the invention. The primary function of the payment devices may not be payment, for example, they may be cellular phone handsets that implement techniques of the invention. Such devices could include cards having a conventional form factor, smaller or larger cards, cards of different shape, key fobs, personal digital assistants (PDAs), appropriately configured cell phone handsets, or indeed any device with the capabilities to implement techniques of the invention. The cards, or other payment devices, can include body portions (e.g., laminated plastic layers of a payment card, case or cabinet of a PDA, chip packaging, and the like), memories 108, 118 associated with the body portions, and processors 106, 116 associated with the body portions and coupled to the memories. The memories 108, 118 can contain appropriate applications. The processors 106, 116 can be operative to facilitate execution of one or more method steps. The applications can be, for example, application identifiers (AIDs) linked to software code in the form of firmware plus data in a card memory such as an electrically erasable programmable read-only memory (EEPROM). Again, note that “smart” cards are not necessarily required and a magnetic stripe card can be employed.
A number of different types of terminals can be employed with system 100. Such terminals can include a contact terminal 122 configured to interface with contact-type device 102, a wireless terminal 124 configured to interface with wireless device 112, a magnetic stripe terminal 125 configured to interface with a magnetic stripe device 150, or a combined terminal 126. Combined terminal 126 is designed to interface with any type of device 102, 112, 150. Some terminals can be contact terminals with plug-in contactless readers. Combined terminal 126 can include a memory 128, a processor portion 130, a reader module 132, and optionally an item interface module such as a bar code scanner 134 and/or a radio frequency identification (RFID) tag reader 136. Items 128, 132, 134, 136 can be coupled to the processor 130. Note that the principles of construction of terminal 126 are applicable to other types of terminals and are described in detail for illustrative purposes. Reader module 132 can be configured for contact communication with card or device 102, contactless communication with card or device 112, reading of magnetic stripe 152, or a combination of any two or more of the foregoing (different types of readers can be provided to interact with different types of cards e.g., contacted, magnetic stripe, or contactless). Terminals 122, 124, 125, 126 can be connected to one or more processing centers 140, 142, 144 via a computer network 138. Network 138 could include, for example, the Internet, or a proprietary network (for example, a virtual private network, such as the BANKNET® network (registered mark of MasterCard International Incorporated, Purchase, N.Y., USA). More than one network could be employed to connect different elements of the system. Processing centers 140, 142, 144 can include, for example, a host computer of an issuer of a payment device.
Many different retail or other establishments, represented by points-of-sale 146, 148, can be connected to network 138. Each such establishment can have one or more terminals. Further, different types of portable payment devices, terminals, or other elements or components can combine or “mix and match” one or more features depicted on the exemplary devices in
Portable payment devices can facilitate transactions by a user with a terminal, such as 122, 124, 125, 126, of a system such as system 100. Such a device can include a processor, for example, the processing units 106, 116 discussed above. The device can also include a memory, such as memory portions 108, 118 discussed above, that is coupled to the processor. Further, the device can include a communications module that is coupled to the processor and configured to interface with a terminal such as one of the terminals 122, 124, 125, 126. The communications module can include, for example, the contacts 110 or antennas 120 together with appropriate circuitry (such as the aforementioned oscillator or oscillators and related circuitry) that permits interfacing with the terminals via contact or wireless communication. The processor of the apparatus can be operable to perform one or more steps of methods and techniques. The processor can perform such operations via hardware techniques, and/or under the influence of program instructions, such as an application, stored in one of the memory units.
As used herein, “facilitating” an action includes performing the action, making the action easier, helping to carry the action out, or causing the action to be performed. Thus, by way of example and not limitation, instructions executing on one processor might facilitate an action carried out by instructions executing on a remote processor, by sending appropriate data or commands to cause or aid the action to be performed.
The portable device can include a body portion. For example, this could be a laminated plastic body (as discussed above) in the case of “smart” cards 102, 112, or the handset chassis and body in the case of a cellular telephone.
It will be appreciated that the terminals 122, 124, 125, 126 are examples of terminal apparatuses for interacting with a payment device of a holder. The apparatus can include a processor such as processor 130, a memory such as memory 128 that is coupled to the processor, and a communications module such as 132 that is coupled to the processor and configured to interface with the portable apparatuses. The processor 130 can be operable to communicate with portable payment devices of a user via the communications module 132. The terminal apparatuses can function via hardware techniques in processor 130, or by program instructions stored in memory 128. Such logic could optionally be provided from a central location such as processing center 140 over network 138. In some instances, the aforementioned bar code scanner 134 and/or RFID tag reader 136 can be provided, and can be coupled to the processor, to gather data, such as a product identification, from a UPC code or RFID tag on a product to be purchased.
The above-described devices 102, 112 can be ISO 7816-compliant contact cards or devices or ISO 14443-compliant proximity cards or devices. In operation, card 112 can be touched or tapped on the terminal 124 or 126, which then contactlessly transmits the electronic data to the proximity IC chip in the card 112 or other wireless device. Magnetic stripe cards can be swiped in a well-known manner.
One or more of the processing centers 140, 142, 144 can include a database such as a data warehouse 154 for storing information of interest. In the context of one or more embodiments of the invention, such as those depicted in
In one or more embodiments, the acquirers, upon notification of the issuer (via the authorization response message), delay submitting the clearing message for those transactions which have been estimated, until they have received final notification from the issuer with the final amount.
In particular, the acquirer delays submitting clearing records for specific transactions (that have been identified by the issuer) until the acquirer receives notification of the final transaction amount. Acquirers are notified, in an authorization response message, that the associated clearing transaction is to be suspended. Acquirers do not submit the transaction into clearing until further notice.
When the final transaction amount is determined, as a result of the claim adjudication process, an adjudicated transaction file is submitted to the issuer and/or the operator of a network operating according to a payment system standard (and/or specification), such as MasterCard International Incorporated of Purchase, N.Y., USA, depending on the preferred process selected. This file is then sent to the acquirer(s) who have the matching suspended transactions. The acquirer(s) then update and submit the clearing records, releasing the final patient responsible amount.
Attention should now be given to
At block 216, the health card is presented to the provider by the member or his or her insured spouse or child. In block 218, provider 204 requests a payment estimate, using, for example, an estimation tool 214 (such as a web site). As indicated at block 220, estimation tool 214 estimates the payment (EPR—estimated patient responsibility), and advises the provider 204, who has the chance to approve at block 222. If the provider 222 approves the EPR, the member 202 is advised at block 224, and the estimator 214 generates an EPR notification message at block 226, which serves to directly notify issuer 210 of the estimation. Receipt by the issuer is indicated at block 228. Estimator 214 preferably notifies issuer 210 by sending a message in real-time. Issuer 210 maintains a record of the estimate that was sent. In one or more embodiments, notification from the estimator 214 to the issuer 210 is done outside of the payment network 208.
If member 202 approves the EPR, as at block 230, provider 204 initiates a standard purchase authorization message, at block 232, using the estimated amount obtained from the estimation tool 214. Issuer 210 receives the purchase authorization message via standard payment network techniques, as shown at block 234. In decision block 236, issuer 210 matches information in the authorization message with the estimation notification previously received and stored in block 228. In one or more embodiments, the minimum information on which the transaction is matched includes account (card) number and amount. In one or more embodiments, the issuer 210 employs a mapping table to map the payer member identifier (ID) received in the estimation notification block 228 to the corresponding account (card) number.
If the match is successful (“YES” branch of decision block 236), the issuer 210, in block 238, authorizes the transaction, turns on a “suspend clearing” flag in the authorization response message, and places a hold on applicable funds or reduces the available balance. In one or more embodiments, the flag is only turned on for approved transactions. The suspend clearing flag can be implemented, for example, as a new data field added to the “auth” and “auth response” and clearing messages, thus adding new data elements and/or flags to current payment network messages. In the event the match is not successful, as per the “NO” branch of decision block 236, the standard authorization process is followed as shown in block 240.
In the case where the matching is successful, the authorization response 242 includes the “suspend clearing” flag, the provider receives the approval code in block 244, and the member 202 signs the EPR receipt in block 246. Provider 204 typically balances his or her terminal and submits transactions, in batch, to the authorization acquirer normally, as shown in block 248. Authorization/clearing acquirer 206 processes non-suspended transactions normally, but suspends clearing for marked transactions, as shown at blocks 250 and 252. Authorization/clearing acquirer 206 pays provider 204 for non-suspended transactions only and submits clearing for those transactions to the payment network operator 208. For suspended items, the provider receives a terminal activity report at block 254.
As shown at block 256, provider 204 submits an insurance claim to payer 212 in a normal fashion. Payer 212 then adjudicates the claim, in block 258, and determines the final patient responsibility amount. Payer 212 sends the adjudicated claim data for the program to the issuer 210, as indicated by block 260. Issuer 210 matches the adjudicated claim with the held estimated authorization, in block 262. In one or more embodiments, issuer 210 translates the payer member ID to an account (card) number, and uses other transaction information, such as date, time, amount, merchant name, and the like, to match the claim information with the authorization. Issuer 210 sends a bulk file with the actual patient responsibility amount to the payment network operator 208. Network operator 208 creates and sends files for each acquirer 206, so that each acquirer 206 can initiate the clearing process, by matching the file to the suspended transaction(s), as in blocks 264 and 266. Provider 204 receives payment and a reconciliation report in block 268. Clearing acquirer 206 sends in the Global Clearing management System (GCMS) first presentment record with a unique interchange rate designator (IRD) and special interchange compliance, as indicated at block 270. The provider receives an explanation of payment in block 272 and the member receives an explanation of benefits in block 274. Note that there is typically only a single acquirer per transaction; however, systems and methods according to one or more embodiments of the invention can handle multiple transactions associated with multiple acquirers. Note also that GCMS is a platform, specific to MasterCard International Incorporated, which translates and processes inbound and outbound files from issuers and acquirers. Other platforms with similar functionality can be used as well, and GCMS is a non-limiting example. Given the teachings herein, the skilled artisan will be able to implement the appropriate functionality. With regard to block 270, note that in an ordinary transaction, interchange rates are enforced and transactions must clear and settle in a specified amount of time, for example, within three days of authorization; otherwise penalties are incurred. In one or more embodiments, because the final transaction amount is not yet known, the timeliness edits are bypassed, and the interchange rules are appropriately modified.
Attention should now be given to
If member 202 approves the EPR, as at block 430, provider 204 initiates a standard purchase authorization message, at block 432, using the estimated amount obtained from the estimation tool 214. Issuer 210 receives the purchase authorization message via standard payment network techniques, as shown at block 434. In decision block 436, operator 208 matches information in the authorization message with the estimation notification previously received and stored in block 428. In one or more embodiments, the minimum information on which the transaction is matched includes account (card) number and amount. In one or more embodiments, the operator 208 employs a mapping table to map the payer member identifier (ID) received in the estimation notification block 428 to the corresponding account (card) number. Note that regardless of who performs the matching, the translation table will typically be required to map Member ID to card number.
If the match is successful (“YES” branch of decision block 436), the operator 208, in block 438, turns on a “suspend clearing” flag before communicating with issuer 210, which prepares the authorization response message in block 439, and also manages the open to buy (OTB) or available balance. When the match is successful, any amount previously held for that specific transaction should be released. In one or more embodiments, the flag is only turned on for approved transactions, as shown in blocks 441 and 443, wherein an authorization response with the “suspend clearing” flag set is sent from issuer 210 to acquirer 206 via network 208. Note that in the embodiments of
In the case where the matching is successful, the authorization response 441, 443 includes the “suspend clearing” flag, the provider receives the approval code in block 444 and the member 202 signs the EPR receipt in block 446
In the second embodiment, payer 212 adjudicates the claim, in block 458, and determines the final patient responsibility amount. Payer 212 sends the adjudicated claim data for the program to the operator 208, as indicated by block 460. Operator 208 matches the adjudicated claim with the held estimated authorization, in block 462. In one or more embodiments, operator 208 translates the payer member ID to an account (card) number, and uses other transaction information, such as date, time, amount, merchant name, and the like, to match the claim information with the authorization. Network operator 208 creates files for each acquirer 206, and sends same in block 464, so that each acquirer 206 can initiate the clearing process, by matching the file to the suspended transaction(s), as in block 466.
Embodiments of the invention may be particularly beneficial in the United States, due to changes in the health care industry, but may also be used cross industry and globally. Advantageously, in one or more embodiments of the invention, merchants (e.g., providers) can secure payment of an estimate at the point of service. Therefore, they do not need to resort to mechanisms such as card on file and/or post service billing.
In view of the specific examples above, it will be appreciated that, in general terms, one or more embodiments of the invention provide a method for processing uncertain transaction amounts in a payment network configured to facilitate transactions between multiple issuers and multiple acquirers. The method includes facilitating a first one of the acquirers 206 receiving, via the payment network (e.g., the network operated by entity 208), an authorization response (see blocks 242, 441, and 443) flagged with a flag. The flag indicates that clearing of a first one of the transactions associated with the authorization response, is to be suspended. The first transaction initially has an uncertain amount (for example, in an insurance plan where the patient-responsible balance is not known at the time the goods or services are provided to the patient). The first transaction is associated with a first payment account (for example, a card account) of a first user 202. The first payment account is, in turn, associated with a first one of the issuers 210.
An additional step includes awaiting subsequent determination of a final certain amount, for example, an adjudicated amount, for the first transaction (for example, by payer 212, as in blocks 258, 458). Upon determination of the final certain amount, a further step includes facilitating the first one of the acquirers 206 proceeding with clearing the first transaction, based on the final certain amount, as at blocks 270, 470.
The steps of facilitating the authorization response, awaiting the final certain amount, and facilitating the clearing are repeated for one or more additional acquirers, and for one or more additional transactions, associated with one or more additional payment accounts of one or more additional one of the issuers. The steps are carried out by the operator 208 of the network (recalling the definition of facilitating herein). The flag is understandable to the issuers and acquirers that are involved with the suspended clearing transactions.
An additional step that can be performed includes facilitating an intermediate party (i) obtaining a notification message pertaining to the first transaction from the third party estimator 214 (blocks 228, 428), and (ii) storing transaction data (e.g., the above-mentioned record of the estimate that was sent) associated with the notification message. The intermediate party can be, for example, the operator of the payment system 208, or the issuer 210 (of the card or other payment device associated with the first transaction). Further additional steps include facilitating the intermediate party obtaining an authorization request pertaining to the first transaction, as at blocks 234, 434, from a merchant associated with the first transaction (e.g., provider 204), and facilitating the intermediate party matching the authorization request against the notification message (blocks 236, 436), and, if the authorization request matches the notification message, facilitating flagging the authorization response for suspended clearing, with the flag (blocks 238, 438). Of course, this additional step can be repeated for additional entities and transactions.
As noted, in some instances, the merchant is a health care provider 204. An additional step that can be carried out includes facilitating submission of an insurance claim (blocks 256, 456) from the provider 204 to a third party payer 212. The insurance claim provides the basis for the aforementioned final certain (e.g., adjudicated) amount. Further steps include facilitating transmission of claim data associated with the insurance claim and the adjudicated amount from the third party payer 212 to the intermediate party 208 or 210, as at blocks 260, 460; facilitating comparison of the claim data with the stored transaction data, as at blocks 262, 462; and, if the comparison of the claim data with the stored transaction data is affirmative (matching successful at 262, 462), facilitating the intermediate party 208 or 210 communicating with the first acquirer 206 to effectuate the clearing of the first transaction, for example, as at blocks 264, 266, 268, and 270 in
As noted elsewhere, in some instances, the notification message 228, 248, from the third party estimator 214, is sent to the intermediate party 208 or 210 by a communications link other than the payment network, for example, via the Internet or an EDI layer. Note also, the third party estimator 214 could be associated with payer 212, or independent of payer 212. Further, note that the one or more of the transactions could be related to health care, an online auction, or the like.
It should be noted that one or more inventive techniques can be employed for situations other than the specific embodiments discussed herein. For example, the initial amount could be based on something other than an estimated patient-responsible amount, such as a maximum possible amount or a fixed amount. Further, techniques set forth herein could be useful in scenarios other than healthcare, and with merchants other than healthcare providers, whenever the actual transaction amount was uncertain until some later time. Thus, providers 204 are illustrative of a variety of merchants, and adjudication 258, 458 is typical of a variety of scenarios where an initially uncertain transaction amount later becomes a final, certain amount. Another exemplary non-limiting application is the field of online auctions; but again, one or more techniques of the invention may be applicable wherever the transaction amount is not known at the point of sale, and authorization is required up front but the amount owed is not yet known.
Aspects of the invention thus provide an open solution, including messaging and associated rules, wherein a plurality of different estimation engines (for example, many different entities 214) can work across the network 208—any transaction, which can typically be determined externally (i.e., outside network 208), can inherit the flag and be processed as a long-running transaction (suspended clearing). One or more embodiments of the invention can include a product or service provided to various and disparate banks or similar financial institutions, even competitors, to enable them to communicate the length of time (period) a hold should occur, across the network. The length may be predetermined, for example, by agreement among participating financial institutions. The flag communicates, at the time of the transaction, the need to apply the hold value. Embodiments of the invention, as noted, bypass timeliness checks and adjusting interchange (blocks 270 and 470).
With reference to
System and Article of Manufacture Details
The invention can employ hardware and/or software aspects. Software includes but is not limited to firmware, resident software, microcode, etc. Software might be employed, for example, in connection with one or more of a terminal 122, 124, 125, 126; a processing center 140, 142, 144 (optionally with data warehouse 154) of a merchant, issuer, acquirer, processor, payment processing network operator, other entity as depicted in blocks 202-214 of
As is known in the art, part or all of one or more aspects of the methods and apparatus discussed herein may be distributed as an article of manufacture that itself comprises a computer readable medium having computer readable code means embodied thereon. The computer readable program code means is operable, in conjunction with a computer system, to carry out all or some of the steps to perform the methods or create the apparatuses discussed herein. The computer readable medium may be a recordable medium (e.g., floppy disks, hard drives, compact disks, EEPROMs, or memory cards) or may be a transmission medium (e.g., a network comprising fiber-optics, the world-wide web, cables, or a wireless channel using time-division multiple access, code-division multiple access, or other radio-frequency channel). Any medium known or developed that can store information suitable for use with a computer system may be used. The computer-readable code means is any mechanism for allowing a computer to read instructions and data, such as magnetic variations on a magnetic media or height variations on the surface of a compact disk. The medium can be distributed on multiple physical devices (or over multiple networks). For example, one device could be a physical memory media associated with a terminal and another device could be a physical memory media associated with a processing center.
The computer systems and servers described herein each contain a memory that will configure associated processors to implement the methods, steps, and functions disclosed herein. Such methods, steps, and functions can be carried out, e.g., by processing capability on elements 102, 112, 122, 124, 125, 126, 140, 142, 144, processors associated with any entities as depicted in blocks 202-214 of
Thus, elements of one or more embodiments of the invention, such as, for example, the aforementioned terminals 122, 124, 125, 126; processing centers 140, 142, 144 with data warehouse 154; processors associated with any entities as depicted in blocks 202-214 of
Accordingly, it will be appreciated that one or more embodiments of the invention can include a computer program comprising computer program code means adapted to perform one or all of the steps of any methods or claims set forth herein when such program is run on a computer, and that such program may be embodied on a computer readable medium. Further, one or more embodiments of the invention can include a computer comprising code adapted to cause the computer to carry out one or more steps of methods or claims set forth herein, together with one or more apparatus elements or features as depicted and described herein.
Thus, aspects of the invention can be implemented, for example, by one or more appropriately programmed general purpose computers, such as, for example, servers or personal computers, located at one or more of the locations 204, 206, 210, 212, 214, as well as within network 208. Such computers can be interconnected, for example, by one or more of payment network 208, another VPN, the Internet, a local area and/or wide area network (LAN and/or WAN), via an EDI layer, and so on. The computers can be programmed, for example, in compiled, interpreted, object-oriented, assembly, and/or machine languages, for example, one or more of C, C++, Java, Visual Basic, and the like (an exemplary and non-limiting list), and can also make use of, for example, Extensible Markup Language (XML), known application programs such as relational database applications, spreadsheets, and the like. The computers can be programmed to implement the logic depicted in the flow charts of
Although illustrative embodiments of the invention have been described herein with reference to the accompanying drawings, it is to be understood that the invention is not limited to those precise embodiments, and that various other changes and modifications may be made by one skilled in the art without departing from the scope or spirit of the invention.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5550734 | Tarter et al. | Aug 1996 | A |
| 5803500 | Mossberg | Sep 1998 | A |
| 6343271 | Peterson et al. | Jan 2002 | B1 |
| 6685088 | Royer et al. | Feb 2004 | B1 |
| 6845906 | Royer et al. | Jan 2005 | B2 |
| 7043451 | Strayer et al. | May 2006 | B2 |
| 7076465 | Blagg et al. | Jul 2006 | B1 |
| 7239226 | Berardi et al. | Jul 2007 | B2 |
| 7249112 | Berardi et al. | Jul 2007 | B2 |
| 7268667 | Beenau et al. | Sep 2007 | B2 |
| 7343344 | Tomoike | Mar 2008 | B2 |
| 7346522 | Baylor et al. | Mar 2008 | B1 |
| 7370018 | Bryant, Jr. et al. | May 2008 | B2 |
| 20030069760 | Gelber | Apr 2003 | A1 |
| 20030200118 | Lee et al. | Oct 2003 | A1 |
| 20040020982 | Hoffman et al. | Feb 2004 | A1 |
| 20040148203 | Whitaker et al. | Jul 2004 | A1 |
| 20050004921 | Beenan et al. | Jan 2005 | A1 |
| 20050015280 | Gabel et al. | Jan 2005 | A1 |
| 20050182660 | Henley | Aug 2005 | A1 |
| 20050192895 | Rogers et al. | Sep 2005 | A1 |
| 20050261968 | Randall et al. | Nov 2005 | A1 |
| 20050288964 | Lutzen et al. | Dec 2005 | A1 |
| 20060167720 | Harrison et al. | Jul 2006 | A1 |
| 20070005402 | Kennedy et al. | Jan 2007 | A1 |
| 20070005403 | Kennedy et al. | Jan 2007 | A1 |
| 20070043595 | Pederson | Feb 2007 | A1 |
| 20070078689 | Zubak et al. | Apr 2007 | A1 |
| 20070106607 | Seib et al. | May 2007 | A1 |
| 20070179813 | Darling | Aug 2007 | A1 |
| 20070271119 | Boerger et al. | Nov 2007 | A1 |
| 20080010096 | Patterson | Jan 2008 | A1 |
| 20080140447 | Pourfallah et al. | Jun 2008 | A1 |
| Number | Date | Country |
|---|---|---|
| WO 2004006162 | Jan 2004 | WO |
| Entry |
|---|
| First Data—Healthcare, http://www.firstdata.com/your_business/healthcare.htm. |
| ISO 8583—Wikipedia, http://en.wikipedia.org/wiki/ISO_8583. |
| American Express HealthPay Plus(SM) > HealthPay Plus Works for Employees, http://www152.americanexpress.com/entcampWeb/HealthPayEmp.jsp. |
| Number | Date | Country | |
|---|---|---|---|
| 20100017235 A1 | Jan 2010 | US |
