Remote Variable Authentication Processing

• US 20110178926A1
• Filed: 01/19/2011
• Published: 07/21/2011
• Est. Priority Date: 01/19/2010
• Status: Abandoned Application

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Lindelsee, Mike, Brand, Olivier, Dimmick, James, Dominguez, Benedicto
• Application Number:
  US13/009,177
• Publication Number:
  US 20110178926A1
• Time in Patent Office: Days
• US Class Current: 705/44
• 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

A remote variable authentication processing system is disclosed. A sending entity initiates a remote payment using an alias over an initiation channel. The alias may be associated with one or more nicknames that identify portable consumer devices and metadata. The metadata describes which channels are available for authentication. The sending entity selects a nickname and an associated authentication channel. The sending entity authenticates with an issuer over the selected authentication channel.

Claims

1. A method comprising:

receiving from a participant a message comprising an alias;

determining one or more consumer payment nicknames associated with the alias; and

sending the one or more consumer payment nicknames and metadata associated with each of the one or more consumer payment nicknames to the participant, the metadata describing authentication channels through which authentication of the one or more consumer payment nicknames can be conducted, wherein the participant presents the one or more consumer payment nicknames and the authentication channels to a sending entity.

2. The method of claim 1, further comprising receiving from the participant an initiation channel identifier and analyzing the metadata to determine compatibility data describing which authentication channel is compatible with the channel described by the initiation channel identifier and sending the compatibility data to the participant.

3. The method of claim 1, wherein the participant is a merchant.

4. The method of claim 2, wherein the authentication channels incompatible with the channel described by the initiation channel identifier are not selectable by the sending entity.

5. The method of claim 2, wherein the authentication channels incompatible with the channel described by the initiation channel identifier are not presented to the sending entity.

6. The method of claim 2, wherein if only one consumer payment nickname and authentication channel is compatible with the initiation channel identifier, then that consumer payment nickname and authentication channel is used to authenticate the consumer payment nickname.

7. The method of claim 1, further comprising receiving a consumer payment nickname and an authentication channel from the participant, the consumer payment nickname and authentication channel being selected by the sending entity.

8. The method of claim 7, further comprising analyzing the received consumer payment nickname to determine an authorizing entity and sending an authentication request message comprising an authentication channel identifier to the authorizing entity.

9. The method of claim 8, further comprising receiving an authentication response message from the authorizing entity, and sending the authentication response message to the participant, wherein the participant will notify the sending entity via the initiation channel of the authentication response message.

10. A non-transitory computer readable medium comprising code that when executed by a processor performs the method of claim 1.

11. A system comprising

a processor;

and

a computer-readable medium coupled to the processor, the computer readable medium comprising code executable by the processor for implementing a method comprising;

receiving from a participant a message comprising an alias;

determining one or more consumer payment nicknames associated with the alias; and

sending the one or more consumer payment nicknames and metadata associated with each of the one or more consumer payment nicknames to the participant, the metadata describing authentication channels through which authentication of the one or more consumer payment nicknames can be conducted, wherein the participant presents the one or more consumer payment nicknames and the authentication channels to a sending entity.

12. The system of claim 11, wherein the method further comprises receiving from the participant an initiation channel identifier and analyzing the metadata to determine compatibility data describing which authentication channel is compatible with the channel described by the initiation channel identifier and sending the compatibility data to the participant.

13. The system of claim 11, wherein the method further comprises receiving a consumer payment nickname and an authentication channel from the participant, the consumer payment nickname and authentication channel being selected by the sending entity.

14. The system of claim 13, wherein the method further comprises analyzing the received consumer payment nickname to determine an authorizing entity and sending an authentication request message comprising an authentication channel identifier to the authorizing entity.

15. A method comprising:

receiving from a payment processing network a message comprising a primary account number and an authentication channel identifier;

receiving from a sending entity, over an authentication channel described by the authentication channel identifier, a passcode;

authenticating the sending entity with the passcode with respect to a portable consumer device associated with the primary account number;

receiving a request for whether the sending entity successfully authenticated from the payment processing network; and

sending to the payment processing network whether the sending entity successfully authenticated.

16. The method of claim 15, further comprising sending a customer payment nickname associated with the primary account number and a request for the passcode to the sending entity.

17. The method of claim 15, further comprising sending a message to redirect the sending entity to a participant.

18. The method of claim 15, further comprising sending an authentication address to a payment processing network, the authentication address indicating where the sending entity may provide the passcode.

19. The method of claim 15, wherein the primary account number and authentication channel identifier are selected by the sending entity.

20. The method of claim 15, wherein the payment processing network sends the sending entity authentication status to a participant.