General Terms and Conditions
for Payment Facilitator Services

v1.9 as of 20. Sept. 2024

Object of the Contract and Conditions für Payment Acceptance
- Object of the Contract
- Definition

General Provisions
Special Terms and Conditions for the Acceptance and Settlement of Credit and Debit Cards with Physical Presentation of the Card
Special Terms and Conditions for the Acceptance and Settlement of Card or Any other Payment Method
Special Terms and Conditions for Contactless Payments

1. Object of the Contract
  These terms and conditions (hereinafter also referred to as “terms“, “agreement“, “contract“) by
  SnapSwap International S.A., registered office - 9, Rue du Laboratoire, L - 1911, Luxembourg - an electronic money institution authorised by the Commission de Surveillance du Secteur Financier under the company registration N°EME-W00000007 (hereinafter referred as “SnapSwap”), in the capacity of Payment Facilitator,
  and
  the Contracting Party (hereinafter - “Contracting Party“) is an entrepreneur/ merchant, who accepted these terms and set them binding for a particular relationship with SnapSwap.
2. Definition
  
  “Acquirer” is a financial institution that acts as an intermediary between merchants and card payment networks such as Visa and Mastercard and provides acquiring of payment transactions service.
  
  “Payment facilitator” is a company that allows merchants, its customers, to accept electronic payments using the payment facilitator’s infrastructure. The Payment facilitator is always entering into the Merchant agreement on behalf of an Acquirer.
  
  “Cards” are payment instruments to initiate payments regarding the respective Payment scheme, including card data stored on another medium (e.g. smartphone). This contract governs the settlement of card transactions in both card-present and card-not-present transactions. Within the scope of this contract term “Cards” also includes “Other payment methods/instruments”, meaning any instruments to initiate any cashless payments (such as mobile payment services, and electronic bank transfers).
  
  “Payment scheme/Payment instrument scheme or association” refers to a central payment network that uses payment instruments to process transactions. Its primary role is to manage payment transactions including operations and clearing. Visa, Mastercard, UnionPay, and American Express are brand examples of such schemes.
  
  “Standards” is a set of standards set by the Payment scheme that must be adhered to.
  
  “Merchants” (also referred to as sub-merchant) are the Payment facilitator’s clients (hereinafter - “Contracting Party“) that are onboarded by SnapSwap to start accepting electronic payments. These can either be physical storefronts accepting card-present transactions, online businesses accepting card-not-present transactions or any other Payment schemes.
  
  “Customer/client of Merchant” is a natural person or legal entity buying services/goods from the Merchant.
  
  “MOTO” (Mail Order Telephone Order) are systems that allow businesses to take and manage payment transactions remotely. This web-based payment system facilitates payment transactions that can be taken over the telephone or via email or written requests.

1. Submission Principles and Authorisation
  1. Under these terms, the Contracting Party is entitled to accept all payment instruments of the agreed type for cashless payment settlement. The Contracting Party shall submit for settlement exclusively to SnapSwap all payment orders issued in its business operations using the agreed payment instruments accepted and submitted under the terms of this agreement.
  2. Should a customer opt for cashless payment settlement using their card or any other means, the Contracting Party must accept it under the terms hereof, provided that acceptance of that payment instrument has been agreed between SnapSwap and the Contracting Party.
  3. Under the terms of this agreement, the Contracting Party is entitled to accept and submit payment orders exclusively within the European Economic Area (EEA) and Switzerland.
    
    Note: Section 1.4 to 1.7 referred only to card-related transactions.
  4. The Contracting Party shall explicitly designate all reserved card transactions as reservations before submission to SnapSwap. Where a card transaction and/or authorisation is not explicitly designated as a “reservation” or “pre-authorization”, it shall be treated as a “final authorisation”. The Contracting Party shall immediately cancel reservations if no card transaction is booked after such a reservation. If a reservation is made, the Contracting Party shall furthermore inform the cardholder of the amount the Contracting Party has reserved on their card and shall obtain their consent thereto. The cardholder’s consent must also be obtained if the Contracting Party subsequently increases the amount of the reservation. The Contracting Party shall submit reservations as a final authorisation within the deadlines specified by the card associations for each card product or type of transaction.
  5. Where a transaction/authorisation with a Mastercard/Visa card is not designated as a reservation despite meeting the following requirements for a reservation, the Contracting Party shall assume potential additional fee by the card schemes for that card transaction in accordance with the applicable schedule of fees and services. The requirements for a reservation as defined herein are as follows:
    - a) Booking later than three working days after obtaining authorisation and/or
    - b) authorisation and clearing amount do not match and/or
    - c) authorisation and clearing currency do not match.
    Furthermore, the Contracting Party shall pay a card scheme fee if the Contracting Party cancels a transaction/authorisation that is not explicitly designated as a reservation. The reason for the cancellation is irrelevant in this case.
  6. A cardholder’s card data may only be saved in a secure, PCI-certified environment and only with the cardholder's express consent. The cardholder's consent (“consent agreement”) must contain the following elements: Confirmation of the saved card number (PCI compliant, e.g. by reducing the number to the last four digits), the reason for using the card data, the agreement term and confirmation by the Contracting Party that all changes will be communicated to the cardholder via an agreed means of communication. The Contracting Party must in advance provide information and obtain the cardholder's consent on the following points: Cancellation and return conditions, registered office of the Contracting Party, transaction amount and currency or the description of how the transaction amount is determined. Where surcharging is allowed on an exceptional basis, e.g. by an express legal condition, confirmation of the surcharge levied. Transactions may only be initiated for the purposes stated in the “consent agreement”.
  7. The issuing of an authorisation number does not restrict SnapSwap's chargeback rights, because when it obtains an authorisation number from the card issuer, SnapSwap can only check the credit limit on the card and whether the card number has been blocked due to card loss or theft.
  8. The form and contents of data transmissions are specified in data protocols of the payment instrument settlement companies and determined on that basis. These must be complied with by the Contracting Party.
    
    At its own expense, the Contracting Party must immediately implement any amendments to the above-mentioned data protocols made by the card payment instrument settlement companies at the request of payment system operators (e.g. card associations).
  9. The Contracting Party is not entitled to assign its claims against SnapSwap to third parties without the prior written consent of SnapSwap.
2. Service Fees
  By accepting these terms and conditions you irrevocably accept relevant Fees as displayed within the relevant section of the service-designated website.
3. Settlements, Lien, Provision and Increase of Collateral
  1. Under the terms of this agreement, and irrespective of the customer of the merchant’s payment orders, SnapSwap shall pay the Contracting Party a sum equal to the total sales transaction submitted minus the agreed service fee and any applicable charges. Such payment shall not constitute any acknowledgment by SnapSwap of any legal obligation to reimburse sales transactions submitted by the Contracting Party. In exchange for such settlement, the Contracting Party assigns to SnapSwap its claim against its customer for the underlying transaction. The assignment shall take effect on receipt of the customer transaction data by SnapSwap. SnapSwap shall accept the assignment. After processing the transaction data submitted by the Contracting Party, SnapSwap shall credit it to the Contracting Party’s internal balance subject to the SnapSwap settlement schedules. The complete data sets or sales slips received by SnapSwap along with the sales revenue shall be allocated for payment to the bank account indicated by the Contracting Party within the payment period agreed with the Contracting Party (here referred to as “settlement rules” related to the merchant payout). By default the merchant gets paid out according to a weekly schedule. This setting can be adjusted to support instant payout or other frequency upon mutual agreement.
  2. The payout process (fund routing) will only be authorised through a credit institution (excluding alternative account providers such as e-money institutions) located within EEA or Switzerland and exclusively under the name of the Contracting Party.
  3. If the reference date or the payout date does not fall on a banking day, the payment period shall begin on the next banking day. For the purposes of the payment and settlement periods under this agreement, “days” shall always refer to banking days applicable to Luxembourg.
  4. SnapSwap shall credit the proceeds of sales revenue received from the relevant payment instrument’s issuer to SnapSwap’s safeguarding account at an EU regulated credit institution. SnapSwap shall ensure that payment amounts received as per the first sentence are not mixed with its own funds. SnapSwap has a valid right to deduct any fees or interest from the safeguarding account it holds for the payment facilitator activities with an authorised credit institution. The fees deducted from the segregated account should be removed as frequently as practicable. In no circumstances should such funds be kept commingled overnight. This obligation to safeguard starts immediately on the reception of funds.
  5. In the case of
    - a) repeated complaints from the customer of the Contracting Party;
    - b) repeated use of unauthorised payment means (e.g.: counterfeit or stolen cards) in the Contracting Party’s business operations;
    - c) well-founded suspicion that total billing amounts have been divided into several smaller amounts;
    - d) non-compliance with these terms;
    - e) to secure its own future claims against the Contracting Party for chargeback of sales transactions or any formal disputes process;
    - f) non-performance due to insolvency or cessation of activity by the Contracting Party,
    SnapSwap is entitled to credit the submitted sales revenue to the Contracting Party, only after dispute periods defined by the payment schemes have expired and to assert its right of retention.
  6. The Contracting Party grants SnapSwap a legal right of lien over all its present and future claims against SnapSwap arising under this contract (particularly payment claims from chargebacks and including any penalties levied by payment instrument scheme) SnapSwap hereby accepts this lien.
  7. SnapSwap is entitled to require the Contracting Party to provide or raise appropriate collateral in the form of bank guarantees or reserves to secure all existing, future and conditional claims. The Contracting Party shall immediately comply with any such request from SnapSwap. If SnapSwap did not ask for collateral to be provided when the contract was signed, it doesn’t circumvent SnapSwap to require collateral protection at a later stage of the relationship in case detection of a higher risk profile. Such circumstances shall in particular include cases where
    - a) SnapSwap becomes aware of serious adverse circumstances affecting the Contracting Party, its owner or shareholders,
    - b) there is or is likely to be a substantial deterioration in the Contracting Party’s financial position or its financial position does not seem secure,
    - c) the value of the existing collateral has fallen or is likely to fall.
  8. The Contracting Party is only entitled to submit sales transactions in the currency agreed. Those transactions must be in the same currency used and/or selected by the merchant’s customers when placing the order or making the purchase. SnapSwap shall settle the transactions in the settlement currency agreed. The exchange rate for currency conversions is determined based on the current SnapSwap schedule of fees and services.
  9. By default, SnapSwap shall provide the Contracting Party with a set of electronic record of activity with among others:
    - a) the transactions submitted
    - b) the settlement balance
    - c) the amount and reason of customer claims
    - d) the level of collateral restrained
    - e) the fee payable
    The Contracting Party must check the accuracy and completeness of the record of activity immediately after receipt. Objections concerning inaccurate or incomplete sales figures or bills issued must be raised by the Contracting Party in writing within four weeks of receipt. The deadline applies to the date the objection is sent. If the Contracting Party does not raise objections in a timely fashion, the record shall be deemed accepted. SnapSwap shall expressly draw attention to this consequence.
  10. Unless otherwise agreed, information on payment transactions effected under Regulation (EU) 2015/751 (Art. 12(1)) shall be provided to the Contracting Party on a monthly basis digitally for a three-month period. After this period, the information shall be deleted and can no longer be provided to the Contracting Party.
4. Payment Instrument Requirements, Use of Third Parties by the Contracting Party
  1. In signing this agreement, the Contracting Party is agreeing by default of any of the payment instrument rules issued by the respective payment scheme, and implement them within the reasonable period specified by SnapSwap. The Contracting Party shall in particular comply with the information provided by card associations on products and services that are illegal and therefore may not be paid for using card association products.
    
    The Contracting Party shall bear any costs it incurs in complying with and implementing the payment instrument’s schemes procedural rules and/or other requirements. SnapSwap shall advise the Contracting Party accordingly where necessary.
    
    The Contracting Party shall reimburse all expenses incurred by SnapSwap that SnapSwap deemed necessary to implement this Contract. These include any penalties imposed on SnapSwap by the acquirer, Mastercard, Visa and/or any other payment association or any other damages arising in connection with the implementation of this Contract.
    
    SnapSwap is entitled to require the Contracting Party to temporarily suspend the submission of transactions, particularly where the acquirer, or the payment scheme requests that acceptance to be suspended.
  2. SnapSwap is obliged, with respect to the payment scheme and acquirer, to obtain under-takings from or enter into agreements with businesses used by the Contracting Party to support the processing of payment transactions (“payment service providers”), in order to ensure the application of payment instrument schemes rules in the processing of payment transactions and which contain the obligations of the payment service providers and give SnapSwap the right to conduct audits and perform checks. Therefore, in connection with the settlement of payment transactions, SnapSwap shall only procure services from payment service providers that have given such undertakings to SnapSwap or have entered into such agreements with SnapSwap. On request, SnapSwap shall provide the Contracting Party with templates for the undertaking or contractual arrangements to be forwarded to the payment service providers. Where a payment service provider appointed by the Contracting Party creates payment obligations for SnapSwap vis-à-vis the payment instrument schemes due to non-compliance with payment instrument schemes requirements (payment of damages, contractual penalties), the Contracting Party must indemnify SnapSwap against these payment obligations.
  3. SnapSwap needs to be informed of any intermediary appointed by the merchant that supports the processing of the merchant’s transactions (“payment service provider”). In respect to the application of the payment association rules, SnapSwap may be required to obtain undertakings or enter into an agreement with those payment service providers. In addition, SnapSwap will have the right to conduct audits and perform checks on the activity provided by those payment service providers. If a payment provider appointed by the Contracting Party creates additional obligations for SnapSwap vis-a-vis the payment scheme obligations or acquirer, the Contracting Party must indemnify SnapSwap against these obligations.
