Legitimate crawler blocked by Vercel bot mitigation on Hobby plan

Our production site (myslotscout.com) has been returning 403 with X-Vercel-Mitigated: challenge on every path (including /robots.txt and /) for over 24 hours now, to any non-JS-executing client - this includes our payment provider's (Paddle) automated domain-verification crawler, which needs to be able to read our site content to approve our account for live payments. A real browser passes the JS challenge silently, but this is blocking a legitimate automated compliance check, not an attack.

We understand verified bots (e.g. Googlebot) are automatically excluded from this check - is there a way to get a similar exception for this specific legitimate use case on the Hobby plan, since System Bypass Rules and system-mitigations pause aren't available without upgrading?

Example blocked request IDs from today:

fra1::1789566352-wyl7CFXTr1JltHDV2B6t796IINGB0BeL
fra1::1789492914-Ull4Z1rV9aMUXtIS8OxhWd8GMtXk6BMq
fra1::1789492930-YVSdkpGkELd2KFwU0nJNLSxWQETOmYIm

Project: permit-tracker (myslotscout.com)

Any help resolving this, or guidance on the right way to report it, would be appreciated.

Thank you for bringing this to our attention. To ensure this is investigated with the necessary priority and privacy, please report all security-related concerns, potential exploits, or abuse directly to the Vercel Security Team.

Please submit your report here: vercel.com/abuse

Reporting via this official channel is the fastest way to reach our security engineers and ensures that sensitive information is handled in a secure environment rather than a public forum.

Thanks, but to clarify - this isn't a security exploit or abuse report. Our own site is being incorrectly blocked by Vercel's own bot mitigation, and we're asking for help with that false positive (or guidance on the right support channel for it), not reporting malicious activity. The abuse form at vercel.com/abuse is specifically for reporting illegal or malicious activity on third-party sites, which doesn't fit this case. Could a member of the support team take a look?