Vowgate
Spending limits that a shopping agent can’t approve for itself.
- Context
- Individual submission · Razorpay AI Buildathon 2026
- Built with
- JavaScript · Node.js · Razorpay · Redis
- Status
- Buildathon submission
Approval belongs to the customer.
A customer reviews the exact shopping constraints before an agent can prepare a checkout. Vowgate checks the merchant, items, delivery, and final payable total against that approval.
The model can extract an instruction, but it cannot authorize a payment. Customer approval activates a signed shopping mandate. A second, single-use mandate binds the exact checkout—including its fees—to a hash. The server checks that boundary before creating a test order.
A checkout is more than an item price.
The canonical checkout includes tax, shipping, fees, currency, delivery, and catalog version. Changes after approval invalidate the binding. The public source also includes an atomic mandate-state adapter and tests for checkout tampering and replay.
What to know
Razorpay Test Mode only. The merchant, catalog, and conformance scenarios are synthetic. This is an individual buildathon submission, not an official Razorpay product or evidence of production payment security.
Read the source
Links point to the revision reviewed for this page. The repository may have newer work.