5. Consent regarding Data Protection, Other Reporting Obligations (PCI)
  1. Both Contracting Parties shall comply with the relevant data protection regulations and provisions. Furthermore, the Contracting Parties shall protect collected and stored transaction and customer-related data against unauthorised access by third parties and shall only use the data for the performance of the contract. The Contracting Party agrees that, in order to provide its services, SnapSwap can forward the Contracting Party’s master data and transaction data to its payment processor and can forward transaction data to payment schemes outside Europe, provided that this is necessary to settle transactions.
    
    The Contracting Party further agrees that SnapSnap processes its data by using risk assessment agencies for the purpose of risk prevention.
  2. Furthermore, the Contracting Party shall protect collected and stored transaction and customer data against unauthorised access by third parties and shall only forward this data to authorised third parties for the performance of the contract. The Contracting Party shall also register with SnapSwap in accordance with the requirements of the Mastercard Site Data Protection (SDP) and Visa Account Information Security (AIS) programs set up by the card associations Mastercard and Visa according to the Payment Card Industry Data Security Standard (PCI DSS) to protect against attacks and to prevent card data from being compromised; where specific transaction volumes are exceeded, the Contracting Party shall, at SnapSwap's request, become certified in line with Mastercard and Visa requirements and provide SnapSwap with a copy of the certificate on an annual basis. Moreover, the Contracting Party shall only submit transactions to SnapSwap via a PCI-certified service provider or PCI- certified software.
  3. The Contracting Party shall provide data processing information related to its customers in the check-out area, together with the order execution.
  4. The payment instrument data provided by customers in writing, by telephone or online must not be stored on the Contracting Party’s own systems once authorisation has been given. In connection with transaction settlement with SnapSwap, the Contracting Party shall only avail of the services of third parties where these parties meet the payment scheme requirements, and particularly for card association, the PCI standards, and undertake to comply with these PCI standards. The Contracting Party shall indemnify SnapSwap against claims for damages and contractual penalties imposed on SnapSwap by acquirer, or any other payment instrument’s scheme (e.g.: Mastercard, Visa or other third parties) due to non-registration and/or non-certification in line with the PCI-DSS standard or due to any successful (or unsuccessful) attempts to compromise transaction data at the Contracting Party’s business.
  5. The Contracting Party is required to treat as confidential any passwords forwarded to it. It is required to immediately inform SnapSwap of any unauthorised attempts to access its transaction related IT systems or of any suspicion that transaction data may have been compromised and to take the necessary measures in consultation with SnapSwap. If a payment instrument scheme reports suspicion that data has been compromised, the Contracting Party is required to immediately inform SnapSwap and to appoint an audit company approved by the payment scheme to conduct a forensic investigation and draw up a PCI audit report. This investigation will involve checking whether the PCI standards were met by the Contracting Party and whether third parties have accessed transaction data in the Contracting Party’s systems or those of companies appointed by it. Once the audit report is drawn up, the Contracting Party must immediately rectify any and all security defects and send SnapSwap a project plan for achieving PCI-DSS compliance. The Contracting Party shall bear the audit costs. Where SnapSwap deems the measures insufficient, SnapSwap is entitled to terminate the contract with immediate effect.
6. Credit Entries, Cancellations
  1. The Contracting Party shall only reimburse transaction revenue from cancelled transactions by means of an instruction to SnapSwap to credit the amount to the customer’s account. SnapSwap shall credit the amount to the customer and debit the Contracting Party by that amount. SnapSwap is entitled to retain the service fee for the original debit transaction (plus the interchange and payment scheme fees). The Contracting Party is not entitled to request a credit entry if it has not submitted the corresponding transaction in advance to SnapSwap for settlement or there is no revenue underlying the transaction submitted. SnapSwap is only required to make reimbursements within six months of the transaction being submitted.
    
    Note: Section 6.2 to 6.4 referred only to card related transactions
  2. If an EMV-certified POS terminal or an EMV- certified checkout system is used (hereinafter also referred to collectively as “terminal”), an electronic credit record must be generated in accordance with the operating instructions of the device and submitted to SnapSwap within two days of submitting the credit entry. At the same time, a credit slip with the card data and credit amount shall be issued, signed by the cashier and the original handed to the cardholder.
  3. If the checkout has no terminal or if an electronic credit record cannot be issued for technical reasons, the credit entry can be documented by issuing and submitting a credit slip, while giving the original to the customer. The Contracting Party’s checkout personnel must fully complete and sign the credit slip. The slip must be submitted to SnapSwap within ten working days after issue. However, if a hard- copy credit slip is submitted, the card issuer may chargeback the card transaction on this ground only. The Contracting Party bears the risk of chargeback on this ground.
  4. If ePayment software is used and a card transaction is cancelled, the Contracting Party shall issue an electronic credit entry to the cardholder’s card using the relevant software.
7. Merchant’s Customer Complaints
  Cardholder complaints and claims in relation to the services provided in the underlying transaction shall be settled directly by the Contracting Party with the customer.
8. Acceptance Information
  Depending on the accepted payment methods or payment instrument of the payment associations, the Contracting Party is required to display the corresponding acceptance marks provided by SnapSwap and the authentication procedure marks in a prominent location at the checkout area and/or on its payment website, in the catalogue or in other media. Furthermore, the Contracting Party shall clearly and unequivocally inform its customers at the above-mentioned appropriate locations if it does not accept a specific payment instrument.
9. Information Disclosure Obligations
  1. The Contracting Party shall immediately inform SnapSwap in writing of any changes to the data provided by it in the service agreement. This applies in particular to:
    - a) changes to the legal form or company name;
    - b) changes of address and/or bank account details;
    - c) change in location of the business operations at which the services underlying the card transactions submitted are provided;
    - d) the sale or lease of the company, other change of ownership and/or closure of the business;
    - e) the transfer of the Contracting Party’s shares or those of its direct or indirect shareholders or other measures with a similar economic effect that result in a change of control at the Contracting Party or its direct or indirect shareholders, in particular where individual shareholders hold more than 25% of the shares or voting rights in the Contracting Party;
    - f) significant changes to the product range offered by the Contracting Party in-store or online, in the catalogue or in other media;
    - g) change of payment service provider or network operator;
    - h) applications for insolvency proceedings or composition proceedings
    - i) significant change in the business volume
  2. When notified of a change of ownership by the new owner, SnapSwap is entitled to only credit the Contracting Party for transaction revenue submitted from that date once it has fully verified the change of ownership.
  3. On request, the Contracting Party shall immediately forward SnapSwap the latest audited annual financial statements or other business documentation required to assess the Contracting Party’s financial position.
  4. The Contracting Party is liable to SnapSwap for damages arising from its culpable breach of these information disclosure obligations.
  5. Under money laundering and anti-terrorist financing regulations applicable in Luxembourg, SnapSwap is required to obtain information on the Contracting Party. The Contracting Party shall duly provide SnapSwap with the information requested fully and accurately, to cooperate with SnapSwap or third parties in the collection of this data and to immediately inform SnapSwap of any changes to this information.
  6. The Contracting Party agrees that SnapSwap can forward the Contracting Party’s company name to the payment instrument schemes or service provider to check for previous breaches of contract with other settlement companies and to mitigate the relevant risks. This consent also applies where the contract is terminated by SnapSwap due to breach of contract on the part of the Contracting Party.
10. Liability, Claims for Damages
  1. SnapSwap and its legal representatives or agents shall only be held liable if they are in breach of essential contractual obligations (key obligations), or in cases of personal injury or damage for which SnapSwap is responsible under mandatory statutory provisions, unless the damage is attributable to grossly negligent or intentional breach of contractual obligations by SnapSwap, its legal representatives or agents.
  2. Where essential contractual obligations as defined above are breached due to inadvertent negligence, SnapSwap's liability shall be limited to EUR 10,000 per instance and a total of EUR 50,000 per calendar year. This limitation of liability also applies in the event of grossly negligent breach of contractual obligations by agents that are not legal representatives or senior executives of SnapSwap.
  3. By all means SnapSwap's liability is limited to damage caused directly by SnapSwap that is generally and typically foreseeable in such cases. There is no liability for lost profits in any case.
  4. SnapSwap's liability for damages arising due to failure to execute a payment order or incorrect or delayed execution of payment is limited to EUR 12,500. This does not apply to wilful intent and gross negligence, damages for interest and risks specifically assumed by SnapSwap.
  5. The Contracting Party is liable to SnapSwap for damages arising due to the culpable compromising of transaction data, due to culpable breach of contract or breach of payment instrument’s breach requirements on the part of the Contracting Party; (contractual) penalties imposed by acquirer, Mastercard, Visa or another payment scheme in connection with breach of contract are also deemed damage.
  6. Any complaints may be submitted to SnapSwap by post (9 Rue du Laboratoire, 1911 Luxembourg) or email to the address “complaints@snapswap.eu“.
  7. For privacy policy and GDPR related questions, the Contracting Party may contact Snapswap via hello@snapswap.eu
  8. For any technical problems, questions during set-up or the first steps as a new customer, three ranges of options are available:
    - a) Through the registered user portal
    - b) https://support.wallee.com/hc/en-us
    - c) info@wallee.com
  9. SnapSwap shall provide an initial confirmation of the reception of the Contracting Party’s complaint within 10 business days via email.
  10. Once SnapSwap concludes its investigation of the complaint matters, an e-mail containing the final response shall be sent to the Contracting Party. Should SnapSwap fail to conclude the investigation and provide the Contracting Party with the final response within 1 month from the date the complaint has been acknowledged, SnapSwap shall issue a holding response stating the reasons why final response is postponed.
  11. Should SnapSwap fail to resolve the complaint to the Contracting Party’s satisfaction, or the offer of redress being insufficient or inappropriate, the Contracting Party may request to have the complaint reviewed by a member of the management team of SnapSwap. In the event the Contracting Party does not receive a satisfactory resolution or has not received a response from the management of SnapSwap within 1 month from the date of such request, the final response will hold contact information of the CSSF, allowing the Contracting Party to seek further out-of-court resolution.
  12. The Contracting Party can find more information about the CSSF’s complaints’ procedure at “https://www.cssf.lu/en/customer-complaints/”.
