Stripe Payments Pro for ERPNext

Stripe Payments Pro is a proper Frappe app (its own module, DocTypes, and hooks.py) that replaces the thin native connector with a modern, Payment Intents-first gateway. Card confirmation runs through Stripe.js and the Payment Intents API so SCA/3DS 2 challenges are handled inline and off-session charges are authenticated correctly. Apple Pay and Google Pay are enabled as express checkout options via the Payment Request Button, with domain verification and merchant setup done as part of delivery. A dedicated Stripe Settings single DocType holds keys, webhook secrets, and per-currency behaviour, with API secrets stored encrypted in the site config rather than in plaintext fields.

Reconciliation is webhook-driven, not polling-based. We register a whitelisted endpoint that verifies Stripe's signature, then map events — payment_intent.succeeded, charge.refunded, charge.dispute.created, invoice.paid and the subscription lifecycle events — onto ERPNext documents through server-side doc_events and controller logic. A successful intent creates or submits the matching Payment Entry against the Sales Invoice or Sales Order, records the Stripe fee, and links the transaction id for audit; refunds and partial refunds post reversing entries; disputes update a custom status so finance sees chargebacks in real time. Subscriptions created in Stripe are synced to ERPNext Subscription records, and recurring invoice.paid events auto-generate the corresponding invoice and payment. Idempotency keys and stored event ids prevent double-posting on Stripe's webhook retries. Role-based permissions and a role profile keep gateway configuration limited to finance admins, while client scripts surface a clean pay experience on the ERPNext portal and web forms.

Because this is build-to-order, ECOSIRE engineers the app against your actual ERPNext version (v15 or v16), your chart of accounts, your currencies, and your invoicing workflow — we do not hand you a generic marketplace download. After a short scoping call we confirm the exact event mappings, subscription rules, and reconciliation accounts you need, build and test on a staging site, run UAT with your team, and cut over with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope, and you receive the full source in a git repository so nothing is locked away.