Payment Terminal Connector (Adyen / Verifone / Ingenico)

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.