✨ 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 WC Marketplace Stripe Connect: splits, transfers & vendor payouts as tables

Read directly from wc_orders with payment_method=stripe and surface Stripe Connect transfer metadata (transfer id, destination account, application fee) stored in wc_orders_meta. Build per-vendor payout tables and split-audit views without manual exports.

♾️ Lifetime License available

SleekView table view for WooCommerce Marketplace Stripe Connect

Stripe Connect splits, finally as columns

WooCommerce Marketplace Stripe Connect routes payments through Stripe's Connect API: the platform charges the buyer, then transfers a per-vendor share to each connected account, keeping an application fee. The plugin records the resulting Stripe transfer ids, destination account ids, transfer amounts, and application-fee amounts as wc_orders_meta keys on the parent order. The default WooCommerce Orders screen shows the platform charge total and not much else: which connected account got which share, and how much application fee accrued, all stay invisible until you click into each order or hop to the Stripe Connect dashboard.

SleekView reads wc_orders on HPOS (or shop_order on legacy) and exposes the Stripe Connect meta keys (transfer id, destination account, transfer amount, application fee) as first-class columns. Where the plugin stores multiple transfers per order in serialised arrays or repeated meta rows, SleekView normalises the join so each transfer is a row, joined to the parent order and the destination vendor account.

Inline edits route through WooCommerce CRUD for order status. Adjustments to Stripe transfers themselves must still happen via the Stripe API or dashboard, since the source of truth lives there. The SleekView workspace shows the recorded transfer history alongside the platform order so finance can reconcile both sides without tab-hopping.

Workflow

How SleekView reads your Stripe Connect WooCommerce schema

1

Pick the source table

Choose wc_orders on HPOS or shop_order on legacy. SleekView detects which path is active and exposes matching columns plus joinable meta keys.
2

Compose your Stripe Connect column set

Add the transfer-id, destination-account, transfer-amount, and application-fee meta keys. The agent UI lists meta keys actually present in your installation.
3

Save and scope the view

Name it ("Pending transfers this week", "Reversed transfers") and gate by WordPress capability so finance, vendor managers, and admins each see their own column set.
4

Edit inline and bulk-update

Edit order-level notes and status through WooCommerce CRUD. For transfer-level changes (reversals, retries), use the Stripe Connect dashboard or API, since that is where the source of truth lives.

Sample columns

A typical Stripe Connect transfers view

SleekView surfaces Stripe Connect transfer metadata from wc_orders_meta joined to wc_orders.
Source: wp_wc_orders + wp_wc_orders_meta (HPOS) or wp_posts (shop_order) + wp_postmeta
Order Destination Transfer ID Amount App fee Status Date
#80142 acct_studio_aurora tr_8821 €164.00 €20.00 Paid Apr 24
#80141 acct_brew_coop tr_8820 €65.00 €7.50 Paid Apr 24
#80140 acct_design_ria tr_8819 €281.00 €31.00 Pending Apr 23
#80139 acct_hello_dev tr_8818 €42.00 €6.00 Reversed Apr 23

Comparison

Default WooCommerce Stripe Connect admin vs SleekView

Default WooCommerce Stripe Connect admin

  • Orders screen shows platform charge only, not per-vendor transfer rows
  • Transfer id, destination account, and application fee live in wc_orders_meta and stay hidden
  • Per-vendor payout totals require hopping to the Stripe Connect dashboard
  • Reversed transfers need per-order admin inspection
  • Cross-vendor payout reconciliation needs CSV exports

SleekView

  • Read wc_orders and surface Stripe transfer metadata as columns
  • Normalise multi-transfer orders so each transfer is a row
  • Per-destination payout totals across any date range
  • Save filtered views ("Pending transfers", "Reversed transfers this week")
  • Cross-reference the WP order side with the Stripe Connect dashboard

Features

What SleekView gives you for WooCommerce Marketplace Stripe Connect

One row per Stripe transfer

Normalise multi-transfer orders so a parent order with three connected-account splits shows as three rows. Each row carries transfer id, destination, amount, and application fee.

Destination-account filters

Filter by destination account, transfer status, or date range. Save "acct_studio_aurora this month" for a per-vendor reconciliation view.

Order-side edits through CRUD

Inline edits to order status route through WooCommerce CRUD so hooks fire. Stripe-side transfer adjustments still go through the Stripe API, since that is where the source of truth lives.

Audience

Who uses SleekView for WC Marketplace Stripe Connect

Platform finance

Reconcile recorded transfers against the Stripe Connect dashboard by date and destination. Application-fee totals sum inline for revenue reporting without separate exports.

Vendor managers

Per-destination payout history: total transferred this month, average per order, reversal rate. Spot vendors whose transfers reverse frequently and need a payout pause.

Marketplace admins

Audit-style views: reversed transfers with reason codes, transfers above a manual-review threshold, refunds with linked transfer reversals.

The bigger picture

Why split payments need a marketplace-aware admin

Stripe Connect is the dominant payment rail for serious WooCommerce marketplaces, and for good reason: it handles per-vendor splits, application fees, and connected-account compliance in a way no native gateway does. The trade-off is that one platform order now produces multiple transfers, each landing on a different connected account, each with its own status lifecycle. The default WooCommerce Orders screen was never designed for that.

It shows the platform charge as one row with a single total, and the per-vendor splits, transfer ids, application fees, and reversed-transfer flags all live in wc_orders_meta, invisible until you open the order. Platform finance teams reconciling daily against the Stripe Connect dashboard end up bouncing between WP Admin and Stripe. Vendor managers comparing payout history across connected accounts run custom SQL.

SleekView normalises one-order-to-many-transfers so each transfer is a row, joined to the platform order, surfacing the meta keys your plugin already writes. Same database, same Stripe-side source of truth, dramatically less tab-hopping.

Questions

Common questions about SleekView for WooCommerce Marketplace Stripe Connect

No. SleekView reads only the WordPress database. The Stripe Connect plugin records transfer metadata locally as wc_orders_meta; SleekView surfaces that recorded data. The Stripe dashboard remains the source of truth for the transfers themselves.

 

Yes. Where the plugin stores multiple transfers per order, SleekView normalises the structure so each transfer becomes a row joined to the parent order. This makes cross-vendor reconciliation views match how Stripe itself models the data.

 

Yes. SleekView reads wc_orders and wc_orders_meta on HPOS (default since WooCommerce 8.2) and falls back to shop_order posts plus postmeta on legacy.

 

No, that has to happen Stripe-side. The transfer lifecycle is owned by Stripe. SleekView can edit order status, internal notes, and order-level meta through WooCommerce CRUD, but a transfer reversal or status change must be initiated in the Stripe Connect dashboard or via the Stripe API.

 

Yes. Aggregate columns sum the application-fee meta key per destination or per date. Useful for platform-revenue reporting without a separate export step.

 

Plugin versions vary in the exact meta-key names. SleekView's agent UI lists meta keys actually present in your installation, so you pick from a real list. Add the keys your plugin version writes; the column set updates accordingly.

 

Queries hit indexed columns on wc_orders. Joins to wc_orders_meta use the order-id index. Pagination is keyset where possible. Per-destination aggregate columns are opt-in per view since they are heavier.

 

Yes. Scoped CSV export ships only the filtered rows with your configured columns, so finance receives the exact slice they need (e.g. "Pending transfers for acct_studio_aurora") rather than the whole orders table.

 

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