Ürün ayrıntıları İngilizce olarak görüntülenir. Çeviriler yakında gelecek.
Kısa bilgiler
- Fiyat
- $299.00 USD
- ERPNext versiyonları
- —
- Kurulum süresi
- 30 dk.
- Lisans
- Bir kerelik kalıcı
- Diller
- 11 language
Tek Seferlik Satın Alma
Moyasar Payment Gateway for ERPNext
A build-to-order Moyasar payment gateway for ERPNext that lets Saudi and MENA sellers accept mada, Apple Pay, STC Pay, SADAD and cards directly from ERPNext. ECOSIRE builds, installs and supports it against your v15/v16 site — request a quotation and we scope, build and hand over the source.
$299.00USD
Şimdi ödeme yok. Bu, ekibimize bir teklif talebi gönderir — fiyat ve sonraki adımlarla e-posta ile dönüş yapacağız.
Temel Özellikler
Registers Moyasar as a native ERPNext Payment Gateway via a `Moyasar Settings` single DocType
Encrypted storage of publishable/secret API keys using Frappe's password fieldtype — no plaintext credentials
Accepts mada, Visa, Mastercard and Amex through the Moyasar hosted form
Apple Pay and STC Pay wallet support for local-first Saudi checkout
SADAD bill-payment reference generation and status reconciliation
Both hosted payment form and direct API charge flows, selectable per checkout surface
Tokenized card storage for recurring/subscription charges driven by a `scheduler_events` job
Whitelisted callback endpoints (`@frappe.whitelist(allow_guest=True)`) for return and webhook URLs
Moyasar webhook signature verification before any Payment Request or Sales Invoice state change
`hooks.py` `doc_events` keep Payment Request, Sales Invoice and payment status in sync
Every API call logged as an `Integration Request` for a complete, queryable audit trail
Refunds initiated from ERPNext call the Moyasar refund API and write back to the source document
Role profile + granular permissions restricting gateway config and refunds to authorized users
Client Script UX on the checkout/Payment Request forms plus configurable success/failure redirect pages
Multi-currency handling with SAR default and per-method enable/disable toggles
Built and tested against ERPNext / Frappe v15 and v16
Bu Ürün Hakkında
Saudi and MENA e-commerce sellers running ERPNext keep hitting the same wall at the checkout: ERPNext core ships integrations for Stripe, PayPal, Razorpay and a handful of others, but there is no native Moyasar connector — and none of the core gateways clear mada, Apple Pay, STC Pay or SADAD, which is exactly what local buyers expect to see. Teams end up reconciling payments by hand, exporting spreadsheets from the Moyasar dashboard, and manually marking Sales Invoices as paid, which breaks straight-through order-to-cash and invites keying errors on every transaction.
Neden Moyasar Payment Gateway for ERPNext
Registers Moyasar as a native ERPNext Payment Gateway via a `Moyasar Settings` single DocType
Encrypted storage of publishable/secret API keys using Frappe's password fieldtype — no plaintext credentials
Accepts mada, Visa, Mastercard and Amex through the Moyasar hosted form
Apple Pay and STC Pay wallet support for local-first Saudi checkout
SADAD bill-payment reference generation and status reconciliation
Both hosted payment form and direct API charge flows, selectable per checkout surface
ECOSIRE builds a proper Frappe app — a versioned, bench-installable package with its own module — that registers Moyasar as a first-class ERPNext Payment Gateway. We add a Moyasar Settings DocType (single) to hold your publishable and secret API keys, currency, and enabled payment methods, encrypted using Frappe's password fieldtype so secrets never sit in plaintext. From there the app wires into the standard Payment Request / Integration Request flow so a hosted Moyasar payment form or a direct API charge can be raised against any Sales Invoice, Sales Order, or web-shop order without leaving ERPNext.
Technically the connector is grounded in Frappe primitives, not a black box. Payment callbacks land on whitelisted methods (@frappe.whitelist(allow_guest=True)) exposed through the Frappe REST API; hooks.py doc_events on Payment Request and Sales Invoice keep document state in sync; and every gateway call is persisted as an Integration Request for a full audit trail. Webhook signatures from Moyasar are verified before any status change is trusted, so spoofed callbacks can't mark an invoice paid. mada, Visa, Mastercard, Amex, Apple Pay and STC Pay run through the hosted form or the API, SADAD handles bill-payment references, and tokenized cards enable recurring charges driven by a scheduler event (scheduler_events) for subscription-style billing. Refunds initiated from ERPNext call Moyasar's refund API and write the result back to the source document. Role-based permissions and a dedicated role profile keep gateway configuration and refund actions off limits for ordinary users.
Because this is build-to-order, nothing ships as an anonymous instant download. You request a quotation, we run a short scoping call to confirm your ERPNext version (v15 or v16), the exact payment methods and currencies you need, your checkout surface (web shop, Payment Request emails, or a custom portal), and any reconciliation or recurring-billing requirements. We then build against a staging clone of your site, run UAT with you, and hand over installable source code plus a git repository. Typical delivery is 2–4 weeks from confirmed scope, and every engagement includes a post-go-live support window and a documented rollback plan.
Ne elde edeceksin
- Installable source code for your ERPNext version (v15 or v16) as a bench-installable Frappe app
- Installation and configuration on your staging site, then production, with credentials wired to Moyasar
- Technical documentation: DocTypes, hooks, whitelisted endpoints, webhook setup and env requirements
- End-user guide plus a live training session for your finance/e-commerce team
- UAT on a staging clone with a documented, tested rollback plan before go-live
- Post-go-live support window for defect fixes and configuration adjustments
- Handover of the private git repository with full commit history
- Moyasar webhook and callback URL configuration checklist for your account
Bu kimin için
Saudi ERPNext e-commerce seller
Runs an ERPNext web shop or storefront and loses conversions because mada, Apple Pay and STC Pay aren't offered natively. Needs local-first acceptance wired straight into Sales Invoices without manual reconciliation.
Finance & reconciliation lead
Owns order-to-cash and is tired of exporting from the Moyasar dashboard and hand-marking invoices paid. Wants every charge, refund and webhook logged as an Integration Request with an auditable trail inside ERPNext.
ERPNext implementation partner / systems integrator
Delivering ERPNext to a KSA client and needs a supported, version-matched Moyasar connector with clean source and git handover rather than a fragile in-house script to maintain.
Subscription / recurring-billing merchant
Charges customers on a recurring cycle and needs tokenized cards plus a scheduler-driven job to raise Moyasar charges automatically against ERPNext subscriptions.
Kuruluma genel bakış
ECOSIRE'dan indirin
Lisansı ecosire.com adresinden satın alın ve hesap kontrol panelinizden Moyasar Payment Gateway for ERPNext uygulamasının ZIP dosyasını indirin.
Uygulamayı bankınıza ekleyin
ZIP dosyasını tezgahınızın uygulamalar klasörüne çıkarın veya çıkarılan uygulamanın yolunu içeren "bench get-app" komutunu çalıştırın.
Sitenize yükleyin
Moyasar Payment Gateway for ERPNext yüklemek ve şemasını uygulamak için `bench --site SITE_NAME install-app APP_NAME` komutunu ve ardından `bench move'u çalıştırın.
Lisansınızı etkinleştirin
Sitenizdeki ECOSIRE Lisans ayarlarını açın ve lisans anahtarınızı etkinleştirin. Ücretsiz ecosire_connect ve ecosire_license_client uygulamalarını gerektirir.
Moyasar Payment Gateway for ERPNext Nasıl Karşılaştırılır
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| Moyasar support (mada/STC Pay/SADAD) | Native connector for all enabled methods | Whatever you build and maintain | Often card-only, mada/STC Pay patchy | |
| ERPNext version fit (v15/v16) | Built and tested to your exact version | Depends on in-house skill | Whatever the listing targets | |
| Integration depth | Payment Gateway + hooks + Integration Request log | As deep as you scope it | Varies; often shallow callback only | |
| Webhook signature verification | Verified before any state change | Must implement yourself | Inconsistent across apps | |
| Source & git handover | Full private repo handed over | You own it by definition | Usually closed/licensed binary | |
| Refunds from ERPNext | Refund API wired to source document | Extra build effort | Rarely included | |
| Support & accountability | Post-go-live window + named team | Internal only | Best-effort forum/email | |
| Time to live | 2–4 weeks from confirmed scope | Unpredictable | Fast if it fits as-is |
Moyasar Payment Gateway for ERPNext hakkında Sıkça Sorulan Sorular
+Is this an instant download from the Frappe Marketplace?
No. This is a build-to-order product. ECOSIRE builds the Moyasar connector against your specific ERPNext version and requirements, installs it, and hands over the source. There is no anonymous instant-download package.
+How long does delivery take?
Typical delivery is 2–4 weeks from confirmed scope. After a short scoping call to lock down your ERPNext version, payment methods, currencies and checkout surface, we build on a staging clone, run UAT with you, then deploy to production.
+Which Frappe/ERPNext versions are supported?
We build and test against ERPNext / Frappe v15 and v16. Tell us your exact version on the scoping call and we target that; the delivered source is a proper bench-installable Frappe app, not a patch.
+What payment methods will my customers see?
mada, Visa, Mastercard and Amex cards, plus Apple Pay, STC Pay and SADAD bill payments — whatever your Moyasar account is enabled for. Each method can be toggled on or off in the Moyasar Settings DocType, and both hosted-form and API checkout flows are supported.
+How do payment confirmations and refunds stay in sync with ERPNext?
Moyasar webhooks hit whitelisted callback endpoints; we verify the signature before trusting any status change, update the Payment Request and Sales Invoice via hooks.py doc_events, and log every call as an Integration Request. Refunds triggered in ERPNext call the Moyasar refund API and write the result back to the source document.
+What about support and updates 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 and source, your team or ECOSIRE can maintain and extend it later; ongoing support or upgrades to future ERPNext versions can be arranged as a separate agreement.
+Can it handle recurring or subscription charges?
Yes. We store tokenized cards via Moyasar and drive recurring charges from a Frappe scheduler_events job, so subscription-style billing runs automatically against your ERPNext documents. Confirm your recurring model on the scoping call so we build the cycle logic to match.
Teklif isteyin
Moyasar Payment Gateway for ERPNext
A build-to-order Moyasar payment gateway for ERPNext that lets Saudi and MENA sellers accept mada, Apple Pay, STC Pay, SADAD and cards directly from ERPNext. ECOSIRE builds, installs and supports it against your v15/v16 site — request a quotation and we scope, build and hand over the source.
- Registers Moyasar as a native ERPNext Payment Gateway via a `Moyasar Settings` single DocType
- Encrypted storage of publishable/secret API keys using Frappe's password fieldtype — no plaintext credentials
- Accepts mada, Visa, Mastercard and Amex through the Moyasar hosted form
- Apple Pay and STC Pay wallet support for local-first Saudi checkout