11. Term, Termination and Payment of Damages
  1. The agreement comes into effect when these terms are accepted by the Contracting Party.
  2. The agreement term is considered by default for an indefinite period. SnapSwap can terminate this agreement subject to a two-month notice period notified in writing. The Contracting Party is entitled to terminate this agreement subject to a two-month notice period notified in writing only after the expiration of 3 (three) years period from the date when this agreement became effective.
  3. If SnapSwap becomes aware of terms breach or of any other negative facts concerning the Contracting Party, its owners or senior executives (elements considered as good cause for termination), SnapSwap may terminate at any time, without prior notice, this present agreement. Good cause for termination without notice by SnapSwap shall include in particular where:
    - a) SnapSwap becomes aware of significant adverse circumstances regarding the Contracting Party or its owners which would make it unreasonable for SnapSwap to honour the contract. Such circumstances shall include a situation where the Contracting Party has provided incorrect information in the contract, if there is or is likely to be a significant deterioration in its financial position (for example due to an (impending) application for insolvency proceedings or composition proceedings, direct debit returns due to insufficient funds, negative financial reports), its financial position does not seem secured or where it is in culpable breach of its information disclosure obligations under the terms of this agreement,
    - b) the Contracting Party has not submitted any sales transaction for settlement within two months of concluding the contract,
    - c) the Contracting Party submits card not present transactions effected without physical presentation of a credit card without having concluded a corresponding service agreement for card not present transactions,
    - d) the Contracting Party is in arrears with the settlement of payables due to SnapSwap despite having received a grace period and having been threatened with termination of the contract,
    - e) the Contracting Party submits sales transactions from third parties for settlement or submits sales transactions for goods or services that are not covered by its business purpose, price segment or categories of goods and services stated by it,
    - f) SnapSwap tells the Contracting Party that the service fee agreed in the discount model is insufficient to cover any fees arising due to the settlement of the Contracting Party’s transactions, and the Contracting Party does not agree to an adjustment within two weeks of receiving the cost calculations and SnapSwap's request for an adjustment,
    - g) the number of card transactions charged back to the Contracting Party in a calendar month exceeds (0,65%) of the total number of card transactions submitted by the Contracting Party during that period, the total number of card transactions charged back to the Contracting Party over one calendar month exceeds 75 disputes.
    - h) the Contracting Party repeatedly makes credit entries without submitting any transactions or making any sales, or the total amount and number of credit entries made by the Contracting Party in calendar month is at least 30% of the total transactions submitted for settlement,
    - i) the amount and number of authorisation requests made by the Contracting Party and rejected by SnapSwap in a calendar month amount to 10% of overall authorisation requests made in this period,
    - j) the Contracting Party repeatedly requests or obvious intends to repeatedly request the authorisation of payment method transactions for which the Contracting Party has no acceptance entitlement,
    - k) the Contracting Party has repeatedly failed to comply with the settlement terms,
    - l) the Contracting Party is in serious and/or repeated breach of its obligations under the agreement, making it unreasonable for SnapSwap to honour the contract,
    - m) the Contracting Party does not comply with SnapSwap's request to register in accordance with the PCI DSS requirements,
    - n) the Contracting Party does not comply with its information disclosure obligations,
    - o) the Contracting Party is not (or no longer) in possession of the licences, approvals and/or other permits necessary for its business operations and/or it has these withdrawn and/or refused for any reason,
    - p) the Contracting Party's shares or those of its direct or indirect shareholders are (fully or partially) transferred or other measures with a similar economic effect are taken resulting in a change of control at the Contracting Party or its direct or indirect shareholders,
    - q) acquirer, Mastercard, Visa or another payment method scheme requests that SnapSwap suspend payment method acceptance for the Contracting Party for good cause which may include but not limited to:
      - aa. Previously disputed charges - Submitting a transaction that was previously disputed and subsequently returned to the merchant. However, the merchant may pursue payment from the customer outside the payment method.
      - bb. Illegal transaction - Transactions must be legal in both the customer’s and merchant’s jurisdiction.
      - cc. Fraudulent or unauthorised transaction.
      - dd. Adding surcharges to transactions, unless it is explicitly done so in accordance with the applicable law, regulations and payment scheme rules.
      - ee. Travelers cheques - Disbursing funds in the form of travellers cheques, if the sole purpose is to allow the cardholder to make a cash purchase of goods and services from the merchant.
      - ff. Debt repayment – Accepting payment methods for:
        - Collecting or refinancing existing debt that has been deemed uncollectible by the merchant providing the associated goods or services.
        - Previous card charges.
        - A transaction that represents the collection of a dishonoured check.
      - gg. Any conduct that could adversely affect the integrity and/or reputation of the payment scheme and/or acquirer.
    - r) the Contracting Party transfers its registered office abroad or transfers its bank account to a bank outside the European Economic Area or Switzerland,
    - s) the Contracting Party does not comply with its obligation to provide, maintain or renew bank guarantees or under another collateral agreement within a reasonable deadline set by SnapSwap,
    - t) when using a POS terminal/POS checkout system, the Contracting Party repeatedly fails to submit sales slips signed by the cardholder despite being asked to do so by SnapSwap or fails to submit these within the deadline set by SnapSwap,
    - u) the Contracting Party fails to comply with SnapSwap's request to install an EMV-certified POS terminal/POS checkout system in good time,
    - v) the Contracting Party changes its product range to the extent that it would be unreasonable for SnapSwap to continue the contractual relationship, even with due regard to the legitimate interests of the Contracting Party,
    - w) when the contract was concluded, the Contracting Party gave false information on its business operations or on the goods or services offered by it, in particular where it did not indicate that these included erotica, third-party gambling revenue, mail-order sales of medication or tobacco products or other goods or services that are illegal or unethical under the laws of any EEA country or the country to which they are delivered, did not notify SnapSwap of subsequent changes to its product range or business purpose in advance in writing, or continues to submit transactions for settlement from this product range or business purpose despite not being approved to do so,
    - x) the Contracting Party does not comply in a timely manner with SnapSwap's request to implement the current payment instrument schemes / payment method procedures,
    - y) the Contracting Party does not meet the security requirements regarding online payments.
  4. At the end of the contract, the Contracting Party shall remove all references to the selected payment instruments acceptance, unless the Contracting Party is otherwise entitled to retain them.
  5. The Parties also agree that the Contracting Party shall submit sales transactions made in its business operations exclusively to SnapSwap for settlement throughout the agreed Contract term. Where the Contracting Party does not submit such sales transactions to SnapSwap for settlement or does not do so to SnapSwap exclusively, SnapSwap is entitled to terminate the contract on exceptional grounds and/or to invoice the Contracting Party for lump-sum compensation in this regard. This lump-sum compensation claim is calculated by multiplying the monthly service fee levied for the last 12 months (or six months where the contract term has not yet been in effect for 12 months), less expenses not incurred by SnapSwap, by the remaining term (i.e. the number of days between the last submission to SnapSwap and the contract term actually agreed). There shall be no claim to lump-sum compensation where the Contracting Party can show that a claim for this amount is not justified. Regardless of the enforcement of a claim for lump-sum compensation, SnapSwap is entitled to assert a claim for damages actually incurred and for other damages, by applying the lump-sum compensation allowance where applicable.
12. Compliance with Statutory and Regulatory Provisions
  The Contracting Party is required to comply with all relevant laws and (regulatory) provisions. The Contracting Party hereby warrants to SnapSwap that it has all the licences, approvals and/or other permits necessary for its business operations and that it shall maintain legal ownership thereof throughout the contract term. The Contracting Party shall immediately inform SnapSwap in writing but not via telecommunications (fax or email) if any such licence, approval or permit is withdrawn, refused and/or not renewed for any reason.
13. Waiver of Statutory Provisions
  Contracting Party claims and objections against SnapSwap regarding any incorrect payment transaction are excluded if the Contracting Party has not notified SnapSwap within 6 months at the latest of the date on which a debit with an unauthorised or incorrect payment transaction was made.
14. Miscellaneous
  1. References to other provisions relate to these Terms and Conditions unless other provisions are specifically indicated.
  2. Any amendments or additions to these Terms and Conditions or to the underlying Contract must be in writing in order to be valid. This also applies to any agreement to revoke this written form requirement.
  3. Should one of the provisions hereof be or become invalid, this shall not affect the validity of the other provisions. The Parties are bound to replace the invalid provision with a valid provision which comes as close as possible to the original economic intent.
  4. SnapSwap can amend or supplement the Terms and Conditions provided it informs the Contracting Party in writing. Amendments or additions shall be deemed acknowledged by the Contracting Party if it has not objected thereto within six weeks of receipt of the written notification. SnapSwap shall expressly draw the Contracting Party’s attention to these consequences when the notification is sent. Objections sent within the six-week period shall be deemed to meet this deadline. If the Contracting Party exercises its right to object, the amendments to the legal relationship between the Contracting Party and SnapSwap shall be dropped and SnapSwap shall be entitled to terminate this service agreement on exceptional grounds subject to two months’ notice. This right to terminate expires within three months of receipt of the Contracting Party’s objection.
  5. The Contracting Party is not entitled to assign claims against SnapSwap to third parties without the prior written consent of SnapSwap.
  6. For the dispute resolution procedure the Parties agree that SnapSwap shall respond to any Contracting Party complaints via email.
  7. Snapswap will provide the Services for the benefit of the Contracting Party solely. The Contracting Party explicitly agrees that Snapswap may outsource (part of) the service to third party providers.
  8. The Contracting Party also acknowledges that Snapswap’s IT infrastructure may be partially outsourced and relying on cloud computing infrastructure and that Snapswap may use third-party providers or contractors for operations or services delivery.
  9. The Contract is subject to the laws of Luxembourg being the sole place of jurisdiction for all legal disputes arising from this contractual relationship.
1. Card Acceptance Terms and Conditions
  The Contracting Party is not authorised to accept the card for cashless payment settlement or to submit card revenue to SnapSwap for settlement where
  - a) the customer does not physically present the card but seeks to transmit or has transmitted the card data to the Contracting Party in writing (e.g. by fax or postcard), by telephone, email or online, unless the Contracting Party has concluded a separate written contract with SnapSwap to this effect,
  - b) the Contracting Party's claim against the cardholder is not established as part of its own business operations but as part of those of a third party, or does not relate to a service provided on their own account to the cardholder,
  - c) the transaction to be settled does not come under the business purpose and goods, product or service segment indicated by the Contracting Party in this Contract, in its voluntary disclosures or in other statements,
  - d) the claim to be settled relates to an illegal or unethical transaction under the laws applicable to the legal transaction with the cardholder,
  - e) given the circumstances in which the card was presented, the Contracting Party should have had doubts as to the customer's entitlement to use the card. Such doubts should arise in particular:
    - aa. where the total amount of the card transaction is split at the cardholder’s request or is to be split across several credit cards,
    - bb. where the cardholder, when presenting the card, has already signalled potential problems with acceptance.
  SnapSwap is entitled to amend or supplement the terms and conditions specified under Section B by written notification to the Contracting Party subject to four weeks’ notice if SnapSwap has to make such amendments due to potential fraudulent practices, changes to legal provisions or corresponding requirements of Mastercard Europe/Inc. (hereinafter referred to collectively as “Mastercard”), Visa Europe/Inc. (hereinafter referred to collectively as “Visa”), acquirer or another card association.
2. Authorisation at POS
  1. The Contracting Party shall transmit authorisation requests regarding card transactions electronically to SnapSwap using a contactless-enabled and EMV- certified POS terminal or a contactless-enabled and EMV-certified checkout system (hereinafter referred to collectively as just “terminal”). The terminal must meet card association security requirements, have card association approval and in particular be PCI-certified and able to process contactless transactions in accordance with the Special Terms and Conditions on Contactless Payment. The Contracting Party shall instruct its network operator accordingly. As part of the authorisation process, the Contracting Party shall read the chip card, where applicable, using the chip reader on the terminal. Unless otherwise agreed in writing with SnapSwap, the Contracting Party is required to immediately request online electronic authorisation for every card transaction, regardless of amount, via the SnapSwap terminal (zero-euro limit). If a chip card is presented, offline authorisation is also permitted if, following the successful reading of the chip, the cardholder is requested by a message in the terminal display to enter a personal identification number (PIN) and payment is confirmed after the PIN has been entered. The magnetic strip on the card should only be read by the terminal if the chip on the card is faulty or the card has no chip; all the data from the magnetic strip shall be sent to SnapSwap.
  2. Card data may only be entered into the terminal manually to obtain authorisation in the event of an operating fault . In this case, the Contracting Party is not obliged to accept the card.
  3. Once a terminal is installed in a checkout area, the Contracting Party shall notify SnapSwap accordingly and provide SnapSwap with the terminal ID number to allow SnapSwap to initialise the terminal and approve it for card processing.
  4. If for technical reasons the terminal, the connection to SnapSwap or the SnapSwap data centre should malfunction, making electronic authorisation requests and/or transaction data transmission impossible, the rules on the non-electronic authorisation of card transactions shall apply to payments with Mastercard, Visa. If in these cases there are any chargebacks by the card issuer, the Contracting Party must prove that electronic authorisation was not possible by presenting an electronic terminal printout with an error message.
  5. For card transactions with Maestro, Visa Electron, and V PAY, the Contracting Party may only obtain online authorisation electronically by means of a terminal. These cards require the cardholder to enter a personal identification number (PIN), which is then accepted by the terminal.
3. Submission Principles
  1. When a payment is initiated, the Contracting Party will use a terminal to read the data either from a chip on the card or from the magnetic strip, if the card has no chip, or from a tap for card with contactless technology or any other mobile or from any mobile payment application. The Contracting Party shall transmit all the data for the transaction, in particular the payment method related data like card number, expiry date for card payment transaction, total billing amount in the original transaction currency and Contracting Party number, to SnapSwap electronically within two days of the transaction date, using a terminal initialised and approved by SnapSwap, unless it is authorised to use sales slips. The Contracting Party is responsible for ensuring that the payment method data is received by SnapSwap in full, on time and in a data set suitable for electronic processing. The Contracting Party shall electronically submit only transactions for which it has received an authorisation number from SnapSwap, unless SnapSwap has approved another submission procedure (e.g. batch procedure) in writing.
  2. The Contracting Party must submit all transaction data from Maestro, Visa Electron, V PAY, Twint to SnapSwap electronically and immediately after the transaction date. Manually produced sales slips may not be submitted for Maestro, Visa Electron, V PAY transactions, nor may any transactions requiring the customer to enter a PIN.
  3. The Contracting Party must keep copies of all electronic and all documents about the sales underlying these transactions, in particular electronic and till receipts or bills and the ‘no refund policy’ (= evidence that before the transaction was completed the customer was notified of the Contracting Party’s general terms and conditions/cancellation policy), for 18 months after the respective slip or document was produced, and must promptly send SnapSwap on request, within the deadline set by SnapSwap, a copy of the sales slip and other documents so that it can examine any queries from the payment method scheme. This does not affect the Contracting Party’s statutory storage obligations. For card specific transaction, if the Contracting Party does not send SnapSwap on request a copy of the sales slip or other documentation for a settled transaction within the deadline set by SnapSwap, and if the transaction is charged back to SnapSwap by the card issuer as a result, SnapSwap is in turn entitled to charge this sales transaction back to the Contracting Party.
