How to set up recurring, auto-renewing payments

Recurring payments sound like a plumbing detail, and for an organisation that bills once a year they more or less are - you ask, you chase the stragglers, you move on until next March. But the moment your membership runs monthly, the maths changes completely, because now you're not running one renewal season a year, you're running twelve, and if you're collecting each of those by hand you'll spend a genuinely daft amount of your life sending "just a reminder your dues are due this week" messages to people who like you and fully intend to pay. That's the situation recurring payments are built to fix, and this piece is about setting them up in a way that actually helps rather than quietly annoying everyone.

Let me carry one example through so this stays grounded. Say you help run Rumah Rintis - a founders' and co-working community in Bandung, 220-odd members, a monthly membership somewhere around Rp 150,000 - 250,000 that gets people a hot desk a few days a week, the Thursday demo nights where someone pitches a half-built MVP to a friendly room, and the monthly mentor office hours. It's the sort of place people love while they're deep in a project and drift from when they get busy, so the membership money comes in monthly and, right now, it comes in one nagging WhatsApp message at a time. Twelve times a year, across 220 people, that's a lot of nagging - and every message you have to send is a small chance for someone to think "ugh, later" and never come back to it.

What auto-renewing payment actually is

Strip the jargon and it's simple: the member gives permission once, and their payment method is then charged automatically each period - each month, in Rumah Rintis's case - until they decide to stop. That's the whole idea. Instead of you asking every month and the member deciding every month, the default flips: the membership continues unless the member actively cancels it. It sounds like a small change and it isn't, because it moves the effort from "remember to pay" (which people forget) to "remember to leave" (which far fewer people get around to doing). I wrote a whole guide on renewals that leans on the same point, so I won't labour it here, but it's worth understanding why it lifts retention rather than just taking it on faith.

Here's the rough shape of it, and I'd hold these numbers loosely because they vary enormously by the kind of group. Suppose that in any given month a manageable 8% of Rumah Rintis members just don't get round to paying the reminder - not because they've decided to leave, but because it landed on a busy day and slipped. That doesn't sound like much. But run it out across a year and a small monthly slip compounds into something ugly: keep 92% each month and, crudely, you're down near 35 - 40% of where you started twelve months on (before any rejoins). Real life is kinder than that arithmetic because people do come back, but the direction is honest - monthly manual collection bleeds members through pure friction, and auto-renewal is the most direct patch for it. The member who'd have quietly lapsed stays, simply because staying became the thing that required no action.

The honest way to do it (this part matters more than the mechanics)

Now, auto-renewal has a bad name in some quarters, and it has earned it, because plenty of businesses use it as a trap - bury the opt-in, make the charge a surprise, and hide the cancel button three menus deep so the money keeps coming from people who forgot they ever signed up. Do not do that. It works for exactly as long as nobody notices, and the day they notice you've turned a member into someone who tells other people your community is a bit dodgy. For a founders' community especially, where the whole thing runs on word of mouth and goodwill, that's a spectacularly bad trade.

The honest version comes down to three habits, and none of them costs you anything:

