Stripe Connect

Stripe Connect powers paid product checkout, booking deposits, final booking payments, invoices, refunds, payouts, and connected-account reporting.

Where To Configure

Use:

• Payments for the Stripe account and money dashboard.
• Settings > Checkout and Tax for checkout behavior.
• Products for product pricing, inventory, tax, and shipping.
• Scheduling for booking deposits, payment timing, and invoice behavior.

Start with Payments when the account itself is not ready, then move outward to the customer path. A healthy Stripe account does not guarantee a purchasable product, a payable booking, a valid tax configuration, or a verified wallet domain.

Console Setup Preview

Use this preview to confirm the console is showing the right payment readiness state before exposing paid customer actions.

If one row is not ready, disable only that customer path where possible. Keep content, contact, or unpaid booking flows live when they are verified.

Connection Flow

1. Open Payments.
2. Start or resume Stripe onboarding.
3. Complete account requirements in Stripe.
4. Return to the console and confirm account status.
5. Review currency, payouts, and business profile information.
6. Test at least one paid workflow before launch.

Record the connected account state after onboarding: requirements, payout posture, expected charge flow, refund owner, and whether product checkout, booking deposits, final payments, invoices, or wallets are enabled. That evidence matters more than the fact that the connect button completed.

Payment Surfaces

Product checkout

Cart and shop orders

Booking deposit checkout

Collect deposit before confirming a booking

Booking final checkout

Collect balance after work or near appointment time

Hosted invoice

Send Stripe invoice link

Embedded checkout

Keep payment experience inside the site when configured

Manual payment

Record offline or out-of-band payment

Refund or credit note

Return money or adjust invoice state

Connected Account Requirements

If payments are unavailable, check:

• Account onboarding status.
• Missing Stripe requirements.
• Business profile details.
• Currency.
• Payout status.
• Payment method support.
• Merchant or wallet domain requirements.

The console should show account or payment readiness before a public checkout path is enabled.

Product Checkout Checklist

• Product is active and visible.
• Price is valid.
• Inventory is sufficient.
• Tax settings are intentional.
• Shipping settings are complete when physical fulfillment is required.
• Stripe is connected.
• Checkout success and return pages work.
• Order appears in Sales and customer portal.

Booking Payment Checklist

• Service is bookable.
• Deposit or payment timing is configured.
• Public booking confirmation page works.
• Pay link or embedded payment action is visible when expected.
• Booking payment state updates in the console.
• Customer receives the right notification.
• Refund, cancellation, and reschedule policies are understood.

Fees And Transfers

The platform may calculate application fees and route money through the connected account. Operators should verify the expected net, payout cadence, and invoice display with the workspace’s financial owner.

Before launch, compare one representative product order and one representative paid booking against the financial owner’s expectations. Confirm gross amount, tax, shipping, discount, application fee, refund owner, payout destination, and what appears on the customer receipt.

Testing Guidance

Do not submit real live-card payments during local QA unless the workspace explicitly intends that charge. For local test workflows, use the seeded test workspace and test-safe webhook tools when available.

For production launch validation, agree on the payment boundary before testing. Some workspaces stop at the final payment screen, while others approve a small live charge followed by an immediate refund; either way, record the order or booking ID and confirm the console state after the test.

Troubleshooting