Produktdetails werden auf Englisch angezeigt. Übersetzungen folgen in Kürze.
Kurze Fakten
- Preis
- $199.00 USD
- ERPNext-Versionen
- —
- Rüstzeit
- 30 Min
- Lizenz
- Einmalig und unbefristet
- Sprachen
- 11 Sprachen
Einmalkauf
Skrill Gateway for ERPNext
A build-to-order Skrill payment integration for ERPNext that adds the Skrill digital wallet, card payments, and 40+ local methods to your checkout. ECOSIRE builds, installs, and supports it against your Frappe/ERPNext v15/v16 site.
$199.00USD
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
Hauptfunktionen
Registers Skrill as a native ERPNext Payment Gateway via a `Skrill Settings` Single DocType (merchant email, secret word, MQI/API password) with credentials stored as password fields
Skrill Quick Checkout hosted-page redirect so card and wallet data never touch your ERPNext site, minimizing PCI DSS scope
Supports the Skrill digital wallet balance, credit/debit cards, and 40+ local payment methods (SOFORT, iDEAL, Giropay, Rapid Transfer, regional bank transfers)
Public whitelisted webhook that validates every Skrill status report with the `md5sig` MD5 signature against your secret word before touching ledgers
Idempotent callback handling — duplicate or replayed status reports are detected and never double-post a Payment Entry
`hooks.py` doc events on Payment Request submit that mint the Skrill session and persist the transaction reference
Automatic `Payment Entry` creation and reconciliation against the originating Sales Invoice inside one atomic transaction
Recurring billing through Skrill's recurring flow, driven by a `scheduler_events` job that requests each installment and posts a new Payment Entry per cycle
`Skrill Refund` DocType with a role-restricted action that calls the Skrill refund API from inside ERPNext
Nightly scheduler job that polls transaction status to sync completed refunds and chargebacks back onto the linked invoice's outstanding amount
Multi-currency configuration child table mapping each ERPNext currency to the correct Skrill settlement behavior
`Skrill Transaction Log` DocType capturing every request, callback, signature result, and status for audit and reconciliation
Whitelisted REST API methods (`frappe.whitelist`) so headless storefronts and custom portals can initiate Skrill payments programmatically
Dedicated Role and Role Profile plus permission rules restricting credential access and refund actions to Accounts users
Sandbox/live environment toggle with separate credential sets for safe UAT before go-live
Built and tested for Frappe/ERPNext v15 and v16 with a bench-installable app and clean migration path
Über dieses Produkt
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.
Warum Skrill Gateway for ERPNext wählen
Registers Skrill as a native ERPNext Payment Gateway via a `Skrill Settings` Single DocType (merchant email, secret word, MQI/API password) with credentials stored as password fields
Skrill Quick Checkout hosted-page redirect so card and wallet data never touch your ERPNext site, minimizing PCI DSS scope
Supports the Skrill digital wallet balance, credit/debit cards, and 40+ local payment methods (SOFORT, iDEAL, Giropay, Rapid Transfer, regional bank transfers)
Public whitelisted webhook that validates every Skrill status report with the `md5sig` MD5 signature against your secret word before touching ledgers
Idempotent callback handling — duplicate or replayed status reports are detected and never double-post a Payment Entry
`hooks.py` doc events on Payment Request submit that mint the Skrill session and persist the transaction reference
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 2-4 weeks from confirmed scope. There is no instant download — you get software built for your exact ERPNext instance, installed, tested, and supported.
Was Sie bekommen
- Installable source code for your version of the `erpnext_skrill` Frappe app (bench-installable, no license keys)
- Installation and configuration on your ERPNext site (Skrill Settings, currencies, webhook URL, sandbox-to-live cutover)
- Technical documentation: DocTypes, hooks, whitelisted endpoints, webhook signature scheme, and scheduler jobs
- End-user guide plus a live training session for your Accounts/finance team covering payments, refunds, and reconciliation
- UAT on a staging copy of your site with sandbox transactions, sign-off checklist, and a documented rollback plan
- Post-go-live support window for defect fixes and configuration adjustments
- Handover of the full git repository with commit history and branch/tag conventions
- Skrill onboarding checklist covering the merchant account, secret word, and MQI/API settings you provision on Skrill's side
Für wen das ist
EU/global ERPNext merchant serving wallet users
Sells across Europe and emerging markets where customers expect to pay from a Skrill wallet or a local method rather than an international card. Needs those payments captured, reconciled, and refundable inside ERPNext instead of a separate Skrill dashboard.
Finance / Accounts manager
Owns reconciliation and the month-end close. Wants every Skrill payment to auto-create a Payment Entry linked to the right Sales Invoice, with refunds and chargebacks flowing back to outstanding amounts and a full transaction audit log.
ERPNext administrator / systems integrator
Runs the bench and the site. Needs a clean, migratable Frappe app with proper DocTypes, hooks, and scheduler events — installable via bench, versioned in git, and safe to upgrade across v15/v16 rather than ad-hoc server-script patches.
Subscription / recurring-revenue operator
Bills customers on a repeating cycle and needs Skrill recurring payments driven automatically from ERPNext, with each installment posting its own Payment Entry and failed renewals surfaced for follow-up.
Installationsübersicht
Von ECOSIRE herunterladen
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei der Skrill Gateway for ERPNext-App von Ihrem Konto-Dashboard herunter.
Fügen Sie die App zu Ihrer Bank hinzu
Extrahieren Sie die ZIP-Datei in den Apps-Ordner Ihrer Bank oder führen Sie „bench get-app“ mit dem Pfad zur extrahierten App aus.
Installieren Sie es auf Ihrer Website
Führen Sie „bench --site SITE_NAME install-app APP_NAME“ gefolgt von „bench migrate“ aus, um Skrill Gateway for ERPNext zu installieren und sein Schema anzuwenden.
Aktivieren Sie Ihre Lizenz
Öffnen Sie die ECOSIRE-Lizenzeinstellungen auf Ihrer Website und aktivieren Sie Ihren Lizenzschlüssel. Erfordert die kostenlosen Apps ecosire_connect und ecosire_license_client.
Wie Skrill Gateway for ERPNext im Vergleich abschneidet
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| Skrill connector for ERPNext | Purpose-built Frappe app registering Skrill as a native Payment Gateway | Built from scratch in-house against Skrill's API docs | Generic marketplace app, often single-currency and card-only | |
| Wallet + 40 local methods | Wallet, cards, and 40+ local methods via Quick Checkout | Only what your team has time to implement | Usually cards only; limited local methods | |
| Invoice reconciliation | Auto Payment Entry linked to Sales Invoice, atomic and idempotent | Depends on developer skill; duplicate-callback risk | Basic status update, manual reconciliation common | |
| Refunds & chargebacks | In-ERPNext refund DocType + nightly status sync to invoice | Extra build effort, frequently skipped | Rarely covered; done in Skrill dashboard | |
| Recurring billing | Scheduler-driven recurring flow, Payment Entry per cycle | Significant added scope to build reliably | Typically not supported | |
| Security & permissions | MD5 signature validation, role profile, transaction audit log | Varies; signature checks sometimes missed | Opaque; limited role control | |
| Fit & ownership | Built to your site, full git repo handover | You own it but carry all build + maintenance | Black-box, vendor-locked, closed source | |
| Support & delivery | Install, UAT, training, post-go-live support window | Internal team is the only support line | Forum/ticket support, no tailoring |
Häufig gestellte Fragen zu Skrill Gateway for ERPNext
How long does delivery take?
This is a build-to-order app, not an instant download. Typical delivery is 2-4 weeks from confirmed scope. After the initial scoping call we lock down your currencies, local-method mix, and ERPNext version, then build against a staging copy of your site, run UAT with sandbox transactions, and schedule go-live.
How do support and updates work after go-live?
Every engagement includes a post-go-live support window for defect fixes and configuration adjustments. Because you receive the full git repository, your team can maintain the app independently, and ECOSIRE offers ongoing support and version-compatibility updates (for example when you move from ERPNext v15 to v16) as a separate arrangement.
Is my ERPNext site in PCI scope?
We use Skrill's Quick Checkout hosted payment page, so cardholder and wallet credentials are entered on Skrill's environment and never pass through or get stored on your ERPNext site. This keeps you in the lightest-touch PCI scope. Your site only receives the signed status report and settlement reference.
Which ERPNext versions are supported?
We build and test for Frappe/ERPNext v15 and v16. The app is delivered as a standard bench-installable Frappe app with proper DocTypes, hooks, and migrations, so it upgrades cleanly rather than relying on ad-hoc server scripts.
Does it handle refunds and chargebacks?
Yes. Refunds are issued from a `Skrill Refund` DocType with a role-restricted action that calls the Skrill refund API from inside ERPNext. A nightly scheduler job then polls transaction status to sync completed refunds and chargebacks back onto the linked Sales Invoice, adjusting the outstanding amount automatically.
Can it drive recurring or subscription billing?
Yes. We implement Skrill's recurring payment flow driven by a scheduler event that requests each installment on schedule and writes a new Payment Entry per cycle, with failed renewals flagged for follow-up. The exact model is confirmed during scoping to match your billing plans.
Can our custom storefront or portal trigger Skrill payments?
Yes. The app exposes whitelisted (`frappe.whitelist`) REST methods so a headless storefront, custom web portal, or the ERPNext Web Shop can initiate a Skrill Quick Checkout session and receive the reconciled result programmatically.
Angebot anfordern
Skrill Gateway for ERPNext
A build-to-order Skrill payment integration for ERPNext that adds the Skrill digital wallet, card payments, and 40+ local methods to your checkout. ECOSIRE builds, installs, and supports it against your Frappe/ERPNext v15/v16 site.
- Registers Skrill as a native ERPNext Payment Gateway via a `Skrill Settings` Single DocType (merchant email, secret word, MQI/API password) with credentials stored as password fields
- Skrill Quick Checkout hosted-page redirect so card and wallet data never touch your ERPNext site, minimizing PCI DSS scope
- Supports the Skrill digital wallet balance, credit/debit cards, and 40+ local payment methods (SOFORT, iDEAL, Giropay, Rapid Transfer, regional bank transfers)
- Public whitelisted webhook that validates every Skrill status report with the `md5sig` MD5 signature against your secret word before touching ledgers