SleekView for PayMongo for WooCommerce: orders & PayMongo metadata as tables
PayMongo's WooCommerce plugin writes payment intent IDs, source types (GCash, Maya, card, GrabPay), and refund state as order metadata. SleekView pivots those keys into named columns, HPOS-aware, with gateway-scoped filters for Filipino finance teams.
♾️ Lifetime License available
PayMongo metadata as first-class columns
PayMongo for WooCommerce does not add its own primary tables. Payment data lives as WooCommerce order metadata: paymongo_payment_id, paymongo_payment_intent, paymongo_source_type (gcash, paymaya, card, grab_pay), and refund IDs are written through the WooCommerce meta API to wp_wc_orders_meta on HPOS or wp_postmeta on legacy. The default orders list ignores them because the screen renders core fields only.
SleekView reads the right storage automatically and pivots the paymongo_* meta keys into named columns. A payment-method filter scopes the view to PayMongo orders. Source type becomes its own column for GCash-versus-card cohort analysis, which is the central conversion question for most Filipino D2C stores running PayMongo as the primary gateway.
Edits route through the WooCommerce CRUD layer for the columns the plugin marks editable. Refunds still flow through PayMongo's admin action that calls its API; SleekView never duplicates that authentication path or proxies PayMongo endpoints.
Workflow
From buried meta keys to gateway-scoped tables
Detect storage mode
wc_orders_meta or postmeta accordingly. Storage detection matches what the PayMongo plugin itself does.
Pivot PayMongo keys
paymongo_payment_id, paymongo_payment_intent, paymongo_source_type, and refund IDs from meta into named columns. The agent UI lists every present key.
Save views per role
Edit inline or bulk-update
Sample columns
A typical PayMongo orders view
wp_wc_orders_meta + wp_postmeta (paymongo_* keys)
| Order # | Status | Total | PayMongo payment ID | Source | Date |
|---|---|---|---|---|---|
| #10801 | Paid | ₱4,200.00 | pay_NaAa01... | GCash | May 18 |
| #10800 | Awaiting source | ₱899.00 | pay_NaAa00... | Maya | May 18 |
| #10799 | Paid | ₱2,150.00 | pay_Na9zff... | Card | May 17 |
| #10798 | Failed | ₱540.00 | pay_Na9zfe... | GrabPay | May 17 |
Comparison
Default PayMongo for WooCommerce admin vs SleekView
Default PayMongo for WooCommerce admin
-
paymongo_payment_idhidden in order meta, never in the orders list - Source type (GCash, Maya, card, GrabPay) not exposed as a column
- No filter to isolate PayMongo orders from other gateways
- Payment intent IDs require opening each order's meta panel
- Refund state mixed with order status, no dedicated refund column
SleekView
-
Pivot paymongo_payment_id and
paymongo_payment_intentinto named columns - Filter by gateway to scope the view to PayMongo orders only
-
Surface
paymongo_source_typeas a column for GCash-vs-card cohort review -
HPOS-aware: reads
wc_orders_metaon modern stores,postmetaon legacy - Refund IDs visible inline for quick reconciliation
Features
What SleekView gives you for PayMongo for WooCommerce
HPOS-aware reads
PayMongo uses the WooCommerce meta API. SleekView mirrors that, reading wc_orders_meta on HPOS and postmeta on legacy. Views work the same on WooCommerce 8.2+ and older installs.
Source-type cohort
Pivot paymongo_source_type as a column and filter chip. Compare AOV and conversion between GCash, Maya, card, and GrabPay cohorts inside the orders view, without a separate analytics integration.
Settlement reconciliation
Surface paymongo_payment_id and payout reference as columns so finance can match PayMongo settlement files to WooCommerce orders inside one screen, not across tabs.
Audience
Who uses SleekView for PayMongo
Finance teams
Reconcile PayMongo settlement files against WooCommerce orders by filtering on payment method and date, with paymongo_payment_id inline. Filipino finance teams collapse weekly settlement matching into one saved view.
Conversion analysts
Segment by paymongo_source_type to compare GCash, Maya, card, and GrabPay conversion and AOV. The data is already in WooCommerce; surfacing it does not require a separate analytics warehouse.
Customer support
Customer queries a payment? Search by PayMongo payment ID or order number, see source type and refund state inline. Refund queries resolve without a PayMongo dashboard lookup.
The bigger picture
PayMongo metadata belongs in the orders list
WooCommerce's orders list shows core fields and treats gateway metadata as out-of-scope. That works for stores with one gateway. It fails for Filipino D2C stores running PayMongo across GCash, Maya, card, and GrabPay in parallel, where the conversion question "does GCash actually drive AOV" has a real answer in paymongo_source_type that nobody can see without opening every order.
Finance teams reconciling PayMongo settlements need paymongo_payment_id as a column to match payout lines. Support fielding refund tickets needs refund IDs inline. Conversion analysts comparing source types need paymongo_source_type as a filter chip.
The default workflow forces a tab-flip between the PayMongo dashboard and WooCommerce admin. SleekView pivots paymongo_* meta into proper columns and detects HPOS automatically, which collapses each workflow into one saved view. The gateway still owns the API operations, refunds still flow through PayMongo, but the data PayMongo writes into your orders finally becomes queryable as plain WooCommerce data.
Questions
Common questions about SleekView for PayMongo for WooCommerce
PayMongo does not add primary tables. Payment data lives as WooCommerce order metadata. SleekView reads wc_orders_meta on HPOS or postmeta on legacy automatically, regardless of storage mode.
paymongo_payment_id, paymongo_payment_intent, paymongo_source_type, refund IDs, and any other paymongo_* key your install writes. The agent UI lists every present key automatically.
No. Refunds go through PayMongo's API via the WooCommerce admin's refund flow. SleekView surfaces refund state but never proxies the gateway API. Inline edits affect only local fields like notes.
 
