✨ 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 Clearpay & Afterpay for WooCommerce: orders & references as tables

Clearpay and Afterpay for WooCommerce write each transaction's Afterpay token and order ID into WooCommerce order meta. SleekView reads wc_orders joined with wc_orders_meta and renders BNPL orders as one queryable audit grid.

♾️ Lifetime License available

SleekView table view for Clearpay & Afterpay for WooCommerce

Clearpay and Afterpay reconciliation without the per-order panel

The Clearpay (UK, EU, AU as Afterpay) WooCommerce gateway persists each transaction's Afterpay token and order ID on the order row via WooCommerce order meta. With HPOS enabled, that data lives in wc_orders_meta against wc_orders; on legacy stores it sits in wp_postmeta against shop_order posts.

The default WooCommerce orders screen shows none of those identifiers on the row, and Clearpay's brand-versus-Afterpay regional split means a store accepting both can't easily filter the audit by brand. Reconciling against the Clearpay or Afterpay merchant dashboard currently means CSV export plus spreadsheet joins, one row at a time.

SleekView reads wc_orders joined with wc_orders_meta and surfaces the Afterpay token, order ID, and capture state as first-class columns. Sort by token to match the merchant dashboard row-for-row, filter by region or currency to split Clearpay from Afterpay, and inline-edit status with gateway hooks intact.

Workflow

Compose a Clearpay/Afterpay audit view in minutes

1

Pick the order source

Point at wc_orders (HPOS) or shop_order posts and filter payment_method to the Clearpay or Afterpay gateway slug. SleekView detects HPOS automatically.
2

Add Afterpay meta columns

Drag the Afterpay token, order ID, and capture state from the column picker. Each is sortable and filterable from the column header.
3

Save the audit views

Build named views per region (GBP Clearpay, AUD Afterpay, USD Afterpay) plus per state (authorized-not-captured, refund-pending). Each is one filter combination saved per role.
4

Edit through the CRUD layer

Inline status changes route through WooCommerce order CRUD so the gateway's capture and refund hooks fire as expected. Bulk operations run row-by-row through the same path.

Sample columns

A typical Clearpay/Afterpay order view

Joins wc_orders with wc_orders_meta to expose the Afterpay token and order ID as sortable columns.
Source: wp_wc_orders + wp_wc_orders_meta (HPOS) or wp_posts (post_type=shop_order) + wp_postmeta
Order Status Customer Total Afterpay token Date
#80312 Captured alex@studio.co £84.00 001.lmkj.4z3a Apr 24
#80311 Authorized ria@design.io £216.00 001.lmkj.4z2z Apr 24
#80310 Captured tom@hello.dev £52.00 001.lmkj.4z2y Apr 23
#80309 Declined mia@brew.coop £128.00 001.lmkj.4z2x Apr 23

Comparison

Default Clearpay & Afterpay for WooCommerce admin vs SleekView

Default Clearpay & Afterpay for WooCommerce admin

  • Afterpay token and order ID are buried in per-order meta
  • No filter splits Clearpay (UK/EU) from Afterpay (AU/US) by brand or currency
  • Authorized-not-captured BNPL orders aren't a default filter
  • Reconciling against the merchant dashboard needs CSV exports plus spreadsheet joins
  • Refund references from Clearpay/Afterpay aren't surfaced inline

SleekView

  • Read Afterpay token, order ID, and capture state as real columns
  • Filter by currency to split GBP Clearpay from USD/AUD Afterpay audits
  • Sort by token to match merchant-dashboard exports row-for-row
  • Inline status edits route through WooCommerce CRUD with gateway hooks intact
  • Per-role saved views gated by WordPress capability

Features

What SleekView gives you for Clearpay & Afterpay for WooCommerce

Tokens as first-class columns

Pivot the Afterpay token and order ID meta keys into named columns. Filtering, sorting, and matching against the Clearpay or Afterpay merchant dashboard becomes one click rather than a custom SQL join.

Brand and currency split

Build saved views per region: GBP Clearpay, AUD Afterpay, USD Afterpay. Currency lives on each order, so the same audit surface keeps each brand's reconciliation cleanly separated.

Inline edits via Woo CRUD

Status changes route through WooCommerce order CRUD so Clearpay and Afterpay capture, refund, and void hooks fire exactly as expected. Bulk operations iterate per row through the same path.

Audience

Who uses SleekView for Clearpay & Afterpay for WooCommerce

Finance

Reconcile the Clearpay or Afterpay merchant dashboard against wc_orders sorted by Afterpay token. Filter by date range and currency for clean monthly close.

Fulfilment

Filter to captured BNPL orders ready to ship with shipping address and line items visible inline. No per-order click-through for the daily pick list.

Support

Customer-rooted lookup of every BNPL order for an email, with Afterpay token and capture state on the row. Refund references surface inline during the call.

The bigger picture

Why multi-region BNPL stores need joined order tables

Clearpay and Afterpay are the same underlying BNPL provider with two brand names: Clearpay in the UK and parts of Europe, Afterpay in Australia and the US. A WooCommerce store that ships across those regions ends up with one gateway but two brand audits, and the default WooCommerce orders screen does not surface that distinction on the row. The Afterpay token and order ID are written into order meta, but reconciliation against the merchant dashboard still means exporting CSVs and joining them in a spreadsheet.

SleekView reads wc_orders joined with wc_orders_meta and puts the token, the order ID, and the capture state on the row. Currency becomes the brand split. Authorized-not-captured becomes one saved filter.

Inline edits route through the gateway's CRUD so capture, void, and refund hooks fire exactly as they would from the per-order screen. The merchant still has the standard Orders screen if they prefer it; the BNPL audit surface is what changes for finance, fulfilment, and support.

Questions

Common questions about SleekView for Clearpay & Afterpay for WooCommerce

Yes. HPOS stores write to wc_orders plus wc_orders_meta; legacy stores write to wp_posts (shop_order) plus wp_postmeta. SleekView reads whichever store is active and keeps the gateway column mapping identical.

 

The Afterpay token, order ID, capture-state flags, and any refund references the gateway writes per order. The column picker lists every Clearpay or Afterpay meta key with values actually present in your data.

 

Bulk status changes route through WooCommerce's order CRUD, so each row triggers Clearpay/Afterpay's capture hook exactly like a manual capture in the order screen. No special bulk-mode that skips gateway side effects.

 

Yes. Refund rows linked to the parent order via WooCommerce's refund relationship appear as a joinable child table, and any merchant-dashboard refund references the gateway writes are exposed as columns.

 

Yes. Currency lives on each order, and the gateway often writes the region or merchant identifier into meta. Build separate audit views per brand or per currency, gated by WordPress capability for the right team.

 

Currency lives on each order row. Filter or group by currency to keep GBP Clearpay reconciliation separate from AUD or USD Afterpay.

 

Yes. Saved views are gated by WordPress capability, so finance lands on a BNPL reconciliation view, fulfilment on a captured-ready-to-ship view, and support on a customer-rooted lookup.

 

Queries hit indexed columns on wc_orders (id, status, date_created_gmt). Joined meta filters use wc_orders_meta indexes. Keep heavier aggregates on detail views and lighter columns on triage views for fast pagination.

 

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