Magento 2 Tap Payments Gateway

主な機能

Unified GCC payment method exposing KNET, mada, Benefit, international cards and Apple Pay in a single Magento checkout selection

Tap hosted redirect flow and embedded card form (Tap web SDK / card-sdk) rendered as a Magento UI checkout component for in-page entry

Saved cards and tokenization via the Tap Customer/Token APIs so returning shoppers pay without re-entering card details (PCI scope minimized — card data never touches your server)

Apple Pay through Tap with domain verification and the Apple Pay JS session handled by the module

Full payment lifecycle mapped to Magento gateway commands (authorize, capture, sale, void, refund) via CommandPool and di.xml

Full and partial refunds and captures issued directly from Magento admin Credit Memos and Invoices, synced to Tap

Signed webhook controller that verifies Tap callbacks, updates order state through OrderRepositoryInterface service contracts, and is idempotent against retries

Encrypted API credentials in system.xml / core_config_data with sandbox and live toggles, plus admin ACL resources from acl.xml

Multi-store, multi-website and multi-currency aware (KWD, SAR, AED, BHD) with per-store-view enable/disable and method title

Configurable payment action (authorize-only vs authorize+capture), min/max order totals and allowed-country / specific-currency rules

Order status mapping (pending, processing, payment_review) and automatic invoice generation on successful capture

Structured debug logging to var/log plus a payment transactions audit trail viewable per order

Works on Magento Open Source and Adobe Commerce; clean upgrade-safe module under app/code with no core hacks

Sandbox-first delivery with a documented test plan covering KNET test cards, mada, Benefit and Apple Pay flows

受注生産、すべておまかせ

自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。

ご注文

一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。

構築とインストール

ECOSIRE がお客様の Magento 2 上で構築・設定・インストールします。

本番稼働 + サポート

約2〜4週間で稼働し、リリース後のサポート期間が付きます。

この製品について

This is a build-to-order Magento 2 payment integration for Tap Payments, engineered and installed by ECOSIRE on your own Magento Open Source or Adobe Commerce store. It is not an instant Marketplace download — we build the module against your store version, theme and checkout, then hand over a clean, upgrade-safe codebase under app/code/Ecosire/TapPayments.

The module is built on Magento's payment method facade and gateway command pool (Magento\Payment\Model\Method\Adapter, CommandPoolInterface, ValidatorPoolInterface), wired through di.xml so authorize, capture, refund and void map to discrete gateway commands. Configuration lives in system.xml with encrypted credentials in core_config_data, and all admin actions are gated by ACL resources in acl.xml.

Shoppers get a unified GCC checkout: KNET, mada, Benefit, international cards and Apple Pay, using either Tap's hosted redirect or the embedded card form (Tap's card-sdk / web SDK) rendered as a Magento UI checkout component. Saved cards and tokenization let returning customers pay in one tap. Webhooks are received by a custom controller that validates Tap signatures and updates order state via service contracts and the OrderRepositoryInterface, with idempotency to survive retries.

Operationally, your team issues full and partial refunds and captures directly from the admin (Credit Memo / Invoice), with every call logged. We deliver REST/webhook handling, Magento 2 multi-store and multi-currency support (KWD, SAR, AED, BHD), debug logging, and a sandbox-first rollout. Because we build it to order, the module fits your Magento version, your one-page or multi-step checkout, and your reconciliation needs — and ECOSIRE supports it after go-live.

得られるもの

A custom Magento 2 module (Ecosire_TapPayments) delivered as source under app/code, installed on your store by ECOSIRE

di.xml / system.xml / acl.xml / webapi/webhook wiring configured for your Magento version and theme

Sandbox configuration and a documented end-to-end test plan (KNET, mada, Benefit, cards, Apple Pay, refunds)

Production go-live: live Tap credentials wired, Apple Pay domain verified, webhooks registered and verified

Admin runbook covering refunds, captures, reconciliation and the debug/log locations

Post-launch support window with bug fixes and Magento/Tap compatibility assistance

これは誰のためのものですか

Kuwait & Bahrain ecommerce merchant

A Magento Open Source store in Kuwait or Bahrain that must accept KNET and Benefit (the dominant local debit rails) alongside cards, and wants a single checkout option rather than several disconnected plugins.

KSA / UAE Adobe Commerce retailer

A multi-store Adobe Commerce merchant across Saudi Arabia and the UAE needing mada, Apple Pay and multi-currency (SAR, AED) with admin-side refunds and reconciliation that survives platform upgrades.

Agency or in-house Magento lead

A technical lead who wants a clean, ACL-gated, upgrade-safe gateway module built to Magento standards (service contracts, gateway commands, no core edits) that their team can maintain and audit.

Magento 2 Tap Payments Gateway の比較方法

基準	エコシエール	カスタムビルド	競合他社	Magento 2 標準機能
KNET, mada, Benefit and Apple Pay in one unified checkout method	付属	部分的なサポート	部分的なサポート	含まれていない
Built and installed against your exact Magento version, theme and checkout	付属	付属	含まれていない	含まれていない
Saved cards / tokenization with minimal PCI scope	付属	部分的なサポート	部分的なサポート	含まれていない
Full and partial refunds and captures from Magento admin	付属	部分的なサポート	付属	含まれていない
Clean upgrade-safe module (service contracts, gateway commands, no core hacks)	付属	部分的なサポート	部分的なサポート	含まれていない
Vendor support and post-launch compatibility fixes for your install	付属	含まれていない	部分的なサポート	含まれていない
Instant self-service download with no build wait	含まれていない	含まれていない	付属	付属

Magento 2 Tap Payments Gateway に関するよくある質問

How long until the Tap Payments gateway is live on my store?

This is build-to-order, so we install on your Magento environment after purchase rather than shipping an instant download. Typical delivery is about 1 to 2 weeks: a few days to build and wire the module against your Magento version and theme, a sandbox round where you test KNET, mada, Benefit, cards and Apple Pay, then production go-live once your live Tap credentials and Apple Pay domain verification are in place. Timeline depends on your store's customizations and how quickly Tap activates your live account.

What ongoing support and updates do I get after launch?

Every build includes a post-launch support window for bug fixes and for compatibility issues against Magento and Tap API changes. Because the module is delivered as clean source under app/code with no core hacks, it survives standard Magento upgrades; if a major Magento or Tap SDK change requires adjustment, ECOSIRE handles it. We also provide an admin runbook so your team can manage refunds, captures and reconciliation independently, and you can engage us for extended maintenance beyond the included window.

Does this work on both Magento Open Source and Adobe Commerce?

Yes. The module is built on standard Magento payment APIs (the payment method adapter, gateway command pool, service contracts and UI checkout components), which are shared between Magento Open Source and Adobe Commerce. We build against your specific version (typically 2.4.x) and confirm compatibility with your checkout, whether default multi-step, one-page, or a third-party checkout.

How are refunds and saved cards handled?

Refunds (full and partial) and captures are issued directly from the Magento admin via Credit Memos and Invoices, which call the Tap API and update the order automatically. Saved cards use Tap tokenization: the card is stored as a token against the Tap customer, so returning shoppers can pay in one tap. Raw card data never touches your server, which keeps your PCI scope minimal.

Will it support KNET, mada, Benefit and Apple Pay in one checkout?

Yes. The module exposes a single Tap Payments method in checkout that routes to KNET, mada, Benefit, international cards or Apple Pay depending on what the shopper selects and what your Tap account is enabled for. You can use Tap's hosted redirect, the embedded in-page card form, or both. Method visibility, allowed currencies and per-store-view settings are configurable in the admin.