Tap Payments Connector (GCC)

Name: Tap Payments Connector (GCC)
Brand: ECOSIRE
SKU: d365bc-tap-payments

核心功能

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

按需定制，全程代劳

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

您下单

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

我们构建与安装

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

上线 + 支持

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

关于此产品

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.

你得到什么

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

这是给谁的

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.

Tap Payments Connector (GCC) 如何比较

标准	伊科西尔	定制建造	竞争对手
Tap pay link generated on the invoice document	包含	部分支持	部分支持
KNET and mada scheme support out of the box	包含	部分支持	部分支持
Automatic reconciliation to the customer ledger entry	包含	部分支持	部分支持
Multi-currency GCC settlement (KWD, SAR, AED, BHD, QAR, OMR)	包含	部分支持	部分支持
Built, installed and supported on your specific tenant	包含	包含	不包括在内
Upgrade-safe per-tenant AL extension (no base-app changes)	包含	部分支持	包含
Secret keys held in isolated storage with scoped permission sets	包含	部分支持	部分支持
Refund handling tied to BC credit memos	包含	部分支持	部分支持

关于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.