Documentation & Setup Guide

Smart Payment Gateway Optimizer for WooCommerce helps you control and optimize how payment gateways are presented and used during checkout.

You can create rules to:

• Prioritize payment gateways.
• Sort gateways dynamically.
• Hide or show payment gateways.
• Recommend specific payment methods.
• Apply conditional payment gateway fees.
• Target rules based on cart and customer conditions.
• Track gateway revenue and fees.
• Monitor successful and failed payments.
• Analyze gateway performance.
• Measure rule performance.
• Identify expensive or underperforming gateways.
• Improve your payment gateway strategy.

The plugin works alongside your existing WooCommerce payment gateways. It does not replace or create payment gateways.

1. Requirements

Before installing the plugin, make sure your store has:

• WordPress installed and configured.
• WooCommerce installed and active.
• At least one WooCommerce payment gateway configured.
• Administrator or Shop Manager access to WordPress.
• A valid plugin ZIP package.

For the best experience, keep WordPress and WooCommerce updated and test major changes on a staging site before applying them to a production store.

WooCommerce recommends keeping the store environment compatible with the current supported WooCommerce version.

2. How to Download the Plugin

From WooCommerce.com

If you purchased the plugin through WooCommerce.com:

1. Log in to your WooCommerce.com account.
2. Open your My Subscriptions or downloads area.
3. Locate Smart Payment Gateway Optimizer for WooCommerce.
4. Select the download option.
5. Download the plugin .zip file to your computer.

Do not extract the ZIP file before uploading it to WordPress.

WooCommerce supports downloading extensions as ZIP packages for manual installation.

Automatic Installation

If the plugin is available through your connected WooCommerce.com store, you may also be able to install it directly through:

WordPress Admin → WooCommerce → Extensions → My Subscriptions

Locate the plugin and select Install.

Automatic installation requires the appropriate WooCommerce.com connection/update functionality.

3. How to Install the Plugin

Method 1 — Install Using WordPress Admin

This is the recommended manual installation method.

Step 1: Open Plugins

From WordPress Admin, go to:

Plugins → Add New Plugin

Step 2: Upload the Plugin

Click:

Upload Plugin

Step 3: Select the ZIP File

Click Choose File and select the downloaded plugin ZIP file.

For example:

smart-payment-gateway-optimizer-for-woocommerce.zip

Step 4: Install

Click:

Install Now

WordPress will upload and install the plugin.

Step 5: Activate

After installation is complete, click:

Activate Plugin

The plugin is now active.

This follows the standard WordPress/WooCommerce extension upload process.

4. How to Verify Installation

After activation:

1. Go to Plugins → Installed Plugins.
2. Find Smart Payment Gateway Optimizer for WooCommerce.
3. Confirm that the plugin is marked as Active.

The plugin also provides a Settings action from the Plugins screen for quick access to its configuration.

5. How to Find Plugin Settings

After activating the plugin, go to:

WooCommerce → Payment Gateway Optimizer

The plugin dashboard contains the main management interface.

You can also use the Settings link displayed on the plugin’s row under:

Plugins → Installed Plugins

6. Before You Configure the Plugin

Before creating optimization rules, make sure your payment gateways are already configured.

Go to:

WooCommerce → Settings → Payments

Configure and enable the payment gateways you want customers to use.

For example:

• Credit/Debit Card
• PayPal
• Stripe
• Bank Transfer
• Cash on Delivery
• Local payment gateways
• Other supported third-party gateways

The Smart Payment Gateway Optimizer does not replace these gateways. It works with the gateways already available in your WooCommerce checkout.

7. Plugin Configuration Overview

The plugin is organized into dedicated tabs so that payment gateway management, rules, analytics, and optimization settings can be configured separately.

The main areas are:

1. Dashboard
2. Gateway Rules
3. Fees
4. Gateway Sorting
5. Gateway Visibility
6. Recommendations
7. Scheduling
8. Analytics
9. General Settings
10. Help & Support

The exact tabs displayed may depend on the installed plugin version and enabled functionality.

8. Dashboard

Purpose

The Dashboard gives you a quick overview of payment gateway performance and optimization results.

It is the main starting point after installing the plugin.

Dashboard KPIs

The dashboard can display metrics such as:

• Total Orders
• Payment Gateway Revenue
• Gateway Fees
• Revenue After Gateway Fees
• Successful Payments
• Failed Payments
• Gateway Success Rate
• Estimated Fee Savings
• Optimization Score
• Best Performing Gateway
• Highest-Cost Gateway
• Top Performing Rule

Gateway Performance

The gateway comparison area helps you compare payment methods.

You can review:

• Gateway name
• Successful payments
• Failed payments
• Success rate
• Revenue
• Fees
• Payment cost

Quick Insights

The plugin can identify important trends such as:

• A gateway with an unusually high failure rate.
• A gateway with comparatively high fees.
• The best-performing gateway.
• The most expensive gateway.
• Rules generating significant payment activity.

How It Works

The dashboard uses the data collected from payment activity and optimization rules.

It is intended to help you answer questions such as:

Which payment gateway performs best?

Which gateway costs the most?

Which payment method has the highest failure rate?

Which rules are being used most often?

Where can payment gateway costs potentially be reduced?

9. Gateway Rules

Purpose

The Gateway Rules section is the core of the optimization engine.

Rules allow you to control gateway behavior according to your store’s requirements.

A rule can evaluate conditions such as:

• Order total
• Cart quantity
• Cart weight
• Products
• Product categories
• Product tags
• Product brands
• Customer role
• Guest customers
• Payment gateway
• Other supported checkout conditions

Rules can then perform actions such as:

• Prioritize a gateway.
• Change gateway position.
• Hide a gateway.
• Show a gateway.
• Recommend a gateway.
• Apply a gateway fee.
• Apply different gateway strategies.

10. Creating Your First Gateway Rule

Go to:

WooCommerce → Payment Gateway Optimizer → Gateway Rules

Click:

Add New Rule

Step 1 — Rule Name

Enter a descriptive name.

Example:

Promote Stripe for Orders Above $100

A descriptive name makes rule management easier when you have many rules.

Step 2 — Enable the Rule

Enable the rule when you want it to participate in optimization.

Disabled rules remain saved but do not affect checkout behavior.

Step 3 — Select Conditions

Configure the conditions under which the rule should apply.

For example:

Order Total

Set:

Order Total > $100

The rule will apply only when the order value exceeds $100.

Cart Quantity

Example:

Cart Quantity >= 5

This can be useful for wholesale or bulk purchases.

Cart Weight

Example:

Cart Weight > 10 kg

This allows payment strategies to be changed for heavier orders.

Products

Select specific products.

Example:

Product = Premium Product

The rule can then target orders containing that product.

Product Categories

Example:

Category = Electronics

You can create payment strategies specifically for electronics purchases.

Product Tags

Example:

Tag = Wholesale

This can be useful for special product groups.

Product Brands

Example:

Brand = Brand A

The rule can target products belonging to a specific brand.

Customer Role

Example:

Customer Role = Wholesale Customer

This allows different payment gateway strategies for different customer types.

Guest Customers

You can create conditions specifically for customers who are not logged in.

Example:

Customer = Guest

11. Gateway Rule Actions

After defining conditions, configure what should happen when the rule matches.

Prioritize Gateway

Promote a selected gateway toward the top of the checkout payment methods.

Example:

Orders above $100 → prioritize Stripe.

Sort Gateways

Control the order in which payment gateways appear.

Example:

1. Stripe
2. PayPal
3. Bank Transfer
4. Cash on Delivery

The optimizer applies the configured ordering when the rule matches.

Hide Gateway

A matching rule can hide a payment gateway.

Example:

Orders above $500 → hide Cash on Delivery.

The gateway will not be presented when the configured condition is satisfied.

Show Gateway

You can make a gateway available only when specific conditions are met.

Example:

Wholesale customers → show Bank Transfer.

Recommend Gateway

Use recommendations to emphasize a preferred payment method.

Example:

Orders above $200 → recommend Stripe.

The purpose is to guide customers toward the payment method that best fits your configured strategy.

12. Rule Priority

When multiple rules could apply to the same checkout, rule priority determines which rules should take precedence.

Use higher priority for rules that must override or take precedence over broader rules.

Example

Rule 1:

All customers → prioritize PayPal

Rule 2:

Wholesale customers → prioritize Bank Transfer

If the wholesale rule has a higher priority, it can take precedence when the customer is a wholesale customer.

