SleekView Charts for Ninja Forms Stripe: Stripe payment dashboards
Group nf_sub submissions by payment_status, sum payment_total across Stripe forms, slice transactions by form ID, and chart paid versus failed Stripe txns per day without leaving WP Admin.
♾️ Lifetime License available
Stripe entries as cards, not submission rows
The Ninja Forms Stripe extension takes form payments via Stripe and writes the result to each nf_sub entry, storing keys like _payment_total, _payment_status, _transaction_id, and _stripe_charge_id in postmeta. The Submissions screen lists rows per form, so total Stripe revenue across forms, paid versus failed mix, and per-day curves all live in SQL queries rather than admin clicks.
SleekView Charts treats nf3_submissions as the dataset and exposes the Stripe meta keys as first-class columns. Sum _payment_total across completed Stripe charges, count entries by _payment_status, group by _form_id to rank forms by Stripe revenue, and slice by post_date for daily order curves. Filters set on the view cascade to every card so the entire dashboard scopes to one campaign in one move.
Charts share the dataset with Table and Kanban modes, so jumping from a Stripe revenue card to the submissions behind it is one tab. On a site with 50,000 entries spread across donation, event, and product forms, the indexed nf3_submissions queries Ninja Forms already uses keep cards responsive without paying for an external analytics tool.
Workflow
From Stripe entry meta to a real dashboard
Point Charts at nf_sub
nf_sub post type as the dataset. SleekView discovers Stripe meta keys like _payment_total, _payment_status, _transaction_id, and _stripe_charge_id for use as group-by and aggregation options.
Add chart cards
_payment_total, a Pie over Stripe status, a Bar of revenue per form, and an Area of paid entries by day. Each card reads from the same scope so view filters stay aligned.
Filter once, chart everywhere
Share by saved view
Sample dashboard
Charts you can build from Stripe submissions on Ninja Forms
Total Stripe revenue
_payment_total on nf_sub entries where _payment_status is succeeded, across the active filter window, with the previous window for context.
Sum(_payment_total)
Stripe status mix
_payment_status values from Stripe such as succeeded, requires_action, processing, failed, and refunded, stored in postmeta for catching pending or stalled charges.
Count
group by _payment_status
Stripe revenue per form
_payment_total per Ninja Forms form, joining nf3_forms for the form name so finance can rank checkout, donation, and event forms by Stripe revenue.
Sum(_payment_total)
group by _form_id
Paid entries per day
post_date, useful for spotting weekday rhythm and confirming Stripe payouts align with on-site form activity.
Count
group by post_date
Comparison
Default Ninja Forms submissions vs SleekView Charts
Default Ninja Forms Submissions screen
- Submissions screen lists per form, no cross-form Stripe aggregate
- Payment status filter exists but doesn't drive any chart
- Stripe _payment_total totals require manual CSV export to sum
- Daily Stripe revenue trend isn't visualized on the submissions page
- No saved dashboards per role for finance versus form admins
SleekView Charts
-
Number, Pie, Bar, and Area cards over
nf3_submissionsin one view -
Group by
_payment_status,_form_id,post_date, or any Stripe meta -
Sum
_payment_total, count paid entries, average order value - Filters cascade across every card on the same dashboard
- Shares dataset and saved views with Table and Kanban modes
Features
What SleekView Charts gives you for Ninja Forms Stripe
Stripe meta as columns
SleekView discovers Stripe keys like _payment_total, _payment_status, _transaction_id, and _stripe_charge_id on nf_sub postmeta, exposed as groupable, aggregatable fields with no glue code.
Group by every payment dimension
Form ID, Stripe status, transaction date, currency, and any custom field show up as group-by options, so finance builds the cards they would otherwise stitch from postmeta and the Stripe API by hand.
Filters apply to every card
Set a date range or one form once at the view level and every Stripe card scopes to the same slice, with no drift between widgets when the team narrows to a single payment method or campaign.
Audience
Who builds Stripe dashboards with SleekView
Finance
Sum _payment_total across succeeded Stripe entries, chart paid versus failed, and reconcile site totals against the Stripe dashboard without a CSV step or external BI.
Sales operations
Track daily Stripe order velocity across donation and product forms, spot which forms drive Stripe revenue, and split by campaign filters set once at the view level.
Form admins
Audit failed and requires_action Stripe entries by form, catch refund spikes, and verify the meta keys the gateway is writing for every submission across the site.
The bigger picture
Why Ninja Forms Stripe data deserves charts
Stripe is the gateway many Ninja Forms sites lean on for product, donation, and event payments because the extension stays inside the existing submission workflow. The submission data is rich. Every entry carries a payment status, a charge ID, a total, a currency, and the form context, but the Submissions screen only paginates rows.
Finance teams reconciling a Stripe payout cycle need the sum of succeeded totals over a date range. Sales ops want to know which form drives the most Stripe volume this month. Form admins want pending or requires_action entries that need follow-up.
None of these are exotic. They are numbers Stripe already wrote into postmeta. SleekView Charts surfaces them as configurable cards on the same dataset Ninja Forms uses, so Stripe reporting becomes one saved view instead of a spreadsheet ritual at month end.
Questions
Common questions about SleekView Charts for Ninja Forms Stripe
Yes. The Stripe action writes its result to postmeta on each nf_sub entry, using keys like _payment_total, _payment_status, _transaction_id, and _stripe_charge_id. SleekView discovers those keys and exposes them as group-by and aggregation options.
Numeric aggregation treats _payment_total as a number regardless of currency, so a naive sum mixes EUR, USD, and GBP into one figure. Group or filter by the currency meta to keep per-currency sums separate, the usual finance reconciliation pattern.
Aggregations run as SELECT ... GROUP BY against indexed columns on nf3_submissions and the related postmeta. Card render time scales with the cardinality of the group-by, not raw row count, so hundreds of thousands of entries stay responsive when grouping by _form_id or _payment_status.
Yes. _payment_status tracks succeeded, requires_action, processing, failed, and refunded. Build a Pie or Bar grouped by status to see the mix, or filter to requires_action and put a Number card on the count so the team chases the right entries quickly.
Cards re-query on view load and on filter change. Set a refresh interval per view if a finance dashboard needs near-live counts. Idle dashboards don't poll, so a closed view doesn't add database load.
Yes. Save views and scope them per WordPress role or capability. Finance sees a payment_total dashboard, form admins see entry volume per form, and editors see only the forms relevant to their team. Each user keeps their personal filters.
SleekView only counts entries that actually have the Stripe meta keys, so older submissions without the gateway data don't pollute the totals. Filter to the start date when Stripe went live to keep the comparison clean across periods.
Each card exports its aggregated rows as CSV with the group-by labels and the aggregate values. Useful for sending finance the raw _payment_status counts behind a Pie or archiving the campaign-end snapshot of a donation form's Stripe revenue.
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 checkoutBrowse more
- Woo Product Reviews Pro
- Yith Woocommerce Ajax Product Filter
- Retainful
- Wholesale Suite
- Woocommerce Zip Checkout
- Yith Woocommerce Order Tracking
- Wc Frontend Manager
- Mollie Payments
- Woocommerce Currency Switcher
- Lemonsqueezy Wp
- Charitable
- Yith Woocommerce Stripe
- Atum Inventory Management
- Wt Woocommerce Customer History
- Woocommerce Subscriptions
- Private Content Restricted Content
- User Role Membership
- Ultimatemember Verified Users
- Memberium For Keap
- Ultimatemember Private Messages
- Kleo Membership
- User Meta Manager
- Kartra Membership
- Simple Membership Pro
- Pmpro Bbpress
- Memberful Wp
- Easy Affiliate
- Armember
- Woocommerce Memberships
- Wp Affiliate Manager