Nigerian, Ghanaian, and Kenyan merchants running ERPNext keep hitting the same wall: ERPNext ships integrations for global processors, but Paystack — the gateway that actually clears cards, bank transfers, USSD, and mobile money across West and East Africa — is not a first-class citizen in ERPNext core. Finance teams end up reconciling Paystack settlements by hand against Sales Invoices, chasing failed charges through the dashboard, and copy-pasting payment references into Payment Entry. There is no native Payment Gateway provider for Paystack, no automated webhook listener, and no way to raise a Payment Request that a customer can settle with USSD or a mobile-money wallet. This is where ERPNext native runs out of road.

ECOSIRE builds a proper Frappe app — a real app in your bench, not a pile of client-side hacks — that registers Paystack as a first-class Payment Gateway and Payment Gateway Account, so it plugs into the standard ERPNext Payment Request and Integration Request flow the same way Stripe or Razorpay would. We add a Paystack Settings single DocType for keys, currency, and channel configuration (encrypted secret fields, test vs live toggle), and wire the payment lifecycle through hooks.py doc events and whitelisted server methods. When a customer pays, Paystack calls a signed webhook endpoint we expose as a whitelisted method; the handler verifies the x-paystack-signature HMAC, resolves the transaction reference back to the originating Sales Invoice or Payment Request, and creates the Payment Entry automatically with the correct settled amount, fees, and channel. Split payments and subaccounts are modelled as child DocTypes so marketplaces and multi-vendor sellers can route a percentage or flat cut to each subaccount on every transaction.

Technically, the build covers the channels your buyers actually use: card, bank transfer, USSD, QR, and mobile money (Ghana MTN/Vodafone/AirtelTigo, Kenya M-Pesa via Paystack), exposed through Paystack's Initialize/Charge/Verify APIs and returned to a themed checkout or a hosted Paystack page. Payment links and Paystack Plans/Subscriptions are surfaced inside ERPNext so recurring billing raises the right invoices on schedule. A scheduler_events hook runs a periodic reconciliation job that re-verifies pending references and closes the gap when a webhook is missed or arrives late — so your books are never stuck on an ambiguous "processing" state. Client Scripts add the pay-now action and reference display on the Sales Invoice form; Role Profiles and permission rules keep API keys and the reconciliation dashboard restricted to Accounts Manager and System Manager. Everything targets Frappe/ERPNext v15 and is forward-checked for v16.

Because this is build-to-order, nothing is downloaded and dropped on your site blind. We start with a short scoping call to confirm your channels, currencies (NGN/GHS/KES/USD), subaccount rules, and which documents trigger payment. We build against your version on a staging bench, run UAT with you using Paystack test keys, then install on production behind a rollback plan and hand over the git repository. Typical delivery is one working week from confirmed scope, followed by a post-go-live support window. You own the source, so nothing is locked to us.