Payment Cards Sample Clauses

Payment Cards. If, after being counseled by Provider on the option to enroll in direct deposit, Participants choose to receive a payment card, Contractor shall be responsible for distributing payment cards to each Participant. Contractor shall be liable for any loss, damage, theft, or misuse of such payment cards from the time Contractor receives their delivery to the time Contractor successfully distributes the same to the Participants. Distribution of such payment cards shall be deemed successful when the same are actually received, and signed for, by the Participants. Contractor shall maintain a log of payment cards that have been distributed to Participants, which must be produced to DYCD upon request.
Payment Cards. 5.1 Personnel shall follow the rules and regulations that apply at any time for accepting and handling credit/debit cards. The enterprise has a duty to and is responsible for ensuring that these rules and regulations are posted at all times in a place where they can easily be read by personnel who receive and process payment cards. 5.2 As long as the personnel follow the guidelines prepared in accordance with the above, it should be possible for them to accept payments by card, exempted from liability.
Payment Cards. The international Payment Cards regarding which the Merchant has entered into an Agreement with Nets and which are thus specified in the Agreement Form, e.g. Mastercard, Maestro, Visa, Visa Electron, VPAY, JCB and UnionPay.. The Card Organisations’ security standard, known as the Payment Card Industry Data Security Standard. Learn more at https:// xxx.xxxxxxxxxxxxxxxxxxxx.xxx. The personal code linked to the Payment Card.
Payment Cards. When accepting payment card payments, you must comply with all applicable Network Rules, including the Network Rules specified by the Visa Rules and Regulations Rules specified by Visa U.S.A., Inc. and Visa International ("Visa"), the Mastercard Rules specified by MasterCard International Incorporated ("Mastercard"), and the American Express Merchant Operating Guide specified by American Express. Collectively, Visa, Mastercard and American Express are referred to in this Agreement as the "Networks". The Network Rules state that you may only accept payments using payment cards for bona fide legal commercial transactions between you and your Customers for goods or services that are free of liens, claims, and encumbrances. You may only use payment network trademarks or service marks consistent with the Network Rules, and the Network Rules also limit your ability to discriminate by card type or charge surcharges for acceptance of payment cards. The Networks may amend the Network Rules at any time without notice to you, and Latipay reserves the right to change the Payment Processing Services at any time to comply with the Network Rules. We may share with the Networks (and the Payment Method Acquirer) information you provide to us that we use to identify the nature of your products or services, including the assignment of your business activities to a particular payment network merchant category code (MCC). Customers typically raise payment card network Disputes (also known as "chargebacks") when a merchant fails to provide the product or service to the Customer, or where the payment card account holder did not authorize the Charge. High Dispute rates (typically those exceeding 1%) may result in your inability to use the Payment Processing Services. Failure to timely and effectively manage Disputes with your Customers may ultimately result in your inability to accept payment cards for your business. When you accept payment card Transactions, Network Rules specifically prohibit you from (i) providing cash refunds for a Charge on a credit card, unless required by Laws, (ii) initiating a Refund more than five calendar days after issuing a credit to your Customer,
Payment Cards. JetBrains accepts major debit and credit cards (“Payment Cards”) for payment via third-party payment gateway providers, including Adyen and PayPal. Any and all Payment Card payments shall be deemed as payments made by the Customer regardless of the name of the card holder making the payment.
Payment Cards. Cvent shall establish and maintain safeguards against the destruction, loss or alteration of payment cards which is in the possession of Cvent and stored in a Cvent platform by implementing the applicable information security controls as set out in the then current version of the Payment Card Industry Data Security Standard (“PCI DSS”), or the immediately preceding version of PCI DSS to the extent still permitted by PCI authorities).
Payment Cards. 2.5.1. The Client can request, at any time, a Card (virtual or physical) for all or some of its Users. Edenred undertakes to answer said request within fifteen (15) Business Days, provided that this is materially possible. Xxxxxxx shall explain the reasons for the impossibility to access the Client’s request, as the case may be. 2.5.2. Each Card is personal to each User and can only be used by said User in accordance with the User Conditions. 2.5.3. The Card can only be used to pay for Mobility Services. 2.5.4. The funds are loaded on the Card by Xxxxxxx based on the balance of the User’s Mobility Budget and as periodically prepaid by the Client, it being understood that no funds shall be loaded on a Card without having first being transferred by the Client to Edenred. Once Xxxxxxx has loaded the funds on the Card, the responsibility for the funds remains exclusive with the Banking Partner. Edenred cannot be held liable for any loss of funds once it has loaded the funds on the card. 2.5.5. Any payment transaction made with the Card by a User will be deduced from the User’s Mobility Budget as available on the Account. 2.5.6. Users can use the Card up to the remaining balance in their respective Mobility Budget up to the maximum specified by the Client. The Client is solely responsible for specifying to each of its Users how and under which conditions the Card may be used. Xxxxxxx assumes no liability for misuse of the Card or for any payment transactions done beyond the scope agreed upon between the Client and its User. 2.5.7. The Client shall communicate to Edenred upon its request all the information related to it and/or its Users, when such information is necessary or useful to enable Edenred to deliver the Services and/or to comply with applicable law. 2.5.8. The Parties acknowledge and accept that the Cards are issued by a certified third party and that Skipr shall only act as an agent of said third party in relation with the Cards, it being understood that the Client shall nevertheless communicate directly with Xxxxxxx for issues in relation to the Cards.
Payment Cards. Users may be required to enter payment card details to access certain features or portions of the Services, to pay any Fees as set forth on the Website or in order for IK or a third party service provider to obtain access to certain information and data associated with such payment card. User represents and
Payment Cards. Available Balance – the amount of cash funds on the Card Account, which can be used for a Card Transaction equal to the sum of a credit limit/overdraft and the Client’s funds on the Card Account by subtracting the Card Transaction already made but not yet written off from the Card Account. Balance – the amount of cash funds on the Card Account without a credit limit or an overdraft and any amounts reserved for Card Transactions already made but not yet written off from the Card Account. Card Account – a Client’s account with the Bank for the custody and accounting cash funds to be used for Card Transactions. Card Code – a Card security code for Card Transactions in the Internet. For Visa Virtual, Visa Light, Visa Classic, Visa Business, Visa Gold and Visa Platinum it is a CVV2 code. For MasterCard Light, MasterCard Classic, MasterCard Business, MasterCard Gold and MasterCard Platinum it is a CVC2 code. Cardholder – a person indicated in the Order for the issue of a payment card whose name, surname and signature sample have been placed on the Card and to whom the Card has been handed over for use. Card – an international payment card issued by the Bank, which the Bank hands over to the Cardholder according to the Order. The Card is linked to the Client’s Card Account, including credit cards (Master Card or Visa) and debit cards (Maestro and Visa Electron) or other Card Password – a password specified in the Order for the issue of a payment card and used by the Bank for identification purposes of the Client or the Cardholder by phone. Card Transaction Limit – the maximum number and/or the total amount (as defined by the Bank) of Card Transactions Authorised by the Bank within a definite period of time (a day, a week or a month). The Parties may agree to set another Card Transaction Limit in the Order for the issue of the payment card, if it does not exceed the maximum Card Transaction Limit applied by Bank. Card Transaction – a payment with a Card for goods and services, cash withdrawals using the card at ATMs and banks, money transfers from the Card Account as per the Order, and Remuneration payments and other activities decreasing the Available Balance. Debit Balance – a Card Account balance, which equals to the amount of the Client’s liabilities towards the Bank at the end of a particular day or an account statement period. The Debit Balance is changed after each Card Transaction.
Payment Cards a. MARKETER shall accept as payment from retail customers CITGO-approved credit, debit and payment cards (collectively, “Payment Cards”) in accordance with the provisions of CITGO’s Payment Card Guide and Regulations, a copy of which has been provided to MARKETER. All Payment Cards are required to be processed through the CITGO Electronic Point of Sale (“EPOS”) Network. b. CITGO shall have the right, in its sole discretion, to amend or terminate the Payment Card Guide and Regulations and/or discontinue its program at any time. CITGO may reject or charge back any Payment Card invoices not conforming to the Payment Card Guide and Regulations. MARKETER further agrees that upon such rejection or charge back, the value of the Payment Card invoices which were rejected or charged back shall become immediately due and owing from MARKETER to CITGO and may be deducted from subsequent settlements of Payment Card transactions. c. MARKETER expressly agrees that CITGO shall have the right but not the obligation to apply the proceeds of Payment Card invoices or any other credits which may be owing to MARKETER toward the payment of any indebtedness owed by MARKETER to CITGO. MARKETER grants to CITGO a security interest in all Payment Card invoices and proceeds from such Payment Card invoices to secure the payment of Motor Fuel purchases from CITGO, and agrees to execute documents reasonably necessary to perfect such security interest. d. MARKETER further agrees to maintain in good working order all of the EPOS Systems located at the Locations. For the purposes of this Section, “good working order” includes having the EPOS Systems properly configured and operating on the most current Payment Card Industry Data Security Standard-compliant version of the application software and hardware. CITGO shall have the right to deactivate the EPOS System for any Location that fails to comply with this “good working order” requirement.