Payment Conditions — Hostnest

Payment Conditions

Last updated: August 22, 2026

These Payment Conditions describe online payment operation through Hostnest and supplement the Terms of Service and Economic Conditions. They apply to hospitality businesses (Properties) and, where relevant, to guests paying deposits through the product workflow.

The platform provider is Sprint di Linguari Stefano, Largo Piave 11, 28066 Galliate (NO), Italy, VAT ID 08001990962, info@hostnest.it.

1. Stripe Connect

Online payments enabled in Hostnest use Stripe Connect. The Property must complete onboarding of a linked Stripe account (Standard account in the current implementation), keep it verified, and meet Stripe requirements for accepting payments (charges enabled).

Stripe operates as an independent payment service provider. Deposit funds are processed on the Property's linked account according to Stripe payout timing and rules. Hostnest does not hold guest funds as a payment institution.

The Property accepts Stripe terms applicable to its Connect account and remains responsible for KYC verification, documentation, and anti-money laundering compliance required by Stripe.

2. Online payment type (V1)

In the current Hostnest product version, only deposit payment associated with a booking is supported online, where configured by the Property with a deposit amount greater than zero.

Not included in V1:

• online payment of the remaining balance through Hostnest;
• a second online payment after the deposit;
• integrated or Hostnest-recorded bank transfer as a payment method;
• storage of full card details on Hostnest systems;
• recurring payment or automatic charge after checkout without a new session.

Any balance, on-property payments, cash, non-integrated POS, or offline collection remain exclusively managed by the Property outside Hostnest V1 flow.

Hostnest may in future enable additional online payment methods (balance, tracked bank transfer, digital wallets) where activated and subject to updated Payment Conditions.

3. Hosted checkout and legal acceptance

Payment takes place through Stripe Checkout (Stripe-hosted payment page). Before redirect, where implemented, the guest accepts these Payment Conditions in the customer area workflow.

The guest is redirected to Stripe's secure checkout to enter payment details and complete the transaction. Hostnest calculates amount and commission server-side based on the Payment record linked to the booking; amount cannot be determined or altered from the customer's browser.

After payment, the guest is redirected to the public customer area linked to the quote/booking. Displayed status may show processing until webhook confirmation.

4. No card storage

Hostnest does not store full card numbers, CVV, or equivalent data. Such information is processed directly by Stripe under its PCI-DSS standards. Hostnest retains technical transaction identifiers (checkout session, payment intent, payment status) necessary for operations and reporting.

5. Balance and reporting

Remaining booking balance, where provided under the Property's terms, is calculated and shown in the backoffice as the difference between agreed total and paid deposit, according to product logic. Balance does not automatically trigger an online payment request in V1.

The Property sees paid amount, Hostnest commission, and, where populated by Stripe, network fees and net amount in the backoffice.

Hostnest does not replace the Property's official accounting or tax receipts to guests unless future features are expressly described.

6. Hostnest commission

Each online payment processed through Hostnest may incur a variable management commission, collected through Stripe application fee where technically provided. Applicable values are stated in Economic Conditions and specific commercial documentation — no fixed percentages in this document.

The Hostnest commission is not returned upon refund, unless otherwise agreed in writing or required by mandatory law.

7. Refunds

In V1 Hostnest does not expose a refund interface in the backoffice. Refunds must be performed by the Property through the Stripe Dashboard (or equivalent Stripe tools) on the linked account.

Hostnest synchronizes payment status through Stripe webhooks (refund events). Where a full refund is recorded, payment status may become refunded in the Hostnest system.

The booking is not automatically cancelled following a refund: operational booking status remains managed by the Property, unless future product changes are expressly communicated.

Partial refunds are not operationally managed in V1 beyond what is technically reflected by supported webhook events; unsupported behavior may fail to update internal status correctly.

8. Chargebacks and disputes

Chargebacks or guest disputes are handled by Stripe under its procedures. The Property is responsible for providing Stripe with requested documentation and managing the relationship with the guest.

Hostnest may record status updates in the system from webhooks where technically supported, but does not replace commercial or legal dispute handling.

Hostnest does not guarantee favorable chargeback outcomes or recovery of refunded or reversed amounts. Any Stripe fees or chargeback-related penalties remain borne by the Property under Stripe terms.

9. Webhooks and state synchronization

Hostnest receives Stripe webhook events with mandatory signature verification. Supported events include, among others, checkout session completion or expiration, charge refund, and Connect account update. Duplicate events are handled idempotently.

Where Stripe account and Property mismatch, Hostnest avoids unauthorized economic mutations. The Property is responsible for maintaining consistent Stripe configuration and monitoring anomalies shown in the backoffice.

10. Zero deposit

If the Property configures a zero deposit, the booking may be confirmed without creating an online payment. No Hostnest management commission applies to payment in that case, because no payment occurs.

11. Idempotency and state consistency

The payment flow is designed to avoid duplication: a booking generates an associated Payment record; checkout reuses open sessions or creates subsequent versions according to application logic. The Property should avoid manually requesting duplicate deposit payments outside the intended workflow.

If customer area and backoffice diverge, system state after webhook processing prevails, except where support intervenes for documented anomalies.

12. Property obligations

The Property is responsible for configuring correct amounts, clearly communicating deposit and balance terms to guests, and handling disputes, chargebacks, and refunds under its own policy and applicable law. Hostnest provides technical tools but does not replace the Property's commercial decisions on refunds and cancellations.

The Property warrants legal authorization to accept payments for proposed stays and compliance with tax, anti-money laundering, and consumer protection law where applicable.

13. Guest obligations (where relevant)

A guest proceeding to payment declares having read these Payment Conditions and Property conditions made available in the quote or customer area. The guest is responsible for correctness of payment data entered on Stripe Checkout.

14. Limitation of liability

Hostnest is not liable for Stripe outages, card issuer declines, chargebacks, payout delays, or Stripe decisions on onboarding or payouts, except in cases of Hostnest's wilful misconduct or gross negligence within limits permitted by law and the Terms of Service.

15. Changes

Hostnest may update these Payment Conditions for product evolution, Stripe requirements, or regulatory changes. Updated versions will be published with revision date. Continued use after effective date may constitute acceptance where permitted by law.