Intermediate Data Generation For Transaction Processing

• US 20100100482A1
• Filed: 01/23/2008
• Published: 04/22/2010
• Est. Priority Date: 01/23/2007
• Status: Abandoned Application

• Current Assignee: Sxipper Incorporated
• Original Assignee: Sxip Identity Corp. (Ping Identity Corporation)
• Inventors: Hardt, Dick C.
• Application Number:
  US12/523,754
• Publication Number:
  US 20100100482A1
• Time in Patent Office: Days
• US Class Current: 705/44
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• 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/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

Abstract

An indirect transaction processor performs rules based processing to verify online transactions. The indirect transaction processor can match indirect indirect data sets to valid data sets used in conventional transaction approval to provide users anonymity in transactions. User approval of transactions can also be implemented, as can other business rules to permit delegated approval and authorization.

Claims

1. A method of generating indirect transaction data for use in a transaction comprising:

receiving a request for indirect transaction data;

generating a set of indirect transaction data and an associated set of transaction conditions in accordance with the received request; and

transmitting the generated set of indirect transaction data.

2. The method of claim 1 wherein the request for indirect transaction data is received from a user, and the generated set of indirect transaction data is transmitted to the user.

3. The method of claim 1 wherein the step of generating indirect transaction data includes generating indirect values for identity information.

4. The method of claim 3 wherein the identity information is selected from a list including a name, an address, a credit card number and an email address.

5. The method of claim 1 wherein at least one element in the set of indirect transaction data is a nonce.

6. The method of claim 1 wherein the transaction conditions are selected from a list including requiring the collection of metadata, requiring cardholder authorization, requiring credit card issuer approval, requiring a specified merchant, requiring a transaction below a specified limit and requiring use of the indirect data within a defined time window.

7. The method of claim 1 wherein the step of generating the set of indirect transaction data is followed by a step of storing the indirect transaction data and the associated set of transaction conditions.

8. A method of approving a transaction based on indirect transaction data, the method comprising:

receiving a request to approve a transaction, the request containing indirect transaction data;

retreiving a set of transaction conditions associated with the received indirect transaction data; and

transmitting a transaction approval in response to the received request if the retrieved transaction conditions are satisfied.

9. The method of claim 8 wherein the step of retrieving transaction conditions includes retrieving a set of direct transaction data associated with the indirect transaction data.

10. The method of claim 8 wherein the indirect transaction data includes at least one unique element to permit retrieval of the transaction conditions.

11. The method of claim 8 wherein the retrieved transaction conditions include obtaining a transaction approval from an external approval agent.

12. The method of claim 11 wherein the external approval agent is the holder of a credit card associated with the indirect transaction data.

13. The method of claim 11 wherein the external approval agent is the issuer of a credit card associated with the indirect transaction data.

14. An indirect transaction processor for generating indirect transaction data and for authorizing transactions based on indirect transaction data, the processor comprising:

an indirect data generator for generating indirect transaction data and a set of transaction conditions associated with a set of direct transaction data, and for storing the direct transaction data, the generated indirect transaction data and the transaction conditions;

an approval engine for receiving a request to authorize transactions based on indirect transaction data, for retrieving direct transaction data and at least one transaction condition associated with the received indirect transaction data, for approving the received requests upon satisfying the transaction conditions associated with the received indirect transaction data.

15. The processor of claim 14 further including a policy database for storing the direct transaction data, the generated transaction data and the transaction conditions for later retrieval.

16. The processor of claim 14 wherein the approval engine includes an external approval interface for determining if transaction conditions reliant on external factors are satisfied.

17. The processor of claim 14 wherein the approval engine includes an analysis engine for analyzing the received request to determine if at least one of the retrieved transaction conditions has been satisfied.