No. SleekView Feedback reads directly from the WooCommerce order post type and any meta keys PayU writes to. You point it at the source, pick the columns for votes, status, category, author, and title, and the board renders. No ETL, no sync, no duplicated data. Anything PayU writes appears on the next page load.

Yes. SleekView ships with anonymous voting backed by cookies, so public visitors can upvote reported issues without a WooCommerce account. You can also require login if you want the board restricted to verified customers, and the same view handles both modes with a single toggle in the block settings.

Each visitor gets a cookie scoped vote token per item. Logged in users are tracked by user ID. The plugin also exposes a rate limit so a single IP cannot spam the board, which is enough to keep public checkout boards honest without forcing a signup wall in front of upset shoppers across Indian cities.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to HDFC netbanking, UPI collect failures, Paytm wallet refunds, or any combination of meta fields PayU already stores. Different boards on different pages can use different filters per bank or instrument.

Refund is just a category value on the order. You can write it into a meta key the WooCommerce order already understands or a dedicated column on a log table. Either way it shows up in the WordPress admin alongside the original transaction, so finance can act on the flag without leaving WordPress.

They write back to the source column, which means your queries and the WooCommerce orders screen can sort by that score. Several teams use the score to gate which payment bugs get triaged first, which makes the board operational and not just a vanity dashboard for the support manager to look at each week.

Both. SleekView ships as a Gutenberg block, an Elementor widget, a Bricks element, and a classic shortcode. Theme developers can also call the render function from PHP and pass a configuration array, so you can mount the board on any product, account, or help template without touching the page editor.

The view paginates server side and only loads the rows it needs to render the current page. Indexed meta keys stay fast even on long tables. For really busy shops, scoping the board by date or bank keeps both the query and the audience focused, so the page feels snappy even on Diwali and Big Billion Day rushes.