US20150248661A1 - Credit account linking system - Google Patents
Credit account linking system Download PDFInfo
- Publication number
- US20150248661A1 US20150248661A1 US14/637,327 US201514637327A US2015248661A1 US 20150248661 A1 US20150248661 A1 US 20150248661A1 US 201514637327 A US201514637327 A US 201514637327A US 2015248661 A1 US2015248661 A1 US 2015248661A1
- Authority
- US
- United States
- Prior art keywords
- customer
- customer information
- credit
- computer
- information
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 claims abstract description 58
- 238000012795 verification Methods 0.000 claims abstract description 36
- 230000000694 effects Effects 0.000 claims description 9
- 238000004590 computer program Methods 0.000 claims 4
- 238000004519 manufacturing process Methods 0.000 claims 3
- 238000010586 diagram Methods 0.000 description 9
- 230000008569 process Effects 0.000 description 5
- 238000013500 data storage Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 239000011800 void material Substances 0.000 description 2
- 230000008901 benefit Effects 0.000 description 1
- 239000011449 brick Substances 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000006073 displacement reaction Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000004570 mortar (masonry) Substances 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 210000003813 thumb Anatomy 0.000 description 1
Images
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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/22—Payment schemes or models
- G06Q20/24—Credit schemes, i.e. "pay after"
-
- 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/08—Payment architectures
- G06Q20/20—Point-of-sale [POS] network systems
-
- 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/22—Payment schemes or models
- G06Q20/227—Payment schemes or models characterised in that multiple accounts are available, e.g. to the payer
-
- 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
- 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
- G06Q20/401—Transaction verification
-
- 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/018—Certifying business or products
- G06Q30/0185—Product, service or business identity fraud
-
- 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
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
Abstract
Description
- This application claims priority to and benefit of co-pending U.S. patent application Ser. No. 61/947,347, filed on Mar. 3, 2014 entitled “DRIVERS LICENSE LOOK-UP” by Tim Pontious, having Attorney Docket No. ADS-063.PRO, and assigned to the assignee of the present application.
- This application is related to co-pending U.S. patent application Ser. No. ______ filed on XXX entitled “DRIVERS LICENSE LOOK-UP”, by Tim Pontious, having Attorney Docket No. ADS-063A, and assigned to the assignee of the present application.
- Presently, when customers forget to take their credit cards with them while shopping, even if the customer has photo identification, the customer is not able to purchase desired goods and services.
- The accompanying drawings, which are incorporated in and form a part of this specification, illustrate various embodiments and, together with the Description of Embodiments, serve to explain principles discussed below. The drawings referred to in this brief description should not be understood as being drawn to scale unless specifically noted.
-
FIG. 1 is a block diagram that illustrates an embodiment of a credit account linker, in accordance with an embodiment. -
FIG. 2 is a block diagram that illustrates an embodiment of a system that includes the credit account linker ofFIG. 1 , in accordance with an embodiment. -
FIG. 3 depicts a flow diagram for a method for linking a customer to a credit account to enable the consumer to purchase items at a store without having the credit card for presentation, in accordance with an embodiment. -
FIG. 4 is a block diagram of an example computer system with which or upon which various embodiments of the present invention may be implemented. - The following is a summary of at least one embodiment of the present technology:
- A method for authorizing access to a customer's credit account is described. The method includes: accessing a set of customer information particular to a customer to achieve an accessed set of customer information; comparing the assessed set of customer information to stored customer information, wherein the stored customer information comprises information associated with a set of customers and is linked to a set of credit accounts associated with the set of customers; based on the comparing, determining if a match between the received set of customer information and the stored customer information exists, wherein if the match exists, identifying a matched stored customer information; identifying a customer credit account, of the set of credit accounts, linked to the matched stored customer information to achieve an identified customer credit account; and generating an a credit verification for the customer, enabling the customer to cause a transactional activity to occur in association with the identified customer credit account. In a further embodiment, the foregoing described method further includes: sending the credit verification to a point of service station.
- Reference will now be made in detail to various embodiments, examples of which are illustrated in the accompanying drawings. While various embodiments are discussed herein, it will be understood that they are not intended to be limiting. On the contrary, the presented embodiments are intended to cover alternatives, modifications and equivalents, which may be included within the spirit and scope the various embodiments as defined by the appended claims. Furthermore, in this Description of Embodiments, numerous specific details are set forth in order to provide a thorough understanding. However, embodiments may be practiced without one or more of these specific details. In other instances, well known methods, procedures, components, and circuits have not been described in detail as not to unnecessarily obscure aspects of the described embodiments.
- Unless specifically stated otherwise as apparent from the following discussions, it is appreciated that throughout the present Description of Embodiments, discussions utilizing terms such as “accessing,” “comparing”, “finding”, “identifying”, “generating”, “sending” or the like, often refer to the actions and processes of an electronic computing device (or portion thereof), module or system, such as, but not limited to, a credit account linking system (See
FIGS. 1 and 2 ). The electronic computing device/module/system transmits, receives, stores, manipulates and/or transforms signals represented as physical (electrical) quantities within the circuits, components, logic, and the like, of the electronic computing device/system into other signals similarly represented as physical electrical quantities within the electronic computing device/system or within or transmitted to other electronic computing devices/systems. - The following definitions apply:
- “Client”: A retail partner of the system described herein for linking a credit account to a consumer.
- “Client System”: the client's Point-of-Service system.
- “Customer”: The client's consumer/customer.
- “Customer Facing Device”: A device that allows direct interaction or communication with customers (such as a signature capture or pin pad device).
- “Driver's License”: The term, “driver's license”, includes any government issued identification. For example, but not limited to such example, a government issued identification may refer to a state issued driver's license, a state identification, a military identification, a federal identification, a locally-issued identification, a province in Canada, etc. The government issued identification may be issued by any governmental authority.
- “Points of Service”: Any channel where a transaction can be processed for a customer (e.g., Catalog, Web, Retail, Mobile, etc.).
- “Request”: The client's system initiated transaction sent to the system described herein for linking a credit account to a customer.
- “Response”: the transactional answer/response the system described herein for linking a credit account to a customer sends to the client.
- “SSN”: Any governmentally assigned social security number (e.g., United States, Canada, etc.).
- Presently, when a customer forgets to take his credit cards with him while shopping, even if the customer has a photo identification, the customer is not able to purchase desired goods and services. Embodiments enable a customer to purchase items at a store location using his credit card account without having his credit card in-hand.
- The following is a high-level non-limiting example of embodiments. In this example, the customer has accidentally left his credit card at home. Embodiments enable the customer to purchase items at a store without having his credit card. For example, the customer selects merchandise to purchase and begins the checkout process. The store associate enters the merchandise into the point of sale (POS) station (e.g., check-out register), totals the transaction, and asks the customer if she would like to place his order on his store-branded credit card. If the customer asks to place an order on his store-branded credit card, the store associate initiates the process of trying to apply the purchase to the customer's store-branded credit card. The store associate initiates this process by selecting an option (of several selectable options) presented at the point of sale station. For example, the selectable options may include, but are not limited to, the following: a new account, a loyalty/database; an account lookup; a transaction; a tender type; a customer; pricing; etc. In this example, the store associate selects the “account lookup” option.
- Before or after selecting the “account lookup” option, the store associate asks the customer to enter personal customer information into the input/output device. In addition to initiating the “account lookup” option, and asking the customer to input his personal information, the store associate also requests a valid photo identification from the customer; the store associate determines if the photo on the valid identification matches the image of the customer.
- The customer enters his personal information into a customer-facing device (input/output device). For example, this personal information may be the last four digits of his social security number. The customer confirms that the information that he entered is correct and “submits” this personal information (via clicking, etc.). In one embodiment, the customer and/or the sales associate scans the customer's driver's license with a two dimensional scanner.
- The submitted personal information (including, in some embodiments, the scanned driver's license information) then is transmitted to a remote server (a server that is remote from the point of service “POS” station). This remote server includes a database of customer information linked with customer credit accounts (in one example, credit card accounts)j. The stored customer information is organized according to an identity of each customer in the database. The identity of each customer is linked to a credit account particular to that consumer. The remote server determines if the personal information that was input by the customer matches any of the stored customer information. Of note, it should be appreciated that the set of customer information includes information that was input from the customer who is trying to purchase items. Whereas, the stored customer information includes information that could potentially relate to the customer.
- If the remote server determines that the personal information submitted by the customer matches stored customer information, then the remote server generates and sends a credit verification to the POS station, validating that a charge may be applied to the customer's credit account. (The customer's credit account is linked to the matched stored customer information for the purchase of the selected items.) If the store associate determines that the customer, who presented the valid photo identification, is that who is indicated in the photo, then the store associate proceeds to charge the customer's credit account (that is linked to the stored customer information having the entered social security information and zip code).
- The following discussion will begin with a description of a credit account linker, with reference to
FIGS. 1 and 2 . The discussion follows with a description of a method of operation, with reference toFIGS. 1-3 . The discussion concludes with a description of an example computer system with which or upon which various embodiments of the present technology may be implemented. - Embodiments of a Credit Account Linker
-
FIGS. 1 and 2 depict block diagrams that illustrates an embodiment of acredit account linker 100 and a system that includes thecredit account linker 100. Thecredit account linker 100 includes the following: acustomer information accessor 105; a customer information comparor 110; amatch determiner 115; a customercredit account identifier 120; and an credit verification generator 125. Thecredit account linker 100 optionally includes ancredit verification sender 130. -
FIG. 1 further depicts thecredit account linker 100 coupled with the customer-facingdevice 155 and thePOS station 160, in one embodiment. - The
customer information accessor 105 is configured for accessing a set of customer information 135 that is particular to acustomer 185. This set of customer information includes a predetermined amount of customer information. For example, in one embodiment, the predetermined amount of customer information is a predetermined number of digits of a social security number of thecustomer 185. For example, the predetermined number of digits is the last four digits of thesocial security number 140 of thecustomer 185. In another embodiment, the predetermined amount of customer information is azip code 145 of thecustomer 185. In yet another embodiment, the predetermined amount of customer information is apassword 150 for thecustomer 185. Of note, the predetermined amount of customer information may be any type and quantity of customer information. The customer-facingdevice 155 provides a request to thecustomer 185 for entry of a predetermined amount of customer information that is particular to thecustomer 185. Further, it should be appreciated that the set of customer information 135 may include one or more pieces of information about thecustomer 185. It should further be appreciated, that in various embodiments, thecustomer 185 may not be the person who is entering the set of customer information 135. A person at a call center or a store associate may be entering the set of customer information 135 into a system, the set of customer information 135, of which, is accessed by thecustomer information accessor 105. - The customer information comparor 110 compares the received set of customer information 135 to the stored
consumer information 170. The set of customer information 135, after being accessed and/or received, is stored at thememory store 165. In one embodiment, thememory store 165 is a database coupled to thecredit account linker 100. In another embodiment, thememory store 165 resides on the memory device described with reference toFIG. 2 . The storedcustomer information 170 includes information associated with a set of customers (e.g., customer A “175A”, customer B “175B”, customer C “175C” and customer n “175 n . . . ” (herein after, “set of customers 175”, unless otherwise specified; of note, the set of customers 175 may be one or more customers) and is linked to a set of credit accounts (e.g.,credit account 180A,credit account 180B,credit account 180C, andcredit account 180 n . . . [hereinafter, “set of credit accounts 180”, unless otherwise specified] [of note, the set of credit accounts may be one or more credit accounts]) associated with the set of customers 175. In other words, a record of personal information for a customer and that customer's credit account information (e.g., credit card account, etc.) is stored at thememory store 165. In another embodiment, the record of personal information for a customer and that customer's credit account information is stored at a memory device separate from thememory store 165. - In one embodiment, a credit card associated with the credit account is a store-branded credit card. The store-branded credit card is associated with an entity (business, not-for-profit organization, etc.) that provides goods and/or services. The “store” may be a merchant that provides goods and/or services, regardless as to whether or not the store is an actual physical place. In other embodiments, the credit card associated with the credit account is not a store-branded credit card. In another embodiment, a credit account is store-branded (“branded-credit account”). In yet another embodiment, a credit account in not a store-branded (“non-branded-credit account”). For example, the credit account may be connected with, but is not limited to being, a retail store, a virtual store, an automobile loan account, etc.
- The
match determiner 115 is configured for, based on the comparing performed by the customer information comparor 110, finding a match between the received set of customer information 135 and the storedcustomer information 170 to achieve a matched storedcustomer information 190. In one embodiment, thematch determiner 115 determines if a predetermined amount of information of the set of customer information 135 that is input by thecustomer 185 is the same as the storedcustomer information 170. Of note, and as discussed herein, the set of customer information 135 may be input by other entities (e.g., store associate, call center employee, etc.) other than thecustomer 185. This predetermined amount of information may be one or more items of information, such as, but not limited to such, the last four digits of the customer's social security number, the zip code of the customer's address, the customer's prearranged password, etc. - If the
match determiner 115 does not find a match, then a matched storedconsumer information 190 is not achieved. Instead, in one embodiment, when thematch determiner 115 does not find a match, a “not found” message is generated by a not found message generator. The not found message is sent to the transmitter (seeFIG. 2 ); the transmitter sends the not found message to thePOS station 160. In receipt of this not found message, thePOS station 160 displays the indication that thecustomer 185 does not have a credit account (as shown by the information stored at the memory store 165); thus, thecredit verification 197 may not be generated. The store associate then has the option to provide thecustomer 185 with the opportunity to create a credit account, via the customer-facingdevice 155 and/or thePOS station 160, with entered customer information that will be linked with a credit account. - The customer
credit account identifier 120 is configured for identifying a customer credit account, of the set of credit accounts 180, linked to the matched storedcustomer information 190 to achieve an identifiedcustomer credit account 195. - The credit verification generator 125 generates a
credit verification 197 for thecustomer 185, such that thecustomer 185 may cause (has the option to cause) a set of charges to be applied to the identifiedconsumer credit account 195. Thecredit verification 197 indicates, at thePOS station 160, that, as to thecustomer 185, a particular transactional activity (e.g., sale, payment, return, void, etc.) is allowed to be processed using the identifiedcustomer credit account 195. In one embodiment, the identifiedcustomer credit account 195 is associated with a store for the particular store at which thecustomer 185 entered into the customer-facingdevice 155 his set of customer information 135. In another embodiment, the identifiedcustomer credit account 195 is associated with a store other than the store at which thecustomer 185 entered his set of customer information 135 into the customer-facingdevice 155. - Additionally, in one embodiment, the
credit verification 197 includes information in addition to the determination of allowing thecustomer 185 to cause a transactional activity to be processed using thecustomer credit account 195, such as, but not limited to, the following types of information: the customer's 185 amount of available credit remaining; the sales history for thecustomer 185; rewards and loyalty information connected with the customer's 185customer credit account 195; and offers, such as reward incentives, for thecustomer 185. - The
credit verification sender 130 sends thecredit verification 197 to a transmitter. The transmitter transmits thecredit verification 197 to the point ofservice station 160, as will be described below with reference to thesystem 200 for linking a customer to a credit account to enable the consumer to purchase items at a store without having his credit card for presentation to the store associate. As already noted herein, the point ofservice station 160 may be any channel at which a transaction can be processed for a customer (e.g., Catalog, Web, Retail, Mobile, etc.), and is not limited to being that of a “brick and mortar” retail store. -
FIG. 2 illustrates asystem 200 for linking a customer to a credit account to enable a customer to purchase items at a store without having a credit card for presentation to the store associate. Thesystem 200 is located at a server that is remote from and communicatively coupled with, via wire and/or wirelessly, to the customer-facingdevice 155 and/or thePOS station 160. In another embodiment, thesystem 200 is a server that is remote from and communicatively coupled with, via wire and/or wirelessly, to the customer-facingdevice 155 and/or thePOS station 160. In one embodiment, thesystem 200 includes the following: thecredit account linker 100; areceiver 205; aprocessor 210; and atransmitter 215. In one embodiment, thesystem 200 further includes amemory store 165. In another embodiment, thememory store 165 resides remote from, but is coupled with, thesystem 200. In other words, thememory store 165 resides at a third party, and is communicatively couple with, via wire and/or wirelessly, thesystem 200. In one embodiment, thesystem 200 includes abar code scanner 220. Thebar code scanner 220 is communicatively coupled with, via wire and/or wirelessly, the customer-facingdevice 155 and/or thePOS station 160. In one embodiment, thebar code scanner 220 is a two dimensional scanner, known in the art, and enabled to scan the bar code on a form of identification, such as, but not limited to, a drivers' license. Of note, thebar code scanner 220 does not have to be at a store. Thebar code scanner 220 may be attached to a device located remotely from the store, such as a desktop computer or a mobile device (e.g., phone, tablet, laptop computer, etc.) Thecredit account linker 100 accesses the information captured by thebar code scanner 220. Thecredit account linker 100 also uses this captured information, as part of the set of customer information 135. - The
system 200 is communicatively coupled, via wire and/or wirelessly, to the customer-facingdevice 155 and thePOS station 160. In one embodiment, the customer-facingdevice 155 and thePOS station 160 are communicatively coupled, via wire and/or wirelessly, to each other. - In one embodiment, the
receiver 205 is configured to receive the set of customer information 135. In one embodiment, thereceiver 205 receives the set of customer information 135 from the customer-facingdevice 155. In another embodiment, thereceiver 205 receives the set of customer information 135 from thePOS station 160. - In one embodiment, the
processor 210 is configured to process the computer-readable and computer-executable instructions (that may reside in any tangible computer readable storage media) such as the following modules described herein: thecustomer information accessor 105; the customer information comparor 110; thematch determiner 115; the customercredit account identifier 120; the credit verification generator 125; and thecredit verification sender 130. - The following discussion sets forth in detail some example methods of operation of embodiments. With reference to
FIGS. 1-3 , flow diagrams ofmethod 300 illustrates an example procedure used by various embodiments.Method 300 includes some procedures that, in various embodiments, are carried out by a processor under the control of computer-readable and computer-executable instructions. In various embodiments, these computer-readable and computer-executable instructions are described as “code segments”, and presented separately (e.g., first codes segment, second code segment, etc.) to describe such instructions. In this fashion, procedures described herein and in conjunction with these flow diagrams, alone or in combination, are, or may be, implemented using a computer, in various embodiments. The computer-readable and computer-executable instructions can reside in any tangible computer readable storage media. Some non-limiting examples of tangible computer readable storage media include random access memory, read only memory, magnetic disks, and optical disks, solid-state disks, any or all of which may be employed within a virtualization infrastructure. The computer-readable and computer-executable instructions, which reside on tangible computer readable storage media, are used to control or operate in conjunction with, for example, one or some combination of processors of a virtual machine. It is appreciated that the processor(s) may be physical or virtual or some combination (it should also be appreciated that a virtual processor is implemented on physical hardware). Although specific procedures are disclosed inmethod 300, such procedures are examples. That is, embodiments are well suited to performing various other procedures or variations of the procedures recited inmethod 300, alone or in combination. Likewise, in some embodiments, the procedures inmethod 300, alone or in combination, may be performed in an order different than presented and/or not all of the procedures described in one or more of these flow diagrams may be performed. It is further appreciated that procedures described inmethod 300, alone or in combination, may be implemented in hardware, or a combination of hardware with firmware and/or software. -
FIG. 3 is a flow diagram of amethod 300 for linking a customer to a credit account to enable the customer to purchase an item(s) at a store without having the credit card for presentation, in accordance with an embodiment. Although specific procedures are disclosed inmethod 300, embodiments are well suited to performing various other procedures or variations of the procedures recited inmethod 300. It is appreciated that the procedures inmethod 300 may be performed in an order different than presented, that not all of the procedures inmethod 300 may be performed, and that additional procedures to those illustrated and described may be performed. All of, or a portion of, the procedures described bymethod 300 can be implemented by a processor or computer system executing instructions which reside, for example, on computer-usable/readable media. The following discussion ofmethod 300 referencesFIGS. 1-4 unless specifically noted otherwise. - At
step 305 ofmethod 300, in one embodiment and as described herein, the set of customer information 135 particular to thecustomer 185 is accessed to achieve an accessed set of customer information 135. In one embodiment, the set of customer information 135 includes a predetermined amount of customer information particular to thecustomer 185. The predetermined amount of customer information particular to thecustomer 185 may be any kind and amount of information that may be accessed (received or captured) at thecredit account linker 100, and may be transmitted via one or more components of the customer-facingdevice 155 and/or thePOS station 160. - At step 310 of
method 300 in one embodiment, and as described herein, the accessed set of customer information is compared to the storedcustomer information 170, wherein the storedcustomer information 170 includes information associated with the set of customers 175 and is linked to a set of credit accounts 180 associated with the set of customers 175. In one embodiment, the credit cards associated with the credit accounts 180 are credit cards. In another embodiment, the credit cards associated with the credit accounts 180 are credit cards associated with a store different from the store in which the customer enters the set of customer information 135 into the customer-facingdevice 155. - At
step 315 ofmethod 300, in one embodiment, and as described herein, based on the comparing performed at step 310, a match between the received set of customer information 135 and the storedcustomer information 170 is determined if it exists. If the match is found to exist, then the matched storedcustomer information 190 is identified. - At
step 320 ofmethod 300, in one embodiment, and as described herein, a customer credit account, of the set of credit accounts 180, which is linked to the matched storedcustomer information 170, is identified to achieve an identifiedcustomer credit account 195. - At
step 325, in one embodiment and as described herein, acredit verification 197 for thecustomer 185 is generated. Thecredit verification 197 indicates, at thePOS station 160, that, as to thecustomer 185, a particular transactional activity (e.g., sale, payment, return, void, etc.) is allowed to be processed using the identifiedcustomer credit account 195. It should be appreciated that thecredit verification 197 may allow more than one transactional activities. Atstep 330, in one embodiment, if the match, as determined instep 315, does not exist, then a “not found” message is generated. The not found message indicates, via thePOS station 160 that the match is determined to not exist. - At step 335, in one embodiment and as described herein, the
credit verification 197 is sent to thePOS station 160. In one embodiment, the sending of thecredit verification 197 to thePOS station 160 includes sending thecredit verification 197 to thetransmitter 215. Thetransmitter 215 then transmits thiscredit verification 197 to thePOS station 160. As noted herein, thePOS station 160 may be any channel at which a transaction can be processed for a customer (e.g., Catalog, Web, Retail, Mobile, etc.) - With reference now to
FIG. 4 , all or portions of some embodiments described herein are composed of computer-readable and computer-executable instructions that reside, for example, in computer-usable/computer-readable storage media of a computer system. That is,FIG. 4 illustrates one example of a type of computer (computer system 400) that can be used in accordance with or to implement various embodiments which are discussed herein. For example, thecomputer system 400 may be used to implement the modules of thecredit account linker 100 and portions of thesystem 200 described herein. It is appreciated thatcomputer system 400 ofFIG. 4 is only an example and that embodiments as described herein can operate on or within a number of different computer systems including, but not limited to, general purpose networked computer systems, embedded computer systems, routers, switches, server devices, client devices, various intermediate devices/nodes, stand alone computer systems, distributed computer systems, media centers, handheld computer systems, multi-media devices, and the like.Computer system 400 ofFIG. 4 is well adapted to having peripheral non-transitory computer-readable storage media 402 such as, for example, a floppy disk, a compact disc, digital versatile disc, other disc based storage, universal serial bus “thumb” drive, removable memory card, and the like coupled thereto. -
System 400 ofFIG. 4 includes an address/data bus 404 for communicating information, and aprocessor 406A coupled with bus 404 for processing information and instructions. As depicted inFIG. 4 ,system 400 is also well suited to a multi-processor environment in which a plurality ofprocessors system 400 is also well suited to having a single processor such as, for example,processor 406A.Processors System 400 also includes data storage features such as a computer usable volatile memory 408, e.g., random access memory (RAM), coupled with bus 404 for storing information and instructions forprocessors -
System 400 also includes computer usable non-volatile memory 410, e.g., read only memory (ROM), coupled with bus 404 for storing static information and instructions forprocessors system 400 is a data storage unit 412 (e.g., a magnetic or optical disk and disk drive) coupled with bus 404 for storing information and instructions.System 400 also includes an optionalalphanumeric input device 414 including alphanumeric and function keys coupled with bus 404 for communicating information and command selections toprocessor 406A orprocessors System 400 also includes an optionalcursor control device 416 coupled with bus 404 for communicating user input information and command selections toprocessor 406A orprocessors system 400 also includes anoptional display device 418 coupled with bus 404 for displaying information. - Referring still to
FIG. 4 ,optional display device 418 ofFIG. 4 may be a liquid crystal device, cathode ray tube, plasma display device or other display device suitable for creating graphic images and alphanumeric characters recognizable to a user. Optionalcursor control device 416 allows the computer user to dynamically signal the movement of a visible symbol (cursor) on a display screen ofdisplay device 418 and indicate user selections of selectable items displayed ondisplay device 418. Many implementations ofcursor control device 416 are known in the art including a trackball, mouse, touch pad, joystick or special keys onalphanumeric input device 414 capable of signaling movement of a given direction or manner of displacement. Alternatively, it will be appreciated that a cursor can be directed and/or activated via input fromalphanumeric input device 414 using special keys and key sequence commands.System 400 is also well suited to having a cursor directed by other means such as, for example, voice commands.System 400 also includes an I/O device 420 forcoupling system 400 with external entities. For example, in one embodiment, I/O device 420 is a modem for enabling wired or wireless communications betweensystem 400 and an external network such as, but not limited to, the Internet. - Referring still to
FIG. 4 , various other components are depicted forsystem 400. Specifically, when present, anoperating system 422,applications 424, modules 726, anddata 428 are shown as typically residing in one or some combination of computer usable volatile memory 408 (e.g., RAM), computer usable non-volatile memory 410 (e.g., ROM), anddata storage unit 412. In some embodiments, all or portions of various embodiments described herein are stored, for example, as anapplication 424 and/ormodule 426 in memory locations within RAM 408, computer-readable storage media withindata storage unit 412, peripheral computer-readable storage media 402, and/or other tangible computer-readable storage media.
Claims (19)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/637,327 US20150248661A1 (en) | 2014-03-03 | 2015-03-03 | Credit account linking system |
US14/637,318 US9256866B2 (en) | 2014-03-03 | 2015-03-03 | Drivers license look-up |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201461947347P | 2014-03-03 | 2014-03-03 | |
US14/637,327 US20150248661A1 (en) | 2014-03-03 | 2015-03-03 | Credit account linking system |
Publications (1)
Publication Number | Publication Date |
---|---|
US20150248661A1 true US20150248661A1 (en) | 2015-09-03 |
Family
ID=54006962
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/637,318 Active US9256866B2 (en) | 2014-03-03 | 2015-03-03 | Drivers license look-up |
US14/637,327 Pending US20150248661A1 (en) | 2014-03-03 | 2015-03-03 | Credit account linking system |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/637,318 Active US9256866B2 (en) | 2014-03-03 | 2015-03-03 | Drivers license look-up |
Country Status (1)
Country | Link |
---|---|
US (2) | US9256866B2 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10332427B2 (en) | 2014-06-30 | 2019-06-25 | Alibaba Group Holding Limited | Processing electronic payments using at least two payment tools for a transaction |
US10580025B2 (en) | 2013-11-15 | 2020-03-03 | Experian Information Solutions, Inc. | Micro-geographic aggregation system |
US10678894B2 (en) | 2016-08-24 | 2020-06-09 | Experian Information Solutions, Inc. | Disambiguation and authentication of device users |
US10936629B2 (en) | 2014-05-07 | 2021-03-02 | Consumerinfo.Com, Inc. | Keeping up with the joneses |
US11010345B1 (en) | 2014-12-19 | 2021-05-18 | Experian Information Solutions, Inc. | User behavior segmentation using latent topic detection |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10325250B2 (en) * | 2014-12-10 | 2019-06-18 | Meijer, Inc. | System and method for linking POS purchases to shopper membership accounts |
US20200104834A1 (en) * | 2018-10-02 | 2020-04-02 | Comenity Llc | Using a customer id in a mobile wallet to make a transaction |
US11164178B2 (en) | 2019-04-04 | 2021-11-02 | Comenity Llc | Adding a credit account to a mobile wallet to make a transaction when the physical card associated with the credit account is unavailable |
JP7357244B2 (en) * | 2019-09-09 | 2023-10-06 | パナソニックIpマネジメント株式会社 | Store usage information distribution device, store usage information distribution system equipped with the same, and store usage information distribution method |
Citations (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080275779A1 (en) * | 2007-02-12 | 2008-11-06 | Dhamodharan Lakshminarayanan | Mobile payment services |
US20090068982A1 (en) * | 2007-09-10 | 2009-03-12 | Microsoft Corporation | Mobile wallet and digital payment |
US20090106152A1 (en) * | 2007-10-17 | 2009-04-23 | The Western Union Company | Money transfers utilizing unique receiver identifier |
US20100125510A1 (en) * | 2008-11-17 | 2010-05-20 | Smith Steven M | System and method of conducting transactions using a mobile wallet system |
US20120265682A1 (en) * | 2011-03-04 | 2012-10-18 | Citibank, N.A. | Methods and Systems Using Contactless Card |
US20120310826A1 (en) * | 2011-06-03 | 2012-12-06 | Saurav Chatterjee | Virtual wallet card selection apparatuses, methods and systems |
US8346672B1 (en) * | 2012-04-10 | 2013-01-01 | Accells Technologies (2009), Ltd. | System and method for secure transaction process via mobile device |
US20130132219A1 (en) * | 2011-11-21 | 2013-05-23 | Mozido, Llc | Using a mobile wallet infrastructure to support multiple mobile wallet providers |
US20130346305A1 (en) * | 2012-06-26 | 2013-12-26 | Carta Worldwide Inc. | Mobile wallet payment processing |
US20140006276A1 (en) * | 2012-06-28 | 2014-01-02 | Bank Of America Corporation | Mobile wallet account number differentiation |
US8639621B1 (en) * | 2012-04-25 | 2014-01-28 | Wells Fargo Bank, N.A. | System and method for a mobile wallet |
US20140129441A1 (en) * | 2012-11-02 | 2014-05-08 | German Blanco | Systems and methods for authorizing sensitive purchase transactions with a mobile device |
US20140172577A1 (en) * | 2012-12-19 | 2014-06-19 | Capital One Financial Corporation | System and method for triggering mobile device functionality using a payment card |
US20140207680A1 (en) * | 2011-10-17 | 2014-07-24 | Capital One Financial Corporation | System and method for providing a mobile wallet shopping companion application |
US20140250005A1 (en) * | 2009-05-01 | 2014-09-04 | Amazon Technologies, Inc. | Real-time mobile wallet server |
US8856045B1 (en) * | 2013-12-18 | 2014-10-07 | PayRange Inc. | Mobile-device-to-machine payment systems |
US8905303B1 (en) * | 2013-09-01 | 2014-12-09 | Mourad Ben Ayed | Method for adaptive wireless payment |
US20150106216A1 (en) * | 2013-10-15 | 2015-04-16 | Intuit Inc. | Methods systems and computer program products for verifying consumer identity during transaction |
US20150178693A1 (en) * | 2013-12-20 | 2015-06-25 | Eric A. Solis | Financial services ecosystem |
US20150278805A1 (en) * | 2012-10-01 | 2015-10-01 | Acuity Systems, Inc. | Authentication system |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6224109B1 (en) * | 1999-08-07 | 2001-05-01 | James Yung Chien Yang | Credit card with driver's license or identification |
US20020147679A1 (en) * | 2001-04-06 | 2002-10-10 | Tardif Ronald L. | Credit card driver's license |
US20080217400A1 (en) * | 2007-03-06 | 2008-09-11 | Portano Michael D | System for preventing fraudulent purchases and identity theft |
-
2015
- 2015-03-03 US US14/637,318 patent/US9256866B2/en active Active
- 2015-03-03 US US14/637,327 patent/US20150248661A1/en active Pending
Patent Citations (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080275779A1 (en) * | 2007-02-12 | 2008-11-06 | Dhamodharan Lakshminarayanan | Mobile payment services |
US20090068982A1 (en) * | 2007-09-10 | 2009-03-12 | Microsoft Corporation | Mobile wallet and digital payment |
US20090106152A1 (en) * | 2007-10-17 | 2009-04-23 | The Western Union Company | Money transfers utilizing unique receiver identifier |
US20100125510A1 (en) * | 2008-11-17 | 2010-05-20 | Smith Steven M | System and method of conducting transactions using a mobile wallet system |
US20140250005A1 (en) * | 2009-05-01 | 2014-09-04 | Amazon Technologies, Inc. | Real-time mobile wallet server |
US20120265682A1 (en) * | 2011-03-04 | 2012-10-18 | Citibank, N.A. | Methods and Systems Using Contactless Card |
US20120310826A1 (en) * | 2011-06-03 | 2012-12-06 | Saurav Chatterjee | Virtual wallet card selection apparatuses, methods and systems |
US20140207680A1 (en) * | 2011-10-17 | 2014-07-24 | Capital One Financial Corporation | System and method for providing a mobile wallet shopping companion application |
US20130132219A1 (en) * | 2011-11-21 | 2013-05-23 | Mozido, Llc | Using a mobile wallet infrastructure to support multiple mobile wallet providers |
US8346672B1 (en) * | 2012-04-10 | 2013-01-01 | Accells Technologies (2009), Ltd. | System and method for secure transaction process via mobile device |
US8639621B1 (en) * | 2012-04-25 | 2014-01-28 | Wells Fargo Bank, N.A. | System and method for a mobile wallet |
US20130346305A1 (en) * | 2012-06-26 | 2013-12-26 | Carta Worldwide Inc. | Mobile wallet payment processing |
US20140006276A1 (en) * | 2012-06-28 | 2014-01-02 | Bank Of America Corporation | Mobile wallet account number differentiation |
US20150278805A1 (en) * | 2012-10-01 | 2015-10-01 | Acuity Systems, Inc. | Authentication system |
US20140129441A1 (en) * | 2012-11-02 | 2014-05-08 | German Blanco | Systems and methods for authorizing sensitive purchase transactions with a mobile device |
US20140172577A1 (en) * | 2012-12-19 | 2014-06-19 | Capital One Financial Corporation | System and method for triggering mobile device functionality using a payment card |
US8905303B1 (en) * | 2013-09-01 | 2014-12-09 | Mourad Ben Ayed | Method for adaptive wireless payment |
US20150106216A1 (en) * | 2013-10-15 | 2015-04-16 | Intuit Inc. | Methods systems and computer program products for verifying consumer identity during transaction |
US8856045B1 (en) * | 2013-12-18 | 2014-10-07 | PayRange Inc. | Mobile-device-to-machine payment systems |
US20150178693A1 (en) * | 2013-12-20 | 2015-06-25 | Eric A. Solis | Financial services ecosystem |
Non-Patent Citations (2)
Title |
---|
Collins English Dictionary – Complete & Unabridged 2012 Digital Edition (2012). Definition of "coupled". * |
Collins English Dictionary â Complete & Unabridged 2012 Digital Edition (2012). Definition of "coupled". * |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10580025B2 (en) | 2013-11-15 | 2020-03-03 | Experian Information Solutions, Inc. | Micro-geographic aggregation system |
US10936629B2 (en) | 2014-05-07 | 2021-03-02 | Consumerinfo.Com, Inc. | Keeping up with the joneses |
US11620314B1 (en) | 2014-05-07 | 2023-04-04 | Consumerinfo.Com, Inc. | User rating based on comparing groups |
US10332427B2 (en) | 2014-06-30 | 2019-06-25 | Alibaba Group Holding Limited | Processing electronic payments using at least two payment tools for a transaction |
US10916160B2 (en) | 2014-06-30 | 2021-02-09 | Advanced New Technologies Co., Ltd. | Processing electronic payments using at least two payment tools for a transaction |
US11010345B1 (en) | 2014-12-19 | 2021-05-18 | Experian Information Solutions, Inc. | User behavior segmentation using latent topic detection |
US10678894B2 (en) | 2016-08-24 | 2020-06-09 | Experian Information Solutions, Inc. | Disambiguation and authentication of device users |
US11550886B2 (en) | 2016-08-24 | 2023-01-10 | Experian Information Solutions, Inc. | Disambiguation and authentication of device users |
Also Published As
Publication number | Publication date |
---|---|
US9256866B2 (en) | 2016-02-09 |
US20150248726A1 (en) | 2015-09-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20150248661A1 (en) | Credit account linking system | |
JP6178790B2 (en) | Payment device with embedded chip | |
US10210565B2 (en) | Systems and methods for facilitating a transaction relating to newly identified items using augmented reality | |
US20170262832A1 (en) | Systems and Methods for Use in Facilitating Payment Account Transactions | |
US9123040B2 (en) | Systems and methods for encoded alias based transactions | |
US20220237602A1 (en) | Authorizing a purchase transaction using a mobile device | |
US20160019528A1 (en) | System and method for payment and settlement using barcode | |
US20150379514A1 (en) | Systems and methods for transaction pre authentication | |
US20180197176A1 (en) | In-store mobile payment | |
US20170287018A1 (en) | Methods and systems for performing an advertisement-based electronic transaction | |
US10380619B2 (en) | Drivers license parser | |
US20220027891A1 (en) | Adding a credit account to a mobile wallet to make a transaction when the physical card associated with the credit account is unavailable | |
US20180247287A1 (en) | Methods and systems for performing a mobile-to-business anywhere ecommerce transaction using a mobile device | |
US10567912B2 (en) | System for tracking physical objects | |
US10726425B2 (en) | Custom communication generator | |
US20140244504A1 (en) | Methods and systems for processing electronic transactions and managing vehicle costs | |
US20170213271A1 (en) | System, method, and non-transitory computer-readable storage media related to providing real-time price matching | |
US11853995B2 (en) | Systems and methods for processing encoded symbols to facilitate secured communication between database systems of two entities and to update database tuples associated with the database systems | |
US20130211899A1 (en) | Consumer promotion management system | |
US20170236116A1 (en) | Apparatus, system and method for creating a restricted use payment card | |
CN110235161B (en) | System and method for collecting device data from digital wallet authentication | |
US20150317642A1 (en) | Process to query electronic sales receipts with a portable computerized device | |
US20140149291A1 (en) | System and method for electronic commerce | |
KR20140010295A (en) | Payment method and mobile terminal using the same | |
US10635995B2 (en) | Systems and methods for facilitating event access through payment accounts |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: COMENITY LLC, OHIO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PONTIOUS, TIM;REEL/FRAME:036672/0561 Effective date: 20150717 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STCV | Information on status: appeal procedure |
Free format text: NOTICE OF APPEAL FILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
AS | Assignment |
Owner name: BREAD FINANCIAL PAYMENTS, INC., OHIO Free format text: MERGER AND CHANGE OF NAME;ASSIGNORS:COMENITY LLC;BREAD FINANCIAL PAYMENTS, INC;REEL/FRAME:063125/0756 Effective date: 20221025 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |