Multi-directional wallet connector apparatuses, methods and systems
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.
1. A virtual wallet payment account linking processor-implemented method, comprising:
creating a user-merchant relationship identifier, wherein the user-merchant relationship identifier is merchant specific;
associating a user-merchant action with the user-merchant relationship identifier, the user-merchant action including selection of a payment button;
linking a native wallet application, a virtual wallet payment account, and a merchant website via the user-merchant relationship identifier, the merchant website displaying the payment button;
performing the user-merchant action to obtain, with the user-merchant relationship identifier, a wallet user interface for the native wallet application and an available payment method; and
mapping the payment button into one or more of the native wallet application and the merchant website.
2. The method of claim 1 , further comprising updating the payment button with data from one or more of the native wallet application, the virtual wallet payment account, and the merchant website.
3. The method of claim 2 , wherein the data includes one or more of an account status, artwork for a payment card corresponding to the virtual wallet payment account, an account balance, and a targeted offer.
4. The method of claim 2 , further comprising:
generating a native wallet user interface widget for extension of the native wallet application; and
updating the payment button includes updating the payment button within a native wallet user interface with data from one or more of the native wallet application, the virtual wallet payment account, and the merchant website via the native wallet user interface widget.
5. The method of claim 2 , further comprising:
generating a merchant website widget for extension of the merchant website; and
updating the payment button includes updating the payment button within the merchant website with data from one or more of the native wallet application and the virtual wallet payment account via the merchant website widget.
6. The method of claim 1 , further comprising dynamically updating the payment button with data from one or more of the native wallet application, the virtual wallet payment account, and the merchant website.
7. The method of claim 1 , further comprising communicatively linking a loyalty provider to one or more of the native wallet application and the merchant website.
8. A virtual wallet payment account linking system, comprising:
a processor; and
a memory disposed in communication with the processor and storing processor-issuable instructions for:
creating a user-merchant relationship identifier, wherein the user-merchant relationship identifier is merchant specific;
associating a user-merchant action with the user-merchant relationship identifier, the user-merchant action including selection of a payment button;
linking a native wallet application, a virtual wallet payment account, and a merchant website via the user-merchant relationship identifier, the merchant website displaying the payment button;
performing the user-merchant action to obtain, with the user-merchant relationship identifier, a wallet user interface for the native wallet application and an available payment method; and
mapping the payment button into one or more of the native wallet application and the merchant website.
9. The system of claim 8 , wherein the processor-issuable instructions include instructions for updating the payment button with data from one or more of the native wallet application, the virtual wallet payment account, and the merchant website.
10. The system of claim 9 , wherein the data includes one or more of an account status, artwork for a payment card corresponding to the virtual wallet payment account, an account balance, and a targeted offer.
11. The system of claim 9 , wherein the processor-issuable instructions include instructions for:
generating a native wallet user interface widget for extension of the native wallet application; and
the processor-issuable instructions for updating the payment button includes processor-issuable instructions for updating the payment button within a native wallet user interface with data from one or more of the native wallet application, the virtual wallet payment account, and the merchant website via the native wallet user interface widget.
12. The system of claim 8 , wherein the processor-issuable instructions include instructions for dynamically updating the payment button with data from one or more of the native wallet application, the virtual wallet payment account, and the merchant website.
13. The system of claim 8 , wherein the processor-issuable instructions include instructions for linking a loyalty provider to one or more of the native wallet application and the merchant website.
14. The system of claim 9 , wherein the processor-issuable instructions include instructions for:
generating a merchant website widget for extension of the merchant website; and
updating the payment button within merchant website with data from one or more of the native wallet application and the virtual wallet payment account via the merchant website widget.
15. A processor-readable tangible medium storing processor-issuable virtual wallet payment account linking instructions for:
creating a user-merchant relationship identifier, wherein the user-merchant relationship identifier is merchant specific;
associating a user-merchant action with the user-merchant relationship identifier, the user-merchant action including selection of a payment button;
linking a native wallet application, a virtual wallet payment account, and a merchant website via the user-merchant relationship identifier, the merchant website displaying the payment button;
performing the user-merchant action to obtain, with the user-merchant relationship identifier, a wallet user interface for the native wallet application and an available payment method; and
mapping the payment button into one or more of the native wallet application and the merchant website.
16. The medium of claim 15 , wherein the instructions include instructions for updating the payment button with data from one or more of the native wallet application, the virtual wallet payment account, and the merchant website.
17. The medium of claim 16 , wherein the data includes one or more of an account status, artwork for a payment card corresponding to the virtual wallet payment account, an account balance, and a targeted offer.
18. The medium of claim 16 , wherein the instructions include instructions for:
generating a native wallet user interface widget for extension of the native wallet application; and
the instructions to update the payment button include instructions for updating the payment button within a native wallet user interface with data from one or more of the native wallet application, the virtual wallet payment account, and the merchant website via the native wallet user interface widget.
19. The medium of claim 15 , wherein the instructions include instructions for dynamically updating the payment button with data from one or more of the native wallet application, the virtual wallet payment account, and the merchant website.
20. The medium of claim 15 , wherein the instructions include instructions for linking a loyalty provider to one or more of the native wallet application and the merchant website.