US20050279827A1 - Methods and systems for providing guaranteed merchant transactions - Google Patents

Methods and systems for providing guaranteed merchant transactions Download PDF

Info

Publication number
US20050279827A1
US20050279827A1 US11/105,167 US10516705A US2005279827A1 US 20050279827 A1 US20050279827 A1 US 20050279827A1 US 10516705 A US10516705 A US 10516705A US 2005279827 A1 US2005279827 A1 US 2005279827A1
Authority
US
United States
Prior art keywords
merchant
transaction
credit
system
issuer
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US11/105,167
Inventor
John Mascavage
Margaret Weichert
Robert Hogan
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
First Data Corp
Original Assignee
First Data Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US56648604P priority Critical
Application filed by First Data Corp filed Critical First Data Corp
Priority to US11/105,167 priority patent/US20050279827A1/en
Assigned to FIRST DATA CORPORATION reassignment FIRST DATA CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MASCAVAGE, JOHN JOSEPH, HOGAN, ROBERT, WEICHERT, MARGARET MORGAN
Publication of US20050279827A1 publication Critical patent/US20050279827A1/en
Assigned to CREDIT SUISSE, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT reassignment CREDIT SUISSE, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT SECURITY AGREEMENT Assignors: CARDSERVICE INTERNATIONAL, INC., DW HOLDINGS, INC., FIRST DATA CORPORATION, FIRST DATA RESOURCES, INC., FUNDSXPRESS, INC., INTELLIGENT RESULTS, INC., LINKPOINT INTERNATIONAL, INC., SIZE TECHNOLOGIES, INC., TASQ TECHNOLOGY, INC., TELECHECK INTERNATIONAL, INC., TELECHECK SERVICES, INC.
Assigned to WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT reassignment WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT SECURITY AGREEMENT Assignors: DW HOLDINGS, INC., FIRST DATA RESOURCES, INC. (K/N/A FIRST DATA RESOURCES, LLC), FUNDSXPRESS FINANCIAL NETWORKS, INC., INTELLIGENT RESULTS, INC. (K/N/A FIRST DATA SOLUTIONS, INC.), LINKPOINT INTERNATIONAL, INC., MONEY NETWORK FINANCIAL, LLC, SIZE TECHNOLOGIES, INC., TASQ TECHNOLOGY, INC., TELECHECK INTERNATIONAL, INC.
Assigned to WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT reassignment WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT SECURITY AGREEMENT Assignors: DW HOLDINGS, INC., FIRST DATA RESOURCES, LLC, FIRST DATA SOLUTIONS, INC., FUNDSXPRESS FINANCIAL NETWORKS, INC., LINKPOINT INTERNATIONAL, INC., MONEY NETWORK FINANCIAL, LLC, SIZE TECHNOLOGIES, INC., TASQ TECHNOLOGY, INC., TELECHECK INTERNATIONAL, INC
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07FCOIN-FREED OR LIKE APPARATUS
    • G07F7/00Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
    • G07F7/08Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/02Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/085Payment architectures involving remote charge determination or related payment systems
    • G06Q20/0855Payment architectures involving remote charge determination or related payment systems involving a third party
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/12Payment architectures specially adapted for electronic shopping systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401Transaction verification
    • G06Q20/4016Transaction verification involving fraud or risk level assessment in transaction processing
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/403Solvency checks
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/403Solvency checks
    • G06Q20/4037Remote solvency checks
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02Banking, e.g. interest calculation, credit approval, mortgages, home banking or on-line banking
    • G06Q40/025Credit processing or loan processing, e.g. risk analysis for mortgages

Abstract

A network arrangement is provided for processing credit transactions. A financial network is used to route communications securely between interfaces with the financial network. Merchant systems are coupled with the interfaces, with each merchant system transmitting requests for authorization of credit transactions through the financial network. An issuer system authorizes credit transactions in response to receipt of requests that specify at least a credit account to be used to support a particular credit transaction and a transaction amount for the particular credit transaction. A guarantor system separate from the issuer system determines whether to guarantee credit transactions in response to the requests and transmits responses indicating whether specific credit transactions are to be guaranteed through the financial network to the merchant systems.

