A native PayTabs payment integration for Microsoft Dynamics 365 Business Central, built as a per-tenant AL extension. Accept cards, Mada, and local MENA wallets, send pay-by-link Arabic/English invoices, route marketplace split-payments, and reconcile across SAR, AED, KWD and more. 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.
示意预览A native PayTabs payment integration for Microsoft Dynamics 365 Business Central, built as a per-tenant AL extension. Accept cards, Mada, and local MENA wallets, send pay-by-link Arabic/English invoices, route marketplace split-payments, and reconcile across SAR, AED, KWD and more.
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
以一次性构建价格开始。我们在启动时与您共同确定范围。
ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。
约 2–4 周内上线,并提供上线后的支持期。
If your GCC business runs Microsoft Dynamics 365 Business Central but settles card payments through a disconnected PayTabs portal, you carry the reconciliation burden manually. This extension closes that gap. ECOSIRE builds, installs, and supports a per-tenant AL extension that wires PayTabs directly into your BC environment so a posted Sales Invoice, a pay-by-link, or a customer-initiated checkout records its payment, capture, and settlement back against the right customer ledger entry automatically.
The extension is written in AL using table and page extensions over the standard Customer, Sales Invoice, and Payment Registration objects, plus a dedicated PayTabs setup page holding your profile ID, server key, and region endpoint. Event subscribers on posting and a Job Queue entry that polls the PayTabs transaction API keep BC and the gateway in sync without manual exports. Webhooks land on a published API page (BC REST/OData) so PayTabs IPN callbacks update transaction status the moment a payment clears or is refunded.
Because PayTabs supports Mada, regional cards, and local wallets, the extension surfaces all enabled methods on the pay-by-link page in Arabic or English. Split-payment / payout routing is supported for marketplace operators who need to direct a share of each settlement to sub-merchants. Multi-currency handling respects your BC currency setup so SAR, AED, KWD and other GCC currencies post correctly.
This is build-to-order: we scope against your exact BC version (cloud SaaS or on-prem), PayTabs account, and posting rules, then deliver a tested per-tenant extension with permission sets and a runbook. It is not an instant AppSource download — it is engineered and supported for your tenant.
Runs Business Central for a Saudi or UAE SME and wants card, Mada, and wallet payments to reconcile automatically against customer ledger entries instead of being keyed in from the PayTabs portal.
Operates a multi-vendor marketplace on BC and needs PayTabs split-payment routing so each settlement automatically directs the correct share to sub-merchants while invoicing stays in BC.
Manages the tenant and needs a clean, supported per-tenant extension with proper permission sets, a job queue, and a webhook endpoint rather than a fragile custom script no one can maintain.
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Native PayTabs (Mada, cards, wallets) inside Business Central | 包含 | 部分支持 | 部分支持 | |
| Pay-by-link on Arabic/English invoices from BC | 包含 | 部分支持 | 部分支持 | |
| Split-payment / marketplace payout routing | 包含 | 部分支持 | 不包括在内 | |
| Multi-currency GCC (SAR, AED, KWD) posting | 包含 | 部分支持 | 部分支持 | |
| Installed and supported on your tenant (per-tenant extension) | 包含 | 部分支持 | 不包括在内 | |
| Built to your exact BC version and posting rules | 包含 | 包含 | 不包括在内 | |
| Job Queue auto-reconciliation + IPN webhook updates | 包含 | 部分支持 | 部分支持 |
No. This is a build-to-order per-tenant AL extension. ECOSIRE scopes it against your exact Business Central version, PayTabs account, and posting rules, then builds, installs, and supports it on your environment. There is no instant AppSource download for this listing.
Typical lead time is 2 to 4 weeks from kickoff, depending on your BC version (cloud SaaS or on-prem), which PayTabs methods you enable, and whether split-payment routing is in scope. We confirm a firm schedule after the scoping call, which precedes any build work.
The price includes 30 days of post-go-live support covering defects and configuration adjustments. Beyond that, we offer an optional maintenance agreement that keeps the extension compatible with Business Central monthly and major releases and with PayTabs API changes. Per-tenant extensions are upgraded and re-tested by us, not auto-pushed.
Yes. Card data is captured on PayTabs' Hosted Payment Page, so cardholder data never touches your Business Central tenant and your PCI scope stays with PayTabs. 3DS and OTP authentication are handled by PayTabs; BC records only the resulting transaction reference and status.
Yes. If your PayTabs account is enabled for split-payment / payout, the extension can route a configured share of each settlement to sub-merchants while the invoice and customer ledger entries remain in Business Central. We confirm your PayTabs account supports this during scoping.
A native PayTabs payment integration for Microsoft Dynamics 365 Business Central, built as a per-tenant AL extension. Accept cards, Mada, and local MENA wallets, send pay-by-link Arabic/English invoices, route marketplace split-payments, and reconcile across SAR, AED, KWD and more.