ERPNext Geidea Payment Gateway

ECOSIRE builds a proper Frappe app — a versioned, installable package with its own module, not a pile of loose customizations — that wires Geidea directly into ERPNext's payment flow. At its core is a Geidea Settings single DocType holding your merchant/API credentials (secret keys encrypted via Frappe's get_password/password fieldtype), plus a Payment Gateway record so Geidea appears anywhere ERPNext offers a gateway. We implement hosted checkout and Geidea Payment Links so a customer can pay a Sales Invoice or Payment Request from the ERPNext portal, an emailed link, or your website. Mada, Visa and Mastercard are all supported through the one integration.

Technically, the app exposes @frappe.whitelist(allow_guest=True) methods that create the Geidea session, redirect the payer to hosted checkout, and receive the return/callback. Server-side we verify the payment signature/hash before trusting any status, then on a confirmed capture we create and submit the matching Payment Entry against the invoice — auto invoice settlement — so AR updates the instant money clears, with no manual marking. hooks.py doc events (e.g. on Payment Request) and a scheduler event give you a reconciliation sweep that re-queries Geidea for any pending/late callbacks so a dropped webhook never leaves an invoice stuck. Idempotency keys prevent double Payment Entries on callback retries. A dedicated role and permission set keeps gateway credentials and the reconciliation logs away from ordinary users, and client scripts surface the payment status and Geidea reference right on the invoice.

Because this is build-to-order, nothing ships as a blind download. We start with a short scoping call to confirm your Geidea product setup (hosted checkout vs. links vs. both), which invoices/portals should offer it, currency and Mada handling, and your Frappe/ERPNext version — the app targets v15 and v16. You get a fixed-scope build, installation on your bench, UAT on a staging site with Geidea test credentials, then a supervised go-live on production. Typical delivery is 2–4 weeks from confirmed scope. You keep the source: the git repository, the app, and full technical docs are handed over so your team (or ours, under support) can maintain it.