Description

    CROSS REFERENCE TO RELATED APPLICATION
  • This application is a nonprovisional of, and claims the benefit of the filing date of, U.S. Provisional Patent Appl. No. 60/566,486, entitled “METHODS AND SYSTEMS FOR PROVIDING GUARANTEED MERCHANT TRANSACTIONS,” filed Apr. 28, 2004 by John Joseph Mascavage et al., the entire disclosure of which is incorporated herein by reference for all purposes.
  • BACKGROUND OF THE INVENTION
  • This application relates generally to merchant transactions. More specifically, this application relates to methods and systems for providing guaranteed merchant transactions.
  • Currently, about 31% of all purchases in the United States are made using payment cards, such as credit, debit, and stored value cards, with the remaining purchases being made in cash (about 38%) and by check (about 27%). Although it is not always evident to many consumers, there is a significant difference in different types of transaction types, in that some transactions are “guaranteed” to the merchant while others are not. As used herein, a “guaranteed” transaction is one in which a merchant is a party to the transaction and in which the risk of loss resulting from successful repudiation is borne by someone other than the merchant party. The most obvious guaranteed transactions are thus those made in cash, where the merchant receives the funds at the time of the purchase directly. Check-based transactions may also be guaranteed transactions when supported by services such as TeleCheck™. With respect to card-based transactions, debit transactions made using a debit card are generally guaranteed transactions because part of the transaction includes a transfer of funds from a customer's account to the merchant's account at the time of the transaction.
  • Credit-card transactions are the prime example of transactions that are not guaranteed. Such transactions typically proceed by having a customer present a credit card, with a receipt of the transaction being presented later by the merchant to a financial institution for payment. Settlement of the transaction involves an issuer of the credit card making the payment and extending credit to the customer, eventually recovering payment for the transaction, and perhaps also a finance charge, from the customer in accordance with a cardholder agreement. Until payment is made to the merchant, however, there remains the possibility that the legitimacy of the transaction may be repudiated, such as by an allegation that the credit card had been stolen, was forged, and the like. The lack of a guarantee thus puts the risk of being defrauded onto the merchant.
  • The protocol for executing transactions sometimes includes safeguards intended to reduce the chance of fraud, but such safeguards are of limited effectiveness. For example, a merchant may seek preauthorization for a transaction by using a network infrastructure to transmit some details of the transaction, such as the credit-card number and a transaction amount, to the issuer. Preauthorization may include verifying that the card number is a valid card number, verifying that the credit account identified by the card number has an open status, and verifying that the credit account has on “open to buy” status on the credit limit. In some instances, such as were an address is provided as part of an address-verification service (“AVS”), the preauthorization may additionally include verifying that the billing address for the credit account matches the address on file for the account holder. Similarly, for certain transactions such as non-face-to-face transactions, a card validation value (“CVV”), often printed on the back of the credit card, may be provided and verified, providing some additional measure of validation that the purchaser is in possession of the card.
  • Thus, if the transaction amount is less than the available credit on the account and the card has no derogatory marks indicating its theft and the like, the transaction may be authorized. Such authorization does not necessarily protect the merchant, however, from presentment of a stolen credit card whose theft has not been reported, or from a variety of other fraud schemes. Legitimate bases may be asserted by the true cardholder to establish that the use of the card was fraudulent, with the risk of such an assertion for every transaction being borne by the merchant. For this reason, some merchants may refuse to accept credit cards or may institute procedures to encourage the use of debit cards over credit cards, but such activities sometimes have the effect of discouraging consumers from purchasing at all from those merchants.
  • In recent years, dangers of fraud perpetrated on merchants have received even more attention because of the evolution of electronic commerce on the Internet, the increase in mail-order and telephone-order transactions, and the like. Such transactions are examples of transactions where the credit card itself is not even presented, and in this way are similar to more traditional telephone and mail-order purchases. A typical electronic transaction proceeds similarly to the transaction described above, but the credit-account number is provided by the customer rather than being extracted directly from the card. Confirmatory information, such as cardholder name, expiry date, and/or identification of a security code printed on the back of the credit card, may sometimes also be collected to try to limit transactions to being executed by the cardholder in possession of the card. A somewhat more sophisticated version of the security-code method has recently been proposed by allowing cardholders to register their cards with a secret password that is not printed on the card. With such a system, registered credit accounts may only be used when the secret password is also provided at the time of transaction. One such method is currently being promoted under the name “Verified by Visa.” While such techniques have the potential of adding greater security to online transactions, they require special registration by the customer and the maintenance of the secret password. In addition, the “Verified by Visa” method currently covers only a small set of chargeback reason codes (two codes), leaving a large number of other potential chargeback codes unaddressed.
  • There accordingly remains a general need in the art for methods and systems that provide convenient guaranteed transactions to merchants for credit transactions.
  • BRIEF SUMMARY OF THE INVENTION
  • Embodiments of the invention thus provide a network arrangement that may be used for processing credit transactions. A financial network is used to route communications securely between interfaces with the financial network. A plurality of merchant systems are coupled with the interfaces, with each such merchant system being adapted to transmit requests for authorization of credit transactions through the financial network. An issuer system is coupled with at least one of the interfaces, and is adapted to authorize credit transactions in response to receipt of requests that specify at least a credit account to be used to support a particular credit transaction and a transaction amount for the particular credit transaction. A guarantor system separate from the issuer system is also coupled with at least one of the interfaces. The guarantor system is adapted to determine whether to guarantee credit transactions in response to the requests for authorization of credit transactions and to transmit responses indicating whether specific credit transactions are to be guaranteed through the financial network to the merchant systems.
  • In some embodiments, each merchant system may be adapted to transmit the requests for authorization through the financial network to the issuer system. In other embodiments, the network arrangement further comprises a merchant-bank system coupled with at least one of the interfaces; the merchant-bank system is controlled by a financial institution that holds a depository account on behalf of a merchant that controls at least one of the merchant systems. The merchant systems may be interfaced with point-of-sale devices adapted to read information defining the credit account from a credit card. Alternatively, the merchant systems may be interfaced with a public network through which a customer may provide information defining the credit account.
  • The network arrangement may be used in methods for processing a credit transaction by a merchant. In one set of embodiments, information defining a credit account to be used to support the credit transaction is received with a merchant system. A request for authorization of the credit transaction is transmitted with the merchant system over a financial network; the request includes the information defining the credit account and a transaction amount for the transaction. A response to the request is received with the merchant system over the financial network. The response identifies whether an issuer of the credit account has authorized the credit transaction and whether a guarantor separate from the issuer has guaranteed payment of the transaction amount for the transaction to the merchant.
  • In some such embodiments, the response may be received from a guarantor system controlled by the guarantor. In other embodiments, a first portion of the response may be received from an issuer system controlled by the issuer and a second portion of the response may be received from a guarantor system controlled by the guarantor. The information defining the credit account may be read from a credit card presented to the merchant or may be received over an interface to the merchant system from a customer located remotely from the merchant in different embodiments. In one embodiment, the request for authorization of the credit transaction is transmitted from the merchant system to an issuer system controlled by the issuer.
  • In another set of embodiments, a request for authorization of a credit transaction between the merchant and a customer is received with a guarantor system. The request includes an identification of a credit account used to support the credit transaction, a transaction amount for the transaction, and an authorization for the transaction provided by an issuer of the credit account. A determination is made with the guarantor system whether to provide a guarantee of payment of the transaction amount to the merchant. A response to the request is transmitted from the guarantor system over a financial network indicating whether to guarantee payment of the transaction amount to the merchant.
  • In some such embodiments, the determination of whether to provide the guarantee is made by determining a risk of repudiation of the transaction by a holder of the credit account. The request for authorization may be received over the financial network from an issuer system controlled by the issuer or from a merchant system controlled by the merchant in different embodiments.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • A further understanding of the nature and advantages of the present invention may be realized by reference to the remaining portions of the specification and the drawings wherein like reference numerals are used throughout the several drawings to refer to similar components. In some instances, a sublabel is associated with a reference numeral and follows a hyphen to denote one of multiple similar components. When reference is made to a reference numeral without specification to an existing sublabel, it is intended to refer to all such multiple similar components.
  • FIG. 1 is a schematic diagram of a network arrangement that may be used in some embodiments of the invention;
  • FIG. 2 is a schematic diagram illustrating a logical structure of a guarantor system that may be used in executing and settling guaranteed credit transactions in some embodiments;
  • FIG. 3 is a schematic illustration of a physical structure of a guarantor system that may be used in executing and settling guaranteed credit transactions in some embodiments;
  • FIG. 4 is a flow diagram providing exemplary illustrations of methods for executing a guaranteed credit transaction in some embodiments; and
  • FIG. 5 is a flow diagram providing exemplary illustrations of methods for settling a guaranteed credit transaction in some embodiments.
  • DETAILED DESCRIPTION OF THE INVENTION
  • Embodiments of the invention provide methods and systems for providing guaranteed credit transactions, where the “guaranteed” nature of each transaction means that the risk of a valid repudiation of the transaction is borne by a party other than a merchant party to the transaction. This is achieved in embodiments of the invention by integrating a guarantor system within a network suitable for processing credit transactions with merchants. The guarantor system is equipped with modules that permit enhanced authorization techniques to be applied with a variety of risk filters so that the guarantor can determine whether to provide the guarantee. In exchange for the guarantee, the guarantor usually receives a small fee from the merchant, effectively providing a cost-based insurance to the merchant. The guarantor system may also be equipped with modules that improve adjudication of repudiations of transactions before payment is made on the guarantee.
  • One example of a network arrangement in which a guarantor system has been integrated in accordance with embodiments of the invention is shown with the schematic diagram of FIG. 1. In this arrangement 100, a plurality of merchant systems 116 are provided in communication with a financial network 112. Usually the financial network is a private network having a variety of security protocols intended to protect the sensitive financial information being exchanged from interception by eavesdroppers. In many instances, for example, communications with the financial network 112 are encrypted. Each of the merchant systems 116 is generally also provided in communication with one or more transaction interfaces. In the case of brick-and-mortar transactions executed when a customer is physically present at a merchant location, the transaction interface may comprise a point-of-sale device 120 equipped to read information from a magnetic stripe of a card, to read information from a chip on a smart card, to read information optically from a card, and the like. Examples of point-of-sale devices that include multiple functionality are described in the following commonly assigned applications, the entire disclosures of which are incorporated herein by reference for all purposes: U.S. Prov. Pat. Appl. No. 60/147,889, entitled “INTEGRATED POINT OF SALE DEVICE,” filed Aug. 9, 1999 by Randy J. Templeton et al.; U.S. Patent Application Ser. No. 09/634,901, entitled “POINT OF SALE PAYMENT SYSTEM,” filed Aug. 9, 2000 by Randy J. Templeton et al.; U.S. Patent Application Ser. No. 10/116,689, entitled “SYSTEMS AND METHODS FOR PERFORMING TRANSACTIONS AT A POINT-OF-SALE,” filed Apr. 3, 2002 by Earney Stoutenburg et al.; U.S. Patent Application Ser. No. 10/116,733, entitled “SYSTEMS AND METHODS FOR DEPLOYING A POINT-OF-SALE SYSTEM,” filed Apr. 3, 2002 by Earney Stoutenburg et al.; U.S. Patent Application Ser. No. 10/116,686, entitled “SYSTEMS AND METHODS FOR UTILIZING A POINT-OF-SALE SYSTEM,” filed Apr. 3, 2002 by Earney Stoutenburg et al.; and U.S. Patent Application Ser. No. 10/116,735, entitled “SYSTEMS AND METHODS FOR CONFIGURING A POINT-OF-SALE SYSTEM,” filed Apr. 3, 2002 by Earney Stoutenburg. In cases where the customer is not physically present, such as where a transaction is executed over a public network 124 like the Internet, the public network 124 itself may correspond to the transaction interface. Other examples of transaction interfaces that may be used when the customer is not physically present include telephone interfaces used to support telephone orders, and the like.
  • FIG. 1 provides examples of different types of merchants who may be equipped to accommodate different types of transactions. For instance, the merchant having merchant system 116-n is equipped only to accommodate brick-and-mortar transactions with a customer 128-3 through a point-of-sale transaction device 120. Transactions executed by such a merchant are thus restricted to “card-present transactions,” in which the credit card is physically present for examination during the transaction itself. In contrast, the merchant having merchant system 116-2 is a purely online Internet retailer and is equipped only to accommodate transactions executed over the public network 124. In such transactions, a customer 128-2 provides only information about the credit card without the card actually being present to execute a so-called “card-not-present transaction.” Some merchant systems, such as merchant system 116-1 may be equipped to interface with different types of transaction interfaces, such as with the public network 124 and with point-of-sale devices 120. Such merchant systems may accommodate a customer 128-1 who executes a card-present transaction at a merchant location, as well as a customer 128-2 who executes a card-not-present transaction over the Internet or telephone.
  • The financial network 112 is also interfaced with financial-institution systems 104 operated by financial institutions. Such financial institutions may act as depository institutions that provide services to one or more of the merchants and/or may act as issuers of credit cards to customers 128. To facilitate the discussion below, a specific embodiment is indicated in FIG. 1 in which financial-institution system 104-2 is operated by a merchant bank that provides services to one of the merchants, and in which financial-institution 104-1 is operated by a credit-card issuer that provides a credit account for one of the customers 128. Of course, both those institutions may act in other capacities as well, with the merchant bank also acting as an issuer to some customers and with the issuer acting as a merchant bank for other customers.
  • The guarantor system 108 is integrated into this network arrangement through an interface with the financial network 112, allowing it to exchange communications both with the merchant systems 116 and with the financial-institution systems 104. The guarantor system 108 may comprise a computational system having programming to implement methods for guaranteeing transactions and for settling guaranteed transactions. Such a computational system is described for certain embodiments with reference to FIGS. 2 and 3, which respectively show logical and physical structures that may be used in some embodiments.
  • For instance, FIG. 2 illustrates that the guarantor system 108 may comprise a plurality of logical modules for implementing methods of the invention. The modules on the left side of the drawing generally correspond to those modules that may be used in coordinating execution of guaranteed transaction, while the modules on the right side of the drawing generally correspond to those modules used in settling a previously guaranteed transaction.
  • In coordinating execution of a guaranteed transaction, information about the transaction may be received by a transaction-receipt module 212 over a first input interface 204. The information is parsed by a transaction-parsing module 216 so that the parsed information may be analyzed for risk factors by a risk-evaluation module 220. The risk-evaluation module may comprise one or more risk filters used in evaluating the risk of repudiation of a transaction. For example, a demographic filter 220 may apply demographic factors like age, occupation, income level, geographic location, and the like that are known to be correlated with relatively high or low levels of repudiation. Similarly, a transaction filter 228 may identify certain aspects of the transaction that are known to be correlated with relatively high or low levels of repudiation, such as the transaction amount, the nature of the product purchased, the type of merchant selling the product, the frequency of the transaction, the time of day of the transaction, hardware- and software-related parameters such as fingerprinting-type information captured by certain scanners, and the like. Of each of the factors may be used in the computation of a risk score, with those aspects correlated with high levels of repudiation tending to increase the score and those with aspects correlated with low levels of repudiation tending to decrease the score. Different aspects may be weighted in different ways by the risk-evaluation module, and the weighting factors may even vary on a transaction-by-transaction basis. For example, a transaction by Customer X known to have a history of repudiating transactions may weight those factors tending to decrease the risk score more heavily than for a transaction by Customer Y known rarely to repudiate a transaction. The application of the various filters may draw on information stored in a data store 236, that may record such information as the correlation levels with identified demographic, transactional, and other factors, a credit score or transaction history for individual customers, and the like.
  • Once the risk-evaluation module has generated a risk score for a particular transaction, a guarantee module 232 determines whether the transaction qualifies for a guarantee by the guarantor. In some instances, such a determination may be made simply on the basis of the risk score alone, while in other embodiments other factors may also be applied. The determination of the guarantee module 232 is routed as a response from the guarantor system 108 by a routing module 246 over output interface 250.
  • Similarly, as part of a method for settling a guaranteed transaction, a repudiation-receipt module 240 may receive information over a second input interface 208 that a particular guaranteed transaction has been repudiated by the cardholder. Generally, this information includes details of the transaction and reasons for the repudiation, and perhaps also detailed results of an investigation performed by an issuer suggesting that the repudiation is valid. An adjudication module 242 coordinates activity for determining whether the guarantor is obliged to pay the merchant for the repudiated transaction. In doing so, the adjudication module may access information from the data store 236. In some instances the adjudication may rely completely on the information received by the repudiation-receipt module 240, such as by honoring a conclusion of an issuer that the transaction was legitimately repudiated. In other instances, an independent adjudication may be initiated by the adjudication module 242 by issuing directions for collection of additional information, to verify an identity of the party to the transaction, address, and other factors known to be correlated with a fraud technique. Results of such investigations are received by the adjudication module 242, which determines the legitimacy of the repudiation and maintains records sufficient to establish the basis for its determination; maintaining such records is especially desired in circumstances where the repudiation is determined to be invalid so that the guarantor will refuse to pay. The determination is provided to the routing module 246 for transmission to appropriate parties as described below.
  • FIG. 3 provides a schematic illustration of a physical structure that may be used to implement the guarantor system 108. FIG. 3 broadly illustrates how individual system elements may be implemented in a separated or more integrated manner. The guarantor system 108 is shown comprised of hardware elements that are electrically coupled via bus 326, including a processor 302, an input device 304, an output device 306, the data store 236, a computer-readable storage media reader 310 a, a communications system 314, a processing acceleration unit 316 such as a DSP or special-purpose processor, and a memory 318. The computer-readable storage media reader 310 a is further connected to a computer-readable storage medium 310 b, the combination comprehensively representing remote, local, fixed, and/or removable storage devices plus storage media for temporarily and/or more permanently containing computer-readable information. The communications system 314 may comprise a wired, wireless, modem, and/or other type of interfacing connection and permits data to be exchanged over input interfaces 204 and 208 and over output interface 250 to implement embodiments described herein.
  • The guarantor system 108 also comprises software elements, shown as being currently located within working memory 320, including an operating system 324 and other code 322, such as a program designed to implement methods of the invention. It will be apparent to those skilled in the art that substantial variations may be made in accordance with specific requirements. For example, customized hardware might also be used and/or particular elements might be implemented in hardware, software (including portable software, such as applets), or both. Further, connection to other computing devices such as network input/output devices may be employed.
  • FIGS. 4 and 5 provide flow diagrams that respectively illustrate methods for executing a guaranteed transaction and methods for settling a guaranteed transaction using the network arrangement 100 described in connection with FIGS. 1-3. As FIG. 4 illustrates, methods of the invention may accommodate both card-present transactions and card-not-present transactions. In the case of a card-present transaction, a customer may select items, including goods and/or services, for purchase at a merchant location at block 404. The customer presents his credit card for reading by the point-of-sale device, which extracts an account number and perhaps other identification from a magnetic stripe, embedded chip, or other storage medium at block 408. A package having transaction information is prepared, including such information as the account number and identification extracted from the credit card, a transaction amount, a listing of items purchased, and the like. The transaction package is transmitted by a merchant system 116 interfaced with the point-of-sale device over the financial network 112 to the merchant-bank system 104-2. Alternatively, in the case of a card-not-present transaction, a customer may select items for purchase from an online Internet shopping site at block 412. The customer communicates identification information printed on the credit card, such as the credit-card number, his name, and the expiration date, at block 416 over an interface connected with a merchant system 116. In the case of an online purchase, the interface may comprise the Internet and in the alternative case of a catalog purchase, the interface may comprise a telephone interface. At block 420, transaction information is prepared in the same fashion as for a card-present transaction, i.e. by preparing a packet having such information as account number, transaction amount, items purchased, and the like, and transmitted over the financial network 112 to the merchant-bank system 104-2.
  • For both card-present and card-not-present transactions, the merchant-bank system 104-2 identifies the issuer from the received information and routes it or a subset of it to the appropriate issuer system 104-1 over the financial network 112 at block 424. The information thus provided to the issuer system 104-3 permits the issuer system 104-1 to determine at block 428 whether to authorize the transaction in accordance with a cardholder agreement between the issuer and cardholder. Such a decision typically turns on such factors as whether the transaction amount is less than an available credit amount and whether the credit account is free of derogatory marks that indicate such things as delinquency on the part of the cardholder, unusual levels of activity on the account (particularly in unusual geographic locations) suggesting fraudulent activity, and the like. If the transaction is denied by the issuer, a denial code is routed by the issuer system 104-1 through the financial network 112 to the merchant system 116 that originated the transaction at block 432. Normally, the merchant will decline the credit transaction upon receipt of a denial code or will allow the customer to provide an alternative method of payment for the selected items.
  • If the issuer authorizes the transaction, the transaction information may be routed through the financial network 112 to the guarantor system 108 at block 436, together with an approval code generated by the issuer system 104-1. Using the methods described above, the guarantor system 108 evaluates risk factors at block 440 to determine whether the transaction is one that meets criteria for providing a guarantee. In some instances, the cost for providing a guarantee of the transaction may vary according to the determined risk level, so that the possibility of obtaining a guarantee is still provided to the merchant, but at a cost that reflects the increased risk. The guarantor system 108 transmits the transaction authorization together with its guarantee decision to the merchant system 116 that originated the transaction request at block 444. If the transaction is guaranteed under conditions acceptable to the merchant, as checked at block 448, the merchant executes the transaction at block 452. If the guarantor is unwilling to guarantee the transaction, or if the guarantee is offered under conditions unacceptable to the merchant, the merchant may still have the option of accepting the risk of loss at block 456 using internal decision-making criteria. Since the transaction has been authorized by the issuer despite the lack of guarantee, a decision by the merchant to execute the transaction and accept the risk is similar to execution of a traditional authorized credit transaction. In many instances, however, the risk evaluation performed by the guarantor system 108 will be recognized by the merchant to be a reliable indicator of risk levels so that the merchant will decline to execute the transaction in the absence of a guarantee.
  • While FIG. 4 indicates one specific order for the routing of transaction information, it should be appreciated that other routings may be performed without exceeding the scope of the invention. For example, in some embodiments, the transaction information may not be routed to the merchant-bank system initially, being instead routed directly from the merchant system to the issuer system. In other embodiments, transaction information may be routed to the issuer system and guarantor system simultaneously, with a transaction being executed only if a positive response is received from both; such simultaneous routing may increase the speed of executing a transaction, but requires the risk-analysis techniques used by the guarantor system 108 to be applied even for transactions that are denied by the issuer system. Still other variations in the order of the functions included in FIG. 4 will be evident to those of skill in the art, as will be functions that may be omitted in some embodiments and supplementary functions that may be performed in some embodiments.
  • After a guaranteed transaction has been executed, it may be settled so that the appropriate parties pay and are paid for the transaction in accordance with the relevant agreements. FIG. 5 provides an overview of settlement functions in some embodiments, although, as for the methods described in connection with FIG. 4, various additional functions may be performed in some embodiments, various functions may be omitted in some embodiments, and various functions may be performed in a different order in some embodiments. Settlement of a particular transaction may begin at block 504 with the merchant depositing a receipt of the transaction with its financial institution, the merchant bark 104-2. At block 508, the merchant bank 104-2 transmits an electronic version of the transaction receipt to the issuer system 104-1 over the financial network 112. This electronic version might include an image reproduction of the transaction receipt or might be comprise descriptive text setting forth relevant particulars of the transaction receipt.
  • At block 512, the issuer system 104-1 posts the transaction to the cardholder's account and later transmits a credit-card statement to the cardholder at block 516 that includes the transaction, and usually several additional transactions executed within a defined period. Under most circumstances, all of the transactions set forth on the cardholder statement will be accepted by the cardholder as legitimate charges, as checked at block 520, so that the cardholder will provide payment towards the outstanding balance of the credit account by a specified due date at block 552. The issuer system 104-1 accordingly initiates transmission of the transaction amount to the merchant bank 104-2 at block 556, and the merchant bank 104-2 credits the merchant account at block 560. While transmission of funds to the merchant bank 104-2 and crediting of the merchant account are shown in FIG. 5 to occur after the cardholder has reviewed his statement, in many instances such crediting will occur much earlier in the process. When such crediting is performed earlier, a successful repudiation of the transaction by the cardholder may require a refund if the transaction was not guaranteed; it is thus particularly convenient to perform the crediting earlier for at least all guaranteed transactions, and even for some nonguaranteed transactions since most of those will not be repudiated in any event.
  • If the transaction is repudiated by the cardholder at block 520, usually by the cardholder informing the issuer that the transaction was not executed by the cardholder or authorized by the cardholder, the issuer will investigate the repudiation at block 524. Such an investigation may be performed at a relatively high level, checking such things as the account number on the transaction receipt, checking the signature on the transaction receipt, and the like, or may be performed at a more detailed level in some embodiments. If the investigation results in a determination that the repudiation is not valid, as checked at block 528, the issuer may demand payment from the cardholder at block 532, with the expectation that the cardholder will pay as described previously so that the merchant account may be properly credited. Continued failure of the cardholder to pay for the transaction may result in recovery actions against the cardholder in accordance with the cardholder agreement.
  • If the repudiation is valid, the ability for the merchant to recover the transaction amount depends on whether the transaction was guaranteed. If not, as checked at block 536, then the merchant has been defrauded as indicated at block 564. If the transaction was guaranteed, however, then responsibility for making the merchant whole rests with the guarantor. Accordingly, at block 540, the issuer system 104-1 transmits information to the guarantor system 108 over the financial network 112. This information may include the electronic version of the transaction receipt, details of the repudiation supplied by the cardholder, details of the investigation that was performed by the issuer and the results of that investigation, and the like. This information may then be used by the adjudication modules of the guarantor system 108 to perform an enhanced adjudication at block 544; some discussion of the nature of the enhanced adjudication was presented above in connection with FIG. 2. If the result of that enhanced adjudication confirms the conclusion that the repudiation was valid, as checked at block 548, then the transaction is one of those that the prior risk analysis failed to identify sufficiently well as likely to be repudiated. Accordingly, the guarantor system 108 initiates transmission of the transaction amount to the merchant bank at block 576 so that the merchant bank may credit the merchant account at block 580. Because of the guaranteed nature of the transaction, such transfer of funds is also performed by the guarantor system 108 when the repudiation is found not to be valid by the enhanced adjudication; in addition, however, the guarantor takes steps to recover payment from the cardholder at block 568, with the expectation that the cardholder will pay the guarantor the requisite amount at block 572 when presented with the evidence that the transaction was improperly repudiated.
  • Thus, having described several embodiments, it will be recognized by those of skill in the art that various modifications, alternative constructions, and equivalents may be used without departing from the spirit of the invention. Accordingly, the above description should not be taken as limiting the scope of the invention, which is defined in the following claims.

Claims (15)

1. A method for processing a credit transaction by a merchant, the method comprising:
receiving, with a merchant system, information defining a credit account to be used to support the credit transaction;
transmitting, with the merchant system over a financial network, a request for authorization of the credit transaction, the request including the information defining the credit account and a transaction amount for the transaction; and
receiving, with the merchant system over the financial network, a response to the request identifying whether an issuer of the credit account has authorized the credit transaction and whether a guarantor separate from the issuer has guaranteed payment of the transaction amount for the transaction to the merchant.
2. The method recited in claim 1 wherein receiving the response comprises receiving the response from a guarantor system controlled by the guarantor.
3. The method recited in claim 1 wherein receiving the response comprises receiving a first portion of the response from an issuer system controlled by the issuer and receiving a second portion of the response from a guarantor system controlled by the guarantor.
4. The method recited in claim 1 wherein receiving the information defining the credit account comprises reading the information from a credit card presented to the merchant.
5. The method recited in claim 1 wherein receiving the information defining the credit account comprises receiving the information over an interface to the merchant system from a customer located remotely from the merchant.
6. The method recited in claim 1 wherein transmitting the request comprises transmitting the request from the merchant system to an issuer system controlled by the issuer.
7. A method for processing a credit transaction by a merchant, the method comprising:
receiving, with a guarantor system, a request for authorization of a credit transaction between the merchant and a customer, the request including an identification of a credit account used to support the credit transaction, a transaction amount for the transaction, and an authorization for the transaction provided by an issuer of the credit account;
determining, with the guarantor system, whether to provide a guarantee of payment of the transaction amount to the merchant; and
transmitting, from the guarantor system over a financial network, a response to the request indicating whether to guarantee payment of the transaction amount to the merchant.
8. The method recited in claim 7 wherein determining whether to provide the guarantee comprises determining a risk of repudiation of the transaction by a holder of the credit account.
9. The method recited in claim 7 wherein receiving the request for authorization comprises receiving the request for authorization over the financial network from an issuer system controlled by the issuer.
10. The method recited in claim 7 wherein receiving the request for authorization comprises receiving the request for authorization over the financial network from a merchant system controlled by the merchant.
11. A network arrangement for processing credit transactions between merchants and customers, the network arrangement comprising:
a financial network adapted to route communications securely between interfaces with the financial network;
a plurality of merchant systems coupled with the interfaces, each such merchant system being adapted to transmit requests for authorization of credit transactions through the financial network;
an issuer system coupled with at least one of the interfaces, the issuer system being adapted to authorize credit transactions in response to receipt of requests specifying at least a credit account to be used to support a particular credit transaction and a transaction amount for the particular credit transactions; and
a guarantor system separate from the issuer system and coupled with at least one of the interfaces, the guarantor system being adapted to determine whether to guarantee credit transactions for merchants in response to the requests for authorization of credit transactions and to transmit responses indicating whether specific credit transactions are to be guaranteed through the financial network to the merchant systems.
12. The network arrangement recited in claim 11 wherein each such merchant system is adapted to transmit the requests for authorization through the financial network to the issuer system.
13. The network arrangement recited in claim 11 further comprising a merchant-bank system coupled with at least one of the interfaces, the merchant-bank system being controlled by a financial institution that holds a depository account on behalf of a merchant that controls at least one of the merchant systems.
14. The network arrangement recited in claim 11 wherein at least one the merchant systems is interfaced with a point-of-sale device adapted to read information defining the credit account from a credit card.
15. The network arrangement recited in claim 11 wherein at least one of the merchant systems is interfaced with a public network through which a customer may provide information defining the credit account.
US11/105,167 2004-04-28 2005-04-12 Methods and systems for providing guaranteed merchant transactions Abandoned US20050279827A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US56648604P true 2004-04-28 2004-04-28
US11/105,167 US20050279827A1 (en) 2004-04-28 2005-04-12 Methods and systems for providing guaranteed merchant transactions

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US11/105,167 US20050279827A1 (en) 2004-04-28 2005-04-12 Methods and systems for providing guaranteed merchant transactions
PCT/US2005/013189 WO2005109307A2 (en) 2004-04-28 2005-04-18 Methods and systems for providing guaranteed merchant transactions
EP05737735A EP1747522A4 (en) 2004-04-28 2005-04-18 Methods and systems for providing guaranteed merchant transactions
CA 2563722 CA2563722A1 (en) 2004-04-28 2005-04-18 Methods and systems for providing guaranteed merchant transactions
US11/924,828 US7967195B2 (en) 2004-04-28 2007-10-26 Methods and systems for providing guaranteed merchant transactions

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US11/924,828 Continuation US7967195B2 (en) 2004-04-28 2007-10-26 Methods and systems for providing guaranteed merchant transactions

Publications (1)

Publication Number Publication Date
US20050279827A1 true US20050279827A1 (en) 2005-12-22

Family

ID=35320894

Family Applications (2)

Application Number Title Priority Date Filing Date
US11/105,167 Abandoned US20050279827A1 (en) 2004-04-28 2005-04-12 Methods and systems for providing guaranteed merchant transactions
US11/924,828 Active 2027-08-17 US7967195B2 (en) 2004-04-28 2007-10-26 Methods and systems for providing guaranteed merchant transactions

Family Applications After (1)

Application Number Title Priority Date Filing Date
US11/924,828 Active 2027-08-17 US7967195B2 (en) 2004-04-28 2007-10-26 Methods and systems for providing guaranteed merchant transactions

Country Status (4)

Country Link
US (2) US20050279827A1 (en)
EP (1) EP1747522A4 (en)
CA (1) CA2563722A1 (en)
WO (1) WO2005109307A2 (en)

Cited By (82)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060144927A1 (en) * 2005-01-06 2006-07-06 First Data Corporation Identity verification systems and methods
US20070012757A1 (en) * 2005-07-14 2007-01-18 First Data Corporation Identity verification switch
US20070233603A1 (en) * 2006-03-30 2007-10-04 Schmidgall Matthew M Flexible routing of electronic-based transactions
US7328844B2 (en) * 2002-01-17 2008-02-12 Darwin Innovations Corporation Point-of-transaction machine with improved versatility and related method
US20080052235A1 (en) * 2004-04-28 2008-02-28 First Data Corporation Methods And Systems For Providing Guaranteed Merchant Transactions
US7822209B2 (en) 2006-06-06 2010-10-26 Red Hat, Inc. Methods and systems for key recovery for a token
US20100332381A1 (en) * 2007-05-25 2010-12-30 Celka Christopher J System and method for automated detection of never-pay data sets
US7962418B1 (en) * 2007-03-30 2011-06-14 Amazon Technologies, Inc. System and method of fulfilling a transaction
US7992203B2 (en) 2006-05-24 2011-08-02 Red Hat, Inc. Methods and systems for secure shared smartcard access
US8074265B2 (en) 2006-08-31 2011-12-06 Red Hat, Inc. Methods and systems for verifying a location factor associated with a token
US8098829B2 (en) 2006-06-06 2012-01-17 Red Hat, Inc. Methods and systems for secure key delivery
US8099765B2 (en) 2006-06-07 2012-01-17 Red Hat, Inc. Methods and systems for remote password reset using an authentication credential managed by a third party
US8176564B2 (en) 2004-11-15 2012-05-08 Microsoft Corporation Special PC mode entered upon detection of undesired state
US8180741B2 (en) 2006-06-06 2012-05-15 Red Hat, Inc. Methods and systems for providing data objects on a token
US20120266227A1 (en) * 2006-10-10 2012-10-18 Equifax Inc. Verification and authentication systems and methods
US8332637B2 (en) 2006-06-06 2012-12-11 Red Hat, Inc. Methods and systems for nonce generation in a token
US20120317019A1 (en) * 2011-05-26 2012-12-13 First Data Corporation Card-Present On-Line Transactions
US8336085B2 (en) * 2004-11-15 2012-12-18 Microsoft Corporation Tuning product policy using observed evidence of customer behavior
US8347078B2 (en) 2004-10-18 2013-01-01 Microsoft Corporation Device certificate individualization
US8353046B2 (en) 2005-06-08 2013-01-08 Microsoft Corporation System and method for delivery of a modular operating system
US8356342B2 (en) * 2006-08-31 2013-01-15 Red Hat, Inc. Method and system for issuing a kill sequence for a token
US8364952B2 (en) 2006-06-06 2013-01-29 Red Hat, Inc. Methods and system for a key recovery plan
US8376225B1 (en) * 2007-04-26 2013-02-19 United Services Automobile Association (Usaa) Secure card
US8412927B2 (en) 2006-06-07 2013-04-02 Red Hat, Inc. Profile framework for token processing system
US8438645B2 (en) 2005-04-27 2013-05-07 Microsoft Corporation Secure clock with grace periods
US8464348B2 (en) 2004-11-15 2013-06-11 Microsoft Corporation Isolated computing environment anchored into CPU and motherboard
US8495380B2 (en) 2006-06-06 2013-07-23 Red Hat, Inc. Methods and systems for server-side key generation
US8589695B2 (en) 2006-06-07 2013-11-19 Red Hat, Inc. Methods and systems for entropy collection for server-side key generation
US8595101B1 (en) 2008-09-08 2013-11-26 Exerian Information Solutions, Inc. Systems and methods for managing consumer accounts using data migration
US8622292B2 (en) * 2005-09-29 2014-01-07 Jeffrey Bart Katz Reservation-based preauthorization payment system
US8639940B2 (en) 2007-02-28 2014-01-28 Red Hat, Inc. Methods and systems for assigning roles on a token
US8693690B2 (en) 2006-12-04 2014-04-08 Red Hat, Inc. Organizing an extensible table for storing cryptographic objects
US8700535B2 (en) 2003-02-25 2014-04-15 Microsoft Corporation Issuing a publisher use license off-line in a digital rights management (DRM) system
US8707024B2 (en) 2006-06-07 2014-04-22 Red Hat, Inc. Methods and systems for managing identity management security domains
US8725646B2 (en) 2005-04-15 2014-05-13 Microsoft Corporation Output protection levels
US8775299B2 (en) 2011-07-12 2014-07-08 Experian Information Solutions, Inc. Systems and methods for large-scale credit data processing
US8781953B2 (en) 2003-03-21 2014-07-15 Consumerinfo.Com, Inc. Card management system and method
US8781969B2 (en) 2005-05-20 2014-07-15 Microsoft Corporation Extensible media rights
US8787566B2 (en) 2006-08-23 2014-07-22 Red Hat, Inc. Strong encryption
US8806219B2 (en) 2006-08-23 2014-08-12 Red Hat, Inc. Time-based function back-off
US8813243B2 (en) 2007-02-02 2014-08-19 Red Hat, Inc. Reducing a size of a security-related data object stored on a token
US8832453B2 (en) 2007-02-28 2014-09-09 Red Hat, Inc. Token recycling
US8856894B1 (en) 2012-11-28 2014-10-07 Consumerinfo.Com, Inc. Always on authentication
US8930251B2 (en) 2008-06-18 2015-01-06 Consumerinfo.Com, Inc. Debt trending systems and methods
US8977844B2 (en) 2006-08-31 2015-03-10 Red Hat, Inc. Smartcard formation with authentication keys
US20150088613A1 (en) * 2013-09-23 2015-03-26 Comdata Network, Inc. Systems, methods, and computer program products for managing fuel costs
US9004355B2 (en) 2005-09-29 2015-04-14 Cardfree Inc Secure system and method to pay for a service provided at a reservation
US20150120555A1 (en) * 2013-10-29 2015-04-30 Elwha Llc Exchange authorization analysis infused with network-acquired data stream information
US20150120440A1 (en) * 2013-10-29 2015-04-30 Elwha LLC, a limited liability corporation of the State of Delaware Guaranty provisioning via internetworking
US20150120473A1 (en) * 2013-10-29 2015-04-30 Elwha LLC, a limited liability corporation of the State of Delaware Vendor-facilitated guaranty provisioning
US20150120502A1 (en) * 2013-10-29 2015-04-30 Elwha LLC, a limited liability corporation of the State of Delaware Supporting guaranty provisioning via user attribute proffering
US20150120550A1 (en) * 2013-10-29 2015-04-30 Elwha LLC, a limited liability corporation of the State of Delaware Guaranty provisioning via wireless service purveyance
US20150120500A1 (en) * 2013-10-29 2015-04-30 Elwha LLC, a limited liability corporation of the State of Delaware Facilitating guaranty provisioning for an exchange
US9038154B2 (en) 2006-08-31 2015-05-19 Red Hat, Inc. Token Registration
US9058627B1 (en) 2002-05-30 2015-06-16 Consumerinfo.Com, Inc. Circular rotational interface for display of consumer credit information
US9081948B2 (en) 2007-03-13 2015-07-14 Red Hat, Inc. Configurable smartcard
US20150199738A1 (en) * 2014-01-14 2015-07-16 Elwha Llc Guaranty investigation
US9147042B1 (en) 2010-11-22 2015-09-29 Experian Information Solutions, Inc. Systems and methods for data verification
US9189605B2 (en) 2005-04-22 2015-11-17 Microsoft Technology Licensing, Llc Protected computing environment
US9230283B1 (en) 2007-12-14 2016-01-05 Consumerinfo.Com, Inc. Card registry systems and methods
US9256904B1 (en) 2008-08-14 2016-02-09 Experian Information Solutions, Inc. Multi-bureau credit file freeze and unfreeze
US9363481B2 (en) 2005-04-22 2016-06-07 Microsoft Technology Licensing, Llc Protected media pipeline
USD759689S1 (en) 2014-03-25 2016-06-21 Consumerinfo.Com, Inc. Display screen or portion thereof with graphical user interface
USD759690S1 (en) 2014-03-25 2016-06-21 Consumerinfo.Com, Inc. Display screen or portion thereof with graphical user interface
USD760256S1 (en) 2014-03-25 2016-06-28 Consumerinfo.Com, Inc. Display screen or portion thereof with graphical user interface
US9436804B2 (en) 2005-04-22 2016-09-06 Microsoft Technology Licensing, Llc Establishing a unique session key using a hardware functionality scan
US9558519B1 (en) 2011-04-29 2017-01-31 Consumerinfo.Com, Inc. Exposing reporting cycle information
US9563916B1 (en) 2006-10-05 2017-02-07 Experian Information Solutions, Inc. System and method for generating a finance attribute from tradeline data
US9576030B1 (en) 2014-05-07 2017-02-21 Consumerinfo.Com, Inc. Keeping up with the joneses
US9595051B2 (en) 2009-05-11 2017-03-14 Experian Marketing Solutions, Inc. Systems and methods for providing anonymized user profile data
US9607336B1 (en) 2011-06-16 2017-03-28 Consumerinfo.Com, Inc. Providing credit inquiry alerts
US9652802B1 (en) 2010-03-24 2017-05-16 Consumerinfo.Com, Inc. Indirect monitoring and reporting of a user's credit data
US9690820B1 (en) 2007-09-27 2017-06-27 Experian Information Solutions, Inc. Database system for triggering event notifications based on updates to database records
US9697263B1 (en) 2013-03-04 2017-07-04 Experian Information Solutions, Inc. Consumer data request fulfillment system
US9710852B1 (en) 2002-05-30 2017-07-18 Consumerinfo.Com, Inc. Credit report timeline user interface
US9769158B2 (en) 2006-06-07 2017-09-19 Red Hat, Inc. Guided enrollment and login for token users
US9830646B1 (en) 2012-11-30 2017-11-28 Consumerinfo.Com, Inc. Credit score goals and alerts systems and methods
US10102536B1 (en) 2013-11-15 2018-10-16 Experian Information Solutions, Inc. Micro-geographic aggregation system
US10157407B2 (en) 2013-10-29 2018-12-18 Elwha Llc Financier-facilitated guaranty provisioning
US10242019B1 (en) 2014-12-19 2019-03-26 Experian Information Solutions, Inc. User behavior segmentation using latent topic detection
US10255598B1 (en) 2012-12-06 2019-04-09 Consumerinfo.Com, Inc. Credit card account data extraction
US10262364B2 (en) 2007-12-14 2019-04-16 Consumerinfo.Com, Inc. Card registry systems and methods

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060235758A1 (en) * 2005-04-08 2006-10-19 Paypal Inc. Authorization techniques
US20100106534A1 (en) * 2008-10-24 2010-04-29 Solid People Llc Certification and risk-management system and method for a rental agreement
US20110035294A1 (en) * 2009-08-04 2011-02-10 Authernative, Inc. Multi-tier transaction processing method and payment system in m- and e- commerce
WO2011103520A1 (en) * 2010-02-18 2011-08-25 Bling Nation, Ltd. Automated transaction system and settlement processes
US8463661B2 (en) 2011-10-26 2013-06-11 Fragmob, Llc Credit card authorization process for direct sales system employing networked mobile computing devices

