Systems And Methods For Brokered Authentication Express Seller Links

• US 20100257102A1
• Filed: 05/12/2010
• Published: 10/07/2010
• Est. Priority Date: 10/11/2006
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Perlman, Jeffrey William
• Granted Patent: US 10,068,220 B2
• Time in Patent Office: Days
• US Class Current: 705/75
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/123 Shopping for digital content
• CPC Class Codes: G06Q 20/29 characterised by micropayments
• 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/403 Solvency checks
• CPC Class Codes: G06Q 20/4037 Remote solvency checks
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G07F 7/08 by coded identity card or credit card or other personal identification means without personal verification means G07F7/02

Abstract

Systems and methods for providing a transaction authorization from a funds facilitation system for a transaction requested by a user to a merchant system such that the user is not required to input any user authentication information in excess of authentication information required by the merchant system are provided. A system and method can include receiving a transaction request from the merchant system containing a merchant ID, a merchant user ID, and a transaction amount. The system identifies a funds facilitation system user ID based on the merchant ID and the merchant user ID and determines satisfaction of a funds facilitation system user authentication requirement based on the merchant system having a trusted status with the funds facilitation system. A transaction authorization message or transaction denial message is provided to the merchant system based on account information associated with the user and the transaction amount.

Claims

1. A method of processing an electronic payment transaction with a merchant system, comprising:

receiving at a funds facilitation system a transaction authorization request from the merchant system, the transaction authorization request including a merchant identification and information identifying an account holder that initiated the transaction authorization request from the merchant system;

comparing the merchant identification with merchant data stored in the funds facilitation system to determine if the merchant system has been categorized by the funds facilitation system as a trusted merchant; and

based on a determination that the merchant system has been categorized as a trusted merchant, transmitting an electronic communication from the funds facilitation system to the merchant system to approve the transaction authorization request without the funds facilitation system receiving any additional authentication information from the account holder.

2. The method of claim 1, further comprising:

based on a determination that the merchant system has not been categorized as a trusted merchant, requiring additional authentication information from the account holder before approving the transaction authorization request.

3. The method of claim 2, wherein the additional authentication information includes a user identification and password for the account holder, the user identification and password being specific to an account in the funds facilitation system.

4. The method of claim 1, wherein the merchant system receives a user identification and password from the account holder prior to transmitting the transaction authorization request to the funds facilitation system, the user identification and password being specific to an account with the merchant system.

5. The method of claim 1, wherein the funds facilitation system requires additional authentication information from the account holder for an initial transaction authorization request initiated by the account holder from the merchant system, and wherein approval without additional authentication information is available for subsequent transaction authorization requests initiated by the account holder from the merchant system.

6. The method of claim 1, wherein the transaction authorization request also identifies a transaction amount.

7. The method of claim 6, wherein the funds facilitation system requires additional authentication information from the account holder if the transaction amount exceeds a predetermined threshold value.

8. The method of claim 6, further comprising:

prior to transmitting the electronic communication to approve the transaction authorization request, determining if the account holder has access to sufficient funds from the funds facilitation system to cover the transaction amount.

9. The method of claim 8, wherein the information identifying the account holder is a merchant user identification that identifies a first account with the merchant system, the method further comprising:

comparing the merchant user identification with an accounts database in the funds facilitation system to identify a funds facilitation system user identification that is associated with the merchant user identification, the funds facilitation system user identification identifying a second account with the funds facilitation system that is associated with the account holder;

wherein the funds facilitation system accesses information associated with the second account to determine if the account holder has access to sufficient funds to cover the transaction amount.

10. The method of claim 9, wherein the funds facilitation system receives an input initiated by the account holder to link the merchant user identification with the funds facilitation system user identification.

11. The method of claim 1, wherein transaction authorization request includes a digital signature associated with the merchant system, the method further comprising:

verifying authenticity of the digital signature;

wherein approval of the transaction authorization request by the funds facilitation system without additional authentication information from the account holder is contingent upon successfully verifying the authenticity of the digital signature.

12. The method of claim 1, further comprising:

accessing a remote user system associated with the account holder to verify that a link cookie is stored on the remote user system, the link cookie including information to confirm the account holder'"'"'s authorization to categorize the merchant system as a trusted merchant, and wherein transmission of the electronic communication approving the transaction authorization request without requiring additional authentication information is further based on a successful verification of the link cookie.

13. The method of claim 12, further comprising:

verifying that the link cookie stored on the remote user system is valid, and wherein transmission of the electronic communication approving the transaction authorization request without requiring additional authentication information is further based on the validity of the link cookie.

14. The method of claim 13, wherein the link cookie remains valid for the duration of a web session between the remote user system and the merchant system.

