system overview - aci worldwide€¦ · system can equally interact with devices via browser based...

MoneyGUARD System Overview

NOT FOR REPRODUCTION. FOR INFORMATION PURPOSES ONLY. Company confidential

© 2014 Spectrum Message Services Pty Ltd.

SYSTEM OVERVIEW

Grow confident, loyal customers profitably

Introduction




NoticesCopyright

© 2014 Spectrum Messages Services Pty Ltd. All rights reserved.

This guide cannot be reproduced, published or disclosed, in whole or in part, by any meanswithout the prior written permission of Spectrum Message Services Pty Ltd. This guide isprovided to the recipient under the terms of the non-disclosure agreement signed by thatrecipient and Spectrum Message Services Pty Ltd. This guide must not be disclosed to anyperson or organisation otherwise than as set out in the terms of that non-disclosureagreement.

The information contained in this guide, while accurate at the time of printing, is subjectto change without notice.

Trademarks

The Spectrum Message Services logo and the MoneyGuard name are trademarks ofSpectrum Message Services Ltd.

All product, brand and trade names used in this publication are the property of theirrespective trademark holders.




Contact Spectrum Message Services

For more information about Spectrum Message Services and its products, contact:

Phone: +61 2 89689307Web: www.spectrummessage.com.auE-mail: [email protected]




Table of Contents:

Table of Contents: ...........................................................................................4

Introduction to MoneyGuard ..........................................................................5

Why do you need a system?............................................................................8

Stay in control of your systems:............................................................................9

MoneyGuard Alerting Strengths....................................................................10

The main strengths of a MG mobile alerting system are: ......................................10

MoneyGuard business case: ...............................................................................10

Protect your investments: ..................................................................................11

ACI integration:.............................................................................................11

MoneyGUARD architecture............................................................................13

Base Systems Overview .....................................................................................13

MoneyGUARD Core System ................................................................................13

MoneyGuard Application Environment .................................................................14Business Flows ........................................................................................................................................................................14Business Objects ....................................................................................................................................................................14

MoneyGUARD Logical Architecture ......................................................................14

Core Modules ....................................................................................................16Database Server .....................................................................................................................................................................16MoneyGuard Transaction Engine ......................................................................................................................................16Billing module ..........................................................................................................................................................................16Enrolment WEB service ........................................................................................................................................................17Mobile browser and data extension .................................................................................................................................17Administrative client ..............................................................................................................................................................18Batch processing module ....................................................................................................................................................19Campaign tool .........................................................................................................................................................................19Interface modules ..................................................................................................................................................................20Call centre Interface..............................................................................................................................................................20Two factor authentication ...................................................................................................................................................20

Some examples: ............................................................................................21

SMS interaction:............................................................................................21

Browser application: .....................................................................................21

Conclusion:....................................................................................................23




Introduction to MoneyGuardMoneyGuard is an interactive mobile alerting, self-service and transaction platform that,although not restricted to this, has its prime application in banking. MoneyGuard cancommunicate with mobile devices via a range of interfaces such as Email, SMS, MobileBrowser, IVR, Data channel, and future messaging standards. MoneyGuard is alsointegrated with a range of back or front end processing and fraud monitoring systems.Specifically the ACI assets such as BASE24, BASE24-eps, Proactive Risk Manager, ACIIssuer, Postilion and other platforms. It can be used for transactional push as well as pullservices. MoneyGuard provides the interface between mobile channels and transactionalsystems based on a flexible business flow.

The entire solution is database driven and logs all incoming and outgoing message ortransaction activity. The system allows the creation of various mobile phone interactionsusing its flow based script driven architecture to enable secure remote client interactionfrom smart phones with a variety of mobile browser or application environments. Thesystem can equally interact with devices via browser based screens, SMS commands,mobile data channels, IVR or email messages.

The Core system has first been in use with OTP Bank in Hungary where it has in excess of1.5 million users and sends out 17M messages a month. One of its uses in this applicationis that it provides users with near real time alerts on credit or debit card transactions, andhas reduced the fraud in Hungary to the world’s lowest rate of less than 0.3 basis pointsversus a much higher global average.

