Tap Payments for WooCommerce

Recursos Principais

KNET, mada and Benefit local debit schemes presented natively at checkout per country (Kuwait, KSA, Bahrain)

International card payments plus an Apple Pay express button on cart, product and checkout pages

Full GCC multi-country coverage from a single Tap (goSell) merchant account and one gateway

Both goSell hosted-page redirect and embedded (on-site) card-element checkout flows supported

Registered as a native WooCommerce payment gateway (WC_Payment_Gateway) under WooCommerce > Settings > Payments

Server-to-server webhook sync with signature verification — order status never relies on the browser returning

Idempotent webhook handling so retried events (charge.succeeded) never double-complete or double-refund an order

Full and partial refunds plus authorize-and-capture, driven from the standard WooCommerce > Orders screen

HPOS / custom order tables (Order Data Storage) compatible — reads and writes the new order schema, not just post meta

WP-Cron reconciliation job that re-checks charge status for any order missing its webhook callback

Separate test and live API key fields with a sandbox toggle for safe pre-launch verification

WPML and WooCommerce multisite friendly, with per-store keys and translatable checkout labels

Feito sob encomenda, pronto para você

Sem configuração por conta própria — um app funcional criado, instalado e com suporte da ECOSIRE.

Você faz o pedido

Comece com um preço único de desenvolvimento. Definimos o escopo com você no início.

Nós criamos e instalamos

A ECOSIRE cria, configura e instala no seu WooCommerce.

No ar + suporte

Você entra no ar em cerca de 2–4 semanas, com um período de suporte pós-lançamento.

Sobre este Produto

Tap Payments for WooCommerce is a build-to-order payment gateway that gives GCC merchants full Gulf local-scheme coverage in a single WooCommerce checkout. One integration accepts KNET (Kuwait), mada (KSA), Benefit (Bahrain), international cards and Apple Pay — so you stop losing carts to shoppers who only pay with their local debit network.

This is not an instant marketplace download. ECOSIRE builds the plugin against your Tap (goSell) merchant account, installs it on your WordPress site, and supports it afterward. We register it as a proper WooCommerce payment gateway (a WC_Payment_Gateway subclass), wire the goSell hosted and embedded checkout flows, and verify server-to-server webhook sync so order status never depends on the customer's browser returning to the thank-you page.

The build is HPOS-aware — it reads and writes through WooCommerce's custom order tables (Order Data Storage) as well as legacy post meta, so your store stays future-proof. Charges, partial and full refunds, and captures are driven from the standard WooCommerce > Orders screen and mirror back to your Tap dashboard. Settings live under WooCommerce > Settings > Payments, with separate test and live API keys, configurable per-country scheme display, and an Apple Pay express button on cart and product pages.

We handle the unglamorous parts: idempotent webhook handling so a retried charge.succeeded never double-completes an order, signature verification on every callback, WP-Cron reconciliation for missed webhooks, and clean WPML / multisite behavior if you run multiple storefronts. You get a documented handover, a staging-first rollout, and a support window. Honest delivery applies — see the lead-time FAQ below.

O que você ganha

Custom Tap Payments gateway plugin built against your goSell merchant account and installed on your WordPress site

Staging-first deployment with end-to-end test transactions across KNET, mada, Benefit, cards and Apple Pay

Configured WooCommerce > Settings > Payments screen with test/live keys, sandbox toggle and per-country scheme display

Verified webhook endpoint (signature-checked, idempotent) plus a WP-Cron reconciliation fallback

Apple Pay domain verification and express-button placement on cart, product and checkout pages

Admin handover document covering settings, refund/capture workflow and webhook troubleshooting

A defined post-launch support window for fixes, WooCommerce/WordPress compatibility and minor adjustments

Para quem é isso

GCC multi-country online retailer

Sells into Kuwait, KSA, UAE and Bahrain and is losing checkouts because shoppers want to pay with KNET, mada or Benefit rather than only an international card. Needs every local scheme live in one WooCommerce gateway.

WooCommerce store owner switching from a hosted SaaS cart

Migrating to self-hosted WooCommerce and wants Tap (goSell) wired in properly — webhooks, refunds and HPOS compatibility included — without learning the Tap API or maintaining custom gateway code themselves.

Agency or developer serving a Gulf merchant

Building a client store and needs a production-grade, supported Tap integration with Apple Pay and embedded checkout, delivered with documentation and a support window instead of a brittle in-house bolt-on.

Como Tap Payments for WooCommerce se compara

Critério	ECOSIRE	Construção personalizada	Concorrente
Native KNET, mada and Benefit local-scheme coverage at checkout	Incluído	Suporte parcial	Suporte parcial
Apple Pay express button on cart and product pages	Incluído	Suporte parcial	Suporte parcial
Built, installed and supported on your site by the vendor	Incluído	Suporte parcial	Não incluído
HPOS / custom order tables compatibility verified	Incluído	Suporte parcial	Suporte parcial
Idempotent, signature-verified webhook sync with WP-Cron reconciliation	Incluído	Suporte parcial	Suporte parcial
Instant self-service marketplace download	Não incluído	Não incluído	Incluído
Customized to your exact GCC country and scheme mix	Incluído	Incluído	Não incluído
Refunds and captures from the standard WooCommerce Orders screen	Incluído	Suporte parcial	Incluído

Perguntas frequentes sobre Tap Payments for WooCommerce

How long until the gateway is live on my store?

This is a build-to-order plugin, not an instant download. After purchase we collect your Tap (goSell) merchant credentials and store details, build and configure the gateway, then deploy to a staging environment for end-to-end testing before going live. Typical delivery is a few business days, depending on how quickly your Tap account, Apple Pay domain verification and WordPress access are available. We confirm a specific lead time with you before we start.

What happens after launch — do I get support and updates?

Yes. Every build includes a defined post-launch support window during which we fix issues, keep the gateway compatible with new WooCommerce and WordPress releases (including HPOS changes), and make minor adjustments. Because the plugin is custom-built for your site rather than a mass-market marketplace listing, there is no public auto-update channel — updates are applied by ECOSIRE. Extended support and maintenance can be arranged.

Do I need my own Tap Payments (goSell) account?

Yes. You contract directly with Tap Payments for your merchant account, settlement and per-transaction pricing. ECOSIRE builds and connects the WooCommerce integration using your live and test API keys — we are the integration and support partner, not the payment processor, and we never take a cut of your transactions.

Does it work with HPOS and my existing theme or page builder?

Yes. The gateway is built against WooCommerce's High-Performance Order Storage (custom order tables) as well as legacy post meta, so it works whether or not HPOS is enabled. It registers as a standard WooCommerce payment gateway and renders through the normal checkout, so it is theme- and builder-agnostic. If you use the newer block-based Checkout, tell us during scoping so we target the block integration.

Will all the local schemes — KNET, mada, Benefit — and Apple Pay actually show at checkout?

Yes, subject to what your Tap merchant account is approved for. Tap enables schemes per country and per merchant, so KNET (Kuwait), mada (KSA) and Benefit (Bahrain) appear once they are active on your account. We configure the gateway to present the correct schemes by country and set up the Apple Pay express button with the required domain verification during the build.