Common use of Access to the System Clause in Contracts

Access to the System. 10.1 Access to the System shall be made by using (a) the customer ID, (b) user IDs and passwords and (c) one time passwords, or (a), (b) and (d) authentication method set forth by the Bank (herein, each of these combinations of (a), (b) and (c), and (a), (b) and (d) shall be referred to as the “Access Code”). In case where the Bank is unable to confirm the identity of the Access Code, the Bank may reject access to the System. 10.2 In case where the Bank confirms the identity of the Access Code, the Bank may regard such access to the System as being made by a duly authorized person and may effect the instructions given thereby. As long as the identity of the Access Code is confirmed, the Bank shall in no case be liable, even if instructions and access to the System are not authorized. 10.3 The Customer shall at its responsibility keep the Access Code, the tokens for one time passwords and authentication method set forth by the Bank (the “OTP Tokens, etc.”) under its control. 10.4 Upon termination of this Agreement, the Customer shall, at the request of the Bank and at its responsibility, destroy the OTP Tokens, etc. or take any other steps necessary to comply with the provisions in Clause 18; provided, however, that the Customer shall promptly return to the Bank the OTP Tokens, etc. if so requested by the Bank. The Bank shall not be held liable for any damages which the Customer may suffer as a result of failure or delay in taking such steps. 10.5 If any OTP Token, etc. is stolen, lost or improperly used or fails to function properly or if the Access Code is divulged or otherwise disclosed to a third party, the Customer shall immediately notify the Bank thereof.

Access to the System. 10.1 Access to the System shall be made by using (a) the combination of customer ID, (b) user IDs and IDs, passwords and (c) one time passwords, or password (a), (b) and (d) authentication method set forth by the Bank (herein, each of these combinations of (a), (b) and (c), and (a), (b) and (d) shall be collectively referred to as the “Access Code”). In case where the Bank is unable to confirm the identity of the Access Code, the Bank may reject access to the System. 10.2 In case where the Bank confirms the identity of the Access Code, the Bank may regard such access to the System as being made by a duly authorized person and may effect the instructions given thereby. As long as the identity of the Access Code is confirmed, the Bank shall in no case be liable, even if instructions and access to the System are not authorized. 10.3 The Customer shall at on its responsibility keep under control the Access Code, Code and the tokens for one time passwords and authentication method set forth by the Bank (the “OTP Tokens, etc.”) under its control). 10.4 Upon termination of this the Agreement, the Customer shall, shall at the request of the Bank and at on its responsibility, destroy the OTP Tokens, etc. Tokens or take any other steps necessary to comply with the provisions in Clause 1819; provided, however, provided that the Customer shall promptly return to the Bank the OTP Tokens, etc. if so requested by the Bank. The Bank shall not be held liable for to any damages which the Customer may suffer as a result of failure or delay in taking such steps. 10.5 If any OTP Token, etc. Token is stolen, lost or improperly used or fails to function properly or if the Access Code is divulged or otherwise disclosed to a third party, the Customer shall immediately notify the Bank thereof.