Stripe Connect, built for businesses where payments are not simple.

Stripe Connect production deployments handling marketplace payments, franchise payouts, and multi-vendor commerce. Built for retail group, franchise operator, and B2B platforms.

The case for proper Stripe Connect integration

Most businesses that accept payments use the standard Stripe integration, which is straightforward: customer pays, you receive the money. Stripe Connect is the version of Stripe designed for businesses where the money flow is more complex than that. If your model involves paying somebody else from each transaction, Connect is the tool.

The common scenarios:

• A marketplace where customers pay you, and you pay multiple sellers from each transaction.
• A franchise model where each franchisee receives part of every transaction.
• A multi-vendor commerce platform where each order may involve products from several vendors.
• A subscription business where revenue is shared with referral partners or affiliates.
• A booking platform where the venue and the platform each take a share of every booking.

Stripe Connect provides the primitives for all of these. What it does not provide is the orchestration logic for your specific business rules, the audit trail your accountant needs, the reconciliation reports your franchisees expect, or the integration into the rest of your stack. Stripe sells you the API; you still have to build the business on top of it.

That orchestration layer is the work. We have built it for several businesses in production, and we know exactly where the complexity hides. The complexity is rarely in the happy-path transaction. It is in refunds, chargebacks, insufficient balance handling, KYC failure recovery, multi-currency settlement, and the reporting that turns “Stripe says you sent $X” into “the franchisee can prove they received exactly what they were owed”.

The honest moment most agencies skip: Stripe Connect is not always the right answer. If your payout structure is simple (one platform fee, one recipient, no edge cases), a standard Stripe integration plus manual payouts via bank transfer is often cheaper to run for years. The Connect case starts at a meaningful payout volume, or with regulatory requirements that demand auditable split payments, or with sellers who need real-time visibility into their balances. About one in five payment discoveries we run ends with our recommendation to stick with standard Stripe and handle splits via accounting.

If you have been quoted a Stripe Connect build and the quote does not include the orchestration and reporting layer, call 0431 000 062. We will tell you what is actually involved.

Symptoms to look for

You probably need proper Stripe Connect integration when one or more of the following are true.

• One transaction needs to split across multiple parties. Standard Stripe handles you receiving money. It does not handle paying out 30% to a franchisee, 5% to a referral partner, and keeping the rest. The split logic currently lives in a spreadsheet, with bank transfers happening manually each week.
• You run a franchise or multi-site model where revenue is shared. Each location or franchisee receives a portion of revenue, and you need to track, pay, and report on that flow accurately. Franchisee disputes about payment timing or amount are eating into the relationship.
• You operate a marketplace. Multiple sellers, one customer-facing checkout, separate payouts to each seller, separate tax and reporting obligations. Sellers want a self-service dashboard showing their own balances and payout history.
• You have refund or chargeback complexity. A refund needs to claw back from the seller, not just from you. Chargebacks need to be allocated to the responsible party. Currently the platform absorbs both, and the unit economics no longer work.
• You need audit-ready financial reporting on the payment flow. Standard Stripe dashboards do not show you the full split-payment story across your business. Your accountant has been re-reconstructing the splits from raw Stripe exports for two years.
• Onboarding new sellers or franchisees has become a manual job. KYC, bank verification, identity checks, tax declarations: each new connected account requires hours of email back and forth. The bottleneck on growth is now the onboarding admin, not the demand.
• You need cross-border or multi-currency payouts. International sellers, franchisees in different countries, or revenue in multiple currencies. The complexity of paying out across borders is currently handled through expensive intermediaries or not handled at all.

DIAGNOSTIC

If two or more describe your situation, Stripe Connect is the right tool. The work is in the integration layer that turns the Stripe primitives into your specific business operations.

The architecture we deploy

Stripe Connect integrations on Nexus follow the same pattern across use cases. The components are deliberately boring. Boring is the point.

Onboarding flow

Sellers, franchisees, or vendors are onboarded through Stripe’s KYC and verification process. Nexus orchestrates the onboarding, tracks status, and surfaces completion in your operational systems. The seller starts in your branded experience, gets handed off to Stripe for verification, and lands back in your system with the correct connected account ID, capabilities, and payout schedule. The “where is this seller stuck” question becomes a query, not a support ticket.

Transaction orchestration

When a payment is captured, Nexus calculates the split based on your business rules (which can be more complex than Stripe’s built-in fee splits), creates the right Stripe Connect transfer instructions, and records the intended flow. The rules can include tiered commission, product-specific splits, seller-specific overrides, and time-based promotional rules, all calculated at the middleware layer and applied to each transaction in milliseconds.

Webhook handling

Stripe’s payment, payout, refund, and chargeback webhooks are handled idempotently. Each event updates the relevant internal state and triggers downstream actions (notification, accounting, reporting). Stripe sends webhooks more than once under failure conditions; Nexus handles the deduplication correctly so a single event never produces a double payout.

Payout management

