The Gravity Forms Stripe add-on stores payment data on every paid entry in wp_gf_entry_meta with keys like payment_status, payment_amount, transaction_id, and subscription_id. Statuses move through Processing, Active, Failed, Refunded, and Cancelled as Stripe webhooks fire back into the site. The default Gravity entries grid shows the rendered total but hides the rich payment lifecycle the add-on is tracking.

SleekView reads wp_gf_entry directly, joins to wp_gf_entry_meta, and surfaces every Stripe meta key as a possible grouping axis or card face element. The natural one is payment_status, which gives an immediate revenue snapshot, but you can also group by Stripe subscription state for recurring forms, by Stripe price ID for tiered offers, or by a custom Order stage field your team adds.

Dragging a card from one column to another writes the new value through GFAPI::update_entry and fires gform_post_update_entry plus the Stripe add-on entry hooks so any downstream feed continues to react. Cancelled subscriptions and refunded payments are filtered out of active boards by default but can be exposed on a churn audit board so finance can see why customers are leaving without polluting the active payment view.

The Gravity Forms Stripe add-on is excellent at moving real money, but its admin treats every payment as a row in the standard Gravity entries grid. That works when payments are occasional. It stops working the moment Stripe is processing dozens of charges a day, subscriptions are renewing on cron, and finance needs to see realized, pending, failed, and refunded revenue at a glance without exporting to a spreadsheet.

A kanban board fixes the part the add-on was never designed to fix: revenue visibility. Each column shows depth and rolled-up dollar value so finance can see at a glance whether processing payments are clearing fast enough or whether failed payments are piling up. Status changes happen with a drag instead of three clicks per entry, which compounds quickly once you are processing hundreds of payments a week.

Because every column maps back to real Stripe webhook data on the entry, the board is not a parallel system that drifts from Stripe. Everything you see is exactly what reconciliation feeds, accounting integrations, and the Stripe dashboard itself already see through the standard webhook events. The end result is a Gravity admin that finally matches how revenue teams actually work.