Abstract: A method is disclosed herein in accordance with an embodiment of the present invention. The method may include deriving at a mobile transaction platform a multi-dimensional context from one or more user transactions and determining at least one life occurrence based, at least in part, on the multi-dimensional context. The one or more user transactions may be conducted through the mobile transaction platform. The one or more user transactions may be stored on a third-party source. In an aspect, the at least one life occurrence has yet to occur. In another aspect of the invention, the life occurrence has already occurred. The multi-dimensional context may include at least one of user location information and life occurrence location information. The multi-dimensional context may include at least one of a time of life occurrence and a current time.

Abstract: A method is disclosed herein in accordance with an embodiment of the present invention. The method may include deriving at a mobile transaction platform a multi-dimensional context from one or more user transactions and determining at least one life occurrence based, at least in part, on the multi-dimensional context. The one or more user transactions may be conducted through the mobile transaction platform. The one or more user transactions may be stored on a third-party source. In an aspect, the at least one life occurrence has yet to occur. In another aspect of the invention, the life occurrence has already occurred. The multi-dimensional context may include at least one of user location information and life occurrence location information. The multi-dimensional context may include at least one of a time of life occurrence and a current time.

Abstract: Configuring a shareable widget interface to mobile wallet functions includes disposing a wallet module in a memory of a client device, and disposing a wallet companion applet in a secure element accessible by the client device, wherein the wallet companion applet facilitates access by at least one other applet and at least one wallet module to content that is stored in the secure element via a mobile wallet function sharable interface.

Abstract: A system for supporting transactions by mobile devices includes a mobile transaction platform server hosting and managing a plurality of wallet services and at least one interface by which a service provider may discover and access the wallet services to build and distribute at least one wallet service to a services ecosystem, wherein the at least one wallet service enables implementation of a mobile transaction according to a template.

Abstract: A system for supporting transactions by mobile devices includes a mobile transaction platform server hosting and managing a plurality of wallet services and at least one interface for deployment of the mobile transaction server within a network ecosystem used by a service provider. The service provider uses a resource of the mobile transaction platform to publish software that provides incremental functionality to a wallet application that operates on the mobile transaction platform.

Abstract: Facilitating exclusive access to a workflow of a service provider via a mobile wallet interface involves, within a client runtime environment, activating through the interface a service provider-specific application so that the service provider-specific application has exclusive access to a secure electronic transaction workflow of the service provider associated with at least one of the service provider-specific application and the wallet, while being denied access by the client runtime environment to any other service provider services or resources.

Abstract: Configuring a plurality of security isolated wallet containers on a single mobile device includes configuring at least one mobile transaction platform-specific application programming interface for facilitating access to secure mobile transaction platform resources by a wallet container executing on a mobile device; disposing a plurality of distinct wallet containers in a memory of the mobile device, wherein each wallet container interfaces with secure mobile transaction platform resources via the at least one application programming interface; disposing at least one service provider-specific wallet in each of the plurality of distinct wallet containers; and enforcing service-provider specific wallet security by a distinct wallet container accessing a portion of the secure mobile transaction platform resources via the at least one application programming interface.

Abstract: Configuring a plurality of security isolated wallet containers on a single mobile device includes configuring at least one mobile transaction platform-specific application programming interface for facilitating access to secure mobile transaction platform resources by a wallet container executing on a mobile device; disposing a plurality of distinct wallet containers in a memory of the mobile device, wherein each wallet container interfaces with secure mobile transaction platform resources via the at least one application programming interface; disposing at least one service provider-specific wallet in each of the plurality of distinct wallet containers; and enforcing service-provider specific wallet security by a distinct wallet container accessing a portion of the secure mobile transaction platform resources via the at least one application programming interface.

Abstract: A platform for performing secure personalized transactions in a multi-domain ecosystem includes a personalization tier that enables service provider personalization for one or more ecosystem elements stored on a mobile device. Further, the platform includes an enabling tier for facilitating interoperation between the personalization tier and a client device. The platform further includes a service tier that may be operating independently of the enabling tier and may enable service delivery for a plurality of services.

Abstract: In a platform comprising a service tier, an enabling tier, and a personalization tier, applying an expert engine to analyze one or more mobile device user and transaction environment requirements and configuring one or more platform features in accordance with the analysis.

