A developer-first payments platform. Stripe powers checkout for a large share of the web, and Gwinn itself settles payments through Stripe Connect — your customers pay into your own Stripe account. When Stripe is the better choice: You have engineering resources and want to build a bespoke checkout. Your business model needs Stripe's full API surface — marketplaces, subscriptions, complex payouts. You already run a storefront you're happy with and only need payments. When Gwinn fits better: You want a store and a point-of-sale, not an API to build against. You'd rather photograph your notebook than write a product catalogue by hand. You sell at markets and online and want one inventory across both. Your catalogue and TWINT on one screen — traditionally: One or the other: a POS app that can't take TWINT, or a TWINT app with no catalogue in it; with Gwinn: Both, on one screen — tap the photo, then choose TWINT, card or cash. What a sale costs — traditionally: Their rate, all in — and at a stall, every one of them beats ours on cards; with Gwinn: Your processor's rate, plus 0% from us in person and 1% online on Free — so take TWINT, which is on the same screen. Building the store — traditionally: A developer, weeks in a builder, or no online store at all; with Gwinn: AI drafts, writes and photographs it in an afternoon. Inventory — traditionally: Rigid grids you maintain by hand; with Gwinn: Scan your notebook; the AI keeps it. Pricing — traditionally: A monthly fee, a higher per-sale rate, or a negotiated contract; with Gwinn: Free in person. 1% online, or flat CHF 25. Your money — traditionally: Held, then paid out; with Gwinn: Straight into your own Stripe. Where your data lives — traditionally: Whichever cloud regions they use — check their sub-processor list; with Gwinn: Europe, mostly Germany — servers we rent from Hetzner.
Start your store free · Pricing · llms.txt