How the Stripe Connect model works here

Payments are created as destination charges with an application fee: the charge is processed on the platform account, the seller's share is transferred to their connected account, and Stripe pays the seller on their payout schedule. The platform pays Stripe's processing fee out of its application fee and is responsible for refunds, disputes and negative balances — which is why those flows are built in, not bolted on.

What sellers see

• Provider-hosted onboarding with the capability and requirement status mirrored in the dashboard.
• Fee schedule shown before connecting a provider and recorded on every transaction.
• Payout history with the provider's real states and estimated arrival dates.

What we deliberately do not do

• No custodial wallet and no manual withdrawal queue.
• No silent provider fallback after a payment has been created.
• No bypass of provider reserves, restrictions or verification requirements.