MultiCash Electronic Banking Internet Communication

Standard Updates

QUESTI ONS ANSWERS
1. Why do you want to upgrade
MultiCash and what
components are you
upgrading?
Your current J.P. Morgan MultiCash product connects to J.P. Morgan using
a communication protocol called File Transfer Access Method (FTAM).
This protocol, using an ISDN connection, has been replaced by a new and
more secure IP-based protocol called Electronic Banking Internet
Communication Standard (EBICS). We want to migrate all existing
MultiCash installations to this new industry standard.
As part of the EBICS implementation, we must upgrade your existing
MultiCash version to ensure that your MultiCash application is compatible
with EBICS. This will be done by a J.P. Morgan technical representative.

2. What is EBICS and how does
it differ to FTAM?
EBICS will continue to support all of the same transmission types as your
existing FTAM ISDN connection with the addition of enhanced, state-of-the-
art security, cost-effective improvement in the area of data and line
encryption and authentication (distributed digital electronic signatures) as
well as higher transmission speed. Data transferred between customer and
bank are first embedded in an XML container and then sent by means of the
Internet transport protocol HTTP using a secure transport method (TLS -
transport encryption).
Data is transmitted block by block, whereby each block is secured
using an authentication signature. If all blocks are not transmitted
successfully, a recovery function allows the session to pick up again
from the last successfully transmitted block.
As an additional feature, included with a view to future PKI-
schemes, the new standard allows the optional use of X.509
certificates to exchange the latest RSA keys between user and
bank. Compliance with security and audit requirements is a
priority. Transfers made via EBICS are confidential, since the data
content is secured not only for the transport but also encrypted.
Protection against manipulation is made by means of encryption
and a message authentic code (MAC) that ensure data integrity.
The sender is authenticated (i.e. server certificates and electronic
signature). The procedure also includes prevention of 'man-in-the-
middle attacks'. The security mechanisms comply with the latest
technical standards, in particular for personal digital signatures.
2009 J PMorgan Chase & Co. All Rights Reserved. J PMorgan Chase Bank, N.A. Member FDIC. Page 1 of 5
All services are subject to applicable laws and regulations and service terms.

QUESTI ONS ANSWERS
3. Why do I need to migrate?
Since 1995, it has been compulsory for all German Banks to comply with
the Banking Communication Standard (BCS), which has become the
industry standard for corporate payment transfers. As the existing BCS
standard cannot support the use via the Internet and with the view to
develop an International standard, the Zentraler Kreditausschuss (ZKA)
enhanced the BCS processes to make them suitable for Internet-based use
and built in some additional features such as the distributed digital
signatures. The resulting EBICS was recently adopted by the ZKA and has
now become the standard method to be used industry wide by all
payment systems using existing BCS methods.
EBICS will not only allow an Internet-based connection, but it will also
provide you with the ability to process SEPA payments, together with the
state-of-the-art security, cost-effective improvement in the area of data
and line encryption and authentication (distributed digital electronic
signatures) as well as higher transmission speed.
4. When will FTAM stop being
supported?
The existing BCS FTAM standard will stop being supported by December
30, 2010 by all German Banks.
5. Can I keep my existing FTAM
(ISDN) connection?
You can keep your existing FTAM connection until December 12, 2010, but
if you continue using FTAM, you will not be able to experience the
benefits of the connection and security enhancements offered through
EBICS
6. Will my dial in number
change?
No, we will not change your existing FTAM (ISDN) number currently stored
within the J.P. Morgan bank parameter settings - but as you migrate to
EBICS, the ISDN number would no longer be required.
7. Will my standard operational
practices change?
No, your existing operational practice does not need to change when
migrating to EBICS. We will need to slightly change the setting of your
J.P. Morgan bank parameter and each user will need to upgrade their
Electronic Signature, but the actual payment processes will stay the
same.
8. Will my communications
access be different?
Yes, you will use the Internet as a connection protocol and you will no
longer need your ISDN line, unless you continue to use other bank
parameter set ups supporting the FTAM connection method.
2009 J PMorgan Chase & Co. All Rights Reserved. J PMorgan Chase Bank, N.A. Member FDIC. Page 2 of 5
All services are subject to applicable laws and regulations and service terms.

