Quick facts
- Price
- $299.00 USD
- dynamics_365_business_central versions
- —
- Setup time
- 45 min
- License
- One-time perpetual
- Languages
- 11 languages
One-time Purchase
Level 2/3 Interchange Optimizer for Business Central
A per-tenant Business Central AL extension that automatically populates and transmits Level 2 (tax, PO) and Level 3 (line-item) data on B2B card transactions so qualifying payments earn lower interchange rates. Built, installed and supported by ECOSIRE on your environment.
$299.00USD
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Key Features
Auto-populates Level 2 data (sales tax amount, tax-exempt flag, customer PO/order number) from the posted Business Central document
Auto-assembles Level 3 line-item data (description, quantity, unit of measure, unit price, line total, optional commodity/product codes, freight) from Sales lines
Per-gateway L2/L3 field mapping module configured for your processor (Authorize.Net, Stripe, Worldpay, Cybersource or acquirer API)
B2B card detection via BIN/card-product code at authorization, routing only commercial/corporate/purchasing cards through the enhanced-data path
Table-extension and page-extension layer adding L2/L3 capture and status fields to Sales Orders and Posted Sales Invoices
Event-subscriber-driven payload assembly (e.g. OnAfterPostSalesDoc / payment-capture) with no modification to base application objects
Works on both open Sales Orders and Posted Sales Invoices, including payment capture against an existing authorization
Interchange-savings report plus an OData/Power BI-ready dataset showing qualified vs. unqualified card volume
Job Queue entry that retries enhanced-data submission and flags transactions that failed gateway L2/L3 validation
Dedicated permission set so finance and AP users get scoped access to optimizer setup and reports
AL test codeunits validating payload assembly and gateway field mapping against your real data shape
Optional Dataverse / Power Platform sync to surface savings metrics outside Business Central
Configuration page for tax mapping, UoM mapping and commodity-code defaults so qualification logic matches your catalog
About this Product
Commercial and corporate cards in Business Central often settle at the most expensive interchange tier simply because the transaction is submitted without the supplementary data card networks reward. Level 2 data (sales tax amount, tax-exempt status, customer PO/order number) and Level 3 data (per-line item descriptions, quantities, unit-of-measure, unit price, commodity codes, freight) signal a low-risk B2B purchase — and qualifying transactions can settle at meaningfully lower interchange rates.
Why Choose Level 2/3 Interchange Optimizer for Business Central
Auto-populates Level 2 data (sales tax amount, tax-exempt flag, customer PO/order number) from the posted Business Central document
Auto-assembles Level 3 line-item data (description, quantity, unit of measure, unit price, line total, optional commodity/product codes, freight) from Sales lines
Per-gateway L2/L3 field mapping module configured for your processor (Authorize.Net, Stripe, Worldpay, Cybersource or acquirer API)
B2B card detection via BIN/card-product code at authorization, routing only commercial/corporate/purchasing cards through the enhanced-data path
Table-extension and page-extension layer adding L2/L3 capture and status fields to Sales Orders and Posted Sales Invoices
Event-subscriber-driven payload assembly (e.g. OnAfterPostSalesDoc / payment-capture) with no modification to base application objects
This is a build-to-order AL extension, not an instant AppSource download. ECOSIRE builds it against your specific gateway and chart of accounts, installs it as a per-tenant extension on your Business Central environment (cloud or on-prem), and supports it after go-live.
What we build. A table-extension and page-extension layer captures the Level 2/3 fields on Sales Orders, Posted Sales Invoices and the payment record. An event subscriber (typically on OnAfterPostSalesDoc or the payment-capture flow of your connector) assembles the L2/L3 payload from the posted document lines — descriptions, quantities, UoM, line amounts, the document tax breakdown and the customer PO. A per-gateway field-mapping module translates that payload into the exact API schema your processor expects (Authorize.Net, Stripe, Worldpay, Cybersource or your acquirer's API), because every gateway names and validates these fields differently. B2B card detection inspects the card BIN / product code returned at authorization and routes only commercial/corporate/purchasing cards through the enhanced-data path, so consumer cards are left untouched. An Interchange Savings report and Power BI-ready dataset show qualified vs. unqualified volume.
Permission sets, a Job Queue entry for retrying enhanced-data submission, and AL test codeunits are included. Optional Dataverse / Power Platform sync surfaces the savings data outside BC. We do not control your card network's qualification rules — we make sure Business Central submits clean, complete L2/L3 data so your transactions are eligible for the better rate.
What you get
- A per-tenant Business Central AL extension (.app) built for your environment, installed by ECOSIRE on your tenant or sandbox
- Per-gateway field-mapping configuration matched to your specific payment processor's L2/L3 API schema
- Dedicated permission set(s) and Job Queue setup for retry and validation handling
- Interchange-savings report and an OData/Power BI-ready dataset for qualified-volume reporting
- AL test codeunits and a documented test run against your sandbox before production install
- Setup and admin documentation covering tax/UoM/commodity mapping and gateway credentials configuration
- Post-go-live support and a defined warranty period, with optional ongoing maintenance
Who this is for
B2B Finance / AP Manager
Runs high commercial-card volume and is frustrated that corporate and purchasing-card payments settle at the most expensive interchange tier. Wants Business Central to submit the L2/L3 data that qualifies those transactions for lower rates without changing how the team posts invoices.
Business Central Administrator / IT Lead
Owns the BC environment and the payment-connector integration. Needs the optimizer delivered as a clean per-tenant extension using event subscribers — no base-app modification, scoped permission sets, and a tested install path through sandbox before production.
Controller / Finance Director
Cares about measurable processing-cost reduction and audit trail. Wants the interchange-savings report and a Power BI dataset showing qualified vs. unqualified card volume so the savings from enhanced data are visible and defensible.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Level 2/3 Interchange Optimizer for Business Central module ZIP from your account dashboard.
Upload to Odoo
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Install the module
Activate Developer Mode, open Apps, click Update Apps List, search for Level 2/3 Interchange Optimizer for Business Central, and press Install.
Configure settings
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Verify & go live
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
How Level 2/3 Interchange Optimizer for Business Central Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Auto-populates L2/L3 data from posted BC documents | ||||
| Per-gateway field mapping configured for your processor | ||||
| B2B card detection via BIN/card-product routing | ||||
| Delivered as upgrade-safe per-tenant extension (no base-app changes) | ||||
| Interchange-savings reporting with Power BI / OData dataset | ||||
| Built, installed and supported on your environment by the vendor | ||||
| Tailored to your tax, UoM and commodity-code mapping | ||||
| AL test codeunits validated against your real data |
Frequently Asked Questions about Level 2/3 Interchange Optimizer for Business Central
+How long does delivery take, and what's the process?
This is built to order, so lead time depends on your gateway and catalog complexity. A typical engagement is roughly 2 to 4 weeks: a short discovery on your processor and document flow, build of the AL extension and per-gateway mapping, a tested install in your sandbox where we validate L2/L3 payloads against real documents, then a scheduled production install on your tenant. You'll have a confirmed timeline before we begin.
+How does ongoing support and updates work after go-live?
Every build includes a post-go-live support and warranty period for defects and gateway field-mapping fixes. Because it ships as a per-tenant extension, ECOSIRE updates it on your schedule — we test the .app against new Business Central release waves and adjust mappings if your processor changes its L2/L3 API. Optional ongoing maintenance covers proactive compatibility testing across BC updates and gateway changes.
+Will this actually lower my interchange rates, or just submit the data?
We make your transactions eligible for lower rates by submitting clean, complete, validated Level 2/3 data — that is the part Business Central controls. Final qualification is decided by the card networks and your acquirer against their rules. We do not control those rules and won't promise a specific basis-point figure, but the savings report shows exactly which transactions qualified so you can verify the impact with your processor.
+Does it modify the base Business Central application?
No. It's delivered as a per-tenant AL extension using table extensions, page extensions and event subscribers (for example on the post and payment-capture flows). Base application objects are not touched, which keeps you upgrade-safe across BC release waves and avoids conflicts with your existing payment connector.
+Which payment gateways and Business Central deployments are supported?
We build the field mapping for your specific processor — common targets include Authorize.Net, Stripe, Worldpay and Cybersource, or your acquirer's direct API. It works on Business Central cloud (SaaS) and supported on-prem versions. If your gateway exposes an L2/L3 enhanced-data API, we can map to it; tell us your processor during discovery and we'll confirm fit before any commitment.
Why Customers Trust ECOSIRE
SOC 2 Aligned
GDPR Compliant
Secure Stripe Payment
30-Day Money Back
Lifetime Updates
LGPL-3.0 License
Related Modules
Request a quote
Level 2/3 Interchange Optimizer for Business Central
A per-tenant Business Central AL extension that automatically populates and transmits Level 2 (tax, PO) and Level 3 (line-item) data on B2B card transactions so qualifying payments earn lower interchange rates. Built, installed and supported by ECOSIRE on your environment.
- Auto-populates Level 2 data (sales tax amount, tax-exempt flag, customer PO/order number) from the posted Business Central document
- Auto-assembles Level 3 line-item data (description, quantity, unit of measure, unit price, line total, optional commodity/product codes, freight) from Sales lines
- Per-gateway L2/L3 field mapping module configured for your processor (Authorize.Net, Stripe, Worldpay, Cybersource or acquirer API)
- B2B card detection via BIN/card-product code at authorization, routing only commercial/corporate/purchasing cards through the enhanced-data path