If you run a multi-vendor marketplace on ERPNext, the money side is where the platform stops helping you. ERPNext models a single company's receivables cleanly, but it has no concept of a connected seller who must be onboarded, KYC-verified, and paid out on their own schedule after your platform keeps a commission. Teams end up reconciling Stripe payouts against a spreadsheet, cutting seller payments manually, and hoping the ledger matches — which does not scale past a handful of vendors and quietly breaks every time a refund or chargeback touches an already-settled order.

We build a proper Frappe app that makes Stripe Connect a first-class part of your ERPNext instance. It ships as an installable app (its own module) with dedicated DocTypes — typically a Connected Seller (mapped to Supplier/Customer), Payout Schedule, Split Payment, and Payout Log — so every connected account, application fee, transfer, and reversal is a queryable, permissioned record rather than a hidden Stripe-only fact. Onboarding uses Stripe Connect account links so sellers complete KYC/identity verification in Stripe's hosted flow, and a signed webhook endpoint (a whitelisted frappe.whitelist(allow_guest=True) method with signature verification) keeps account.updated, payout.paid, charge.refunded, and transfer.reversed events in sync with your DocTypes.

Technically, the split happens at charge time: we set the application fee and the destination connected account on the PaymentIntent, so your commission is retained and the seller's share is routed automatically. hooks.py doc events fire on order/invoice submission to create the split records, scheduler events (frappe.get_hooks("scheduler_events") — hourly/daily) run payout batches against each seller's configured schedule and retry failed transfers, and client scripts surface seller balances and payout status inside the marketplace UI. Reversal and refund handling is built in — a refund on a settled order reverses the associated transfer and application fee and writes a correcting entry so your ERPNext ledger and Stripe never drift. Role profiles and permission rules keep sellers scoped to their own payout data. It targets Frappe/ERPNext v15 and v16, with all Stripe access via the official API and secrets held in Site Config, never in code.

Because this is build-to-order, nothing is shipped from a generic marketplace listing. We start with a scoping call to pin down your vendor model, commission structure, payout cadence, and supported countries/currencies, then build against your instance, validate on a staging site, and hand over the running app with source. Typical delivery is one working week from confirmed scope. You are not buying an instant download — you are commissioning an app that fits how your marketplace actually settles money, installed and supported by the team that wrote it.