A per-tenant AL extension that connects MyFatoorah's broad GCC local payment coverage to Business Central invoicing, pay-by-invoice links, multi-currency settlement, refunds and automated reconciliation. Built, installed and supported by ECOSIRE on your tenant. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $299.00 USD; request a quote for a scoped proposal.
Manifesto do app
Feito em torno do seu fluxo de trabalho
A per-tenant AL extension that connects MyFatoorah's broad GCC local payment coverage to Business Central invoicing, pay-by-invoice links, multi-currency settlement, refunds and automated reconciliation. Built, installed and supported by ECOSIRE on your tenant.
Sem configuração por conta própria — um app funcional criado, instalado e com suporte da ECOSIRE.
Comece com um preço único de desenvolvimento. Definimos o escopo com você no início.
A ECOSIRE cria, configura e instala no seu Dynamics 365 Business Central.
Você entra no ar em cerca de 2–4 semanas, com um período de suporte pós-lançamento.
MyFatoorah aggregates the widest single-integration spread of GCC local payment methods — KNET in Kuwait, Mada in Saudi Arabia, Benefit in Bahrain, plus Fawry-style and card rails across the region. This extension brings that breadth directly into Microsoft Dynamics 365 Business Central so your finance team stops bouncing between a gateway dashboard and the ERP.
ECOSIRE builds this as a per-tenant AL extension (not a generic AppSource listing). We deploy it straight onto your Business Central environment — Online (SaaS) or on-prem — using table and page extensions on the Posted Sales Invoice and Customer Ledger Entry, an httpclient-based service layer wrapping the MyFatoorah REST API, and event subscribers on invoice posting so a hosted payment link is generated automatically. Webhook callbacks land via a published AL API page (OData v4) and are matched back to the originating invoice.
Reconciliation is the point of the whole thing: settled MyFatoorah transactions are pulled in and applied against Customer Ledger Entries, with a Job Queue entry polling for status so nothing is manually keyed. Refunds are initiated from inside Business Central and write back as corrective entries. Card-on-file uses MyFatoorah tokenization so no PAN ever touches your tenant.
Because it is build-to-order, scope is yours: multi-company, specific MyFatoorah supplier accounts per legal entity, dimension mapping, a dedicated permission set, and optional Power Platform / Dataverse surfacing of payment status. We hand over the source, a signed app file installed under your tenant, and a runbook. This is honest delivery — a real engineering engagement with a lead time, not a one-click download.
Runs receivables for a Kuwait-centric or multi-GCC merchant and wants settled KNET/Mada/Benefit payments to reconcile against Customer Ledger Entries automatically instead of manual matching from a gateway export.
Owns the tenant and needs the gateway delivered as a clean per-tenant extension with a proper permission set, Job Queue setup and source handover — not a black-box AppSource app they cannot audit.
Sends pay-by-invoice links to GCC customers and needs the broadest local-method breadth (one integration covering KNET, Mada, Benefit, Fawry-style) plus tokenized card-on-file for repeat buyers, all visible inside the ERP.
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| Broad GCC local-method coverage (KNET, Mada, Benefit, Fawry-style) in one integration | Incluído | Suporte parcial | Suporte parcial | |
| Installed as an auditable per-tenant AL extension with source handover | Incluído | Incluído | Não incluído | |
| Automated reconciliation against Customer Ledger Entries via Job Queue | Incluído | Suporte parcial | Suporte parcial | |
| In-ERP refunds and tokenized card-on-file (no PAN on tenant) | Incluído | Suporte parcial | Suporte parcial | |
| Built, installed and supported on your specific tenant by the vendor | Incluído | Não incluído | Não incluído | |
| Multi-company, multi-currency GCC with per-entity MyFatoorah accounts | Incluído | Suporte parcial | Suporte parcial | |
| Optional Power Platform / Dataverse payment-status surfacing | Incluído | Suporte parcial | Não incluído | |
| Fixed one-time build price with no per-transaction software fee to the vendor | Incluído | Suporte parcial | Não incluído |
This is build-to-order. After a short scoping call we confirm your MyFatoorah accounts, legal entities and reconciliation rules, then build and test against the MyFatoorah sandbox. Typical lead time is about 2 to 4 weeks depending on multi-company scope and Power Platform options. You get a UAT pass in a sandbox tenant before we cut over to production — no surprise go-lives.
Every build includes a post-go-live support window for bug fixes. Because it is a per-tenant extension we own, updates are delivered as new versioned .app releases — we reinstall on your tenant and re-run UAT. We track Business Central monthly/major release compatibility and MyFatoorah API changes, and offer an optional retainer for proactive maintenance, new payment methods and feature additions.
No. All sensitive card data is handled by MyFatoorah's hosted payment pages and tokenization. Card-on-file stores only a MyFatoorah token, never a PAN, so your tenant stays out of cardholder-data scope. The AL extension only ever moves tokens, transaction references and status.
Yes. The extension is written in AL using supported, cloud-ready objects (httpclient, API pages, Job Queue, event subscribers) so it installs on Business Central Online as a per-tenant extension and equally on a supported on-premises deployment. The MyFatoorah webhook endpoint is exposed through a published API page over OData v4.
Yes. We support multiple legal entities with per-company MyFatoorah supplier accounts and dimension mapping, plus multi-currency GCC settlement (KWD, SAR, BHD, AED, USD) with currency-aware application against the Customer Ledger Entries. The exact company and currency matrix is confirmed during scoping.
A build-to-order Odoo localization that loads Algeria's full wilaya and commune hierarchy with bilingual French and Arabic names, wired into partner addresses and reporting. ECOSIRE builds, installs, and supports it after your quotation.
A build-to-order 2Checkout (Verifone) payment integration for ERPNext, giving global digital-goods sellers card acceptance, 45+ local payment methods, multi-currency checkout, and reconciled invoices. ECOSIRE scopes, builds, installs, and supports it on your ERPNext v15/v16 instance.
A build-to-order 2Checkout / Verifone payment gateway for Magento 2 and Adobe Commerce: localized checkout in 12 languages, iDEAL, Giropay and regional methods, multi-currency global selling, subscription billing and tax/invoicing automation — engineered, installed and supported by ECOSIRE.
A per-tenant AL extension that connects MyFatoorah's broad GCC local payment coverage to Business Central invoicing, pay-by-invoice links, multi-currency settlement, refunds and automated reconciliation. Built, installed and supported by ECOSIRE on your tenant.