1. Stripe Connect requirement for online card payments and payouts
Stripe Connect onboarding and payout readiness are required before a provider location can use online card payments and payout flows through FoundBookings. Providers must accept FoundBookings Stripe Connect Terms and applicable Stripe terms, including Stripe's Connected Account Agreement where applicable, before Stripe onboarding can begin.
Stripe services are provided by Stripe, not FoundBookings. Stripe terms govern Stripe's payment, connected-account, compliance, risk, dispute, account, and payout services. Providers remain responsible for their connected-account responsibilities under Stripe's terms, and FoundBookings terms govern the provider's relationship with the FoundBookings platform.
2. Onboarding, KYC, and account information
Providers are responsible for giving accurate, complete, and current Stripe onboarding, know-your-customer, ownership, business, tax, bank, identity, and compliance information.
FoundBookings may create or manage onboarding links, receive account status, capabilities, requirements, payout-readiness signals, and related identifiers from Stripe, and show relevant status information in the dashboard.
Stripe may restrict, reject, suspend, hold, review, delay, or close accounts, capabilities, charges, transfers, or payouts for reasons determined by Stripe or applicable law.
3. Location-level payout readiness and paid booking restrictions
FoundBookings is designed around location-level payout readiness. Each provider location that accepts online card payments must have the relevant payout/account readiness configured.
FoundBookings may suspend or prevent paid bookings, payment collection, checkout confirmation, or payout-related actions where payout readiness is incomplete, failed, restricted, under review, or no longer supported.
4. Provider responsibility for services, refunds, and customer obligations
Providers remain responsible for the services, customer communications, provider policies, refunds, cancellations, no-shows, consumer obligations, taxes, and legal duties connected with their own business.
Using Stripe Connect or FoundBookings payment tooling does not make FoundBookings responsible for provider service delivery or provider-controlled customer disputes.
5. Fees, transfers, payouts, reversals, refunds, disputes, and chargebacks
Stripe fees, platform fees, transfer timing, payout timing, refund handling, disputes, chargebacks, reversals, negative balances, and account reserves may apply. These beta terms do not invent fee amounts; any production fees should be disclosed in plan, checkout, or commercial documentation before use.
FoundBookings may create transfers, reverse transfers, support refunds, record payment status, and use payment identifiers where required for checkout operation, refund handling, fraud prevention, dispute support, reconciliation, or platform integrity.
FoundBookings does not guarantee payout timing. Stripe, banks, card networks, compliance reviews, disputes, refunds, account status, or technical issues may delay or prevent payouts.
6. Card data, Stripe data sharing, and test/live mode
Card entry is handled by Stripe or Stripe-supported payment components. FoundBookings does not store full card numbers. FoundBookings may store payment-provider identifiers, payment status, refund status, transfer references, and saved-payment-method identifiers needed to operate the platform.
FoundBookings may share information with Stripe and receive information from Stripe where needed for onboarding, payment processing, fraud prevention, compliance, refunds, disputes, payouts, transfers, account status, or support.
Test-mode payments, test accounts, or sandbox activity are not live payment commitments. Production/live-mode behavior may be updated before launch after review with qualified counsel and payment operations owners.