Payments

Sell subscriptions and one-off products through your own Stripe account. Connect it with one restricted key and Gemmein makes your Payment Links, manages subscriptions and writes receipts, so you build none of it.

Payments are processed by Stripe on your own account. Gemmein hosts the webhook and receives only the webhook events. Any provider that signs its webhooks, GoCardless, Paddle or Lemon Squeezy among them, drives access the same way through a relay.

In this section

Limits

Gemmein does not do the following, and none of it is planned. If your business depends on one of them, use a different backend. Credit packs are products; see Credits.

• No usage quotas or record-count limits. "Ten projects on the free plan" is your app's logic. Gemmein tells you who holds what; it does not count your records.
• No seats or per-organization billing. Each account is one person, one identity, with no organizations, memberships, invitations or ownership transfers.
• No physical goods. No shipping, addresses, delivery rates, inventory, stock reservation, variants, fulfilment, tracking or returns. Gemmein is for software and digital access.
• No multi-item carts. One product per checkout, by design. A "cart" is N checkouts, or one bundled product you price as a bundle. Don't build a cart UI that promises otherwise.
• No marketplace shapes: multiple sellers, payouts, commissions or inter-party disputes.
• No usage-based invoicing, and no tax calculation, invoicing or accounting export. Stripe handles these.
• No DRM. Gemmein controls whether a person may fetch a file. Nothing stops a legitimately downloaded file being reshared afterwards, and no backend can change that. For an external asset (a delivery link you host elsewhere), the host is responsible for everything after the link is issued.
• Chargebacks aren't handled. A dispute does not revoke access, because Gemmein doesn't receive dispute events. Handle those in Stripe and revoke by hand if you need to.