Payment Device Terms of Service

Last Updated: 3/31/2025

These terms apply to the use of Payment Devices and payment device services provided by Ready (the ​“Payment Device Services”), and where applicable, will supplement and form part of Submerchant’s agreement with Ready for payment processing and related services (the ​“Agreement”). For purposes of these terms, ​“Agreement” may refer to the Submerchant Agreement or SaaS Agreement. ​“Submerchant” refers to Customer or any other designation used to identify you, our customer, in the Agreement. All capitalized terms not defined herein are as defined in the Agreement. 

The Payment Device Services may be enabled by Ready as part of Submerchant’s standard Account settings subject to regional availability and Ready’s ongoing review and approval, which may be withheld in Ready’s discretion. Submerchant may request to activate, disable, or adjust such settings at any time via the Ready Hub and/​or the relevant support channels available to Submerchant at Ready. Use of the Payment Device Services may be subject to Submerchant providing Ready with additional information and/​or performing technical updates to Submerchant’s Payment Device in accordance with the relevant documentation and usage instructions made available by Ready for such purpose. It is Submerchant’s responsibility to ensure proper use and integration of its Payment Devices in accordance with the applicable specifications, usage instructions, technical requirements, guidelines, and documentation set out in these terms and in the Ready Docs. Ready will not be responsible for disruptions to the Payment Device Services and/​or performance issues resulting from Payment Device misuse and/​or erroneous integration by Submerchant. 

Ready may update these terms from time to time to reflect the latest technical developments and updates to the Payment Device Services, or to reflect new Payment Device Services made available to Submerchant by Ready. Submerchant’s continued use of the Payment Device Services will indicate acceptance of such updated terms. To receive notification of such updates, Submerchant can subscribe via email using the link at the bottom of this page. The most up to date version of these terms will remain available to Submerchant online. Unless otherwise agreed, the following terms apply to Agreements entered into on or after 1 March 2024. 

Last update 1 March 2024

https://brand.adyen.com/api/asset/eyJjbGllbnRJZCI6bnVsbCwiaWQiOjI0Nzk0LCJ0aW1lc3RhbXAiOjE3MjEyMDMxODAsInZlcnNpb24iOjE3MjEyMDMxNjd9:adyen:hUIg7dUcVmmLtjzgcaCMG0LdrAjcH_EYjdHSIZ4DJsM/download

1. Payment Devices 

1.1 Payment Device Pricing 

Pricing for Payment Devices and accessories will be as agreed in the Agreement or as set out in Ready’s latest pricing list, unless otherwise expressly agreed between Ready and Submerchant. The latest pricing list for Payment Devices and accessories can be provided upon request. 

The sales price for each Payment Device includes the following: 

  • Payment Device hardware equipped with the relevant Software, Ready key, basic functionality testing, and secure packaging (including an anti-tamper seal), each carried out in a secure environment in accordance with applicable PCI DSS security standards; 

  • Cables and initial supplies necessary to operate the Payment Device; 

  • Registration of the Payment Device under Submerchant’s account on the Ready platform; 

  • Shipment to one designated address per store via standard courier delivery services; 

  • License to use Ready’s Payment Device Software to access the Services on the Ready platform; 

  • Support for the Payment Device Software installed on the Payment Devices; and 

  • Support for additional services provided for Payment Devices. 

The sales price for each Payment Device excludes the following: 

  • Replacement Services unless explicated stated otherwise, as defined and described in Article 2 below; 

  • First-line support for in-store personnel, as described in Clause 4.2 below; 

  • Optional value added services, as described in Article 6 below; 

  • Optional accessories (such as, base stations, and frames) and additional supplies (such as additional paper rolls for printers, and other consumables); and 

  • Federal, state, and local sales, use, excise or similar taxes or tax-like charges. 

1.2 Payment Device Ordering and Shipping 

To order Payment Devices, Submerchant must contact support, their client manager, or their sales representative. 

