Common use of Payment Applications Clause in Contracts

Payment Applications. Merchant may be using special services, hardware or software provided by a third party (“Third Party Payment System”) to assist Merchant in processing transactions, including authorizations, batch settlement or accounting functions. In the event Merchant uses a Third Party Payment System including, but not limited to, a POS terminal, POS system, POS software, payment software, payment gateway, virtual terminal, cardholder activated terminal or automated fuel dispenser, Merchant is responsible for assuring third party system is PA-DSS certified and complies with the PABP (Payment Application Best Practices) as set forth by the Payment Card Industry Security Standards Council (PCI-SSC) and the Card Associations. Merchant must ensure that any software or system updates of Third Party Payment System(s) satisfies all security standards required under the Rules (including PABP, PA-DSS and PCI-DSS). All electronic commerce Merchants must provide Cardholders with a secure and encrypted transaction method, utilizing a valid Secure Sockets Layer (SSL) certificate or 3D Secure. Neither Bank nor NMS has any responsibility for any transaction until that point in time until such party, as applicable, receives data about the transaction. Merchant must notify Bank and NMS of its use of any Third Party Payment System that will have access to and/or stores Cardholder or Payment Card information.

Appears in 5 contracts

Samples: Merchant Processing Agreement Terms and Conditions, Merchant Processing Agreement Terms and Conditions, Merchant Processing Agreement Terms and Conditions

AutoNDA by SimpleDocs

Payment Applications. Merchant may be using special services, hardware or software provided by a third party (“Third Party Payment System”) to assist Merchant in processing transactions, including authorizations, batch settlement or accounting functions. In the event Merchant uses a Third Party Payment System including, but not limited to, a POS terminal, POS system, POS software, payment software, payment gateway, virtual terminal, cardholder activated terminal or automated fuel dispenser, Merchant is responsible for assuring third party system is PA-DSS certified and complies with the PABP (Payment Application Best Practices) as set forth by the Payment Card Industry Security Standards Council (PCI-SSC) and the Card Associations. Merchant must ensure that any software or system updates of Third Party Payment System(s) satisfies all security standards required under the Rules (including PABP, PA-DSS and PCI-DSS). All electronic commerce Merchants must provide Cardholders with a secure and encrypted transaction method, utilizing a valid Secure Sockets Layer (SSL) certificate or 3D Secure. Neither Bank nor NMS has any no responsibility for any transaction until that point in time until such party, as applicable, Bank receives data about the transaction. Merchant must notify Bank and NMS of its use of any Third Party Payment System that will have access to and/or stores Cardholder or Payment Card information.

Appears in 4 contracts

Samples: Merchant Processing Agreement Terms and Conditions, Merchant Processing Agreement, Merchant Processing Agreement

Payment Applications. Merchant may be using special services, hardware or software provided by a third party (“Third Party Payment System”) to assist Merchant in processing transactions, including authorizations, batch settlement or accounting functions. In the event Merchant uses a Third Party Payment System including, but not limited to, a POS terminal, POS system, POS software, payment software, payment gateway, virtual terminal, cardholder activated terminal or automated fuel dispenser, Merchant is responsible for assuring third party system is PA-DSS certified and complies with the PABP (Payment Application Best Practices) as set forth by the Payment Card Industry Security Standards Council (PCI-SSC) and the Card Associations. Merchant must ensure that any software or system updates of Third Party Payment System(s) satisfies all security standards required under the Rules (including PABP, PA-DSS and PCI-DSS). All electronic commerce Merchants must provide Cardholders with a secure and encrypted transaction method, utilizing a valid Secure Sockets Layer (SSL) certificate or 3D Secure. Neither Bank nor NMS Service Provider has any no responsibility for any transaction until that point in time until such party, as applicable, Service Provider receives data about the transaction. Merchant must notify Bank and NMS Service Provider of its use of any Third Party Payment System that will have access to and/or stores Cardholder or Payment Card information.

Appears in 3 contracts

Samples: Merchant Processing Agreement Terms and Conditions, Merchant Processing Agreement Terms and Conditions, Merchant Agreement

Payment Applications. Merchant may be using special services, hardware or software provided by a third party (“Third Party Payment System”) to assist Merchant in processing transactionsTransactions, including authorizationsAuthorizations, batch settlement settlement, or accounting functions. In the event Merchant uses a Third Party Payment System including, but not limited to, a POS terminal, POS system, POS software, payment software, payment gateway, virtual terminal, cardholder Cardholder activated terminal or automated fuel dispenser, Merchant is responsible for assuring third party system is PA-DSS certified and complies with the PABP (Payment Application Best Practices) as set forth by the Payment Card Industry Security Standards Council (PCI-SSC) and the Card Associations. Merchant must ensure that any software or system updates of Third Party Payment System(s) satisfies satisfy all security standards required under the Rules (including PABP, PA-DSS and PCI-PCI- DSS). All electronic commerce Merchants must provide Cardholders with a secure and encrypted transaction method, utilizing a valid Secure Sockets Layer (SSL) certificate or 3D Secure. Neither Bank nor NMS has any no responsibility for any transaction Transaction until that point in time until such party, as applicable, Bank receives data about the transactionTransaction. Merchant must notify Bank and NMS of its use of any Third Party Payment System that will have access to and/or or stores Cardholder or Payment Card information.

