TECHNICAL FIELDThe subject matter described herein relates generally to computer systems for consolidated registration of payment cards. More particularly, the subject matter described herein relates to methods, systems, and computer readable media for registering digital payment cards in a digital wallet with a fraud detection engine executing on a computer system.
BACKGROUNDPayment network and bank computer systems are typically configured to analyze transactions for fraud in the use of payment cards. Payment card fraud can be, e.g., counterfeit fraud, which involves counterfeit payment cards being used fraudulently at ATMs and point-of-sale (POS) devices, often in a foreign country relative to the cardholder's home country. To address this problem, some bank computer systems are programmed to sometimes deny transactions from countries where such fraud is common unless the cardholder alerts the payment card issuer of his travels to that country. For instance, when a cardholder travels to a country where counterfeit fraud is currently a problem, the bank computer system may deny the cardholder's transactions with a payment card unless the cardholder previously registered the payment card for travel with the bank computer system. Registering payment cards can be technically challenging where multiple computer systems are involved. Registering payment cards can also be inconvenient to users.
In light of these difficulties, there exists a need for methods, systems, and computer readable media for consolidated registration of payment cards.
SUMMARYThe subject matter described herein relates to methods, systems, and computer readable media for consolidated registration of payment cards. In some examples, a method includes receiving, by a travel registration manager implemented on at least one processor, data specifying a geographic location and one or more dates of travel to the geographic location for the user. The method includes receiving, by the travel registration manager, a selection of a plurality of digital payment cards from a first digital wallet for a user. The method includes registering, by the travel registration manager and with a fraud detection engine executing on a computer system, the plurality of digital payment cards for the user and the dates of travel to the geographic location, thereby causing the fraud detection engine to modify a risk score of at least a first transaction initiated by the user during the dates of travel and within a threshold geographic distance of the geographic location. In addition, the mobile devices (e.g., phone or smart watch) associated with the digital cards can be registered in the travel registration database. At the time of the payment, the location of the consumer may be verified either through the capability of the mobile payment application or phone. In the former case, the transaction is also authenticated, giving a better fraud score.
The subject matter described in this specification may be implemented in hardware, software, firmware, or combinations of hardware, software and/or firmware. In some examples, the subject matter described in this specification may be implemented using a non-transitory computer readable medium storing computer executable instructions that when executed by one or more processors of a computer cause the computer to perform operations. Computer readable media suitable for implementing the subject matter described in this specification include non-transitory computer-readable media, such as disk memory devices, chip memory devices, programmable logic devices, random access memory (RAM), read only memory (ROM), optical read/write memory, cache memory, magnetic read/write memory, flash memory, and application specific integrated circuits. In addition, a computer readable medium that implements the subject matter described in this specification may be located on a single device or computing platform or may be distributed across multiple devices or computing platforms.
BRIEF DESCRIPTION OF THE DRAWINGSFIG. 1 is a block diagram of an example communications environment for consolidated registration of payment cards;
FIG. 2 is a block diagram of an example communications environment for initiation a transaction using a payment card registered for travel;
FIGS. 3A-B are screen shots illustrating a user registering payment cards for travel;
FIG. 4 is a flow chart of an example method for consolidated registration of payment cards; and
FIG. 5 is a flow chart of an example method illustrating a first transaction approved as a result of registering digital payment cards.
DETAILED DESCRIPTIONFIG. 1 is a block diagram of anexample communications environment100 for consolidated registration of payment cards.Environment100 includes apayment network server102 configured, by virtue of appropriate programming, for receiving requests from merchants, typically through a merchant acquirer or other appropriate entity depending on the card processing network, for authorization of payment card transactions against a payment card account of a customer.
In operation,payment network server102 registers payment cards for travel for auser104.Payment network server102 can register both digital payment cards in digital wallets foruser104 and physical payment cards in a single interaction withuser104, which can reduce the processing load and networking load associated with registering multiple payment cards.Payment network server102 can also simplify the technical aspects of the storage and transmission of protected data between computer systems. Furthermore,payment network server102 can improve the user experience foruser104 by simplifying the process for registering multiple payment cards, which can also result in fewer declined transactions for users in general.
As illustrated inFIG. 1,user104 is operating first and seconduser computer devices106 and108, which can be, for example, a mobile phone and a tablet computer.Environment100 also includes a packet-baseddata communications network110, e.g., the Internet.Environment100 can include other computer systems that facilitate electronic payment transactions, including a bankfraud detection engine128 executing on a system of one or more computers, a travelbooking computer system130, and a different merchant computer system.
Payment network server102 can be a distributed computing system that includes one ormore processors112 andmemory114.Memory114 stores instructions forprocessors112 that can be loaded, e.g., into random access memory (RAM), and executed byprocessors112 to causeprocessors112 to perform operations for registering payment cards.Payment network server102 implements, usingprocessors112 andmemory114, atravel registration manager116, adigital wallet server118, a networkfraud detection engine120, and anauthentication server122.
Travel registration manager116 is configured for receiving, using packet-baseddata communications network110, data specifying a geographic location and one or more dates of travel to the geographic location for a user. The data specifying the geographic location can include any appropriate type of data for specifying geographic locations, for example, zip codes; county, state, country names; and latitude and longitude or global positioning system (GPS) coordinates. The data specifying the dates typically specifies days of the year that the user is planning on travelling to the geographic location, but any appropriate type of data specifying a time or range of times can be used.Travel registration manager116 is also configured to receive device specific information, e.g., device ID, for device or consumer identification.
Travel registration manager116 is configured for receiving a selection of digital payment cards from a first digital wallet foruser104. For example, suppose thatuser computer device106 hosts the first digital wallet foruser104.User104 can use a graphical user interface (GUI) displayed onuser computer device106 to select some or all of the digital payment cards hosted on the first digital wallet. The GUI can be, e.g., a web site hosted bytravel registration manager116 and displayed in a web browser executing onuser computer device106.User computer device106 transmits a message over packet-baseddata communications network110 totravel registration manager116 that specifies the selected digital payment cards and device ID.
Travel registration manager116 is configured for registering, with a fraud detection engine executing on a computer system, the selected digital payment cards, mapped physical cards, devices (mobile phone or smart watch) for the user and the dates of travel to the geographic location. For example, the fraud detection engine can be networkfraud detection engine120, which executes onpayment network server102. In another example,travel registration manager116 alternatively or additionally registers the selected digital payment cards with bankfraud detection engine128. Registering the digital payment cards includes transmitting a message to the fraud detection engine, which in response accesses a database storing records for digital payment cards. The fraud detection engine can add, to a record for each of the digital payment cards, the data specifying the geographic location and the dates of travel to the geographic location or a reference to the data.
Fraud detection engine120 can then use the registration in analyzing transactions to produce fraud scores. Whenfraud detection engine120 receives data specifying a transaction,fraud detection engine120 accesses the record in the database for the digital payment card used in the transaction. If the digital payment card, physical card or device has been registered and the transaction matches the date and geographic location of the registration, thenfraud detection engine120 modifies a risk score of the transaction, e.g., by reducing the risk score since the transaction is less likely to be fraudulent given that the user registered the digital payment card.
Travel registration manager116 is configured to register multiple payment cards withfraud detection engine120 in a single interaction withuser104. Registering multiple payment cards in a single interaction can be useful, e.g., for reducing the processing and networking overhead associated with multiple transactions on multiple computer systems, and for reducing the time it takesuser104 to register multiple payment cards on different computer systems. Registering multiple payment cards in a single interaction with the user improves the accuracy of fraud detection byfraud detection engine120 and improves the user experience by reducing the likelihood of a legitimate transaction inadvertently being declined in an effort to reduce fraud.
Travel registration manager116 can register multiple payment cards in a single interaction in a number of different ways. As described above,travel registration manager116 can register multiple digital payment cards selected from a digital wallet foruser104, even where the multiple digital payment cards are issued from different banks or associated with different payment networks. In the case where some of the digital payment cards are associated with different banks and payment networks, travelregistration manager116 can access a database storing registration instructions. The database can be populated by a system administrator or by a bank or payment network using an application programming interface (API).Travel registration manager116 registers, by executing appropriate software, with the different banks and payment networks using the registration instructions.
Travel registration manager116 can optionally also register any other payment cards associated with the selected digital payment cards. For example, a digital payment card may be associated with a physical payment card by virtue of being associated with a common financial account for satisfying payments initiated with both the digital payment card and the physical payment card. Whenuser104 selects the digital payment card for registration,travel registration manager116 uses a repository ofpayment card information124 and amapping126 between digital payment cards and physical payment cards to determine that the digital payment card is associated with the physical payment card and automatically registers the physical payment card in additional to the digital payment card.
In another example, a first digital payment card in one digital wallet, e.g., a digital wallet onuser computer device106, may be associated with a second digital payment card in another digital wallet, e.g., a digital wallet onuser computer device108. The digital payment cards are associated by virtue of being associated with a common financial account for satisfying payments initiated with both the digital payment cards. Whenuser104 selects the digital payment card for registration,travel registration manager116 usesrepository124 andmapping126 to determine that the first digital payment card is associated with the second digital payment card and automatically registers the second digital payment card in additional to the first digital payment card.
In some examples,payment network server102 has access torepository124 andmapping126 as a result of executingdigital wallet server118.Digital wallet server118 provides services foruser104 to set up digital wallets. For example,digital wallet server118 can provide a graphical user interface (GUI) touser computer device106 for setting up digital wallets, e.g., by collecting personal and financial information fromuser104.User computer device106 can then execute a digital wallet client for hosting the digital wallet.
For example,user104 may initially supply information specifying a physical payment card todigital wallet server118 usinguser computer device106.Digital wallet server118 then generates a token, i.e., a unique sequence of letters or numbers or both, for the physical payment card and stores the token onuser computer device106 as the digital payment card.Digital wallet server118 records data for both the physical and digital payment cards incard repository124 and creates an electronic association between the physical payment card and the digital payment card inmapping126.
User104 may then later request a digital payment card associated with the same physical payment card fromuser device108.Digital wallet server118 generates a different token and stores the token onuser computer device108 as a different digital payment card associated with the same physical payment card.Digital wallet server118 records data for the different digital payment card incard repository124 and creates an electronic association for the different digital payment card inmapping126. In the event thatuser104 registers the digital payment card on eitheruser computer device106 oruser computer device108,travel registration manager116 can automatically register both digital payment cards and the physical payment card.Travel registration manager116 can send a message to the user computer device that was used for registration to display a notice touser104 indicating that the other payment cards were also registered.
Authentication server122 authenticatesuser104 to some or all of the services inenvironment100, e.g., travelregistration manager116 anddigital wallet server118. In general,authentication server122 can use any appropriate techniques for authentication and other types of security to ensure protection of personal and financial data foruser104.User104 can authenticate toauthentication server122, e.g., using biometric authorization on one or both ofuser devices106 and108, or by providing user credentials.
In some examples,payment network server102 registers payment cards in connection withuser104 booking travel on travel bookingcomputer system130. For example,user104 may use a web browser executing onuser computer device106 to load a web site hosted by travel bookingcomputer system130 for making travel reservations.User104 can purchase a flight, book a hotel room, or a reserve a car using a digital payment card hosted on the digital wallet ofuser computer device106. In connection with the travel booking,payment network server102 registers multiple digital payment cards for the dates and locations of the travel.Payment network server102 oruser computer device106 can determine the dates and locations of the travel by parsing text generated by travel bookingcomputer system130, e.g., a confirmation web page or e-mail.
Payment network server102 may or may not coordinate with travel bookingcomputer system130 in registering digital payment cards in connection with travel booking. For example, travel bookingcomputer system130 can be configured to encourage users to register payment cards by presenting an option to register payment cards after booking travel, e.g., by displaying a hyperlink topayment network server102 in a web page presented after the travel is booked, or by executing a script supplied by a system administrator ofpayment network server102. In cases where travel bookingcomputer system130 is not configured to coordinate withpayment network server102,user104 can still take actions to causetravel registration manager116 to register payment cards after booking travel on travel bookingcomputer system130. For example,user104 can use an e-mail client onuser computer device106 to forward a confirmation e-mail to an e-mail address monitored bytravel registration manager116.
In some examples,user104 makes a purchase usingmerchant computer system132 that is not explicitly travel-related but is nonetheless associated with future travel. For example,user104 may purchase an event ticket for an event in a location that is different from a home location specified in a user profile foruser104, e.g., a user profile associated with a digital wallet.User104 can still register payment cards usingtravel registration manager116, e.g., by directing a web browser executing onuser computer device106 to a web site hosted bytravel registration manager116, or by executing a client app fortravel registration manager116 installed onuser computer device106.
FIG. 2 is a block diagram of anexample communications environment100 for initiating a transaction using a payment card registered for travel.Environment200 includes thepayment network server102, theuser computer device106, and the packet-baseddata communications network110 ofFIG. 1.Environment200 also includes a merchant point-of-sale device202, an acquirer server implemented on a system of one or more computers, and anissuer server226 implemented on a system of one or more computers. In the depicted example,issuer server226 executes the bankfraud detection engine128 ofFIG. 1.
User computer device106 includes one ormore processors208 andmemory210.Memory210 stores instructions forprocessors208 that can be loaded, e.g., into random access memory (RAM), and executed byprocessors208 to causeprocessors208 to perform operations for initiating a transaction using a payment card registered for travel.User computer device106 typically includes a display and a user input device, e.g., a touchscreen.
User computer device106 implements, usingprocessors208 andmemory210, adigital wallet client212, aweb browser214, and adigital wallet216.User computer device106 also includes alocation determination system222, which can be a global positioning system (GPS) receiver, a cellular or wi-fi network location determination system, or any appropriate combination of hardware and software for determining a geographic location ofuser computer device106.
Digital wallet client212 can interact with a digital wallet server, e.g., thedigital wallet server118 ofFIG. 1, to hostdigital wallet216 onuser computer device106. Hostingdigital wallet216 includes storing data such as tokens corresponding todigital payment cards218 and otherdigital items220 such as digital coupons, digital tickets, and electronic boarding passes for flights. Hostingdigital wallet216 also includes providing an interface for a user to initiate transactions usingdigital payment cards218.
For example,digital wallet client212 can present a GUI on a display screen ofuser computer device106 for a user to view items stored indigital wallet216 and for the user to add and delete items fromdigital wallet216, e.g., by interacting withdigital wallet server118 over packet-baseddata communications network110. The user may alternatively or additionally access information regardingdigital wallet216 usingweb browser214, e.g., by loading a web page hosted bydigital wallet server118. The user can initiate the transaction, e.g., by bringinguser computer device106 to within an appropriate distance ofmerchant POS device202, causinguser computer device106 andmerchant POS device202 to establish a near-field communication (NFC) session. During the NFC communications session,user computer device106 can transmit, e.g., a token or other appropriate data representing one ofdigital payment cards218 and optionally data fromlocation determination system222.
Merchant POS device202 then exchanges messages withpayment network server102 for authorization of the transaction.Payment network server102 exchanges messages, as appropriate depending on the structure of the payment network, withacquirer server204 andissuer server226 to determine whether or not to authorize the transaction.Payment network server102 may use the networkfraud detection engine120 ofFIG. 1 to determine whether or not to decline the transaction for exceeding a threshold risk score indicating fraud. Thefraud detection engine120 ofFIG. 1 may alternatively produce a fraud score for the transaction for the issuer (consumer's bank) to decide whether to approve or decline the transaction. Alternatively or additionally, issuer server may use bankfraud detection engine128 to whether or not to decline the transaction for exceeding a threshold risk score indicating fraud.
In either case, the system modifies a risk score (likely reducing the score) if the digital payment card used was registered for travel and the date and geographic location of the transaction match the dates and geographic location of the registration. The system can determine that the geographic location matches the registration, for example, using data fromlocation determination system222 or data frommerchant POS device202 or both.Issuer server226 implements atransaction analyzer224 configured to ultimately determine to authorize the transaction based on the risk score and other data, e.g., whether there are sufficient funds or credit for the account associated with the digital payment card to satisfy the amount of the transaction.
FIGS. 3A-B are line drawings of computer screen shots that may be displayed onuser device106 for registering payment cards for travel. The user can be theuser104 ofFIG. 1 registering payment cards onuser computer device106 by exchanging messages withtravel registration manager116 over packet-baseddata communications network110.
InFIG. 3A, screen shot302 shows a prompt of a GUI for a user to initiate registration of payment cards. For example,user device106 can be configured, by virtue of appropriate programming, to present screen shot302 afteruser104 books travel on the travelbooking computer system130 ofFIG. 1. InFIG. 3B, screen shot304 shows an interface for selecting digital payment cards from a digital wallet for registration. For example,digital wallet client212 ofFIG. 2 can determine to display some or all ofdigital payment cards218 ofFIG. 2.
Afteruser104 selects some or all of the digital payment cards,user computer device106 transmits a message to travelregistration manager116 specifying the selected digital payment cards, causingtravel registration manager116 to register the digital payment cards. For example, ifuser104 has just booked travel on the travelbooking computer system130 ofFIG. 1,user computer device106 can transmit a message to travelregistration manager116 specifying the dates and geographic locations of the booked travel.
In one exemplary implementation, the computer screen shots illustrated inFIGS. 3A and 3B and the automatic payment card steps triggered through user interaction with the user interfaces may be implemented bydigital wallet client212 illustrated inFIG. 1. In an alternate implementation,user device106 may be provided with a payment card registration application that displays the computer screen shots illustrated inFIGS. 3A and 3B and preforms the steps described herein for automatic payment card registration.
FIG. 4 is a flow chart of anexample method400 for consolidated registration of payment cards.Method400 is performed by a system of one or more computers configured, by virtue of appropriate programming, to register digital payment cards for travel with a fraud detection engine. For example, thetravel registration manager116 ofFIG. 1 can performmethod400.
The system receives, using a packet-based data communications network, data specifying a geographic location and one or more dates of travel to the geographic location for a user (402). For example, receiving the data specifying the geographic location and the dates of travel to the geographic location can include parsing text data generated as a result of the user booking one or more travel-related reservations using one of the digital payment cards in the first digital wallet. The system receives a selection of digital payment cards from a first digital wallet for the user (404).
The system registers, with a fraud detection engine executing on a computer system, the digital payment cards for the user, the associated mobile devices and the dates of travel to the geographic location (406). Registering the digital payment cards causes the fraud detection engine to modify a risk score of at least a first transaction initiated by the user during the dates of travel and within a threshold geographic distance of the geographic location. Causing the fraud detection engine to modify the risk score for the first transaction initiated by the user can cause the fraud detection engine to reduce the risk score as a result of registering the digital payment cards.
For example, suppose that the user initiates the first transaction using a first digital payment card in the first digital wallet. The first digital payment card is associated with a financial account at an issuer bank for satisfying payments initiated with the first digital payment card. Causing the fraud detection engine to reduce the risk score the first transaction initiated by the user can cause an issuer computer system for the issuer bank to approve the first transaction initiated by the user.
In some examples, a first digital payment card in the selection is issued by a first bank and a second digital payment card in the selection is issued by a second bank. In those situations, registering the digital payment cards includes registering the first digital payment card with a first fraud detection engine executing on a first computer system for the first bank and registering the second digital payment card with a second fraud detection engine executing on a second computer system for the second bank.
In some examples, registering the digital payment cards includes determining, using a mapping between digital payment cards and physical payment cards, that a first digital payment card of the first digital wallet is associated with a first physical payment card by virtue of being associated with a common financial account for satisfying payments initiated with both the first digital payment card and the first physical payment card. In those situations, registering the digital payment cards includes registering both the first digital payment card and the first physical payment card with the fraud detection engine.
The system may also determine that the first digital payment card of the first digital wallet is associated with a second digital payment card of a second digital wallet for the user by determining that the second digital payment card is also associated with the common financial account for satisfying payments initiated with both the first digital payment card and the second digital payment card. In those situations, registering the digital payment cards includes registering both the first digital payment card and the second digital payment card with the fraud detection engine. For example, the first digital wallet can be hosted on a first computer device for the user and the second digital wallet can be hosted on a second computer device for the user, and the first and second computer devices each include a processor and memory storing instructions for initiating payment transactions using digital wallets.
FIG. 5 is a flow chart of anexample method500 illustrating a first transaction approved as a result of registering digital payment cards.Method500 is performed by a system of one or more computers configured, by virtue of appropriate programming, to analyze and approve or deny transactions initiated using payment cards. For example, theissuer server226 ofFIG. 2 can performmethod500.
The system registers a user's digital payment cards for a geographic location and one or more dates of travel to the geographic location for the user (502). The system receives data specifying a first transaction initiated by the user's mobile computer device using one of the digital payment cards stored in a digital wallet hosted on the user's mobile computer device (504). The system determines that a current date matches the dates of travel (506). The system determines, using data from a location determination system of the user's mobile computer device, that the mobile computer device is within a threshold distance of the geographic location (508).
The system reduces a risk score for the first transaction as a result of registering the digital payment cards, i.e., the risk score is lower than it would have been absent registration of the digital payment cards (510). The system approves the first transaction as a result of reducing the risk score (512).
The subject matter described herein improves the functionality ofuser device106,payment network server102,issuer server226 andnetwork110 by automatically registering multiple payment cards without requiring the user to manually enter payment card numbers (e.g., PAN numbers) or provide such information via a telephone call. In addition, by automatically registering multiple cards in a single interaction with a user, the number of messages traveling acrossnetwork110 is reduced over the case where the user initiates a separate registration transaction (e.g., by telephone) for each payment card. The subject matter described herein also improves the technological field of payment card transaction security. Automatically transmitting stored payment card numbers topayment network server102 for travel registration along with travel location information, improves the accuracy of payment card verification bypayment network server102. In addition, the likelihood of payment card information being overheard by someone in close proximity to the user is reduced over manual payment card travel registration.
Accordingly, while the methods, systems, and computer readable media have been described herein in reference to specific embodiments, features, and illustrative embodiments, it will be appreciated that the utility of the subject matter is not thus limited, but rather extends to and encompasses numerous other variations, modifications and alternative embodiments, as will suggest themselves to those of ordinary skill in the field of the present subject matter, based on the disclosure herein.
Various combinations and sub-combinations of the structures and features described herein are contemplated and will be apparent to a skilled person having knowledge of this disclosure. Any of the various features and elements as disclosed herein may be combined with one or more other disclosed features and elements unless indicated to the contrary herein. Correspondingly, the subject matter as hereinafter claimed is intended to be broadly construed and interpreted, as including all such variations, modifications and alternative embodiments, within its scope and including equivalents of the claims.
It is understood that various details of the presently disclosed subject matter may be changed without departing from the scope of the presently disclosed subject matter. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation.