TRANSACTION PROCESSING USING A GLOBAL UNIQUE IDENTIFIER

• US 20140081862A1
• Filed: 09/06/2013
• Published: 03/20/2014
• Est. Priority Date: 07/29/2008
• Status: Active Grant

• Current Assignee: Barbara Elizabeth Patterson
• Original Assignee: Barbara Elizabeth Patterson
• Inventors: Patterson, Barbara Elizabeth
• Granted Patent: US 9,183,555 B2
• 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/0855 involving a third party
• 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/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• 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/401 Transaction verification
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 30/0215 Including financial accounts
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

A Globally Unique IDentifier (GUID) is used to match an authorization request with an authorization response for a transaction between a merchant and a consumer upon an account within a payment processing system where the payment amount is unknown until after the merchant receives the authorization response that includes the GUID. After receiving the authorization response and when the payment amount is known, the merchant forms a transmission that has information for delivery to an issuer of the account. This information is sufficient for the issuer to forward the payment amount from the account to pay the merchant for the transaction. While including the GUID and the payment amount, the information does not include an identifier of the account.

Claims

1-20. -20. (canceled)

21. A method comprising:

obtaining, by an acceptance point device associate with a merchant, account information, including an account identifier, from a consumer to conduct a transaction with the merchant;

sending an authorization request having a code for the transaction that is unique among a plurality of transactions of the merchant in a plurality of merchants, an amount of funds to be authorized for the transaction, and the account identifier; and

receiving an authorization response message that includes a Globally Unique Identifier (GUID) instead of the account identifier, the code for the transaction, and an indication of whether the transaction was approved.

22. The method of claim 21 further comprising:

storing the GUID instead of the account identifier for use in subsequent processing of the transaction.

23. The method of claim 21 wherein the amount of funds to be authorized for the transaction is a preliminary quantity of funds and wherein the method further comprises:

transmitting a final quantity of funds along with the GUID.

24. The method of claim 21 further comprising:

forming a transmission including a clearing and settlement request and the GUID but not the account identifier.

25. The method of claim 21 wherein the code for the transaction is a date on which the authorization request was formed, a merchant identifier of the merchant and a logical address corresponding to the location of the merchant device.

26. The method of claim 21 wherein the code for the transaction is created using a pseudo random number generator.

27. The method of claim 21 further comprising:

generating the code for the transaction.

28. The method of claim 21 further comprising:

associating the GUID in the authorization response with the transaction.

29. The method of claim 21 wherein the account information is obtained from a portable consumer device associated with the consumer.

30. The method of claim 21 wherein the code for the transaction is unique among the plurality of transactions of the merchant but not unique across merchants within a payment processing system.

31. The method of claim 21 wherein the GUID was derived using an algorithm without having the account identifier as an input to the algorithm.

32. An acceptance point device comprising a processor and a non-transitory computer readable medium storing computer readable code configured to be executed by the processor to:

obtain account information, including an account identifier, from a consumer to conduct a transaction with the merchant;

send an authorization request having a code for the transaction that is unique among a plurality of transactions of the merchant in a plurality of merchants, an amount of funds to be authorized for the transaction, and the account identifier; and

receive an authorization response message that includes a Globally Unique Identifier (GUID) instead of the account identifier, the code for the transaction, and an indication of whether the transaction was approved.

33. The acceptance point device of claim 32 wherein the computer readable code is further configured to be executed by the processor to:

store the GUID instead of the account identifier for use in subsequent processing of the transaction.

34. The acceptance point device of claim 32 wherein the amount of funds to be authorized for the transaction is a preliminary quantity of funds and wherein the computer readable code is further configured to be executed by the processor to:

transmit a final quantity of funds along with the GUID.

35. The acceptance point device of claim 32 wherein the computer readable code is further configured to be executed by the processor to:

form a transmission including a clearing and settlement request and the GUID but not the account identifier.

36. The acceptance point device of claim 32 wherein the code for the transaction is a date on which the authorization request was formed, a merchant identifier of the merchant and a logical address corresponding to the location of the merchant device.

37. The acceptance point device of claim 32 wherein the code for the transaction is created using a pseudo random number generator.

38. The acceptance point device of claim 32 wherein the computer readable code is further configured to be executed by the processor to:

generate the code for the transaction.

39. The acceptance point device of claim 32 wherein the computer readable code is further configured to be executed by the processor to:

associate the GUID in the authorization response with the transaction.

40. The acceptance point device of claim 32 wherein the account information is obtained from a portable consumer device associated with the consumer.

41. The acceptance point device of claim 32 wherein the code for the transaction is unique among the plurality of transactions of the merchant but not unique across merchants within a payment processing system.

42. The acceptance point device of claim 32 wherein the GUID was derived using an algorithm without having the account identifier as an input to the algorithm.