Ready will, where possible, strive to process smaller Payment Device orders and transfer the goods to the carrier within one business day of receiving the order. Delivery lead times communicated by Ready’s carrier are based on estimates and not guaranteed. In case of any carrier delay, Ready and Submerchant will cooperate to resolve such delay as soon as possible. 

For larger quantity orders, separate lead times will apply, depending on Payment Device model(s), fulfillment region(s), and total inventory requested. Submerchant understands that large quantity orders may require upfront commitments by Submerchant to purchase the forecasted Payment Devices with sufficient lead time to allow Ready to meet Submerchant’s expected delivery timelines. Such estimated lead times will be separately provided by Ready to Submerchant on a case-by-case basis. 

Orders for Payment Devices are invoiced to Submerchant on a monthly basis, based on the shipping date of the relevant Payment Device(s).

Ready will ship new Payment Devices directly to Submerchant’s stores unless Submerchant explicitly requests otherwise. For replacement and return orders, Ready always ships directly to stores. 

2. Payment Device Replacement Service 

2.1 Scope of the Payment Device Replacement Service 

The Payment Device Replacement Service (“Replacement Service”) entitles Submerchant to the replacement of defective Payment Devices (excluding accessories) with a refurbished Payment Device of the same model type in the following cases: 

  • As a result of a hardware defect in which the Payment Device cannot be used to submit Transactions to Ready. 

  • The Payment Device otherwise materially fails to function in accordance with the guidance and documentation provided by Ready. 

Payment Devices are no longer eligible for Replacement Services if: (i) they have reached their end-of-life (“EOL”) date, as communicated by Ready, or (ii) they are no longer PCI PTS compliant. 

2.2 Payment Device Replacement Service Pricing 

If Submerchant procures the Replacement Service, the following will apply: 

  • The Replacement Service is procured for all Payment Devices provided to Submerchant by Ready, unless otherwise agreed in the Agreement or if a specific device is not eligible for The Replacement Service. 

  • A monthly fee per Payment Device applies as agreed in the Agreement, which fee will be invoiced starting the month after shipment of the Payment Device. Such fee may be adjusted by Ready from time to time pursuant to a written agreement with Submerchant. 

2.3 Term and Termination of the Payment Device Replacement Service 

The Replacement Service will continue for the enterity of the time a Submerchant’s Payment Devices remain in their possession., unless terminated by Submerchant or Ready in accordance with this Clause 2.3.

Submerchant may terminate the Replacement Service per the end of any calendar month by returning all devices to Ready. No fees paid for the Replacement Service are rebated on termination of the Agreement or in case of loss or destruction of a Payment Device. 

Ready may decide to no longer support the Replacement Service for a specific Payment Device model by providing Submerchant with at least six (6) months’ prior notice of termination of the Replacement Service for the relevant Payment Device model. The Replacement Service will no longer be available for the relevant Payment Device model after the termination date. No Replacement Service fee will be payable by Submerchant after such termination date. 

The termination date for a Payment Device model will not be earlier than three (3) years from the date Submerchant purchased the Payment Device, unless such earlier date is expressly indicated to Submerchant before Submerchant places the order for the Payment Device. 

If the termination date for a Payment Device model is less than three (3) years from the purchase date of an individual Payment Device (without express indication), Ready agrees to compensate Submerchant (within one (1) month from the notice of the earlier EOL date) by refunding an amount equal to 50% of the total Replacement Service fees paid for that individual Payment Device on the following invoice. After notification of the earlier termination date, Submerchant may (in its sole discretion) choose to (i) continue the Replacement Service for the relevant model at the price agreed in the Agreement, or (ii) terminate the Replacement Service for the relevant model in accordance with this clause. 

2.4 Payment Device Replacement Process 

To request a replacement under the Replacement Service, Submerchant must (prior to the expiry of the term of the Replacement Service) submit a Payment Device replacement request in the Ready Hub. 

