Processing Agreement

This Payment Processing Agreement for Sub-merchants (“Agreement”) is issued in connection with the Payload User Agreement (“User Agreement”), and sets forth the terms and conditions that govern the payment processing services to be provided by Payload, LLC dba (“Payload”) to its registered sub-merchants (“Sub-merchant(s)”). Such payment processing services are provided by JPMorgan Chase & Co (“Processor” and as such bank may change from time to time, the “Member Bank”) pursuant to a Payment Facilitator Merchant Agreement (“Processor Agreement”). Payload is required to enter into this Agreement with its customers Sub-merchants for purposes of this Agreement and the Processing Agreement. This Agreement constitutes “Additional Terms” as defined in the User Agreement. Sub-merchant has registered to receive the Payload services more fully described at (the “Website”), in accordance with the User Agreement posted to the Website from time to time. Sub-merchant has submitted an Application for the Services described herein, and by its acceptance of the Application, Payload agrees to provide Sub-merchant with certain payment processing services (“Services”) in accordance with the terms of this Agreement to facilitate Sub-merchant’s acceptance of credit and debit card payments for goods and services provided to Cardholders. In consideration of Sub-merchant’s receipt of credit or debit card funded payments, and participation in programs affiliated with MasterCard International Inc. (“MasterCard”), VISA U.S.A. Inc (“VISA”), Discover Financial Services, LLC (“Discover”), and Other Networks (defined below) (collectively, “Associations”), Sub-merchant is required to comply with the Operating Regulations (defined below) as they pertain to applicable credit and debit card payments. Payload and Sub-merchant agree as follows:

Terms and Conditions

  1. Definitions

    Unless otherwise defined above, all capitalized terms used in this Agreement shall have the meanings given to them herein or in Appendix A attached to this Agreement.

  2. The Services.

    Payload is a registered PSP and Payment Facilitator as provided for in the Operating Regulations. Pursuant to the Processing Agreement, Payload has arranged for Processor to acquire, process and settle payment for transactions initiated by Sub-merchant’s Payors, by means of Instruction Based Funding. Such acquiring, processing, and settlement shall be made in accordance with the Operating Regulations using the channels set forth in the Account Application, which include: credit/debit card and EFT (electronic funds transfer) payments through the Website, (collectively “Payments”). Subject to processing delays and risk holds, Payload has made arrangements as a Payment Facilitator to cause Payments to be made to Sub-merchant. Processor will periodically transfer Payments to Sub-merchant’s Account based upon instructions provided by Payload via Instruction Based Funding, as more fully described in the User Agreement.

  3. Authorization.

    Sub-merchant hereby authorizes Payload to facilitate the debiting and crediting of the bank account described in its Application (“Bank Account”), for purposes of depositing Payments to Sub-merchant’s Bank Account, debiting from Sub-merchant’s Bank Account any chargebacks, refunds, or reversals, and debiting any fees or charges owed to Payload. Sub-merchant agrees to keep this bank information up-to-date with Payload at all times. Failure to do so may result in Payments being misdirected, withheld, or returned to its Payors. Payload shall in no event be liable for any damages directly or indirectly resulting from incorrect bank information.

  4. Sub-merchant Responsibilities

    1. Sub-merchant agrees to comply, and to cause third parties acting as Sub-merchant’s agent (“Agents”) to comply, with the Operating Regulations, the Payment Card Industry Data Security Standards (“PCI-DSS”), the VISA Cardholder Information Security Program, the MasterCard Site Data Protection Program, and any other program or requirement that may be published and/or mandated by the Associations or payment networks. Sub-merchant may review the VISA, MasterCard, American Express, and Discover websites for a copy of the Visa, MasterCard and Discover regulations. The websites are: and and Sub-merchant will comply with the Card acceptance and website requirements set forth in the Operating Regulations. Without limiting the foregoing, Sub-merchant agrees that it will fully comply with any and all anti-money laundering laws and regulations, including but not limited to the Bank Secrecy Act, the US Treasury’s Office of foreign Assets Control (OFAC) and the Federal Trade Commission. For purposes of this section, Agents include, but are not limited to, Sub-merchant’s software providers and/or equipment providers.

    2. Sub-merchant also agrees to a direct processing agreement with Processor, in the form provided by Processor, as a supplement to this Agreement and will provide Payload with a copy of such agreement upon request.

    3. Sub-merchant will permit Payload to perform risk monitoring functions as required by the Operating Regulations and requirements of the Processor or Member Bank.

    4. Sub-merchant will notify Payload immediately of any Payor disputes or other matters that require escalation to Processor and immediately forward any notices received by Sub-merchant concerning a disputed payment transaction.

    5. Sub-merchant will assure that only sales transactions produced as the direct result of bona fide sales to Payors for such identified products and/or services are completed and delivered to Payload for processing.

    6. Sub-merchant will not present sales transactions for any purposes related to any illegal or prohibited activity, including but not limited to money-laundering or financing of terrorist activities.

    7. Third Parties. Payload and Sub-merchant may use one or more third party service providers (“TPSP’s”) in connection with the Services and/or the processing of some or all of its Card transactions. In no event shall Sub-merchant use a TPSP unless such TPSP is compliant with PCI and/or the Payment Application Data Security Standard (“PA-DSS”), depending on the type of TPSP, as required by the Operating Rules. Sub-merchant acknowledges and agrees that Sub-merchant shall cause its TPSP to complete any steps or certifications required by any Association (e.g., registrations, PA-DSS, PCI, audits, etc). Sub-merchant shall cause its TPSP to cooperate with Payload in completing any such steps or certifications (if applicable), and in performing any necessary due diligence on such TPSP. Sub-merchant shall be solely responsible for any and all applicable fees, costs, expenses and liabilities associated with such steps, registrations and certifications. Sub-merchant shall bear all risk and responsibility for conducting Sub-merchant’s own due diligence regarding the fitness of any TPSP(s) for a particular purpose and for determining the extent of such TPSP’s compliance with the Operating Rules and applicable law. Sub-merchant expressly agrees that neither Processor, Member Bank, nor Payload shall in any event be liable to Sub-merchant or any third party for any actions or inactions of any TPSP used by Sub-merchant, even if Processor, Member Bank or Payload introduced or recommended such TPSP.

  5. Sub-merchant Prohibitions

    Sub-merchant acknowledges and agrees that the prohibited actions described below (“Prohibited Actions”) are actions which may mislead, disadvantage, defraud or damage any, or all of, the following entities: (a) Payor; (b) issuing bank(s); (c) settlement bank(s); (d) Associations; (e) Payload; (f) Processor; or (f) Member Bank. Sub-merchant agrees that it must take all available steps and precautions to prevent fraud, theft, or misappropriation of Payor data. Sub-merchant agrees that it will not take any of the following Prohibited Actions and it will not permit a third party under its control to take the actions described in Section 4.1 in any situation where it has knowledge of such actions. Sub-merchant is deemed to be responsible for and to control the conduct of its employees, contractors, customers, and representatives.

    1. Sale Transactions. Sub-merchant will not submit any sales transaction to Processor: (a) that adds any surcharge to the transaction, except to the extent authorized by the Operating Regulations and Applicable Law; (b) that adds any tax to the transaction, unless Applicable Law expressly allows for the customer to impose a tax (any tax amount, if allowed, must be included in the transaction amount and not collected separately); (c) that represents the refinancing or transfer of an existing Payor obligation that is deemed to be uncollectible or arises from the dishonor of a Payor’s personal check or from the acceptance of a Card at a terminal that dispenses scrip; (d) that Sub-merchant knows or should have known to be fraudulent or not authorized by the Payor, or that it knows or should have known to be authorized by a customer colluding with Sub-merchant for a fraudulent purpose; (e) until after the services are performed, and/or Sub-merchant has completed the transaction, unless Sub-merchant has obtained Payor consent for a recurring transaction; (f) where a valid authorization was required but not obtained; (g) where multiple authorizations for amounts less than the total sale amount have been obtained; (h) which results in a disbursement of cash or cash equivalent to a Payor; (i) that establishes a maximum dollar sale transaction amount, except to the extent authorized by the Operating Regulations.

    2. Refund Transactions. Sub-merchant will not submit any refund transaction to Processor: (a) that does not correlate to an original sales transaction from the Cardholder; (b) that exceeds the amount shown as the total on the original sale transaction; (c) more than three (3) business days following either: (i) a regulatory requirement granting a Payor’s right to a refund; or (ii) a non-disputed Payor request.

    3. Other Prohibited Activities. Sub-merchant will not: (a) use any Payor data or other transaction data for any purpose not authorized by this Agreement; (b) disclose any Payor data or other transaction data to any entity except for necessary disclosures to affected Payors, and through Processor to affected Association entities (c) provide to Processor or Payload any inaccurate, incomplete, or misleading information; (d) fail to provide Payload with timely notification of events that have caused or could cause material changes in the Sub-merchant’s ability to fulfill its obligations under this Agreement, including but not limited to (i) adverse changes in Sub-merchant’s financial health; (ii) adverse changes in Sub-merchant’s business conditions or environment; or (iii) actions by governmental or non-governmental agencies; (e) transfer or attempt to transfer its financial liability by asking or requiring Payors to waive their dispute rights; (f) submit transactions on behalf of another entity that the Associations would consider a sub-ISO, Payment Service Provider (PSP), Payload, or other third party payment provider; (g) submit transactions for entities that do not have their principal places of business in the United States.

  6. Rights to Dispute Charges; Reports; Invoices.

    Sub-merchant expressly agree that its failure to notify Payload that it has not received any settlement funds within three (3) business days from the date that settlement was due to occur, or fail to reject any report, notice, or invoice within thirty (30) business days from the date the report or invoice is made available to Sub-merchant, shall constitute Sub-merchant’s acceptance of the same. In the event Sub-merchant believes that Payload has failed in any way to provide the Services, Sub-merchant agrees to provide Payload with written notice, specifically detailing any alleged failure, within sixty (60) days of the date on which the alleged failure first occurred.

  7. Parties to the Agreement; Entire Agreement

    This Agreement constitutes the agreement required by the Processing Agreement between Payload, as an Affiliated Payfac under the Processing Agreement, and its sub-merchants. In addition, the Sub-merchant may be required under the Processing Agreement to enter into a direct processing agreement with Processor (“Direct Processing Agreement”) if it processes transactions in excess of a certain dollar amount as required by the Operating Regulations. Payload and Sub-merchant acknowledge and agree that Processor and Member Bank are hereby made parties to this Agreement for that purpose, and each shall have the right to enforce against Sub-merchant all terms and conditions of this Agreement, and any future amendments or addenda to which they are a party, that are set forth therein. This Agreement and the Direct Processing Agreement, if applicable, shall constitute the entire agreement between the parties concerning the subject matter hereof. This Agreement shall not be superseded or replaced by the Direct Processing Agreement. In the event of a conflict between the terms of this Agreement and the Direct Processing Agreement, the terms of the Direct Processing Agreement shall control.

  8. Investigations

    Sub-merchant will promptly notify Payload in the event Sub-merchant becomes aware of any unusual or suspicious activity regarding its customers and will cooperate with Processor, Payload, Member Bank and the Associations, as applicable, in connection with any investigation of its customers’ background or activity.

  9. Security Interest; Reserve Account; Right of Setoff

    1. Security Interest and Lien. Sub-merchant hereby grants a security interest and lien upon funds payable to or in the Bank Account or any substitute account now and in the future and all proceeds thereof to Payload to secure all fees, costs, and charges due in accordance with this Agreement (the “Amounts Due”). In the exercise of its rights with regard to the security interest and lien, Payload may only debit the Bank Account to the extent of the then existing amounts due and shall only do so if Payload becomes reasonably concerned about whether the Sub-merchant will otherwise fulfill its financial obligations. The security interest and lien granted herein shall survive the termination of this Agreement until all amounts due are determined and paid in full. Sub-merchant hereby authorizes Payload to prepare all documents or to take other actions reasonably necessary to perfect its security interest or lien in the Bank Account or any substitute account therefor.

    2. Establishment of Reserve Account. Payload may withhold funds by temporarily suspending or delaying payouts of proceeds to Sub-merchant and/or designate in a separate reserve account (“Reserve”) to secure the performance of Sub-merchant obligations under any agreement between Sub-merchant and Payload. We may require a Reserve for any reason related to Sub-merchant’s use of the Services. The Reserve will be in an amount as reasonably determined by Payload to cover potential losses to Payload. If Sub-merchant does not have sufficient funds in its Reserve, Payload may fund the Reserve from any funding source associated with the Services, including any funds (a) deposited by you Sub-merchant, (B) due to you Sub-merchant, or (c) available in y Sub-merchant’s Bank Account, or other payment instruction registered with Payload.

    3. Set-Off Rights. To the extent permitted by law, Payload may set off against the proceeds for any obligation Sub-merchant owes Payload under any agreement with Payload (e.g., disputes or refunds). If Sub-merchant owes Payload an amount that exceeds Sub-merchant’s cumulative incoming proceeds, Payload may debit the Bank Account. Sub-merchant's failure to fully pay amounts that it owes to Payload on demand will be a breach of these terms. Sub-merchant is liable for any of Payload’s costs associated with collection in addition to any amounts owed, including attorneys’ fees and expenses, collection agency fees, and any applicable interest.

    4. Auditing and Credit Investigation. Sub-merchant authorizes Payload or its respective agents to investigate the background and personal and business credit history of any of the principals and employees associated with Sub-merchant’s business from time to time, and to obtain a business report on Sub-merchant’s business from any company providing credit reporting service. Payload may terminate this Agreement if the information received in any investigation is unsatisfactory in Payload’ sole discretion. Payload may also audit from time to time Sub-merchant’s compliance with the terms of this Agreement. Sub-merchant shall provide all information requested by Payload necessary to complete the audit. Upon Payload’ request, Sub-merchant shall provide all of its books and records, including financial statements for Sub-merchant and personal financial statements for all guarantors. Sub-merchant authorizes Payload to make on-site visits to any and all of the Sub-merchant’s locations with regard to all information necessary or pertinent to the Services.

  10. Audits

    At any reasonable time upon reasonable notice to Sub-merchant, Sub-merchant shall allow auditors, including the auditors of Payload, any Association or any third party designated by Payload, Processor or the applicable Association, to review the files held and the procedures followed by Sub-merchant at any or all of Sub-merchant’s offices or places of business. Any such audit shall be at Sub-merchant’s expense. Sub-merchant will assist such auditors as may be necessary for them to complete their audit and will cooperate fully. In the event that a third-party audit is requested by an Association, Member Bank or regulatory agency, and/or required by the Operating Regulations or applicable law, Payload may, at its option, and at Sub-merchant’s sole expense, either retain a third party to perform the audit, or require that Sub-merchant directly retain a specific third-party auditor. If Payload requires that Sub-merchant directly retain the auditor, Sub-merchant shall arrange immediately for such audit to be performed and will provide Payload and the Associations with a copy of any final audit report.

  11. Representations and Warranties; Authorization.

    Sub-merchant hereby represents and warrants that the execution, delivery and performance of this Agreement has been duly authorized by all necessary appropriate authorizing actions of Sub-merchant; that the execution, delivery and performance of this Agreement will not contravene any applicable by-law, corporate charter, partnership or joint venture agreement, law, regulation, order or judgment involving Sub-merchant; that the execution, delivery and performance of the Agreement will not contravene any provision or constitute a default under any other agreement, license or contract which Sub-merchant is bound; that the Agreement is valid and enforceable in accordance with its terms against Sub-merchant as if each Sub-merchant had signed the Agreement; that the fees and charges in the Sub-merchant Agreement shall apply separately and independently to Payload and Sub-merchant; and that Sub-merchant will be bound by any amendments and modifications to the Agreement agreed to by Payload.

  12. Data Security and Privacy

    Sub-merchant represents to Payload that it does not have access to Card information (such as the Cardholder’s account number, expiration date, and CVV2) and will not request access to such Card information from Payload. In the event that Sub-merchant receives such Card or other personal information of its customers in connection with the processing services provided under this Agreement, Sub-merchant agrees that it will not use it for any fraudulent purpose or in violation of any Card Organization Rules, including but not limited to PCI DSS or Applicable Laws. If at any time Sub-merchant believes that customer personal information has been compromised, Sub-merchant must notify Payload promptly and assist in providing notification to the proper parties. Sub-merchant must ensure compliance by itself and any third party service provider utilized by Sub-merchant, with all security standards and guidelines that are applicable to Sub-merchant and published from time to time, including without limitation those published by Visa, MasterCard or any other Card Organization, and including, without limitation, the Visa U.S.A. Cardholder Information Security Program (“CISP”), the MasterCard Site Data Protection (“SDP”), and (where applicable), the PCI Security Standards Council, Visa, and MasterCard PA-DSS (“Payment Application Data Security Standards”) (collectively, the “Security Guidelines”). Payload will not be responsible for unauthorized use or access to customers’ personal information or financial data by Sub-merchant, Sub-merchant’s employees, or any other party associated with Sub-merchant. If any Card Organization requires an audit of Sub-merchant due to a data security compromise event or suspected event, Sub-merchant agrees to cooperate with such audit. Sub-merchant may not use any Card information other than for the sole purpose of completing the transaction authorized by the customer for which the information was provided to Sub-merchant, or as specifically allowed by the Operating Regulations or as required by law. Payload may use any and all information gathered in the performance of the Services or the operation of the Website in accordance with its Privacy Policy located at . In addition, Sub-merchant agrees that Payload may use such information for any lawful purpose including marketing and deriving statistics regarding its Website and the Services.

  13. Modification of this Agreement or the Services

    Payload may from time to time without prior notice amend or modify this Agreement or the Services and Website, including without limitation a change to the pricing, terms or products offered; provided, however, that Payload will not modify the Services in a manner that would, in its sole discretion, significantly adversely affect Sub-merchant’s use thereof, without providing at least ten days’ prior notice to Sub-merchant of any such modification. Such notice may be made by means of email or a posting on the Website. Sub-merchant’s continued use of the Services following notification of any change or amendment to this Agreement or the Services shall be evidence of its consent and agreement to the modification or amendment. Posting notice of any modification or amendment on the Website shall be deemed adequate notification.

  14. Fees

    1. Sub-merchant shall pay the fees as described in and in the amounts set forth in the Application. Customers of Sub-merchant may be required to pay fees in order to make online Payments, if provided for in the enrollment documentation for the Services as set forth on the Website. Sub-merchant is responsible for disclosing all customer-paid fees to customers. If a dispute arises related to non-disclosure of customer-paid fees, Sub-merchant shall be liable to Payload for the full transaction amount including fees or charges for facilitating the payment of amounts due to Sub-merchant, as Payload may determine in its sole discretion. Payload may grant or deny to customers the ability to use the Payload Services for any reason in its sole discretion . Payload reserves the right to modify and amend all fees payable for the Services upon ten days’ notice to Sub-merchant.

    2. Third Party Assessments. Notwithstanding any other provision of this Agreement, Sub-merchant shall be responsible for all amounts imposed or assessed to Sub-merchant, Payload Processor, or Member Bank in connection with this Agreement by third parties such as, but not limited to, Associations and third-party service Payloads (including telecommunication companies) to the extent that such amounts are not the direct result of the gross negligence or willful misconduct of Processor, Member Bank or Payload as applicable. Such amounts include, but are not limited to, fees, fines, assessments, penalties, loss allocations etc. Any changes or increases in such amounts shall automatically become effective upon notice to Sub-merchant. In the event that Processor assesses Payload with the cost of funds associated with a circumstance where Processor, for whatever reason, advances settlement or any amounts and/or delays the assessment of any fees, Sub-merchant shall be fully responsible for any portion of such assessment that is attributable to the Services for Sub-merchant.

    3. Late Fees. If Sub-merchant does not pay amounts owed to Payload when due, Payload may charge and Sub-merchant agrees to pay a late fee of 1.5% per month on the outstanding balance, or the highest amount allowed by law, whichever is less.

    4. Collection Charges. Should Payload take any action against Sub-merchant to collect sums due hereunder, Sub-merchant agrees to pay all costs associated with such collection efforts, including but not limited to reasonable attorney’s fees.

    5. Taxes, Information Filings and Backup Withholding. Sub-merchant agrees to pay all federal, state, and local sales, use, income, property and excise taxes, which may be assessed in connection with the Services and related products provided under this Agreement. Sub-merchant agrees and understands that Payload or its designee will provide information reporting to the Internal Revenue Services and applicable state treasurers for all reportable payment transactions of Sub-merchant as defined in IRC § 6050W. If necessary, Payload or its designee will conduct backup withholding on the revenue generated by the reportable payment transactions of the Sub-merchant.

  15. Term and Termination

    1. This Agreement shall be binding upon Sub-merchant’s execution hereof. The term of this Agreement shall begin, and the terms of the Agreement shall be deemed accepted and binding on the date Payload begins providing the Services to Sub-merchant, and shall continue until either party gives the other at least 30 days written notice of termination.

    2. Notwithstanding the foregoing, Payload may immediately cease providing Services or terminate this Agreement without notice if: (i) Sub-merchant fails to pay any amount to Payload or Processor when due, (ii) Payload has received a request from Processor, Member Bank, or the Associations to terminate this Agreement; (iii) Payload believes that the provision of a service to Sub-merchant may be a violation of the Operating Regulations or any Applicable Laws; (iv) Payload believes that Sub-merchant has violated or is likely to violate the Operating Regulations or Applicable Law; (v) Payload determines that Sub-merchant poses a financial or regulatory risk to Payload or an Association, (vi) the Processing Agreement is terminated for any reason; (vii) any Association deregisters Payload; (viii) Processor or Member Bank ceases to be a member of or to participate in programs affiliated with the Associations that permit them to offer the Services; (ix) Payload fails to have the required licenses or registrations, or is the subject of any regulatory enforcement action in connection with any Applicable Law.

  16. Limitation of Liability; Indemnification

    1. Sub-merchant agrees to notify in writing of any alleged breach by Payload or Processor of this Agreement, which notice will specifically detail such alleged breach, within thirty (30) days of the date on which the alleged breach first occurred. Failure to provide such notice shall be deemed an acceptance by Sub-merchant and a waiver of any and all rights to dispute such breach. Sub-merchant hereby authorizes Payload to assert any such claim against Processor on its behalf, and to take all steps deemed necessary or appropriate in connection with such claim.

    2. Sub-merchant is liable for all acts, omissions, Payor disputes, and other Payor customer service-related issues. Sub-merchant acknowledges that Processor may refuse to process transactions for it in Processor’s reasonable discretion, and Sub-merchant agrees that Sub-merchant, and not Payload, shall be responsible for resolving any issues, problems, or disputes with its customers.

    3. EXCEPT FOR THOSE EXPRESS WARRANTIES MADE IN THIS AGREEMENT, PAYLOAD DISCLAIMS ALL WARRANTIES, INCLUDING, WITHOUT LIMITATION, ANY EXPRESS OR IMPLIED WARRANTIES OF NON-INFRINGEMENT, SUB-MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SUB-MERCHANT HEREBY ACKNOWLEDGES THAT THERE ARE RISKS ASSOCIATED WITH THE ACCEPTANCE OF CARDS AND SUB-MERCHANT HEREBY ASSUMES ALL SUCH RISKS EXCEPT AS MAY BE EXPRESSLY SET FORTH HEREIN. Sub-merchant’s sole and exclusive remedy for any and all claims against Payload arising out of or in any way related to the transactions contemplated herein shall be termination of this Agreement. Neither Processor, Member Bank, nor Payload shall be deemed to be in default under this Agreement or liable for any delay or loss in the performance, failure to perform, or interruption of any Services resulting, directly or indirectly, from a Force Majeure Event. Upon such an occurrence, performance by Processor, Member Bank and Payload shall be excused until the cause for the delay has been removed and Processor, Member Bank, and Payload have had a reasonable time to again provide the Services. No cause of action, regardless of form, shall be brought by either party more than 1 year after the cause of action arose, other than one for the nonpayment of fees and amounts due Payload under this Agreement. Any restriction on Payload’s liability under this Agreement shall apply in the same manner to Processor and Member Bank.

    4. Sub-merchant acknowledges and agrees that: (i) Sub-merchant’s receipt of Payments are transactions between Sub-merchant and the relevant Payor who is a customer of Sub-merchant and not with Payload nor any of Payload’s affiliates; (ii) Payload is a Payment Facilitator for Sub-merchant and is not a party to any transaction; and (iii) funds processed by Processor or its service providers (including any bank service providers) in connection with the processing of Payments are not deposit obligations and are not insured for Sub-merchant’s benefit by any governmental agency.

    5. Indemnification. Sub-merchant shall indemnify, defend, and hold harmless Payload and its directors, officers, employees, affiliates and agents from and against all proceedings, claims, losses, damages, demands, liabilities and expenses whatsoever, including all reasonable legal and accounting fees and expenses and all reasonable collection costs, incurred by Payload its directors, officers, employees, affiliates and agents resulting from or arising out of the Services in this Agreement, Sub-merchant’s payment activities, the business of Sub-merchant or its customers, any sales transaction acquired by Processor or Member Bank, any information provided by Sub-Merchant on which Payload relied in determining to grant, extend or continue Services was inaccurate, misrepresented or fraudulent, use or alleged misuse of the ACH system and/or fines assessed against Payload, Member Bank, or any financial institution in connection therewith, any noncompliance with the Operating Rules (or any rules or regulations promulgated by or in conjunction with the Associations) by Sub-merchant or its agents (including any TPSP), any issue, problems, or disputes between Processor and any Sub-merchant, or Member Bank and Sub-merchant, any Data Incident, any infiltration, hack, breach, or violation of the processing system of Sub-merchants, TPSP, or any other third party processor or system, or by reason of any breach or nonperformance of any provision of this Agreement, on the part of Sub-merchant, or its employees, agents, TPSPs, or customers. The indemnification obligations hereunder shall survive the termination of the Agreement.

      “Data Incident” is defined as any alleged or actual compromise, unauthorized access, disclosure, theft, or unauthorized use of a Card or Cardholder information, regardless of cause, including without limitation, a breach of or intrusion into any system, or failure, malfunction, inadequacy, or error affecting any server, wherever located, or hardware or software of any system, through which Card information resides, passes through, and/or could have been compromised.

    6. Limitation of Liability. Payload shall not be liable for lost profits, lost business or any incidental, special, consequential or punitive damages whether arising out of circumstances known or foreseeable. In no event will Payload be liable for any damages or losses (i) that are wholly or partially caused by Sub-merchant, or its employees, agents, or TPSPs. Further, neither Payload nor Member Bank shall be liable to Sub-merchant or Sub-merchant's customers or any other person for any of the following: (i) any loss caused by a transaction downgrade resulting from defective or faulty software or equipment; (ii) any loss or liability resulting from the product or service of a third party; (iii) denial of credit to any person or Sub-merchant’s retention of any Card or any attempt to do so; or (iv) any delay by a third party in processing any credit or debit entry, nor for the failure of a third party to process, credit, or debit any such entry or for other acts of omission. In no event shall Payload’s liability exceed the fees paid to and retained by Payload during the one (1) month period immediately prior to the event giving rise to the claim of damages.

  17. NOTICE

    Except for notices provided by Payload to Sub-merchant on the Sub-merchant statement, all notices, requests, demands or other instruments, which may be or are required to be given by any party herein, shall be in writing and each shall be deemed to have been properly given (i) three business days after being sent by certified mail, return receipt requested or (ii) upon delivery by a nationally recognized overnight delivery service to the addresses listed herein for the respective parties. Notices shall be addressed as follows:

    If to Payload: 4455 Carver Woods Drive Suite 200 Cincinnati, OH 45242 Attn: President

    If to Sub-Merchant: The physical or email address provided in the application.

    Any Party may change the address to which subsequent notices are to be sent by notice to the other Parties given as set forth above in this Section.

  18. Miscellaneous

    Payload may amend this Agreement upon notice to Sub-merchant in accordance with Payload’s standard operating procedures. This Agreement is entered into, governed by, and construed pursuant to the laws of the State of Ohio without regard to conflicts of law provisions. Payload may assign this Agreement upon prior written consent to Sub-merchant; however, this Agreement may not be assigned by Sub-merchant without the prior written consent of Payload. This Agreement shall be binding upon and inure to the benefit of the parties hereto and their respective successors, transferees and assignees. This Agreement is for the benefit of, and may be enforced only by, Payload and Sub-merchant and is not for the benefit of, and may not be enforced by, any other party. If any provision of this Agreement is determined to be illegal or invalid, such illegality or invalidity of that provisions will not affect any of the remaining provisions and this Agreement will be construed as if such provision is not contained in the Agreement. “Member Bank” as used in this Agreement shall mean a member of VISA, MasterCard and/or Discover, as applicable, that provides sponsorship services in connection with this Agreement. As of the commencement of this Agreement, Member Bank shall be JP Morgan, a New York banking corporation, located in New York City, New York. The Member Bank may be changed, and its rights and obligations assigned to another party by Processor at any time without notice to Payload or Sub-merchant.



  1. Sub-merchant agrees that it will take all steps necessary to assist Payload in complying with its obligations under the Operating Regulations and Applicable Laws related to the settlement of sales transactions, including but not limited to filing of quarterly or other reports required under the Operating Regulations and the payment of assessments, chargebacks and fees in connection with transactions processed under this Agreement.

  2. Sub-merchant will establish and maintain its Bank Account with a financial institution to credit the payments and fees Sub-merchant charges its customers. Sub-merchant authorizes Processor and Member Bank to initiate and make transfers to and from the Bank Account to effect the transactions contemplated by this Agreement (“Payments”). Any deficit in the Bank Account owing shall be paid by Sub-merchant into the Bank Account or directly to Payload to cover any deficit. Sub-merchant agrees to reimburse Payload, on demand, for any losses incurred as a result of insufficient funds in the Bank Account. Sub-merchant and Payload will mutually agree upon the provision of reporting and exchange of data as may be required by Payload to monitor and manage the activity relative to the Bank Account including any transfers to and from the Bank Account.

  3. During the term of this Agreement and for no less than one year thereafter, Sub-merchant will maintain a positive balance in the Bank Account at all times sufficient to accommodate all funding required by this Agreement. If at any time a deficit balance exists in the Bank Account, Payload shall give Sub-merchant written notice of such deficit and Sub-merchant shall have two (2) business days to cure such deficit and Payload reserves the right to require that Sub-merchant maintain a minimum balance in the Bank Account in an amount to be reasonably determined by Payload. Any fees, interest expenses or other expenses with respect to the Bank Account will be the sole responsibility of Sub-merchant and will be paid directly by Sub-merchant. If Processor or Payload incurs any fees, interest expenses or other expenses with respect to funding any deficit in the Bank Account, such amount shall be reimbursed by Sub-merchant, on demand by Payload, at Processor’s standard Cost of Funds rate on Processor’s Payload Price Schedule. Alternatively, if Payload has required the establishment of a Reserve Account, Payload may offset such an amount against the Reserve Account in accordance with Section 8 of this Agreement.

  4. Processor has established a partitioned credit limit for eCheck activity. Processor may limit Sub-merchant’s eCheck activity under this Agreement if necessary to maintain such limit. Sub-merchant acknowledges and agrees that Payload may at any time determine to restrict the amount or type of transactions Payload or Processor is willing to accept based on standards established and administered by Processor in its sole discretion. Processor or Member Bank may reject any ACH entry (“Entry”) which does not comply with the requirements of this Agreement, the NACHA Operating Regulations, Applicable Law or Member Bank’s or Processor’s requirements and specifications. Sub-merchant has no right to cancel or amend any Entry after its receipt by Processor or Member Bank. Sub-merchant is responsible for payment for an Entry even if the Entry is erroneous or is a duplicate Entry and regardless of whether Sub-merchant was the source of the error or duplicate Entry. Sub-merchant agrees not to initiate any Entry or other transaction in violation of Applicable Law.

  5. The terms of this Attachment A do not modify Sub-merchant’s due diligence obligations, including, without limitation, Sub-merchant’s responsibility to satisfy all applicable anti-money laundering (AML) policies. Sub-merchant will ensure that each customer authorizes Processor to initiate credit and debit ACH entries to the customer’s Bank Account.

  6. Each time Sub-merchant transmits an Entry to Processor or Member Bank, Sub-merchant represents and warrants to Processor and Member Bank that:

    • The Originator has authorized Sub-merchant to transmit Entries to Processor and Member Bank on behalf of Sub-merchant, in a manner that complies with the NACHA Operating Regulations, for processing and transmittal by Processor and Member Bank through the ACH system, which authorization has not been terminated and is in full force and effect, and Sub-merchant has agreed to make payment for any credit Entries originated and for any debit Entries returned by the RDFI;

    • Sub-merchant agrees to be bound by the NACHA Operating Regulations and to not initiate transactions in violation of United States law, and agrees to assume the responsibilities and perform the obligations of an Originator under the NACHA Operating Regulations;

    • Each Receiver of an Entry has authorized, in a manner that complies with the requirements of the Operating Regulations, Sub-merchant, or an agent of Sub-merchant, to initiate the Entry, and no such authorization has been revoked;

    • Sub-merchant has no knowledge of the revocation of the Receiver’s authorization or the termination of the agreement between the RDFI and the Receiver concerning the Entry; and

    • The Entry accurately reflects the entry data furnished to Sub-merchant and does not violate any agreement between Originator and Sub-merchant.



