RepoAccess

RepoAccess turns a payment into GitHub access, and a refund back into no access, without a platform in the middle taking a cut. It runs as a single Cloudflare Worker on your own account. Your buyer pays with the payment provider you already use, types their GitHub username, and is invited to the GitHub team that carries your private repository. If that payment is later refunded or charged back, the access goes with it, whether or not you were watching. HOW IT WORKS 1. The buyer pays at your checkout, with your provider, at your price. 2. The provider's webhook reaches your Worker, which verifies the signature and runs a durable Workflow. 3. The buyer lands in the GitHub team holding your repo. If your checkout collected the username, they are added directly; otherwise they open a one-time claim link and enter it there. 4. On a refund or chargeback, access is revoked and any pending invitation is cancelled. There is no "Login with GitHub" and nothing phones home. GitHub's own invitation is the identity check: it goes to that account's email, and only its owner can accept it. WHAT A REFUND ACTUALLY REMOVES A refund revokes the product that was refunded, not the buyer. Only the teams on that grant are touched, plus any invitation still pending. Organization membership is then reconciled against live GitHub state: if the buyer is still in a team from another purchase, they keep it and everything it entitles them to, and they leave the organization only when they are in no product team at all. So a buyer who owns product A, buys B and refunds B loses B and keeps A. The check runs against GitHub itself, never against the Worker's own records. FREE AND PAID Core is AGPL and free: a Stripe adapter, the full grant and revoke engine, the claim page, and a guided setup wizard. It runs on Cloudflare's free Workers tier. Pro is $129 once, with twelve months of updates and support, and adds adapters for Paddle, Lemon Squeezy, Gumroad, Razorpay and Telegram Stars. The Telegram Stars adapter is a full bot: a storefront your buyers browse, a support relay, and payment and refund handling inside the chat. WHO IT IS FOR People who already sell code and hand out access by hand: authors of boilerplates, starter kits and templates, paid courses with a private repository, and small tools. It is also the only practical route for sellers in countries the usual payment processors do not serve, since the provider is yours to choose and nothing is tied to one of them. WHO IT IS NOT FOR It is not a payment processor and does not replace one; it sits behind the processor you already have. It is not a hosted service either: you deploy it, you own the account, and the setup needs a GitHub organization, a team per product and an access token, which the wizard walks you through. A free GitHub organization is enough, and free organizations have free seats.