Mada Cards Gateway for 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.

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.