As used in this Agreement, the following terms mean as follows:

“Application”means the application for the Services required by Payload and completed and delivered by Sub-merchant as a prerequisite for participating in the Services.

“Applicable Laws”shall mean all applicable state, federal, and local laws, rules and regulations, including without limitation, the Bank Secrecy Act, the implementing regulations issued by the U.S. Treasury’s Office of Foreign Assets Control (OFAC) and the Federal Trade Commission, as well as any and all other federal and state anti-money laundering laws and regulations.

“Bank Account”shall mean the Sub-merchant’s bank account identified in its Application or other documentation provided to Payload to set up the Services.

“Cardholder”shall mean any person authorized to use a Card or the accounts established in connection with a Card.

“Cards”shall mean MasterCard, VISA, Discover and Other Network cards, account numbers assigned to a Cardholder or other forms of payment accepted by Processor, for which pricing is set forth in the account opening documentation.

“Force Majeure Event”shall mean errors in data provided by Sub-merchant or others, labor disputes, fire, weather or other casualty, power outages, and funding delays, however caused, governmental orders or regulations, or any other cause, whether similar or dissimilar to the foregoing, beyond Processor’s, Member Bank’s, or Payload’s reasonable control.

“Instruction Based Funding”shall mean the process for funding Sub-merchant’s transactions, as more fully described in Attachment A.

