Where MerchantGuard leads
- Focused payment fraud detection
- Likely deeper integration with payment rails
- Niche depth on fraud-specific signals
Where GenZAgents leads
- Broader receipt format covering all AI work, not just payments
- Audit + compliance evidence packs
- Cross-provider portability
- Open spec on GitHub (prior-art defense against patent attempts)
Where MerchantGuard focuses
MerchantGuard targets the specific use case of agent payment fraud — when an AI agent transacts on behalf of a user, how do you detect fraudulent or unauthorised payments? Niche-focused; deeper on that specific signal stack.
Where GenZAgents has broader scope
Our receipt format covers all AI-mediated work, not just payments. Compliance evidence, audit trails, cross-provider portability, IDE integration, framework integration. Broader product; suited to org-wide deployment rather than payment-fraud-specific.
The patent prior-art angle
MerchantGuard filed USPTO 99462472 attempting to patent some aspects of receipt-style AI work tracking. Our public spec on GitHub (work-receipt-spec, pushed v0.1.0 May 2026) is prior art that limits the patent's scope. This is one of the explicit reasons we open-sourced the spec.
When MerchantGuard might be the right fit
If your specific concern is agent payment fraud and you want a specialised tool: MerchantGuard might suit. For broader trust + audit + compliance: GenZAgents.
Integration potential
MerchantGuard receipts (if they had a compatible format) could feed our receipt feed for fraud-signal augmentation. The integration story would benefit both products and the customer. Their adoption of our open spec would be the path.
Realistic competitive read
We compete on broader product surface. They compete on niche depth. Customers needing both buy the broader product (us) for the org-wide layer and might add MerchantGuard for specific payment-fraud lanes. The market has room for both at different layers.