The system can easily be customised by either bank staff, third parties or SMS PL bymodifying business scripts using a graphical tool to add further interactive as well as pushbased services. A screen editor is provided to allow the definition of user friendly input andoutput screens. These screens can be used directly or in conjunction with a local phoneapplication. The SMS messages are defined in multi-lingual templates.Some of the services the system has provided:

Transaction notification to the cardholder with detail on merchant name andlocation in near real time based on fraud alerts or customer preferences

Interactive card blocking on BASE24, BASE24-eps, PRM or Postilion

Interactive Balance and Mini statement inquiry

Interactive gaming

QR based P2P payments

Card activation

Exchange rate inquiry

Stock quotes

EFT Transaction authorisation

Mobile phone top up or other virtual POS applications

Bill payments

Two factor authentication




Variable alert limit setting

Other data queries and collections

NFC wallet in the cloud

Everyday interactive contact with the customers

Builds confidence

Builds loyalty

Done profitably by creating fee income

Reduces call centre staff interaction

Provides new services




MoneyGUARD connection diagram




Why do you need a system?Mobile payments are one of the fastest growing areas in the payments industry.According to In-stat research it is forecast to reach 45 billion transactions per year in2015.

Most cardholders now hold a mobile phone, and increasingly the majority of these aresmart phones, followed by feature phones with internet access. The datacommunications costs are coming down at the same time. The world’s 7 billion peoplenow own over 7 billion mobile phones which are getting increasingly smart. It is foreseenthat smart phones will have a penetration of more than 75% in the next 4 years. Insome markets this has already been achieved.

Simply adding SMS gateway capability to existing banking systems for mobile alertingwill not suffice to manage the rapid growth in volume and applications, and channels.

Getting a dedicated MoneyGuard system caters for a comprehensive customer contactstrategy with many use cases. The applicability can be split into three main applicationareas: Mobile Interactive Alerting, Mobile Self Service and Mobile Payments.

When creating such a system you have to take care of the following issues:

• Redundancy and fault tolerance

• High speed transaction filtering and processing

• Dynamic creation of multi- lingual messages or browser screens in Near Real Time

• Creation of range of fraud and service alerts directly from the transactionalenvironment in high speed

• Cardholder data management

• Interfaces to external systems (PRM, BASE24-eps, Postilion or other ISO8583)

• Billing for alerts and transactions

• Administration, reporting and management

• Enrolment via console, bulk or web interface

• Processing of incoming requests via browser or sms

• Connection to multiple gateways

• Provision of a dynamic development environment allowing for a single platformsolution for SMS alerting, mobile information services and mobile payments.

• Solution platform for the emerging market of NFC, P2P payments andmicropayments.

• Ability to change functionality without down time

In short create the environment that allows you to keep up with the future demands of thisincreasingly important channel.




Stay in control of your systems:

Many payment and also mobile systems provide functionality in a code driven way.Customisations often have to be performed by specialist staff at the supplier.

As MoneyGuard separates the business logic from the technical interfaces, it becomesmuch easier to customise. MoneyGuard comes with a number of graphical based toolsallowing modification of business flows, definition of mobile screens and messages.

The modules that interface with the core payment systems exchange data via clearlydefined protocols and use an internal messaging queue to relate to all other modules inthe system.

The Database driven architecture also allows the easy definition of new clientsparameters, new client medias, new sub systems and transaction types. New interfacescan also easily be added to the architecture. Extensive use of SOAP web services allowsfor easy updating of client data and parameters.

All of this means that Financial Institutions can choose their level of vendor dependencebetween being highly self-sufficient in development to outsourcing to a trusted thirdparty.




MoneyGuard Alerting StrengthsThe main strengths of a MG mobile alerting system are:

It is directly interfaced with the transactional host systems (eg BASE24, ACI Issuer, Postilionor BASE24eps), or the fraud monitoring system (eg PRM) and therefore delivers thetransactions near real time to the mobile phone.

It sends enough context in the message for the user to relate immediately to the transaction.

