Works with the store you already run.
There are two jobs here, and they are different. Reporting sales is what creates verified impact: a connector, the plugin, or one API call. Showing proof is the widget, proof pages, and your public verification page. Wire the first, embed the second.
Report your sales
Verified impact starts with a reported sale. Pick the path that matches your stack.
Stripe
Tie donations to Stripe payment events. Add a webhook endpoint in Stripe, select two events, paste the signing secret.
WooCommerce
WordPress plugin that reports orders to the API and embeds the widget.
REST API
Record sales and fetch proof from your own backend. Two endpoints, API-key auth, idempotent by design.
AI builders
Building with Bolt, Lovable, Cursor, or v0? Paste one prompt from your dashboard and the AI wires the integration correctly.
Show the proof
Once donations verify, put the evidence where customers can see it. These display your impact. They do not report sales.
Impact widget
One script tag shows your verified totals on any site, including Webflow, Squarespace, and Wix custom code blocks. Five minutes to embed.
Proof pages
Every donation gets a public proof page. The receipt kit gives you a ready-made receipt line and QR code to link from order confirmations.
Verification page
Your public page at omguarantee.com/verified/you, showing verified totals, charities, and on-chain anchors anyone can check.
Don't see your platform?
If your store can send a webhook or make one server-side API call, it can report sales. If it lets you add a script tag, it can show the proof. Tell us what you run and we'll point you at the fastest path.