A server computer can provide a merchant or other entity with a payment card (or other payment device) detection service that can determine a level of fraud based on the account type being presented (e.g., credit, debit, prepaid, etc.) at the time of purchase. For example, a payment account number (PAN) can be used to perform a database lookup (e.g., a range lookup) to identify the payment account type, which can then be fed into a fraud detection system. The level of fraud can then be used to determine an authorization result (e.g., accept, reject, or review). A use of a merchant processor computer that implements fraud processing can allow a merchant to implement discounting, acceptance, and/or fraud rules based on the card type.
Legal claims defining the scope of protection, as filed with the USPTO.
1. A method for authorizing a first authorization request for a transaction between a client computer of a consumer and a merchant computer, the method comprising performing by a server computer: storing, in a user database, authorization credentials for users of the server computer, the authorization credentials including merchant identifiers, user names, and passwords; receiving, at a network interface, user credentials from a user computer via a communications network, the user credentials including a merchant identifier, a user name, and a password; responsive to receiving the user credentials, accessing the user database to identify the user name and to verify the received password corresponds to a stored password linked to a user name in the user database; receiving, from the user computer, a modification to a rule, the modification specifying one or more criteria to make a change in processing the transaction, including routing of an authorization result; responsive to accessing the user database, using the merchant identifier to store a modified rule including the modification to the rule into a merchant profile database; receiving, from the merchant computer via the communications network, transaction information and the first authorization request for the transaction, the transaction information including the merchant identifier corresponding to the merchant computer and an account number of an account of the consumer, wherein the account number was received by the merchant computer from the client computer; responsive to receiving the first authorization request, parsing the account number to determine an account type identifier; sending a query to an account database, the query including the account type identifier; receiving an account type corresponding to the account number from the account database; sending the transaction information and the account type to a fraud detection engine of the server computer; determining, by the fraud detection engine, a level of fraud for the transaction using the account type and the transaction information; retrieving, using the merchant identifier, the modified rule from the merchant profile database; determining a first authorization result for the transaction based on the modified rule and the level of fraud, wherein the first authorization result includes the change in the transaction; responsive to the first authorization result including the change in the transaction, transmitting (1) information about the change to the merchant computer via the communications network and (2) instructions to the merchant computer to communicate with the client computer to determine whether the change is accepted by the client computer; receiving, via the communications network, a confirmation response from the merchant computer indicating that the client computer accepted the change; and proceeding to process the changed transaction.
2. The method of claim 1 , wherein processing the changed transaction includes: responsive to the confirmation response, generating a second authorization request that includes the change in the transaction: sending the second authorization request to an issuer computer via a processing network; receiving an authorization response from the issuer computer via the processing network; and transmitting a second authorization result to the merchant computer.
3. The method of claim 2 , further comprising: responsive to receiving the first authorization request, parsing the account number to determine a bank identifier; sending a separate query to the account database, the separate query including the bank identifier; and receiving bank information corresponding to the bank identifier from the account database, wherein the bank information corresponds to the issuer computer.
4. The method of claim 2 , further comprising: responsive to receiving the first authorization request, parsing the account number to determine a bank identifier, wherein the query includes the bank identifier; and receiving bank information corresponding to the bank identifier from the account database, wherein the bank information corresponds to the issuer computer.
5. The method of claim 1 , wherein the account type corresponds to one of a plurality of fields in the account database corresponding to an entry that matches the query, and wherein the account type identifier and a bank identifier are included in the query to identify the entry.
6. The method of claim 5 , wherein the account type indicates the account is of a prepaid type, and wherein the modified rule specifies the change in the transaction for the account type being the prepaid type.
7. The method of claim 1 , further comprising: sending an initial authorization request to an issuer computer, the initial authorization request including the query; and receiving an initial authorization response generated by the issuer computer, wherein the initial authorization response includes the account type.
8. A computer product comprising a non-transitory computer readable medium storing a plurality of instructions that when executed control a server computer to authorize a first authorization request for a transaction between a client computer of a consumer and a merchant computer, the instructions comprising: storing, in a user database, authorization credentials for users of the server computer, the authorization credentials including merchant identifiers, user names, and passwords; receiving, at a network interface, user credentials from a user computer via a communications network, the user credentials including a merchant identifier, a user name, and a password; responsive to receiving the user credentials, accessing the user database to identify the user name and to verify the received password corresponds to a stored password linked to a user name in the user database; receiving, from the user computer, a modification to a rule, the modification specifying one or more criteria to make a change in processing the transaction, including routing of an authorization result; responsive to accessing the user database, using the merchant identifier to store a modified rule including the modification to the rule into a merchant profile database; receiving, from the merchant computer via the communications network, transaction information and the first authorization request for the transaction, the transaction information including the merchant identifier corresponding to the merchant computer and an account number of an account of the consumer, wherein the account number was received by the merchant computer from the client computer; responsive to receiving the first authorization request, parsing the account number to determine an account type identifier; sending a query to an account database, the query including the account type identifier; receiving an account type corresponding to the account number from the account database; sending the transaction information and the account type to a fraud detection engine of the server computer; determining, by the fraud detection engine, a level of fraud for the transaction using the account type and the transaction information; retrieving, using the merchant identifier, the modified rule from the merchant profile database; determining a first authorization result for the transaction based on the modified rule and the level of fraud, wherein the first authorization result includes the change in the transaction; responsive to the first authorization result including the change in the transaction, transmitting (1) information about the change to the merchant computer via the communications network and (2) instructions to the merchant computer to communicate with the client computer to determine whether the change is accepted by the client computer; receiving, via the communications network, a confirmation response from the merchant computer indicating that the client computer accepted the change; and proceeding to process the changed transaction.
9. The computer product of claim 8 , wherein processing the changed transaction includes: responsive to the confirmation response, generating a second authorization request that includes the change in the transaction: sending the second authorization request to an issuer computer via a processing network; receiving an authorization response from the issuer computer via the processing network; and transmitting a second authorization result to the merchant computer.
10. The computer product of claim 9 , wherein the instructions further comprise: responsive to receiving the first authorization request, parsing the account number to determine a bank identifier; sending a separate query to the account database, the separate query including the bank identifier; and receiving bank information corresponding to the bank identifier from the account database, wherein the bank information corresponds to the issuer computer.
11. The computer product of claim 9 , wherein the instructions further comprise: responsive to receiving the first authorization request, parsing the account number to determine a bank identifier, wherein the query includes the bank identifier; and receiving bank information corresponding to the bank identifier from the account database, wherein the bank information corresponds to the issuer computer.
12. The computer product of claim 8 , wherein the account type corresponds to one of a plurality of fields in the account database corresponding to an entry that matches the query, and wherein the account type identifier and a bank identifier are included in the query to identify the entry.
13. The computer product of claim 12 , wherein the account type indicates the account is of a prepaid type, and wherein the modified rule specifies the change in the transaction for the account type being the prepaid type.
14. The computer product of claim 8 , wherein the instructions further comprise: sending an initial authorization request to an issuer computer, the initial authorization request including the query; and receiving an initial authorization response generated by the issuer computer, wherein the initial authorization response includes the account type.
15. A server computer for authorizing a first authorization request for a transaction between a client computer of a consumer and a merchant computer, the server computer comprising one or more processors configured to: store, in a user database, authorization credentials for users of the server computer, the authorization credentials including merchant identifiers, user names, and passwords; receive, at a network interface, user credentials from a user computer via a communications network, the user credentials including a merchant identifier, a user name, and a password; responsive to receiving the user credentials, access the user database to identify the user name and to verify the received password corresponds to a stored password linked to a user name in the user database; receive, from the user computer, a modification to a rule, the modification specifying one or more criteria to make a change in processing the transaction, including routing of an authorization result; responsive to accessing the user database, use the merchant identifier to store a modified rule including the modification to the rule into a merchant profile database; receive, from the merchant computer via the communications network, transaction information and the first authorization request for the transaction, the transaction information including the merchant identifier corresponding to the merchant computer and an account number of an account of the consumer, wherein the account number was received by the merchant computer from the client computer; responsive to receiving the first authorization request, parse the account number to determine an account type identifier; send a query to an account database, the query including the account type identifier; receive an account type corresponding to the account number from the account database; send the transaction information and the account type to a fraud detection engine of the server computer; determine, by the fraud detection engine, a level of fraud for the transaction using the account type and the transaction information; retrieve, using the merchant identifier, the modified rule from the merchant profile database; determine a first authorization result for the transaction based on the modified rule and the level of fraud, wherein the first authorization result includes the change in the transaction; responsive to the first authorization result including the change in the transaction, transmit (1) information about the change to the merchant computer via the communications network and (2) instructions to the merchant computer to communicate with the client computer to determine whether the change is accepted by the client computer; receive, via the communications network, a confirmation response from the merchant computer indicating that the client computer accepted the change; and proceed to process the changed transaction.
16. The server computer of claim 15 , wherein processing the changed transaction includes: responsive to the confirmation response, generating a second authorization request that includes the change in the transaction: sending the second authorization request to an issuer computer via a processing network; receiving an authorization response from the issuer computer via the processing network; and transmitting a second authorization result to the merchant computer.
17. The server computer of claim 16 , wherein the one or more processors are further configured to: responsive to receiving the first authorization request, parse the account number to determine a bank identifier; send a separate query to the account database, the separate query including the bank identifier; and receive bank information corresponding to the bank identifier from the account database, wherein the bank information corresponds to the issuer computer.
18. The server computer of claim 16 , wherein the one or more processors are further configured to: responsive to receiving the first authorization request, parse the account number to determine a bank identifier, wherein the query includes the bank identifier; and receive bank information corresponding to the bank identifier from the account database, wherein the bank information corresponds to the issuer computer.
19. The server computer of claim 15 , wherein the account type corresponds to one of a plurality of fields in the account database corresponding to an entry that matches the query, and wherein the account type identifier and a bank identifier are included in the query to identify the entry.
20. The server computer of claim 15 , wherein the one or more processors are further configured to: send an initial authorization request to an issuer computer, the initial authorization request including the query; and receive an initial authorization response generated by the issuer computer, wherein the initial authorization response includes the account type.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
March 28, 2019
December 15, 2020
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.