4. Reclaiming Card-related Transaction
  1. In the event of non-compliance with one or more provisions, SnapSwap is entitled to reserve their right to reclaim payment of settled transactions within a period of 18 months from the date of a card transaction if the card issuer has charged the transaction back to SnapSwap.
  2. In the cases mentioned above, SnapSwap shall invoice the Contracting Party for card transaction already paid, less the service fee already paid on that card transaction by the Contracting Party, and shall offset it against the Contracting Party’s other due receivables. If offsetting is not possible, the Contracting Party must pay the total immediately upon receipt of SnapSwap's invoice.
  3. The provisions of Section B shall continue to apply for 18 months after this contract comes to an end.
1. Payment Method Acceptance Terms and Conditions
  1. The Contracting Party is not authorised to accept card or any other payment method agreed data for cashless payment settlement or to submit transactions to SnapSwap for settlement under the following circumstances:
    - a) the customer’s residential, delivery or billing address is located in a FATF (Financial Action Task Force) High-Risk Jurisdiction subject to a Call for Action or “blacklist country”.
    - b) for transactions transmitted in writing, by telephone or online, the Contracting Party does not use the current payment authentication procedures. (For card transaction, currently “Verified by Visa” and “Mastercard SecureCode” (in future “Mastercard Identity Check“) or “Maestro SecureCode”) to transmit Mastercard, Visa or Maestro card data online and/or does not send the three-digit card security number to SnapSwap electronically when the card data is transmitted by telephone or in writing,
    - c) the sale to be settled was not carried out directly between the customer and the Contracting Party, but in a third-party business,
    - d) the transaction underlying the sale to be settled does not correspond to the Contracting Party’s business purpose or area of business as stated in the acceptance agreement or voluntary disclosures,
    - e) the claim to be settled relates to illegal, unethical, violent or degrading content under the laws applicable to the legal transaction with the cardholder,
    - f) for transaction performed through MOTO and e-commerce sales channels, the Contracting Party’s goods or services underlying the sale to be settled are offered for sale under domain addresses (URL) or advertising or sales channels not mentioned by the Contracting Party in the agreement or not subsequently approved by SnapSwap in writing following notification by the Contracting Party,
    - g) given the circumstances in which the customer payment method was presented, the Contracting Party should have had doubts as to the customer's entitlement to use this method. Such doubts should arise in particular:
      - aa. where the total amount of the transaction is split at the customer’s request or is to be split across several payment method(s),
      - bb. where the client, when presenting the payment method, has already signalled potential problems with acceptance.
  2. SnapSwap is entitled to amend or supplement the conditions by written notification to the Contracting Party with four weeks’ notice if SnapSwap deems this necessary due to potential misuse or to comply with changes in statutory provisions or with the requirements of acquirer, or the payment schemes.
2. Reclaiming Payment for Card-related Transactions
  1. In the event of non-compliance with provisions, SnapSwap is entitled to reserve its right to reclaim payment of card revenue settled within a period of 18 months from the date of a card transaction if the card issuer has charged the transaction back to SnapSwap.
  2. Furthermore, the Contracting Party must refund any transaction previously paid by SnapSwap if the customer demands that the debit to its account is cancelled or refuses payment and the customer declares in writing, within six months of its account being debited or the date on which the service was or should have been provided, that
    - a) they did not receive the goods or services at the delivery address provided by them, unless – within 14 days of being notified of the complaint by SnapSwap – the Contracting Party can provide documentation showing that the goods were delivered to the delivery address provided,
    - b) the goods supplied or the services provided by the Contracting Party did not match the Contracting Party’s product description in terms of quality, colour, size, quantity or service, the goods were delivered in damaged condition or too late, or the services were inadequate or provided too late, unless the Contracting Party claims either that the customer did not return the goods or else can prove by means of appropriate documentation that the defect, the deviation or the damage either did not exist or has been rectified by replacing or repairing the goods or rectifying the service and delivering the goods or services to the customer again.
  3. SnapSwap shall invoice the Contracting Party for the transaction previously paid, less the service fee billed, and shall offset the balance against funds credited for other transactions. If offsetting is not possible, the Contracting Party must pay the total revenue charged back immediately upon receipt of SnapSwap's invoice.
  4. The issuing of an authorisation number does not restrict SnapSwap's restitution rights, because when it obtains an authorisation number from the card issuer, SnapSwap can only check the credit limit on the card and whether the card number has been blocked due to card loss or theft. SnapSwap cannot check that the customer’s name matches the name of the legitimate holder of the card presented.
  5. If the card is accepted online, SnapSwap shall not reclaim payment of the transaction from the Contracting Party on the grounds that the legitimate cardholder did not authorise his account to be debited if the Contracting Party can prove that it verified the legitimacy transaction using the available authentication procedures. For card-related transaction, (currently “Mastercard SecureCode” (in future “Mastercard Identity Check”) or “Maestro SecureCode” for Mastercard and Maestro sales and “Verified by Visa” for Visa or Visa Electron sales) in accordance with Mastercard and/or Visa requirements. Payments may still be charged back if the card transaction was effected using a prepaid card.
3. Additional Security Requirements regarding Online Payments
  1. If a Contracting Party saves, processes or transmits payment data in its usual course of business, it must implement security measures in its IT infrastructure in order to avoid the theft of sensitive payment data through its systems. For saving, processing or transmitting contractual payment data, the Contracting Party shall only use service providers that have made a contractual undertaking to comply with best principles of data security and shall, upon request, provide evidence of this undertaking to SnapSwap.
  2. If a Contracting Party saves, processes or transmits payment data, it must cooperate with SnapSwap and the competent law enforcement agency, the acquirer and/or any instrument scheme in investigating payment security incidents as well as incidents relating to data protection breaches.
  3. The Contracting Party shall support technologies, e.g. in accordance with the requirements set out in Section C which enable issuers of payment cards and other payment methods to authenticate the client for the relevant transaction.
  4. The Contracting Party shall clearly separate the payment processes from its online shop in order to make it easier for cardholders to determine when they are communicating with the payment provider and when they are communicating with the Contracting Party (e.g. by redirecting the cardholder and opening a new window so that the payment process is not displayed within a frame of the Contracting Party).
