Some products need PayPal. Others need bank transfer, Stripe, or invoice on delivery. Here is how to give every WooCommerce product its own payment method — without breaking your checkout.
Most WooCommerce stores start with one or two payment gateways enabled globally — Stripe, PayPal, maybe a local bank transfer. That works until your catalog grows. Suddenly you have digital downloads that should never be paid by invoice, B2B products that should never go through credit card, or subscription products that only work with one specific processor. The default WooCommerce settings give you no way to scope a gateway to a single product, and the result is failed orders, support tickets, and lost revenue.
What "payment gateway per product" actually means
The idea is simple: every product in your catalog can declare which payment gateways are allowed for it. When a customer adds that product to the cart, only the allowed gateways appear at checkout. If they remove the product, the original set of gateways comes back. This gives you precise control over how each item is paid for, without writing a single line of code.
Why store owners need this in 2026
- **Compliance and fraud control**: some products (gift cards, prepaid services, high-ticket electronics) have a much higher chargeback rate on credit card. Limiting them to bank transfer or a verified wallet drops chargebacks dramatically.
- **B2B vs B2C in the same store**: wholesale customers expect invoice or SEPA; consumers expect Apple Pay and iDEAL. A single global gateway list cannot serve both.
- **Local payment methods**: if you sell to the Netherlands you need iDEAL, to Germany you need Klarna, to Brazil you need Pix. Per-product targeting lets you only show local methods where they make sense.
- **Subscription and recurring billing**: only certain gateways tokenize cards. Recurring products must restrict checkout to those.
How to set it up
Install **WooCommerce Payment Gateway Per Product** by Dreamfox Media. In every product's edit screen you get a new "Payment gateways" panel where you tick the methods allowed for that product. Save the product and the rule is live. There is no global configuration to maintain — the per-product setting always wins.
Handling the mixed cart
The hardest part of any per-product gateway logic is the mixed cart: what happens when a customer adds two products with conflicting payment rules? The plugin handles this by computing the **intersection** of allowed gateways across all cart items. If product A allows Stripe and PayPal, and product B only allows Stripe, the checkout will only show Stripe. If the intersection is empty, the customer is told which item is the conflict so they can remove it — instead of seeing an empty payment section and bouncing.
Free vs premium
The free version on WordPress.org gives you category-based gateway restriction. The premium version adds per-product rules, role-based rules, and the mixed-cart conflict resolver. For any store with more than a handful of SKUs the premium version pays for itself in the first month from recovered checkouts.
Common mistakes to avoid
- Hiding all gateways on a product (leaves the customer with no way to pay)
- Forgetting to re-test the cart after enabling a new gateway globally
- Not whitelisting your default gateway as a fallback on shipping-only products
Next step
If you also need to control which shipping method is available per product, pair this plugin with our [WooCommerce Shipping Gateway Per Product](/plugins/woocommerce-shipping-gateway-per-product). The two work together so checkout always shows the right options for what is actually in the cart.