Upon receipt of the replacement request with all required details, Ready will aim to process and transfer to the carrier a replacement of the same or an equivalent model offering at least the same level of functionality within one (1) business day. For replacement requests of more than twenty (20) Payment Devices, a longer replacement process timeline may apply. 

The shipment with the replacement Payment Device will contain return instructions (for return at Ready’s expense) for the defective Payment Device. Submerchant must return the defective Payment Device in accordance with the return instructions within two weeks of receiving the replacement Payment Device. If the Payment Device is not returned within this period, Submerchant will be charged the costs of the replacement Payment Device. 

2.5 Defects and Exclusions 

Ready will examine the defective Payment Device to establish the cause of the reported defect. If the defect is confirmed and covered by the Replacement Service (as set forth in Clause 2.1 above), no additional costs will apply to Submerchant. 

Additional costs will apply if: 

  • Payment Device defect is confirmed but not covered by the Replacement Services (certain out-of-scope defects are described below), Submerchant will be charged the out-of-scope repair costs. 

  • Payment Device defect cannot be confirmed, in which case Submerchant will be charged 50% of the Payment Device’s then-current standard list price. 

Out-of-scope defects include:

  • Changes, repairs, modification or amendments to or tampering with the Payment Device by parties other than Ready (or any attempt to do so); 

  • Use of Payment Devices with improper consumables, accessories, or devices not provided and/​or prior approved by Ready; 

  • Exposure to undue external conditions (e.g., contact with water, temperature outside operating conditions, oxidation, dropping the device); 

  • Improper use and/​or use that is contrary to Ready’s operating instructions for the Payment Device; 

  • Power supply defects caused by use of Payment Device with improper voltage and/​or after improper charging; 

  • Missing parts not returned by Submerchant or damaged plastics; 

  • Issues that Submerchant could have resolved by updating or enabling updates of the Payment Device software in accordance with Article 3 below; and 

  • Failures of the Payment Device’s rechargeable battery through improper use by Submerchant. 

2.6 Hardware Warranty 

If Submerchant has purchased a terminal that does not qualify for The Replacement Services, a four (4) month warranty period will apply for Payment Devices and accessories purchased by Submerchant, starting from the shipment date of the relevant hardware. To claim under this hardware warranty, Submerchant should complete a warranty claim form and return the defective Payment Device to Ready in accordance with Ready’s instructions. Ready will investigate and repair or replace the Payment Device or accessory if the defect is covered by the hardware warranty. Ready reserves the right to replace the Payment Device with a refurbished device. Warranty claims made after the expiry of the four (4) month period and defects caused by the out-of-scope causes listed in Clause 2.5 above are excluded from this hardware warranty. 

3. Payment Device Software and Updates 

3.1 Payment Device Software 

Ready provides and maintains the Payment Device software (“Payment Device Software”) and utilizes a Terminal API that allows Submerchant’s Payment Devices to connect and interface with the Ready platform in order to submit Transactions to Ready. The Terminal API enables Payment Devices to function and connect to the Ready platform to submit Transactions via Payment Devices (“Payment Device Software”).

Ready will make patches and releases available from time to time for the Payment Device Software for all supported Payment Devices as set out in Clause 3.2 below. Ready will, as part of the Services and at no additional charge, support the use of the Payment Device Software by providing implementation support as specified in Clause 4.1 below. 

3.2 Payment Device Software Updates 

3.2.1 Distribution of Updates 

The Payment Device Software updates will be remotely and automatically loaded to the supported Payment Devices by Ready, unless otherwise agreed. As part of this automated process, a pre-release version of the Payment Device Software may be uploaded to a maximum of 2% of Submerchant’s Payment Devices. To enable updates, Submerchant should board and connect the Payment Device to the internet for at least one 24 hour period every quarter. If this requirement is not met, Ready cannot guarantee quality of service. In case Payment Device Software updates are not loaded automatically by Ready but loaded to the supported Payment Devices based on a schedule determined by Submerchant, Submerchant ensures that Payment Device Software is updated regularly at least every six (6) months. 

