✨ 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 SagePay: Opayo transactions as tables

Surface SagePay vendor tx codes, 3D Secure status, and capture state from wc_orders_meta as real columns. Filter on auth vs capture, reconcile refunds, and audit 3DS challenges without opening each order.

♾️ Lifetime License available

SleekView table view for WooCommerce SagePay (Opayo)

Opayo gateway data as columns

SagePay, now branded Opayo by Elavon, stores per-order data through its WooCommerce extension as meta on each order. On HPOS stores those land in wc_orders_meta as keys like _wc_sagepay_vendor_tx_code, _wc_sagepay_vps_tx_id, _wc_sagepay_status, and _wc_sagepay_3dsecure_status. The default Orders screen never surfaces any of them, so checking whether a payment cleared 3D Secure or whether an auth has been captured means opening each order one at a time.

SleekView reads those keys as real columns alongside the WooCommerce status, total, and customer email. Authorised-but-uncaptured orders become a saved view sorted by auth age. 3D Secure challenges and abandons surface as a separate fraud-audit table joined on _wc_sagepay_3dsecure_status. The legacy refund records on shop_order_refund or refund rows on wc_orders (HPOS) join the parent transaction for full reconciliation.

Inline status edits route through the WooCommerce CRUD layer, so woocommerce_order_status_changed and the plugin's own capture, void, and refund handlers fire as expected. SleekView reads what the plugin writes; it does not call Opayo APIs directly.

Workflow

How SleekView reads the SagePay plugin schema

1

Pick the base table

Choose wc_orders for the transaction workspace or woocommerce_payment_tokens for a token-rooted view. HPOS or legacy is detected automatically.
2

Add SagePay meta columns

From the meta picker pull _wc_sagepay_vendor_tx_code, _wc_sagepay_vps_tx_id, _wc_sagepay_status, and 3DS or AVS keys as needed.
3

Save the workflow views

"Auths approaching expiry", "3DS abandoned today", "Refunds this week". Gate each view by WordPress capability so finance, risk, and support see the right rows.
4

Bulk-update through CRUD

After a capture run, bulk-flip authorised orders to processing through SleekView. CRUD writes keep woocommerce_order_status_changed hooks firing for downstream integrations.

Sample columns

A typical SagePay transactions view

Joins wc_orders with SagePay meta keys (_wc_sagepay_vendor_tx_code, _wc_sagepay_3dsecure_status).
Source: wp_wc_orders + wp_wc_orders_meta + wp_woocommerce_payment_tokens
Order # Vendor TX Amount 3DS Capture Date
#9421 ORD-9421-AB £148.00 Authenticated Captured Apr 24
#9420 ORD-9420-CD £68.00 Attempt Authorised Apr 24
#9419 ORD-9419-EF £225.00 Abandoned None Apr 23
#9418 ORD-9418-GH £42.00 Authenticated Refunded Apr 22

Comparison

Default WooCommerce SagePay admin vs SleekView

Default WooCommerce SagePay admin

  • Vendor tx code and VPS tx id live in wc_orders_meta, never in the Orders list
  • 3D Secure result only visible after opening each order one at a time
  • No filter for authorised-not-captured auths approaching expiry
  • Refund reconciliation against the MySagePay portal is manual
  • Tokens in woocommerce_payment_tokens aren't surfaced in the order context

SleekView

  • _wc_sagepay_vendor_tx_code, _wc_sagepay_status, and 3DS status as columns
  • Saved view for auths approaching expiry sorted by auth age
  • Filter on 3D Secure challenge, attempt, or abandoned for risk audits
  • Bulk-update post-capture status with hooks firing through CRUD
  • Customer-rooted token view from woocommerce_payment_tokens

Features

What SleekView gives you for WooCommerce SagePay (Opayo)

Vendor tx and 3DS as columns

Add _wc_sagepay_vendor_tx_code, _wc_sagepay_3dsecure_status, and _wc_sagepay_avs_cv2 from the meta picker. Each view picks its columns; finance, support, and risk get different ones.

Auth-vs-capture filters

Filter on auth status approved combined with capture status not equal to captured. Sort by auth date ascending to surface auths nearing the SagePay reversal window.

3D Secure audit

Filter on _wc_sagepay_3dsecure_status equals Abandoned or Attempt to audit drop-off in the challenge flow. Useful for tuning fraud rules and chasing recoverable carts.

Audience

Who uses SleekView for WooCommerce SagePay

Finance ops

Reconcile MySagePay settlements by filtering on capture date and grouping by currency. Capture and refund totals visible inline; export to CSV for the accountant.

Risk and chargebacks

3DS audit view: filter abandoned or attempted authentications, sort by amount. Spot patterns that would otherwise show only as a monthly chargeback report.

Customer support

Customer history with vendor tx code, 3DS status, and capture state per order. Hand evidence packs to dispute teams without recompiling them manually.

The bigger picture

Why card-gateway ops need row-level views

SagePay (now Opayo) is one of the more configurable card gateways in the UK and Irish markets and is in heavy use across mid-sized stores. Auth, capture, void, and refund are separate operations, 3D Secure adds another lifecycle dimension, and the WooCommerce extension writes all of that data into order meta. The default Orders screen ignores it.

A merchant sees the WooCommerce status and the total, not whether the auth has been captured, not whether the 3DS challenge was abandoned, not whether AVS matched, not how close the auth is to expiry. Finance teams reconcile MySagePay batches by hand, risk teams chase chargebacks reactively, and support teams answer dispute questions by opening each order one at a time. SleekView reads the data the plugin already records and exposes it as columns.

The plugin's own handlers continue to run. The change is that gateway-level visibility finally lives inside the WordPress admin as a queryable table.

Questions

Common questions about SleekView for WooCommerce SagePay (Opayo)

Yes. The meta keys are the same across both brandings since Opayo is the same product re-named. SleekView reads whichever the WooCommerce extension version installed actually writes, scanned from wc_orders_meta at config time.

 

Yes. Keys read from wc_orders_meta on HPOS and from postmeta on legacy stores. The same configuration works on both schemas because SleekView detects the active path automatically.

 

Yes. _wc_sagepay_3dsecure_status records values like Authenticated, Attempt, Abandoned, or Not Checked. Filter on Abandoned to audit drop-off at the challenge step or on Attempt for soft-decline review.

 

Yes. Status edits route through WooCommerce CRUD, so woocommerce_order_status_changed fires and the SagePay extension's own capture, void, and refund handlers run as expected from the order context.

 

Yes. Build a view on woocommerce_payment_tokens filtered by gateway slug. Join woocommerce_payment_tokenmeta for the SagePay token reference per saved card.

 

Yes. Build a view scoped to one order or customer with transaction id, 3DS status, AVS or CV2, and order notes. Export to CSV or PDF and attach to the dispute response.

 

Queries hit indexed columns on wc_orders directly and use wc_orders_meta indexes for meta filters. Aggregates (lifetime captured value per customer) are opt-in per view since they're heavier than direct columns.

 

No. The Opayo portal is the source of truth for settlements, chargebacks, and gateway-level history. SleekView gives WooCommerce-side ops a row-level view of the data the plugin syncs into WordPress so reconciliation requires fewer context switches.

 

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