Skip to content
Payments & ledger

One payment path for dues, tickets and gifts

Three modules take money, and they share one implementation. That is not a tidiness preference — building payment three times is how you end up with three ledgers that disagree and a treasurer reconciling by hand.

Offline payment, treated as a first-class path

Most member organisations still take a large share of their income by bank transfer or cheque, and most software treats that as an afterthought. Metrolo gives it the full flow: rich-text instructions you write, a generated reference number, a note field, an account selector when you bank in more than one place, an optional cheque image upload, and a pending-approval screen that is honest about not being settled yet.

An approval queue with a trail

Payments arrive in a queue. Someone with the finance grant matches them against the bank, approves or rejects, and the effect propagates — the ticket becomes valid, the membership starts, the campaign total moves. Every decision is recorded with who made it.

Gross and net, on every view

Every administrative money screen shows what was charged and what actually arrived after service charges. The ledger stores both, so a report and a bank statement can be put side by side without arithmetic.

Card payments, honestly described

Stripe and PayPal adapters are on the roadmap and are not built today. The admin screens for credentials exist; the adapters, webhooks and reconciliation behind them do not yet. We would rather write that here than have you find it in month two.

FAQ

Payments & ledger — questions

If yours is not here, ask on a call. We answer specifics.

Does Metrolo take a percentage?

No. There is no revenue share on dues, tickets or donations. Your payment provider's fees are between you and them.

Can we use our existing bank accounts?

Yes. You configure the accounts and the instructions members see, including different accounts for different purposes.

What if a member pays the wrong amount?

The approval queue is where a human decides. You can reject with a reason, and the member sees the state change.

See payments & ledger against your own setup

Bring the awkward case — the exception your constitution requires, the thing your current system cannot do. That is the useful half of a demo.