Illustrative previewA 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.
Key Features
Tabby split-in-4 and pay-later option presented at Business Central checkout for eligible customers
Eligibility and credit-limit check at order time via Tabby's checkout/sessions API before the BNPL option is shown
Authorization and capture of the Tabby order directly from the Sales Order, with status written back to BC
Full and partial refunds issued to Tabby from the Posted Sales Invoice using an AL action — no portal switching
Settlement payout reconciliation that maps each Tabby net payout to originating BC documents and clears AR
Automatic posting of Tabby merchant fees to a dedicated G/L account so the customer ledger ties out
Multi-currency GCC support for AED, SAR and KWD using BC's native currency and exchange-rate framework
Job queue entry that polls Tabby settlement and order status on a schedule you control
Secured webhook/API endpoint for Tabby callbacks (payment captured, refunded, settled) with signature validation
Dedicated permission sets separating BNPL operators from finance reconcilers
Isolated Tabby setup table for API keys, merchant code and environment toggle (test vs live) — no secrets in code
Implemented as table and page extensions with event subscribers on posting routines, keeping core BC objects untouched
Built to order, done for you
No DIY setup — a working app, built, installed and supported by ECOSIRE.
- 1
You order
Start with a one-time build price. We scope it with you at kickoff.
- 2
We build & install
ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.
- 3
Go live + support
You go live in about 2–4 weeks, with a post-launch support window.
About this Product
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.
What you get
- A per-tenant Business Central AL extension (.app) built for your environment, installed by ECOSIRE
- Tabby setup page with sandbox and live credential profiles and an environment toggle
- Permission sets for BNPL operations and finance reconciliation, ready to assign to user groups
- Job queue setup for automated settlement and order-status polling
- Configured G/L mapping for Tabby clearing, merchant fee and the AED/SAR/KWD currency setup
- Deployment to your BC sandbox, validation against Tabby's test environment, then promotion to production
- Admin and finance handover guide covering checkout, refunds and the settlement reconciliation workflow
- A post-go-live support and warranty window with a defined channel for fixes and questions
Who this is for
GCC D2C / retail finance manager
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.
Business Central administrator / IT lead
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.
E-commerce / operations owner
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.
How Tabby BNPL for Business Central Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Tabby split-in-4 / pay-later at BC checkout | Included | Partial support | Partial support | |
| Eligibility / credit-limit check at order time | Included | Partial support | Partial support | |
| Settlement payout reconciliation against AR in BC | Included | Partial support | Not included | |
| Automatic merchant-fee posting to G/L | Included | Partial support | Not included | |
| Multi-currency GCC (AED, SAR, KWD) | Included | Partial support | Partial support | |
| Refunds issued from BC without portal switching | Included | Partial support | Partial support | |
| Built, installed and supported on your tenant | Included | Partial support | Not included | |
| Update-safe per-tenant extension (no core changes) | Included | Partial support | Included |
Frequently Asked Questions about Tabby BNPL for Business Central
How is this delivered — is it an instant AppSource download?
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.
What is the typical delivery lead time?
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.
What ongoing support and updates are included?
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.
Does it support multiple GCC currencies?
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.
Will this conflict with Business Central updates or other apps?
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.
Related Modules
Built to order
Dynamics 365 Business Central
One-time
Advanced Approval Workflows
Configurable, rule-based approval matrices for every Business Central document type, with per-workflow approvers, amount limits, delegation, and email/mobile responses. Built and installed by ECOSIRE as a per-tenant AL extension.
From $499.00Starting point — quoted to your scope
Built to order
Dynamics 365 Business Central
One-time
Adyen Payment Orchestration for Business Central
A build-to-order AL extension that brings Adyen's 150+ global payment methods and unified settlement reconciliation into Business Central accounts receivable, complementing the first-party D365 Commerce Adyen connector.
From $499.00Starting point — quoted to your scope
Built to order
Dynamics 365 Business Central
One-time
Affiliate & Referral Management for Business Central
A build-to-order Business Central extension that registers affiliates and referrers, attributes sales to referral codes and links, calculates tiered commission, and posts payouts as vendor invoices — installed per-tenant and supported by ECOSIRE.
From $499.00Starting point — quoted to your scope
Built to order
Dynamics 365 Business Central
One-time
Africa Multi-Country Payroll for Business Central
A build-to-order AL extension that adds localized, multi-country African payroll to your Business Central tenant — per-country PAYE and statutory deductions, multi-currency multi-entity runs, statutory filing exports, and employee self-service payslips.
From $799.00Starting point — quoted to your scope
Request a quote
Tabby BNPL for Business Central
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.
- Tabby split-in-4 and pay-later option presented at Business Central checkout for eligible customers
- Eligibility and credit-limit check at order time via Tabby's checkout/sessions API before the BNPL option is shown
- Authorization and capture of the Tabby order directly from the Sales Order, with status written back to BC
- Full and partial refunds issued to Tabby from the Posted Sales Invoice using an AL action — no portal switching