PaymentHood woocommerce payments

Offering more than one way to pay lifts conversion — some customers reach for a card, some a wallet, some a local method they trust. WooCommerce supports multiple payment gateways at once. The real question is how to manage several of them without ending up with a plugin per provider.

Enabling multiple gateways the standard way

  1. Install each provider’s pluginPlugins → Add New Plugin, one per gateway.
  2. Configure each under WooCommerce → Settings → Payments (API keys, display name, currency).
  3. Enable the ones you want. They appear at checkout in the order shown on that Payments screen — drag to reorder.

Customers then choose their method at checkout. This works, and for two or three gateways it’s perfectly fine.

Where it starts to hurt

WooCommerce lets you list multiple gateways, but it gives you nothing to manage them as a group. There’s no built-in way to:

  • Route automatically — send ZAR to one provider, NGN to another, cards to a third — without branching logic somewhere.
  • Fail over — if your only card provider has an outage, those sales are gone until they recover.
  • Reconcile in one place — every provider settles in its own report and format.

And operationally, each gateway is its own plugin: its own updates, its own occasional breakage, its own security surface. Enable too many and checkout gets cluttered, which hurts conversion instead of helping it.

The one-plugin approach

Instead of a plugin per gateway, connect WooCommerce to many providers through a single plugin (this is what payment orchestration does). You still offer several methods at checkout, but:

  • One plugin to install and keep updated, not five.
  • Add or switch providers from a dashboard — no new installation.
  • Automatic routing and failover across providers.
  • One reconciliation view instead of five settlement reports.

Choosing which provider handles a payment

With a single orchestration layer you get an actual decision point. You can:

  • Route by rule — currency, country, or payment method decides the provider.
  • Fail over — a technical decline retries through another provider instead of showing the customer an error.
  • Still let the customer choose among the methods you present, when that’s what you want.

The difference from stacking plugins is that the decision lives in configuration you control, not scattered across separate integrations.

Where PaymentHood fits

PaymentHood connects WooCommerce to 36+ payment providers through one free, open-source plugin — with routing, automatic failover, webhook verification and one reconciliation view. You offer as many methods as you like at checkout while maintaining a single integration, and you add or switch providers from a dashboard rather than in code.

See the WooCommerce integration or the full provider directory.

One integration, every payment provider

PaymentHood gives you routing, failover, idempotency and webhook verification across 36+ providers — without rebuilding any of it per provider.