Transaction processing

• US 8,229,854 B2
• Filed: 08/06/2009
• Issued: 07/24/2012
• Est. Priority Date: 06/27/2001
• Status: Active Grant

• Current Assignee: Orbis Patents Limited (Orbis Technology)
• Original Assignee: Orbiscom Limited (MasterCard Incorporated)
• Inventors: Stephen, Kavanagh, Clarke, Conor, Guilfoyle, Kleron, Brosnan, Patrick
• Primary Examiner(s): Colbert, Ella
• Application Number:
  US12/461,289
• Publication Number:
  US 20100017328A1
• Time in Patent Office: 1,083 Days
• Field of Search: 705/39, 705/42, 705/44, 707/694, 707/703, 707/779, 707/792, 707/803, 707/805, 235/379, 235/380, 709/200, 709/217, 709/218, 709/227
• US Class Current: 705/44
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06K 19/00 Record carriers for use with machines and with at least a part designed to carry digital markings
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/08 Payment architectures
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/108 Remote banking, e.g. home banking
• CPC Class Codes: G06Q 20/1085 involving automatic teller machines [ATMs]
• CPC Class Codes: G06Q 20/22 Payment schemes or models
• CPC Class Codes: G06Q 20/24 Credit schemes, i.e. "pay after"
• CPC Class Codes: G06Q 20/305 using wired telephone networks
• CPC Class Codes: G06Q 20/34 using cards, e.g. integrated circuit [IC] cards or magnetic cards
• CPC Class Codes: G06Q 20/354 Card activation or deactivation
• CPC Class Codes: G06Q 20/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
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 20/403 Solvency checks
• CPC Class Codes: G06Q 20/4037 Remote solvency checks
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 20/407 Cancellation of a transaction
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G07F 7/08 : by coded identity card or credit card or other personal identification means without personal verification means G07F7/02
• CPC Class Codes: G07F 7/122 : Online card verification

Abstract

A transaction processing system for the real time authorization of payment transactions, The system comprises a verification system (4) connected to an issuer card management system (3). A cardholder can access the system via an interface (2) which can be for example the Internet, a wireless device, telephone, or a branch visit. The interface allows the cardholder to input rules governing how their credit card transactions are to be authorized. When the cardholder initiates a purchase transaction with their credit card, an authorization request is passed from the card network to the verification system which executes the rules created by the cardholder in order to approve or deny the transaction.

Claims

1. A transaction processing system implemented using at least one programmable data processing apparatus, for processing requests to authorize card transactions, comprising:

a request interface configured to receive requests from customers to authorize card transactions,

a rule database configured to store cardholder rules,

instructions to generate positive and negative authorization outputs based on authorization requests received from the request interface,

(A) setup means for storing cardholder rules, each cardholder rule being associated with at least one customer wherein the setup means comprises;

(i) a fraud manager interface enabling a fraud manager with access control to;

(a) define templates, wherein each template comprises a structure of placeholders for population with information specifying at least one action and at least one notification, the information including authorization request message fields, relational operators, values, and logical operators,

(b) populate placeholders of a template with information to generate a template rule, and

(ii) a definition interface configured to;

(a) select at least one template rule, and

(b) select and populate at least one of the defined templates to generate at least one cardholder rule referring to the at least one selected template and the information populating the template, and specifying an action and a notification, and

(B) authorization means for dynamically retrieving from the rule database a cardholder rule associated with a customer of each authorization request on a per-transaction basis, for applying the retrieved cardholder rule to the transaction request, and for executing the cardholder rule with reference to a template rule and implementing the action and notification specified in the template rule, and an authorization interface for transmitting the positive and negative authorization outputs.

2. The transaction processing system as claimed in claim 1, wherein:

the rules database is configured to store system rules which apply to all transactions, and product rules which apply to groups of cards, and index said cardholder rules on card number, and the authorization means includes means for retrieving system rules and product rules and to successively apply said system, product, and cardholder rules upon receipt of an authorization request.

3. The transaction processing system as claimed in claim 1, wherein said template rules are stored in a format which does not require parsing of logical string-based expressions for processing.

4. The transaction processing system as claimed in claim 3, wherein the authorization means includes means for receiving confirmation of authorization from a customer in response to a notification.

5. The transaction processing system as claimed in claim 1, further comprising a network interface for a card payment network, and a card management system interface for an issuer card management system.

6. The transaction processing system as claimed in claim 5, wherein the network interface and the card management system interface each comprises a communication header module configured to convert received messages into a standardized data sequence of bytes.

7. The transaction processing system as claimed in claim 6, wherein the network interface and the card management system interface each comprises a protocol header module comprising means for converting the standardized data sequence of bytes into an internal format for processing.

8. The transaction processing system as claimed in claim 6, wherein the communication header and the protocol header modules comprise means for sequentially checking for, receiving, converting and routing messages and data.

9. The transaction processing system as claimed in claim 6, wherein the communication header and protocol header modules are configured to route transaction requests and responses between a card payment network a card management system.

10. The transaction processing system as claimed in claim 1, wherein the authorization means includes means for automatically transmitting at least one of a notification to at least one of the fraud manager or a customer once a possible fraud is detected or an authorization request result to a customer.

11. The transaction processing system as claimed in claim 1, wherein said setup means comprises means for providing at least one of an on-line banking interface or an automated teller machine interface.

12. The transaction processing system as claimed in claim 1, wherein the authorization means includes means for receiving a cardholder request that a card be deactivated.

13. The transaction processing system as claimed in claim 1, wherein the authorization means includes means for receiving a Short Message Service from a cardholder to deactivate a card.

14. A computerized method for processing requests to authorize card transactions, comprising:

storing cardholder rules on a non-transitory computer readable medium, each cardholder rule being associated with at least one customer;

defining templates, by a fraud manager with access control as enabled by a fraud manager interface, wherein each template comprises a structure of placeholders to be populated with information specifying at least one action and at least one notification, the information including authorization request message fields, relational operators, values, and logical operators,

populating template placeholders, by said fraud manager, with information to generate a template rule,

receiving at least one template rule selection, and

generating at least one cardholder rule, based on received user input, referring to the at least one selected template and the information populating the template, and specifying an action and a notification, and

dynamically retrieving, on a per-transaction basis from the rule database, a cardholder rule associated with a customer from each authorization request,

applying the retrieved cardholder rule to the transaction request,

executing the cardholder rule with reference to a template rule,

implementing the action and notification specified in the template rule, and

transmitting the positive and negative authorization outputs.

15. The computerized method of claim 14, comprising storing system rules which apply to all transactions, and product rules which apply to groups of cards, and indexing said cardholder rules by card number, and retrieving system rules and product rules and to successively apply said system, product, and cardholder rules upon receipt of an authorization request.

16. The computerized method of claim 14, comprising storing said template rules in a format which does not require parsing of logical string-based expressions for processing.

17. The computerized method of claim 16, comprising receiving further functions to receive confirmation of authorization from a customer in response to a notification.

18. The computerized method of claim 14, comprising interfacing with a card payment network, and interfacing with an issuer card management system.

19. The computerized method of claim 18, comprising converting received messages into a standardized data sequence of bytes.

20. The computerized method of claim 19, comprising routing transaction requests and responses between a card payment network a card management system.

21. The computerized method of claim 19, comprising converting the standardized data sequence of bytes into an internal format for processing.

22. The computerized method of claim 19, comprising sequentially checking for, receiving, converting and routing messages and data.

23. The computerized method of claim 14, comprising receiving a Short Message Service from a cardholder to deactivate a card.

24. The computerized method of claim 14, comprising automatically transmitting at least one of a notification to at least one of the fraud manager or a customer once a possible fraud is detected or an authorization request result to a customer.

25. The computerized method of claim 14, comprising receiving input from at least one of an on-line banking interface or an automated teller machine interface.

26. The computerized method of claim 14, comprising receiving a cardholder request that a card be deactivated.

27. A non-transitory computer readable storage medium encoded with instructions that, executed by a computer, cause the computer to execute the steps of:

defining templates, by a fraud manager with access control as enabled by a fraud manager interface, wherein each template comprises a structure of placeholders to be populated with information specifying at least one action and at least one notification, the information including authorization request message fields, relational operators, values, and logical operators,

populating template placeholders, by the fraud manager, with information to generate a template rule,

receiving at least one template rule selection, and

generating at least one cardholder rule, based on received user input, referring to the at least one selected template and the information populating the template, and specifying an action and a notification, and

dynamically retrieving, on a per-transaction basis from the rule database, a cardholder rule associated with a customer from each authorization request,

applying the retrieved cardholder rule to the transaction request,

executing the cardholder rule with reference to a template rule,

implementing the action and notification specified in the template rule, and

transmitting the positive and negative authorization outputs.