15. The method of claim 13, wherein the link cookie remains valid for a plurality of web sessions between the remote user system and the merchant system.

16. A computer-implemented method of providing a transaction authorization for a transaction requested by a user to a merchant system, the transaction authorization being provided from a funds facilitation system that requires a funds facilitation user authentication, the transaction authorization being provided to a trusted merchant system without requiring user input of any funds facilitation user authentication information in excess of merchant authentication information required by the merchant system, the method comprising:

executing instructions in a processor-implemented system for receiving a transaction authorization request from the merchant system, the transaction authorization request containing a merchant ID, a merchant user ID, and a transaction amount;

executing instructions in a processor-implemented system for identifying a funds facilitation system user ID based on the merchant ID and the merchant user ID;

executing instructions in a processor-implemented system for determining satisfaction of the funds facilitation user authentication based on the merchant system associated with the merchant ID having a trusted status with the funds facilitation system and the existence of a funds facilitation system user ID that is associated with both the merchant ID and the merchant user ID;

executing instructions in a processor-implemented system for providing a transaction authorization message or a transaction denial message to the merchant system based on account information associated with the funds facilitation system user ID and the transaction amount.

17. The method of claim 16, wherein a transaction authorization message is provided to the merchant system if the account information identifies sufficient funds in the user'"'"'s account for paying the transaction amount.

18. The method of claim 17, wherein an additional funds identification interface is provided to the user if the account information identifies insufficient funds in the user'"'"'s account for paying the transaction amount.

19. The method of claim 16, wherein a transaction authorization message is provided to the merchant system if the account information identifies sufficient funds in the user'"'"'s account for paying the transaction amount and the transaction amount is less than a high-value transaction threshold.

20. The method of claim 16, wherein the transaction authorization request from the merchant system is signed, wherein satisfaction of the funds facilitation user authentication is further based on a validation of the transaction authorization request signature.

21. The method of claim 16, wherein the user is validated at the merchant system using merchant authentication information provided by the user to the merchant system prior to the transmission of a transaction authorization request from the merchant system.

22. The method of claim 21, wherein the merchant authentication information is a username and password combination.

23. The method of claim 16, wherein a user that is authenticated at the merchant system is able to make the transaction request without any keyboard input following the user accessing a webpage displaying a product or service for sale.

24. The method of claim 16, wherein the user has provided account linking information to one of the merchant system or the funds facilitation system prior to the user making a transaction request;

wherein the account linking information enables the merchant system or the funds facilitation system to track an association between a merchant user ID and a funds facilitation user ID.

25. The method of claim 16, wherein the funds facilitation system requires additional user input in excess of the merchant authentication information required by the merchant system to satisfy the funds facilitation user authentication requirement if the merchant system does not have a trusted status with the funds facilitation system.

26. The method of claim 25, wherein the additional user input includes a funds facilitation system username and password combination, a funds facilitation dynamic username and password combination, or user biometric data.

27. A computer-implemented system for providing a transaction authorization for a transaction requested by a user to a merchant system, the transaction authorization being provided from a funds facilitation system that requires a funds facilitation user authentication, the transaction authorization being provided to a trusted merchant system without requiring user input of any funds facilitation user authentication information in excess of merchant authentication information required by the merchant system, comprising:

a processor;

a computer-readable storage medium containing instructions which when executed on the processor, cause the processor to perform operations including;

receiving a transaction authorization request from the merchant system, the transaction authorization request containing a merchant ID, a merchant user ID, and a transaction amount;

identifying a funds facilitation system user ID based on the merchant ID and the merchant user ID;

determining satisfaction of the funds facilitation user authentication based on the merchant system associated with the merchant ID having a trusted status with the funds facilitation system and the existence of a funds facilitation system user ID that is associated with both the merchant ID and the merchant user ID;

providing a transaction authorization message or a transaction denial message to the merchant system based on account information associated with the funds facilitation system user ID and the transaction amount.

28. The system of claim 27, wherein a transaction authorization message is provided to the merchant system if the account information identifies sufficient funds in the user'"'"'s account for paying the transaction amount.

29. The system of claim 28, wherein an additional funds identification interface is provided to the user if the account information identifies insufficient funds in the user'"'"'s account for paying the transaction amount.

30. The system of claim 27, wherein a transaction authorization message is provided to the merchant system if the account information identifies sufficient funds in the user'"'"'s account for paying the transaction amount and the transaction amount is less than a high-value transaction threshold.

31. The system of claim 27, wherein the transaction authorization request from the merchant system is signed, wherein satisfaction of the funds facilitation user authentication is further based on a validation of the transaction authorization request signature.

