The Merchant shall Clause Examples for Any Agreement
The Merchant shall.Comply with the international payment systems� card processing rules: � Ensure that the transaction amount is clearly visible to the payer before making the payment; � Do not refuse the customer the service envisaged in this Agreement for buying goods/services unless the Merchant finds the transaction suspicious; � Ensure that the POS terminal payment receipt (slip) displays the Merchant’s business name, which must appear on the Client’s statement; � Ensure that the customer signs the receipt (slip) of a magnetic-stripe transaction; � If the a magnetic-stripe transaction amount exceeds 100 (one hundred) GEL, request additionally the customer’s ID card and put down the ID card number on the printed sales receipt (slip); � Keep the sales receipt (slip) signed by the customer for 180 (one hundred and eighty) days; � Consider a payment transaction authorized only if the sales slip shows “approved�, response code 000.
The Merchant shall.2.2.1.1 Observe Visa Electron/Visa, Mastercard/Maestro and China UnionPay card service rules at POS: x Have the customer sign the magnetic stripe transaction sales slip; x If the magnetic stripe transaction is above 100 GEL, request additionally the ĐƵƐƚŽIDŵcĞarƌd ͛Ɛ and put down the ID number on the sales slip; x Keep the signed sales slip for 180 (one hundred and eighty) days; x Consider the payment successfully completed only if the sales slip shows ͞ĐŽŶĨ͟,ŝ code 000. reƌspŵonĞseĚ
2.2.1.2 Service Visa Electron/Visa, Mastercard/Maestro and China UnionPay cards by observing strictly the rules under this Agreement;
2.2.1.3 Forward the batch to the Processing Centre according to the rules hereunder;
2.2.1.4 Register the Merchant as a TBC Bank client / open account(s) for the Merchant (unless the Merchant is already registered/ has accounts with TBC Bank;
2.2.1.5 ZĞƚƵƌŶ ƚŚĞ ƌĞƐƉĞĐƚŝǀĞ ĂŵŽƵŶƚ ƚŽ ƚŚĞ ĂŶŬ͛Ɛ ĂĐĐ within 5 (five) banking days therefrom;
2.2.1.6 Ensure that Terminals are operated only by the personnel duly instructed/trained by the Bank or by other entity/ies specified in the General Provisions. Request the Bank or the Processing Centre in writing to provide training/ give instructions to his/her/its new employees;
2.2.1.7 Not transfer/ make POS Terminals accessible to third parties;
2.2.1.8 Not transfer the POS Terminal to a different branch ĂŶĚͬŽƌ ŽƵƚůĞƚ ǁŝƚŚŽƵƚ ƚŚĞ written approval;
2.2.1.9 Not post a credit entry without a debit entry;
2.2.1.10 Not accept a card payment for a purpose other than the payment for goods or services sold (.e.g. for collecting a debt, etc.) ;
2.2.1.11 Not charge additional fees/ payments above the transaction amount;
2.2.1.12 Install POS Terminals and display the advertising materials only upon prior agreement with the Bank;
2.2.1.13 Keep the sales slips and batch receipts for 180 (one hundred and eighty) days and deliver them to the Bank within 5 (five) banking days from receiving the ĂŶŬ͛Ɛ; ƌĞƋƵĞƐƚ
2.2.1.14 Keep information related to card transactions confidential;
2.2.1.15 Not request or use the payment card number for a purpose other than payment for goods or services;
2.2.1.16 Inform the Bank regarding his/her/its engagement with a third party (whether a subsidiary or an affiliate) that will have access to payment card data. These persons shall comply with Visa Electron/Visa, Mastercard/Maestro and China UnionPay security standards, for the violation of which the Merchant will incur full responsibility;
2.2.1.1...
The Merchant shallsafekeep and retain all transactional records, data and documents in relation to the details of Goods and Services sold to the Customer on the Platform not less than 12 (twelve) months from the transaction date which include at least name, address and contact detail of the Customer, delivery status of Goods and Services, date of transaction, detail of refund made by the Customer, authorization result, payment result, transaction number, receipt or relevant vouchers, messages or correspondence in any form transacted a Customer on the Platform;
The Merchant shall.2.2.1.1 Comply with rules for accepting Visa Electron/Visa, Mastercard/Maestro and China UnionPay card payments via POS terminals: x Ensure that the transaction amount is clearly visible to the payer before making the paym; ent x Do not refuse the customer the service envisaged in this Agreement foyrinbgu goods/services unless the Merchant finds the transaction suspicious; x Ensure that the customer signs the receiptip(s)l of a magnetic-stripe transaction; x If the a magnetic-stripe transaction amount exceeds 100 (one hundred) GEL, request DGGLWLRQDOO\ WKH FXVWRPHU¶V ,' FDUG DQG SXW G receipt (slip); x Keep the sales receip(st lip) signed by the customer for 180 (one hundred and eighty) days; code 000.
The Merchant shall.7.1 Inform the Customer that he will receive a text message emanating from KCB Mobile Banking Service to confirm that funds have been debited from the Customer’s Account in payment of the applicable goods or services. The Merchant will be informed via a preferable banking channel of the credit into the Collection Account;
7.2 Inform KCB in writing within five
The Merchant shall.(a) provide the Relevant NETS Entity with a deposit in the amount of Singapore Dollars Two Hundred (S$200) (or such other amount notified to the Merchant by the Relevant NETS Entity) for the installation of the NETS Access Device, in the form of a crossed cheque made payable to the Relevant NETS Entity (or to such other entity within the NETS Group) or in such other manner as may be notified by the Relevant NETS Entity to the Merchant;
(b) display or affix such notice or legend in respect of the said ownership on each NETS Access Device as may be requested by the Relevant NETS Entity (or if so displayed or affixed by the Relevant NETS Entity, the Merchant shall not tamper with or remove, cover or conceal the same);
(c) not assert any Claim whatsoever in relation to the ownership of any NETS Access Device regardless of the manner or degree of attachment thereof to the Merchant's premises; and
(d) return at its own expense and unconditionally to the Relevant NETS Entity any NETS Access Device upon request by the Relevant NETS Entity without undue delay.
The Merchant shall.(i) purchase the number of Terminal(s) at the purchase price, as specified in the Service Agreement (the “Purchased Terminals�), from the Supplier; and/or
(ii) lease the number of Terminals at the monthly fee, as specified in the Service Agreement (the �Leased Terminals�), from the Supplier. For clarity, if the Service Agreement is not completed by inserting the relevant number of Terminals to be leased and/or purchased, then the Merchant will not be leasing and/or purchasing any Terminals pursuant to such uncompleted section(s).
The Merchant shall.6.2.1 be responsible for integrating its systems (including, without limitation the Merchant’s Sites) with the API in accordance with the standards set out in the User Guides;
6.2.2 only access the API using the API Credentials;
6.2.3 keep the API Credentials secure and not disclose it to any other person;
6.2.4 comply with any limits Rvvup puts on the number and frequency of API requests from time to time;
6.2.5 put in place and regularly review and test measures in relation to the Merchant's systems which:
(i) secure the API, the API Data, and the API Credential from infringement, misappropriation, theft, misuse or unauthorised access;
(ii) prevent the upload of malware into Rvvup's systems or other malicious attempts/attacks that may affect the security of Rvvup's systems;
6.2.6 not use the Services:
(i) for any unlawful purpose or criminal activity whatsoever, including fraud, or to promote any unlawful act;
(ii) in any way which may infringe the Intellectual Property Rights of Rvvup or any other party;
6.2.7 not interfere with or degrade the Services in any way (including uploading any material which contains a virus or other malicious code or attempting a Denial of Service attack or similar);
6.2.8 not distribute, licence, sell, rent, lease or otherwise deal in or encumber the API;
6.2.9 not modify, add to, enhance, copy, reverse engineer or decompile the API;
6.2.10 be responsible for resolving any issues with a Plugin it chooses to use;
The Merchant shall.1.3.1 Pay the Bank a relevant commission fee for relevant services extended in line with tariffs set by the Bank for the time being.
1.3.2 At the request of the Bank, provide it with any information and documents that provide proof for any relevant banking transaction;
1.3.3 Bear responsibility for accuracy of information provided in the application form and to inform the Bank in writing about any changes in the information, within five days after these changes take effect. If the Merchant fails to notify the Bank of these changes, it shall be held accountable for any consequence that might arise.
1.3.4 Before applying for each new account, submit to the Bank all documents that are legally required for opening a new account.
1.3.5 Return the funds to the Bank and pay a due fine, if the Merchant uses or/and spends funds that were mistakenly transferred to its account.
The Merchant shall.4.1.1 comply with the Guidance Documentation, Acceptable Use Policy and any other instructions, guidance, procedures and/or requirements given by Rvvup from time to time in accordance with any timescales specified by Rvvup;
4.1.2 only use the Services for its business purposes and as specifically permitted in the Agreement;
4.1.3 not make the Services available to any third party or use the Services on behalf of a third party;
4.1.4 be responsible for integrating its systems with the API in accordance with the standards set out in the Guidance Documentation;
4.1.5 only access the API using the API Credentials;
4.1.6 keep the API Credentials secure and not disclose it to any other person;
4.1.7 comply with any limits Rvvup puts on the number and frequency of API requests from time to time;
4.1.8 put in place and regularly review and test measures in relation to the Merchant's systems which:
(i) secure the API, the API Data, and the API Credential from infringement, misappropriation, theft, misuse or unauthorised access;
(ii) prevent the upload of malware into Rvvup's systems or other malicious attempts/attacks that may affect the security of Rvvup's systems;
4.1.9 not use the Services:
(i) for any unlawful purpose or criminal activity whatsoever, including fraud, or to promote any unlawful act;
(ii) in any way which may infringe the Intellectual Property Rights of Rvvup or any other party;
4.1.10 not interfere with or degrade the Services in any way (including uploading any material which contains a virus or other malicious code or attempting a Denial of Service attack or similar);
4.1.11 not distribute, licence, sell, rent, lease or otherwise deal in or encumber the API or the Services;
4.1.12 not modify, add to, enhance, copy, reverse engineer or decompile the API or the Services;
4.1.13 be responsible for resolving any issues with a Plugin it chooses to use;