Use clear rule names and priorities to avoid creating conflicting strategies.

13. Gateway Fees

Purpose

The Fees functionality allows you to apply additional payment gateway charges based on configured conditions.

Fees can be used when your business wants to recover some or all of the additional cost associated with a payment method.

Depending on the configured rule, fees can be based on:

• Payment gateway
• Order amount
• Product
• Category
• Customer role
• Cart quantity
• Cart weight
• Other supported conditions

14. Configuring a Payment Gateway Fee

Go to:

WooCommerce → Payment Gateway Optimizer → Fees

Create a new fee rule.

Step 1 — Select Gateway

Choose the payment gateway to which the fee applies.

Example:

Credit Card

Step 2 — Select Fee Type

Depending on the available configuration, choose:

• Fixed fee
• Percentage fee

Step 3 — Enter Fee Amount

Example:

2%

or:

$3.00

Step 4 — Configure Conditions

For example:

Order Total > $100

The fee will only be applied when the order meets the configured conditions.

Example

You could configure:

Gateway: Credit Card

Fee: 2%

Condition: Order total greater than $100

Result:

A customer paying with the selected gateway for an order above $100 receives the configured payment gateway fee.

15. Important Fee Behavior

Payment gateway fees are controlled by your configuration.

The plugin does not automatically assume that every gateway should have a fee.

You decide:

• Which gateway is affected.
• When the fee applies.
• How the fee is calculated.
• Which customers or carts are targeted.

Always configure fees according to your local laws, payment provider agreements, and applicable card/payment regulations.

16. Gateway Sorting

Purpose

Gateway sorting controls the order in which payment methods are displayed during checkout.

This is useful when you want to:

• Promote your preferred gateway.
• Put lower-cost gateways first.
• Prioritize gateways with better success rates.
• Promote specific gateways for high-value orders.
• Create different gateway ordering strategies.

17. Example Gateway Sorting Strategy

Suppose your store has:

1. PayPal
2. Stripe
3. Bank Transfer
4. Cash on Delivery

You may configure:

Standard Orders

1. Stripe
2. PayPal
3. Bank Transfer
4. Cash on Delivery

High-Value Orders

1. Bank Transfer
2. Stripe
3. PayPal
4. Cash on Delivery

Wholesale Orders

1. Bank Transfer
2. Stripe
3. PayPal

The optimizer determines which strategy should be used according to the configured rules.

18. Gateway Visibility

The Gateway Visibility functionality controls whether payment gateways should be available under specific conditions.

You can create strategies such as:

Example 1

Hide Cash on Delivery for orders above $500.

Example 2

Hide Bank Transfer for guest customers.

Example 3

Show a specific gateway only for customers in a particular customer segment.

Example 4

Hide a gateway when the cart contains a particular product category.

This allows you to create a more controlled checkout experience.

19. Gateway Recommendations

Recommendations help guide customers toward your preferred payment method.

For example:

Orders above $200 → recommend Credit Card.

or:

Wholesale customers → recommend Bank Transfer.

Recommendations are intended to complement your existing checkout experience rather than replace your payment gateways.

20. Scheduling

Purpose

The Scheduling tab allows you to control when automatic optimization processing should run.

Scheduling is useful for stores with large catalogs or stores that want optimization operations to run periodically rather than continuously.

Available Settings

Depending on the plugin configuration, scheduling can include:

• Enable/Disable scheduling
• Hourly frequency
• Daily frequency
• Weekly frequency
• Minimum batch size
• Batch processing delay

21. Batch Processing

For larger WooCommerce stores, optimization operations can process data in batches.

For example:

Batch Size = 100

The plugin processes records in manageable groups instead of attempting to process a very large dataset in a single operation.

This helps reduce:

• Memory usage
• Long-running requests
• Server load
• Timeout risks

The scheduler is designed to make background processing more suitable for larger stores.

22. Analytics

Purpose

The Analytics tab provides detailed information about payment gateway performance.

Use Analytics to understand:

• Which gateways generate the most revenue.
• Which gateways have the highest fees.
• Which gateways have the best success rates.
• Which gateways have payment failures.
• Which rules are being triggered.
• Which payment strategies are performing better.

23. Gateway Analytics

Gateway analytics can include:

• Gateway
• Orders
• Successful payments
• Failed payments
• Success rate
• Revenue
• Fees
• Revenue after gateway fees

Example

This allows you to compare payment methods using actual store activity.

24. Rule Performance Analytics

Rule analytics show how your optimization rules are performing.

You can analyze:

• Rule usage
• Orders affected
• Revenue
• Gateway fees
• Successful payments
• Failed payments
• Success rate

Example

Rule:

Promote Stripe for Orders Above $100

Analytics may show:

• Orders affected: 250
• Revenue: $42,000
• Success rate: 98%
• Gateway fees: $1,050

This helps you determine whether a rule is actually useful.

25. Payment Success and Failure Tracking

The plugin can track successful and failed payment outcomes.

Successful payments can be used to measure:

• Gateway success rate.
• Gateway revenue.
• Rule performance.

Failed payments can help identify:

• Gateway reliability problems.
• High failure-rate gateways.
• Potential checkout issues.
• Rules associated with poor payment outcomes.

26. Optimization Score

The dashboard can provide an Optimization Score to give you a quick high-level indication of your configured payment strategy.

The score is based on the performance data available to the plugin and can consider factors such as:

• Gateway success rates.
• Payment fees.
• Gateway performance.
• Optimization activity.

Use the score as a monitoring indicator rather than as an accounting or financial metric.

27. Best Performing Gateway

The dashboard identifies the gateway performing best according to the available payment statistics.

This can help answer:

Which payment gateway is currently performing best in my store?

You can then use this information when designing future gateway rules and prioritization strategies.

28. Highest-Cost Gateway

The analytics area can identify gateways generating comparatively higher payment costs.

This helps you investigate:

• Gateway fee differences.
• Payment method usage.
• High-cost payment methods.
• Potential optimization opportunities.

The plugin does not automatically assume that the most expensive gateway should be disabled. The decision remains under your control.

29. General Settings

The General Settings tab contains the plugin-wide configuration.

Depending on the plugin version, this area may include settings for:

• Enable/disable optimizer functionality.
• Default optimization behavior.
• Default gateway behavior.
• Logging.
• Analytics.
• Processing behavior.
• Other global preferences.

Global settings apply across the plugin unless a specific rule overrides the behavior.

30. Recommended Initial Configuration

After installation, we recommend the following setup sequence.

Step 1

Install and activate the plugin.

Step 2

Verify that WooCommerce is active.

Step 3

Verify your payment gateways under:

WooCommerce → Settings → Payments

Step 4

Open:

WooCommerce → Payment Gateway Optimizer

Step 5

Review the Dashboard.

Step 6

Configure your general preferences.

Step 7

Create one simple gateway sorting rule.

For example:

Prioritize Stripe for orders above $100.

Step 8

Test the rule on your staging site.

Step 9

Create additional visibility, recommendation, or fee rules.

Step 10

Review Analytics after receiving payment activity.

Step 11

Adjust your gateway strategy based on actual performance.

31. Recommended Rule-Building Strategy

Avoid creating dozens of complicated rules immediately.

Start with simple rules.

Level 1 — Basic Sorting

Example:

Always prioritize Stripe.

Level 2 — Order-Based Rules

Example:

Orders above $200 → prioritize Stripe.

Level 3 — Customer-Based Rules

Example:

Wholesale customers → prioritize Bank Transfer.

Level 4 — Product-Based Rules

Example:

Electronics category → prioritize Credit Card.

Level 5 — Combined Conditions

Example:

Wholesale customer + order above $500 → prioritize Bank Transfer.

Build gradually and test each strategy.

32. Example: Reduce Use of a High-Cost Gateway

Suppose your analytics show that Gateway A has significantly higher payment costs than Gateway B.

You could create:

Condition:

Order total > $100

Action:

Prioritize Gateway B

This does not disable Gateway A. It simply gives Gateway B higher visibility.

This is useful when you want to encourage a preferred payment method while still preserving customer choice.

33. Example: Hide Cash on Delivery for High-Value Orders

Create a rule:

Condition:

Order total > $500

Action:

Hide Cash on Delivery

Result:

Cash on Delivery is unavailable for orders above the configured threshold.

This can help merchants manage payment risk for high-value orders.

34. Example: Wholesale Payment Strategy

Create:

Condition:

Customer role = Wholesale Customer

Action:

Prioritize Bank Transfer

Optional additional action:

Hide selected consumer-oriented payment methods.

Result:

Wholesale customers receive a payment gateway strategy specifically designed for their customer segment.

35. Example: Conditional Payment Gateway Fee

Create:

Gateway:

Credit Card

Condition:

Order total > $100

Fee:

2%

Result:

The configured fee is applied when the customer selects the specified gateway and the order satisfies the rule.

36. Example: Product Category Strategy

Suppose electronics have a preferred payment provider.

Create:

Condition:

Product Category = Electronics

Action:

Prioritize the preferred gateway.

Result:

When the cart contains products matching the configured category, the payment gateway strategy can change automatically.

37. Testing Your Configuration

Always test new payment rules before enabling them on a live store.

Recommended test scenarios:

Test 1 — Normal Order

Place an order below the rule threshold.

Verify the default gateway behavior.

Test 2 — Matching Order

Place an order that satisfies the rule.

Verify:

• Gateway order.
• Gateway visibility.
• Recommendation.
• Fee calculation.

Test 3 — Non-Matching Order

Change one condition so that the rule should not match.

Verify that the rule no longer affects checkout.

Test 4 — Multiple Rules

Test an order that matches multiple rules.

Verify that rule priority produces the expected result.

Test 5 — Payment Completion

Complete a successful payment.

Verify that the transaction appears in the relevant analytics.

Test 6 — Failed Payment

Perform a controlled failed-payment test where supported.

Verify that the failure is reflected in gateway performance analytics.

38. Cart & Checkout Blocks

Smart Payment Gateway Optimizer is designed to work with modern WooCommerce checkout experiences, including WooCommerce Cart and Checkout Blocks.

When using Checkout Blocks:

• Gateway optimization should be handled server-side.
• Rules should not depend solely on classic checkout JavaScript.
• Payment gateway behavior should be tested using the actual checkout block used by the store.
• Third-party gateway compatibility should be verified with the gateway provider’s current WooCommerce implementation.

If you use a third-party payment gateway, make sure the gateway itself supports your WooCommerce checkout configuration.

39. Third-Party Payment Gateways

The plugin is designed to work with existing WooCommerce payment gateways.

You can use it with gateways provided by:

• WooCommerce extensions.
• Payment providers.
• Banks.
• Regional payment services.
• Custom WooCommerce payment gateways.

The plugin does not replace the gateway’s payment processing API.

Instead, it works with the payment gateways exposed by WooCommerce and applies your configured optimization strategy.

40. Analytics Data and Rule Attribution

When an order is processed through a configured optimization rule, the plugin can associate the relevant rule with that order for rule-performance reporting.

Gateway performance and rule performance are separate concepts:

Gateway Analytics

Answers:

How is this payment gateway performing?

Rule Analytics

Answers:

How are orders affected by this optimization rule performing?

Keeping these metrics separate makes analytics more meaningful.

41. Multiple Rules

You can create multiple optimization rules.

For example:

Rule 1

All orders → prioritize Stripe.

Rule 2

Orders above $500 → prioritize Bank Transfer.

Rule 3

Wholesale customers → prioritize Bank Transfer.

Rule 4

Orders above $1,000 → hide Cash on Delivery.

The plugin evaluates the applicable rules and applies the configured strategy according to rule priority and conditions.

For complex configurations, use descriptive rule names and priorities.

42. Rule Management Best Practices

For large stores:

• Use descriptive rule names.
• Keep conditions simple where possible.
• Use rule priorities consistently.
• Disable outdated rules instead of immediately deleting them.
• Avoid creating contradictory rules.
• Test changes on staging.
• Review analytics regularly.
• Remove obsolete strategies.
• Monitor failed-payment rates after changing gateway priorities.

43. Performance Recommendations

For stores with large order volumes:

• Avoid unnecessarily complex rules.
• Use specific conditions instead of broad conditions where possible.
• Enable scheduled/background processing where applicable.
• Use reasonable batch sizes.
• Avoid creating hundreds of overlapping rules.
• Review analytics periodically.
• Keep WooCommerce and payment gateways updated.

The plugin is designed to support stores where optimization data and background processing may involve substantial amounts of information.

44. What Happens When the Plugin Is Disabled?

When the optimizer is disabled, your underlying WooCommerce payment gateways continue to operate according to their normal WooCommerce configuration.

The plugin does not replace the payment gateway itself.

Therefore, disabling the optimizer does not mean that your payment provider or payment gateway plugin is disabled.

45. What Happens If a Rule Does Not Match?

If a rule’s conditions are not satisfied, that rule does not affect the checkout.

For example:

Rule:

Orders above $100 → prioritize Stripe.

Customer order:

$75

The rule does not apply.

The normal WooCommerce gateway configuration remains available.

46. What Happens When Multiple Rules Match?

When multiple rules match the same checkout, the plugin uses the configured rule priority and optimization logic to determine the applicable strategy.

For this reason, rule priorities should be planned carefully.

A recommended approach is:

• Low priority → general/default rules.
• Medium priority → targeted rules.
• High priority → special/exception rules.

47. Troubleshooting

Payment Gateway Is Not Showing

Check:

1. WooCommerce → Settings → Payments.
2. Confirm the gateway is enabled.
3. Check whether a visibility rule is hiding it.
4. Check whether another rule changes its behavior.
5. Review rule priority.
6. Test with the rule temporarily disabled.

Gateway Is Showing in the Wrong Position

Check:

1. Gateway sorting rules.
2. Rule priority.
3. Whether multiple rules match.
4. Whether the payment gateway itself has a separate ordering mechanism.
5. Whether the checkout uses a custom payment gateway integration.

Fee Is Not Applied

Check:

1. The fee rule is enabled.
2. The selected gateway is correct.
3. The order satisfies all conditions.
4. The customer selected the affected gateway.
5. Another rule does not override the configuration.
6. The checkout implementation supports the configured fee behavior.

Fee Is Applied Unexpectedly

Check:

1. All active fee rules.
2. Rule conditions.
3. Rule priority.
4. Customer role conditions.
5. Product/category conditions.
6. Whether multiple rules are applying fees.

Analytics Are Empty

Analytics require payment/order activity to generate meaningful data.

Check:

1. Orders have been placed after plugin activation.
2. The selected payment gateways are actually being used.
3. Orders reached the relevant payment status.
4. Rules were active when the orders were created.
5. The dashboard filters, if available, are configured correctly.

48. Frequently Asked Questions

Does the plugin create payment gateways?

No.

It works with the payment gateways already installed and configured in WooCommerce.

Does the plugin replace Stripe, PayPal, or other payment gateways?

No.

It works alongside existing gateway plugins.

Can I sort payment gateways?

Yes.

You can create gateway sorting and prioritization strategies based on supported conditions.

Can I hide payment gateways?

Yes.

Gateway visibility rules can hide or show payment methods when specific conditions are met.

Can I prioritize payment gateways?

Yes.

You can configure rules to promote preferred payment gateways.

Can I charge payment gateway fees?

Yes.

You can configure conditional payment gateway fees using supported fixed or percentage fee options.

Can fees depend on the order total?

Yes.

Order total can be used as a rule condition.

Can I create rules based on products?

Yes.

Product-specific conditions can be used when creating optimization rules.

Can I create category-based rules?

Yes.

Product categories can be used to create targeted gateway strategies.

Can I create customer-role rules?

Yes.

Customer roles can be used to create different payment strategies for different customer groups.

Can I target guest customers?

Yes.

Guest customers can be targeted separately from logged-in customers.

Can rules use cart quantity?

Yes.

Cart quantity can be used as a condition.

Can rules use cart weight?

Yes.

Cart weight can be used for weight-based payment strategies.

Can I track failed payments?

Yes.

The plugin can track successful and failed payment activity for gateway performance analysis.

Can I compare payment gateways?

Yes.

The analytics dashboard provides gateway-level performance information for comparison.

Can I see payment gateway fees?

Yes.

Gateway analytics can report recorded gateway fee information.

Can I see which gateway performs best?

Yes.

The dashboard can identify the best-performing gateway based on available performance data.

Can I see which gateway is most expensive?

Yes.

Gateway analytics can help identify gateways with comparatively higher payment costs.

Can I track rule performance?

Yes.

Rules can be associated with order activity so that their performance can be analyzed separately from overall gateway performance.

Does the plugin automatically change my payment gateway configuration?

No.

The plugin applies the optimization behavior you configure through its rules and settings. Your underlying gateway configuration remains controlled by WooCommerce and the individual gateway plugin.

Is the plugin compatible with WooCommerce Checkout Blocks?

The plugin is designed to support modern WooCommerce checkout experiences, including Cart and Checkout Blocks. Always test your specific payment gateway combination because third-party gateway implementations can differ.

Is the plugin compatible with HPOS?

Yes. The plugin is designed for modern WooCommerce stores using High-Performance Order Storage.

Do I need to configure every payment gateway?

No.

Configure only the gateways and strategies you want the optimizer to manage.

Can I use multiple rules?

Yes.

You can create multiple rules and use conditions and priorities to build a complete payment gateway strategy.

Can I disable a rule temporarily?

Yes.

Disable the rule instead of deleting it when you want to temporarily stop it from affecting checkout.

49. Recommended First-Day Setup

For most stores, start with this simple workflow:

1. Install the plugin

Upload and activate the plugin.

2. Verify payment gateways

Go to:

WooCommerce → Settings → Payments

Make sure all required gateways are working.

3. Open the optimizer

Go to:

WooCommerce → Payment Gateway Optimizer

4. Review Dashboard

Understand your existing gateway performance.

5. Create one simple rule

Example:

Orders above $100 → prioritize the preferred gateway.

6. Test checkout

Test both matching and non-matching orders.

7. Add visibility rules

Hide payment methods only where there is a clear business reason.

8. Configure fees

If your business requires payment gateway fees, create the appropriate conditional fee rules.

9. Add customer/product strategies

Create targeted rules for wholesale customers, product categories, brands, or other business segments.

10. Review Analytics

After sufficient order activity, review gateway and rule performance.

11. Optimize gradually

Use actual performance data to refine your payment gateway strategy.

50. Recommended Configuration Workflow

A mature store can follow this optimization cycle:

Configure Gateways

↓

Create Rules

↓

Prioritize / Hide / Recommend / Apply Fees

↓

Test Checkout

↓

Collect Payment Data

↓

Review Gateway Analytics

↓

Review Rule Performance

↓

Identify Opportunities

↓

Adjust Rules

↓

Monitor Results

This creates a continuous payment gateway optimization process instead of relying on static gateway ordering.

51. Best Practices

For the best results:

Keep Rules Understandable

Avoid overly complicated conditions unless they are genuinely required.

Start Small

Create a few high-value rules first.

Monitor Results

Do not assume that a gateway is better simply because its processing fee is lower. Consider payment success rate, customer usage, revenue, and business requirements.

Test Changes

Always test gateway changes before applying them to a live store.

Avoid Conflicting Rules

Use priorities to make your intended strategy clear.

Review Analytics

Use actual payment performance data to improve your rules.

Keep Payment Gateways Updated

Payment gateway extensions should be kept compatible with your WooCommerce version.

52. Getting the Most from Smart Payment Gateway Optimizer

The plugin is most powerful when used as an ongoing optimization system.

Instead of simply asking:

“Which payment gateway should I display first?”

you can analyze:

• Which gateway converts the most payment attempts.
• Which gateway has the lowest failure rate.
• Which gateway generates the most revenue.
• Which gateway costs the most.
• Which rules are affecting the most orders.
• Which payment strategies work for high-value orders.
• Which gateways should be prioritized for specific customers.
• Where payment gateway costs can potentially be optimized.

Use these insights to continuously improve your store’s payment strategy.

53. Quick Reference

54. Summary

Smart Payment Gateway Optimizer for WooCommerce gives store owners more control over their payment strategy.

Instead of treating every payment gateway equally, you can build rules around:

• Order value
• Cart quantity
• Cart weight
• Products
• Categories
• Tags
• Brands
• Customer roles
• Guest customers
• Gateway performance

You can then:

• Sort gateways.
• Prioritize gateways.
• Hide gateways.
• Show gateways.
• Recommend gateways.
• Apply conditional gateway fees.
• Track gateway performance.
• Track successful and failed payments.
• Analyze rule performance.
• Monitor payment costs.
• Continuously optimize your payment strategy.

The recommended approach is to start with a small number of simple rules, test them carefully, monitor real payment activity, and gradually build a more advanced gateway optimization strategy.