• Be upfront that it's recurring. When someone switches auto-renew on, they should know in plain words what they're agreeing to - the amount, the frequency, and that it'll keep going until they stop it. No fine print, no dark pattern. "Rp 200,000 a month, charged on the 1st, cancel anytime" is the entire disclosure and it's enough.
• Remind them before each charge, not after. A short note a few days ahead - "heads up, your Rumah Rintis membership renews on Monday" - means nobody ever gets an unexplained line on their statement. It feels almost counterintuitive (you're reminding people of a charge they might have forgotten, which sounds like handing them a chance to cancel), but the goodwill is worth far more than the handful who bail, and the ones who bail were unhappy anyway.
• Make cancelling genuinely easy. One clear link, no phone call, no "please email us to request cancellation". If leaving is easy, staying is a real choice, and a membership full of people who are actively choosing to stay is worth more than one padded out with people who can't work out how to get off it.

What you actually need to set it up

Three things, and that's about it. First, a payment method that supports recurring charges - something that can be charged again next month without the member re-entering their details each time. Second, the member's consent - a clear, deliberate opt-in, not a pre-ticked box they didn't notice. Third, a reminder before each charge, as above. Get those three and you've got honest recurring billing; miss the consent or the reminder and you've got the trap version, which will cost you more than it makes.

The first of those - a payment method that can actually be charged again automatically - is where things get interesting in Indonesia, and it's worth being clear-headed about it rather than assuming it works the way the overseas SaaS blog posts say it does.

The Indonesian reality: cards versus QRIS and e-wallets

True "set and forget" auto-charging was built around the credit card. The member's card is stored (safely, as a token, by the payment gateway) and charged each month without them lifting a finger. That works fine here too - for the members who have a suitable card. The snag is that credit card penetration in Indonesia is low compared with the countries where auto-renewal became normal, and a lot of Indonesian debit cards aren't set up for repeat online charges either. So if you build your whole recurring system on stored cards, you've quietly designed it for the minority of your members and left everyone else stuck on manual payment.

The way most of your members actually pay is QRIS, an e-wallet like GoPay or OVO or Dana, or a bank transfer, and here's the honest complication: QRIS is fundamentally a scan-and-approve-each-time method. It's brilliant - fast, everywhere, no card needed - but it was not designed to silently pull money out of someone's wallet next month while they're asleep. Some e-wallets do offer a subscription or auto-debit link, and where a member is willing to set that up it's close to true auto-renewal, but coverage is patchy and not everyone will bother linking it. I'd not pretend otherwise. The detail of which methods to offer and how they behave is a topic in itself, and I've covered the practical side of taking payment online in a separate guide on collecting dues, so I won't repeat all of it here.

What this means in practice is that for a lot of Indonesian communities, the pragmatic default isn't pure auto-charge at all - it's a reminder-plus-one-tap flow. True automatic charging for the members whose card or linked wallet supports it, and for everyone else a scheduled reminder that lands with a saved payment link already filled in, so paying is one tap and a QRIS scan rather than a fresh chase every month. Is that technically "set and forget" for those members? No - they still tap once. But it's a world away from you personally messaging 220 people, it keeps the friction down to about fifteen seconds, and it fits how people here actually pay rather than how a payment textbook wishes they did. For Rumah Rintis, that mixed approach will almost certainly collect more than a card-only system that half the members can't use, so don't let the pursuit of a perfectly silent charge talk you out of the flow that actually works.

How to introduce it to members who are already with you

Rolling this out to brand-new joiners is easy - you just offer auto-renew as an option when they sign up, at the moment they're already getting their payment details out, and a good share will take it because it saves them the monthly faff. Existing members need more care, and there's one rule that matters above all the others: don't silently flip people onto automatic charging. Even if your terms technically let you, waking up one morning to an auto-debit you didn't knowingly agree to is exactly the "trap" feeling that does the damage, and doing it to your founding members - the people who'll forgive a lot but not that - is how you turn advocates into complainers.

So make it opt-in, and sell it honestly as the convenience it is. A single friendly message does the job: "we've added auto-renew, so if you're tired of the monthly reminder you can switch it on once and forget about it - Rp 200,000 a month, cancel anytime, here's the link". Frame it as you saving them a chore, because that's true, and let people come to it in their own time. Some will switch straight away, plenty will ignore it and carry on paying manually, and that's completely fine - the manual folks still get their reminder and their one-tap link, so nobody's worse off. Over a few months the proportion on auto-renew climbs on its own, without you having strong-armed a single person, and a member who chose auto-renew is a far steadier member than one who got signed up to it and hasn't noticed yet.

Start rough here too. You don't need every payment method wired up and every edge case handled before you offer this to anyone. Turn it on for the members whose cards support it, add the reminder-plus-link flow for the rest, watch how many take it up, and improve one piece at a time….

This is a fair chunk of what Anggota is built to handle quietly in the background - recurring monthly billing, the heads-up before each charge, a one-tap payment page with QRIS, e-wallets and bank transfer for the members who can't be auto-charged, and an easy cancel so none of it ever feels like a trap. If that sounds like it'd save you a stack of monthly WhatsApp messages, you're welcome to try it for free and see how it fits your community. And if you'd rather take the ideas above and run them through whatever you already use, that's genuinely fine - the principles hold either way, and a payment setup your members trust is worth building however you get there.