Yes. SleekView detects HPOS vs legacy and reads accordingly, same as the PayMongo plugin itself. WooCommerce 8.2+ defaults to HPOS; older installs on postmeta still work.
Yes. Filter by _payment_method = paymongo or by presence of paymongo_payment_id. Useful for stores running multiple gateways that reconcile each independently against its own settlement file.
Pivot paymongo_source_type into a filter chip and a column. Compare conversion and AOV between GCash, Maya, card, and GrabPay cohorts inside the orders view. This is the central conversion question for most Filipino D2C stores.
Yes. PayMongo writes failure codes to order meta on declined transactions. SleekView surfaces that as a column so support can triage clusters by reason instead of opening orders one at a time.
 Yes. Filter to PayMongo orders by date range, surface the VAT and other tax columns recorded as line-item meta, and export to CSV. The saved view reruns each month so finance does not rebuild the report.
 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
- Woocommerce Color Swatches
- Woocommerce Invoice System
- Woocommerce Marketplace Stripe Connect
- Woocommerce Allegro Pl
- Samcart Bridge
- Woocommerce Store Credit
- Woocommerce Product Vendors Pro
- Bigcommerce
- Woocommerce Shipping Multiple Addresses
- Woocommerce Multistore
- Woocommerce Clearpay Afterpay
- Woocommerce Distance Rate Shipping
- Bigcommerce Bridge
- Woocommerce Sezzle
- Woocommerce Order Export
- Buddypress Docs
- Userpro Pro
- Ultimatemember Social
- Memberium Active Campaign
- Tva Thrive Apprentice
- Memberpress Developer
- Ultimatemember Mailchimp
- Memberpress Affiliate Royale
- Loginpress Pro
- Premium Content Block
- Profile Magic
- Ultimatemember Followers
- Simple Membership
- Groups Paid Membership
- Simple Membership Pro