Stripe Connect / marketplaces: Stripe Connect integrations designed around how your marketplace moves money.
From your first connected account to complex seller payout workflows, we help platforms design onboarding, charges, fees, transfers, refunds and reporting with the right responsibilities in the right places.
Architecture-led integrations · Customer-owned code · Stripe-certified professionals
- 01BuyerPays at checkoutthen: Payment
- 02Your platformKeeps the platform feethen: Transfer
- 03Seller's connected accountBalance updatesthen: Payout
- 04Seller's bankOn the payout schedule
01The problem
A marketplace is more than a checkout button.
Money moves between your customers, your platform and your sellers, and each step has an owner. Where those owners are unclear, the problems arrive after launch.
- 01
Seller onboarding drop-off
Sellers stall on verification requirements and never become payable.
- 02
Unclear responsibilities
Nobody has decided who carries fees, refunds and disputes: the platform or the seller.
- 03
Unsupported charge patterns
The flow the product needs does not match the charge model that was built.
- 04
Refund and dispute allocation
A refund or dispute lands on the wrong balance, or on no one in particular.
- 05
Disconnected records
Charges, transfers and payouts do not reconcile with your own orders and ledgers.
- 06
Country and capability limits
Connect features, account types and payouts vary by country and business model.
02Services
From connected accounts to operational payouts.
- 01
Connected account architecture
Integration type, supported account configuration, permissions, capabilities, responsibilities and onboarding requirements.
What you receive
- Account model decision, written down
- Capabilities per country
- Who owns which responsibility
- 02
Seller and provider onboarding
Stripe-hosted or embedded onboarding, return and refresh states, requirements-due handling and the seller dashboard connection.
What you receive
- Onboarding journey in your product
- Status and requirements-due UX
- Re-entry when information is missing
- 03
Charges and funds flow
A choice among supported direct, destination or separate-charges-and-transfers patterns, made after a responsibility, geography and business-model review.
What you receive
- Charge model matched to the business
- Server-side charge and transfer code
- Funds-flow diagram for your team
- 04
Platform fees and balances
Application fees where applicable, reversals, refunds, reconciliation and reporting design.
What you receive
- Fee logic in code
- Refund and reversal handling
- Reconciliation against your ledger
- 05
Payout operations
Payout status, schedules and configuration where supported, failure handling, restrictions and seller support workflows.
What you receive
- Payout status surfaced to sellers
- Failed-payout handling
- Support views for your team
- 06
Webhooks, migration and monitoring
Account update events, charge and transfer events, idempotency, reconciliation, migration feasibility and ongoing observability.
What you receive
- Idempotent Connect webhook handlers
- Migration feasibility notes
- Monitoring on account and payout events
Have sellers, countries and payout rules in mind already? Bring them to a call and we will map the architecture with you.
03Funds flow
Choose the money movement model before writing the code.
Funds move differently under each model. Fees, refunds, disputes and platform liability depend on the model and on configuration.
- 01BuyerPays the sellerthen: Payment
- 02Seller's connected accountThe charge is created herethen: Application fee
- 03Your platformReceives its feethen
- 04Seller's bankPayout from the seller's balance
What we verifyThe seller's account is the one charged. Stripe fees, refunds and disputes typically sit with the connected account, depending on configuration.
04Use cases
Common Connect implementations we help deliver.
Patterns, not client stories: each shows the journey and the engineering behind it.
Service marketplace
Customers book a provider → the provider is onboarded → payment is captured under the chosen charge model → the seller balance and refund states are reconciled.
Multi-vendor commerce
One basket, several sellers → the order is split → transfers follow fulfilment → refunds reverse only the affected seller's share.
Booking platform
A booking is made → payment is taken now or held as the model allows → cancellations follow your policy → the provider is paid out.
Vertical SaaS with merchant payouts
Your software's merchants onboard as connected accounts → their customers pay through your product → fees and payouts are reported back in your app.
05Deliverables
What you’ll own at handover.
- A Connect architecture note covering the account model and funds-flow decisions.
- Seller onboarding screens and account-status UX, as scoped.
- Server-side charge, transfer and fee integrations, with webhook handlers.
- Refund, dispute and negative-balance edge cases handled, as scoped.
- A test-mode runbook, monitoring and a reconciliation approach.
- Client-owned implementation, with rollout and permissions handed over.
Exact deliverables depend on the scope we agree in writing.
06How we work
Architecture before implementation.
Responsibilities are reviewed for your business model and countries before anything is built.
- 01Eligibility and use-case discoveryCountries, business model and the account types Stripe supports for them.
- 02Funds-flow mappingThe charge model, fees, refunds and disputes, with an owner for each.
- 03Platform and connected-account UXOnboarding, status and payout screens for sellers and for your team.
- 04Build and webhook testServer-side integration, with account, charge and transfer events exercised in test mode.
- 05Edge-case and operational checksRefunds, disputes, failed payouts and restricted accounts, verified before launch.
- 06Launch and supportA staged rollout, monitoring and support by the month or as needed.
07Team and credentials
The people who design the funds flow build it.
Cevrynt, Inc. is a Stripe partner in the Stripe Partner Ecosystem.
The partnership belongs to the company. The certifications below belong to the people named.
View our Stripe Partner Directory profile (opens in a new tab)
Arindam Pradhan
Founder, engineering lead
Stripe Certified Professional — Implementation Architect
Anupam Pradhan
Stripe Certified Professional — Payments Architect
Subhadip Giri
Full stack developer
Stripe Certified Professional — Payments Architect
- 300+
- projects delivered
- 50+
- CRM deployments
- 90,000+
- leads a day handled by systems we built
- 9GB+
- production databases
- ~$800 → $150
- monthly cloud costs, cut for a client
Delivered by the team, including work as GreenBorn Infotech.
You work directly with Arindam Pradhan, who has built production software since 2018, and four senior engineers with six or more years each. We work remotely from India with overlap into US and European hours. These figures cover the team’s software delivery in general, not Stripe work alone.
Platform subscriptions too? See Stripe Billing. Need capacity by the month? See Dedicated Engineers. Other Stripe work is on the Stripe Payments page.
08Questions
Stripe Connect questions, answered first.
The short answer leads. Open any row for the full one, in the same words we would use on the call.
01Which Stripe Connect charge type should our marketplace use?It depends on who carries what
It depends on who should carry charges and payouts, how refunds and fees are handled, and which markets and countries Stripe supports for your model. We decide it with you during the architecture review.
02Can you build seller onboarding and verification flows?Yes
Yes. We integrate the account onboarding journey into your product and handle requirements-due and status changes using the APIs Stripe supports.
03Can we collect a platform fee?Often, depending on the model
Often, using the appropriate supported charge arrangement. We confirm your Stripe account capabilities and how fees are treated before building it.
04Can you support cross-border sellers?After a country review
We assess the supported countries and cross-border constraints for your specific business model before promising coverage.
05Can you repair an existing Stripe Connect integration?Yes, after an audit
Yes. We audit account states, events, charge and transfer records and the failures users see, then scope a fix.
06How are Connect projects priced?Written scope after review
With a written project scope after a review. Projects range from simple onboarding to more complex funds-flow systems, and nothing is billed before you agree the scope.
Still deciding?Discuss your Connect architectureor write toarin@cevrynt.com
09Related services
Marketplaces usually need more than payouts.
- For SaaS and subscription productsStripe Billing & subscriptionsTrials, invoices, renewals, migrations and webhook reconciliation.Scoped after a technical review
- For POS, kiosk and mobile productsStripe Terminal & Tap to PayKiosk, POS and mobile payments, including real native integration experience.Scoped after a technical review
- The Stripe Payments hubAll Stripe workCheckout and payments, webhooks, migrations, and every Stripe specialty in one place.Scoped after an audit
- For agencies and startupsDedicated EngineersOngoing Stripe and product work by the month, from engineers who join your team.From $4,000/month per engineer
FreeGuide · 44 checks · 41-page PDF
Stripe Integration Health Check
The checklist our team runs at the start of a Stripe audit. Use it on your own integration in an afternoon and see where it is likely to fail first.
- Webhooks8
- Payments and idempotency6
- Billing and subscriptions8
- Connect (platforms and marketplaces)6
- Terminal and in-person payments5
- Keys, access and security6
- Operations and monitoring5
Book a call
Build the marketplace funds flow correctly from day one.
Walk us through your sellers, countries, payout rules and current stack. We will identify the architecture that needs to be scoped.