It is interactive in nature and accepts a blocking command from the card holder, a reply to amarketing message or an information request.

It has a range of interfaces with normal legacy systems, as well as Help Desks and IVRsystems.

It uses Business Rules and a web based development environment that allow for easy usercustomisation.

It is scalable and has built in redundancy.

Meets PCI/DSS compliance requirements

It provides the cheapest and fastest channel to provide customer service.

It generates an up to date client database containing mobile phone numbers.

The scripting language allows for the easy building of new functionality of interfaces andsupports multi lingual applications

Has built in campaign tools

Has a built in billing engine

Can connect to multiple gateways and can mix email, SMS, voice and data services in a singletransaction

Browser functionality has application look and feel but does not require maintenance ofvarious OS specific phone applets.

MoneyGuard business case:

The business case for a interactive mobile alerting and messaging system is very strong:

When alerts are sent based on cardholder individual preferences then significantfee income can be generated from the messages

When alerts are sent based on fraud rules then the automation of the contactstrategy provides increased efficiencies, lower false positive ratios and quickeraction on fraud by cardholder participation

Promotes good customer service by notifying a cardholder immediately when acard is blocked or a transaction is declined and allowing them to take action

As the alerts are cheaper more rules can be created leading to an overall lowerfraud rate

Additional interactive services can be provided via browser and SMS that furthergenerate revenue and cost savings

SMS is the most unobtrusive way to interact with the customer




Cheaper to provide new services on a single development environment ratherthan creating and maintaining multiple bespoke systems for each channel.

Protect your investments:

For many institutions it can be costly and time consuming to continue to keep up withthe rapid change in payment standards and developments in mobile platform.

As MoneyGuard separates the business logic from the actual interfaces and paymentengines, it is much easier to keep up to date with changes by only replacing thosemodules and interfaces affected.

The core logic, the robust housekeeping, the billing, the client database and the platformredundancy, and stability remain regardless of these changes.

ACI integration:MoneyGuard has been closely integrated with the ACI assets. This chapter will briefly address this.

PRM:MoneyGuard can be used to generate SMS alerts based on the firing of specific rules replacingcalls with automated interactive SMS.

MoneyGuard can also use the PRM transaction data to generate alerts based on customerpreferences by amount and transaction type. The PRM user interface will show the SMS interactionin the normal review window and tieback can be used when replies are received from thecustomer.

It can also automatically send an alert to a customer to notify them of a card being blocked by aReal Time rule and allow the customer to respond or unblock by Icing the account.

BASE24, BASE24-eps or Postilion:These platforms can route transaction advices to MoneyGuard upon which MoneyGuard can sendalerts based on transaction type and amount threshold (eg ATM>100, POS>50, CNP>20 and alloverseas). Automatic card blocking can be done on an SMS response with all these platforms.Interactive balance enquiries are also an often used feature.

In the self service area we can provide Balance information, last transaction, P2P payments,Cardless ATM, and transaction profiling by the cardholder themselves.

ACI Issuer:A range of event driven push alerts and interactive pull requests can be offered with the ACIIssuer system. Thresholds can be defined for eg minimum balance, transaction levels, and alertsgenerated when needed.

A self-service client can also be provided for various queries and interactive settings.

Other systemsIntegration with other ACI assets such as Universal On line Banker, On Line Banker, EnterpriseBanker, Money Transfer System, and Retail Commerce Server can be offered.




MoneyGuard can also be integrated with non ACI systems, such as VisionPlus. Other bespokeinterfaces can be created on request or access can be provided via web services that can be calledfrom external systems.

An Universal Payments (UP) hub interface has also been defined to interconnect MoneyGuard withexternal systems.




MoneyGUARD architectureBase Systems Overview

MoneyGuard solves the problem of multi-service SMS, Email, IVR or mobile data provision with acore platform that handles those functions common to all mobile services. This is combined withan application environment, controlled by the integral Transaction Engine, which runs a BusinessFlow created with a graphical Flow editor supplied with the system.

The Operation Support components and Integration Support components are carefully designed toensure that MoneyGUARD can be easily administered and quickly integrated with corporate legacysystems.

