✨ 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 OctanePay: gateway transactions as tables

Read directly from wc_orders, wc_orders_meta, and OctanePay's transaction references. Surface auth codes, capture status, and gateway response data as real columns instead of digging into each order.

♾️ Lifetime License available

SleekView table view for WooCommerce OctanePay

Gateway data hides inside each order, not on the list

WooCommerce OctanePay processes payments through its own gateway and stores transaction references, authorisation codes, and gateway response payloads in wc_orders_meta. The default Orders screen shows order number, status, customer, total, payment method label. The transaction id, response code, and capture state stay buried in postmeta-style storage until you click into each order one at a time.

SleekView reads wc_orders together with OctanePay's stored meta keys so transaction id, auth code, capture status, and last gateway error become first-class columns. Finance pulls every authorised-but-not-captured order from the last 72 hours, support filters by gateway error code to triage chargebacks, and ops bulk-flips orders through capture without per-order click-through.

Inline edits to order status route through WooCommerce's CRUD layer, so OctanePay's hooks fire as expected, capture requests run, and order-status emails send. Direct edits to gateway meta are guarded by conflict detection so a stale admin row never overwrites a fresh gateway callback.

Workflow

How SleekView reads your OctanePay setup

1

Pick the source

Choose wc_orders for HPOS or shop_order posts on legacy. SleekView detects which path is active and surfaces the matching joinable meta.
2

Compose gateway columns

Add transaction id, auth code, capture status, and gateway error from the column picker. Meta keys not present in your data don't clutter the list.
3

Save the operational views

Name them ("Authorised over 48h", "Refunded this week", "Gateway errors") and gate them by capability so finance, support, and risk each see their own table.
4

Edit inline or bulk-capture

Flip status through CRUD so OctanePay's capture and refund hooks fire, email triggers run, and audit trails write. Bulk operations iterate per row, never silently in batch.

Sample columns

A typical OctanePay transactions view

Joins wc_orders with OctanePay meta keys like _octanepay_transaction_id and _octanepay_auth_code.
Source: wp_wc_orders + wp_wc_orders_meta (OctanePay keys)
Order # Transaction ID Capture Auth code Total Date
#10428 OP-tx-4F92A1 Captured A12345 $184.00 Apr 24
#10427 OP-tx-4F9219 Authorised A12331 $72.50 Apr 24
#10426 OP-tx-4F91FE Captured A12306 $312.00 Apr 23
#10425 OP-tx-4F91A4 Refunded A12287 $48.00 Apr 23

Comparison

Default WooCommerce OctanePay admin vs SleekView

Default WooCommerce OctanePay admin

  • Transaction id lives in wc_orders_meta and is invisible in the Orders list
  • Auth-vs-capture state isn't a default column, only a derived status
  • Gateway response codes need per-order inspection to debug failed captures
  • No way to filter authorised-but-not-captured orders as a saved view
  • Refunds initiated through the gateway aren't grouped as a reviewable list

SleekView

  • Surface _octanepay_transaction_id and _octanepay_capture_status as columns
  • Saved view: authorised-but-not-captured in the last 72 hours
  • Filter by gateway response code for fast chargeback triage
  • Bulk-capture orders through WooCommerce CRUD so OctanePay's capture hook fires
  • Dedicated refunds view joined back to the parent order

Features

What SleekView gives you for WooCommerce OctanePay

Gateway meta as first-class columns

Pull _octanepay_transaction_id, _octanepay_auth_code, and _octanepay_capture_status from wc_orders_meta straight into the table. Finance and support stop opening orders to read a string.

Authorise vs capture filters

Saved view for authorised but not captured orders within a date window. Catch stuck payments before the auth expires instead of finding them after the customer emails.

Bulk-capture safely

Iterate captures through WooCommerce CRUD so woocommerce_order_status_changed and OctanePay's capture handler fire per row. No batch endpoint that skips hooks, no silent direct writes.

Audience

Who uses SleekView for WooCommerce OctanePay

Finance ops

Reconcile captures against the gateway settlement file: order, transaction id, capture status, and total in one row, filtered by date range.

Support

Search by customer email, see transaction id and last gateway error inline, and re-trigger capture or refund without leaving WordPress.

Risk and fraud

Saved view of refunded or chargeback-flagged orders with auth code and AVS/CVV response columns. Pattern-spotting becomes a sort, not a query.

The bigger picture

Why gateway audit beats per-order clicks

Payment gateway plugins like OctanePay are designed to handle the gateway side cleanly: take card details, send to the processor, write transaction references back to the order. That part works. What stops working at volume is the operational side: finance reconciling captures against a settlement file, support chasing failed captures the customer hasn't noticed yet, risk reviewing chargeback patterns.

All of those jobs need the gateway meta surfaced at the row level (transaction id, auth code, capture state, response code) and the default WooCommerce Orders screen doesn't show any of it. Operators end up opening every order, copy-pasting numbers into spreadsheets, and missing the authorised-but-not-captured rows until the auth expires. SleekView turns the same data into the views each role needs: a finance audit table joined with capture state, a support workspace with transaction id inline, a risk view of refunds and chargebacks.

Same database, same hooks, dramatically less per-order clicking.

Questions

Common questions about SleekView for WooCommerce OctanePay

Yes. SleekView reads wc_orders and wc_orders_meta on HPOS (default since WooCommerce 8.2) and falls back to shop_order posts with postmeta on legacy stores. OctanePay's meta keys are the same on both schemas.

 

Status changes through WooCommerce CRUD trigger OctanePay's capture or refund handlers as configured. The actual gateway call goes through the plugin's hook chain, not a SleekView shortcut, so the behaviour matches manual admin edits exactly.

 

Yes, if OctanePay stores them in wc_orders_meta. SleekView lists meta keys actually present in your install, so the column picker shows whatever the gateway plugin writes (transaction id, auth code, response code, AVS, CVV, last error).

 

If OctanePay stores multiple transaction records per order in meta or in a related table, SleekView can render them as a related child table on the order row, or as their own view scoped to those records. The default Orders screen shows only the headline status.

 

Yes. Edits go through CRUD, so woocommerce_order_status_changed fires and the email hooks WooCommerce ships with run as expected. Bulk operations iterate through CRUD per row, so the email behaviour matches one-at-a-time admin edits.

 

Queries hit indexed columns on wc_orders directly. Meta filters use wc_orders_meta joins, which are indexed by order_id and meta_key. Aggregate columns (total captured this week) are opt-in per view to keep triage queries fast.

 

Yes. Any SleekView table exports to CSV with the visible column set. Useful for monthly settlement reconciliation, end-of-quarter finance close, or sharing a filtered chargeback list with a payments analyst outside WordPress.

 

Column definitions reference meta keys by exact name, so a gateway plugin update that renames keys requires updating the SleekView column definitions. The column picker shows the keys actually present in current data, so detecting the rename is straightforward.

 

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