“Loyalty points are a per-store gimmick.” They don’t have to be. The interesting version of loyalty is a single credit that behaves like money across a whole network of independent merchants — earn it buying coffee, spend it on a haircut, top up with a card if you run short. The surprising part, per a VBWD analysis, is that the hardest thing about a shared currency — one balance that clears cleanly across many businesses — is the part you switch on rather than build.

Most loyalty programs are per-store because portable credit is genuinely hard: you need one ledger, one settlement model, and clean accounting when a customer earns at merchant A and redeems at merchant B. VBWD — a self-hosted, source-available full-stack SaaS SDK — already has that ledger in the invoice line item and already isolates merchants as tenants. The work rides on token_payment, multi-tenant, shop, marketplace, and discount.

The token is money, not points

The token_payment plugin is a token/credit economy with metered billing. Run it at network scale rather than single-store scale, and the balance becomes a private, closed-loop currency: one wallet a customer earns into, tops up through the payment core, and redeems at checkout anywhere in the network. Because every spend is an invoice line item, a redemption is a real, reconciled transaction — not a coupon counter drifting out of sync. As the original puts it:

A gift card is closed-loop but single-merchant. Bank money is open-loop but heavily regulated. A network credit sits between: it moves like money inside your fence and nowhere outside it.

Independent merchants, one currency

A network is only interesting if the members are genuinely independent. VBWD’s core is multi-tenant, so each merchant gets its own storefront, catalogue, orders, stock, and branding; shop gives every tenant real commerce, and marketplace presents them as listings under one roof. The combination people don’t expect is fully separate merchants sharing one currency between them, all living in the same core — so the credit earned at one tenant is, by construction, spendable and accountable at another.

Clearing, solved by the ledger

Ask anyone who has run a coalition program what breaks and they say settlement. VBWD’s answer is that there is nothing extra to reconcile against:

A credit earned is an obligation on the network; a credit redeemed is that obligation discharged at whichever tenant accepted it.

Because it is all one ledger of line items, the operator can see at any moment who is owed what, and when real payouts are due the withdraw capability moves settled balances out. The event-driven core with native signed webhooks means every earn and burn can trigger a fraud check, a tier upgrade, or a notification without polling.

Levers on top

A currency is a foundation; a program needs levers. The discount plugin runs “earn double this weekend” or “20% off when you pay in credits,” and because discounts and token spends are both line items on the same invoice, a promotion mixing cash, credit, and a coupon reconciles correctly. Add the referral capability and members widen circulation for you.

The boundary

Here is the honest limit. VBWD gives you a clean, portable credit and the tenants to spend it across. It does not give you a business model for that credit — the earn rate, the burn value, the float, and the regulatory treatment of stored value in your jurisdiction are yours. It keeps the ledger honest; it does not sign off on your economics or your compliance, so bring an accountant and possibly a lawyer. You also still recruit merchants, set the rules, and run the deployment.

What makes this buildable now is that none of the pieces are bespoke — the platform has already carried a tarot app, a dice-market game, a pharmacy shop, and dataset publishing. Read the full analysis on VBWD, or clone the public SDK to start.

Written for Red Robot with AI assistance and human editing. Adapted from an original analysis published on VBWD.