Abstract: Isolating distinct service provider widgets within a wallet container is accomplished by configuring a widget to provide access to an issuer-specific service group of services that are accessible in a service tier of a multi-tier platform for providing secure transactions, determining widget isolation requirements for operating the widget, configuring a widget descriptor with the isolation requirements, and communicating with the configured widget that has been deployed on a mobile device to provide at least one service from the issuer-specific service group.

Abstract: Selecting ecosystem features for inclusion in operational tiers includes taking a reference implementation of a specific application adapted to operate in a multi-domain computing ecosystem and, using a computer, breaking down the reference implementation into service related components, determining ecosystem participants for the reference implementation, and using a feature allocation engine to configure operational features that enable one of the service related components.

Abstract: A method for performing an electronic transaction over two distinct networks with a mobile wallet comprises the steps of receiving form of payment information from a mobile wallet over a first wireless network of a retail environment with a mobile device on which the mobile wallet is deployed; sending second wireless network description information of the retail environment over the first wireless network to facilitate access to the second wireless network by the mobile device, wherein the first wireless network operates within access range of the second wireless network; sending service information from a service provider associated with the retail environment over the second wireless network to request execution of a service provider-specific widget on the mobile device; and completing the electronic transaction, that was initiated by receiving the default form of payment information, by exchanging payment confirmation information over the second network via the service provider-specific widget.

Abstract: Deploying an issuer-specific widget to a wallet container on a client device is accomplished by configuring a widget to provide access to an issuer-specific service group of services that are accessible in a service tier of a multi-tier platform for providing secure transactions, determining service-provider specific resource access requirements for operating the widget, configuring a widget descriptor with the access requirements, and communicating with wallet container to ensure successful deployment of the configured widget that meets the access requirements in the widget descriptor.

Abstract: Tokenizing a wrapper in a secure personalized transaction conducted within a multi-domain ecosystem involves mapping a portion of a plurality of information fields of an electronic transaction message received by a networked device of the multi-domain ecosystem to common format message fields that are then configured into a common format message. The configured common format message is wrapped in a protocol abstraction content wrapper, which is tokenized. The token and/or the wrapper is transmitted to a second networked device in the ecosystem for authentication of a transaction identifiable in the electronic transaction message.

Abstract: Updating a widget comprises receiving a query from a mobile device for the existence of an updated widget; transmitting information indicative of the availability of the updated widget to the mobile device; receiving a request for the updated widget from the mobile device; and transmitting the updated widget to the mobile device.

Abstract: Configuring a shareable widget interface to mobile wallet functions includes disposing a wallet module in a memory of a client device, and disposing a wallet companion applet in a secure element accessible by the client device, wherein the wallet companion applet facilitates access by at least one other applet and at least one wallet module to content that is stored in the secure element via a mobile wallet function sharable interface.

Abstract: Configuring a plurality of security isolated wallet containers on a single mobile device includes configuring at least one mobile transaction platform-specific application programming interface for facilitating access to secure mobile transaction platform resources by a wallet container executing on a mobile device; disposing a plurality of distinct wallet containers in a memory of the mobile device, wherein each wallet container interfaces with secure mobile transaction platform resources via the at least one application programming interface; disposing at least one service provider-specific wallet in each of the plurality of distinct wallet containers; and enforcing service-provider specific wallet security by a distinct wallet container accessing a portion of the secure mobile transaction platform resources via the at least one application programming interface.

Abstract: Configuring a shareable widget interface to mobile wallet functions includes disposing a wallet module in a memory of a client device, and disposing a wallet companion applet in a secure element accessible by the client device, wherein the wallet companion applet facilitates access by at least one other applet and at least one wallet module to content that is stored in the secure element via a mobile wallet function sharable interface.

Abstract: Configuring a plurality of security isolated wallet containers on a single mobile device includes configuring at least one mobile transaction platform-specific application programming interface for facilitating access to secure mobile transaction platform resources by a wallet container executing on a mobile device; disposing a plurality of distinct wallet containers in a memory of the mobile device, wherein each wallet container interfaces with secure mobile transaction platform resources via the at least one application programming interface; disposing at least one service provider-specific wallet in each of the plurality of distinct wallet containers; and enforcing service-provider specific wallet security by a distinct wallet container accessing a portion of the secure mobile transaction platform resources via the at least one application programming interface.