Education · Payments
The account structure behind getting paid.
A guest taps a card once. Behind that moment, the payment still needs a merchant identity, a balance, a payout destination, fee rules, and a home for disputes. Connect is infrastructure for that multi-party shape.
The public definition
Stripe Connect is built for platforms whose business customers collect payments from their own customers.
Stripe describes Connect as a way for SaaS platforms and marketplaces to manage payments and move money between multiple parties. The valet operator participates through a connected account rather than every party sharing one generic merchant account.
Follow one payment
The card charge and the bank deposit are not the same event
The money path
→Exact responsibility depends on the platform's Connect design. There is no single universal Connect configuration.
Why onboarding asks business questions
Software profile
Using the product- Company name and operational settings
- Locations, users, and service rules
- Not enough to enable payment capabilities
Payments account
Receiving funds- Legal entity and representatives
- Verification and capability requirements
- Bank account and payout controls
The questions an operator should ask
You do not need to learn an integration's private architecture to understand your commercial position.
Ask which legal entity is presented as the merchant, where charges and refunds appear, who responds to disputes, how fees are disclosed, when payouts become available, and what happens if verification is incomplete.
Stripe's public Connect documentation explains connected accounts, charges, balances, and payouts. Your provider's agreement should explain how those building blocks are configured for you.
The trust test
One guest payment should have one understandable merchant story.
The receipt, statement descriptor, connected account, dispute record, and payout should all point back to the same transaction and business relationship. Connect supplies the plumbing. Clear configuration and explanation make it trustworthy.
Reconciliation is where that story becomes operational. Pick one payment and trace its gross amount, platform or processing fees, refund activity, balance availability, payout, and bank deposit. Then repeat the exercise for a dispute and a negative balance. The person closing the month should not need private integration knowledge to explain why the amount collected at the curb differs from the amount that reached the bank.
Keep verification current before it becomes an emergency. Business details, representatives, capabilities, and bank accounts can change. Route requests through a known owner, warn operators before a payout interruption when possible, and never ask staff to send sensitive verification documents through ordinary support chat. Payments onboarding is part of the financial control environment, not a form to rush through at launch.
