Hi, I have a custom button in XYplorer that runs a little personal script I’ve been using for over a year.
It retrieves the CSV payment exports from my coaching clients, renames and organizes everything by month and amount into their project folders. It usually does the job without me having to lift a finger. Three weeks ago, while I was in a remote session with a client (a coach who runs a paid Discord server for $97/month), the script suddenly crashed.
He’d just switched from Stripe to Whop to process his community’s subscription payments... And, of course, the CSV export format changed… different columns, different structure my parsing went haywire immediately. So I had to spend part of the evening figuring out exactly what Whop was returning before tweaking the parsing, because guessing blindly about client payment data isn’t exactly the best idea. After digging around a bit, I came across a helpful Whop review that clearly detailed the columns and fees (which really helped me get the script back on track). The result: the script is now updated, and it’s been running smoothly ever since. I’m curious to know if anyone else here has ever had this kind of issue with scripts related to payment platform exports that change without warning.
An XYplorer script that causes issues with Whop—a good Whop review helped me out
-
Elyot
- Posts: 1
- Joined: 16 Oct 2026 12:11
XYplorer Beta Club