4. Other Contracting Party Obligations
  1. The Contracting Party must comply with the provisions on distance contracts according to the laws of its jurisdiction of incorporation. In particular, it must incontrovertibly point out to the customer that it is responsible for the sale of the goods or services, payment settlement, the goods and services themselves, customer service, processing complaints and conditions of sale. The Contracting Party must identify itself as the customer’s contracting party on its homepage, in its catalogue or in its other media.
  2. The customer must have access to the Contracting Party’s General Terms and Conditions on its homepage, in its catalogue or in its other media and these must be acknowledged by the customer before they enter the transaction-related data.
  3. The Contracting Party must clearly indicate the following information on its homepage, accessible via the internet address indicated in the contract, in its catalogue or in its other media:
    - a) company name and address, commercial register number and relevant commercial court if applicable, name of senior executive(s) and/or board members and all other details required by law,
    - b) contact address for customer service, including email address and telephone number,
    - c) description of goods and services on offer as well as the price of the goods and services including all taxes and other price components, plus any delivery and shipping costs,
    - d) data protection provisions and information on the security of card data transmission,
    - e) card scheme logos, and settlement currency,
    - f) delivery terms and refund policy,
    - g) general terms & conditions.
  4. In the event of any new internet domain addresses (URL) and new sales channels via which the Contracting Party intends to submit transactions to SnapSwap, the Contracting Party must promptly contact SnapSwap in writing for its approval before submitting transactions.
  5. The Contracting Party shall ensure that payment-related data cannot be misused by its staff or on its premises. SnapSwap must be immediately notified if the Contracting Party suspects or knows that such data is being misused in its business, that data espionage is going on in its business or an excessively high rate of authorisation requests are being denied.
  6. The Contracting Party shall transmit payment-related data to SnapSwap exclusively in encrypted form using at least 128-bit encryption.
  7. The Contracting Party shall allow SnapSwap to inspect its premises on request to enable SnapSwap to verify compliance with the terms of the contract.
1. Scope
  1. The following rules apply in addition to the acceptance and submission of transactions using payment with a contactless interface.
  2. Under the following provisions, SnapSwap allows the Contracting Party to accept payment method with a contactless interface for cashless payments and to submit receivables generated using such payment method to SnapSwap for settlement.
2. Submission Principles and Authorisation
  1. When a payment method with a contactless interface is presented, the Contracting Party shall read the data contactlessly, that is without physical contact between the terminal and the payment method, using a terminal-reader combination initialised and approved by SnapSwap (hereinafter “terminal”) and obtain electronic authorisation from SnapSwap. For card-related transaction, Once authorisation is issued, the Contracting Party shall send all the data for the card transaction, in particular card number, expiry date, total billing amount and SnapSwap Contracting Party number, to SnapSwap electronically in the original transaction every business day via an end-of-day reconciliation.
    
    Regardless of any payment method, The Contracting Party is responsible for ensuring that the transaction data is received by SnapSwap in full, on time and in a data set suitable for electronic processing.
  2. For card-related transactions, the Contracting Party must have the cardholder authenticate the card transaction by signing their name or entering their PIN or by making correct use of a biometric method. This obligation does not apply to cases where the individual card transaction does not exceed the limit for contactless payments. This amount is set by the card associations rules applicable in the country of the payment terminal.
  3. If contactless data is sent without cardholder authentication by signature or PIN or by making correct use of a biometric method, SnapSwap obligation to pay is limited per cardholder and transaction to the transaction limit without authentication. This obligation only applies to SnapSwap where the individual card transaction submitted does not exceed the transaction limit without authentication.
  4. Authentication is required in all cases where the individual card transaction exceeds the transaction limit without authentication. If the Contracting Party does not comply with this obligation, SnapSwap is released from its obligation to pay. If the card issuer charges the card transaction back to SnapSwap because no authentication was obtained by a signature on the sales slip, correct PIN entry or correct use of a biometric method, SnapSwap is entitled to charge the card transaction back to the Contracting Party.
  5. For card-related transaction, If, for technical reasons, it is not possible to authenticate a contactless electronic authorisation request, e.g. because the chip on the card does not permit such a function or the terminal used for this transaction cannot determine the card data by contactless means, the card data must in all cases be read physically (by contact between the card and the terminal) from the chip on the card or, where necessary, from the magnetic strip, and the cardholder must authenticate payment by means of their signature or by entering their PIN using a terminal in accordance with the standards defined by SnapSwap in their conditions for the acceptance and settlement of credit and debit cards.
3. Other Contracting Party Obligations
  1. The Contracting Party must affix the acceptance mark required by the relevant payment scheme and provided by SnapSwap in a prominent position near the checkout.
  2. The Contracting Party shall use an adequate payment method reader that shows all acceptance marks under the respective payment scheme requirements for all payment method(s) the Contracting Party is entitled to accept in accordance with the service agreement with SnapSwap.
  3. The Contracting Party shall keep the contactless terminal in use for at least 12 months after it is first used.
  4. The Contracting Party’s funds which are managed by SnapSwap, and not yet settled in the merchant's own bank account, are safeguarded in an EU commercial credit institution selected by Snapswap. Those funds are not considered as deposits and not subject to deposit guarantee scheme Directive obligations.

General Terms and Conditions for Payment Facilitator Services

Object of the Contract and Terms and Conditions for Payment Acceptance

Object of the Contract

Definition

General Provisions

Submission Principles and Authorisation

Service Fees

Settlements, Lien, Provision and Increase of Collateral

Payment Instrument Requirements, Use of Third Parties by the Contracting Party

Consent regarding Data Protection, Other Reporting Obligations (PCI)

Credit Entries, Cancellations

Merchant’s Customer Complaints

Acceptance Information

Information Disclosure Obligations

Liability, Claims for Damages

Term, Termination and Payment of Damages

Compliance with Statutory and Regulatory Provisions

Waiver of Statutory Provisions

Miscellaneous

Special Terms and Conditions for the Acceptance and Settlement of Credit and Debit Cards with Physical Presentation of the Card

Card Acceptance Terms and Conditions

Authorisation at POS

Submission Principles

Reclaiming Card-related Transaction

Special Terms and Conditions for the Acceptance and Settlement of Card or Any other Payment Method

Payment Method Acceptance Terms and Conditions

Reclaiming Payment for Card-related Transactions

Additional Security Requirements regarding Online Payments

Other Contracting Party Obligations

Special Terms and Conditions for Contactless Payments

Scope

Submission Principles and Authorisation

Other Contracting Party Obligations

General Terms and Conditions
for Payment Facilitator Services