Mollie Subscription Billing: The SaaS Bill, Not the Pallet Money

Mollie is the payment provider for ReVend's own SaaS subscriptions. That sentence is boring on purpose. It means Mollie is for tenant packages, mandates, subscription invoices and failed-payment handling. It is not the rail for Market deals, Auction settlements, escrow funds or pickup payments. Mixing those would be the kind of finance soup nobody wants to audit.

What exists today

/settings/billing already shows the tenant's package context: active plan, enabled modules, limits, storage usage, billing contact and VAT details. The public pricing page reads from the same package catalog. Platform admins manage plans, modules, features and limits from the package matrix instead of hardcoding tier names into the app.

What Mollie will add

RM-082 connects that package truth to the payment rail: Mollie customers, mandate setup, subscriptions, payment success/failure webhooks, invoice state and dunning signals. The plan engine remains ReVend's source of truth; Mollie confirms whether the subscription money actually arrived.

What Mollie does not touch

Market and Auction deal money flows through the escrow model where escrow is enabled. Pickup finance is handled by the ITAD's own Core invoicing and settlement records. Trade-in customers may see invoices and certificates in their portal, but that does not make Mollie the mover of operational funds. The pallet money and the SaaS bill live in different rooms, and the doors are labelled for a reason.

Why the boundary matters

Subscription billing decides whether a tenant is paying ReVend. Operational finance decides who owes whom for assets, pickups, services, fees, refunds or disputes. Keeping those separate makes audits cleaner, support conversations shorter, and future add-ons possible without accidentally turning a SaaS invoice into a settlement ledger.