MoneyGUARD Core System

The MoneyGUARD Core consists of

Transaction Processing

Scaling

Redundancy

Access Control

Integration Support

System Administration

Security.




MoneyGuard Application Environment

MoneyGuard is designed to allow users to customise the system to suit individual needs.

Business Flows

This is the most commonly used method to customise MoneyGuard; it is a simple and quickmethod of customising the system to implement Business Rules. Business Flows define howMoneyGuard handles transactions. The Business Flows are created with a graphical flow editor toolthat allows each customer to decide on the business logic of how events are processed.

One customer may want a card automatically blocked on an incoming message whilst another maywant to alert the call centre and ring the cardholder.

With the flow editor various actions can be initiated that involve the sending of an SMS, theexecution of a financial transaction, the information exchange via browser based screens, or anapplication on a smart phone or tablet, or to look up client data on the database.

Business Objects

These are more complex than scripts and generally consist of interface modules that can becalled from the flow. Business Objects provide the specific functionality needed to talk to anothersystem, and when needed may provide their own specific configuration and customisationinterfaces. Business Objects insulate core functions from application specific ones thus enabling awide range of services to be implemented on a single MoneyGuard Platform. As we are an ACIpartner, standard objects exist to interface with BASE24eps, BASE24, Postilion, ACI Issuer andPRM. Interfaces to other transactional or fraud monitoring systems can easily be added.

MoneyGUARD Logical Architecture




MoneyGUARD consists of a set of software modules and interfaces to provide the richfunctionality, flexibility, reliability and performance that makes it possible for the system tohandle a high number of transactions real time in a 24/7 environment.

MoneyGUARD’s Software architecture




Core Modules

Database Server

The database is the core of the system. All modules communicate with each other via acentral message queue. The database stores the Message queue as well as all the client dataand management data required to interact with cardholders. The system stores client data(card numbers, phone numbers, filtering information, etc.), prices (packages, message andtransaction costs for billing), system data (message template structures and otherparameters), a log of all sent and received sms, email messages and transactions, and thescripts and flows. The system typically runs on an SQL server. The database can be replicatedor clustered for redundancy and load balancing.

Currently Spectrum Message Services Pty Ltd supports interaction with MS-SQL, ORACLE andDB2 servers.

MoneyGuard Transaction Engine

The Transaction Engine is the module that implements the core transaction flow messagehandling functionality of the MoneyGuard system:

Outgoing traffic

Listens to the Host and External interfaces to see if there is any transmittable dataavailable

Constructs an SMS message, email or screen based on the transaction data and clientdata

Forwards the constructed message to the SMS gateway, email or browser module

Updates the client and transaction records

Incoming traffic

Listens to the GSM and Data IF to see if there is an incoming SMS message or dataexchange

Analyses the data

Checks sender authentication or cardholder verification

Forwards the transaction to the corresponding module

Updates the client and transaction records

Billing module

The billing module is a scheduled process that extracts billing information from thetransaction and client data according to the billing rules. The format of the billing informationis a readable text file.




Enrolment WEB service

The enrolment WEB service is a front-end https SOAP based web service that communicateswith either internet banking pages at the Financial Institution or its CRM system to allow self-service customer enrolment and data maintenance. It is connected to the client database andgives the clients direct access to their configuration settings. Using this front-end the clientscould be enabled to:

Subscribe/unsubscribe to/from the service

Add/delete a bank card number from their list

Adding/modify phone numbers

Setting/modifying filtering information(ATM, POS, value limit)

Subscribe to other alerts or services

Mobile browser and data extension

This module consists of a MoneyGuard CGI engine that allows the dynamic painting of formson the mobile browser of a mobile device, or within a native application. The forms are drivenby the flow engine. Mobile data support is provided in the flow engine by allowing the user todefine interactive web screens that are mobile device friendly. The user can create WebFormnodes that generate html output visible on any mobile device with a browser. Any dataentered by the user is returned to the flow for processing.

