HyperPay Payment Gateway for Business Central

Key Features

High Mada approval-rate card acceptance with correct HyperPay brand routing for Saudi-issued cards

Apple Pay, STC Pay, and local wallet checkout flows surfaced inside Business Central sales documents

Tokenized recurring billing using HyperPay registration tokens stored against the BC Customer record

Full 3DS and OTP authentication, with asynchronous outcomes confirmed via webhook to a BC API page

Refund initiation from posted sales invoices with automatic reversal posting to BC ledgers

Settlement reconciliation via a scheduled Job Queue entry that matches HyperPay payouts to bank account ledger entries

Dedicated HyperPay Setup page for entity IDs, access token, environment (test/live), and brand toggles

Table and page extensions on Customer, Sales Header, and Payment Method to carry gateway references and statuses

AL codeunit using BC HttpClient against HyperPay COPYandPAY and Server-to-Server APIs over HTTPS

Event subscribers on sales posting and payment registration to trigger authorize, capture, and refund calls

ZATCA-aligned posting: payment references and statuses captured so e-invoicing flows stay consistent

Dedicated permission set and optional Dataverse/Power Platform exposure for Power Automate and Power BI

Secure credential handling via isolated storage, with separate test and live entity configuration

Audit trail of every gateway request, response code, and authentication result on the source document

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

HyperPay Payment Gateway for Business Central is a build-to-order AL extension that wires Dynamics 365 Business Central directly into HyperPay, a SAMA-licensed Saudi payment processor, so card and wallet payments are authorized, captured, refunded, and reconciled without leaving BC.

This is not an instant AppSource download. ECOSIRE builds the extension to your exact configuration, installs it as a per-tenant extension on your Business Central environment (SaaS or on-prem), and supports it after go-live. We tune it to your sales flow, chart of accounts, and ZATCA-aligned posting requirements.

Under the hood, the extension adds table and page extensions to Customer, Sales Header, and Payment Method, plus dedicated setup pages for HyperPay credentials (entity IDs, access token, and Mada/Apple Pay/STC Pay brand routing). An AL codeunit calls the HyperPay COPYandPAY and Server-to-Server APIs over HTTPS using BC's HttpClient, while event subscribers on posting routines (OnAfterPostSalesDoc and payment registration) trigger authorization, capture, and refund calls. Webhook callbacks land via an API page exposed on the BC OData/REST surface to confirm asynchronous 3DS/OTP outcomes.

You get high-Mada-approval card acceptance with the correct brand routing, Apple Pay and STC Pay and local wallet support, tokenized recurring billing using HyperPay registration tokens stored against the customer, full 3DS and OTP authentication handling, and refund plus reconciliation that posts back to BC ledgers and clears the payment in the bank account.

Permission sets, a Job Queue entry for settlement reconciliation, and optional Dataverse/Power Platform exposure are configured as part of delivery. ECOSIRE provides source-available AL, documentation, and a support window after handover.

What you get

Per-tenant AL extension (.app) built for your Business Central version and installed on your environment

HyperPay Setup page configured with your entity IDs, access token, and Mada/Apple Pay/STC Pay routing

Source-available AL code: table/page extensions, gateway codeunit, event subscribers, and API page

Dedicated permission set and Job Queue entry configured for settlement reconciliation

Sandbox validation in HyperPay test mode plus a live go-live cutover with a real low-value transaction

Configuration and operations guide covering setup, refunds, reconciliation, and webhook handling

Post-handover support window for fixes, BC update compatibility, and configuration assistance

Who this is for

Saudi Finance Manager

Owns the AR and reconciliation process and needs HyperPay settlements to match bank ledger entries inside Business Central, with refunds posting cleanly and an audit trail on every invoice.

E-commerce / Retail Operations Lead

Sells to Saudi consumers and demands high Mada approval rates plus Apple Pay and STC Pay at checkout, with tokenized recurring billing for subscriptions managed from the customer record.

BC Administrator / IT Manager

Runs the tenant and wants a clean per-tenant extension with a scoped permission set, isolated-storage credentials, webhook-based 3DS confirmation, and no fragile manual coding to maintain.

How HyperPay Payment Gateway for Business Central Compares

Criterion	ECOSIRE	Custom Build	Competitor
SAMA-licensed HyperPay integration with correct Mada/Apple Pay/STC Pay brand routing	Included	Partial support	Partial support
Installed and supported on your tenant as a per-tenant AL extension	Included	Partial support	Not included
Tokenized recurring billing tied to the BC Customer record	Included	Partial support	Partial support
3DS/OTP confirmed via webhook to a BC API page (server-to-server)	Included	Partial support	Partial support
Automatic refund posting and settlement reconciliation to BC ledgers	Included	Partial support	Partial support
Source-available AL code you can keep and extend	Included	Included	Not included
ZATCA-aligned posting and Saudi-first configuration out of the engagement	Included	Partial support	Partial support
Tailored to your chart of accounts and posting flow	Included	Included	Not included

Frequently Asked Questions about HyperPay Payment Gateway for Business Central

Is this a download from Microsoft AppSource?

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.

How long does delivery take?

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.

What happens with ongoing support and Business Central updates?

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.

Do I need my own HyperPay merchant account?

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.

How are 3DS and OTP authentication handled?

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.

Can recurring billing and refunds be automated?

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.