Skip to main content

Performance Tips

Most “PayRequest feels slow” reports come down to working with large lists one row at a time. These are practical habits — not code-level tuning — for keeping your dashboard fast and your workflow efficient as your customer, product, and transaction counts grow.

Use Tags to Narrow Down Large Lists

Rather than scrolling through hundreds of customers, subscriptions, or products, tag records into meaningful groups (e.g. “Enterprise”, “Annual Review”, “Legacy Pricing”) and filter by tag. This is faster to work with and makes Bulk Actions selection much quicker too, since tag filters support AND/OR logic.

Use Bulk Actions Instead of One-by-One Edits

If you’re about to make the same change to more than a handful of records — a price adjustment, a status change, a tag — do it once through Bulk Actions rather than opening each record individually. It’s faster for you and produces a single auditable entry in the action history instead of dozens of individual edits.

Export Instead of Browsing Thousands of Rows

For analysis, reporting, or just reviewing large volumes of data, export to CSV via Export Functions and work in a spreadsheet. Paging through thousands of dashboard rows is slower than filtering/sorting the same data locally once it’s exported.

Search and Filter Rather Than Scroll

List pages (Transactions, Customers, Products) support search and status/method filters — use them instead of paging through results manually, especially on accounts with a long transaction history.

Keep Automations and Tags Purposeful

A very large number of tags or automation rules can make the dashboard itself harder to navigate (not technically slower, just noisier). Periodically review and retire tags/automations you no longer use.

FAQ

Large datasets naturally take more time to query and render than small ones. Using the built-in search/filter to narrow what’s displayed, or exporting to CSV for offline analysis, is usually faster than scrolling through everything.
There’s no documented hard limit tied to your plan tier for these — if you’re operating at a scale where dashboard performance is a real bottleneck, contact support so we can look at your specific account.
Not meaningfully on its own, but an unwieldy tag list makes tag-based selection slower to use effectively. Keep tags purposeful and periodically prune ones you no longer need.

Next Steps

Bulk Operations

Make mass changes instead of editing records one at a time

Tags System

Organize large datasets for faster filtering

Export Functions

Work with large datasets offline