The short version
This summary is for convenience only and does not replace the full Payment Terms below.
- The host is the seller; Q2GO is not. You pay the host for your stay. Q2GO is a marketplace intermediary that only facilitates the payment; the host is the seller and the Seller of Record.
- How your booking money moves. Your card payment is processed by our payment provider (Stripe) through Q2GO's platform account and, at the moment of payment, the host's share is transferred to the host's account with the provider; Q2GO's service fee and any tax Q2GO must collect stay with Q2GO. We are not a bank, an escrow or trust account, or a payment institution (Payment Rail Disclosure).
- You pay in the listing's currency. You are charged the amounts shown at checkout, in the currency of the listing, with no currency conversion applied at the moment of charge.
- Confirmation depends on the listing mode and payment flow. Instant Book and Host Approval Required are distinct modes; saving a card for a future charge is a separate payment flow (Section 8).
- When your card is charged. Unless the host has chosen to charge at booking, you save a card at checkout and are not charged then: the card is charged when the Booking's free-cancellation period ends, and about 48 hours before that (or shortly after booking, if less than 48 hours remain) the amount is first authorised (held) on it. Cancel in time and you are not charged, and any hold is released. A stay with no free-cancellation period left is charged at checkout (Sections 6 and 7).
- Hosts pay our fee, guests do not. Guests pay only the booking price. Q2GO's 10% service fee (capped monthly per host account) is deducted from the host's share of each booking payment.
- Refunds and chargebacks come from the host's side. Refunds are funded from the host's side of the transaction, and a refund after a payout can leave the host owing money.
1. Scope and who these terms apply to
1.1 These Payment Terms ("Payment Terms") govern how payments for Bookings are handled on the Q2GO Platform operated by Q2GO LTD ("Q2GO", "we", "us", or "our"), a private limited company incorporated in England and Wales. They apply to both Guests (who pay for a Booking) and Hosts (who are paid for a Booking).
1.2 These Payment Terms form part of, and are incorporated into, the Terms of Service. Capitalised terms used but not defined here have the meaning given in the Terms of Service (Section 2). Where these Payment Terms and the Terms of Service differ on a payment topic, these Payment Terms control for that topic.
1.3 The Platform is offered to users in the United Kingdom and the European Economic Area (EU/EEA).
2. Definitions
The following terms have the meanings given below wherever they appear in these Payment Terms.
- "Payment Provider" — a third-party payment service through which Booking payments are processed and the Host's share is transferred and paid out (for card payments: Stripe, through its connected-account service).
- "Payout Account" — the account a Host holds with a Payment Provider into which Booking funds are credited.
- "Connected-Account Model" — the destination-charge arrangement: a Booking payment is charged on Q2GO's platform account with the Host as settlement merchant, and the Host's share is transferred at once to the Host's Payout Account with the Payment Provider.
- "Off-Session Charge" — an automatic charge of a payment method the Guest has chosen to save, taken at a later scheduled time without the Guest re-entering payment details.
- "Service Fee" — the fee Q2GO charges Hosts under the Service Fee Policy, deducted from the Host's share of Booking payments.
- "Policy Snapshot" — the cancellation and refund terms recorded with a Booking at the time it is made (see the Cancellation & Refund Policy).
3. Our role; the Host as seller and Seller of Record
3.1 Q2GO is a marketplace intermediary. For booking payments, the Host is the seller and the Seller of Record, responsible for fulfilment, guest service, refunds, invoicing for the stay, and taxes on the stay. Q2GO is a technology platform that facilitates the payment; Q2GO is not the seller, the merchant of record for the stay, the holder of booking funds, or the funder of refunds.
3.2 Card payments are processed by the Payment Provider as destination charges: one charge on Q2GO's platform account with the Host as settlement merchant, and an immediate transfer of the Host's share to the Host's Payout Account; Q2GO's Service Fee and any tax Q2GO must collect remain with Q2GO. Q2GO does not hold booking funds as its own and is not a bank, escrow provider, trust account, or payment institution. See the Payment Rail Disclosure.
4. Processing by our payment providers
4.1 Booking payments are processed by our third-party Payment Providers under their own terms, which also apply to you. Card and payment-credential data is handled by the Payment Provider; Q2GO does not store full card numbers or card security codes (CVV).
4.2 Each Booking payment is processed under the Connected-Account Model: the Host's share is transferred to the Host's Payout Account at the moment of payment, less Q2GO's Service Fee and any tax Q2GO must collect and remit; the Payment Provider's processing fee on that payment, which the Payment Provider charges to Q2GO, is then recovered from the Host's share.
4.3 A Host must complete the Payment Provider's identity and "know your customer" (KYC) checks and keep its Payout Account in good standing before it can receive Booking payments or payouts. If the Host's Payout Account is not ready — for example, charges or payouts are not enabled, or there are outstanding requirements — the payment or payout will not proceed.
5. Where booking funds are held
5.1 The Host's share is held in the Host's Payout Account balance with the Payment Provider until it is paid out; Q2GO's Service Fee and any tax Q2GO collects are held in Q2GO's account with the Payment Provider. Q2GO is not a bank, an escrow provider, a trust account, or a payment institution. Refunds and disputes are first debited by the Payment Provider to Q2GO's platform account and recovered from the Host's share (sections 12–13); where an amount cannot be recovered from the Host, Q2GO may bear it towards the Payment Provider.
5.2 A delay between payment and the release of a Host payout is a matter of payout timing and Payment Provider settlement, not custody by Q2GO. See the Host Payout Policy and the Payment Rail / No-Escrow Disclosure.
6. What you pay and in what currency
6.1 You are charged according to the payment schedule shown at checkout, in the currency of the listing, with no currency conversion applied at the moment of charge. Before you confirm a Booking, you are responsible for reviewing the listing, the dates, the total price, any taxes or fees shown, and the cancellation policy.
6.2 When you are charged. The timing is set by the listing, not chosen at checkout, and the checkout shows it before you confirm: (a) by default, you save a payment method at checkout and are not charged then; it is charged automatically when the Booking's free-cancellation period ends; (b) if the Host has chosen to charge at booking, or no free-cancellation period remains (for example, a non-refundable rate), you are charged at checkout. A charge is never taken earlier than 85 days before check-in (Cancellation & Refund Policy §3.2A); for a Booking made further ahead the payment method is saved and charged then (see Section 7).
7. Authorisation, capture, and saved-card later charge
7.1 By completing checkout, you authorise the charges shown for that Booking. Confirmation depends on the listing approval mode and payment flow in Section 8; authorising a charge does not replace required Host approval.
7.2 Saved payment method — later charge. Where a Booking is charged later (Section 6.2(a)), you authorise the saved payment method to be charged off-session, without re-entering your details, for the Booking amount, when the free-cancellation period ends. You also authorise the full amount to be authorised (held) on the payment method about 48 hours before the free-cancellation period ends (or shortly after booking, if less than 48 hours remain); if the issuer limits how long the hold remains valid, it may be released and placed again before it expires. The system is designed to prevent duplicate charges; if a duplicate charge is ever taken in error, it will be corrected and refunded. The hold is captured when the free-cancellation period ends, or released — with no charge — if you cancel in time. If an authorisation or charge fails, you will be notified by email and in the app and may complete your bank's authentication or use another payment method; failed attempts may be retried while the free-cancellation period is open. If the charge fails when it ends, you have 24 hours from that failure (never beyond the start of the check-in day in the property's local time) to complete payment; until then the Booking is pending payment, and it is cancelled if payment is not completed.
7.3 What is stored. The payment credentials are stored by the Payment Provider; Q2GO does not store your full card number or CVV.
7.4 How to withdraw your authorisation. You may withdraw your authorisation for a future Off-Session Charge only where the Platform permits removal of the saved payment method and no open future Booking still depends on it. Removing a saved method does not, by itself, cancel a Booking. If a scheduled charge fails because no valid payment method is available, the Booking may be marked as payment failed and may be cancelled unless updated within the retry window; cancellation and any refund are governed by the Cancellation & Refund Policy and the Policy Snapshot for that Booking.
7.5 Cancellation charges. If a Booking is cancelled after its free-cancellation period has ended but before the Booking amount was charged — by you, or by us because the payment could not be completed in the time given to you (7.2) — the amount that the Booking's cancellation policy does not refund (the "cancellation charge") is due. You authorise us to charge it, once, to the payment method saved for the Booking. We do not charge it if the cancellation was caused by an error on our side or by the Host, if the Booking was never confirmed, or, for a cancellation for non-payment, if we did not notify you of the failed payment by email. If the charge fails, the amount remains due and we may contact you about it; we do not retry it automatically.
7.6 Your authorisation is explicit and recorded. The authorisations in 7.1, 7.2 and 7.5 are given when you confirm the Booking and are recorded with it — the exact version of these Payment Terms and of the cancellation policy you accepted, the time, and how you accepted. We rely only on the authorisations in the version you accepted for that Booking. If we materially change what you authorise, we will ask for your acceptance again before relying on the change; a later version never extends an earlier authorisation.
8. Confirmation, holds, and failed payments
8.1 Listing-specific booking modes. Each listing uses Instant Book or Host Approval Required (Request to Book). For Instant Book, confirmation follows the applicable payment or authorisation flow. For Request to Book, submission creates a pending request; the Host must explicitly approve, and the applicable payment requirements must also be satisfied before confirmation. Payment alone does not approve a host-approval request. A listing may be configured to require approval for its first specified number of bookings before switching to Instant Book. The mode is determined by the listing setting, not chosen randomly. Where a Booking is charged later, saving a payment method is not itself a charge of the stay amount: after any required Host approval and successful card setup, the booking may be confirmed pending its scheduled charge. The payment schedule and booking status are shown separately. See the Payment Terms.
8.2 Holds expire. A Booking that is awaiting payment expires after about 30 minutes, processed by scheduled cleanup, after which the held dates are released and, where a payment authorisation was created, it is cancelled.
8.3 Failed payments. If a payment fails, the Booking may require a further payment action and will not be confirmed until payment succeeds. Where a payment authorisation has not yet been captured, cancelling the Booking releases the hold and no money moves.
9. Host payouts
9.1 Host payouts are released on the timing set out in the Host Payout Policy — generally a defined period after check-in or service start — and are subject to eligibility checks and to holds (for example, a pending refund or an open dispute). This is a payout-release timing rule: the Host's share stays in the Host's Payout Account balance meanwhile, and it is not an escrow or trust arrangement.
9.2 A payout is released only where the Booking is eligible — for example, the payment is in a payable state, there is no open refund, hold, or dispute, the Host's Payout Account is present and ready, the release time has passed, and the stay has begun. The detail is set out in the Host Payout Policy.
10. Taxes on the stay
10.1 Stay pricing and local taxes. The Host sets the stay price and remains the Seller of Record. Q2GO may estimate or calculate tourist/local tax lines only for a supported, approved jurisdiction rule and an enabled use case. The booking breakdown distinguishes estimates, amounts charged online and passed to the Host, and amounts payable at the property. A calculation or pass-through does not mean Q2GO files or remits tax. Platform collection is separately gated and is not globally enabled; it must be explicitly enabled for the approved jurisdiction/use case. The current calculation and collection capability is not a promise of automated remittance to an authority. Unless a specific supported arrangement expressly states otherwise, the Host remains responsible for verifying, reporting and remitting the applicable stay taxes.
10.2 Tax on Q2GO's own Service Fee is addressed in Section 11 and the Service Fee Policy.
11. Service Fee — host-side, deducted from the payment
11.1 Guests pay no Q2GO fee. Q2GO adds no fee to the amount you pay for a Booking.
11.2 Q2GO's charge to Hosts is the Service Fee under the Service Fee Policy, deducted from the Host's share of each Booking payment and capped monthly per host account. Its rate, caps, currency, VAT and refund treatment are set out in that Policy.
12. Refunds
12.1 Refunds are processed back through the same Payment Provider, under the Cancellation & Refund Policy and the Policy Snapshot recorded with the Booking. The Payment Provider debits the refund to Q2GO's platform account, and Q2GO recovers the Host's share by reversing the transfer to the Host; the Host bears refunds of its share. Where an amount cannot be recovered from the Host, Q2GO may bear it towards the Payment Provider.
12.2 Refund after a payout. Because a Host is generally paid after check-in, refunds may be reversed from the Host connected account and may create a negative connected-account balance; Q2GO may remain exposed to payment-provider recovery risk. The detail is set out in the Host Payout Policy and the Host / Supplier Terms.
13. Chargebacks, reversals, and negative balance (Hosts)
13.1 Where a payment is reversed, refunded, or charged back, or where a Host's Payout Account balance becomes negative, the Host remains responsible to Q2GO and to the Payment Provider for the amount concerned, and Q2GO may recover that amount from the Host, including by deducting it from future payouts, collection activity, legal claims, or other lawful means.
13.2 When a card dispute or chargeback is opened, the affected payout may be frozen, the dispute is recorded with its evidence deadline, and transfers may be reversed. The Host remains responsible for amounts reversed or charged back.
14. Payment methods and provider roles
14.1 Booking payments are processed by our third-party Payment Providers, each acting in its own role under its own terms. A payment method is offered only where it can work under the Connected-Account Model; otherwise it is not offered for live Bookings.
14.2 Q2GO chooses Payment Providers with reasonable care but is not responsible for a Payment Provider's own acts, omissions, or terms beyond what these Payment Terms and applicable law provide. Q2GO does not guarantee payment, payout, or refund timing beyond what these policies and applicable law require, as these depend on the Payment Provider and the banks involved.
15. Your consumer rights, governing law, and disputes
15.1 If you are a consumer, you have mandatory rights under the consumer law of your country of residence, and nothing in these Payment Terms limits those rights.
15.2 The limitation of liability, governing law, and dispute-resolution provisions of the Terms of Service (Sections 15 and 20) apply to these Payment Terms. These Payment Terms, and any dispute arising out of or in connection with them, are governed by the laws of England and Wales, and the courts of England and Wales have jurisdiction, without affecting the mandatory consumer-law protections of your country of residence.
16. Changes to these Payment Terms
16.1 We may update these Payment Terms from time to time. Where we make a material change, we will give notice and, where the law requires, a reasonable period before the change takes effect for existing users. The version number and "effective" date show the current version, and we keep prior versions and a short note of what changed in the version archive in the Legal Centre.
17. Contact
17.1 You can contact us about these Payment Terms, or about a payment or billing question, at legal@q2go.net. Q2GO LTD is a private limited company incorporated in England and Wales; its company number is 17332954 and its registered office is 128 City Road, London, United Kingdom, EC1V 2NX.
18. Language
18.1 These Payment Terms are published in English and in Hebrew. The English version is the controlling version; the Hebrew version is provided so that Hebrew-speaking users can understand the Payment Terms, and in the event of any conflict the English version prevails.

