Venmo Web Payment Note Search

WHAT IT DOES

This userscript helps Venmo users search, organize, and export their payment history. It scans the Venmo web app payment history page and extracts payment notes/messages, amounts, dates, participants (sender/recipient), status, and emojis. The script provides a powerful searchable interface where you can filter payments by keyword (case-sensitive or not), date range, and amount range. It highlights matching terms in the results, detects recurring payments with similar notes or amounts, and exports filtered results as CSV or JSON. You can also highlight payments containing specific terms or emojis, making it easy to track specific types of transactions like rent payments, reimbursements, or shared expenses.

WHERE IT RUNS

The script works specifically on the Venmo web app payment history page (venmo.com). It runs entirely within your browser, reading only the visible content of the current page. It does not track your browsing history, access other tabs, or send any data externally. All search queries, filters, and settings are stored locally in your browser using GM_setValue.

HOW TO USE

After installation, open the panel by clicking the tool's icon in the BotGentz sidebar. First, navigate to your Venmo payment history page. Enter a search query in the "Search notes or messages" field to filter payments by note content. Toggle "Case sensitive" for exact matching. Use the date range and amount range filters to narrow results. Enter comma-separated terms in "Highlight terms" to visually highlight matching payments. Click "Search and filter" to run your query. Results appear in the panel with highlighted matches, recurring pattern detection, and a summary count. You can export the current results as CSV or JSON using the export section. Use "Clear results" to remove the current results from the panel.

THE TECHNICAL MECHANISM

This script uses DOM traversal and pattern matching to extract payment data from the Venmo web app. It scans the page for payment elements using common class names like [class*="payment"], [role="row"], and data-testid patterns. For each payment, it extracts text and applies regex patterns to identify dates (multiple formats), amounts with currency symbols, statuses (Completed, Pending, Canceled), and payment notes. The note extraction looks for text after "Note:" or "Message:" labels, and also captures emojis using Unicode range matching. The filtering system applies query matching to both the note and full raw text, date parsing to filter by range, and numeric comparison for amount filtering. The highlighting function wraps matched terms in brackets for visual identification. The recurring detection algorithm groups payments by normalized note text and rounded amounts, flagging patterns that appear two or more times with example dates. The export function formats data as standard CSV (with proper quoting) or JSON. All processing is local—no data leaves your browser.

THE PANEL

The panel is draggable anywhere on the screen and remembers its position between sessions. It can be collapsed to a small floating bubble to minimize distraction, and expanded again with a single click. The panel's width can be adjusted, and pressing the Escape key closes it instantly. All settings—search query, case sensitivity, highlight terms, and export format—are persisted locally using GM_setValue, so your preferences remain intact across page reloads and browser restarts.

PLEASE NOTE

This userscript requires the free BotGentz extension to function. The script is designed for the Venmo web app; it will not work on the mobile app or other websites. The payment extraction relies on the current structure of the Venmo web app—if Venmo updates their UI, the script may need to be updated. The script does not access your Venmo account credentials or API; it only reads what is visible on the page. Recurring payment detection is based on similar notes or amounts and may produce false positives—always verify patterns manually. No data from your browsing is stored or transmitted anywhere—all processing occurs entirely in your browser.