Citations (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5334823A (en) * 1992-01-10 1994-08-02 National Bancard Corporation Systems and methods for operating data card terminals for transaction chargeback protection
US5428210A (en) * 1992-01-10 1995-06-27 National Bancard Corporation Data card terminal with embossed character reader and signature capture
US5448047A (en) * 1992-10-30 1995-09-05 Microbilt Corporation Card validation method using multiple cord data regions
US5903882A (en) * 1996-12-13 1999-05-11 Certco, Llc Reliance server for electronic transaction system
US5914472A (en) * 1997-09-23 1999-06-22 At&T Corp Credit card spending authorization control system
US6163771A (en) * 1997-08-28 2000-12-19 Walker Digital, Llc Method and device for generating a single-use financial account number
US6254000B1 (en) * 1998-11-13 2001-07-03 First Data Corporation System and method for providing a card transaction authorization fraud warning
US20010034720A1 (en) * 2000-03-07 2001-10-25 David Armes System for facilitating a transaction
US20010034702A1 (en) * 2000-02-04 2001-10-25 Mockett Gregory P. System and method for dynamically issuing and processing transaction specific digital credit or debit cards
US20020013765A1 (en) * 2000-05-23 2002-01-31 Gil Shwartz Intrinsic authorization for electronic transactions
US20020120582A1 (en) * 2001-02-26 2002-08-29 Stephen Elston Method for establishing an electronic commerce account
US20020123938A1 (en) * 2001-03-01 2002-09-05 Yu Philip S. Systems and methods to facilitate a transaction wherein a purchaser is associated with an approver
US20020139837A1 (en) * 2001-03-12 2002-10-03 Spitz Clayton P. Purchasing card transaction risk model
US20030046224A1 (en) * 2001-08-30 2003-03-06 Mujtaba M. Shahid Method and apparatus for handling monetary transactions
US20030083986A1 (en) * 2000-08-15 2003-05-01 Toshiaki Kobayashi Method of credit guarantee in electronic commerce
US20030093367A1 (en) * 2001-11-15 2003-05-15 First Data Corporation Online incremental payment method
US20030101134A1 (en) * 2001-11-28 2003-05-29 Liu James C. Method and system for trusted transaction approval
US20030126075A1 (en) * 2001-11-15 2003-07-03 First Data Corporation Online funds transfer method
US20030172027A1 (en) * 2001-03-23 2003-09-11 Scott Walter G. Method for conducting a credit transaction using biometric information
US20030233292A1 (en) * 2002-06-13 2003-12-18 Visa U.S.A., Inc. Method and system for facilitating electronic dispute resolution
US20040030644A1 (en) * 2001-12-14 2004-02-12 Shaper Stephen J. Systems for facilitating card processing systems/improved risk control
US20040031856A1 (en) * 1998-09-16 2004-02-19 Alon Atsmon Physical presence digital authentication system
US20040049455A1 (en) * 2001-07-06 2004-03-11 Hossein Mohsenzadeh Secure authentication and payment system
US20040064405A1 (en) * 2002-09-30 2004-04-01 First Data Corporation Methods and systems for processing partial payments using debit cards
US20040199462A1 (en) * 2003-04-02 2004-10-07 Ed Starrs Fraud control method and system for network transactions
US20040230527A1 (en) * 2003-04-29 2004-11-18 First Data Corporation Authentication for online money transfers
US20040260644A1 (en) * 2003-04-23 2004-12-23 Robert Doerner Credit authorization systems and methods
US20050131816A1 (en) * 1999-05-14 2005-06-16 Britto Mark J. Computer-based funds transfer system
US20050192901A1 (en) * 2003-06-30 2005-09-01 Mccoy Randal A. Credit card supported electronic payments
US20050234833A1 (en) * 2004-04-16 2005-10-20 First Data Corporation Methods and systems for online transaction processing
US20050278244A1 (en) * 2000-02-22 2005-12-15 Yuan Frank S Auction with methods and mechanisms to avoid fraud
US20060016880A1 (en) * 2004-07-20 2006-01-26 Irek Singer Wireless payment processing system
US20060026097A1 (en) * 2004-07-30 2006-02-02 Kagi, Inc. Method and apparatus for verifying a financial instrument
US20060031161A1 (en) * 1999-01-15 2006-02-09 D Agostino John System and method for performing secure credit card purchases
US6999943B1 (en) * 2000-03-10 2006-02-14 Doublecredit.Com, Inc. Routing methods and systems for increasing payment transaction volume and profitability
US7043441B1 (en) * 1997-10-01 2006-05-09 At&T Corp. Method and apparatus using digital credentials and other electronic certificates for electronic transactions
US20060143121A1 (en) * 1998-11-23 2006-06-29 Treider Kevin C Electronic factoring
US20060229961A1 (en) * 2005-04-08 2006-10-12 Efunds Corporation Risk evaluation method and system using ACH data
US7191151B1 (en) * 2001-08-23 2007-03-13 Paypal, Inc. Instant availability of electronically transferred funds

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100215450B1 (en) * 1996-05-17 1999-08-16 윤종용 Method and apparatus of object-oriented image representation using irregular mesh
US7685067B1 (en) * 1999-05-14 2010-03-23 Amazon.Com, Inc. Computer-assisted funds transfer system
US7555450B2 (en) * 1999-06-04 2009-06-30 Alternative Financial Solutions Llc Process for seeking authorization for present receipt of legal tender and associated system
US20010044787A1 (en) * 2000-01-13 2001-11-22 Gil Shwartz Secure private agent for electronic transactions
US7191149B1 (en) * 2000-06-05 2007-03-13 Alternative Financial Solutions, Llc Process for seeking authorization for present receipt of legal tender and associated system
WO2002017918A2 (en) * 2000-08-30 2002-03-07 Pfizer Products Inc. Sustained release formulations for growth hormone secretagogues
US20020040344A1 (en) * 2000-10-04 2002-04-04 Preiser Randall F. Check guarantee, verification, processing, credit reports and collection system and method awarding purchase points for usage of checks
JP2004524605A (en) * 2000-12-14 2004-08-12 クィジッド テクノロジーズ リミテッドQuizid Technologies Limited Authentication system
US7104443B1 (en) * 2001-04-23 2006-09-12 Debitman Card, Inc. Method and system for facilitating electronic funds transactions
US7775426B2 (en) * 2001-04-23 2010-08-17 Paul David K Method and system for facilitating electronic funds transactions
US20070174164A1 (en) * 2001-06-01 2007-07-26 American Express Travel Related Services Company, Inc. Network/Processor Fraud Scoring for Card Not Present Transactions
US20070174208A1 (en) * 2001-06-01 2007-07-26 American Express Travel Related Services Company, Inc. System and Method for Global Automated Address Verification
US7542931B2 (en) * 2001-06-01 2009-06-02 American Express Travel Related Services Company, Inc. System and method for global automated address verification
US20030004819A1 (en) * 2001-06-28 2003-01-02 International Business Machines Corporation Anonymous email guarantor processing
US7131571B2 (en) * 2002-03-26 2006-11-07 First Data Corporation Alternative payment devices using electronic check processing as a payment mechanism
US6821374B2 (en) * 2003-01-03 2004-11-23 Kenneth Ian Greenhill Pressure sensitive label without pressure sensitive carrier
US7644019B2 (en) * 2003-04-21 2010-01-05 Buysafe, Inc. Safe transaction guaranty
ES2581236T3 (en) * 2003-06-10 2016-09-02 Mastercard International, Inc. Systems and methods which allow for secure payment transactions using a data structure formatted
US6886741B1 (en) * 2004-03-08 2005-05-03 Melvin E. Salveson Electronic transaction system
US20050279827A1 (en) * 2004-04-28 2005-12-22 First Data Corporation Methods and systems for providing guaranteed merchant transactions
US20080133419A1 (en) * 2006-12-05 2008-06-05 Brian Wormington Secure financial transaction system and method

Patent Citations (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5428210A (en) * 1992-01-10 1995-06-27 National Bancard Corporation Data card terminal with embossed character reader and signature capture
US5432326A (en) * 1992-01-10 1995-07-11 National Bancard Corporation Systems and methods for operating data card terminals for transaction chargeback protection
US5334823A (en) * 1992-01-10 1994-08-02 National Bancard Corporation Systems and methods for operating data card terminals for transaction chargeback protection
US5448047A (en) * 1992-10-30 1995-09-05 Microbilt Corporation Card validation method using multiple cord data regions
US5903882A (en) * 1996-12-13 1999-05-11 Certco, Llc Reliance server for electronic transaction system
US6163771A (en) * 1997-08-28 2000-12-19 Walker Digital, Llc Method and device for generating a single-use financial account number
US5914472A (en) * 1997-09-23 1999-06-22 At&T Corp Credit card spending authorization control system
US7043441B1 (en) * 1997-10-01 2006-05-09 At&T Corp. Method and apparatus using digital credentials and other electronic certificates for electronic transactions
US20040031856A1 (en) * 1998-09-16 2004-02-19 Alon Atsmon Physical presence digital authentication system
US6254000B1 (en) * 1998-11-13 2001-07-03 First Data Corporation System and method for providing a card transaction authorization fraud warning
US20060143121A1 (en) * 1998-11-23 2006-06-29 Treider Kevin C Electronic factoring
US20060031161A1 (en) * 1999-01-15 2006-02-09 D Agostino John System and method for performing secure credit card purchases
US20050131816A1 (en) * 1999-05-14 2005-06-16 Britto Mark J. Computer-based funds transfer system
US20010034702A1 (en) * 2000-02-04 2001-10-25 Mockett Gregory P. System and method for dynamically issuing and processing transaction specific digital credit or debit cards
US20050278244A1 (en) * 2000-02-22 2005-12-15 Yuan Frank S Auction with methods and mechanisms to avoid fraud
US20010034720A1 (en) * 2000-03-07 2001-10-25 David Armes System for facilitating a transaction
US6999943B1 (en) * 2000-03-10 2006-02-14 Doublecredit.Com, Inc. Routing methods and systems for increasing payment transaction volume and profitability
US20020013765A1 (en) * 2000-05-23 2002-01-31 Gil Shwartz Intrinsic authorization for electronic transactions
US20030083986A1 (en) * 2000-08-15 2003-05-01 Toshiaki Kobayashi Method of credit guarantee in electronic commerce
US20020120582A1 (en) * 2001-02-26 2002-08-29 Stephen Elston Method for establishing an electronic commerce account
US20020123938A1 (en) * 2001-03-01 2002-09-05 Yu Philip S. Systems and methods to facilitate a transaction wherein a purchaser is associated with an approver
US20020139837A1 (en) * 2001-03-12 2002-10-03 Spitz Clayton P. Purchasing card transaction risk model
US6783065B2 (en) * 2001-03-12 2004-08-31 First Data Corporation Purchasing card transaction risk model
US20030172027A1 (en) * 2001-03-23 2003-09-11 Scott Walter G. Method for conducting a credit transaction using biometric information
US20040049455A1 (en) * 2001-07-06 2004-03-11 Hossein Mohsenzadeh Secure authentication and payment system
US7191151B1 (en) * 2001-08-23 2007-03-13 Paypal, Inc. Instant availability of electronically transferred funds
US20030046224A1 (en) * 2001-08-30 2003-03-06 Mujtaba M. Shahid Method and apparatus for handling monetary transactions
US20030093367A1 (en) * 2001-11-15 2003-05-15 First Data Corporation Online incremental payment method
US20030126075A1 (en) * 2001-11-15 2003-07-03 First Data Corporation Online funds transfer method
US20030101134A1 (en) * 2001-11-28 2003-05-29 Liu James C. Method and system for trusted transaction approval
US20040030644A1 (en) * 2001-12-14 2004-02-12 Shaper Stephen J. Systems for facilitating card processing systems/improved risk control
US20030233292A1 (en) * 2002-06-13 2003-12-18 Visa U.S.A., Inc. Method and system for facilitating electronic dispute resolution
US20040064405A1 (en) * 2002-09-30 2004-04-01 First Data Corporation Methods and systems for processing partial payments using debit cards
US20040199462A1 (en) * 2003-04-02 2004-10-07 Ed Starrs Fraud control method and system for network transactions
US20040260644A1 (en) * 2003-04-23 2004-12-23 Robert Doerner Credit authorization systems and methods
US20040230527A1 (en) * 2003-04-29 2004-11-18 First Data Corporation Authentication for online money transfers
US20050192901A1 (en) * 2003-06-30 2005-09-01 Mccoy Randal A. Credit card supported electronic payments
US20050234833A1 (en) * 2004-04-16 2005-10-20 First Data Corporation Methods and systems for online transaction processing
US20060016880A1 (en) * 2004-07-20 2006-01-26 Irek Singer Wireless payment processing system
US20060026097A1 (en) * 2004-07-30 2006-02-02 Kagi, Inc. Method and apparatus for verifying a financial instrument
US20060229961A1 (en) * 2005-04-08 2006-10-12 Efunds Corporation Risk evaluation method and system using ACH data

Cited By (119)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7328844B2 (en) * 2002-01-17 2008-02-12 Darwin Innovations Corporation Point-of-transaction machine with improved versatility and related method
US9058627B1 (en) 2002-05-30 2015-06-16 Consumerinfo.Com, Inc. Circular rotational interface for display of consumer credit information
US9710852B1 (en) 2002-05-30 2017-07-18 Consumerinfo.Com, Inc. Credit report timeline user interface
US9400589B1 (en) 2002-05-30 2016-07-26 Consumerinfo.Com, Inc. Circular rotational interface for display of consumer credit information
US8700535B2 (en) 2003-02-25 2014-04-15 Microsoft Corporation Issuing a publisher use license off-line in a digital rights management (DRM) system
US8719171B2 (en) 2003-02-25 2014-05-06 Microsoft Corporation Issuing a publisher use license off-line in a digital rights management (DRM) system
US8781953B2 (en) 2003-03-21 2014-07-15 Consumerinfo.Com, Inc. Card management system and method
US7967195B2 (en) * 2004-04-28 2011-06-28 First Data Corporation Methods and systems for providing guaranteed merchant transactions
US20080052235A1 (en) * 2004-04-28 2008-02-28 First Data Corporation Methods And Systems For Providing Guaranteed Merchant Transactions
US8347078B2 (en) 2004-10-18 2013-01-01 Microsoft Corporation Device certificate individualization
US9336359B2 (en) 2004-10-18 2016-05-10 Microsoft Technology Licensing, Llc Device certificate individualization
US8176564B2 (en) 2004-11-15 2012-05-08 Microsoft Corporation Special PC mode entered upon detection of undesired state
US8336085B2 (en) * 2004-11-15 2012-12-18 Microsoft Corporation Tuning product policy using observed evidence of customer behavior
US9224168B2 (en) 2004-11-15 2015-12-29 Microsoft Technology Licensing, Llc Tuning product policy using observed evidence of customer behavior
US8464348B2 (en) 2004-11-15 2013-06-11 Microsoft Corporation Isolated computing environment anchored into CPU and motherboard
US20060144927A1 (en) * 2005-01-06 2006-07-06 First Data Corporation Identity verification systems and methods
US20130105573A1 (en) * 2005-01-06 2013-05-02 Early Warning Services, Llc Identity verification systems and methods
US20090313069A1 (en) * 2005-01-06 2009-12-17 Early Warning Services, Llc Identity Verification Systems and Methods
US8172132B2 (en) 2005-01-06 2012-05-08 Early Warning Services, Llc Identity verification systems and methods
US7566002B2 (en) * 2005-01-06 2009-07-28 Early Warning Services, Llc Identity verification systems and methods
US8725646B2 (en) 2005-04-15 2014-05-13 Microsoft Corporation Output protection levels
US9436804B2 (en) 2005-04-22 2016-09-06 Microsoft Technology Licensing, Llc Establishing a unique session key using a hardware functionality scan
US9363481B2 (en) 2005-04-22 2016-06-07 Microsoft Technology Licensing, Llc Protected media pipeline
US9189605B2 (en) 2005-04-22 2015-11-17 Microsoft Technology Licensing, Llc Protected computing environment
US8438645B2 (en) 2005-04-27 2013-05-07 Microsoft Corporation Secure clock with grace periods
US8781969B2 (en) 2005-05-20 2014-07-15 Microsoft Corporation Extensible media rights
US8353046B2 (en) 2005-06-08 2013-01-08 Microsoft Corporation System and method for delivery of a modular operating system
US20070012757A1 (en) * 2005-07-14 2007-01-18 First Data Corporation Identity verification switch
US8109435B2 (en) * 2005-07-14 2012-02-07 Early Warning Services, Llc Identity verification switch
US9004355B2 (en) 2005-09-29 2015-04-14 Cardfree Inc Secure system and method to pay for a service provided at a reservation
US8622292B2 (en) * 2005-09-29 2014-01-07 Jeffrey Bart Katz Reservation-based preauthorization payment system
US20070233603A1 (en) * 2006-03-30 2007-10-04 Schmidgall Matthew M Flexible routing of electronic-based transactions
US7992203B2 (en) 2006-05-24 2011-08-02 Red Hat, Inc. Methods and systems for secure shared smartcard access
US8762350B2 (en) 2006-06-06 2014-06-24 Red Hat, Inc. Methods and systems for providing data objects on a token
US9450763B2 (en) 2006-06-06 2016-09-20 Red Hat, Inc. Server-side key generation
US8098829B2 (en) 2006-06-06 2012-01-17 Red Hat, Inc. Methods and systems for secure key delivery
US8495380B2 (en) 2006-06-06 2013-07-23 Red Hat, Inc. Methods and systems for server-side key generation
US7822209B2 (en) 2006-06-06 2010-10-26 Red Hat, Inc. Methods and systems for key recovery for a token
US8180741B2 (en) 2006-06-06 2012-05-15 Red Hat, Inc. Methods and systems for providing data objects on a token
US8364952B2 (en) 2006-06-06 2013-01-29 Red Hat, Inc. Methods and system for a key recovery plan
US8332637B2 (en) 2006-06-06 2012-12-11 Red Hat, Inc. Methods and systems for nonce generation in a token
US8099765B2 (en) 2006-06-07 2012-01-17 Red Hat, Inc. Methods and systems for remote password reset using an authentication credential managed by a third party
US8589695B2 (en) 2006-06-07 2013-11-19 Red Hat, Inc. Methods and systems for entropy collection for server-side key generation
US8707024B2 (en) 2006-06-07 2014-04-22 Red Hat, Inc. Methods and systems for managing identity management security domains
US8412927B2 (en) 2006-06-07 2013-04-02 Red Hat, Inc. Profile framework for token processing system
US9769158B2 (en) 2006-06-07 2017-09-19 Red Hat, Inc. Guided enrollment and login for token users
US8806219B2 (en) 2006-08-23 2014-08-12 Red Hat, Inc. Time-based function back-off
US8787566B2 (en) 2006-08-23 2014-07-22 Red Hat, Inc. Strong encryption
US9762572B2 (en) 2006-08-31 2017-09-12 Red Hat, Inc. Smartcard formation with authentication
US8356342B2 (en) * 2006-08-31 2013-01-15 Red Hat, Inc. Method and system for issuing a kill sequence for a token
US8977844B2 (en) 2006-08-31 2015-03-10 Red Hat, Inc. Smartcard formation with authentication keys
US8074265B2 (en) 2006-08-31 2011-12-06 Red Hat, Inc. Methods and systems for verifying a location factor associated with a token
US9038154B2 (en) 2006-08-31 2015-05-19 Red Hat, Inc. Token Registration
US9563916B1 (en) 2006-10-05 2017-02-07 Experian Information Solutions, Inc. System and method for generating a finance attribute from tradeline data
US10121194B1 (en) 2006-10-05 2018-11-06 Experian Information Solutions, Inc. System and method for generating a finance attribute from tradeline data
US8793777B2 (en) * 2006-10-10 2014-07-29 Equifax, Inc. Verification and authentication systems and methods
US20120266227A1 (en) * 2006-10-10 2012-10-18 Equifax Inc. Verification and authentication systems and methods
US8693690B2 (en) 2006-12-04 2014-04-08 Red Hat, Inc. Organizing an extensible table for storing cryptographic objects
US8813243B2 (en) 2007-02-02 2014-08-19 Red Hat, Inc. Reducing a size of a security-related data object stored on a token
US8639940B2 (en) 2007-02-28 2014-01-28 Red Hat, Inc. Methods and systems for assigning roles on a token
US8832453B2 (en) 2007-02-28 2014-09-09 Red Hat, Inc. Token recycling
US9081948B2 (en) 2007-03-13 2015-07-14 Red Hat, Inc. Configurable smartcard
US8370264B1 (en) 2007-03-30 2013-02-05 Amazon Technologies, Inc. System and method of fulfilling a transaction
US7962418B1 (en) * 2007-03-30 2011-06-14 Amazon Technologies, Inc. System and method of fulfilling a transaction
US9299073B1 (en) 2007-04-26 2016-03-29 United Services Automobile Association (Usaa) Secure card
US8376225B1 (en) * 2007-04-26 2013-02-19 United Services Automobile Association (Usaa) Secure card
US8733640B1 (en) 2007-04-26 2014-05-27 United Services Automobile Association (Usaa) Secure card
US20130173450A1 (en) * 2007-05-25 2013-07-04 Experian Information Solutions, Inc. System and method for automated detection of never-pay data sets
US9251541B2 (en) * 2007-05-25 2016-02-02 Experian Information Solutions, Inc. System and method for automated detection of never-pay data sets
US20100332381A1 (en) * 2007-05-25 2010-12-30 Celka Christopher J System and method for automated detection of never-pay data sets
US8364588B2 (en) * 2007-05-25 2013-01-29 Experian Information Solutions, Inc. System and method for automated detection of never-pay data sets
US9690820B1 (en) 2007-09-27 2017-06-27 Experian Information Solutions, Inc. Database system for triggering event notifications based on updates to database records
US10262364B2 (en) 2007-12-14 2019-04-16 Consumerinfo.Com, Inc. Card registry systems and methods
US9230283B1 (en) 2007-12-14 2016-01-05 Consumerinfo.Com, Inc. Card registry systems and methods
US9767513B1 (en) 2007-12-14 2017-09-19 Consumerinfo.Com, Inc. Card registry systems and methods
US9542682B1 (en) 2007-12-14 2017-01-10 Consumerinfo.Com, Inc. Card registry systems and methods
US8930251B2 (en) 2008-06-18 2015-01-06 Consumerinfo.Com, Inc. Debt trending systems and methods
US9489694B2 (en) * 2008-08-14 2016-11-08 Experian Information Solutions, Inc. Multi-bureau credit file freeze and unfreeze
US10115155B1 (en) * 2008-08-14 2018-10-30 Experian Information Solution, Inc. Multi-bureau credit file freeze and unfreeze
US9256904B1 (en) 2008-08-14 2016-02-09 Experian Information Solutions, Inc. Multi-bureau credit file freeze and unfreeze
US9792648B1 (en) * 2008-08-14 2017-10-17 Experian Information Solutions, Inc. Multi-bureau credit file freeze and unfreeze
US8595101B1 (en) 2008-09-08 2013-11-26 Exerian Information Solutions, Inc. Systems and methods for managing consumer accounts using data migration
US9595051B2 (en) 2009-05-11 2017-03-14 Experian Marketing Solutions, Inc. Systems and methods for providing anonymized user profile data
US9652802B1 (en) 2010-03-24 2017-05-16 Consumerinfo.Com, Inc. Indirect monitoring and reporting of a user's credit data
US9684905B1 (en) 2010-11-22 2017-06-20 Experian Information Solutions, Inc. Systems and methods for data verification
US9147042B1 (en) 2010-11-22 2015-09-29 Experian Information Solutions, Inc. Systems and methods for data verification
US9558519B1 (en) 2011-04-29 2017-01-31 Consumerinfo.Com, Inc. Exposing reporting cycle information
US20120317019A1 (en) * 2011-05-26 2012-12-13 First Data Corporation Card-Present On-Line Transactions
US9059980B2 (en) 2011-05-26 2015-06-16 First Data Corporation Systems and methods for authenticating mobile devices
US9106633B2 (en) 2011-05-26 2015-08-11 First Data Corporation Systems and methods for authenticating mobile device communications
US8775305B2 (en) * 2011-05-26 2014-07-08 First Data Corporation Card-present on-line transactions
US9154477B2 (en) 2011-05-26 2015-10-06 First Data Corporation Systems and methods for encrypting mobile device communications
US9331996B2 (en) 2011-05-26 2016-05-03 First Data Corporation Systems and methods for identifying devices by a trusted service manager
US9106632B2 (en) 2011-05-26 2015-08-11 First Data Corporation Provisioning by delivered items
US9607336B1 (en) 2011-06-16 2017-03-28 Consumerinfo.Com, Inc. Providing credit inquiry alerts
US8775299B2 (en) 2011-07-12 2014-07-08 Experian Information Solutions, Inc. Systems and methods for large-scale credit data processing
US8856894B1 (en) 2012-11-28 2014-10-07 Consumerinfo.Com, Inc. Always on authentication
US9916621B1 (en) 2012-11-30 2018-03-13 Consumerinfo.Com, Inc. Presentation of credit score factors
US9830646B1 (en) 2012-11-30 2017-11-28 Consumerinfo.Com, Inc. Credit score goals and alerts systems and methods
US10255598B1 (en) 2012-12-06 2019-04-09 Consumerinfo.Com, Inc. Credit card account data extraction
US9697263B1 (en) 2013-03-04 2017-07-04 Experian Information Solutions, Inc. Consumer data request fulfillment system
US20150088613A1 (en) * 2013-09-23 2015-03-26 Comdata Network, Inc. Systems, methods, and computer program products for managing fuel costs
US20150120555A1 (en) * 2013-10-29 2015-04-30 Elwha Llc Exchange authorization analysis infused with network-acquired data stream information
US20150120550A1 (en) * 2013-10-29 2015-04-30 Elwha LLC, a limited liability corporation of the State of Delaware Guaranty provisioning via wireless service purveyance
US20150120502A1 (en) * 2013-10-29 2015-04-30 Elwha LLC, a limited liability corporation of the State of Delaware Supporting guaranty provisioning via user attribute proffering
US20150120473A1 (en) * 2013-10-29 2015-04-30 Elwha LLC, a limited liability corporation of the State of Delaware Vendor-facilitated guaranty provisioning
US10157407B2 (en) 2013-10-29 2018-12-18 Elwha Llc Financier-facilitated guaranty provisioning
US9818105B2 (en) * 2013-10-29 2017-11-14 Elwha Llc Guaranty provisioning via wireless service purveyance
US9934498B2 (en) * 2013-10-29 2018-04-03 Elwha Llc Facilitating guaranty provisioning for an exchange
US20150120500A1 (en) * 2013-10-29 2015-04-30 Elwha LLC, a limited liability corporation of the State of Delaware Facilitating guaranty provisioning for an exchange
US20150120440A1 (en) * 2013-10-29 2015-04-30 Elwha LLC, a limited liability corporation of the State of Delaware Guaranty provisioning via internetworking
US10102536B1 (en) 2013-11-15 2018-10-16 Experian Information Solutions, Inc. Micro-geographic aggregation system
US20150199738A1 (en) * 2014-01-14 2015-07-16 Elwha Llc Guaranty investigation
USD759689S1 (en) 2014-03-25 2016-06-21 Consumerinfo.Com, Inc. Display screen or portion thereof with graphical user interface
USD760256S1 (en) 2014-03-25 2016-06-28 Consumerinfo.Com, Inc. Display screen or portion thereof with graphical user interface
USD759690S1 (en) 2014-03-25 2016-06-21 Consumerinfo.Com, Inc. Display screen or portion thereof with graphical user interface
US9576030B1 (en) 2014-05-07 2017-02-21 Consumerinfo.Com, Inc. Keeping up with the joneses
US10019508B1 (en) 2014-05-07 2018-07-10 Consumerinfo.Com, Inc. Keeping up with the joneses
US10242019B1 (en) 2014-12-19 2019-03-26 Experian Information Solutions, Inc. User behavior segmentation using latent topic detection

Also Published As

Publication number Publication date
US7967195B2 (en) 2011-06-28
EP1747522A4 (en) 2012-12-19
CA2563722A1 (en) 2005-11-17
WO2005109307A2 (en) 2005-11-17
EP1747522A2 (en) 2007-01-31
WO2005109307A3 (en) 2007-03-01
US20080052235A1 (en) 2008-02-28

Similar Documents

Publication Publication Date Title
US8061597B2 (en) System and method for disputing individual items that are the subject of a transaction
US5949044A (en) Method and apparatus for funds and credit line transfers
AU2007345585B2 (en) Signature based negative list for off line payment device validation
US7346575B1 (en) Systems and methods for selectively delaying financial transactions
US8370259B2 (en) Verifying the source of electronically exchanged value
US8489506B2 (en) Portable consumer device verification system
US6786400B1 (en) Multiple account banking system and method
US8073776B2 (en) Method and apparatus for a no pre-set spending limit transaction card
AU2001257280C1 (en) Online payer authentication service
US8099360B2 (en) Method and apparatus for issuing and managing gift certificates
AU2003217732B2 (en) Credit extension process using a prepaid card
US8046260B2 (en) Method and system for authorising returns
US6193155B1 (en) Method and apparatus for issuing and managing gift certificates
US7780075B2 (en) Methods and systems for transferring funds
US8781966B2 (en) Money transfer transactions via pre-paid wireless communication devices
US20040139008A1 (en) Payment system clearing for transactions
US20070156579A1 (en) System and method of reducing or eliminating change in cash transaction by crediting at least part of change to buyer's account over electronic medium
US8565723B2 (en) Onetime passwords for mobile wallets
US20020170958A1 (en) Computer readable universal authorization card system and method for using same
JP5663487B2 (en) System and method for processing online merchant and the transaction
US6012039A (en) Tokenless biometric electronic rewards system
CN102812488B (en) Trading system to reduce fraud
US20030200180A1 (en) Money card system, method and apparatus
US7567934B2 (en) Credit card system and method
US6736314B2 (en) Methods and systems for transferring funds

Legal Events

Date Code Title Description
AS Assignment

Owner name: FIRST DATA CORPORATION, COLORADO

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MASCAVAGE, JOHN JOSEPH;WEICHERT, MARGARET MORGAN;HOGAN, ROBERT;REEL/FRAME:016473/0494;SIGNING DATES FROM 20050707 TO 20050814

AS Assignment

Owner name: CREDIT SUISSE, CAYMAN ISLANDS BRANCH, AS COLLATERA

Free format text: SECURITY AGREEMENT;ASSIGNORS:FIRST DATA CORPORATION;CARDSERVICE INTERNATIONAL, INC.;FUNDSXPRESS, INC.;AND OTHERS;REEL/FRAME:020045/0165

Effective date: 20071019

AS Assignment

Owner name: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATE

Free format text: SECURITY AGREEMENT;ASSIGNORS:DW HOLDINGS, INC.;FIRST DATA RESOURCES, INC. (K/N/A FIRST DATA RESOURCES, LLC);FUNDSXPRESS FINANCIAL NETWORKS, INC.;AND OTHERS;REEL/FRAME:025368/0183

Effective date: 20100820

AS Assignment

Owner name: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATE

Free format text: SECURITY AGREEMENT;ASSIGNORS:DW HOLDINGS, INC.;FIRST DATA RESOURCES, LLC;FUNDSXPRESS FINANCIAL NETWORKS, INC.;AND OTHERS;REEL/FRAME:025719/0590

Effective date: 20101217

STCB Information on status: application discontinuation

Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION