Most ERPNext teams hit the same wall with the built-in Stripe payment gateway: it can accept a one-off card payment against a Sales Order or Sales Invoice, but that is roughly where it stops. There is no native support for saved-card subscriptions that stay in step with an ERPNext Subscription, no Stripe Connect marketplace payouts to your sellers or partners, no reliable webhook pipeline that turns a charge.succeeded or invoice.paid event into a fully reconciled Payment Entry, and no structured handling of charge.dispute.created or partial refunds. Finance ends up exporting the Stripe dashboard to a spreadsheet and hand-matching payouts against bank statements — every month, forever.

ERPNext Stripe Connect & Billing Pro is a proper Frappe app (its own module, hooks.py, DocTypes, and fixtures) that we build to your exact billing model. On the inbound side it wires ERPNext to Stripe Checkout Sessions and payment links, so a Sales Invoice or Sales Order produces a hosted, PCI-friendly payment page (or a shareable link) instead of raw card fields on your server. A hardened, signature-verified webhook endpoint — exposed as a @frappe.whitelist(allow_guest=True) method that validates the Stripe-Signature header — receives events and, through idempotent server-side logic, creates and submits the matching Payment Entry, reconciles it against the reference invoice, and records the Stripe object IDs (payment_intent, charge, balance_transaction) on custom fields for a full audit trail.

For recurring revenue, we sync ERPNext Subscription and Subscription Plan records with Stripe Products, Prices, and Subscriptions so plan changes, proration, trial periods, and cancellations flow both ways. Scheduler events (scheduler_events hooks running hourly/daily) poll for drift, retry failed charges, and expire access when a subscription lapses. If you operate a marketplace or multi-vendor model, the Connect layer automates onboarding of connected accounts, computes application fees and split payouts, and books each transfer and payout as its own reconciled entry so your Payout Ledger DocType always ties back to Stripe's balance. Dispute and refund events are captured as first-class records with role-scoped workflows, and every mutation is guarded by permissions and role profiles so only authorized users can trigger refunds or release payouts.

Because this is build-to-order, nothing ships as a blind download. We start with a scoping call to map your invoicing flow, subscription plans, tax and currency rules, and Connect topology, then implement against your Frappe/ERPNext v15 or v16 site. You get server scripts and doc_events hooks tuned to your document lifecycle, optional client scripts for in-form actions (generate payment link, view Stripe status), and the whitelisted REST methods your other systems need. Typical delivery is one working week from confirmed scope, validated on a staging bench before we touch production, with source code, documentation, and a support window handed over so your team fully owns what we built.