SleekView Kanban for Clearpay for WooCommerce
SleekView reads WooCommerce orders paid through the Clearpay UK and European BNPL gateway, groups every order by status, and lets finance drag orders between Pending, Approved, Completed, and Refunded so the underlying WooCommerce order updates the moment the column changes.
♾️ Lifetime License available
Why Clearpay BNPL orders fit a kanban view
Clearpay for WooCommerce is the UK and European brand of Afterpay for Buy Now Pay Later payments. Orders come through with the standard WooCommerce statuses like wc-pending, wc-processing, wc-on-hold, wc-completed, and wc-refunded, plus Clearpay-specific metadata in wp_postmeta for the clearpay_order_id, the clearpay_token, the consumer_id, and the Clearpay payment status. The native WooCommerce orders screen shows them mixed with all other orders.
SleekView Kanban reads the same WooCommerce orders you would query with WC_Order, filtered to orders that used the Clearpay gateway. Pick post_status as the group column and every order becomes a card slotted under Pending, Approved, Completed, or Refunded. Card fronts show the customer name, the order total in GBP or EUR, the clearpay_order_id, the consumer_id, the date placed, and the Clearpay installment plan summary, so finance has every Clearpay-specific detail right on the card.
Dragging a card between columns calls the standard WooCommerce status transition the admin uses, which fires woocommerce_order_status_changed. Clearpay's refund flow fires for refund transitions when configured, the customer notification email goes out through WooCommerce's email module, the Clearpay Merchant Portal reflects the change, and any extension subscribed to the WooCommerce hooks reacts, exactly as it would after a manual admin status change.
Workflow
From Clearpay order list to live UK finance board
Connect your WooCommerce order source
Pick post_status as the group column
Choose what each Clearpay order card shows
Enable drag-and-drop status updates
Sample board
Sample Clearpay BNPL order board
Comparison
Default WooCommerce orders vs SleekView Kanban
Default WooCommerce orders list
- Flat orders list with status as a small label per row, no Clearpay distinction
- No visual sense of how many Clearpay BNPL orders are pending versus completed
- Bulk status changes require checkboxes and a dropdown at the top of the screen
- Filtering by payment gateway requires custom URL parameters or SQL queries directly
- Finance staff need full shop manager access just to flip an order to refunded
SleekView Kanban
-
Reads the standard
wp_postsor HPOS orders directly without a sync -
Drag a card to fire
woocommerce_order_status_changednormally - Cards show customer, total in GBP or EUR, clearpay_order_id, consumer_id, plan
- Column counts update live so a Pending Clearpay backlog stays visible at all times
-
Per-role capabilities tie writeback to
edit_shop_orderas expected
Features
What SleekView Kanban gives you for Clearpay for WooCommerce
Native Clearpay BNPL engine
Every column maps to a real WooCommerce order status registered through wc_register_order_status. Clearpay refund flow fires for refund transitions when configured, customer emails go out through WooCommerce, the Clearpay Merchant Portal reflects the change, and subscribed extensions react.
Drag-and-drop with audit trail
Each move writes a note to the order timeline naming the user who dragged it and the column it came from. If a finance lead pushes a refund through the board, the chain of custody stays permanent and visible to compliance reviewers later during the next monthly audit cycle window.
Saved boards per region
Filter to Clearpay transactions from the UK for the UK finance lead, EU transactions for the EU reconciliation lead, and high-value transactions for the senior reviewer. Each saved view becomes a shareable URL that opens straight into the right board every shift the finance team works.
Audience
Where a Clearpay kanban changes daily work
Daily UK BNPL reconciliation
UK finance pulls the Completed column for the day filtered to Clearpay, sums the totals in GBP and EUR separately, and reconciles against the Clearpay Merchant Portal payouts report for the day without manually exporting CSVs from both systems to find discrepancies daily in spreadsheets.
BNPL approval triage
When Clearpay orders sit in Pending longer than the Clearpay SLA, finance filters the affected cohort by Clearpay payment status, identifies the BNPL approval issue, and contacts Clearpay support with the clearpay_order_id values from the cards to resolve before more orders stall in queue.
Refund workflow
Support drags refund-approved orders from Completed to Refunded, the Clearpay refund flow fires for the refund transition, and finance reconciles the refund batch against the Clearpay Merchant Portal refund report without having to manually trigger refunds from Clearpay one at a time.
The bigger picture
Why this view matters for a Clearpay-connected store
UK and European stores running Clearpay for WooCommerce process hundreds of BNPL transactions every day through the Clearpay gateway. Some clear instantly after Clearpay approves the installment plan, some take a few minutes for additional review, some get declined when the customer fails the credit check. The default WooCommerce orders screen mixes Clearpay transactions with COD, prepaid, and other gateway orders, which makes Clearpay-specific reconciliation a CSV export exercise every single day for finance.
The disconnect between what the Clearpay Merchant Portal shows and what WooCommerce shows is the source of most accounting headaches for Clearpay merchants in the UK and EU. A successful BNPL approval lands in Clearpay but the WooCommerce order stays Pending because the webhook failed. A refund shows in WooCommerce but never appears in the Clearpay Portal because the integration was misconfigured.
A daily payout from Clearpay shows revenue that does not match WooCommerce. A kanban view that reads and writes the same WooCommerce orders the gateway processed, filtered to Clearpay specifically, keeps the team and the books honest. Every drag is a real status change, every column count reflects the real Clearpay pipeline health, and the cards themselves carry enough context for a new finance analyst to handle reconciliation on day one of the job.
Questions
Common questions about SleekView Kanban for Clearpay for WooCommerce
Yes. SleekView reads standard WooCommerce orders and filters to orders that used the Clearpay gateway through the order meta. The board scopes to Clearpay transactions so finance sees Clearpay-specific reconciliation separately from COD and other payment method orders processed on the storefront.
 Yes. The plugin's refund integration listens for woocommerce_order_status_changed to refunded and calls the Clearpay refund API when configured. Dragging a card to Refunded fires the same status transition the admin uses, so the Clearpay refund fires exactly as it would after a manual refund.
 Yes. Card fields are configurable per board. Most finance teams show the customer billing name, order total in GBP or EUR, clearpay_order_id from order meta, consumer_id, date placed, and the Clearpay installment plan summary so finance has every detail directly visible on each card.
 Yes. Every move runs through current_user_can('edit_shop_order') before the status writeback hits the database. A shop manager can move anything, a finance role with limited access can drag for personal sorting but the change does not persist, and unauthorized moves snap back with a toast.
 Filters apply at the database query level. A typical board scopes to Clearpay orders from the current and prior day for the daily reconciliation, so the rendered card count stays under a thousand. Older orders remain queryable through a separate saved archive view for monthly audits cycle.
 Yes. SleekView reads from the wc_orders table when HPOS is enabled and falls back to the wp_posts orders post type otherwise. The same column mapping and drag behavior work in both modes, and you can switch between them without redoing your saved board views on the finance team monitors.
 Yes. The board filter lets you include orders from multiple BNPL gateways like Clearpay, Klarna, and Sezzle or scope to Clearpay only. Most finance teams keep a dedicated Clearpay board for the daily reconciliation and a combined BNPL board for management reporting without rebuilding filters.
 Yes. Every drag writes an order note through WooCommerce's native order notes API. The note names the user, the source status, the destination status, and the timestamp. It shows up in the order edit screen, in the customer-facing order history if enabled, and in any export that pulls notes.
 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.
Lifetime ♾️
Most popular
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
€749
Continue to checkout