✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for WooCommerce Checkout Fees: gateway fees as tables

Read gateway fee config from wp_options and per-order fee lines from wc_orders_meta. Audit COD, Stripe, and PayPal surcharges in one sortable view without opening each order.

♾️ Lifetime License available

SleekView table view for WooCommerce Checkout Fees

Audit gateway fees without opening each order

WooCommerce Checkout Fees plugins (often shipped as part of "WooCommerce Payment Gateway Based Fees" or "WC Checkout Fees" by various authors) let you attach a flat or percentage fee per payment gateway, country, shipping method, or cart total. The default admin is usually a settings tab under WooCommerce, plus the fee showing up as a line on each order. There is no list view that says "Stripe surcharge fired on 318 orders this month, generating $1,272."

SleekView reads gateway fee rules from wp_options (typically a key like wc_checkout_fees_settings) and joins each applied fee back to its order through wc_orders on HPOS or shop_order on legacy. A per-gateway audit view surfaces order id, gateway, fee amount, customer email, and date, all sortable and filterable. A kanban grouped by gateway makes the gateway mix obvious for finance.

Inline edits update the plugin's config option with conflict detection, so disabling the COD surcharge, raising a Stripe percentage, or scoping a rule to a country list happens from the same screen as the audit. Refunds get the right treatment because SleekView joins shop_order_refund children (legacy) or the HPOS refund parent-id link, so the per-gateway revenue figure stays honest.

Workflow

How SleekView reads Checkout Fees data

1

Pick the source

Gateway rule list from wp_options, or the per-order fee-audit table joining wc_orders_meta back to wc_orders.payment_method.
2

Compose columns

Add gateway, country, status, customer email, fee type (flat versus percentage), and any related wc_orders_meta keys actually present in your data.
3

Save and scope per role

Name the view ("Stripe surcharges this quarter", "COD refunds") and gate it by WordPress capability. Finance, support, and merchandising each get their own column set.
4

Edit inline or bulk-toggle

Toggle a gateway fee on or off, adjust a flat amount, change a percentage, or refund a single order. Bulk operations iterate through WooCommerce CRUD so hooks fire as expected.

Sample columns

Gateway fee audit

Joins applied fees from wc_orders_meta back to wc_orders.payment_method for a per-gateway breakdown.
Source: wp_options (fee config) + wp_wc_orders_meta (applied fees)
Order Gateway Fee Customer Status Date
#7421 Stripe €3.20 alex@studio.co Completed Apr 24
#7420 PayPal €4.10 ria@design.io Completed Apr 24
#7419 Cash on delivery €5.00 tom@hello.dev Processing Apr 23
#7418 Stripe €2.80 mia@brew.coop Refunded Apr 23

Comparison

Default Checkout Fees admin vs SleekView

Default Checkout Fees admin

  • Fee config is a settings tab, with no audit list of which gateway fee fired on which orders
  • Per-gateway revenue requires exporting orders and pivoting in a spreadsheet
  • wc_orders.payment_method isn't filterable alongside fee amount in the default Orders screen
  • Refunded fee amounts aren't subtracted from any per-gateway view because there's no per-gateway view
  • Bulk-toggling a gateway fee requires opening the settings tab even for a one-click off

SleekView

  • Per-gateway fee-audit view joining wc_orders_meta to wc_orders.payment_method
  • Aggregate columns: order count, sum of fee amount, refund-adjusted revenue per gateway
  • Filter by gateway, country (from wc_order_addresses), and date range together
  • Inline-toggle a gateway fee on or off from the rule list
  • Kanban view grouping orders by gateway with the fee amount on each card

Features

What SleekView gives you for WooCommerce Checkout Fees

Per-gateway revenue table

Read applied fees from wc_orders_meta joined to wc_orders.payment_method. Each row shows order, gateway, fee, and customer so finance can reconcile COD, Stripe, and PayPal surcharges in one view.

Filter gateway and country together

Combine wc_orders.payment_method, wc_order_addresses.country, status, and date. Save the filter as a named view, for example "French COD surcharges this quarter", so finance does not rebuild it monthly.

Inline-toggle gateway fees

Turn a gateway fee on or off, adjust a flat amount, change a percentage, all from the rule list. Writes update the plugin config option with conflict detection and clear the WooCommerce gateway-fees cache.

Audience

Who uses SleekView for WooCommerce Checkout Fees

Finance ops

Per-gateway revenue with refund adjustments, filtered by date. Reconcile the COD bucket against the gateway statement without exporting orders to a spreadsheet.

Customer support

Customer disputes a surcharge mid-call. Search by order id, see the gateway and fee amount on one row, refund inline through WooCommerce CRUD so order-status hooks fire correctly.

Merchandising

Decide whether to keep a gateway fee based on per-gateway order count and refund rate. Kanban view groups orders by gateway with the fee on each card.

The bigger picture

Why gateway-fee audits need a real view

Gateway surcharges exist because payment-processor fees vary, sometimes by a lot. A COD order costs the merchant the bank-deposit fee; a Stripe order costs roughly 1.4 to 2.9 percent plus a fixed amount; a PayPal order costs similar with cross-border adjustments; an iDEAL order costs almost nothing. Merchants that recover those costs with a checkout fee plugin are right to do so, but they almost never audit the rules afterwards.

The default admin makes the audit hard: per-gateway revenue lives in wc_orders_meta but never shows on the Orders screen, refunds offset the revenue but no view subtracts them, and toggling a rule means opening the settings tab. SleekView turns the audit into a saved view: per-gateway order count, fee revenue, refund-adjusted figure, all sortable and filterable. Same database, same hooks, dramatically less spreadsheet plumbing for the finance lead who has to justify keeping or killing each surcharge.

Questions

Common questions about SleekView for WooCommerce Checkout Fees

Any plugin that writes the fee as a standard WooCommerce fee line. That includes WC Payment Gateway Based Fees, Plugin Republic's Checkout Add-Ons, and most smaller commercial variants. Applied fees land in wc_orders_meta on HPOS or _fee_lines postmeta on legacy, which is what SleekView reads.

 

Yes. Applied fees come from wc_orders_meta when HPOS is on and from postmeta on legacy. The join key (order_id) is the same in both schemas, so saved views keep working through an HPOS migration.

 

Yes. Add aggregate columns to a gateway-rule list: order count and sum of fee amount, optionally minus refunded amounts. SleekView runs the aggregate as a subquery on wc_orders_meta filtered by gateway and date range.

 

Optionally yes. Refunds are stored as child orders with shop_order_refund type on legacy and a parent-id link on HPOS. SleekView can join refund rows by parent id and subtract refunded fee amounts, so the per-gateway revenue figure does not overstate.

 

Yes. SleekView writes through the plugin's settings API where exposed, which triggers the plugin's own cache-clear hook. On plugins without that API, it writes the option directly and calls WC_Cache_Helper::get_transient_version to bump the WooCommerce transient version, which is what most checkout caches key off.

 

Yes. Country lives on wc_order_addresses.country. SleekView joins it so a finance view can filter by Stripe in Germany separately from Stripe in the UK, useful when gateway fees vary by region or when local taxes change the effective surcharge.

 

Yes. The plugin stores the rule type (flat versus percentage) as part of the fee config. SleekView surfaces this as a column on the rule list so a finance review can see at a glance which gateways charge a percentage versus a flat fee, and per-order fee amounts show the calculated value as written by the plugin.

 

Queries hit indexed columns (order_id, payment_method, date_created_gmt) directly on wc_orders and wc_orders_meta. Aggregate columns are opt-in per view since they're heavier. Keep them off triage views and on monthly-reconcile views for fast query plans.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView