Introduction to Online Banking -C1
The purpose of this user guide is to explain the current functionality available as part of Member Direct Online Banking Interface.
The Member Direct online access system is a web-based application that clients can use to perform basic banking functions. Note that the application does not perform any of these functions itself. Rather, it sends requests to the host banking systems to perform a function such as transferring funds or paying a bill. When the function is completed, the result is returned to the system, which then displays a message stating that the corresponding function is completed.
Members can do their online (internet) banking via Member Direct. Members login to Member Direct using their 16-digit Member card number (PAN) and password (PAC). The members should be a CIF customer. One card may have more than one account linked in it. Members should be able to view their own details and also the list of investment products they have invested in.
The users should be able to view their account summary and also the statement details. New accounts can be created by the members using the online (internet) banking via Member Direct and also the existing accounts can be renamed. Users are able to transfer funds between their own accounts and to others accounts. This funds transfer can be scheduled to future date also. For future dated transactions which are pending, there has to be a provision to delete the future dated transaction when it is in the pending status. At any time, the list of scheduled funds transfer can be viewed.
The other main provision required is that the users should be able to make the bill, provided the vendors to which they want to pay the bill are added to the account from the vendor list provided by the bank. This payment also can be scheduled for future date and if transactions are not yet done, there will be provision to delete the transactions.
The interface development would consist for two parts:
- Interface ISO messages (request and response) to Temenos Transact.
- Development is done in Temenos Transact for the member direct interface, for its various functions or events.
MDI Narrative:
- Extra narration is required to be displayed for MDI to provide transparency of exchange rates. It’s a requirement by Payment Card Industry Data Security Standard (PCI DSS) and applies wherever account data is stored, processed or transmitted.
- PCI DSS requirement states that, “Mask PAN when displayed; the first six and last four digits are the maximum number of digits you may display”.
Members can perform the following functions through Member Direct which updates the banking system in real time.
List of functionality supported:
- Login in using the PAN and PAC.
- View account summary; which is list of all their accounts and respective balances under each membership.
- View account details:
- Demand accounts: Current balance and current rate.
- Term deposits: Principle investment, current balance, term start date, term maturity, Interest rate, and where the interest will be applied at interest period and what will happen to funds at maturity.
- Loans: Loan type, balance, interest rate, maturity date, schedule, accrued interest, interest charged etc.
- Tax sheltered: (RRSPs and RRIFs). : Contract number, contract type, balance, contract open date etc.
- Generate online statements.
- Transfer money between accounts immediately or setup onetime or recurring automatic transfers.
- Add or delete vendor for bill payment processing.
- Make bill payments to external payees (utilities companies, credit cards, property taxes, telecommunications and retail stores.) See bill payments interface for further details.
- Ability to perform current, future and recurring bill payments.
- Rename demand accounts, term deposits and loans to suit the purpose the member is using the funds for.
- Open new demand accounts (including transfer of funds to the account).
- Open new term deposits (including transfer of funds to the term deposits).
- Open RRSP products within an existing contract (including funding the RRSP).
- Create and cancel stop payments.
- Create and cancel automatic transfers (standing orders).
- Change personal access code (PAC).
- Temenos Transact to provide the inter-member funds transfer capability: Central1 will provide the banking relationship number and product type, category and fund within the request and Temenos Transact will process the inter-member transaction to the 1st product type, category and fund match on the “transfer to” banking relationship.
- Temenos Transact to support the inter-currency transfers for intra and inter member transfers.
- Temenos Transact to provide the capability to direct e-transfer debits and credits to different internal accounts.
- Requirements for statement masking.
- Central1 populates specific (pre-defined) values in BIT 103 (account identification 2) to identify transactions as CAD or USD wire transfer as opposed to a regular inter member transfer. The pre-defined values used in BIT103 will represent Temenos Transact internal accounts. Temenos Transact must be able to identify the pre-defined values in BIT 103 and appropriately map the transaction to specific funds transfer transaction codes.
- The general Central1 login process is: Standard authentication request with the disclaimer has been read flag in BM48 set to N is sent to banking system. For a business login, the banking system replies with membership = 9999 and BM44 = “7004” or “7005” (BM44 is set this way because banking system checks “MDSB Disclaimer has been read Flag” and determines that this member has not read the MDSB disclaimer). As there will only be one disclaimer acceptance field for business members in Temenos Transact, BM44 should only contain “7005”.
- Ability to perform single or mass activation of dormancy accounts.
Below are the list of other functionality supported:

On subsequent logins, only Bit Map 18 is required to be returned unless there has been a change to the MDSB disclaimer for any reason, in which case the READ and ACCEPT disclaimer process can be triggered by returning “7005” in BM44 as per above.

Financial institution requires an ability to exclude PAN or PAC authentication in Temenos Transact so that it can be validated by 3rd party.

Financial constitution needs an ability to restrict customer and its related accounts to be displayed from online banking MDI based on card.

EUF is an enhanced feature supported by C1 to support below functionalities:
- Auto deposit: Using this features, the money is auto deposited to bank account without manual intervention when an e-transfer is received.
- Request money: Customer can request money from their e-transfer recipient list.

Financial institutions also have the ability to list all the interest rates applicable for an escalating term deposits. These rates are viewed in MDI regardless of the year of the contract. Listing of Interest rates is in chronological order from oldest to newest.

Financial institution requires an ability to display the last month interest charged on lines of credit via online banking.

MDSB is an extended version of MDI for the business customer which requires delegates, consolidated and signer’s functionality.

All the cards of the business will be assigned to owner (the actual business) and FI’s will not maintain any internal information for the person the business has given the card to (a card holder) like the actual customer (member of business) who will use the card. Business can assign card to any person (a card holder).
Any card holder logs in with business card. Temenos Transact will send the UMID of the business for the signer request and the card is also assigned to business, since UMID matches, it is the authorization.

The signer functionality works based on the UMID of the card holder – login message and the signer list UMID of signer applicable for each account. If the UMID matches transaction is approved, else the transaction is placed in queue for approval from signer.

In case of MDSB, once the login is successful, C1 send a request for the list of signer who should approve the transaction for each product (account), Temenos Transact reply back with all signer associated to account.
In case signer is not defined, Temenos Transact will reply back with same no of signer as 1 and UMID as same UMID of card holder, such that the financial transaction does not require additional approval.
Validation for signer is done based on UMID > UMID is an identification of the person who can approve the transaction.

Using MDSB, the business owner can add delegate to MDSB (delegate is assigning a person an access to MDSB, like financial advisor etc).
Delegate can have either read access only or initiate and read access.
Delegate with read access can only view the account and balances and cannot perform any financial transaction.
Delegate with initiate and read access, can view and initiate financial transaction (financial transaction will not be complete, the actual owner have to login with card, to approve the transaction, so that the transaction hits the system).
Owner can decide which cards can be accessed by delegate in case of consolidate management is opted.

Consolidate Management is an extended functionality in MDSB, where in the business customer can link up to 3 cards to same login.
Business A, can link personal card, another business card to same business A login. This feature provide business to view the complete details in a single screen and initiate transaction between cards.
Financial transaction between business card and personal card does not require approval, whereas the transaction between 2 different business card require approval from the debit side card holder.

Ability to determine whether initial product to be considered for a subsequent occurrence of change product for an account.
Financial institutions has an ability to decide whether original product will be used or the current product to be used when change product happens for an account.
In this topic