BANCORP BANK (THE); PHOENIX PAYMENT SYSTEMS, INC. DBA ELECTRONIC PAYMENT EXCHANGE (EPX)

Home Browse Search

9.1. Documenting Transactions. Merchant or EPX on its behalf shall submit the following information to Bank in connection with Transaction processing: i. The DBA name of Merchant, name of Merchant and Merchant's address; ii. Merchant customer service telephone number; iii. Merchant Internet address; iv. Merchant Number assigned by Bank; v. The Card account number, validation date and/or expiration date of the Card, if one appears on the Card; vi. Name, address and telephone number of Cardholder; and vii. Such additional information as may be required by Bank, EPX and/or the Associations, from time to time. Merchant or EPX on its behalf shall not submit a Transaction to Bank (electronically or otherwise) until Merchant has performed its obligations to the Cardholder in connection with the Transaction or obtained Cardholder's consent for aPre-Authorized Recurring Order Transaction. Merchant must not initiate a Transaction to Bank that Merchant knows or should have known to be fraudulent or not authorized by the Cardholder. Merchant is responsible for its employees' actions. Merchant may transmit a Transaction which effects a prepayment of services or full prepayment of custom-ordered merchandise, manufacriired to a Cardholder's specifications, if Merchant advises Cardholder of the immediate billing at the time of the Transaction and within time limits established by the Associations. 9.2. Authorization for Transactions. Merchant or EPX on Merchant's behalf shall obtain Authorization of Transactions as follows: i. Electronically Transmitted Transaction. Merchant or EPX on its behalf shall submit each Transaction for Authorization to the EPX System. The EPX System shall respond with the Issuer's- authorize or decline to a Transaction transmitted for Authorization and shall capture and process for Merchant the information relating to the Transaction. ii. Card-Present Transactions. The following additional requirement applies to Card-Present Transactions: If a terminal or software application is inoperable at the time of an Authorization request, the Transaction may be manually authorized. In that case, the Transaction shall be entered as a Forced Sale, provided the approval number is also entered, and Merchant shall be subject to an additional IVR authorization fee as outlined in Schedule B. iii. Card-Not-Present Transactions. The following additional requirements apply to Card-Not-Present Transactions: 1. All Card-Not-Present Transactions are at Merchant's risk. As to each, Card-Not-Present Transactions Merchant warrants to Bank that the person whose name is submitted to Bank as Cardholder either made or authorized another to make the purchase. Upon breach of this warranty, Bank may charge back the Transaction to Merchant. If Bank charges back the Transaction to Merchant, Merchant shall pay Bank the amount of the Transaction, any Chazgeback fee in Schedule B, plus any Association fine or assessment. Bank may charge the Transaction to the Operating Account or Reserve Account without prior notice to Merchant; 2. All Card-Not-Present Transactions must be electronically authorized and, in addition to the information required in Paragraph 9.1 (Documenting Transactions), also shall indicate: an authorization code, if required; customer address and address verification; and in lieu of Cardholder's signature, a notation of (a) mail order, (b) telephone order, (c) e-commerce order, or (d) pre-authorized order, on the signature line; 3. If Merchant accepts aPre-Authorized Recurring Order Transaction, the Cardholder shall execute and deliver to Merchant a written request for this pre-authorization. This written request shall be maintained by Merchant and made available upon request to Bank. All annual billings must be reafFirmed at least once a year. Merchant shall not deliver goods or perform services covered by aPre-Authorized Recurring Order Transaction after receiving Initials Page 11 of 19