The Payment Device Software updates will be regularly pushed by Ready to the Payment Devices of Submerchant. Ready reserves the right to release an update to the Payment Device Software at any time in its discretion in order to repair an urgent issue with the Ready Payment Device Software (“Emergency Patch”). Examples of reasons for Ready to issue Emergency Patches include but are not limited to Software updates required to urgently address potential security concerns, PCI DSS responsibilities, updated Scheme Owner requirements, or material Service stability issues. 

Ready reserves the right to disable specific Payment Device Software from processing Transactions, deprecate specific Payment Device Software, or deprecate specific Terminal API versions from processing Transactions in its discretion. Where Ready deprecates specific Payment Device Software or Terminal API versions, Submerchant must upgrade its Payment Devices to the latest available version. 

In the case of Android Payment Devices, Ready will be responsible for ensuring that the Android Operating System (OS) installed on the Payment Device is regularly updated to reflect the latest security patches. Such updates will be promptly implemented to maintain the security and integrity of Android Payment Devices. 

3.3 Support of Payment Devices 

Ready will use all commercially reasonable efforts to support the Payment Device Software for each Payment Device sold by Ready to Submerchant for at least three (3) years subsequent to the delivery of the Payment Device to Submerchant. If Ready discontinues support of a certain type of Payment Device, Ready will, where reasonably possible, announce this at least six (6) months in advance to Submerchant. 

In certain circumstances Ready may decide to end support of the Payment Device Software for a Payment Device sold to Submerchant before the end of the three-year period (such circumstances include, but are not limited to, instances where support is discontinued by the hardware vendor, there is a security compromise which cannot be fixed on such Payment Device by an Ready Payment Device Software update, or there are new Scheme Owner requirements which cannot be fulfilled with such Payment Device). In these certain circumstances, Ready will compensate Submerchant by crediting a proportional part of the sales price to Submerchant to buy a replacement Payment Device from Ready. 

4. Payment Device Support 

4.1 Implementation Support (Ready’s Responsibility) 

Ready will support Submerchant and their stores as follows: 

  • By providing reasonable technical guidance as requested. 

  • By maintaining technical documentation. 

  • By supporting reasonable troubleshooting efforts as requested. 

4.2 First Line Support (Submerchant’s Responsibility) 

Submerchant is responsible for all first-line support activities to the end users of the Payment Devices (for example, in-store personnel) including all on-site activities (such as, for example, in-store installation, troubleshooting or replacement) with respect to the Payment Devices. For any issues concerning the Payment Devices, Submerchant’s in-store personnel should contact Submerchant’s first line support team (the ​“First Line Support”).

To enable the First Line Support to perform the below support tasks, Ready will make materials and training available to Submerchant. 

First Line support consists of: 

  • General triage and troubleshooting with respect to the Payment Device: 

  • Submerchant network issues; 

  • Hardware and accessory issues; 

  • Basic account and Payment Device configuration; and 

  • Theft, fraud, or misplacement issues. 

  • Transaction support (troubleshooting with regard to particular Transactions): 

  • Payment statuses: refunds and refusal reasons; 

  • Payment retries; and 

  • Mail Order/​Telephone Order Transactions: ability to perform payments over the phone in case of network outage. 

4.3 End-user and On-site Support (Submerchant’s Responsibility) 

Submerchant’s responsibilities also includes: 

  • Being available to accept delivery of Payment Devices at the designated address during regular business hours; 

  • In the event of damage that potentially affects the functionality or security of a Payment Device (such as a broken casing, screen, or keypad), loss, theft, or destruction of a Payment Device, informing Ready immediately, and in no event later than 24 hours after discovery of the incident. Submerchant must inform Ready by sending an email to Ready Support with the serial number of the Payment Device (if available) and identifying appropriate Submerchant contacts who will be available to follow up. In addition, as soon as possible but no later than five (5) business days after discovery of the incident, Submerchant will provide Ready with a complete description of the details of the incident and summarize all efforts undertaken or planned to investigate the incident and secure the information and Payment Devices at issue; 

  • Installing and configuring Payment Devices on site in accordance with the applicable installation and configuration instructions provided for the Payment Device. If Submerchant wants to connect Payment Devices to a cash register system, Submerchant is also responsible for such installation and connection; and 

  • If Submerchant cannot resolve the issue through their First Line Support, Ready’s Second Line Support is available to assist Submerchant as set out in Clause 4.4 below. 

