⚡ VBWD

Stop rebuilding billing. Start shipping.

Every subscription business ends up writing the same thing: plans, carts, coupons, taxes, invoices, retries, refunds, webhooks — and an admin to run it, plus a finance team that just wants it to reconcile. VBWD ships that whole money path, wired and tested, so you launch in days, not quarters. Walk the journey end to end.

It starts with a plan

Your customer lands on a storefront you control — plans, prices, trials and add-ons, all driven from the admin. No hard-coded pricing pages: change a tier and it is live.

A checkout that meets the buyer where they are

One checkout, every rail. Cards via Stripe, PayPal, regional providers — or the customer's own token balance, with no card at all. Coupons validate server-side, tax is computed per region, and the flow is idempotent and retry-safe.

A clean invoice, the instant they pay

Payment captured, invoice issued — automatically. Customers see their active subscriptions, token balance and a full invoice history they can view or download as PDF. No support ticket to "resend the receipt."

Everything, in one admin

On your side, every invoice across every customer sits in one place — paid, pending, refunded — filterable, searchable, exportable.

And pricing is never a deploy. Edit a plan, its taxes, trial length or billing cycle from the admin and changes go live without shipping code.

Everything around the payment, already wired up

That whole journey is one platform. You don't need yet another payment integration — you need identity, plans, invoices, taxes, retries, refunds, webhooks and an admin UI already wired around it. VBWD ships that surface, then gets out of your way.

What the engine handles for you

• Plan catalogue with categories, add-ons, discounts, trials, intro pricing.
• Monthly / annual / custom billing cycles + prorated upgrades and downgrades.
• Dunning, retries and payment-method-failure handling.
• Token-grant refresh on each renewal; per-plan daily limits.
• Cancellation flow with grace period; line-item invoicing per subscription, bundle and add-on.
• Multi-currency pricing, regional tax, country-availability matrix.

Two halves that meet at the cart

Pay with tokens — not just cards

Token Balance is a first-class payment method at checkout. Customers top up a wallet (or earn tokens from referrals and plan grants), then spend that balance on subscriptions, packages and one-off purchases — no card required. The checkout lists every enabled rail side by side, so a buyer picks Token Balance, Stripe, PayPal, invoice or a regional provider in one click. Token spend is metered against the wallet ledger and reconciled into the very same invoices as any other payment, so accounting stays in one place.

Payment rails — implemented (3)

Payment rails — planned (20)

Every rail is a plugin

Each provider implements the same PaymentProviderPlugin interface — create_payment_intent, capture_payment, refund_payment, a webhook handler — plus a matching fe-user checkout component. Adding a tenth provider is one plugin, not a core change.