x402 is making machine-native payments trivial — an agent hits an endpoint, pays a fraction of a cent, gets its response. Beautiful. But it quietly creates a new problem: if you're the one getting paid, you now have hundreds or thousands of tiny, agent-driven transactions a month that someone eventually has to turn into receipts, records, and something your accountant can actually use.
That's what we're building Stubly for. You point your x402 payment events at a Stubly webhook; it deduplicates them, generates clean PDF receipts, keeps a compliance-grade transaction record, and exports to CSV / QuickBooks / Xero. It sits downstream of the payment — we don't touch the money, we just make the paperwork disappear.
We're in early access and, honestly, still learning. If you're shipping x402 endpoints and getting paid over them: how are you handling the accounting side today, if at all? I'd love to compare notes — reply here or reach me at jeff@getstubly.com.
— Jeff, getstubly.com
Top comments (1)
Sitting downstream of the money is a smart scope choice. One thing I wondered though: the record is only compliance-grade if the events feeding it are real, and a webhook URL is something anyone can POST to. Do you verify events against the settlement layer before they become receipts, or is the payload trusted as-is during early access?