Enterprise ERPNext merchants processing more than $1M quickly hit the ceiling of what ERPNext handles natively. Out of the box, ERPNext offers a handful of Payment Gateway integrations and a generic Payment Gateway Account, but there is no first-class Adyen connector, no shared tokenization vault across sales channels, no unified reconciliation between e-commerce, in-app, and physical POS terminals, and no structured handling of Adyen's asynchronous webhook (notification) model. Finance teams end up stitching together CSV exports, manual journal entries, and a separate PSP per region — exactly the fragmentation a global processor like Adyen is meant to eliminate.

ECOSIRE builds a proper Frappe app (installable via bench get-app / bench install-app) with its own module, so nothing is patched into ERPNext core and upgrades stay clean. The app introduces dedicated DocTypes — Adyen Settings (single, with API key, merchant account, HMAC key, and live/test toggle), Adyen Payment Session, Adyen Notification (the raw webhook ledger), and Adyen Payment Token for stored network tokens. It wires into the order and invoice lifecycle through hooks.py doc events (for example on_submit of Sales Invoice / Sales Order and on_payment_authorized), exposes @frappe.whitelist() endpoints for the checkout /payments and /payments/details calls, and drives in-person flows through Adyen's Terminal API so ERPNext POS Profiles can settle on physical card readers. Every gateway credential is stored using Frappe's encrypted field handling, never in plaintext.

The webhook lane is the heart of the design. Adyen delivers authorisations, captures, refunds, chargebacks, and payout events asynchronously, so the app exposes a whitelisted notification endpoint that validates the HMAC signature, persists each event as an Adyen Notification record for a durable audit trail, and only then acts on it — idempotently, so Adyen's at-least-once retries never double-post a Payment Entry. A scheduler_events job reconciles pending sessions and sweeps unmatched notifications, and Payment Entries / Journal Entries are created against the correct company and bank account so your reconciliation in ERPNext matches Adyen's settlement reports. 3-D Secure 2 and Adyen RevenueProtect are enabled at the session level, and Client Scripts render the Adyen Web Drop-in/Components on the ERPNext-hosted checkout for card and 100+ local payment methods.

Because this is build-to-order, we start from your confirmed scope — your Frappe/ERPNext version (v15 or v16), your channels (web, in-app, POS), the payment methods and currencies you need, and how you want settlements posted. We build against your requirements, run UAT on a staging bench, and hand over the full git repository. Typical delivery is 2-4 weeks from confirmed scope. There is no marketplace download — ECOSIRE writes, installs, tests, and supports the code for your specific environment, and you own the source at handover.