Common use of MESSAGE Clause in Contracts

MESSAGE. processing 4.1 Every SWIFT CBT shall provide such facility for the creation, transmission, confirmation and cancellation of messages so as to enable participants to carry out instructions to execute or cancel any Transaction. 4.2 Every participant shall submit messages according to the SWIFT standards and MEPS+ specific conventions set out in the SWIFT User Handbooks and MEPS+ User Manuals respectively. 4.3 Instructions for Transactions pending settlement or execution, including forward- dated Transactions before their value date (but excluding SGSMB transactions), may be cancelled by the participant which initiated the Transaction. 4.4 For any SGSMB transaction that is not matched, the participant that sent the instruction may initiate its cancellation. For any SGSMB transaction that is matched, both participants that are parties to the transaction are required to initiate and confirm the cancellation. 4.5 A cancellation request shall be unsuccessful if the Transaction is settled before the host system receives the request for cancellation. 4.6 Notwithstanding any provision in these Rules, participants shall not be able to cancel, through their SWIFT CBT, instructions for IFT or SGSMB transactions that are initiated by the Service Provider or by MAS. 4.7 Participants shall be responsible for putting in place adequate controls to prevent the unauthorised use of their SWIFT CBT and the unauthorised transmission of messages via their SWIFT CBT, and shall conduct regular checks to ensure that the integrity of their SWIFT CBT and message transmissions via their SWIFT CBT is maintained.

MESSAGE. processing 4.1 Every SWIFT CBT will shall provide such facility for the creation, transmission, confirmation and cancellation of messages so as to enable participants to carry out instructions to execute or cancel any TransactionIFT or SGSMB transactions, or such other transactions as the Service Provider may approve by notice in writing, under MEPS+. 4.2 Every participant shall submit messages according to the SWIFT formats standards and MEPS+ specific conventions set out in the SWIFT User Handbooks and MEPS+ User functional specificationsUser Manuals respectively. 4.3 Instructions for Transactions transactions pending settlement or execution, including forward- dated Transactions transactions before their value date (but excluding SGSMB transactions), may be cancelled by the participant which initiated the Transactiontransaction. 4.4 For any SGSMB transaction that is not matched, the participant that sent the instruction may initiate its cancellation. For any SGSMB transaction that is matched, both participants that are parties to the transaction are required to initiate and confirm the cancellation. 4.5 A cancellation request shall will be unsuccessful if the Transaction transaction is settled before the host system receives the request for cancellation. 4.6 Notwithstanding any provision in these Rules, participants shall not be able to cancel, through their SWIFT CBT, instructions for IFT or SGSMB transactions that are initiated by the Service Provider or by MAS. 4.7 Participants shall be responsible for putting in place adequate controls to prevent the unauthorised use of their SWIFT CBT and the unauthorised transmission of messages via their SWIFT CBT, and shall conduct regular checks to ensure that the integrity of their SWIFT CBT and message transmissions via their SWIFT CBT is maintained.

MESSAGE. processing 4.1 Every SWIFT CBT shall provide such facility for the creation, transmission, confirmation and cancellation of messages so as to enable participants to carry out instructions to execute or cancel any TransactionIFT or SGSMB transactions, or such other transactions as the Service Provider may approve by notice in writing, under MEPS+. 4.2 Every participant shall submit messages according to the SWIFT standards and MEPS+ specific conventions set out in the SWIFT User Handbooks and MEPS+ User Manuals respectively. 4.3 Instructions for Transactions transactions pending settlement or execution, including forward- dated Transactions transactions before their value date (but excluding SGSMB transactions), may be cancelled by the participant which initiated the Transactiontransaction. 4.4 For any SGSMB transaction that is not matched, the participant that sent the instruction may initiate its cancellation. For any SGSMB transaction that is matched, both participants that are parties to the transaction are required to initiate and confirm the cancellation. 4.5 A cancellation request shall will be unsuccessful if the Transaction transaction is settled before the host system receives the request for cancellation. 4.6 Notwithstanding any provision in these Rules, participants shall not be able to cancel, through their SWIFT CBT, instructions for IFT or SGSMB transactions that are initiated by the Service Provider or by MAS. 4.7 Participants shall be responsible for putting in place adequate controls to prevent the unauthorised use of their SWIFT CBT and the unauthorised transmission of messages via their SWIFT CBT, and shall conduct regular checks to ensure that the integrity of their SWIFT CBT and message transmissions via their SWIFT CBT is maintained.

MESSAGE. processing 4.1 Every SWIFT CBT shall provide such facility for the creation, transmission, confirmation and cancellation of messages so as to enable participants to carry out instructions to execute or cancel any IFT or SGSMB transactions, or such other transactions as the Service Provider may approve by notice in writing, under MEPS+any Transaction. 4.2 Every participant shall submit messages according to the SWIFT standards and MEPS+ specific conventions set out in the SWIFT User Handbooks and MEPS+ User Manuals respectively. 4.3 Instructions for transactions Transactions pending settlement or execution, including forward- forward-dated transactions Transactions before their value date (but excluding SGSMB transactions), may be cancelled by the participant which initiated the TransactiontransactionTransaction. 4.4 For any SGSMB transaction that is not matched, the participant that sent the instruction may initiate its cancellation. For any SGSMB transaction that is matched, both participants that are parties to the transaction are required to initiate and confirm the cancellation. 4.5 A cancellation request will shall be unsuccessful if the transaction Transaction is settled before the host system receives the request for cancellation. 4.6 Notwithstanding any provision in these Rules, participants shall not be able to cancel, through their SWIFT CBT, instructions for IFT or SGSMB transactions that are initiated by the Service Provider or by MAS. 4.7 Participants shall be responsible for putting in place adequate controls to prevent the unauthorised use of their SWIFT CBT and the unauthorised transmission of messages via their SWIFT CBT, and shall conduct regular checks to ensure that the integrity of their SWIFT CBT and message transmissions via their SWIFT CBT is maintained.