Appears in 3 contracts

Samples: Merchant Processing Agreement, Merchant Processing Agreement, Merchant Processing Agreement

Payment Applications. Merchant may be using special services, hardware or software provided by a third party (“Third Party Payment System”) to assist Merchant in processing transactionsTransactions, including authorizationsAuthorizations, batch settlement settlement, or accounting functions. In the event Merchant uses a Third Party Payment System including, but not limited to, a POS terminal, POS system, POS software, payment software, payment gateway, virtual terminal, cardholder Cardholder activated terminal or automated fuel dispenser, Merchant is responsible for assuring third party system is PA-DSS certified and complies with the PABP (Payment Application Best Practices) as set forth by the Payment Card Industry Security Standards Council (PCI-SSC) and the Card Associations. Merchant must ensure that any software or system updates of Third Party Payment System(s) satisfies satisfy all security standards required under the Rules (including PABP, PA-PA- DSS and PCI-DSS). All electronic commerce Merchants must provide Cardholders with a secure and encrypted transaction method, utilizing a valid Secure Sockets Layer (SSL) certificate or 3D Secure. Neither Company and Bank nor NMS has any have no responsibility for any transaction Transaction until that point in time until such party, as applicable, receives Company and Bank receive data about the transactionTransaction. Merchant must notify Company and Bank and NMS of its use of any Third Party Payment System that will have access to and/or or stores Cardholder or Payment Card information.

Appears in 2 contracts

Samples: Merchant Processing Agreement Terms and Conditions, Merchant Processing Agreement

AutoNDA by SimpleDocs

Payment Applications. Merchant may be using special services, hardware or software provided by a third party (“Third Party Payment System”) to assist Merchant in processing transactionsTransactions, including authorizationsAuthorizations, batch settlement settlement, or accounting functions. In the event Merchant uses a Third Party Payment System including, but not limited to, a POS terminal, POS system, POS software, payment software, payment gateway, virtual terminal, cardholder Cardholder activated terminal or automated fuel dispenser, Merchant is responsible for assuring third party system is PA-DSS certified and complies with the PABP (Payment Application Best Practices) as set forth by the Payment Card Industry Security Standards Council (PCI-SSC) and the Card Associations. Merchant must ensure that any software or system updates of Third Party Payment System(s) satisfies satisfy all security standards required under the Rules (including PABP, PA-DSS PADSS and PCI-DSS). All electronic commerce Merchants must provide Cardholders with a secure and encrypted transaction method, utilizing a valid Secure Sockets Layer (SSL) certificate or 3D Secure. Neither Company and Bank nor NMS has any have no responsibility for any transaction Transaction until that point in time until such party, as applicable, receives Company and Bank receive data about the transactionTransaction. Merchant must notify Company and Bank and NMS of its use of any Third Party Payment System that will have access to and/or or stores Cardholder or Payment Card information.

Appears in 1 contract

Samples: Merchant Processing Agreement

Payment Applications. Merchant may be using special services, hardware or software provided by a third party (“Third Party Payment System”) to assist Merchant in processing transactionsTransactions, including authorizationsAuthorizations, batch settlement settlement, or accounting functions. In the event Merchant uses a Third Party Payment System including, but not limited to, a POS terminal, POS system, POS software, payment software, payment gateway, virtual terminal, cardholder Cardholder activated terminal or automated fuel dispenser, Merchant is responsible for assuring third party system is PA-DSS certified and complies with the PABP (Payment Application Best Practices) as set forth by the Payment Card Industry Security Standards Council (PCI-SSC) and the Card Associations. Merchant must ensure that any software or system updates of Third Party Payment System(s) satisfies satisfy all security standards required under the Rules (including PABP, PA-DSS and PCI-DSS). All electronic commerce Merchants must provide Cardholders with a secure and encrypted transaction method, utilizing a valid Secure Sockets Layer (SSL) certificate or 3D Secure. Neither Company and Bank nor NMS has any have no responsibility for any transaction Transaction until that point in time until such party, as applicable, receives Company and Bank receive data about the transactionTransaction. Merchant must notify Company and Bank and NMS of its use of any Third Party Payment System that will have access to and/or or stores Cardholder or Payment Card information.

Appears in 1 contract

Samples: Merchant Processing Agreement

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!