Multi-directional wallet connector apparatuses, methods and systems
First Claim
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 the wallet service connection target action on the target entity, wherein the wallet service connection target action is to map a wallet user interface obtained as a result of the wallet service connection source action into a native wallet user interface and generate a native wallet user interface widget for extension; and
obtaining a result of the wallet service connection target action.
1 Assignment
0 Petitions
Accused Products
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.
-
Citations
24 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 the wallet service connection target action on the target entity, wherein the wallet service connection target action is to map a wallet user interface obtained as a result of the wallet service connection source action into a native wallet user interface and generate a native wallet user interface widget for extension; and obtaining a result of the wallet service connection target action. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
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 the wallet service connection target action on the target entity, wherein the wallet service connection target action is to map a wallet user interface obtained as a result of the wallet service connection source action into a native wallet user interface and generate a native wallet user interface widget for extension; and obtain a result of the wallet service connection target action. - View Dependent Claims (8, 9, 10, 11, 12)
-
-
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 the wallet service connection target action on the target entity, wherein the wallet service connection target action is to map a wallet user interface obtained as a result of the wallet service connection source action into a native wallet user interface and generate a native wallet user interface widget for extension; and obtain a result of the wallet service connection target action. - View Dependent Claims (14, 15, 16, 17, 18)
-
-
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 the wallet service connection target action on the target entity, wherein the wallet service connection target action is to map a wallet user interface obtained as a result of the wallet service connection source action into a native wallet user interface and generate a native wallet user interface widget for extension; and obtain a result of the wallet service connection target action. - View Dependent Claims (20, 21, 22, 23, 24)
-
Specification