// billing infrastructure for builders

Billing.
That easy.

Drop in a script tag. Start charging. No signup forms, no webhook plumbing, no three-week Stripe integration. Four lines to revenue.

index.html

<!-- grab the SDK -->
<script src="https://cdn.stackpays.com/sdk.js"></script>
<script>
  const ms = StackPays('your-account-id')
  // that's it. charge money.
  ms.charge(12.34)
</script>

How It Works

Zero to revenue in sixty seconds.

Claim your ID

Go to stackpays.com. Pick an account ID. No forms, no KYC, no credit card. You're a supplier now.

Drop the script tag

One <script> from our CDN. Works in any HTML page, React app, Notion embed, anywhere.

Call `charge()`

Buyer sees a payment modal. They pay exactly what you charge. Clean, simple, branded to you.

Cash out

Hit $100, complete KYC, withdraw. Fee comes at cashout — your buyers never see a surcharge.

// Cryptographically signed receipt
{
  "receipt_id": "rx_8f3k2m9...",
  "supplier":   "your-account-id",
  "amount":     12.34,
  "item":       "premium-access",
  "ts":         1709847362,
  "sig":        "ed25519:9c3f..."
}

// Verify anywhere. No webhook needed.
const valid = StackPays.verify(receipt)

The Receipt Primitive

The receipt is the API.

Every payment produces a cryptographically signed receipt. A self-contained proof of payment your frontend, your backend, or any third-party service can verify with a single function call.

No webhooks. No polling. No server required. The buyer's browser carries the proof.

Client-side content gating — no backend at all

Server-side verification — stateless signature check

Third-party fulfillment — any service can consume receipts

Comparison

The gap in the market.

	Stripe	Gumroad	StackPays
Time to first charge	Days to weeks	~30 minutes	< 60 seconds
KYC required to start	Yes	Yes	No
Backend required	Yes	No	No
Your UI, your brand	Yes (with work)	No	Yes
Buyer sees fees	No	No	No
Portable proof of payment	Webhook only	No	Signed receipt
Lines of code	100+	Embed/hosted	4

Ecosystem

Receipts create an ecosystem.

Any service can verify a StackPays receipt. No partnership required — just check the signature. An open primitive for payment-gated experiences.

⚡

Content Gating

WordPress plugins, static site generators, or single-page apps that unlock content on receipt verification. No accounts, no paywalls — just proof of payment.

🔑

License Servers

Services that exchange StackPays receipts for software license keys, activation tokens, or API credentials. Receipt in, key out.

🤖

Bot Integrations

Discord bots that grant roles. Telegram bots that unlock groups. Slack apps that provision access. All verifying the same receipt primitive.

📦

Digital Delivery

File hosting services that serve downloads, courses, or assets upon receipt presentation. No integration with StackPays required.

📊

Analytics

Revenue dashboards and business intelligence tools that ingest receipt streams. Real-time sales tracking without proprietary APIs.

🔄

Your Idea Here

Receipts are a portable, open primitive. If your service can verify an Ed25519 signature, it can join the ecosystem. No permission needed.

Billing.That easy.