Product details are displayed in English. Translations coming soon.
Quick facts
- Price
- $249.00 USD
- dynamics_365_business_central versions
- —
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
एक बार की खरीदारी
Mada Cards Gateway for Business Central
A per-tenant AL extension that wires Saudi Mada domestic-scheme acceptance into your Business Central payment flow — maximizing local approval rates and lowering interchange. Built, installed, and supported by ECOSIRE on your own BC environment.
$249.00USD
अभी कोई भुगतान नहीं। यह हमारी टीम को एक कोटेशन अनुरोध भेजता है — हम कीमत और अगले चरणों के साथ ईमेल द्वारा संपर्क करेंगे।
प्रमुख सुविधाएँ
Mada domestic-scheme routing for Saudi-issued cards, raising local approval and lowering interchange versus international rails
Apple Pay over Mada where your acquirer exposes the capability
Tokenized card-on-file stored as acquirer tokens in a Customer/Payment-Method table extension — no PAN ever lands in BC
3DS / OTP challenge flow enforced on every transaction per SAMA requirements
AL codeunit integration to your chosen Mada-enabled acquirer (HyperPay, PayTabs, Moyasar, Tap, or bank gateway)
Page extensions adding a 'Pay with Mada' action on Sales Orders and posted documents
Event subscribers on posting and payment-registration codeunits to write authorization and settlement status back to the ledger
Job Queue entry that reconciles authorizations, captures, and settlements on a schedule
Approval/decline reason codes and settlement references logged for a clean Finance audit trail
Dedicated permission sets so only authorized roles can trigger or refund Mada payments
Refund and void support routed back through the same acquirer token
Optional Dataverse / Power Platform sync exposing payment status to Power BI and model-driven apps
Delivered as a signed per-tenant extension installable on BC Online or on-prem — no AppSource dependency
Configuration page for acquirer credentials, currency (SAR), and routing preferences
इस उत्पाद के बारे में
Mada Cards Gateway for Business Central is a build-to-order AL extension that brings Saudi Mada domestic-scheme card acceptance directly into your Business Central payment flow. Saudi-issued cards routed over the international Visa/Mastercard rails frequently see higher decline rates and richer fees; routing them over Mada lifts local approval and lowers cost. This extension makes that routing native to BC.
Mada Cards Gateway for Business Central क्यों चुनें
Mada domestic-scheme routing for Saudi-issued cards, raising local approval and lowering interchange versus international rails
Apple Pay over Mada where your acquirer exposes the capability
Tokenized card-on-file stored as acquirer tokens in a Customer/Payment-Method table extension — no PAN ever lands in BC
3DS / OTP challenge flow enforced on every transaction per SAMA requirements
AL codeunit integration to your chosen Mada-enabled acquirer (HyperPay, PayTabs, Moyasar, Tap, or bank gateway)
Page extensions adding a 'Pay with Mada' action on Sales Orders and posted documents
ECOSIRE designs, builds, and ships this as a per-tenant extension (not a public AppSource listing) installed on your own Business Central Online or on-prem environment. We deliver real AL artifacts: a table extension on Customer / Payment Method to hold tokens and scheme preferences, page extensions that surface a "Pay with Mada" action on the Sales Order and posted documents, event subscribers on posting and payment-registration codeunits, a dedicated codeunit that calls your acquirer's Mada-enabled API, and a Job Queue entry that reconciles authorizations and settlements.
Card data never lands in BC — the extension stores only acquirer tokens (card-on-file), and every transaction runs through 3DS / OTP per SAMA requirements. Apple Pay over Mada is supported where your acquirer exposes it. Approval/decline reason codes, settlement references, and reconciliation status are written back to the ledger so Finance has a clean audit trail.
Because it is custom-built, we adapt to your acquirer (HyperPay, PayTabs, Moyasar, Tap, or your bank's gateway), your permission sets, and your chart of accounts. Optional Dataverse / Power Platform sync exposes payment status to Power BI and model-driven apps. Honest delivery: a typical build is 5–10 business days, after which ECOSIRE installs, smoke-tests in your sandbox, and promotes to production with you.
What you get
- Signed per-tenant Business Central AL extension (.app) packaging the Mada gateway integration
- Source AL project (table/page extensions, codeunits, event subscribers, Job Queue setup) handed over to your team
- Acquirer integration wired to your specific Mada-enabled provider and credentials
- Dedicated permission sets for Mada payment, refund, and configuration roles
- Setup/configuration page for acquirer keys, SAR currency, 3DS/OTP, and routing preferences
- Installation and sandbox smoke-test on your BC environment, then supervised production promotion
- Admin and operator handover documentation plus a short walkthrough session
- Optional Dataverse / Power Platform sync configuration for payment status
Who this is for
Saudi BC Merchant / E-commerce Owner
Runs a Saudi retail or online business on Business Central and wants Mada acceptance to cut declines on local cards and reduce per-transaction fees versus international scheme routing.
Finance / Controller
Needs every Mada authorization, capture, refund, and settlement reconciled back to the ledger with reason codes and references for clean month-end and SAMA-aligned audit trails.
BC Administrator / IT Lead
Owns the BC tenant and wants a clean per-tenant extension with proper permission sets, Job Queue reconciliation, and a documented handover — not a fragile bolt-on or an opaque AppSource black box.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Mada Cards Gateway for Business Central module ZIP from your account dashboard.
Upload to Odoo
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Install the module
Activate Developer Mode, open Apps, click Update Apps List, search for Mada Cards Gateway for Business Central, and press Install.
Configure settings
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Verify & go live
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
How Mada Cards Gateway for Business Central Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Mada domestic-scheme routing built into BC payment flow | Included | Partial support | Partial support | |
| Apple Pay over Mada support | Included | Partial support | Partial support | |
| Tokenized card-on-file with no PAN stored in BC | Included | Partial support | Included | |
| 3DS / OTP enforced per SAMA on every transaction | Included | Partial support | Included | |
| Tailored to your specific acquirer, chart of accounts, and permission sets | Included | Included | Not included | |
| Job Queue reconciliation writing settlement status back to the ledger | Included | Partial support | Partial support | |
| Installed and supported on your tenant by the builder | Included | Not included | Not included | |
| Source AL project handed over to your team | Included | Included | Not included |
Frequently Asked Questions about Mada Cards Gateway for Business Central
How long until the Mada gateway is live in my Business Central?
This is build-to-order, not an instant download. A typical build runs 5–10 business days depending on your acquirer and customizations. ECOSIRE then installs the per-tenant extension in your sandbox, runs a smoke test against the acquirer, and promotes it to production with you. We confirm a firm timeline after a short scoping call about your acquirer and BC version.
What ongoing support and updates do I get after delivery?
You receive the source AL project and a signed extension, plus a handover. ECOSIRE offers ongoing support to keep the extension compatible with Business Central's twice-yearly major updates and with acquirer API changes. Support and update terms are agreed separately from the one-time build fee; we will flag any BC or acquirer change that requires a re-publish.
Does card data get stored in Business Central?
No. The extension stores only acquirer-issued tokens for card-on-file. The full PAN never enters BC, and every transaction runs through 3DS/OTP. This keeps your BC tenant out of PCI scope for cardholder data while still letting customers pay with saved cards.
Which Mada acquirer or gateway does it work with?
Because it is custom-built, we wire the AL codeunit to your chosen Mada-enabled acquirer — for example HyperPay, PayTabs, Moyasar, Tap, or your bank's gateway. Tell us which one you use and we build against its API, credentials, and webhook model.
Is this published on Microsoft AppSource?
No. It is delivered as a per-tenant extension installed directly on your Business Central environment (Online or on-prem). That lets us tailor routing, permission sets, and acquirer integration to your tenant without the constraints of a one-size-fits-all AppSource app.
Can payment status flow into Power BI or Power Platform?
Yes, optionally. We can configure Dataverse / Power Platform sync so authorization and settlement status are available to Power BI dashboards and model-driven apps, giving Finance and operations a live view of Mada payment performance.
Related Modules
कोटेशन का अनुरोध करें
Mada Cards Gateway for Business Central
A per-tenant AL extension that wires Saudi Mada domestic-scheme acceptance into your Business Central payment flow — maximizing local approval rates and lowering interchange. Built, installed, and supported by ECOSIRE on your own BC environment.
- Mada domestic-scheme routing for Saudi-issued cards, raising local approval and lowering interchange versus international rails
- Apple Pay over Mada where your acquirer exposes the capability
- Tokenized card-on-file stored as acquirer tokens in a Customer/Payment-Method table extension — no PAN ever lands in BC
- 3DS / OTP challenge flow enforced on every transaction per SAMA requirements