Payouts to sellers, franchisees, or vendors are scheduled according to your rules (daily, weekly, monthly, or on-demand). Each payout is reconciled to the underlying transactions for full traceability. When a franchisee asks “what was this $4,237 deposit for”, the answer is a list of the underlying transactions, available to them in their own portal, with the calculation rules visible at the line level.

Accounting integration

Every transaction, every transfer, every payout, and every chargeback flows to your accounting system (Xero or MYOB) with correct treatment. Platform revenue, gross sales, and pass-through payments are correctly separated. The platform’s own revenue figure (the take, not the gross) is the figure that appears on the P&L; the gross flows through a clearing account that reconciles to zero. This is the accounting treatment most off-the-shelf Stripe Connect integrations get wrong.

Audit and reporting

Every event is logged. Full reconciliation reports are available for any time period. Franchisees, sellers, or vendors can be given access to their own data through a controlled portal. The auditor’s question “show me how this payout was calculated” gets answered from the audit log in two minutes, including the transaction-level breakdown and the rule version that was active at the time.

Three engagement shapes

We structure Stripe Connect engagements one of three ways. All three start with discovery.

• Single-tier marketplace. From $15,000. One platform, one type of seller, standard split rules. 4 to 6 weeks. Best when the business model is established and the split logic is uniform across sellers.
• Complex marketplace or franchise platform. From $40,000. Multi-tier splits, custom payout rules, full reporting, accounting integration. 8 to 12 weeks. Best for franchise networks and marketplaces where the split logic varies by seller, product, or promotion.
• Run With Us retainer. From $6,500 per month. Ongoing monitoring, continuous additions, security patching, quarterly review. Best when your seller base is growing and the rules continue to evolve.

Call 0431 000 062 to talk through which fits.

Stripe Connect implementations we have built

Three Stripe Connect implementations. Two named clients, one confidential at client request. Reference calls available.

Wesfarmers, marketplace platform

• Problem: Multi-vendor commerce platform requiring split payments to multiple parties on every transaction. Standard payment integration did not cover the model. Vendor payouts were being managed via a spreadsheet and manual bank transfers, taking four people most of a day each week.
• Built: Stripe Connect integration with Nexus orchestrating the split logic. Each order calculated platform fee, vendor share, and any referral fees. Payouts scheduled and tracked. Full reconciliation reports daily. Built over 10 weeks.
• Result: Vendor payouts moved from manual weekly process to automated daily. Reconciliation time reduced significantly. Platform now scales to additional vendors without operational overhead. Onboarding a new vendor takes hours, not weeks.
• Stack: Shopify Plus, Stripe Connect (Custom accounts), Nexus middleware, PostgreSQL, AWS Sydney, custom payout engine.

Motiv8sports franchise platform

• Problem: Sports franchise model with weekly payouts to franchisees, complex commission rules based on program type, and a need to handle franchisee-specific tax and reporting. Franchisees were calling head office weekly to dispute payment amounts. Reconciliation took two staff most of a day each week.
• Built: Custom Stripe Connect implementation with franchise-specific split rules. Custom franchisee portal showing their own transactions, payouts, and reports. Accounting integration to franchisee-side Xero accounts. Built over 14 weeks across 100+ franchises Australia-wide.
• Result: Weekly payouts now automated. Franchisee complaints about payment delays eliminated. Compliance reporting available on-demand for both head office and franchisees. Head office support load dropped to almost zero on payment-related queries.
• Stack: Symfony platform, Stripe Connect (Express accounts), Nexus middleware, Xero API (multi-tenant), PostgreSQL, AWS Sydney.

A booking marketplace, name confidential

• Problem: Booking platform with venues taking 85% and the platform taking 15%. Refund and cancellation handling was complex, because both parties had committed costs that needed to be allocated correctly when a booking was cancelled. The CFO had stopped trusting the gross-vs-net revenue split and was reconstructing it from raw Stripe data each month.
• Built: Stripe Connect with custom refund and cancellation logic. Tiered cancellation policy (full refund at 7+ days, 50% at 48 hours, no refund inside 24 hours) applied automatically. Insufficient-balance handling for cases where a venue had spent their payout before a customer’s late refund came through.
• Result: Refund disputes between platform and venues dropped to near zero. The CFO’s parallel revenue reconstruction process retired. Net revenue figure now trusted on the day it lands, not reconstructed two weeks later.
• Stack: Custom booking platform, Stripe Connect (Standard accounts), Nexus middleware, Xero API, PostgreSQL, AWS Sydney.

Who you will work with

No account managers, no offshore teams, no juniors learning on your project. The two engineers below scope, build, and ship the work. Both have built Stripe Connect in production. The person who hears your split logic in discovery is the person who writes the code that calculates it. Your accountant should be in the room for at least the rules review session — Stripe Connect projects fail when the engineering and the accounting are not aligned.

How we ship it

Stripe Connect projects run in three phases. Each phase is fixed scope and fixed price.

For most builds, total project time is 6 to 10 weeks. Multi-currency, cross-border, or 100+ seller onboarding deployments extend timelines.

Stripe Connect integration FAQs