WO2008036475A2 - Online payer authorization systems and methods - Google Patents
Online payer authorization systems and methods Download PDFInfo
- Publication number
- WO2008036475A2 WO2008036475A2 PCT/US2007/075377 US2007075377W WO2008036475A2 WO 2008036475 A2 WO2008036475 A2 WO 2008036475A2 US 2007075377 W US2007075377 W US 2007075377W WO 2008036475 A2 WO2008036475 A2 WO 2008036475A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- customer
- transaction
- electronic
- record
- merchant
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
Definitions
- Embodiments of the present invention relate generally to a payer authorization system for purchase transactions. More specifically, embodiments of the present invention relate to systems and methods for obtaining payer authorization of a transaction while the transaction is in process.
- Embodiments of the present invention thus provide an in-process payer authorization system.
- the system includes a server computer that is configured to host a merchant e-commerce web site and create a purchase transaction record based on a transaction with a customer.
- the purchase transaction record includes an account identifier of the customer.
- the server computer is also configured to render a first display screen on a computer of the customer.
- the first display screen is configured to query whether the customer is registered for in-process payer authorization.
- the server computer is further configured to include information based on a response to the query in the transaction record and render a second display screen on the computer of the customer.
- the second display screen is configured to receive a confirmation code from the customer.
- the system also includes a host computer system that is configured to receive the transaction record from the server computer and locate an in-process payer authorization record relating to the customer.
- the in-process payer authorization record includes an electronic address of the customer.
- the host computer system is further configured to generate a random code relating to the purchase transaction and send an electronic communication to the electronic address of the customer.
- the electronic communication includes the random code.
- the host computer system is also configured to, while the transaction with the customer is in progress, receive the confirmation code from the server computer, compare the confirmation code to the random code, and, based on the comparison, determine whether to authorize the transaction.
- the electronic address is an email address of the customer.
- the electronic communication may be an SMS message to a mobile phone number of the customer.
- the method includes, at a host computer system of a credit card processor, receiving a purchase transaction record from a merchant that includes an account identifier for a customer.
- the method also includes locating a record relating to the customer, which record identifies an electronic address for the customer.
- the method also includes generating a random code and sending an electronic message that includes the random code to the electronic address of the customer.
- the method also includes receiving a communication that includes a code from the customer via the merchant.
- the method also includes comparing the code in the communication to the random code, and, in response to the comparison, authorizing the purchase transaction.
- the electronic address is an email address of the customer.
- Sending an electronic message to the electronic address of the customer may include sending an SMS message to a mobile phone number of the customer.
- the method may include pre- registering the customer prior to the transaction. Pre-registering the customer may include receiving a request to register from the customer, which request includes at least the account identifier of the customer and the electronic contact address for the customer. Pre-registering the customer also may include verifying the electronic address of the customer.
- the method May include thereafter charging the merchant a reduced interchange rate for the purchase transaction.
- the method also may include thereafter shipping merchandise relating to the transaction to the customer at an expedited rate.
- Still other embodiments provide a method of processing a purchase transaction.
- the method includes, at a server computer of an online merchant, receiving from a customer a selection of at least one item to be purchased by the customer, initiating a checkout process for the at least one item, and sending a transaction record relating to the purchase transaction to a host computer system of a transaction processor, which transaction request includes a presentation instrument account identifier of the customer.
- the method also includes using the account identifier to locate a record of the customer, which record includes an electronic address of the customer.
- the method further includes, at the host computer system of the transaction processor, generating a random code, sending an electronic message to the electronic address of the customer, wherein the electronic message includes the random code, and, while the checkout process is in progress, receiving a confirmation code from the customer at the merchant server.
- the method further includes sending the confirmation code from the merchant server to the host computer system of the transaction processor, at the host computer system of the transaction processor, comparing the confirmation code to the random code, and based on the comparison, authorizing the transaction.
- Still other embodiments provide an in-process payer authorization system that includes means for creating a purchase transaction record based on a transaction with a consumer, which purchase transaction record includes an account identifier of the consumer, means for locating an electronic address of the consumer using the account identifier while the transaction is in process, means for generating a random code relating to the purchase transaction while the transaction is in process, means for transmitting the random code to the electronic address of the consumer, means for receiving a confirmation code from the consumer while the transaction is in process, means for comparing the confirmation code to the random code, and means for authorizing the transaction based on the comparison while the transaction is in process.
- Figure 1 illustrates an online payer authorization system according to embodiments of the invention.
- Figure 2 illustrates a method of obtaining payer authorization during an online purchase transaction according to embodiments of the invention, which method may be implemented in the system of Fig. 1.
- Figures 3A and 3B illustrate exemplary display screens that may be used to obtain payer authorization during an online purchase transaction according to embodiments of the invention.
- Embodiments of the present invention relate to systems and methods for obtaining payer authorization during the course of an online purchase transaction, hi order to provide a context for describing embodiments of the present invention, embodiments of the invention will be described herein with reference to using a credit card account to purchase merchandise over the Internet from an online merchant. Those skilled in the art will appreciate, however, that the systems and methods described herein may be applied to, for example, obtaining payer authorization during a telephone purchase or the like.
- a process is terminated when its operations are completed, but could have additional steps not included in the figure.
- a process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc.
- a process corresponds to a function
- its termination corresponds to a return of the function to the calling function or the main function.
- the term “storage medium” may represent one or more devices for storing data, including read only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage mediums, optical storage mediums, flash memory devices and/or other machine readable mediums for storing information.
- ROM read only memory
- RAM random access memory
- magnetic RAM magnetic RAM
- core memory magnetic disk storage mediums
- optical storage mediums flash memory devices and/or other machine readable mediums for storing information.
- computer-readable medium includes, but is not limited to portable or fixed storage devices, optical storage devices, wireless channels and various other mediums capable of storing, containing or carrying instruction(s) and/or data.
- embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof.
- the program code or code segments to perform the necessary tasks may be stored in a machine readable medium such as storage medium.
- a processor(s) may perform the necessary tasks.
- a code segment may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements.
- a code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.
- an online merchant may obtain confirmation of payer (AKA, consumer or customer) authorization for a credit card (AKA presentation instrument) purchase transaction even thought the payer's credit card is not present. This is accomplished with the assistance of the merchant's credit card transaction processor, who sends a randomly- generated confirmation code to an electronic device of the payer while the payer is "checking out" from the merchant's online store. The payer then provides that code to the merchant, via, for example, a dialog box that pops up on the payer's computer screen while checking out from the merchant's online store. The code, as entered by the payer, is transmitted to the processor, and the transaction is completed if a match exists.
- the consumer/payer/card holder registers for the payer authorization service, in exchange for which an online merchant offers the customer, for example, expedited shipping on orders.
- the merchant provides this incentive to thereby receive lower transaction processing fees, chargeback protection, and/or the like from the merchant's credit card transaction processor.
- the transaction processor is able to provide this reduced rate, since the additional level of authorization reduces the risk that the transaction processor will have to incur the expense of a fraudulent transaction.
- the customer may pre-register for the service prior to initiating a transaction or may register during the checkout process of a transaction.
- the registration process may require the customer to provide personal information not available on the customer's card to thereby establish the customer's identity for registration purposes, hi other words, the registration process will include a level of security that would prevent a card thief from imitating the customer during the registration process.
- the customer also provides means for immediate contact with the customer, such as an email address or mobile phone number (AKA electronic address), to which the customer may receive a Short Message Service (SMS, or text message), email, or the like.
- SMS Short Message Service
- the customer is queried whether he is registered in the payer authorization service. If not, he is given the opportunity to register, which he may decline. If the customer is registered or elects to register, completion of the payment portion of the transaction is suspended while the merchant's credit card transaction processor generates a random code and sends it to the customer by way of the electronic address the customer provided. When the customer receives the random code, the customer inputs the code into a transaction processing window and completes the payment process. The transaction is completed only if the random code matches the code generated by the transaction processor. Of course, all other relevant portions (account number, credit card expiration date, billing zip code, name on card, etc.) of a typical transaction must match as well.
- Fig. 1 illustrates an exemplary system 100 according to embodiments of the invention.
- the system 100 is merely exemplary of a number of possible embodiments.
- the system 100 relates to an online merchant, but other exemplary systems may relate to a merchant having a telephone ordering system.
- a customer using a customer computing device 102, is communicating with an online merchant 104 via a network 106, such as the Internet.
- the online merchant may be, for example, a server connected to the Internet, which server hosts an e-commerce web site of the merchant.
- the customer selects merchandise or services for purchase from the merchant and initiates a checkout process.
- the merchant's online checkout system queries the customer whether the customer has enrolled in "in-process payer authorization.” (Those skilled in the art will appreciate that the use of the term "in-process payer authorization" is not intended to be limiting.
- the online merchant 104 sends a transaction record to the merchant's credit card transaction processor 108.
- the transaction record may include an indication that the customer has registered for in-process payer authorization and wishes to use that service in completing the current transaction. If so, the transaction processor 108 uses this information to locate a record relating to the customer, which record includes the electronic address of the customer. The transaction processor also may generate a random code for transmission to the customer as part of the in-process payer authorization.
- the customer's in-process payer authorization record may reside in any of several locations, hi some embodiments, the record is maintained by the merchant's credit card transaction processor 108. This may be the case, for example, if the processor 108 is also the processor for the entity that issued the customer his credit card (i.e., issuer). Li other embodiments, however, the processor 108 may have to communicate via a gateway 110 to a credit card transaction processing network 112, which may be any of the many well known transaction processing networks.
- the customer's in- process payer authorization record may reside at the gateway 110 or at any of a number of locations throughout the credit card transaction processing network 112. Those skilled in the art will appreciate that many possibilities exist.
- the transaction processor 108 sends the transaction record to the gateway 110.
- the transaction record includes the random code.
- the gateway 110 may contact the customer for authorization, as will be described.
- the transaction processor 108 may contact the customer for payer authorization as will be described.
- the gateway 110 contacts the customer using the customer's electronic address.
- the contact is made through a communication network 114, which may be the Internet, a Public Switched Telephone Network (PSTN), and/or the like.
- the network 114 may communicate with the customer through a wireless link 116.
- PSTN Public Switched Telephone Network
- the communication is an email to the customer. In other embodiments, the communication is a SMS message to the customer. In any case, the communication includes the random code.
- the customer may receive the communication on any of a variety of devices 118, including wired (e.g., a personal computer), or wireless (e.g., cell phone, PDA, etc.) devices.
- the customer enters a confirmation code into an appropriate space in the checkout portion of the merchant's web site (e.g., a dialog box).
- the merchant 104 forwards the confirmation code to the transaction processor 108 for comparison to the random code, and the transaction is completed if the codes match.
- the transaction processor 108 maintains the in-process payer authorization record for the customer.
- the transaction processor 108 acquires the customer's electronic address from the record, generates the random code, and SMS-messages the code to a cell phone or PDA of the customer. This all takes place before any communication is made from the transaction processor 108 to the gateway 110 and/or transaction processing network 112.
- Fig. 2 illustrates an exemplary method 200 according to embodiments of the invention.
- the method 200 may be implemented in the system 100 of Fig. 1 or other appropriate system.
- Those skilled in the art will appreciate that other methods according to other embodiments may have more, fewer, or different blocks than those illustrated and described here. Further, those skilled in the art will appreciate that other methods according to other embodiments may traverse the steps illustrated and described herein in a different order than that depicted.
- the method 200 begins with the optional block 202 of pre-registering a consumer (AKA, payer, customer, card holder) to participate in in-process payer authorization.
- AKA payer, customer, card holder
- Any of a variety of entities may offer a consumer/card holder an opportunity to register for the service.
- an online merchant may offer a frequent customer the opportunity to receive expedited shipping if the customer enrolls in and uses in-process payer authorization for purchases at the merchant's web site.
- the card holder's processor also may offer the card holder the opportunity to enroll as a means for the customer to provide better security for the card holder's credit card.
- the card holder In pre-registering, the card holder creates a record with a credit card transaction processor, such as the processor 108 of Fig. 1.
- the transaction processor maybe the card holder's transaction processor, although this is not a requirement.
- the card holder may be required, however, to provide information, for security purposes, that confirms the card holder's identity.
- the card holder In completing the pre-registration process, the card holder provides an electronic address (e.g., email address, cell phone number, etc.) to which in-process payer authorization messages may be directed.
- an electronic address e.g., email address, cell phone number, etc.
- a merchant is registered to provide in-process payer authorization to its customers. This may include a transaction processor working with the merchant to code appropriate procedures into the merchant's web site checkout process.
- a merchant may be offered a fee reduction (e.g., a lower "interchange fee," transaction processing fee, and/or the like) for transactions in which a consumer provides in-process payer authorization.
- a consumer initiates a transaction with a registered merchant.
- a determination is made whether the consumer is registered with in-process payer authorization. This may be accomplished by rendering a display screen, such as the display screen 300 of Fig. 3 A, on the consumer's computer. By selecting an appropriate button, the consumer is given an opportunity to register at block 210. Registration at block 210 is substantially similar to consumer pre- registration discussed previously at block 202. If the consumer is already registered and elects to use in-process payer authorization for the current transaction, the process continues at block 212.
- the merchant forwards a transaction request to the merchant's credit card transaction processor.
- the transaction request includes an indication that the consumer intends to use in-process payer authorization for the current transaction.
- an in-process payer authorization record relating to the consumer resides with the transaction processor, and the transaction processor uses the transaction request to locate the record.
- the record includes an electronic address for the consumer.
- the transaction processor then generates a random code and sends the code to a communication device (e.g., cell phone, PDA, personal computer, etc.) of the consumer. This takes place at block 214.
- a communication device e.g., cell phone, PDA, personal computer, etc.
- the consumer submits a confirmation code to the merchant.
- the confirmation code is passed through to the merchant's transaction processor, possibly as part of a transaction authorization or as part of a completed transaction request.
- a decision is made whether the confirmation code provided by the consumer matches the random code generated by the transaction processor. If not, the transaction is denied at block 218. If, however, the confirmation code is received by the transaction processor and matches the random code the transaction processor generated, then the transaction is allowed at block 220.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Economics (AREA)
- Marketing (AREA)
- Development Economics (AREA)
- Technology Law (AREA)
- Computer Security & Cryptography (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- User Interface Of Digital Computer (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The system also configured to render a first display screen on a computer of the customer that is configured to query whether the customer is registered (210) for in-process payer authorization.
Description
ONLINE PAYERAUTHORIZATION SYSTEMS AND METHODS
[0001] Embodiments of the present invention relate generally to a payer authorization system for purchase transactions. More specifically, embodiments of the present invention relate to systems and methods for obtaining payer authorization of a transaction while the transaction is in process.
BACKGROUND OF THE INVENTION
[0002] Online perchance transactions are becoming increasingly popular. Such transactions are almost exclusively settled using a credit or debit account. Because the presentation instrument (i.e., credit card) is not physically present for inspection by the online merchant to complete the transaction, such transactions are subject to a higher incidence of fraud. Merchants typically pay a higher rate (e.g., an interchange rate) for such transactions.
[0003] Moreover, presentation instrument holders also are at risk of having a credit card stolen. A stolen card may be used to complete online purchases before the card gets reported lost or stolen. Some online merchants protect themselves from such fraud by delaying shipment of merchandise purchased online, which is inconvenient for the customer. Customers, however, have few options to protect themselves from such fraud. Hence, for all the foregoing reasons, improved systems and methods are needed to reduce the incidence of fraud in online purchase transactions.
BRIEF SUMMARY OF THE INVENTION
[0004] Embodiments of the present invention thus provide an in-process payer authorization system. The system includes a server computer that is configured to host a merchant e-commerce web site and create a purchase transaction record based on a transaction with a customer. The purchase transaction record includes an account identifier of the customer. The server computer is also configured to render a first display screen on a computer of the customer. The first display screen is configured to query whether the customer is registered for in-process payer authorization. The server computer is further configured to include information based on a response to the query in the transaction record and render a second display screen on the computer of the customer. The second display screen is configured to receive a confirmation code from the customer. The system also includes a host computer system that is configured to receive the transaction record from the
server computer and locate an in-process payer authorization record relating to the customer. The in-process payer authorization record includes an electronic address of the customer. The host computer system is further configured to generate a random code relating to the purchase transaction and send an electronic communication to the electronic address of the customer. The electronic communication includes the random code. The host computer system is also configured to, while the transaction with the customer is in progress, receive the confirmation code from the server computer, compare the confirmation code to the random code, and, based on the comparison, determine whether to authorize the transaction. In some embodiments, the electronic address is an email address of the customer. The electronic communication may be an SMS message to a mobile phone number of the customer.
[0005] Other embodiments provide a method of processing a purchase transaction. The method includes, at a host computer system of a credit card processor, receiving a purchase transaction record from a merchant that includes an account identifier for a customer. The method also includes locating a record relating to the customer, which record identifies an electronic address for the customer. The method also includes generating a random code and sending an electronic message that includes the random code to the electronic address of the customer. The method also includes receiving a communication that includes a code from the customer via the merchant. The method also includes comparing the code in the communication to the random code, and, in response to the comparison, authorizing the purchase transaction.
[0006] In some embodiments, the electronic address is an email address of the customer. Sending an electronic message to the electronic address of the customer may include sending an SMS message to a mobile phone number of the customer. The method may include pre- registering the customer prior to the transaction. Pre-registering the customer may include receiving a request to register from the customer, which request includes at least the account identifier of the customer and the electronic contact address for the customer. Pre-registering the customer also may include verifying the electronic address of the customer. The method May include thereafter charging the merchant a reduced interchange rate for the purchase transaction. The method also may include thereafter shipping merchandise relating to the transaction to the customer at an expedited rate.
[0007] Still other embodiments provide a method of processing a purchase transaction. The method includes, at a server computer of an online merchant, receiving from a customer a selection of at least one item to be purchased by the customer, initiating a checkout process for the at least one item, and sending a transaction record relating to the purchase transaction to a host computer system of a transaction processor, which transaction request includes a presentation instrument account identifier of the customer. The method also includes using the account identifier to locate a record of the customer, which record includes an electronic address of the customer. The method further includes, at the host computer system of the transaction processor, generating a random code, sending an electronic message to the electronic address of the customer, wherein the electronic message includes the random code, and, while the checkout process is in progress, receiving a confirmation code from the customer at the merchant server. The method further includes sending the confirmation code from the merchant server to the host computer system of the transaction processor, at the host computer system of the transaction processor, comparing the confirmation code to the random code, and based on the comparison, authorizing the transaction.
[0008] Still other embodiments provide an in-process payer authorization system that includes means for creating a purchase transaction record based on a transaction with a consumer, which purchase transaction record includes an account identifier of the consumer, means for locating an electronic address of the consumer using the account identifier while the transaction is in process, means for generating a random code relating to the purchase transaction while the transaction is in process, means for transmitting the random code to the electronic address of the consumer, means for receiving a confirmation code from the consumer while the transaction is in process, means for comparing the confirmation code to the random code, and means for authorizing the transaction based on the comparison while the transaction is in process.
BRIEF DESCRIPTION OF THE DRAWINGS
[0009] 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. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the
description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.
[0010] Figure 1 illustrates an online payer authorization system according to embodiments of the invention.
[0011] Figure 2 illustrates a method of obtaining payer authorization during an online purchase transaction according to embodiments of the invention, which method may be implemented in the system of Fig. 1.
[0012] Figures 3A and 3B illustrate exemplary display screens that may be used to obtain payer authorization during an online purchase transaction according to embodiments of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0013] Embodiments of the present invention relate to systems and methods for obtaining payer authorization during the course of an online purchase transaction, hi order to provide a context for describing embodiments of the present invention, embodiments of the invention will be described herein with reference to using a credit card account to purchase merchandise over the Internet from an online merchant. Those skilled in the art will appreciate, however, that the systems and methods described herein may be applied to, for example, obtaining payer authorization during a telephone purchase or the like.
[0014] The ensuing description provides preferred exemplary embodiment(s) only, and is not intended to limit the scope, applicability or configuration of the invention. Rather, the ensuing description of the preferred exemplary embodiment(s) will provide those skilled in the art with an enabling description for implementing a preferred exemplary embodiment of the invention. It is to be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the invention as set forth in the appended claims.
[0015] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, systems may be shown in block diagrams in order not to obscure the embodiments in unnecessary detail. In other instances, well-known processes, structures and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
[0016] Also, it is noted that the embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently, hi addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed, but could have additional steps not included in the figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination corresponds to a return of the function to the calling function or the main function.
[0017] Moreover, as disclosed herein, the term "storage medium" may represent one or more devices for storing data, including read only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage mediums, optical storage mediums, flash memory devices and/or other machine readable mediums for storing information. The term "computer-readable medium" includes, but is not limited to portable or fixed storage devices, optical storage devices, wireless channels and various other mediums capable of storing, containing or carrying instruction(s) and/or data.
[0018] Furthermore, embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the necessary tasks may be stored in a machine readable medium such as storage medium. A processor(s) may perform the necessary tasks. A code segment may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.
[0019] According to embodiments of the present invention, an online merchant may obtain confirmation of payer (AKA, consumer or customer) authorization for a credit card (AKA presentation instrument) purchase transaction even thought the payer's credit card is not present. This is accomplished with the assistance of the merchant's credit card transaction
processor, who sends a randomly- generated confirmation code to an electronic device of the payer while the payer is "checking out" from the merchant's online store. The payer then provides that code to the merchant, via, for example, a dialog box that pops up on the payer's computer screen while checking out from the merchant's online store. The code, as entered by the payer, is transmitted to the processor, and the transaction is completed if a match exists.
[0020] In a specific example of the present invention, the consumer/payer/card holder registers for the payer authorization service, in exchange for which an online merchant offers the customer, for example, expedited shipping on orders. The merchant provides this incentive to thereby receive lower transaction processing fees, chargeback protection, and/or the like from the merchant's credit card transaction processor. The transaction processor is able to provide this reduced rate, since the additional level of authorization reduces the risk that the transaction processor will have to incur the expense of a fraudulent transaction.
[0021] The customer may pre-register for the service prior to initiating a transaction or may register during the checkout process of a transaction. The registration process may require the customer to provide personal information not available on the customer's card to thereby establish the customer's identity for registration purposes, hi other words, the registration process will include a level of security that would prevent a card thief from imitating the customer during the registration process. The customer also provides means for immediate contact with the customer, such as an email address or mobile phone number (AKA electronic address), to which the customer may receive a Short Message Service (SMS, or text message), email, or the like.
[0022] As the customer is completing the payment portion of the online transaction, the customer is queried whether he is registered in the payer authorization service. If not, he is given the opportunity to register, which he may decline. If the customer is registered or elects to register, completion of the payment portion of the transaction is suspended while the merchant's credit card transaction processor generates a random code and sends it to the customer by way of the electronic address the customer provided. When the customer receives the random code, the customer inputs the code into a transaction processing window and completes the payment process. The transaction is completed only if the random code matches the code generated by the transaction processor. Of course, all other relevant
portions (account number, credit card expiration date, billing zip code, name on card, etc.) of a typical transaction must match as well.
[0023] Having described embodiments of the present invention generally, attention is directed to Fig. 1, which illustrates an exemplary system 100 according to embodiments of the invention. Those skilled in the art will appreciate that the system 100 is merely exemplary of a number of possible embodiments. For example, the system 100 relates to an online merchant, but other exemplary systems may relate to a merchant having a telephone ordering system.
[0024] According to this exemplary embodiment, a customer, using a customer computing device 102, is communicating with an online merchant 104 via a network 106, such as the Internet. The online merchant may be, for example, a server connected to the Internet, which server hosts an e-commerce web site of the merchant. In ways known to those skilled in the art, the customer selects merchandise or services for purchase from the merchant and initiates a checkout process. At an appropriate point in the checkout process (e.g., after the customer has provided a credit card number), the merchant's online checkout system queries the customer whether the customer has enrolled in "in-process payer authorization." (Those skilled in the art will appreciate that the use of the term "in-process payer authorization" is not intended to be limiting. Herein the term will be used broadly to refer to any process that implements any embodiments of the present invention.) As will be explained in greater detail hereinafter, the customer will be given the opportunity to register if he has not already done so. For purposes of describing this exemplary system embodiment, however, it will be assumed that the customer has registered for in-process payer authorization.
[0025] Once the customer acknowledges having registered for in-process payer authorization, the online merchant 104 sends a transaction record to the merchant's credit card transaction processor 108. The transaction record may include an indication that the customer has registered for in-process payer authorization and wishes to use that service in completing the current transaction. If so, the transaction processor 108 uses this information to locate a record relating to the customer, which record includes the electronic address of the customer. The transaction processor also may generate a random code for transmission to the customer as part of the in-process payer authorization.
[0026] The customer's in-process payer authorization record, that includes the customer's electronic address, may reside in any of several locations, hi some embodiments, the record
is maintained by the merchant's credit card transaction processor 108. This may be the case, for example, if the processor 108 is also the processor for the entity that issued the customer his credit card (i.e., issuer). Li other embodiments, however, the processor 108 may have to communicate via a gateway 110 to a credit card transaction processing network 112, which may be any of the many well known transaction processing networks. The customer's in- process payer authorization record may reside at the gateway 110 or at any of a number of locations throughout the credit card transaction processing network 112. Those skilled in the art will appreciate that many possibilities exist.
[0027] Having located the customer's record and associated electronic address, the transaction processor 108, in some embodiments, sends the transaction record to the gateway 110. The transaction record includes the random code. In these embodiments, the gateway 110 may contact the customer for authorization, as will be described. In other embodiments, the transaction processor 108 may contact the customer for payer authorization as will be described.
[0028] Continuing with a description of the illustrated embodiment, while the customer is checking out of the merchant's online store, the gateway 110 contacts the customer using the customer's electronic address. In this embodiment, the contact is made through a communication network 114, which may be the Internet, a Public Switched Telephone Network (PSTN), and/or the like. The network 114 may communicate with the customer through a wireless link 116.
[0029] In some embodiments, the communication is an email to the customer. In other embodiments, the communication is a SMS message to the customer. In any case, the communication includes the random code. The customer may receive the communication on any of a variety of devices 118, including wired (e.g., a personal computer), or wireless (e.g., cell phone, PDA, etc.) devices. Once the customer receives the communication that includes the random code, the customer enters a confirmation code into an appropriate space in the checkout portion of the merchant's web site (e.g., a dialog box). As will be described, in completing the transaction, the merchant 104 forwards the confirmation code to the transaction processor 108 for comparison to the random code, and the transaction is completed if the codes match.
[0030] As mentioned previously, the foregoing is but one exemplary system 100 according to embodiments of the invention. For example, in an alternative embodiment, the transaction
processor 108 maintains the in-process payer authorization record for the customer. The transaction processor 108 acquires the customer's electronic address from the record, generates the random code, and SMS-messages the code to a cell phone or PDA of the customer. This all takes place before any communication is made from the transaction processor 108 to the gateway 110 and/or transaction processing network 112. Those skilled in the art will appreciate that many other possible embodiments exist.
[0031] Having described exemplary system embodiments, attention is directed to Fig. 2, which illustrates an exemplary method 200 according to embodiments of the invention. The method 200 may be implemented in the system 100 of Fig. 1 or other appropriate system. Those skilled in the art will appreciate that other methods according to other embodiments may have more, fewer, or different blocks than those illustrated and described here. Further, those skilled in the art will appreciate that other methods according to other embodiments may traverse the steps illustrated and described herein in a different order than that depicted.
[0032] The method 200 begins with the optional block 202 of pre-registering a consumer (AKA, payer, customer, card holder) to participate in in-process payer authorization. Any of a variety of entities may offer a consumer/card holder an opportunity to register for the service. For example, an online merchant may offer a frequent customer the opportunity to receive expedited shipping if the customer enrolls in and uses in-process payer authorization for purchases at the merchant's web site. The card holder's processor also may offer the card holder the opportunity to enroll as a means for the customer to provide better security for the card holder's credit card.
[0033] In pre-registering, the card holder creates a record with a credit card transaction processor, such as the processor 108 of Fig. 1. The transaction processor maybe the card holder's transaction processor, although this is not a requirement. The card holder may be required, however, to provide information, for security purposes, that confirms the card holder's identity. In completing the pre-registration process, the card holder provides an electronic address (e.g., email address, cell phone number, etc.) to which in-process payer authorization messages may be directed.
[0034] At block 204, a merchant is registered to provide in-process payer authorization to its customers. This may include a transaction processor working with the merchant to code appropriate procedures into the merchant's web site checkout process. A merchant may be
offered a fee reduction (e.g., a lower "interchange fee," transaction processing fee, and/or the like) for transactions in which a consumer provides in-process payer authorization.
[0035] At block 206, a consumer initiates a transaction with a registered merchant. At an appropriate point in the checkout process (block 208), a determination is made whether the consumer is registered with in-process payer authorization. This may be accomplished by rendering a display screen, such as the display screen 300 of Fig. 3 A, on the consumer's computer. By selecting an appropriate button, the consumer is given an opportunity to register at block 210. Registration at block 210 is substantially similar to consumer pre- registration discussed previously at block 202. If the consumer is already registered and elects to use in-process payer authorization for the current transaction, the process continues at block 212.
[0036] At block 212, the merchant forwards a transaction request to the merchant's credit card transaction processor. The transaction request includes an indication that the consumer intends to use in-process payer authorization for the current transaction. In this specific embodiment, an in-process payer authorization record relating to the consumer resides with the transaction processor, and the transaction processor uses the transaction request to locate the record. The record includes an electronic address for the consumer. The transaction processor then generates a random code and sends the code to a communication device (e.g., cell phone, PDA, personal computer, etc.) of the consumer. This takes place at block 214.
[0037] In response to a display screen rendered on the consumer's computer, such as the display screen 302 of Fig. 3B (which may be a popup window or dialog box), the consumer submits a confirmation code to the merchant. The confirmation code is passed through to the merchant's transaction processor, possibly as part of a transaction authorization or as part of a completed transaction request. At block 216 a decision is made whether the confirmation code provided by the consumer matches the random code generated by the transaction processor. If not, the transaction is denied at block 218. If, however, the confirmation code is received by the transaction processor and matches the random code the transaction processor generated, then the transaction is allowed at block 220.
[0038] 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 and scope of the invention. Additionally, a number of well known processes and elements have not been described in order to avoid unnecessarily obscuring the
present invention. For example, those skilled in the art know how to arrange computers into a network and enable communication among the computers. Moreover, those skilled in the art will appreciate that the concepts discussed herein may be directed toward other types of "card not present" transactions, such as telephone purchases (mail order/telephone order, AKA "MOTO") and the like. Accordingly, the above description should not be taken as limiting the scope of the invention, which is defined in the following claims.
Claims
1. An in-process payer authorization system, comprising: a server computer configured to: host a merchant e-commerce web site; create a purchase transaction record based on a transaction with a customer, wherein the purchase transaction record includes an account identifier of the customer; render a first display screen on a computer of the customer, wherein the first display screen is configured to query whether the customer is registered for in- process payer authorization; include information based on a response to the query in the transaction record; and render a second display screen on the computer of the customer, wherein the second display screen is configured to receive a confirmation code from the customer; a host computer system configured to: receive the transaction record from the server computer; locate an in-process payer authorization record relating to the customer, wherein the in-process payer authorization record includes an electronic address of the customer; generate a random code relating to the purchase transaction; send an electronic communication to the electronic address of the customer, wherein the electronic communication includes the random code; while the transaction with the customer is in progress, receive the confirmation code from the server computer; compare the confirmation code to the random code; and based on the comparison, determine whether to authorize the transaction.
2. The system of claim 1, wherein the electronic address comprises an email address of the customer.
3. The system of claim 1, wherein the electronic communication comprises an SMS message to a mobile phone number of the customer.
4. A method of processing a purchase transaction, comprising: at a host computer system of a credit card processor, receiving a purchase transaction record from a merchant, wherein the purchase transaction record includes an account identifier for a customer; locating a record relating to the customer, wherein the record identifies an electronic address for the customer; generating a random code; sending an electronic message to the electronic address of the customer, wherein the electronic message includes the random code; receiving a communication from the customer via the merchant, wherein the communication includes a code; comparing the code in the communication to the random code; and in response to the comparison, authorizing the purchase transaction.
5. The method of claim 4, wherein the electronic address comprises an email address of the customer.
6. The method of claim 4, wherein sending an electronic message to the electronic address of the customer comprises sending an SMS message to a mobile phone number of the customer.
7. The method of claim 4, further comprising, pre-registering the customer prior to the transaction, wherein pre-registering the customer comprises: receiving a request to register from the customer, wherein the request includes at least the account identifier of the customer and the electronic contact address for the customer; and verifying the electronic address of the customer.
8. The method of claim 4, further comprising, thereafter charging the merchant a reduced interchange rate for the purchase transaction.
9. The method of claim 4, further comprising, thereafter shipping merchandise relating to the transaction to the customer at an expedited rate.
10. A method of processing a purchase transaction, comprising: at a server computer of an online merchant, receiving from a customer a selection of at least one item to be purchased by the customer; initiating a checkout process for the at least one item; sending a transaction record relating to the purchase transaction to a host computer system of a transaction processor, wherein the transaction request includes a presentation instrument account identifier of the customer; using the account identifier to locate a record of the customer, wherein the record includes an electronic address of the customer; at the host computer system of the transaction processor, generating a random code; sending an electronic message to the electronic address of the customer, wherein the electronic message includes the random code; while the checkout process is in progress, receiving a confirmation code from the customer at the merchant server; sending the confirmation code from the merchant server to the host computer system of the transaction processor; at the host computer system of the transaction processor, comparing the confirmation code to the random code; and based on the comparison, authorizing the transaction.
11. The method of claim 10, wherein the electronic address comprises an email address of the customer.
12. The method of claim 10, wherein sending an electronic message to the electronic address of the customer comprises sending an SMS message to a mobile phone number of the customer.
13. The method of claim 10, further comprising, thereafter charging the merchant a reduced interchange rate for the purchase transaction.
14. The method of claim 10, further comprising, thereafter shipping the at least one item to the customer at an expedited rate.
15. The method of claim 10, further comprising, pre-registering the customer prior to the transaction, wherein pre-registering the customer comprises receiving a request to register from the customer, wherein the request includes at least the account identifier of the customer and the electronic address of the customer.
16. An in-process payer authorization system, comprising: means for creating a purchase transaction record based on a transaction with a consumer, wherein the purchase transaction record includes an account identifier of the consumer; means for locating an electronic address of the consumer using the account identifier while the transaction is in process; means for generating a random code relating to the purchase transaction while the transaction is in process; means for transmitting the random code to the electronic address of the consumer; means for receiving a confirmation code from the consumer while the transaction is in process; means for comparing the confirmation code to the random code; and
means for authorizing the transaction based on the comparison while the transaction is in process.
17. The method of claim 16, wherein the means for transmitting the random code to the electronic address of the consumer comprises means for sending an SMS message to a mobile phone of the consumer.
18. The method of claim 16, further comprising means for shipping an item relating to the transaction to the consumer at an expedited rate.
19. The method of claim 16, further comprising means for charging the merchant a reduced interchange rate for the purchase transaction.
20. The method of claim 16, further comprising means for pre-registering the customer prior to the transaction, wherein pre-registering the customer comprises receiving a request to register from the customer, wherein the request includes at least the account identifier of the customer and the electronic address of the customer.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/533,585 | 2006-09-20 | ||
US11/533,585 US20080077526A1 (en) | 2006-09-20 | 2006-09-20 | Online payer authorization systems and methods |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2008036475A2 true WO2008036475A2 (en) | 2008-03-27 |
WO2008036475A3 WO2008036475A3 (en) | 2008-07-31 |
Family
ID=39201823
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2007/075377 WO2008036475A2 (en) | 2006-09-20 | 2007-08-07 | Online payer authorization systems and methods |
Country Status (2)
Country | Link |
---|---|
US (1) | US20080077526A1 (en) |
WO (1) | WO2008036475A2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2015185869A1 (en) * | 2014-06-05 | 2015-12-10 | Orange | Securing an entry in a user database |
Families Citing this family (88)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
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 |
US7451113B1 (en) | 2003-03-21 | 2008-11-11 | Mighty Net, Inc. | Card management system and method |
US8732004B1 (en) | 2004-09-22 | 2014-05-20 | Experian Information Solutions, Inc. | Automated analysis of data to generate prospect notifications based on trigger events |
US8175889B1 (en) | 2005-04-06 | 2012-05-08 | Experian Information Solutions, Inc. | Systems and methods for tracking changes of address based on service disconnect/connect data |
US20070043577A1 (en) * | 2005-08-16 | 2007-02-22 | Sheldon Kasower | Apparatus and method of enabling a victim of identity theft to resolve and prevent fraud |
US8036979B1 (en) | 2006-10-05 | 2011-10-11 | Experian Information Solutions, Inc. | System and method for generating a finance attribute from tradeline data |
US7657569B1 (en) | 2006-11-28 | 2010-02-02 | Lower My Bills, Inc. | System and method of removing duplicate leads |
US7778885B1 (en) | 2006-12-04 | 2010-08-17 | Lower My Bills, Inc. | System and method of enhancing leads |
US8606626B1 (en) | 2007-01-31 | 2013-12-10 | Experian Information Solutions, Inc. | Systems and methods for providing a direct marketing campaign planning environment |
US8606666B1 (en) | 2007-01-31 | 2013-12-10 | Experian Information Solutions, Inc. | System and method for providing an aggregation tool |
US8793184B2 (en) * | 2007-02-12 | 2014-07-29 | Visa U.S.A. Inc. | Mobile payment services |
WO2008147918A2 (en) | 2007-05-25 | 2008-12-04 | Experian Information Solutions, Inc. | System and method for automated detection of never-pay data sets |
US8121942B2 (en) | 2007-06-25 | 2012-02-21 | Visa U.S.A. Inc. | Systems and methods for secure and transparent cardless transactions |
US8099363B1 (en) * | 2007-06-30 | 2012-01-17 | Michael W. Kilchenstein, Jr. | Methods and systems for processing card-not-present financial transactions as card-present financial transactions |
US9990674B1 (en) | 2007-12-14 | 2018-06-05 | Consumerinfo.Com, Inc. | Card registry systems and methods |
US8127986B1 (en) | 2007-12-14 | 2012-03-06 | Consumerinfo.Com, Inc. | Card registry systems and methods |
US8536976B2 (en) * | 2008-06-11 | 2013-09-17 | Veritrix, Inc. | Single-channel multi-factor authentication |
US8006291B2 (en) | 2008-05-13 | 2011-08-23 | Veritrix, Inc. | Multi-channel multi-factor authentication |
US8516562B2 (en) | 2008-05-13 | 2013-08-20 | Veritrix, Inc. | Multi-channel multi-factor authentication |
US8468358B2 (en) | 2010-11-09 | 2013-06-18 | Veritrix, Inc. | Methods for identifying the guarantor of an application |
US10373198B1 (en) | 2008-06-13 | 2019-08-06 | Lmb Mortgage Services, Inc. | System and method of generating existing customer leads |
US8312033B1 (en) | 2008-06-26 | 2012-11-13 | Experian Marketing Solutions, Inc. | Systems and methods for providing an integrated identifier |
US8166297B2 (en) | 2008-07-02 | 2012-04-24 | Veritrix, Inc. | Systems and methods for controlling access to encrypted data stored on a mobile device |
US7991689B1 (en) | 2008-07-23 | 2011-08-02 | Experian Information Solutions, Inc. | Systems and methods for detecting bust out fraud using credit data |
US9256904B1 (en) | 2008-08-14 | 2016-02-09 | Experian Information Solutions, Inc. | Multi-bureau credit file freeze and unfreeze |
US7860772B2 (en) * | 2008-09-30 | 2010-12-28 | Ebay, Inc. | Funding on-line accounts |
EP2353125A4 (en) | 2008-11-03 | 2013-06-12 | Veritrix Inc | User authentication for social networks |
US8060424B2 (en) | 2008-11-05 | 2011-11-15 | Consumerinfo.Com, Inc. | On-line method and system for monitoring and reporting unused available credit |
AU2009311303B2 (en) * | 2008-11-06 | 2015-09-10 | Visa International Service Association | Online challenge-response |
US20110137748A1 (en) * | 2009-12-09 | 2011-06-09 | Yigal Baher | Systems and Methods for Virtual Credit Card Transactions |
US9652802B1 (en) | 2010-03-24 | 2017-05-16 | Consumerinfo.Com, Inc. | Indirect monitoring and reporting of a user's credit data |
US10453093B1 (en) | 2010-04-30 | 2019-10-22 | Lmb Mortgage Services, Inc. | System and method of optimizing matching of leads |
US8744956B1 (en) | 2010-07-01 | 2014-06-03 | Experian Information Solutions, Inc. | Systems and methods for permission arbitrated transaction services |
US8931058B2 (en) | 2010-07-01 | 2015-01-06 | Experian Information Solutions, Inc. | Systems and methods for permission arbitrated transaction services |
WO2012030836A2 (en) * | 2010-09-03 | 2012-03-08 | Visa International Service Association | Protecting express enrollment using a challenge |
US8782217B1 (en) | 2010-11-10 | 2014-07-15 | Safetyweb, Inc. | Online identity management |
US9147042B1 (en) | 2010-11-22 | 2015-09-29 | Experian Information Solutions, Inc. | Systems and methods for data verification |
EP2676197B1 (en) | 2011-02-18 | 2018-11-28 | CSidentity Corporation | System and methods for identifying compromised personally identifiable information on the internet |
US8904289B2 (en) * | 2011-04-21 | 2014-12-02 | Touchstream Technologies, Inc. | Play control of content on a display device |
US9767195B2 (en) | 2011-04-21 | 2017-09-19 | Touchstream Technologies, Inc. | Virtualized hosting and displaying of content using a swappable media player |
US9665854B1 (en) | 2011-06-16 | 2017-05-30 | Consumerinfo.Com, Inc. | Authentication alerts |
US9483606B1 (en) | 2011-07-08 | 2016-11-01 | Consumerinfo.Com, Inc. | Lifescore |
US20130024366A1 (en) * | 2011-07-21 | 2013-01-24 | Ebay, Inc. | Merchant initiated payment using consumer device |
US8474014B2 (en) | 2011-08-16 | 2013-06-25 | Veritrix, Inc. | Methods for the secure use of one-time passwords |
US9106691B1 (en) | 2011-09-16 | 2015-08-11 | Consumerinfo.Com, Inc. | Systems and methods of identity protection and management |
US8738516B1 (en) | 2011-10-13 | 2014-05-27 | Consumerinfo.Com, Inc. | Debt services candidate locator |
US11030562B1 (en) | 2011-10-31 | 2021-06-08 | Consumerinfo.Com, Inc. | Pre-data breach monitoring |
US9853959B1 (en) | 2012-05-07 | 2017-12-26 | Consumerinfo.Com, Inc. | Storage and maintenance of personal data |
US9710805B2 (en) | 2012-06-18 | 2017-07-18 | Paypal, Inc. | Prepaid wallet for merchants |
EP2717207A1 (en) * | 2012-10-05 | 2014-04-09 | Alcatel Lucent | Cloud based payment method |
US9654541B1 (en) | 2012-11-12 | 2017-05-16 | Consumerinfo.Com, Inc. | Aggregating user web browsing data |
US9015813B2 (en) | 2012-11-21 | 2015-04-21 | Jack Bicer | Systems and methods for authentication, verification, and payments |
US8677116B1 (en) | 2012-11-21 | 2014-03-18 | Jack Bicer | Systems and methods for authentication and verification |
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 |
US10255598B1 (en) | 2012-12-06 | 2019-04-09 | Consumerinfo.Com, Inc. | Credit card account data extraction |
US10102570B1 (en) | 2013-03-14 | 2018-10-16 | Consumerinfo.Com, Inc. | Account vulnerability alerts |
US9406085B1 (en) | 2013-03-14 | 2016-08-02 | Consumerinfo.Com, Inc. | System and methods for credit dispute processing, resolution, and reporting |
US9870589B1 (en) | 2013-03-14 | 2018-01-16 | Consumerinfo.Com, Inc. | Credit utilization tracking and reporting |
US8812387B1 (en) | 2013-03-14 | 2014-08-19 | Csidentity Corporation | System and method for identifying related credit inquiries |
US9633322B1 (en) | 2013-03-15 | 2017-04-25 | Consumerinfo.Com, Inc. | Adjustment of knowledge-based authentication |
US10664936B2 (en) | 2013-03-15 | 2020-05-26 | Csidentity Corporation | Authentication systems and methods for on-demand products |
US20160042344A1 (en) * | 2013-04-23 | 2016-02-11 | Naveen Patibandla | Method and system for facilitating online and offline financial transactions |
US10685398B1 (en) | 2013-04-23 | 2020-06-16 | Consumerinfo.Com, Inc. | Presenting credit score information |
US9721147B1 (en) | 2013-05-23 | 2017-08-01 | Consumerinfo.Com, Inc. | Digital identity |
US9443268B1 (en) | 2013-08-16 | 2016-09-13 | Consumerinfo.Com, Inc. | Bill payment and reporting |
US10325314B1 (en) | 2013-11-15 | 2019-06-18 | Consumerinfo.Com, Inc. | Payment reporting systems |
US9477737B1 (en) | 2013-11-20 | 2016-10-25 | Consumerinfo.Com, Inc. | Systems and user interfaces for dynamic access of multiple remote databases and synchronization of data based on user rules |
US10262362B1 (en) | 2014-02-14 | 2019-04-16 | Experian Information Solutions, Inc. | Automatic generation of code for attributes |
US9344419B2 (en) | 2014-02-27 | 2016-05-17 | K.Y. Trix Ltd. | Methods of authenticating users to a site |
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 |
US9892457B1 (en) | 2014-04-16 | 2018-02-13 | Consumerinfo.Com, Inc. | Providing credit data in search results |
US10373240B1 (en) | 2014-04-25 | 2019-08-06 | Csidentity Corporation | Systems, methods and computer-program products for eligibility verification |
US10339527B1 (en) | 2014-10-31 | 2019-07-02 | Experian Information Solutions, Inc. | System and architecture for electronic fraud detection |
US10242019B1 (en) | 2014-12-19 | 2019-03-26 | Experian Information Solutions, Inc. | User behavior segmentation using latent topic detection |
US11151468B1 (en) | 2015-07-02 | 2021-10-19 | Experian Information Solutions, Inc. | Behavior analysis using distributed representations of event data |
US10404675B2 (en) | 2017-08-16 | 2019-09-03 | Bank Of America Corporation | Elastic authentication system |
US10699028B1 (en) | 2017-09-28 | 2020-06-30 | Csidentity Corporation | Identity security architecture systems and methods |
US10896472B1 (en) | 2017-11-14 | 2021-01-19 | Csidentity Corporation | Security and identity verification system and architecture |
US10911234B2 (en) | 2018-06-22 | 2021-02-02 | Experian Information Solutions, Inc. | System and method for a token gateway environment |
US11257078B2 (en) * | 2018-08-20 | 2022-02-22 | Mastercard International Incorporated | Method and system for utilizing blockchain and telecom network for two factor authentication and enhancing security |
US10880313B2 (en) | 2018-09-05 | 2020-12-29 | Consumerinfo.Com, Inc. | Database platform for realtime updating of user data from third party sources |
US11315179B1 (en) | 2018-11-16 | 2022-04-26 | Consumerinfo.Com, Inc. | Methods and apparatuses for customized card recommendations |
US11238656B1 (en) | 2019-02-22 | 2022-02-01 | Consumerinfo.Com, Inc. | System and method for an augmented reality experience via an artificial intelligence bot |
US11941065B1 (en) | 2019-09-13 | 2024-03-26 | Experian Information Solutions, Inc. | Single identifier platform for storing entity data |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070174448A1 (en) * | 2000-04-14 | 2007-07-26 | Arun Ahuja | Method and system for notifying customers of transaction opportunities |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6993658B1 (en) * | 2000-03-06 | 2006-01-31 | April System Design Ab | Use of personal communication devices for user authentication |
US20060020542A1 (en) * | 2004-07-21 | 2006-01-26 | Litle Thomas J | Method and system for processing financial transactions |
US20070192215A1 (en) * | 2006-02-10 | 2007-08-16 | Taylor Thomas B | Computer-implemented registration for providing inventory fulfillment services to merchants |
-
2006
- 2006-09-20 US US11/533,585 patent/US20080077526A1/en not_active Abandoned
-
2007
- 2007-08-07 WO PCT/US2007/075377 patent/WO2008036475A2/en active Application Filing
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070174448A1 (en) * | 2000-04-14 | 2007-07-26 | Arun Ahuja | Method and system for notifying customers of transaction opportunities |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2015185869A1 (en) * | 2014-06-05 | 2015-12-10 | Orange | Securing an entry in a user database |
FR3022054A1 (en) * | 2014-06-05 | 2015-12-11 | Orange | SECURING AN ENTRY INTO A USER DATABASE |
US11978030B2 (en) | 2014-06-05 | 2024-05-07 | Orange | Securing an entry in a user database |
Also Published As
Publication number | Publication date |
---|---|
US20080077526A1 (en) | 2008-03-27 |
WO2008036475A3 (en) | 2008-07-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20080077526A1 (en) | Online payer authorization systems and methods | |
US11587067B2 (en) | Digital wallet system and method | |
KR101947629B1 (en) | Methods and systems for verifying transactions | |
US9111274B2 (en) | Payment processing | |
US9471921B1 (en) | Secure mobile payment authorization | |
US8635157B2 (en) | Mobile system and method for payments and non-financial transactions | |
US7873540B2 (en) | Virtual terminal payer authorization systems and methods | |
US8985445B2 (en) | Payment transaction receipt system and method | |
US11049096B2 (en) | Fault tolerant token based transaction systems | |
US20070063017A1 (en) | System and method for securely making payments and deposits | |
US20110035318A1 (en) | Credit and debit card transaction approval using location verification | |
AU2019283784A1 (en) | Methods and systems for providing 3-D secure service on-behalf-of merchants | |
EP2368224A1 (en) | Mobile barcode generation and payment | |
US20160328701A1 (en) | Mobile point of sale system for reverse settlement, and method thereof | |
JP2009532814A (en) | Method and system for enhancing consumer payments |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07813854 Country of ref document: EP Kind code of ref document: A2 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 07813854 Country of ref document: EP Kind code of ref document: A2 |