4.4 Second Line Support (Ready’s Responsibility) 

Submerchant’s First Line support team can, at no additional charge, contact Ready’s second-line support helpdesk (“Second Line Support”) in case of an issue occurring in the Ready Payment Device Software which cannot be resolved by the First Line Support using the documentation and tools provided by Ready to Submerchant. In case Payment Device Software is older than six (6) months, Ready reserves the right to limit support and troubleshooting services offered until the Payment Devices are updated with Software not older than six (6) months. 

Ready’s Second Line Support is available in the English language; other languages may also be available. 

4.5 Payment Device Support Service Levels 

For Payment Device Support, the service levels below will apply. 

4.5.1 Availability and Response Time 

Service Window Response Time* 

Second Line Support

9:00-18:00 hours CET, PST and SGT on local business days 

8 local business hours 

Emergency Support** (priority 1 and 2 issues as set out below)

24 x 7 x 365 (via email to dedicated emergency email address) 

30 minutes

* Response time is the time between: 

a. The moment the issue is reported by Submerchant to Ready together with all reasonably required information to be able to investigate and address the issue; and 

b. The moment Ready has responded to a call or (in all other cases) provided its initial feedback on the issue and has started the resolution process of the issue (automated confirmation of e-mail receipt is not considered initial feedback). 

**“Emergency Support” is support for issues in Payment Device Software which block the submission of Transactions via a particular model of Payment Device generically, excluding issues affecting one individual Payment Device. 

4.5.2 Resolution Time 

Payment Device Software Issue PriorityResolution Time Target* 

Priority 1: Issue blocking acceptance of payments for all Payment Methods via all (properly updated) Payment Devices of a particular model

4 hours after ticket is logged with Ready 

Priority 2: Issue blocking use of an individual Payment Method via all (properly updated) Payment Devices of a particular model (payment via other Payment Methods still possible)

1 business day 

Priority 3: All other issues in Payment Device Software materially hindering the acceptance of payments

Reasonable efforts to resolve in next update 

*The ​“Resolution Time Target” is defined as when Ready will make an update available for the Payment Device Software (or a recommended change in the setting of the same) that resolves the issue or provides a work-around for the same. This Resolution Time Target only applies to issues originating in the Payment Device Software and caused by a previous update issued by Ready for such Payment Device Software. Excluded from the Resolution Time Target are issues caused or originating in: software embedded by the hardware manufacturer of the Payment Device, systems or software of Scheme Owners, third party cash register, user error, not installing updates or not following installation and usage instructions as provided by Ready. 

5. Submerchant Payment Device Responsibilities 

To access and use the Services of Ready when operating and using the Payment Device, Submerchant must: 

  • Ensure that the Payment Device is kept and operated in a suitable environment, used only for the Transactions for which it is designed, and operated in a proper manner; 

  • Make no alteration to the Payment Device and not remove any component(s) from the Payment Device without the prior written consent of Ready; 

  • Permit Ready or its duly authorized representative to inspect the Payment Device at all reasonable times, subject to reasonable notice and during reasonable working hours at the relevant location; 

  • Not allow any third party to use the Payment Device or submit Transactions via the Payment Device on behalf of a third party without the prior written consent of Ready. The Payment Device may only be used by Submerchant to submit Transactions to Ready in its own name and for the business it registered for when entering into Agreement; 

  • Comply with the relevant usage manuals for the Payment Devices and the Ready POS Services in general as published on Ready Docs, including in particular: 

  • The Payment Device manual, 

  • The Network Requirements manual for Payment Devices to ensure IP connectivity for the Payment Devices to enable their proper functioning, and 

  • The Payment Security manual which provides guidelines to assist Submerchant in the safe and secure use of the Payment Device and POS Services; 

  • Comply with PCI DSS security requirements when handling and using Payment Devices and, upon Ready’s request, fill out Self-Assessment Questionnaires (‘SAQs’) prescribed by the Scheme Owners under applicable PCI DSS regulations to confirm such compliance; and 

  • Follow the Scheme Rules in operating the Payment Devices to submit Transactions. 

