You don't need a storefront platform to want to know the moment you make a sale. A lot of creators and solo sellers run entirely on payment or checkout tools — Stripe Checkout, Gumroad, Lemon Squeezy — with no "store" to install a plugin on. Those tools already know about every sale the instant it happens; the only missing piece is getting that event somewhere you'll actually see it.

The webhook-recipe approach

Every platform in this list already has a webhook feature — a setting where you paste in a URL and the platform sends a JSON payload to it whenever something happens. GotASale gives you that URL from your dashboard: add a source, copy the webhook address it generates, and paste it into the payment tool's own settings. No app to install on their side, no code to write on yours. Most of these also support a signing secret, which GotASale uses to verify that a request claiming to be from, say, Stripe actually came from Stripe and not someone guessing your webhook URL.

It's worth being clear about what this isn't: GotASale doesn't use Stripe Connect, doesn't need OAuth access to your Gumroad account, and doesn't sit between your customer and your payment processor. It only listens for the webhook event you configure yourself, in your own account, on the platform's own infrastructure. If you ever want to stop, removing the webhook URL from that platform's settings is enough — there's nothing else to disconnect.

What's supported today

Eight payment and SaaS platforms have a purpose-built setup flow: Stripe (checkout.session.completed for one-time payments, invoice.paid for renewals, charge.refunded for refunds), Gumroad (its account-wide or per-product Ping URL), Lemon Squeezy (order_created and, optionally, subscription_payment_success), Paddle (transaction.completed, which covers both one-off and renewal payments on Paddle Billing), Ko-fi (donations, shop orders, and subscriptions, if your Ko-fi plan includes webhooks), ThriveCart, SamCart, and Stan Store, each with their own order- and refund-style events. Anything else that can send a webhook — your own backend, or a no-code tool like Zapier, Make, or n8n — can use GotASale's generic Custom Webhook endpoint, or a field-mapping option for JSON shapes you don't control.

The generic option expects a specific shape: an order total, a currency, and a customer name or email are the only required fields, and everything else — line items, address, a specific event type — is optional. If you're coming from Zapier, Make, or n8n instead, where you don't always control the exact JSON shape being sent, Custom mapping lets you point GotASale at the right fields using dot-notation paths — for example buyer.full_name or items.0.title — rather than reshaping the payload yourself before it arrives.

Why this matters if you sell in more than one place

A lot of solo sellers don't run on just one of these — a course might sell through both Gumroad and a Stripe Checkout link, or a membership might run through Stan Store while merch sells through Shopify. Each of those tools has its own dashboard and its own idea of what a "sale" looks like. Routing them all through GotASale means one notification format and one place to see all of it, regardless of which processor actually took the payment.

Before connecting a setup like this, checking sales across three tools usually means three logins and three slightly different definitions of "today's revenue." After, a single Telegram chat or Slack channel shows every sale as it happens, without changing anything about how the underlying tools actually process the payment.

Connecting one of these takes a few minutes: add the source in your dashboard, paste the webhook URL — and secret, where the platform provides one — into that platform's settings, and send a test event. Each setup guide linked above walks through the exact screen names for that platform.

Most of these platforms also flag test-mode activity — a test-mode Stripe charge, a Gumroad test ping, a ThriveCart or Stan Store test purchase — and GotASale tags the resulting notification as a test too, so a practice run through checkout doesn't get mistaken for a real sale while you're confirming everything is wired up correctly. And because this is the same underlying webhook system that powers the platform-specific setup guides, a store already running WooCommerce or Shopify can add a Stripe or Gumroad source alongside it without any conflict — sales from either one land in the same channels.

Takeaway

  • Stripe, Gumroad, Lemon Squeezy, Paddle, Ko-fi, ThriveCart, SamCart, Stan Store — plus a generic webhook for anything else.
  • Same three steps every time: add the source, paste the URL, verify with a test event.
  • No plugin, no app install, no server code required.

Start with the platform you already use

Connect Stripe, Gumroad, or any other supported source and see your first notification within minutes.