HyperPay Payment Gateway for Business Central

No. This is a build-to-order extension. ECOSIRE builds it to your configuration, installs it as a per-tenant extension on your Business Central environment, and supports it after go-live. There is no instant AppSource listing to download.

Typical delivery is about 2 to 3 weeks from kickoff. That covers requirements, building the AL extension, HyperPay sandbox validation, installation on your tenant, and a supervised live cutover with a real low-value test transaction. Complex chart-of-account or multi-entity setups can extend this, and we confirm the timeline in writing before we start.

The price includes a post-handover support window for fixes and configuration help. Because Microsoft ships BC major updates twice a year, we offer an ongoing maintenance arrangement to keep the extension compatible and re-validate the HyperPay integration after each update. You receive source-available AL either way, so you are never locked out of your own code.

Yes. You contract directly with HyperPay (a SAMA-licensed processor) for your merchant account, entity IDs, and access token. ECOSIRE configures those credentials securely in the BC extension using isolated storage and routes the correct brands for Mada, Apple Pay, and STC Pay.

The extension initiates payments through HyperPay's APIs and handles 3DS and OTP challenges. Asynchronous authentication outcomes are confirmed via a webhook callback that lands on a Business Central API page, so the sales document status only updates once the authentication result is verified server-to-server.

Yes. Recurring billing uses HyperPay registration tokens stored against the BC Customer, so subsequent charges run without re-entering card data. Refunds are initiated from the posted sales invoice and post a reversal to your ledgers, and a Job Queue entry reconciles HyperPay settlements against bank account ledger entries.