6. Additional Services for Use of Payment Devices 

The following additional services are offered by Ready to Submerchant in relation to the use of Payment Devices. Such additional services will either be enabled by default (at no additional cost) or at the election of Submerchant as priced in the Agreement. 

6.1 Cellular Connection and Data 

As a default service, for specific models of Payment Devices, Ready will supply the SIM card together with the Payment Device and will remotely activate the SIM card. Cellular traffic for Transaction processing and actions such as configuration updates are included in pricing outlined in Agreement. For Android Payment Devices, Submerchant may not cellular data for any non-Ready applications. Ready reserves the right to throttle the connection speed and/​or block cellular traffic if cellular data is used for any non-Ready application. Ready will not be liable for any additional costs as a result of excessive data usage. 

Payment Devices can only be used with SIM cards that are supplied by Ready. Upon termination of Agreement, all SIM cards will be deactivated and must be returned by Submerchant together with the Payment Devices as set out in Agreement. 

Ready reserves the right to enable or disable the SIM card in Payment Devices. 

6.2 Offline Payments 

Payment Devices will by default process all Transactions online only. In case of connectivity issues to the Scheme Owner or Card Issuer, the Transaction will be declined. Submerchant may choose to configure Payment Devices to also accept Transactions offline as follows: 

  • Online preferred”, if supported by the Card configuration and only in case of connectivity issues towards the Scheme Owner and/​or Card Issuer, authorize Transactions offline below a certain Transaction amount limit set by Submerchant; 

  • Offline preferred”, if supported by the Card configuration, authorizes Transactions offline below a certain Transaction amount limit set by Submerchant without attempting to go online; and 

  • Store and Forward”, ignoring the Card configuration and only in case of connectivity issues towards the Scheme Owner and/​or Card Issuer, force offline Authorisation of Transactions below a certain Transaction amount limit set by Submerchant (‘Forced authorisation threshold’).

Submerchant agrees that by enabling offline payments, Submerchant’s integration may approve Transactions before Shopper funds are received, making it possible that Submerchant will not receive the funds for the goods and/​or services purchased by the Shopper. By enabling offline payments, Submerchant acknowledges that there is a higher risk that card fraud goes undetected. For the options above, any Transaction for an amount exceeding the relevant limit set by Submerchant will always require online processing only or will be declined in case of connectivity issues. Transactions authorized offline will be stored on the Payment Device and forwarded to the Scheme Owner and Card Issuer when the Payment Device is online. 

Transactions that were authorized offline may fail to be Captured, which could result in no Settlement to Submerchant. However, some Scheme Owners may offer a limited Capture guarantee and fraud Chargeback protection for Transactions authorized offline in line with the configuration of the Card up to a certain Transaction amount. Ready does not accept any responsibility for any failed Captures or the defense of Chargebacks and/​or disputes in respect of Transactions authorized offline. If Submerchant chooses to authorize Transactions offline, Submerchant accepts full liability for, and shall indemnify and hold Ready harmless from, any (third party) claims in respect of the associated risks regarding Chargebacks, disputes and Capture/​Settlement failures. 

6.6 Manual Keyed Entry 

