Chair Saved-Payment-Method Consent
This is a required condition of making a Booking. It is presented as a separate affirmative acceptance at checkout and is not bundled into general acceptance of the Terms.
Checkout copy
Save this payment method
Chair requires an authorized saved payment method for every Booking. You authorize Chair to save this payment method and charge it without you being present in the following situations:
- Scheduled Booking payment. Chair schedules collection based on the cancellation tier shown for the Booking: approximately 22 hours before Start Time for Flexible and approximately 70 hours before Start Time for Moderate or Strict. If a Booking is confirmed after its scheduled collection time, Chair charges it at confirmation.
- Cancellation charge. If you cancel, Chair may charge the Renter Fee and any nonrefundable portion of the Booking Subtotal under the Host’s cancellation policy. Chair will display the amount and basis before you submit the cancellation.
- Incident charge. If a Host reports eligible physical damage or extraordinary cleaning and Chair approves an amount, Chair may charge up to $200 per Booking. You will receive notice, an opportunity to respond, and an appeal period before the charge.
You must maintain an authorized payment method (a) while any Booking is scheduled or remains unpaid, and (b) after each completed Booking until the incident-report period expires without a claim or, if a timely claim is submitted, until that claim is finally resolved and every approved amount is paid. You may replace this payment method in Settings. If you remove it without providing an eligible replacement, Chair may cancel an uncollected future Booking, restrict your account, or require payment of outstanding amounts before further use. Removing a payment method does not eliminate amounts already owed.
☐ I authorize Chair to save and charge this payment method as described above.
Consent-record requirements
Record the following for every acceptance:
- User and account identifier;
- Stripe customer and payment-method identifiers;
- UTC acceptance timestamp;
- consent-text version and exact text shown;
- interface and app/web version; and
- available audit information appropriate under the Privacy Policy.
Tie consent to the payment method, not only the account. A replacement payment method requires fresh consent. Prior consent covers only the scope of the version accepted.
Each Booking record—not the reusable consent record—should store:
- the consent-record identifier relied upon;
- the cancellation-tier and policy-version snapshot;
- Booking Subtotal, Host Fee, Renter Fee, and taxes shown;
- scheduled collection time;
- any cancellation calculation and amount displayed before confirmation; and
- arrival, incident, refund, and dispute records associated with that Booking.
Log scheduled Booking, cancellation, and incident charges as distinct charge purposes.
Confirm the final language and presentation against Stripe’s then-current requirements and obtain counsel’s approval before enabling off-session charges.