A per-tenant AL extension that adds compliant card surcharges or convenience fees to Business Central payments, with card-brand and region-aware rules, caps, exemptions, and disclosure text — built, installed, and supported by ECOSIRE. One-time license from $199.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

A per-tenant AL extension that adds compliant card surcharges or convenience fees to Business Central payments, with card-brand and region-aware rules, caps, exemptions, and disclosure text — built, installed, and supported by ECOSIRE.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
Card processing fees quietly erode margin on every electronic payment your Business Central tenant takes. The Surcharge & Convenience Fee Engine lets US and MENA merchants offset that cost the compliant way — distinguishing a true card surcharge (assessed only on credit, capped, never on debit) from a flat convenience fee (charged for an alternative payment channel), and enforcing the rules automatically so your finance team never has to remember which states or regions are off-limits.
Card-brand and region-aware surcharge rules in a configurable Surcharge Rule table (Visa, Mastercard, Amex, Discover; per state/region)
Clear engine-level distinction between a card surcharge (credit-only, capped) and a flat convenience fee (alternative channel)
Automatic, separately-labelled fee line injected onto the posted invoice or receipt at the correct G/L account via posting event subscribers
Configurable caps (e.g. surcharge ceiling) and automatic exemptions for debit cards and regulated regions where surcharging is prohibited
Disclosure text rendered on payment pages and printed on documents so the fee is visible before the customer commits
AL table extensions on Sales Header / Service Header carrying fee basis, fee type, and disclosure state
This is not an instant AppSource download. ECOSIRE builds the engine as a per-tenant AL extension, scoped to your Business Central environment, your card-brand mix, and the jurisdictions you actually trade in. We install it on your sandbox first, validate against your real payment and posting flows, then publish to production.
Under the hood it ships as a clean AL app: table extensions on Sales Header / Service Header to carry fee basis and disclosure state, a page extension that surfaces the calculated fee and disclosure text on payment and document pages, and event subscribers on posting routines that inject a separate, clearly-labelled fee line onto the invoice or receipt at the correct G/L account. Rules live in a configurable Surcharge Rule table — card brand, region/state, fee type, percentage or flat amount, cap, and exemption flags (debit cards, regulated regions) — all governed by a dedicated permission set.
Disclosure text renders on pay pages and prints on documents so the surcharge is visible before the customer commits, satisfying the core card-network disclosure requirement. Everything stays inside Business Central — no third-party middleware, no data leaving your tenant. Where you need it, we expose fee data over the BC REST/OData API for your storefront or Power Platform flows. ECOSIRE owns the build, the BC version upgrades, and ongoing support.
Wants to recover card processing cost on credit-card sales without falling foul of state-level surcharge bans or card-network caps, and needs the fee posted cleanly to its own G/L account for reconciliation.
Charges a convenience fee on certain online payment channels and needs region-aware rules plus customer-facing disclosure that holds up across the jurisdictions they sell into.
Needs the capability delivered as a governed per-tenant AL extension with a proper permission set and OData access — not a fragile manual customization — and wants ECOSIRE to own version upgrades.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Surcharge & Convenience Fee Engine for Business Central 模块 ZIP。
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中(或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传)。
激活开发者模式,打开应用程序,单击更新应用程序列表,搜索 Surcharge & Convenience Fee Engine for Business Central,然后按安装。
打开新菜单,粘贴您的 ECOSIRE 许可证密钥,连接任何外部凭据(Shopify、Amazon、Stripe 等),然后保存。
运行内置连接测试,同步前 10 条记录,并安排定期 cron。如果出现任何问题,请联系支持人员。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Card-brand and region/state-aware surcharge rules | ||||
| Enforced surcharge vs convenience-fee distinction with caps and exemptions | ||||
| Customer-facing disclosure text on pay pages and printed documents | ||||
| Automatic separate fee line at a dedicated G/L account via posting subscribers | ||||
| Built, installed, and supported on your tenant with BC-upgrade maintenance | ||||
| Tailored to your exact jurisdictions and card mix (no generic preset) | ||||
| BC REST/OData and Power Platform / Dataverse exposure for checkout |
It is build-to-order, not an instant AppSource download. After we confirm your card-brand mix, jurisdictions, and posting setup, a typical build is delivered in about 2 to 3 weeks: we develop the AL extension, install and validate it on your Business Central sandbox, then publish to production as a per-tenant extension once you sign off. Complex multi-region rule sets or storefront/Power Platform integration can extend the timeline, and we'll tell you upfront.
ECOSIRE does. Because this ships as a per-tenant AL extension we maintain, your defined support window covers configuration changes (new rules, caps, exemptions), bug fixes, and re-validation against Microsoft's BC major releases so the extension keeps installing cleanly after platform updates. We monitor your environment's update ring and adjust the app ahead of forced upgrades.
The engine enforces the controls compliance depends on — credit-only surcharging, debit exemption, configurable caps, region/state exemptions, and pre-commitment disclosure text. We configure those rules to the jurisdictions you specify, but ECOSIRE is not a law firm: you remain responsible for confirming the legality of surcharging in each region with your own counsel, and we update the rule table when you instruct us to.
A surcharge is assessed specifically on credit-card payments, is capped, and is prohibited on debit and in certain regions — the engine enforces all of that. A convenience fee is a flat charge for using an alternative payment channel and follows different rules. Conflating the two is a common compliance trap, so the engine treats them as distinct fee types with their own rule logic, caps, and disclosure.
Yes. Posting event subscribers inject the fee as a separate, clearly-labelled line at the G/L account you nominate, so it reconciles independently from product revenue. Everything runs inside your BC tenant — no third-party middleware and no payment data leaving Microsoft's environment. Fee data is only exposed externally if you ask us to publish the optional OData endpoint.
A per-tenant AL extension that adds compliant card surcharges or convenience fees to Business Central payments, with card-brand and region-aware rules, caps, exemptions, and disclosure text — built, installed, and supported by ECOSIRE.