“Sub-merchant Supplier”shall mean a third party other than Processor used by Sub-merchant or a Payload in connection with the Services received hereunder, including but not limited to, Sub-merchant’s software providers, equipment providers, and/or third-party processors.

“Operating Regulations”shall mean the by-laws, operating regulations and/or all other rules, guidelines, policies and procedures of VISA, MasterCard, Discover, and/or Other Networks, and all other applicable rules, regulations and requirements of Processor, Member Bank, Payload, banks, institutions, organizations, associations, or networks which govern or affect any services provided under this Agreement, and all state and federal laws, rules and regulations which govern or otherwise affect the activities of Payload, including, but not limited to, those of the National Automated Clearing House Association (“NACHA”) and the Federal Trade Commission (“FTC”), as any or all of the foregoing may be amended and in effect from time to time.

“Other Network”shall mean any funds transfer network, including without limitation the network operated by NACHA, or card association other than VISA, MasterCard, or Discover that is identified in the Price Schedule or any subsequent amendment to this Agreement and in which Payload participates pursuant to the Processing Agreement.

“Payments”shall mean payments initiated by Payors using a Card or by means of ACH transfer.

“Payment Facilitator”shall have the meaning given that term in the Operating Regulations.

“Payment Processing”shall mean the process for funding Sub-merchant’s customers’ sales transactions, as more fully described in Attachment A.

“Payor”shall mean any customer of Sub-merchant who authorizes a payment to Sub-merchant, or who authorizes Sub-merchant to initiate a payment to the credit of Sub-merchant’s account, and for purposes hereof, “Payor” shall include a Cardholder.

“PSP”shall mean Payment Service Provider, as defined in the Operating Regulations.

“Services”shall mean any and all services described in, and provided by Payload to Sub-merchant in support of Sub-merchant’s role as a Payload or PSP, as defined in the Operating Regulations.

0129628.0622551 4844-4693-4565v7