It is not an instant AppSource install — this is built to order for your environment. Typical delivery is about one working week depending on how many gateways you connect, whether EMV terminals are in scope, and your sandbox-to-production change windows. We build and test in your BC sandbox first, then install the per-tenant extension in production with you. If your governance requires an AppSource-track app instead of a per-tenant extension, we scope that variant up front.

ECOSIRE supports the extension after go-live. You receive the full AL source in a Git repository, so you are never locked in, and we provide a support window for fixes and for compatibility with Business Central's continuous monthly/major updates. Gateway API changes, new processors, additional payment workflows or Power Platform integrations are handled as scoped enhancements. We can also operate it under a retainer if you prefer hands-off maintenance.

No. Payment methods are tokenized at the gateway, and only the token plus non-sensitive metadata are stored. Full PAN and bank-account numbers never touch the BC database, which keeps your Business Central environment out of most PCI DSS scope. Hosted pay-links and terminal flows keep card entry on PCI-validated infrastructure.

Yes. The abstraction layer is designed so you can route different customers, currencies or transaction types to different processors — for example settling B2B Level 3 card volume through CardConnect while running ACH or subscription cards through Stripe — all behind one Business Central workflow. This is the lever that lets you negotiate interchange and switch processors without re-training AR.

Event subscribers on the posting routines capture transactions against the originating Sales Invoice or Cash Receipt, and a Job Queue entry ingests gateway webhooks for authorizations, captures, refunds, disputes and ACH return codes. Each event is mapped back to the correct ledger entry, so your GL stays reconciled automatically rather than through a manual import.