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. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $249.00 USD; request a quote for a scoped proposal.
示意预览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.
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
以一次性构建价格开始。我们在启动时与您共同确定范围。
ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。
约 2–4 周内上线,并提供上线后的支持期。
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.
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.
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.
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.
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.
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Mada domestic-scheme routing built into BC payment flow | 包含 | 部分支持 | 部分支持 | |
| Apple Pay over Mada support | 包含 | 部分支持 | 部分支持 | |
| Tokenized card-on-file with no PAN stored in BC | 包含 | 部分支持 | 包含 | |
| 3DS / OTP enforced per SAMA on every transaction | 包含 | 部分支持 | 包含 | |
| Tailored to your specific acquirer, chart of accounts, and permission sets | 包含 | 包含 | 不包括在内 | |
| Job Queue reconciliation writing settlement status back to the ledger | 包含 | 部分支持 | 部分支持 | |
| Installed and supported on your tenant by the builder | 包含 | 不包括在内 | 不包括在内 | |
| Source AL project handed over to your team | 包含 | 包含 | 不包括在内 |
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.
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.
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.
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.
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.
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.
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.