Printers Lounge · Community Operations Lead · October 2025–Present

← Back to Bhagya Rathnasekara’s portfolio

Printers Lounge is a private research community on Telegram. Access is bought once rather than subscribed to, which makes the moment of purchase the only gate there is.

I assembled that gate: the public site on Lovable, the Stripe checkout and payment flow behind it, and the access workflow that connects a confirmed payment to a single-use Telegram invitation. I supported and helped execute the October 2025 launch, and I have run day-to-day community operations since.

What follows is how that system works, what it deliberately leaves to a person, and where it stops.

The operating problem

Reusable invitation links can be forwarded outside a paid Telegram community. The operating flow reduces that risk by verifying payment before access, issuing a single-use invitation, and continuing access review and moderation after entry.

The problem is ordinary and it is the reason the rest of this page exists. A Telegram invite link is a URL. Anyone holding it can pass it on, and nothing about the link itself knows whether the person redeeming it paid. Any paid community on Telegram that hands out a standing invite has, in effect, published its front door.

Building the front door

The community needed somewhere to explain itself and take money before anyone reached Telegram.

I built that page on Lovable. It is a site builder, and for a single page carrying an explanation and a checkout it was the right trade: what mattered was not how the page was authored but that the copy, the price and the payment path could be changed the same afternoon we learned something. It is not a hand-built application and I would not describe it as one.

I configured the Stripe side myself — the product, the price, the checkout and the payment flow the access workflow later reads from. That configuration is the part that quietly decides whether a purchase becomes a member or becomes a support ticket, so it got more care than the page did.

Controlled access path

1. The site. A prospective member reads what the community is and what it is not, and buys from that page. Nobody reaches Telegram from here.
2. Stripe checkout. Payment is taken through the checkout I configured. Until this completes, nothing downstream happens at all.
3. Payment verification. The payment is confirmed before anything is issued. This ordering is the whole design: verification is not a check performed on a member who is already inside, it is the condition of getting in.
4. Single-use invitation. The verified buyer receives an invitation that stops working once it is redeemed. Forwarding it achieves nothing, because the second person to use it finds it already spent.