Cool to see another founder tackling this — respect the hustle.
I think we're solving different slices of the same problem. QBitFlow wraps authorization + verification in smart contracts. What I ended up building is just the verification primitive: "did X USDC land at Y address?" — no smart contract, no percentage fee, $0.05 flat.
For someone who wants a turnkey checkout flow, QBitFlow makes sense. For someone who already handles their own payment UX and just needs reliable confirmation, that's where paywatcher.dev fits.
On the $10k payment: $0.05 vs $75 is a pretty different cost structure. But it's also a different scope — apples and oranges to some degree.
Would genuinely be curious what others here prefer: full-stack payment handling or composable primitives?
I think we're solving different slices of the same problem. QBitFlow wraps authorization + verification in smart contracts. What I ended up building is just the verification primitive: "did X USDC land at Y address?" — no smart contract, no percentage fee, $0.05 flat.
For someone who wants a turnkey checkout flow, QBitFlow makes sense. For someone who already handles their own payment UX and just needs reliable confirmation, that's where paywatcher.dev fits.
On the $10k payment: $0.05 vs $75 is a pretty different cost structure. But it's also a different scope — apples and oranges to some degree.
Would genuinely be curious what others here prefer: full-stack payment handling or composable primitives?