Multi-Directional Wallet Connector Apparatuses, Methods and Systems

• US 20130246261A1
• Filed: 03/13/2013
• Published: 09/19/2013
• Est. Priority Date: 08/18/2011
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Purves, Thomas, Mahadkar, Shilpak, Theurer, Tenni, Hammad, Ayman
• Granted Patent: US 9,355,393 B2
• Time in Patent Office: Days
• US Class Current: 705/41
• CPC Class Codes: G06Q 20/105 involving programming of a portable memory device, e.g. IC cards, "electronic purses"
• CPC Class Codes: G06Q 20/227 characterised in that multiple accounts are available, e.g. to the payer
• CPC Class Codes: G06Q 20/28 Pre-payment schemes, e.g. "pay before"
• CPC Class Codes: G06Q 20/36 using electronic wallets or electronic money safes

Abstract

The MULTI-DIRECTIONAL WALLET CONNECTOR APPARATUSES, METHODS AND SYSTEMS (“W-CONNECTOR”) facilitates the enrollment of payment accounts in a consumer'"'"'s virtual wallet. The consumer may be logged into their payment account issuer'"'"'s web site and designate one or more payment accounts for enrollment in a virtual wallet. The issuer may then share account, billing and/or other relevant information with the virtual wallet provider to facilitate the enrollment of the designated payment accounts in the virtual wallet. The W-CONNECTOR may also be configured to facilitate the creation and funding of pre-paid accounts in a consumer'"'"'s virtual wallet.

Claims

1. A multi-directional wallet service connection processor implemented method comprising:

receiving, via a processor, a wallet service connection request;

determining at least one entity to be involved in fulfilling the wallet service connection request, including any of a source entity and a target entity;

determining a wallet service connection source action and a wallet service connection target action;

determining a wallet service connection privilege associated with the at least one entity and the wallet service connection source action and the wallet service connection target action;

performing the wallet service connection source action on the source entity;

providing a result of the performed wallet service connection source action on the source entity to the target entity for execution of a complimentary wallet service connection target action on the target entity; and

obtaining a result of the performed complimentary wallet service connection target action.

2. The method of claim 1, wherein the at least one entity include a requestor entity.

3. The method of claim 2, wherein any of the source entity, the target entity, and the requestor entity include an identifier.

4. The method of claim 1, wherein the at least one entity include any of an issuer, a merchant, a consumer, a payment network, a digital wallet provider, a marketing partner, a loyalty partner, a shipping partner, a social network provider.

5. The method of claim 1, further comprising:

obtaining a context and an information type wherein the context and the information type are used to select the wallet service connection privilege.

6. The method of claim 1, wherein the wallet service connection source action is to retrieve a wallet management user interface specific to the source entity, and the wallet service connection target action is to map the retrieved wallet management user interface into a native wallet user interface and generate a native wallet user interface widget for extension.

7. A multi-directional wallet service connection system, comprising:

a processor; and

a memory disposed in communication with the processor and storing processor-issuable instructions to;

receive, via a processor, a wallet service connection request;

determine at least one entity to be involved in fulfilling the wallet service connection request, including any of a source entity and a target entity;

determine a wallet service connection source action and a wallet service connection target action;

determine a wallet service connection privilege associated with the at least one entity and the wallet service connection source action and the wallet service connection target action;

perform the wallet service connection source action on the source entity;

provide a result of the performed wallet service connection source action on the source entity to the target entity for execution of a complimentary wallet service connection target action on the target entity; and

obtain a result of the performed complimentary wallet service connection target action.

8. The system of claim 7, wherein the at least one entity include a requestor entity.

9. The system of claim 8, wherein any of the source entity, the target entity, and the requestor entity include an identifier.

10. The system of claim 7, wherein the at least one entity include any of an issuer, a merchant, a consumer, a payment network, a digital wallet provider, a marketing partner, a loyalty partner, a shipping partner, a social network provider.

11. The system of claim 7, further comprising:

obtain a context and an information type wherein the context and the information type are used to select the wallet service connection privilege.

12. The system of claim 7, wherein the wallet service connection source action is to retrieve a wallet management user interface specific to the source entity, and the wallet service connection target action is to map the retrieved wallet management user interface into a native wallet user interface and generate a native wallet user interface widget for extension.

13. A processor-readable tangible medium storing processor-issuable multi-directional wallet service connection instructions to:

receive, via a processor, a wallet service connection request;

determine at least one entity to be involved in fulfilling the wallet service connection request, including any of a source entity and a target entity;

determine a wallet service connection source action and a wallet service connection target action;

determine a wallet service connection privilege associated with the at least one entity and the wallet service connection source action and the wallet service connection target action;

perform the wallet service connection source action on the source entity;

provide a result of the performed wallet service connection source action on the source entity to the target entity for execution of a complimentary wallet service connection target action on the target entity; and

obtain a result of the performed complimentary wallet service connection target action.

