Multi-directional wallet connector apparatuses, methods and systems

• US 9,959,531 B2
• Filed: 05/30/2016
• Issued: 05/01/2018
• 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
• Primary Examiner(s): LE, THIEN MINH
• Application Number:
  US15/168,127
• Publication Number:
  US 20160379192A1
• Time in Patent Office: 701 Days
• Field of Search: 235380
• 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 user-merchant reference linking processor-implemented method, comprising:

receiving, via a processor, 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;

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

performing a user-merchant action to obtain a wallet user interface;

mapping the wallet user interface into a native wallet user interface of a native wallet application; and

generating a native wallet user interface widget for extension of the native wallet application.

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

3. The method of claim 1, 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.

4. 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;

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

perform a user-merchant action to obtain a wallet user interface;

map the wallet user interface into a native wallet user interface of a native wallet application; and

generate a native wallet user interface widget for extension of the native wallet application.

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

6. The system of claim 4, 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.

7. 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;

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

perform a user-merchant action to obtain a wallet user interface;

map the wallet user interface into a native wallet user interface of a native wallet application; and

generate a native wallet user interface widget for extension of the native wallet application.

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

9. The medium of claim 7, 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.