For Developers

Two endpoints and a script tag.

Report each sale with one server-side call. Fetch proof for the receipt. Show verified totals with the widget. If you'd rather not write code, a webhook connector or the AI-builder prompt does the wiring for you.

Get an API keySee integrations
Pick your path

Three ways in

All of them land in the same pipeline. A sale is recorded, a donation is committed, and verification runs from there.

Stripe connector

No code. Add a webhook endpoint in Stripe, select two events, paste the signing secret in your dashboard.

AI builders

Building with Bolt, Lovable, Replit, Cursor, or v0? Your dashboard has a paste-in prompt that gives the AI the exact contract. Often the fastest route.

REST API

Two endpoints, API-key auth, idempotent by design. Samples below.

The API

Real requests, real responses

Every sample below is served by the endpoint it names.

bash
# Server-side only. The API key is a secret. Never call this from the browser.
curl -X POST https://www.omguarantee.com/api/v1/events \
  -H "Authorization: Bearer omg_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "order_id": "1001",
    "amount": 59.90,
    "currency": "USD",
    "idempotency_key": "order-1001"
  }'

Field rules

  • ●order_id: required, non-empty string. Your store's order number. Do not put personal data in it.
  • ●amount: required, positive number. The sale total. Your impact rule decides the donation.
  • ●idempotency_key: required, non-empty string. Same key, same donation. Retries are safe.
  • ●currency: optional three-letter ISO code, defaults to USD.
  • ●The charity is not in the request. It comes from the impact rule you set in the dashboard. Until an active rule exists the API returns 422 and records nothing.
  • ●Auth is Authorization: Bearer omg_… from Dashboard, API Keys. Rate limit is 100 requests per minute per key.
  • ●Proof lookup accepts order_id or idempotency_key and returns proof_url, qr_url, receipt_line, amount, currency, charity name, and status. Impact units appear only when the charity has confirmed a rate.
  • ●Widget attributes: data-merchant (your public slug, required), data-widget (badge or counter), data-size (small, medium, large).
Receipt kit

Proof your customers can hold

Every donation gets a public proof page, excluded from search indexes, safe to link from a customer receipt.

Proof page

A public URL stating the amount, the charity, and the verification status. No customer data on it.

Receipt line

A ready-to-print sentence with the proof link, returned by the proof endpoint.

QR code

A PNG of the proof link, sized for order confirmations and packing slips.

Where things live

Integrations overview

Connectors, the plugin, and the widget, in one place.

How verification works

The pipeline from sale to on-chain anchor.

AI-builder prompt

On your dashboard's Integrations page after signup.

API keys

Generated on signup, managed in the dashboard.

Ship the honest version.

Create an account, set an impact rule, and record your first sale with one curl. The proof page exists the moment the donation does.

Get an API keyTalk to us