WP Simple Pay turns any WordPress page into a Stripe checkout. Every successful or attempted payment writes a row into the plugin's transactions table with the Stripe payment intent ID, the customer email, the amount, the currency, the live or test mode, and a status column carrying the Stripe value such as succeeded, requires_action, processing, failed, or refunded. Subscriptions live in a related table with their own Stripe status: active, past_due, canceled, or incomplete.

SleekView reads the WP Simple Pay transactions table and exposes the columns as fields. The natural column to group by is status, which moves through the Stripe values listed above for every payment. Cards show the customer email, the amount and currency, the payment method type from the Stripe metadata, and the date. A second board reads the subscriptions table and groups by its own status column so recurring revenue and one-off payments stay on separate views without losing context.

Drag and drop on a payments board is intentionally restricted: writing back to Stripe is destructive, so SleekView limits direct status changes to a manual review flag stored on the WP Simple Pay row rather than the Stripe status itself. The recommended pattern is to use the board for reading, sorting, and assigning, then trigger refunds and reactivations through the plugin's standard refund and cancel actions exposed on the card back, which call WP Simple Pay's existing Stripe helpers.

WP Simple Pay's transactions screen is a sorted list of rows that came from Stripe. It is reliable, it links to each charge in the Stripe dashboard, and that is most of what it does. Finance teams want more: they want to see how many charges are pending right now, how many failed today, how many subscriptions are past due, and they want to work each of those columns down during the day.

A kanban grouped by the Stripe status column gives that view. Succeeded, Processing, Pending, Failed, and Refunded become columns with counts, the subscription board adds Active, Past due, Canceled, and Incomplete next door, and each card carries the customer email, the amount, the currency, and the method. Card actions trigger the plugin's standard refund and cancel helpers so the integration with Stripe stays clean and direct status writes never bypass the gateway.

The team reads the same data the transactions screen reads, just with position and counts doing the heavy lifting.