Tap Payments Connector (GCC)

Key Features

Tap-hosted pay link generated from Posted Sales Invoice and Sales Invoice pages via an AL page-extension action

Full GCC scheme support — KNET, mada, Visa, Mastercard and Apple Pay through the Tap Charge API

Webhook receiver that captures Tap charge events and verifies them against the Tap API before posting

Job queue entry that polls pending charges and posts cash receipts on a schedule you control

Automatic reconciliation — captured payments apply against the originating customer ledger entry, closing the invoice

Refund handling from a credit-memo action that calls the Tap refund endpoint and reverses the application

Multi-currency support across KWD, SAR, AED, BHD, QAR and OMR so receipt currency matches the charge

Tap API secret keys stored in Business Central isolated storage, never in a plain table field

Dedicated permission sets so finance users can reconcile without holding gateway credentials

Charge log table with status, Tap charge id, scheme and timestamps for full audit traceability

Sandbox and live key separation with a guarded production cutover

Upgrade-safe per-tenant extension — table/page extensions and event subscribers only, no base-app code changes

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

Collect Tap Payments directly against Business Central invoices

Microsoft Dynamics 365 Business Central has no native Tap Payments integration. GCC merchants either export invoices to a separate Tap dashboard and re-key settlements, or they pay an external developer to wire it up. This extension closes that gap as a per-tenant AL extension that ECOSIRE builds, installs and supports on your Business Central environment.

We add a Tap Payments setup page (encrypted secret keys held in isolated storage), and extend the Posted Sales Invoice and Sales Invoice pages with a "Generate Pay Link" action. The action calls the Tap Charge API and writes back a hosted payment URL that you embed in the emailed PDF or send by SMS/WhatsApp. Your customer pays via KNET, mada, Visa, Mastercard or Apple Pay; Tap fires a webhook our Azure-fronted endpoint receives.

A job queue entry polls and verifies charge status, then posts a Cash Receipt that applies against the originating customer ledger entry — closing the invoice automatically. Refunds are issued from a posted credit memo action that calls the Tap refund endpoint and reverses the application. Multi-currency is honored end to end (KWD, SAR, AED, BHD, QAR, OMR) so the receipt currency matches the charge.

This is honest build-to-order: there is no instant AppSource download. After purchase we scope your Tap account, currencies and reconciliation rules, build against your tenant, install the signed extension, configure permission sets, and run a sandbox-to-production cutover with you. You own a clean, upgrade-safe AL extension — not a brittle customization buried in the base app.

What you get

A signed per-tenant AL extension (.app) built for your Business Central version and installed on your tenant

Tap Payments setup page with isolated-storage key handling and sandbox/live toggle

Page extensions adding pay-link, status and refund actions to sales invoice documents

Webhook endpoint and job queue configuration for capture and reconciliation

Permission sets for gateway admin and finance reconciliation roles

Sandbox validation pass plus a documented production go-live cutover with ECOSIRE

Configuration and operations guide covering setup, refunds and troubleshooting

Post-go-live support window with bug fixes and Business Central update compatibility checks

Who this is for

GCC merchant finance manager

Runs collections in Kuwait, KSA, UAE, Bahrain, Qatar or Oman and wants customers to pay KNET, mada or card straight from the invoice instead of re-keying settlements from the Tap dashboard.

Business Central administrator

Owns the tenant and needs a clean, upgrade-safe extension with proper permission sets and isolated-storage secrets — not an unsupported base-app customization that breaks at the next Microsoft update.

Accounts receivable accountant

Spends hours matching Tap settlements to open invoices; wants captured payments to auto-apply against the right customer ledger entry so invoices close themselves and refunds reverse cleanly.

How Tap Payments Connector (GCC) Compares

Criterion	ECOSIRE	Custom Build	Competitor
Tap pay link generated on the invoice document	Included	Partial support	Partial support
KNET and mada scheme support out of the box	Included	Partial support	Partial support
Automatic reconciliation to the customer ledger entry	Included	Partial support	Partial support
Multi-currency GCC settlement (KWD, SAR, AED, BHD, QAR, OMR)	Included	Partial support	Partial support
Built, installed and supported on your specific tenant	Included	Included	Not included
Upgrade-safe per-tenant AL extension (no base-app changes)	Included	Partial support	Included
Secret keys held in isolated storage with scoped permission sets	Included	Partial support	Partial support
Refund handling tied to BC credit memos	Included	Partial support	Partial support

Frequently Asked Questions about Tap Payments Connector (GCC)

Is this an instant download from Microsoft AppSource?

No. This is a build-to-order extension. There is no instant AppSource install. After purchase ECOSIRE scopes your Tap account, currencies and reconciliation rules, builds the AL extension against your specific Business Central version, installs it as a signed per-tenant extension, and runs a sandbox-to-production cutover with you.

How long until it is live on our environment?

Typical delivery is two to four weeks from when you provide Tap sandbox/live API keys and a sandbox tenant. Timing depends on your currency mix, the document types you want pay links on, and any custom reconciliation rules. We confirm a firm date during scoping before any build work starts.

Who supports it and what about Business Central updates?

ECOSIRE supports it directly. The price includes a post-go-live support window for bug fixes. Because it is a per-tenant AL extension using only table/page extensions and event subscribers, it is upgrade-safe by design; we validate compatibility against Microsoft's major Business Central releases and ship a recompiled version if a release ever requires it. Ongoing maintenance plans are available.

Where are our Tap API keys stored?

Secret keys are held in Business Central isolated storage, never in a plain table field exposed to users. We provision dedicated permission sets so finance users can reconcile and issue refunds without ever holding the gateway credentials, and we keep sandbox and live keys separated with a guarded production cutover.

Can it reconcile and refund automatically, or just create pay links?

Both. A job queue entry polls pending Tap charges, verifies them via the Tap API, and posts a cash receipt that applies against the originating customer ledger entry — closing the invoice. Refunds are issued from a posted credit memo action that calls the Tap refund endpoint and reverses the application, all logged in a dedicated charge table.