A build-to-order Dynamics 365 Business Central extension that offers Tabby split-in-4 / pay-later at checkout for GCC merchants, captures and refunds orders from BC, and reconciles Tabby settlement payouts against AR in AED, SAR and KWD. 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 build-to-order Dynamics 365 Business Central extension that offers Tabby split-in-4 / pay-later at checkout
for GCC merchants, captures and refunds orders from BC, and reconciles Tabby settlement payouts against AR in AED, SAR and KWD.
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
以一次性构建价格开始。我们在启动时与您共同确定范围。
ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。
约 2–4 周内上线,并提供上线后的支持期。
Tabby BNPL for Business Central is a per-tenant AL extension that wires Tabby's buy-now-pay-later (split-in-4 and pay-later) into your Dynamics 365 Business Central order-to-cash flow. ECOSIRE builds it to your environment, installs it as a tenant-specific extension (not a generic AppSource download), and supports it after go-live.
At order time, the extension calls Tabby's checkout/sessions API to run an eligibility and credit-limit check, then presents the BNPL option to the customer. On approval, the order is authorized and captured; refunds and partial refunds are issued back through Tabby directly from the Sales Order or Posted Sales Invoice using an AL action and event subscribers on the posting routines — no separate portal switching.
The real accounting value is in reconciliation. Tabby settles net of fees on a payout cycle, so we map each Tabby payout to the originating BC documents, post the merchant fee to a dedicated G/L account, and clear the AR balance so your customer ledger and bank reconciliation actually tie out. Multi-currency GCC is handled natively for AED, SAR and KWD using BC's currency and exchange-rate framework.
Technically this is delivered as table and page extensions over Sales and Payments, event subscribers (OnAfterPost, OnBeforeRelease), a job queue entry that polls settlement status, dedicated permission sets, and a secured API/webhook endpoint for Tabby callbacks. Credentials live in isolated setup tables, never in code.
Because it is built-to-order, you get a clean fit to your chart of accounts, your tax setup and your sandbox-then-production rollout — with an honest delivery lead time rather than a one-click promise. ECOSIRE delivers, deploys to your sandbox, validates against Tabby's test environment, then promotes to production.
Wants BNPL to lift average order value without breaking the books — needs Tabby payouts, fees and AR to reconcile cleanly inside Business Central instead of a side spreadsheet.
Needs the integration delivered as a clean per-tenant extension that survives BC updates, with permission sets, isolated credentials and a sandbox-first rollout rather than risky core customization.
Wants the Tabby split-in-4 option live at checkout with real eligibility checks, and one place to issue refunds, so support and fulfilment teams don't bounce between BC and the Tabby portal.
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Dynamics 365 Business Central 原生 |
|---|---|---|---|---|
| Tabby split-in-4 / pay-later at BC checkout | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Eligibility / credit-limit check at order time | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Settlement payout reconciliation against AR in BC | 包含 | 部分支持 | 不包括在内 | 不包括在内 |
| Automatic merchant-fee posting to G/L | 包含 | 部分支持 | 不包括在内 | 不包括在内 |
| Multi-currency GCC (AED, SAR, KWD) | 包含 | 部分支持 | 部分支持 | 部分支持 |
| Refunds issued from BC without portal switching | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Built, installed and supported on your tenant | 包含 | 部分支持 | 不包括在内 | 不包括在内 |
| Update-safe per-tenant extension (no core changes) | 包含 | 部分支持 | 包含 | 不包括在内 |
No. This is a build-to-order, per-tenant Business Central extension. ECOSIRE builds it for your specific environment, chart of accounts and tax setup, then installs it as a tenant-specific extension. It is not a one-click AppSource app, and we do not claim an instant download — you get a fit-to-purpose integration instead of a generic one.
Most builds are scoped, developed, deployed to your sandbox and validated against Tabby's test environment within roughly two to four weeks, depending on your chart-of-accounts complexity, the GCC currencies in scope and approval cycles on your side. We confirm a firm timeline in writing after a short scoping call before any work starts.
Every build includes a post-go-live support and warranty window for fixes and questions through a defined channel. Because Tabby's API and Business Central both evolve, we offer an ongoing maintenance arrangement to keep the extension compatible with BC monthly updates and any Tabby API changes — quoted separately from the one-time build.
Yes. AED, SAR and KWD are supported out of the build using Business Central's native multi-currency and exchange-rate framework, so payouts and AR clearing post in the correct currency. Additional GCC currencies can be added during scoping if Tabby supports them in your market.
It is built as table and page extensions with event subscribers, so it does not modify core BC objects — that is what keeps it update-safe. Credentials and configuration live in dedicated setup tables, and permission sets isolate access. If you run other payment or e-commerce apps, we check for event and field overlap during scoping.
A build-to-order Dynamics 365 Business Central extension that offers Tabby split-in-4 / pay-later at checkout for GCC merchants, captures and refunds orders from BC, and reconciles Tabby settlement payouts against AR in AED, SAR and KWD.