SleekView Kanban for Mollie Payments for WooCommerce
Mollie Payments for WooCommerce writes payment method, payment ID, customer reference, and last webhook status to each order in wc_orders_meta. SleekView Kanban groups orders by Mollie status so finance drags entries between Open, Paid, Refunded, and Failed.
♾️ Lifetime License available
Run the Mollie ops board over wc_orders_meta
Mollie Payments for WooCommerce covers the full European payment-method landscape: iDEAL, Bancontact, SEPA Direct Debit, Klarna, SOFORT, plus cards and Apple Pay. The plugin writes Mollie-side state to each WooCommerce order through wc_orders_meta with _mollie_-prefixed keys: payment ID, payment method, customer reference, last webhook status, and a webhook-receipt timestamp. The default WooCommerce order screen reads those as raw meta values, which makes 'how is iDEAL trending today' or 'which SEPA orders are still pending clearance' a manual filter and a scroll.
SleekView Kanban reads wc_orders joined to the Mollie meta keys and groups orders by the Mollie payment status: open, paid, authorized, canceled, expired, refunded, failed. The board renders one column per consolidated state: Open, Paid, Refunded, Failed. Each card shows the customer name, the amount and currency, the payment-method badge (iDEAL, Bancontact, SEPA, Klarna, card, Apple Pay), and a small webhook-status chip for orders whose webhook is overdue.
Drag a card from Open to Paid and SleekView checks the Mollie payment status via the plugin's stored credentials and updates the WooCommerce order accordingly. Refunds drag straight from Paid to Refunded with the standard Mollie refund endpoint. The webhook-recovery flow stays available on the card menu for orders whose webhook never arrived, so the ops team has a board-driven place to run reconciliation instead of digging into the Mollie Dashboard.
Workflow
From Mollie meta to a payments ops board
Point SleekView at the Mollie meta keys
Pick the Mollie payment status as the status column
Choose what shows on each card
Enable drag-and-drop with the Mollie API
Sample board
Sample Mollie payments ops board
Comparison
Default Mollie plugin admin vs SleekView Kanban
Default Mollie plugin admin
- Mollie plugin exposes payment state via raw _mollie_ meta keys on the WooCommerce order page
- No kanban view grouping orders by Mollie payment status across the working day
- SEPA clearance queue requires the Mollie Dashboard or a manual order-list filter
- Webhook-overdue orders only surface when ops notices a missing status update on the order
- No cross-method boards splitting iDEAL, Bancontact, SEPA, Klarna, card cohorts
SleekView Kanban
-
One card per
wc_ordersrow with a_mollie_payment_idmeta value - Group by Mollie status promoted from the payment-status meta
- Drag a card and SleekView calls the Mollie status-check or refund API for the payment ID
- Payment-method badge shows iDEAL, Bancontact, SEPA, Klarna, card, or Apple Pay
- Webhook-overdue chip flags orders whose Mollie webhook is later than the SLA
Features
What SleekView Kanban gives you for Mollie Payments for WooCommerce
Webhook recovery from the card menu
Mollie webhooks occasionally fail or arrive late. SleekView reads _mollie_last_webhook_status and timestamps and exposes a 'Refetch from Mollie' action from the card menu, which calls the status endpoint and reconciles the WooCommerce order so the working queue stays accurate.
Method-aware boards
iDEAL, Bancontact, SEPA, Klarna, card, and Apple Pay each behave differently. SleekView promotes _mollie_payment_method as a column and renders a badge per card. A saved board filtered to SEPA only becomes the clearance-watch queue, with a card showing the date SEPA settlement is expected.
Drag calls the Mollie API
Drop a card on Refunded and SleekView calls the Mollie refund endpoint for the payment ID, using the plugin's stored credentials. The WooCommerce order status updates and the standard payment hooks fire, so the storefront and the Mollie Dashboard agree without manual reconciliation.
Audience
Three ways stores use the Mollie kanban view
Daily payment-status reconciliation
Open the board, read the Open column count, and refetch any cards with overdue webhooks via the card menu. SleekView updates the Mollie status, the card lands in Paid or Failed automatically, and the daily reconciliation finishes without a Mollie Dashboard session.
SEPA clearance tracking
Filter the board to payment_method equal to SEPA Direct Debit. The Open column becomes the SEPA clearance queue, each card carries an expected clearance date, and ops sees at a glance how many orders sit waiting versus how many cleared today.
Cross-method finance review
Finance opens a board with all payment methods visible and uses the badge to assess the day's mix. iDEAL share, Bancontact share, card share, and Klarna share all read from column counts cross-tabulated with the method badge, ready for the weekly review.
The bigger picture
Why Mollie reconciliation belongs on a kanban
Mollie's strength is breadth: one plugin, one merchant account, many European payment methods, each with its own clearance behavior. The default WooCommerce order screen treats Mollie state as raw meta on individual orders, which means the daily reconciliation, the SEPA clearance watch, the webhook-recovery sweep, and the cross-method finance review all run as separate row-list filters. The kanban consolidates that work into one screen.
Four columns split the day, badges on the card front surface payment method and webhook state, and a card-menu action runs the Mollie status-refetch flow without leaving WordPress. Drag-and-drop calls the same Mollie API the plugin uses today, so the refund endpoint, the webhook handler, the Mollie Dashboard, and the WooCommerce order lifecycle all keep working unchanged. The board reads in seconds, the ops team measures progress in column counts, and the cross-method finance review answers from badges rather than from a Mollie Dashboard tab.
Questions
Common questions about SleekView Kanban for Mollie Payments for WooCommerce
No. The Mollie Dashboard remains the canonical surface for account-level reporting, payout reconciliation, and customer-facing case handling. SleekView is a WooCommerce-side board that calls the same Mollie API the plugin uses, so day-to-day refund, status-refetch, and reconciliation work happens without leaving WordPress.
 SleekView calls the Mollie status endpoint for the payment ID stored in _mollie_payment_id on the order, using the plugin's stored credentials. If Mollie reports the payment as paid, SleekView writes the WooCommerce order status to processing or complete according to the store's order-handling rules and the standard payment-complete hooks fire.
 SleekView reads _mollie_last_webhook_status and the receipt timestamp on render. If the timestamp is older than the configured SLA (default 30 minutes for non-SEPA, 5 days for SEPA), the card shows an overdue chip. The card-menu 'Refetch from Mollie' action calls the status endpoint and reconciles the order.
 Yes. The plugin records the method on _mollie_payment_method. SleekView promotes that as a column and lets a saved board filter on it, so an iDEAL-only board scopes to that method, the column counts answer the daily iDEAL question, and cross-method noise stays out of the working view.
 Dragging to Refunded opens the refund dialog where the operator confirms full or partial amount and a reason. SleekView then calls the Mollie refund endpoint the same way the plugin's order-page refund action does. The WooCommerce order status updates to reflect the refund and the meta records the refund ID.
 SEPA Direct Debit clears over several days, and Mollie reports the payment as open until clearance. SleekView keeps SEPA cards in the Open column for the whole clearance window, with an expected-clearance date on the card. Once Mollie's webhook reports paid, the card moves to Paid automatically.
 Yes. Mollie supports test and live API keys. SleekView surfaces the environment as a column and lets every board filter on it, so the live board hides test traffic and a sandbox board scopes to QA orders only. The same applies to multi-merchant stores running multiple Mollie accounts.
 The board reflects the change on the next refresh. SleekView reads wc_orders_meta live, so webhook-driven updates from Mollie (paid confirmations, cancellations, refund posts) land on the board the same way as a drag-driven update. The card moves to the column matching the new Mollie status.
 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