Payment Terminal Connector (Adyen / Verifone / Ingenico)

Name: Payment Terminal Connector (Adyen / Verifone / Ingenico)
Brand: ECOSIRE
SKU: bc-payment-terminal-connector

核心功能

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

Event subscribers that finalize and post the payment on sale completion, writing standard bank and customer ledger entries

Dedicated permission set and field-level security so terminal operations are role-gated

Configurable terminal pairing per till / register with timeout, retry and graceful decline handling

Automatic reconciliation matching of terminal batch settlements against BC payment entries

Receipt data (masked card, scheme, auth code, AID/ARQC reference) returned to BC for printed and emailed receipts

Sandbox-first delivery validated against your acquirer's test terminals before production cutover

按需定制，全程代劳

无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。

您下单

以一次性构建价格开始。我们在启动时与您共同确定范围。

我们构建与安装

ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。

上线 + 支持

约 2–4 周内上线，并提供上线后的支持期。

关于此产品

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.

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.

你得到什么

A per-tenant Business Central AL extension (.app) built for your terminal vendor, acquirer and POS pages, installed on your tenant

Vendor-specific Terminal API integration codeunit (Adyen / Verifone / Ingenico) implementing the shared payment interface

Table and page extensions over your POS sale document plus the supporting payment-setup pages

A dedicated permission set and recommended role-center assignments for terminal operators and supervisors

Sandbox deployment, end-to-end test pass against acquirer test terminals, then supervised production cutover

Configuration of terminal pairing, EMV/regional parameters, tip and surcharge rules to your requirements

Admin and operator documentation plus a short handover walkthrough for your team

Post-go-live support window with bug fixes and compatibility maintenance under the agreed support terms

这是给谁的

Multi-store Retail Operations Manager

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.

Restaurant / Hospitality Owner

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.

BC Finance / Compliance Lead

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.

Payment Terminal Connector (Adyen / Verifone / Ingenico) 如何比较

标准	伊科西尔	定制建造	竞争对手
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	包含	部分支持	部分支持

关于Payment Terminal Connector (Adyen / Verifone / Ingenico)的常见问题

Is this an instant AppSource download?

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.

How long until it is live?

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.

How does this keep us PCI-out-of-scope?

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.

Which terminals and acquirers are supported?

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.

What ongoing support and updates do we get?

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.

Will it work with our existing POS and BC customizations?

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.