TagPay uses a modular architecture and is designed to function as a stand-alone mobile wallet solution and/or to function as a front-end end transaction technology to be integrated with existing wallet or bank back offices. The second approach is referred to "gateway" mode or GWTag™.

TagPay Modular Approach

The TagPay platform supports various modules. TagPay comes with a set of standard modules that can be activated or modified to meet the needs of a specific mobile money service. This modular approach offers the most complete and customizable mobile money platform.

TagPay used as a stand-alone platform

When used as a stand-alone platform TagPay's architecture is designed to manage stored value accounts. All of the modules depicted above are active and the GW back-office API is not used. The web interfaces for agents, users, merchants, and administrators are used and the account management is handled entirely within the platform.

Using TagPay with an external back office

GWTag™ is a way of using a TagPay™ platform with user accounts managed by an external Back-Office: typically a bank or an existing wallet. Users can make any of the existing transactions supported by TagPay (e.g. peer to peer transactions, payments on merchant's TagPay POS terminals, etc.) using the account managed by the external Back-Office and/or using the stored value account managed by the TagPay platform.

GWTag™ does not provide all the TagPay features and interfaces. Specifically, users can not access their transaction history or account settings on the Web. This function is instead provided by the external Bank/Wallet back-Office.

In order to work, GWTag™ needs to be connected to a account management platform (Back-Office) such as banking back office or any type of electronic wallet platform. The application uses standard PHP language and can be adapted to meet specific requirements. Dialogue protocols are based on HTTP or HTTPS, depending upon the customers’ architecture and requirements.

The following diagrams describe the technical architecture of a TagPay platform and the GWTag™ architecture and exchanges between the different entities.