Global and EU merchants who sell to wallet users keep hitting the same wall: ERPNext ships with Payment Gateway and Payment Request DocTypes, but there is no native Skrill connector. Customers who pay with their Skrill balance, a European card, or a local method like SOFORT, iDEAL, or a regional bank transfer either abandon the cart or force your finance team to reconcile off-platform payments by hand. That manual bridge breaks the link between the money and the Sales Invoice, delays revenue recognition, and makes refunds and chargebacks a spreadsheet exercise.

ECOSIRE builds a proper Frappe app — erpnext_skrill — that registers Skrill as a first-class ERPNext Payment Gateway. We add a Skrill Settings (Single) DocType to hold your merchant email, secret word, MQI/API password, and hashed credentials, plus a per-currency configuration child table. When a Payment Request is submitted, hooks.py doc events and whitelisted server methods generate a Skrill Quick Checkout session and redirect the customer to Skrill's hosted payment page — so card data and wallet credentials never touch your ERPNext site, keeping you out of heavy PCI scope. On return, a public whitelisted webhook endpoint validates Skrill's status report using the MD5 signature (md5sig) against your secret word, then updates the Payment Request, creates the Payment Entry, and reconciles it to the originating Sales Invoice inside a single database transaction so a duplicate callback can never double-post.

Beyond the one-shot checkout, we wire the pieces ERPNext operators actually need day to day. Recurring billing is handled through Skrill's recurring payment flow, driven by a scheduler event that requests the next installment and writes a fresh Payment Entry on each cycle. Refunds are issued from within ERPNext — a Skrill Refund DocType with a role-restricted button calls the Skrill refund API, and a nightly scheduler_events job polls transaction status to sync completed refunds and chargebacks back onto the linked invoice, flipping outstanding amounts automatically. Every gateway call, callback, and signature check is written to a Skrill Transaction Log DocType for audit, and permissions are locked down with a dedicated Role and Role Profile so only Accounts users can view credentials or trigger refunds.

Because this is build-to-order, nothing is a black box. After a short scoping call we confirm your currencies, local-method mix, ERPNext version (v15 or v16), and whether you need Payment Request, Web Shop checkout, or a custom portal flow. We build against a staging copy of your site, run UAT with real sandbox transactions, and hand over the full git repository. Typical delivery is one working week from confirmed scope. There is no instant download — you get software built for your exact ERPNext instance, installed, tested, and supported.