Securing Cards and Account Data Sample Clauses

Securing Cards and Account Data. You must secure Cards and Card Account Data in your possession or control, and you must ensure that your Stripe Issuing Accountholders secure Cards and Card Account Data in their possession or control. When stored or processed digitally, you must use appropriate organisational and technical measures to secure the Cards and Card Account Data in your possession or control, including through industry-standard encryption. You must monitor, and you must ensure that your Stripe Issuing Accountholders monitor, for suspicious, fraudulent and unauthorised Card Transactions on each Stripe Issuing Accountholder’s Stripe Issuing Account and each Card.
Sample 1Sample 2Sample 3See All (29)
AutoNDA by SimpleDocs
Securing Cards and Account Data. You and your Card Authorised Users are responsible for securing Cards and Card Account Data. When stored or processed digitally, you must use appropriate organisational and technical measures to secure Cards and Card Account Data in your and your Card Authorised Users’ possession or control, including through the use of industry-standard encryption and anti-fraud measures. You must monitor for any suspicious or unauthorised activities and fraud on your Stripe Issuing Account and each Card.
Sample 1Sample 2Sample 3See All (28)
Securing Cards and Account Data. In addition to the data security obligations outlined in Section 10, the applicable Issuing Bank Terms describe your data security obligations related to Cards and Account Data.
Sample 1

Related to Securing Cards and Account Data

  • Records and Accounts The Trustee shall maintain accurate and detailed records and accounts of all transactions of the Trust, which shall be available at all reasonable times for inspection by any legally entitled person or entity to the extent required by applicable law, or any other person determined by the Committee.

  • Security Violations and Accounts Updates Grantee will adhere to the Confidentiality Article requirements and HHS Data Usage Agreement of this contract and immediately contact System Agency if a security violation is detected, or if Grantee has any reason to suspect that the security or integrity of the CMBHS data has been or may be compromised in any way.

  • Funds and Accounts Section 7.1. Authorization to Create Funds and Accounts 20 Section 7.2. Investment of Funds 20 Section 7.3. Establishment of Funds 21 Section 7.4. Funding Loan Payment Fund 21 Section 7.5. Expense Fund 22 Section 7.6. Closing Costs 22 Section 7.7. Project Fund 22 Section 7.8. Rebate Fund 24

  • Accessing the Website and Account Security We reserve the right to withdraw or amend this Website and any service or material we provide on the Website in our sole discretion without notice. We will not be liable if for any reason all or any part of the Website is unavailable at any time or for any period. From time to time, we may restrict access to some parts of the Website, or the entire Website, to users, including registered users. To access the Website or some of the resources it offers, you may be asked to provide certain registration details or other information. It is a condition of your use of the Website and any resources downloaded from the Website that all the information you provide on the Website is correct, current, and complete. You agree that all information you provide to register with this Website or otherwise, including but not limited to through the use of any interactive features on the Website, is governed by our Privacy Policy, and you consent to all actions we take with respect to your information consistent with our Privacy Policy. If you choose, or are provided with, a user name, password or any other piece of information as part of our security procedures, you must treat such information as confidential, and you must not disclose it to any other person or entity. You also acknowledge that your account is personal to you and agree not to provide any other person with access to this Website or portions of it using your user name, password or other security information. You agree to notify us immediately of any unauthorized access to or use of your user name or password or any other breach of security. You also agree to ensure that you exit from your account at the end of each session. You should use particular caution when accessing your account from a public or shared computer so that others are not able to view or record your password or other personal information. We have the right to disable any user name, password or other identifier, whether chosen by you or provided by us, at any time in our sole discretion for any or no reason, including if, in our opinion, you have violated any provision of these Terms of Use.

  • Books and Accounts (a) The General Partner shall cause the Partnership to keep and maintain at its principal executive office full and complete books and records which shall include each of the following:

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit B.

  • Additional Requirements from Authorized Users An Authorized User may have distinct requirements that must be met by all individuals employed by or working for the Authorized User. The Contractor’s Staff Members will be expected to comply with these requirements as a condition of the placement.

  • Notice and Account Details Party A: To be advised. Party B: To be advised. 3.

  • Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, e-Tel must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Security and Access The Executive agrees and covenants (a) to comply with all Company security policies and procedures as in force from time to time including without limitation those regarding computer equipment, telephone systems, voicemail systems, facilities access, monitoring, key cards, access codes, Company intranet, internet, social media and instant messaging systems, computer systems, e-mail systems, computer networks, document storage systems, software, data security, encryption, firewalls, passwords and any and all other Company facilities, IT resources and communication technologies (“Facilities Information Technology and Access Resources”); (b) not to access or use any Facilities and Information Technology Resources except as authorized by the Company; and (iii) not to access or use any Facilities and Information Technology Resources in any manner after the termination of the Executive’s employment by the Company, whether termination is voluntary or involuntary. The Executive agrees to notify the Company promptly in the event he learns of any violation of the foregoing by others, or of any other misappropriation or unauthorized access, use, reproduction or reverse engineering of, or tampering with any Facilities and Information Technology Access Resources or other Company property or materials by others.

Time is Money Join Law Insider Premium to draft better contracts faster.