32. The system of claim 27, wherein the user is validated at the merchant system using merchant authentication information provided by the user to the merchant system prior to the transmission of a transaction authorization request from the merchant system.

33. The system of claim 32, wherein the merchant authentication information includes a username and password combination, a dynamic username and password combination, or user biometric data.

34. The system of claim 27, wherein a user that is authenticated at the merchant system is able to make the transaction request via a mouse-click of an interface button without any keyboard input following the user accessing a webpage displaying a product or service for sale.

35. The system of claim 27, wherein the user has provided account linking information to one of the merchant system or the funds facilitation system prior to the user making a transaction request;

wherein the account linking information enables the merchant system or the funds facilitation system to track an association between a merchant user ID and a funds facilitation user ID.

36. The system of claim 27, wherein the funds facilitation system requires additional user input in excess of the merchant authentication information required by the merchant system to satisfy the funds facilitation user authentication requirement if the merchant system does not have a trusted status with the funds facilitation system.

37. The system of claim 27, wherein the additional user input includes a funds facilitation system username and password combination, a funds facilitation dynamic username and password combination, or user biometric data.

38. The system of claim 27, wherein the instructions further cause the processor to access a remote user system to verify that a link cookie is stored on the remote user system, the link cookie including information to confirm the user'"'"'s authorization of the trusted status of the merchant system, and wherein satisfaction of the funds facilitation user authentication is further based on a successful verification of the link cookie.

39. The system of claim 38, wherein the instructions further cause the process to verify that the link cookie stored on the remote user system is valid, and wherein satisfaction of the funds facilitation user authentication is further based on the validity of the link cookie.

40. The system of claim 39, wherein the link cookie remains valid for the duration of a web session between the remote user system and the merchant system.

41. The system of claim 39, wherein the link cookie remains valid for a plurality of web sessions between the remote user system and the merchant system.

42. A method of processing an electronic payment at a merchant system, comprising:

receiving at the merchant system, authentication information that identifies an account holder with the merchant system;

receiving at the merchant system, a transaction request that specifies payment from the funds facilitation system;

comparing the authentication information with account information stored in a database associated with the merchant system to identify a merchant user identification associated with the account holder;

generating a transaction authorization request that includes the merchant user identification and that also includes a merchant identification, the merchant identification being an identification associated with the merchant system in the funds facilitation system;

transmitting the transaction authorization request from the merchant system to the funds facilitation system so that the funds facilitation system can compare the merchant identification with merchant data stored in the funds facilitation system to determine if the merchant system has been categorized by the funds facilitation system as a trusted merchant, and based on a determination that the merchant system has been categorized as a trusted merchant, transmit an electronic communication from the funds facilitation system to the merchant system to approve the transaction authorization request without the funds facilitation system receiving any additional authentication information from the account holder;

receiving the electronic communication from the funds facilitation system at the merchant system; and

based upon receipt of the electronic communication, the merchant system approving the transaction request.

43. The method of claim 42, wherein the authentication information includes a username and password.

44. The method of claim 42, wherein the funds facilitation system requires additional authentication information from the account holder for an initial transaction authorization request initiated by the account holder from the merchant system, and wherein approval without additional authentication information is available for subsequent transaction authorization requests initiated by the account holder from the merchant system.

45. A method of processing an electronic payment transaction with a merchant system, comprising:

receiving at a funds facilitation system a first transaction authorization request from the merchant system;

in association with the first transaction authorization request, receiving authentication information from an account holder who initiated the first transaction authorization request to verify the identity of the account holder in relation to an account with the funds facilitation system;

based on a successful verification of the authentication information, generating cookie information associated with the account holder and the merchant system and storing the cookie information at a remote user system of the account holder;

in response to the first transaction authorization request and the successful verification of the authentication information, transmitting a first electronic communication from the funds facilitation system to the merchant system to approve the first transaction authorization request;

receiving at the funds facilitation system a subsequent transaction authorization request from the merchant system;

in response to the subsequent transaction authorization request, verifying that the cookie information is stored at the remote user system of the account holder and is valid; and

based on a successful verification that the cookie information is stored at the remote user system and is valid, transmitting a subsequent electronic communication from the funds facilitation system to the merchant system to approve the subsequent transaction authorization request without the funds facilitation system again receiving the authentication information from the account holder.

46. The method of claim 45, wherein the cookie information stored on the remote user system remains valid for the duration of a web session between the remote user system and the merchant system.

47. The method of claim 45, wherein the cookie information stored on the remote user system remains valid for a plurality of web sessions between the remote user system and the merchant system.

48. The method of claim 45, wherein the first transaction authorization request and the subsequent transaction authorization request are transmitted by the merchant system after the merchant system has received and verified authentication information from the account holder in relation to an account with the merchant system.