SleekView for Gravity Forms Stripe
SleekView reads gf_entry plus the Stripe transaction meta the Stripe add-on stamps onto each paying entry (transaction id, customer id, payment method) and renders the queue as a sortable, filterable table with amount, status and method as real columns alongside entry ID and form.
♾️ Lifetime License available
Gravity Forms takes Stripe payments. The queue needs a real revenue table.
The Gravity Forms Stripe add-on routes payments through Stripe and stamps the transaction outcome onto the entry. gf_entry tracks payment_status, payment_date, payment_amount and currency. gf_entry_meta carries the Stripe-specific keys: transaction_id, customer_id, payment_method (card, link, ach, sepa), capture status and fee amount.
The default Gravity Forms admin shows payment status as a column on the per-form Entries screen and surfaces the Stripe transaction inside each entry's detail view. It does not list paying entries across forms as a single revenue table, filter by payment method, or surface refund and dispute cohorts at a glance. Finance teams end up exporting to CSV or jumping to the Stripe dashboard, which does not know which form produced which charge.
SleekView reads gf_entry and the Stripe meta directly. Amount, currency, payment status, payment method, customer ID and Stripe transaction ID sit as real columns next to entry ID and form. Sort by amount, filter to refunded across every form, bulk-export a reconciliation cohort against the matching Stripe payout.
Workflow
How SleekView reads Gravity Forms Stripe data
Pick the entry source
Compose the column set
Save and scope the view
Edit inline or export
Sample columns
A typical Gravity Forms Stripe revenue table
gf_entry + gf_entry_meta (stripe_transaction_id, stripe_customer_id, payment_method)
| Entry | Amount | Status | Method | Customer | Paid |
|---|---|---|---|---|---|
| 7301 | $249.00 | Paid | Card | cus_NkP2 | May 14 |
| 7300 | $49.00 | Paid | Link | cus_NkN9 | May 14 |
| 7299 | $899.00 | Pending | ACH | cus_NkL3 | — |
| 7298 | $149.00 | Refunded | Card | cus_Nk8H | May 12 |
| 7297 | $59.00 | Failed | Card | — | — |
Comparison
Default Gravity Forms Stripe admin vs SleekView
Default Gravity Forms admin
- Payment status visible per entry, no cross-form revenue table
- Stripe transaction ID and customer ID hidden in each entry's detail view
- No filter to refunded or failed transactions across every form
- Bulk export per form, not as a single revenue cohort
- No saved per-role view for finance, support or product
SleekView
- Read directly from gf_entry joined with the Stripe add-on meta
- Amount, payment status, payment method and Stripe customer ID as sortable columns
- Filter to refunded or failed across every form in one click
- Export a date-bounded cohort for reconciliation against the matching Stripe payout
- Filters carry between the table view and the chart view on the same paying entries
Features
What SleekView gives you for Gravity Forms Stripe
Revenue from gf_entry directly
Render Stripe-paying entries as a real revenue table reading from gf_entry and the Stripe meta. Finance gets the cohort in WP Admin without jumping to Stripe or a spreadsheet.
Filter by payment method
Sort and filter by payment_method to see card versus Link, ACH or SEPA. Useful for understanding alternative-method adoption and prioritising checkout polish.
Surface failed and refunded entries
Filter by payment_status in (Failed, Refunded) and the table reveals the cohort across every form. Support can triage friction without exporting CSVs.
Audience
Who uses SleekView for Gravity Forms Stripe
Finance teams
Anchor a weekly close on Stripe-paying entries filtered by date_paid. Export the cohort for reconciliation against the matching Stripe payout.
Founders and operators
Watch revenue concentration by sorting by amount and grouping by form. Spot the workhorse checkout and the experiments that are not paying their way.
Customer support
Filter to refunded or failed entries and group by form. Identify the checkout generating the most payment friction and brief product on what to fix next.
The bigger picture
Why Gravity Forms Stripe needs a revenue table
Gravity Forms with the Stripe add-on is how many WordPress sites take payments without standing up WooCommerce. The data is captured cleanly, gf_entry already carries payment_amount, payment_status, date_paid and currency, and the Stripe add-on layers in transaction IDs, customer IDs and payment-method labels. What is missing is the table view.
Finance teams should not be exporting CSVs every Monday to figure out the previous week's revenue, and operators should not be flipping between WP Admin and the Stripe dashboard to understand which form produced which charge. SleekView reads what Gravity Forms already writes and renders it as a real revenue table. Amount, method, status, customer and form become sortable columns on a single screen in WP Admin.
The Stripe dashboard remains the source of truth for the gateway side, but the form side of the picture finally has a list view to live in.
Questions
Common questions about SleekView for Gravity Forms Stripe
The Gravity Forms gf_entry table plus the Stripe meta the add-on writes to gf_entry_meta (stripe_transaction_id, stripe_customer_id, payment_method, capture_status). No data is duplicated, the table runs against the tables the add-on already maintains.
Yes. payment_amount and payment_status mirror what Gravity Forms received back from the Stripe API. Subtle differences can appear if the Stripe dashboard reflects updated states (refunds, disputes) that Gravity Forms has not yet synced via webhook, but the standard charge lifecycle matches.
Yes if the add-on writes the Stripe fee amount into entry meta. SleekView pivots that as a column so net revenue can be calculated alongside gross. Sites that do not store the fee see gross amounts only.
Yes. Recurring entries appear in gf_entry with the relevant subscription flags and the Stripe subscription ID in meta. Filter by subscription ID or recurring-only entries for an MRR cohort.
Yes. gf_entry stores the currency code per entry. Sort or filter by currency_code to split USD, EUR, GBP and the rest. Useful for businesses taking multi-currency payments through Stripe.
No. Gravity Forms indexes gf_entry on payment_status and date_paid, and the Stripe meta keys are indexed by entry_id. The queries run efficiently on sites with hundreds of thousands of paying entries.
Yes. Filter to payment_status of Refunded or Partially Refunded and sort by date_paid. The table makes the refund cohort visible without exporting CSVs.
Yes. Each saved SleekView is scoped by WordPress capability. Finance sees the revenue and reconciliation table while support sees the refund queue, each with its own filter presets and exports.
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