Yes. Cancellation writes go through MeprSubscription::cancel, which is the same action the MemberPress admin Cancel button calls. That means the gateway cancel API fires, the subscription status flips in mepr_subscriptions, and any access rules tied to that membership recompute. Failed gateway calls leave the card in its original column and surface the error on the card.

By default the four statuses MemberPress writes to mepr_subscriptions become columns: active, pending, cancelled, and suspended. You can hide columns you do not use, reorder them, and add a synthetic Failed column built from mepr_transactions where status is failed in the last 30 days for a dunning-focused board.

Yes. Point the data source at mepr_transactions instead of mepr_subscriptions and the statuses complete, pending, failed, and refunded become the columns. This is useful for sites that sell mostly lifetime memberships and want a refund-review board instead of a recurring billing board.

Yes. SleekView reads whatever status values are present in mepr_subscriptions, so custom values from add-ons or your own code appear as additional columns. You can assign a colour and an icon per custom status, and they participate in drag-and-drop the same way the built-in statuses do.

Yes. Card meta supports joins, so you can add the member email from wp_users, the membership level title from mepr_products, lifetime spend from a sum across mepr_transactions, and any user meta key. Computed columns such as days since last successful charge are also supported.

SleekView paginates per column, loads a configurable number of cards per page, and uses indexed reads against mepr_subscriptions on the status column. Counts at the column header are cached per filter set and refresh after each write. Boards stay responsive on sites with tens of thousands of subscribers.

Yes. Drag-and-drop writes are gated behind a WordPress capability you choose. Out of the box the board respects mepr-admin, but you can map any capability or custom role. Support team members see the same board with the cards locked so they can read context without being able to move members between billing states.

It works alongside. The MemberPress admin remains the source of truth for editing memberships, products, and rules. SleekView Kanban is a reading and quick-action layer on top of the same mepr_subscriptions table. Every card has a link straight to the underlying subscription edit screen for the cases where you need the full editor.