14. The medium of claim 13, wherein the at least one entity include a requestor entity.

15. The medium of claim 14, wherein any of the source entity, the target entity, and the requestor entity include an identifier.

16. The medium of claim 13, wherein the at least one entity include any of an issuer, a merchant, a consumer, a payment network, a digital wallet provider, a marketing partner, a loyalty partner, a shipping partner, a social network provider.

17. The medium of claim 13, further comprising:

obtain a context and an information type wherein the context and the information type are used to select the wallet service connection privilege.

18. The medium of claim 13, wherein the wallet service connection source action is to retrieve a wallet management user interface specific to the source entity, and the wallet service connection target action is to map the retrieved wallet management user interface into a native wallet user interface and generate a native wallet user interface widget for extension.

19. A multi-directional wallet service connection apparatus, comprising:

a processor; and

a memory disposed in communication with the processor and storing processor-issuable instructions to;

receive, via a processor, a wallet service connection request;

determine at least one entity to be involved in fulfilling the wallet service connection request, including any of a source entity and a target entity;

determine a wallet service connection source action and a wallet service connection target action;

determine a wallet service connection privilege associated with the at least one entity and the wallet service connection source action and the wallet service connection target action;

perform the wallet service connection source action on the source entity;

provide a result of the performed wallet service connection source action on the source entity to the target entity for execution of a complimentary wallet service connection target action on the target entity; and

obtain a result of the performed complimentary wallet service connection target action.

20. The apparatus of claim 19, wherein the at least one entity include a requestor entity.

21. The apparatus of claim 20, wherein any of the source entity, the target entity, and the requestor entity include an identifier.

22. The apparatus of claim 19, wherein the at least one entity include any of an issuer, a merchant, a consumer, a payment network, a digital wallet provider, a marketing partner, a loyalty partner, a shipping partner, a social network provider.

23. The apparatus of claim 19, further comprising:

obtain a context and an information type wherein the context and the information type are used to select the wallet service connection privilege.

24. The apparatus of claim 19, wherein the wallet service connection source action is to retrieve a wallet management user interface specific to the source entity, and the wallet service connection target action is to map the retrieved wallet management user interface into a native wallet user interface and generate a native wallet user interface widget for extension.

25. A mobile wallet transaction user interface processor-implemented method, comprising:

receiving a mobile wallet transaction checkout request and a mobile wallet identifier;

determining a wallet transaction preferred payment method;

generating a mobile wallet transaction overlay with the determined wallet transaction preferred payment method; and

providing the mobile wallet transaction overlay.

26. A third-party value added wallet service processor-implemented method, comprising:

receiving a third-party value added user interface integration request;

determining a digital wallet account identifier;

determining an integration privilege associated with a third-party and a digital wallet account;

wherein the digital wallet account is associated with the digital wallet account identifier; and

when the integration privilege is permitted, integrating the third-party value added user interface with a digital wallet account user interface.

27. A user-merchant reference linking processor-implemented method, comprising:

receiving a wallet credential log-in request;

creating a user-merchant relationship identifier, wherein the user-merchant relationship identifier is merchant specific;

storing user-merchant actions and associating the user-merchant actions with the user-merchant relationship identifier; and

associating non-merchant specific user history with a user history identifier, wherein the user history identifier is related to the user-merchant relationship identifier.

28. The method of claim 27, wherein the user-merchant actions include transaction history, preferences, and permissions.

29. The method of claim 27, further comprising:

receiving a wallet-merchant connection request;

providing the user-merchant actions and the non-merchant specific user history in response to the wallet-merchant connection request.

30. A user-merchant reference linking system, comprising:

a processor; and

a memory disposed in communication with the processor and storing processor-issuable instructions to;

receive a wallet credential log-in request;

create a user-merchant relationship identifier, wherein the user-merchant relationship identifier is merchant specific;

store user-merchant actions and associate the user-merchant actions with the user-merchant relationship identifier; and

associate non-merchant specific user history with a user history identifier, wherein the user history identifier is related to the user-merchant relationship identifier.

31. The system of claim 30, wherein the user-merchant actions include transaction history, preferences, and permissions.

32. The system of claim 30, further comprising:

receive a wallet-merchant connection request;

provide the user-merchant actions and the non-merchant specific user history in response to the wallet-merchant connection request.

33. A processor-readable tangible medium storing processor-issuable user-merchant reference linking instructions to:

receive a wallet credential log-in request;

create a user-merchant relationship identifier, wherein the user-merchant relationship identifier is merchant specific;

store user-merchant actions and associate the user-merchant actions with the user-merchant relationship identifier; and

associate non-merchant specific user history with a user history identifier, wherein the user history identifier is related to the user-merchant relationship identifier.

34. The medium of claim 33, wherein the user-merchant actions include transaction history, preferences, and permissions.

35. The medium of claim 33, further comprising:

receive a wallet-merchant connection request;

provide the user-merchant actions and the non-merchant specific user history in response to the wallet-merchant connection request.