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. One-time license from $399.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

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.
Sem pagamento agora. Isto envia um pedido de orçamento à nossa equipe — responderemos por e-mail com preços e próximos passos.
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.
Routing Rules setup table: map currency, region, card scheme and amount band to a preferred acquirer/MID, with priority ordering and fallback chains
Per-currency/region acquirer scoring that factors recent decline rate so routing adapts to live acceptance performance
Multi-MID management: register, enable/disable, and assign multiple merchant IDs per acquirer with credentials stored via Isolated Storage
Dynamic currency conversion at checkout — present the buyer's local currency and lock the quoted rate for the transaction
FX rate locking captured on the document, with realized gain/loss posted to configurable G/L accounts on settlement
Decline-recovery retry routing: failed authorizations automatically re-attempt against the next-best MID via the Job Queue
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.
Compre a licença em ecosire.com e baixe o ZIP do módulo Multi-Currency Payment Routing & FX for Business Central no painel da sua conta.
Extraia o ZIP em sua pasta de complementos personalizados do Odoo no servidor (ou faça upload via Aplicativos > Instalar do arquivo em Odoo.sh/runbot).
Ative o modo de desenvolvedor, abra Aplicativos, clique em Atualizar lista de aplicativos, procure por Multi-Currency Payment Routing & FX for Business Central e pressione Instalar.
Abra o novo menu, cole sua chave de licença ECOSIRE, conecte quaisquer credenciais externas (Shopify, Amazon, Stripe, etc.) e salve.
Execute o teste de conexão integrado, sincronize seus primeiros 10 registros e agende o cron recorrente. Entre em contato com o suporte se algo falhar.
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| 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.