QUESTI ONS ANSWERS
9. Will there be any hardware
change requirements?
This will depend on your existing hardware specifications, as only
MultiCash Version 3.21 with Release 007 will be EBICS and SEPA
compatible, please see below for a summary of minimum requirements.
Comms PC
Permanent Internet connection required (i.e. via Network)
MultiCash Client
Operating System: Windows (i.e. Windows XP)
EU/ES Medium: Floppy disc drive, USB connection slot or network server
Hardware Requirements: 500 MHz Pentium III, 128 MB RMA (recommended
256 MB RAM),40 GB HDD, CD-ROM drive, Mouse, Keyboard, Monitor
(resolution at 1.024*768) and Printer drivers / connection
MultiCash Server
Operating System: Windows (i.e. Windows 2003 server recommended with
NTFS [32bit], Windows XP or Windows Vista SVP1)
Hardware Requirements: 1 GHz. Pentium 4, 256 MB RAM, 40GB HDD (min.
50MB free space left), CD-ROM, Mouse, Keyboard, Monitor (resolution at
1.024*768)
Network
Recommended is a Network in Ethernet-Topology with 100Mbit
10. How will the MultiCash
upgrade affect my existing
electronic signature?
We will upgrade your electronic signature version, but you will be able to
continue using your existing signature for all bank parameter set ups,
including the ones still using the FTAM BCS standard.
There is no separate electronic signature for different banks required,
however each user will need to reinitialize with J.P. Morgan after the
upgrade to update our bank server with the new, extended security keys.
11. Can I continue using my
FTAM connection for other
bank parameter set ups?
Yes, you will be able to continue using your existing FTAM connection for
other banks until they no longer support the FTAM connection method.
Please confirm this with your other banking partners.
2009 J PMorgan Chase & Co. All Rights Reserved. J PMorgan Chase Bank, N.A. Member FDIC. Page 3 of 5
All services are subject to applicable laws and regulations and service terms.

QUESTI ONS ANSWERS
12. Is there any preparation that
I need to do prior to the site
visit?
Prior to the migration day
Please complete the MultiCash technical questionnaire supplied on the
Web site, as the data provided will enable us to provide you with an
outline of all requirements prior to the MultiCash upgrade, including
potential changes to your technical hardware or network set up.
Once a date has been scheduled for the migration, if banking
relationships outside of J.P. Morgan are also set up in MultiCash, we
would ask you to please contact these bank(s) in advance and inform
them of the upgrade. Due to the upgrade of MultiCash, Basis, FTAM, EBICS
and EU/ES modules, you will need to re-initialize with their bank
parameter files to ensure that your EUs/ESs will work after the upgrade.

On the day of the migration
Please ensure that the technical requirements, which will be confirmed
after receipt of the MultiCash technical questionnaire, will be available
on the day of migration.
Please ensure that the following users will be available to complete the
MultiCash upgrade:
All MultiCash users must be present to complete their user profile
initialization step for their EBICS connection to J.P. Morgan.
Technical IT contact must be present to ensure that full
Administrator access can be guarantied for the MultiCash upgrade
to all servers and client computers.
MultiCash Administrator must be present to ensure that the necessary
modifications to bank parameter file(s) and MultiCash in general can be
completed.
13. When will J.P. Morgan do the
upgrade?
We will contact you between the second and third quarter of 2009 to
discuss the MultiCash - EBICS migration with you in more detail and allow
you the opportunity to ask any further questions you might have. We will
also outline the migration requirements for your set up, any potential
preparation work required, schedule a migration date and overview of the
agenda for the migration day in more details when we have our initial
migration call with you.
Please note that you will need to complete the technical specification
questionnaire about your existing MultiCash set up in order to assist us
with the migration.
2009 J PMorgan Chase & Co. All Rights Reserved. J PMorgan Chase Bank, N.A. Member FDIC. Page 4 of 5
All services are subject to applicable laws and regulations and service terms.

QUESTI ONS ANSWERS
14. How long will it take?
The upgrade shouldn't take longer than a day, but we will contact you in
person to discuss the MultiCash upgrade and EBICS migration in more
detail with you, including an estimation of the completion time.
15. What training is required?
Depending on the version upgrade, there should only be minor differences
between your existing and the new MultiCash application and we will
contact you in person to discuss the MultiCash upgrade and EBICS
migration in more detail. We will cover an overview of the version
differences at this time. With regards to the transmission method change
from FTAM to EBICS, no training will be required as the actual
transmission process will stay the same.

16. What is the cost of migrating
my MultiCash to EBICS?
There will be no extra cost for the MultiCash upgrade or migration to the
EBICS BCS communication standard, as this is a banking industry-wide
rollout.



2009 J PMorgan Chase & Co. All Rights Reserved. J PMorgan Chase Bank, N.A. Member FDIC. Page 5 of 5
All services are subject to applicable laws and regulations and service terms.