A per-tenant Business Central extension that routes each payment to the best acquirer by currency and region, manages multiple MIDs, locks FX rates, posts realized gain/loss, and retries declined cross-border transactions — built, installed, and supported by ECOSIRE. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $399.00 USD; request a quote for a scoped proposal.
示意预览A per-tenant Business Central extension that routes each payment to the best acquirer by currency and region, manages multiple MIDs, locks FX rates, posts realized gain/loss, and retries declined cross-border transactions — built, installed, and supported by ECOSIRE.
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
以一次性构建价格开始。我们在启动时与您共同确定范围。
ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。
约 2–4 周内上线,并提供上线后的支持期。
Cross-border card acceptance leaks money in two places at once: declines from acquirers that don't process a given currency or region well, and FX cost from converting at the wrong rate at the wrong time. Business Central's native Currencies, Currency Exchange Rates, and payment-registration pages handle the accounting side, but they have no concept of acquirer routing, multi-MID selection, or decline recovery. This extension fills that gap.
ECOSIRE builds this as a per-tenant AL extension installed directly onto your Business Central environment (cloud SaaS or on-prem). We add table and page extensions to your payment and customer documents, a Routing Rules setup table (currency, region, card scheme, amount band → preferred MID), and event subscribers on the posting and payment-application codeunits so routing decisions are captured and FX is booked correctly. Acquirer calls run through a configurable connector to your chosen gateway/PSP (for example Stripe, Adyen, or Checkout.com) over its REST API, with retries handled by the BC Job Queue.
When a payment is initiated, the extension scores eligible MIDs by currency/region fit and recent decline rate, presents (or auto-applies) dynamic currency conversion at checkout, locks the FX rate for the transaction, and on settlement posts the realized FX gain/loss to the G/L accounts you specify. Declined authorizations are re-routed to the next-best acquirer automatically. Everything is permission-set gated, telemetry-logged, and exposed via the BC REST/OData API and optionally surfaced in Power BI or Dataverse.
You receive a working, documented extension on your tenant — not a starter template. ECOSIRE handles design, AL development, installation, UAT, and ongoing support.
Sells in multiple currencies and watches cross-border decline rates and FX cost erode margin. Wants each payment routed to the acquirer that accepts it cheapest, with FX gain/loss landing automatically in the correct G/L accounts.
Owns the tenant and needs new capability delivered as a clean per-tenant extension — no base-app modifications, proper permission sets, Job Queue jobs, and telemetry — installable on a sandbox first and supportable long-term.
Manages multiple MIDs across PSPs and reconciles settlement. Needs visibility into which MID processed each transaction, locked rates, retry outcomes, and exportable data for Power BI reporting.
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Per-currency/region acquirer routing across multiple MIDs | 包含 | 部分支持 | 部分支持 | |
| FX rate locking with realized gain/loss posted to G/L | 包含 | 部分支持 | 部分支持 | |
| Decline-recovery retry routing to next-best acquirer | 包含 | 部分支持 | 不包括在内 | |
| Delivered as upgrade-safe per-tenant AL extension (no base-app changes) | 包含 | 部分支持 | 包含 | |
| Built, installed and supported on your specific tenant/PSP | 包含 | 包含 | 不包括在内 | |
| Routing/FX data exposed via REST/OData for Power BI & Dataverse | 包含 | 部分支持 | 部分支持 | |
| Tailored to your exact currencies, regions, rules and G/L mapping | 包含 | 包含 | 不包括在内 |
It is build-to-order. After a short scoping call we confirm your currencies, regions, PSP/acquirers and G/L mapping, then develop the AL extension and install it first on your Business Central sandbox for UAT and finally on production. Typical delivery is about 3 to 5 weeks depending on how many acquirers and routing rules you need and PSP credential availability. You get a working extension on your own tenant — there is no instant AppSource download involved.
Yes. The build includes a post-launch support window for fixes and adjustments. Because Business Central ships major updates twice a year, we offer a maintenance arrangement to recompile and re-test the extension against new BC releases, add acquirers or routing rules, and handle PSP API changes. Support terms are agreed before go-live.
No. It is delivered as a per-tenant extension using table extensions, page extensions and event subscribers. The base app is untouched, which keeps your environment upgrade-safe and your tenant clean.
The connector is built for your chosen PSP — commonly Stripe, Adyen or Checkout.com — calling its REST API. If you use multiple PSPs we configure multi-MID routing across them. Tell us your acquirers during scoping and we build the connector and routing rules to match; additional acquirers can be added later under the maintenance arrangement.
Yes. Routing outcomes, chosen MID, locked rates and FX gain/loss are exposed through the BC REST/OData API and can be surfaced in Power BI or pushed into Dataverse for Power Automate flows. Every routing decision and retry is also logged to Application Insights telemetry.
A per-tenant Business Central extension that routes each payment to the best acquirer by currency and region, manages multiple MIDs, locks FX rates, posts realized gain/loss, and retries declined cross-border transactions — built, installed, and supported by ECOSIRE.