Submerchant may choose to enable Manual Keyed Entry (“MKE”) on the Payment Devices in accordance with guidelines provided on Ready Docs. In such a case, Submerchant accepts full liability and shall indemnify and hold Ready harmless from any (third party) claims in respect of Chargebacks and fraud regarding Transactions executed through the use of MKE. Ready reserves its right to set up and/​or increase Submerchant’s MPL Reserve Level as a result of the number of MKE Transactions. 

6.7 Mail Order/​Telephone Order 

Subject to confirmation by Ready, Submerchant may choose to enable activation of Mail Order/​Telephone Order (“MO/TO”) Transactions on the Payment Device whereby payments can be processed remotely by keying in the Card details on the Payment Device while the Card is not present. Submerchant also has the option to enable MO/TO Refunds via the Payment Device. In both scenarios Submerchant accepts full liability and shall indemnify and hold Ready harmless from any (third-party) claims in respect of Chargebacks and fraud regarding Transactions executed through the use of MO/TO. Ready reserves the right to set up or increase Submerchant’s MPL Reserve Level as a result of the number of MO/TO Transactions. Submerchant represents and warrants that Submerchant will comply with the Scheme Rules and PCI DSS requirements applicable to MO/TO Transactions. 

6.12 Gift Cards and Other Stored Value Cards 

Submerchant may elect to use the Terminal API to process Transactions using stored value cards, including gift cards and mall cards. Stored value cards are payment cards with a monetary value stored on the card itself instead of in a bank account. In order to enable this feature, Submerchant must have a direct contract with the card provider and comply with all regulatory and tax requirements around stored value cards in the country where the card was issued (such as expiry period, Transaction limit, and cross-border Transaction capability). 

Submerchant assumes responsibility for the balance on the stored value card, as well as for refunding the amount or issuing new stored value cards to shoppers for returned items. Because many stored value cards require a PIN as Card Verification Method (CVM), Submerchants should make sure that the PIN is securely provided to customers at the point of purchase. 

6.16 Drop Shipping 

Ready will ship Payment Device directly to Submerchant stores when terminals are ordered or when processing a replacement as part of the Payment Device Replacement Service outlined is Clause 2. 

6.16.1 Drop Shipping Conditions 

Submerchant agrees that Drop Shipping Services will be subject to the Payment Device ordering and shipping process set out in Clause 2.2 above. Payment Devices will be delivered on a Delivered Duty Paid (“DDP”) destination basis to the relevant addresses provided by Submerchant to Ready. Submerchant will provide Ready with accurate addresses for all Submerchant Affiliates at the time of ordering Payment Devices and understands that Ready cannot change the shipping address for orders once the Payment Devices are in transit. Submerchant accepts responsibility resulting from any incorrect address provided to Ready and agrees to assume any additional costs and responsibility for contacting the relevant carrier and to recover and/​or reroute the shipment to its correct destination. Submerchant will purchase the Payment Devices directly from Ready and as such, any risk of loss and responsibility will pass from Ready to Submerchant and from Submerchant to Submerchant Affiliates upon delivery to Submerchant Affiliates. For the avoidance of doubt, Ready will not be subject to additional liability or responsibility for the Payment Devices once delivered to Submerchant Affiliates including any additional costs resulting from a Submerchant Affiliate’s inability to accept the Payment Devices at the time of delivery. Ready reserves the right to use a local Ready entity as the selling party. 

6.16.2 Pricing, Invoicing and Taxes 

Pricing for the Drop Shipping Services are priced in addition to the Ready Services and will be included in the Payment Devices invoice. 

For Drop Shipping Services to countries outside the European Union, the supply of Payment Devices by Ready to Submerchant may be subject to VAT/GST/JCT or other indirect taxes (hereinafter, referred to as VAT). Ready invoices the VAT due on the purchase price of Payment Devices in accordance with the applicable VAT legislation. If Ready has a local entity in the ship-to-country, Ready will endeavor to use the local Ready entity as the selling party and therefore invoice the local applicable VAT rate, based on the ship-to location provided by Submerchant.