One payment layer that maps multiple gateways — Stripe, PayPal, Braintree and regional providers — into Dynamics 365 Business Central, with unified pay links, currency/region routing rules, and automated cross-gateway reconciliation. Built, installed as a per-tenant AL extension, and supported by ECOSIRE. One-time license from $499.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

One payment layer that maps multiple gateways — Stripe, PayPal, Braintree and regional providers — into Dynamics 365 Business Central, with unified pay links, currency/region routing rules, and automated cross-gateway reconciliation. Built, installed as a per-tenant AL extension, 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.
Companies that take payments across several regions usually end up with one gateway per country and no single view of money in. Multi-Gateway Payment Hub is a per-tenant AL extension that ECOSIRE builds, installs and supports directly on your Dynamics 365 Business Central environment. It adds one payment abstraction layer in front of Stripe, PayPal, Braintree and the regional gateways you actually use, so every sales document, posted invoice and Customer card speaks to a single, consistent interface.
Plug-in gateway architecture: each provider (Stripe, PayPal, Braintree, regional) is a codeunit implementing a shared AL `Payment Gateway` interface, so providers can be added or swapped without touching core logic
Unified Pay Link action added via page extensions on Sales Order, Sales Invoice and posted sales documents — one button regardless of the underlying gateway
Routing rules engine: a setup table keyed by currency code, country/region and amount band selects the correct gateway per transaction
Inbound webhook handling through a custom API page (REST/OData v4) that updates payment status and writes back to the source document
Automated cross-gateway reconciliation via a Job Queue entry that matches captured payments to Bank/Customer ledger entries
Refund initiation directly from the document, with the reversal posted back into the General Ledger and gateway
The extension ships a plug-in architecture: each gateway is implemented behind a shared AL interface (codeunit implementing a Payment Gateway interface), so adding or swapping a provider is a contained change, not a rewrite. Page extensions on Sales Invoice, Sales Order and the posted documents surface a unified "Pay Link" action, and routing rules — defined in a setup table keyed by currency, country/region code and amount band — decide which gateway handles each transaction. Webhook callbacks land via an API page (REST/OData v4) that updates payment status, and a Job Queue entry runs reconciliation that matches captured payments back to BC ledger entries across every gateway at once. Refunds and chargebacks are first-class: initiate a refund from the document, and the matching reversal flows back into the General Ledger.
Because this is build-to-order, nothing is fabricated to fit a generic AppSource listing. ECOSIRE scopes it to your gateways, your currencies, your chart of accounts and your permission model, then delivers it as a signed per-tenant extension installed on your sandbox first, then production. You get the AL source, dedicated permission sets, and a documented hand-over. There is no instant download — there is a real extension, built for your tenant, with a person behind it.
Owns the close across countries and is tired of logging into three gateway dashboards to reconcile. Wants every captured payment matched to BC ledger entries automatically, with mismatches flagged before month-end.
Responsible for the tenant and its extensions. Wants payment logic delivered as a clean per-tenant AL extension with proper permission sets and Isolated Storage for keys — not a pile of customizations bolted onto base objects.
Sends invoices that need to be paid fast in the customer's local method. Wants a single Pay Link on the document that automatically routes to the right gateway by currency and region without the team picking manually.
Compre a licença em ecosire.com e baixe o ZIP do módulo Multi-Gateway Payment Hub 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-Gateway Payment Hub 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 |
|---|---|---|---|---|
| Unifies multiple gateways behind one interface in BC | ||||
| Currency/region/amount routing rules engine | ||||
| Automated cross-gateway reconciliation to BC ledger | ||||
| Built and installed as a per-tenant AL extension for your tenant | ||||
| Scoped to your exact gateways, currencies and chart of accounts | ||||
| Full AL source code handed over to you | ||||
| Vendor-supported updates against BC major releases | ||||
| Refund and chargeback handling posted back to the GL | ||||
| Add a new/regional gateway without re-architecting |
No. Multi-Gateway Payment Hub is build-to-order. ECOSIRE scopes it to your specific gateways, currencies and chart of accounts, builds it in AL, and installs it as a signed per-tenant extension on your Business Central environment — sandbox first, then production. There is no public AppSource listing to click-install; you get a real extension built for your tenant.
Typical delivery is around 3 to 5 weeks from a confirmed scope, depending on how many gateways you operate and how complex your routing and posting rules are. We start with a short discovery to lock the gateway list, currencies and reconciliation logic, then build and test on your sandbox, then schedule the production install with you. The one-time build price is USD 499 for a standard scope; gateways or workflows beyond the standard set are quoted up front.
Secrets are stored using Business Central Isolated Storage, scoped to the extension — they are never written into ordinary table fields visible in the data. Access is further gated by dedicated permission sets, so only administrators can manage credentials while operators and reconcilers see only what they need.
Yes — that is the point of the plug-in architecture. Each provider is a codeunit implementing the same shared AL interface, so a regional or niche gateway with a documented REST API can be added as its own connector without disturbing the routing engine, the Pay Link action or reconciliation. We confirm the provider's API supports the operations we need during scoping.
Because you receive the full AL source and a per-tenant extension, you are never locked out. ECOSIRE offers ongoing support to recompile and re-test the extension against Business Central's twice-yearly major releases, add gateways, and adjust routing or posting rules as your business changes. Support terms are agreed separately from the one-time build; we hand over a runbook so your own admin can also manage day-to-day operation.
One payment layer that maps multiple gateways — Stripe, PayPal, Braintree and regional providers — into Dynamics 365 Business Central, with unified pay links, currency/region routing rules, and automated cross-gateway reconciliation. Built, installed as a per-tenant AL extension, and supported by ECOSIRE.