产品详细信息以英文显示。翻译即将推出。
速览
- 价格
- $299.00 USD
- dynamics_365_business_central 版本
- —
- 设置时间
- 120分钟
- 许可证
- 一次永久
- 语言
- 11 语言
一次性购买
MyFatoorah Payment Gateway for Business Central
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.
$299.00USD
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
核心功能
Broadest single-integration GCC local-method coverage via MyFatoorah: KNET (Kuwait), Mada (KSA), Benefit (Bahrain), Fawry-style and regional card rails
Pay-by-invoice hosted payment links generated automatically on invoice posting via an AL event subscriber on the Posted Sales Invoice
MyFatoorah REST API service layer built in AL with httpclient, retry/timeout handling and structured response parsing (no PAN stored on tenant)
Webhook callback ingestion through a published Business Central API page (OData v4) that matches payments to the originating invoice
Automated reconciliation: settled transactions applied against Customer Ledger Entries with a Job Queue entry polling MyFatoorah for status
In-ERP refund initiation that writes corrective entries back to the customer ledger and the linked invoice
Tokenized card-on-file using MyFatoorah tokenization for repeat customers, with no cardholder data persisted in Business Central
Multi-currency GCC settlement (KWD, SAR, BHD, AED, USD) with currency-aware application and rounding handling
Dedicated permission set and entitlements so payment operations are role-scoped and audit-clean
Table and page extensions on Customer Ledger Entry and the Customer Card surfacing live payment/transaction status
Multi-company support with per-legal-entity MyFatoorah account and dimension mapping
Optional Power Platform / Dataverse surfacing of payment status for Power BI dashboards and Power Apps approvals
关于此产品
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.
为什么选择 MyFatoorah Payment Gateway for Business Central
Broadest single-integration GCC local-method coverage via MyFatoorah: KNET (Kuwait), Mada (KSA), Benefit (Bahrain), Fawry-style and regional card rails
Pay-by-invoice hosted payment links generated automatically on invoice posting via an AL event subscriber on the Posted Sales Invoice
MyFatoorah REST API service layer built in AL with httpclient, retry/timeout handling and structured response parsing (no PAN stored on tenant)
Webhook callback ingestion through a published Business Central API page (OData v4) that matches payments to the originating invoice
Automated reconciliation: settled transactions applied against Customer Ledger Entries with a Job Queue entry polling MyFatoorah for status
In-ERP refund initiation that writes corrective entries back to the customer ledger and the linked invoice
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.
你得到什么
- Signed per-tenant AL extension (.app) installed on your Business Central environment (Online or on-prem)
- Full AL source code with table/page extensions, the MyFatoorah service codeunit, event subscribers and the published API page
- Configured MyFatoorah connection (API key, supplier accounts per legal entity) on a dedicated Setup page
- Dedicated permission set and entitlement file scoping payment operations to authorized roles
- Job Queue entry configured for automated reconciliation polling, with documented cadence
- Configuration and operations runbook covering setup, webhook endpoint, refund flow and troubleshooting
- UAT in a sandbox tenant against the MyFatoorah test environment before production cutover
- Post-go-live support window with bug fixes and a documented update/versioning path
这是给谁的
GCC Finance Manager
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.
Business Central Administrator / Partner
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.
E-commerce / Operations Lead
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.
安装概述
从ECOSIRE下载
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 MyFatoorah Payment Gateway for Business Central 模块 ZIP。
上传至Odoo
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中（或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传）。
安装模块
激活开发者模式，打开应用程序，单击更新应用程序列表，搜索 MyFatoorah Payment Gateway for Business Central，然后按安装。
配置设置
打开新菜单，粘贴您的 ECOSIRE 许可证密钥，连接任何外部凭据（Shopify、Amazon、Stripe 等），然后保存。
验证并上线
运行内置连接测试，同步前 10 条记录，并安排定期 cron。如果出现任何问题，请联系支持人员。
MyFatoorah Payment Gateway for Business Central 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Broad GCC local-method coverage (KNET, Mada, Benefit, Fawry-style) in one integration | 包含 | 部分支持 | 部分支持 | |
| Installed as an auditable per-tenant AL extension with source handover | 包含 | 包含 | 不包括在内 | |
| Automated reconciliation against Customer Ledger Entries via Job Queue | 包含 | 部分支持 | 部分支持 | |
| In-ERP refunds and tokenized card-on-file (no PAN on tenant) | 包含 | 部分支持 | 部分支持 | |
| Built, installed and supported on your specific tenant by the vendor | 包含 | 不包括在内 | 不包括在内 | |
| Multi-company, multi-currency GCC with per-entity MyFatoorah accounts | 包含 | 部分支持 | 部分支持 | |
| Optional Power Platform / Dataverse payment-status surfacing | 包含 | 部分支持 | 不包括在内 | |
| Fixed one-time build price with no per-transaction software fee to the vendor | 包含 | 部分支持 | 不包括在内 |
关于MyFatoorah Payment Gateway for Business Central的常见问题
How long does delivery take, since this isn't an instant AppSource download?
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.
What does ongoing support and updates look like after go-live?
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.
Is cardholder data stored in our Business Central tenant?
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.
Can it run on Business Central Online (SaaS) and on-premises?
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.
Will it work across multiple companies and currencies?
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.
相关模块
申请报价
MyFatoorah Payment Gateway for Business Central
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.
- Broadest single-integration GCC local-method coverage via MyFatoorah: KNET (Kuwait), Mada (KSA), Benefit (Bahrain), Fawry-style and regional card rails
- Pay-by-invoice hosted payment links generated automatically on invoice posting via an AL event subscriber on the Posted Sales Invoice
- MyFatoorah REST API service layer built in AL with httpclient, retry/timeout handling and structured response parsing (no PAN stored on tenant)
- Webhook callback ingestion through a published Business Central API page (OData v4) that matches payments to the originating invoice