|
|
 |
|
|
 |
|
Also see:
|
|
|
Home>
Products> Banking and Finance> Bank.companion> FAQs
Bank.companion
FAQs
We have Internet banking already
implemented. Can you provide mobile and SMS banking? If so, how
will this be integrated?
Yes, the product is designed and built with components that will
be customised and deployed to offer services over the mobile and
via SMS. This will be integrated with your existing Internet banking
system for the purpose of handling the customer profile and other
common details.
Can Bank.companion be deployed without
tampering with the existing system?
Banks will provide APIs/other interface details for the purpose
of retrieving relevant information from the Host system. We will
assist in developing an interface to the Host system. XML is one
of the data exchange formats currently used in this product.
What security features are built into
it for the purpose of handling financial transactions over the
Internet and mobile phone?
Security being a major concern to banks, we have built a number
of features at several levels to protect transactions over the
Internet.
Application Level:
- Unique ID and password
- Session level control
- Automatic time-out
- Maximum retry lock
- Challenge Response - secret codes for financial transactions
Lock on pages with transactions already processed
SIM number for identification of customer for SMS (Pull) banking
Personalised account codes for use in SMS (Pull) banking
Data Encryption:
- 128-bit encryption SSL and digital certificates (optional)
- WTLS (Wireless Transport Layer Security) 56-bit encryption
Are the functionalities/services restricted
to what is offered now? How easy is it to add customised functionalities
to suit our customers?
The services can be fully customised as per the requirement of the
bank. The design and architecture allow customisation with minimal
effort.
When GPRS arrives, will the software work
without major changes?
The software has been designed to support and work with GPRS with
minor modifications.
How effectively are the different delivery
channels integrated?
The product offers cross-channelling facility to customers. Customers
can request over their mobile and be served over the Internet (e.g.
statement of account). They can also configure required services
over the Internet and avail of them on their mobile (e.g. SMS alerts).
For a transaction conducted over the Internet, customers will receive
a confirmation on their mobile. The channels are fully integrated
and handled by a single software.
Upon what technology is the product built?
Using state-of-the-art Enterprise Java Beans (EJB) component-based
technology, it is built on a JavaTM 2 Platform, Enterprise Edition
(J2EE) standards.
What are the platforms on which the
product may be deployed?
As it uses EJB-based industry standard application server technology,
it runs on Windows NT and various flavours of Unix.
Can we initially go in for SMS banking
and later move on to adding other channels, viz. Internet and WAP?
Yes. The software is modular-based and the bank can be selective
in introducing the delivery channels in phases.
|
|
| |
 |
|