The flow shown above has blue nodes that depict html browser forms or SMS messages,green boxes that interact with the data base and orange boxes that show transactions. Withthis graphical environment, customers can define their own mobile interaction using standard




business objects to interact with the underlying transactional systems. A screen editor isprovided which is optimised for the mobile platform to define the screens that are shown tothe customer.

The controls available to define mobile device friendly web pages are static text, pictures, editboxes (for free format data entry), combo boxes (drop down menus), buttons, radio groupsand check boxes and a number of other frequently used structures.

When combined with small applets on the phone then preset information and locationinformation can be used in the applications.

Administrative client

This front-end module is for the system administrators and used for the following tasks:

Systems monitoring

General purpose data access and manipulating

System parameters setup

Client maintenance

Message template editing and maintenance

Setting up of billing parameters

Defining client groups and organisations

Loading and managing the flows




Batch processing module

This module is a background process that accesses batch files on a given location andcreated in a defined format, and processes them as if they were entered one by one via theWEB interface or the Administrative client module. This is useful for processing large amountsof data coming from an external system, for example in the case of bulk take-on’s, or uponcard replacement this interface can be used to update the card information in the clientdatabase.

Campaign tool

This tool is used to plan and launch marketing campaigns. Subsections of the user data basecan be selected and several campaigns can run at the same time. The system allows thefollowing:

Selection of users:

o via SQL query from the MoneyGuard database

o by providing a file with the list of mobile phone numbers

Setting a start and end date during which messages are sent to the audience (oneper customer), choices are to run tasks daily weekly or monthly. Defining thetimeslot in the day during which campaign messages are sent to the users.

Defining the message content.

o Either a constant message

o Or a message including fields that are query related from an externaldatabase

Allowing users to respond and express their interest in receiving more informationand sending their phone details back to the CRM system

The tools has two levels of user rights:




o Ability to edit

o Ability to launch/stop campaign

User activity is logged in campaign tool

Interface modules

MoneyGuard has been integrated with various host environment and fraud monitoringtools. It can take a raw data feed of payment transactions as they occur in the applicablepayment message formats (eg ISO8583). The system is able to filter in excess of athousand transactions per second to send alerts based on customer set preferences. Thesystem can also read Alerts tables from fraud monitoring tools and can send sms alertswhen fraud rules are triggered.

Modules are available for BASE24BIC, BASE24-eps, PRM and other systems on request.

The PRM interface consists of a Reader module to obtain the transaction and alert feedand a Writer module to update the Action Table to notify operators of automated actionstaken

Call centre Interface

The system has a pop up interface that allows able a screen to be displayed to a fraud orcustomer service operator with the details of a customer request, the messages sent andreceived, as well as the customer details. This interface can also take the form ofinterfacing with a call centre queue or a direct tieback to the transaction host to blockcards or change other parameters such as daily limits.

Optionally IVR and Voice dialling can be provided as well.

Two factor authentication

This module allows the system to create a second factor number that is sent via SMS tothe cardholder’s mobile phone to authenticate the transaction when entered into thebrowser.




Some examples:

SMS interaction:

Browser application:

Mobile payment application




Picture shows payment with a mobile phone by reading a presented QR code from a POSscreen




Conclusion:MoneyGuard is a versatile product that can be used for a range of mobile interactiveservices using either SMS, email, voice or smart phone applications. The product has aproven scalable architecture and can be implemented at a small scale as well as in alarge systems environment.

It’s range of interfaces and unique scripting language make it ideally suitable for fast tomarket implementations in the mobile space. The core technology is provided by a teamof developers with experience in payment transaction processing, SMS and browserconnectivity, IVR systems and legacy host systems.

The system allows a high degree of customisation and personalisation by the FinancialInstitution staff itself, or its contracted resources, without the need for low level complexcoding. It comes with a graphical environment allowing the creation of SMS, email andBrowser interactions in simple flows.

The system has proven itself in the high availability secure 7/24 environment in thebanking world and has a wide range of applications.

Currently the system is installed by a range of clients across the world.

For further info please contact: [email protected]

system overview - aci worldwide€¦ · system can equally interact with devices via browser based...

Documents