Using a mobile wallet infrastructure to support multiple mobile wallet providers

At a computer system including at least one processor and a memory, a computer-implemented a method for performing a transaction for a customer using a third party mobile wallet owned by another entity than the customer, the method comprising the following:

• the computing system receiving communication from an agent terminal over one of a plurality of communication channels connected to the cloud-based transaction platform, the agent communication indicating that a customer desires to perform a transaction comprising a mobile wallet transaction using a third party mobile wallet, the mobile wallet transaction comprising at least one of a mobile wallet transfer in which funds are transferred from the mobile wallet of the customer to a third party mobile wallet, a mobile wallet withdrawal in which funds are withdrawn from the third party mobile wallet and provided to the customer, or a mobile wallet deposit in which funds are deposited into the third party mobile wallet;
• the computing system sending the agent communication to the third party mobile wallet platform;
• the computing system receiving communication from the third party mobile wallet platform confirming processing of the transaction, the transaction comprising at least one of the mobile wallet transfer, the mobile wallet withdrawal or the mobile wallet deposit;
• the computing system determining whether the mobile wallet transaction comprises the mobile wallet withdrawal and when the mobile wallet transaction is determined to comprise the mobile wallet withdrawal, generating and providing a perishable withdrawal code to the consumer, which is presented to the agent terminal to facilitate processing of the mobile wallet withdrawal;
• and
• the computing system sending communication to the agent terminal over one of a plurality of communication channels connected to the cloud-based transaction platform, the communication indicating confirmation of the processing of the transaction, wherein the computing system includes:
• one or more processors;
• system memory;
• an integration tier configured to manage mobile wallet sessions with a mobile device on which a mobile wallet application is installed and including web services communication mechanisms for interfacing with the mobile wallet application which is installed on a hardware SIM card as well as with a plurality of different device types over a plurality of different communication channels, the integration tier being configured to receive binary and text messages from the mobile device;
• a notification services engine configured to interface with the integration tier and to send Short Message Peer-to-Peer (SSMP) messages, Short Messaging Service (SMS) messages and Simple Mail Transfer Protocol (SMTP) messages over the different communication channels to different devices, including the mobile device, to interface with the mobile wallet application installed on the hardware SIM card;
• service connectors that are each configured to connect the computing system to a different third party system, each of the service connectors being configured as a separate module for integrating a corresponding external service to the computing system;
• a payment handler that exposes a common API for interacting with different payment processors;
• a security services engine that performs subscriber authentication utilizing a database-based Access Control List (ACL);
• and
• a rules engine configured to enforce constraints on financial transactions performed with the mobile wallet application.

One or more computer-readable hardware storage devices having stored thereon computer-executable instructions that are executable by the one or more processors of a computing system to cause the computing system to perform a transaction for a customer using a third party mobile wallet owned by another entity than the customer, comprising the following:

• the computing system receiving communication from an agent terminal over one of a plurality of communication channels connected to the cloud-based transaction platform, the agent communication indicating that a customer desires to perform a transaction comprising a mobile wallet transaction using a third party mobile wallet, the mobile wallet transaction comprising at least one of a mobile wallet transfer in which funds are transferred from the mobile wallet of the customer to a third party mobile wallet, a mobile wallet withdrawal in which funds are withdrawn from the third party mobile wallet and provided to the customer, or a mobile wallet deposit in which funds are deposited into the third party mobile wallet;
• the computing system sending the agent communication to the third party mobile wallet platform;
• the computing system receiving communication from the third party mobile wallet platform confirming processing of the transaction, the transaction comprising at least one of the mobile wallet transfer, the mobile wallet withdrawal or the mobile wallet deposit;
• the computing system determining whether the mobile wallet transaction comprises the mobile wallet withdrawal and when the mobile wallet transaction is determined to comprise the mobile wallet withdrawal, generating and providing a perishable withdrawal code to the consumer, which is presented to the agent terminal to facilitate processing of the mobile wallet withdrawal;
• and
• the computing system sending communication to the agent terminal over one of a plurality of communication channels connected to the cloud-based transaction platform, the communication indicating confirmation of the processing of the transaction, wherein the computing system includes:
• one or more processors;
• system memory;
• an integration tier configured to manage mobile wallet sessions with a mobile device on which a mobile wallet application is installed and including web services communication mechanisms for interfacing with the mobile wallet application which is installed on a hardware SIM card as well as with a plurality of different device types over a plurality of different communication channels, the integration tier being configured to receive binary and text messages from the mobile device;
• a notification services engine configured to interface with the integration tier and to send Short Message Peer-to-Peer (SSMP) messages, Short Messaging Service (SMS) messages and Simple Mail Transfer Protocol (SMTP) messages over the different communication channels to different devices, including the mobile device, to interface with the mobile wallet application installed on the hardware SIM card;
• service connectors that are each configured to connect the computing system to a different third party system, each of the service connectors being configured as a separate module for integrating a corresponding external service to the computing system;
• a payment handler that exposes a common API for interacting with different payment processors;
• a security services engine that performs subscriber authentication utilizing a database-based Access Control List (ACL);
• and
• a rules engine configured to enforce constraints on financial transactions performed with the mobile wallet application.