A build-to-order Business Central extension that links your POS to Adyen, Verifone or Ingenico card terminals through a device-agnostic Terminal API for fast, EMV-secure, semi-integrated in-store payments. One-time license from $499.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

A build-to-order Business Central extension that links your POS to Adyen, Verifone or Ingenico card terminals through a device-agnostic Terminal API for fast, EMV-secure, semi-integrated in-store payments.
Sin pago ahora. Esto envía una solicitud de presupuesto a nuestro equipo; te responderemos por correo con precios y próximos pasos.
Most Business Central POS deployments still capture in-store card payments manually: a cashier reads the total off the screen, keys it into a standalone terminal, then types the approval code back into BC. That double entry is slow, error-prone, and keeps your BC environment squarely inside PCI scope.
Device-agnostic Terminal API integration with a swappable AL interface codeunit per vendor (Adyen, Verifone, Ingenico)
EMV chip, contactless (NFC) and mobile wallet (Apple Pay / Google Pay) acceptance routed entirely through the terminal
Semi-integrated flow that keeps cardholder data off Business Central and your network, holding the BC tenant PCI-out-of-scope
One-button Authorize, Capture, Refund and Reversal driven from the POS sale screen
Tip-on-terminal prompts captured back onto the BC sale line, and configurable surcharge / convenience-fee support
Table and page extensions over your POS sale document storing approval token, masked PAN, scheme, auth code and terminal ID
The Payment Terminal Connector is a per-tenant AL extension that ECOSIRE builds, installs and supports directly on your Business Central environment. It wires your POS sale lines to a physical card terminal — Adyen, Verifone, or Ingenico — through a device-agnostic Terminal API so the cashier presses one button and the terminal does the rest.
Because the flow is semi-integrated, the cardholder data never touches Business Central or your network. BC sends an amount and receives back an approval token, masked PAN, scheme and auth code — keeping your environment PCI-out-of-scope under SAQ C-VT / P2PE depending on your acquirer setup.
The extension ships as table and page extensions over your POS sale document, an interface-based codeunit abstraction so each terminal vendor is a swappable implementation, event subscribers that post payments on sale finalization, and a dedicated permission set. Auth, capture, refund and reversal are all driven from the POS screen, with tip-on-terminal and surcharge captured back onto the BC sale line. Reconciliation entries flow into your bank and ledger exactly like any other BC payment.
Delivered as a per-tenant extension (not a public AppSource listing) so we can match your terminal model, acquirer, regional EMV config and existing POS pages precisely. ECOSIRE scopes the build with you, develops and tests it against your acquirer's test terminals, deploys to sandbox then production, and supports it after go-live. Honest lead time, real engineers, no black box.
Runs several BC-powered stores and needs every till to take chip, contactless and wallet payments through certified terminals without cashiers re-keying totals or chasing mismatched batch settlements.
Wants pay-at-table or counter terminals that prompt for tips on the device, apply surcharges where allowed, and post cleanly to Business Central so daily reconciliation is one click, not a spreadsheet.
Needs in-store card acceptance to stay PCI-out-of-scope, with cardholder data never entering BC, role-gated terminal operations, and auth/refund/reversal fully auditable in the ledger.
Compre la licencia en ecosire.com y descargue el módulo ZIP Payment Terminal Connector (Adyen / Verifone / Ingenico) desde el panel de su cuenta.
Extraiga el ZIP en su carpeta de complementos personalizados de Odoo en el servidor (o cárguelo a través de Aplicaciones > Instalar desde archivo en Odoo.sh/runbot).
Active el modo de desarrollador, abra Aplicaciones, haga clic en Actualizar lista de aplicaciones, busque Payment Terminal Connector (Adyen / Verifone / Ingenico) y presione Instalar.
Abra el nuevo menú, pegue su clave de licencia de ECOSIRE, conecte cualquier credencial externa (Shopify, Amazon, Stripe, etc.) y guarde.
Ejecute la prueba de conexión integrada, sincronice sus primeros 10 registros y programe el cron recurrente. Póngase en contacto con el soporte si algo falla.
| Criterio | ECOSIRE | Construcción personalizada | Competidor | Odoo Nativo |
|---|---|---|---|---|
| Device-agnostic Terminal API (Adyen / Verifone / Ingenico) | ||||
| Semi-integrated, PCI-out-of-scope payment flow | ||||
| Auth, capture, refund and reversal from the BC POS screen | ||||
| Tip-on-terminal and surcharge captured back to the BC sale line | ||||
| Matched to your exact terminal, acquirer, EMV region and POS pages | ||||
| Built, installed and supported on your tenant by the vendor | ||||
| Automatic batch-settlement reconciliation into BC ledger entries |
No. This is a build-to-order, per-tenant Business Central extension. We deliberately deliver it as a per-tenant AL extension rather than a public AppSource app so we can match your exact terminal model, acquirer, regional EMV configuration and existing POS pages. ECOSIRE builds it, installs it on your sandbox and production environments, and supports it.
After scoping, a typical build, sandbox test pass against your acquirer's test terminals, and supervised production cutover runs about 3 to 5 weeks. The main variables are your acquirer's terminal certification timeline and how customized your current POS pages are. We confirm a firm date during scoping before any work starts.
The integration is semi-integrated: Business Central sends only an amount and reference to the terminal, and the terminal handles all card capture, encryption and transmission to the acquirer. Cardholder data never passes through BC or your server. BC only stores non-sensitive results — masked PAN, scheme, auth code and an approval token. Depending on your acquirer and deployment this typically maps to SAQ C-VT or P2PE; we align the build to your acquirer's requirements but final PCI attestation is between you and your acquirer.
The extension uses a device-agnostic Terminal API with a swappable vendor codeunit, so Adyen, Verifone and Ingenico terminals are all supported, and additional models can be added. We target your specific terminal family and acquirer during the build. If you tell us your hardware and acquirer up front, we confirm compatibility during scoping.
After go-live you get a support window covering bug fixes and compatibility maintenance as Microsoft ships new Business Central major releases and as your terminal vendor updates their Terminal API. Because it is a per-tenant extension we can patch and redeploy it to your tenant directly. Enhancements beyond the original scope (new terminal vendors, new payment features) are quoted separately.
Yes — that is precisely why it is build-to-order. We extend your existing POS sale document with table and page extensions and hook posting through event subscribers rather than replacing your flow, so it coexists with your current customizations. We review your environment during scoping to confirm there are no conflicts before development begins.
A build-to-order Business Central extension that links your POS to Adyen, Verifone or Ingenico card terminals through a device-agnostic Terminal API for fast, EMV-secure, semi-integrated in-store payments.