LarsaSub is launching soon. Purchases and account registration open shortly.
Use cases

Where LarsaSub fits

LarsaSub is built for one job: billing European customers from a Laravel application, through Mollie. These are the situations it was designed for, and the ones it was not.

A good fit

Your customers pay by direct debit

A Dutch or Belgian SaaS where customers expect iDEAL for the first payment and SEPA Direct Debit after that. LarsaSub manages the mandates, plans and executes the monthly charges, and treats settlement as what it is: asynchronous. Access follows activation, not payment confirmation, so a customer is never locked out while a direct debit is in transit.

Your tenants bill their own customers

A platform where every tenant (a studio, a school, an agency) charges their own end users. With Mollie Connect each tenant onboards their own Mollie account via OAuth, money settles directly to the tenant, and the platform takes an application fee per transaction. Dual billing adds the other direction: you bill your tenants while they bill their users.

Your bookkeeper wants real invoices

Sequential invoice numbers per year, VAT with per-plan rates and reverse charge for EU businesses, credit notes when a payment is refunded or charged back, and PDF downloads for your customers. Invoices are immutable snapshots, generated automatically for every paid charge.

Your tenants live in their own databases

Multi-database tenancy where the billable owners sit in per-tenant databases and billing state belongs on a landlord connection. LarsaSub scopes registrations per tenant, resolves the tenant without touching the owner, and activates your tenant context on webhooks, scheduled commands and queue workers, where no request context exists.

You sell modules, seats or variable amounts

A base subscription plus add-ons the customer switches on and off, prorated per calendar day, with prepaid days refunded as credit. The same cost lines take amounts your application computes: measure usage or processing costs yourself, set the line before the monthly run, and the charge, mandate collection and invoice follow automatically.

You sell one-time things too

Workshops, credits, hardware, setup fees. Single payments live next to subscriptions, carry optional order lines with per-line VAT, and notify your own models (an order, a booking) on every status change, so fulfillment logic stays in your code and payment state stays in LarsaSub. A credit wallet with expiry covers refunds and goodwill.

You only need to take payments

No subscriptions at all: a checkout, a booking fee, a top-up, a donation. Nine of the ten payment methods work for one-time payments, you get the invoice, the credit note on a refund, the customer dashboard and the admin screens, and none of the subscription machinery has to be switched on. This site is the proof: LarsaSub licenses are sold, invoiced and refunded by LarsaSub.

You want customers to fix their own failed payments

A direct debit bounces, and the customer sees it in their own dashboard with a pay-now button and a choice of method: iDEAL, Bancontact, card, Apple Pay. The same for a first payment that never completed and for a checkout the customer abandoned halfway. Chasing failed collections by hand is what this replaces.

Your customers do not all speak your language

Plan names, descriptions and content are stored per locale, and the frozen text follows the customer's own language: the description on their bank statement, the lines on their invoice, the entries in their credit ledger and all 35 notification e-mails. Set the seller country and the VAT rules follow, including reverse charge and 0% outside the EU.

Limits

When LarsaSub is not the right fit

A specialized tool should be clear about its edges. Skip LarsaSub if any of these describe you:

  • ✗ Your payment provider is not Mollie. The provider layer is abstracted behind a contract, but Mollie is the only implementation today, and every payment method ships as a Mollie flow. If you are committed to another provider, a package built around that provider will serve you better.
  • ✗ Your business is registered outside Europe. Mollie onboards businesses in the EEA, the UK and Switzerland; without a Mollie account there is nothing to bill with. Your customers can be anywhere: recurring card and PayPal mandates work worldwide, and non-EU invoices get 0% VAT. But if the seller itself is outside Europe, a billing package built around a US-centric payment provider is the better starting point.
  • ✗ You need built-in usage metering right now. LarsaSub does not yet count your API calls or seat-hours for you. Variable monthly amounts themselves are supported: your application does the measuring and sets the amount on a cost line, LarsaSub does the billing. Built-in metering, rating and aggregation are in development: record usage events and LarsaSub turns them into a priced line on the monthly invoice.
  • ✗ You want to bill a year up front. A plan can run for any term you like, from one month to five years, but the collection itself is monthly. Paying a full year in one go, with the discount that usually comes with it, is in development and lands before 1.0.
  • ✗ Discount codes are central to how you sell. There is no coupon or promo-code system: no redeemable codes, no campaign rules, no referral credits out of the box. You can price a plan lower, run an introduction price for the first period, or credit an amount to a customer's wallet — but if your growth plan runs on codes at checkout, you would be building that part yourself.
  • ✗ You need full EU VAT compliance handled for you. Per-plan rates, reverse charge for EU businesses and 0% outside the EU are built in and land correctly on every invoice. VIES validation of VAT numbers and destination-country rates under the One Stop Shop are not. Selling B2C into other EU countries, you may keep charging your own rate below the €10,000 annual threshold — sellers established in a single EU country, electronic services and distance sales counted together. Above it the destination rate applies, and that part is yours to add.
  • ✗ You want a merchant of record. LarsaSub bills from a Mollie account you or your tenant owns: whoever makes the sale stays the merchant and files their own VAT. On Mollie Connect the money settles into the tenant's own account and the invoice carries the tenant's own seller details — the platform is never the seller, it only takes an application fee. If you want a reseller to take that liability over, that is a service, not a package.
  • ✗ You have one simple plan and no invoice requirements. If a single card-paid plan with no bookkeeping obligations covers your case, a generic subscription library is less to install and less to learn.
the short version
# LarsaSub assumes:
provider: Mollie
market:   EEA/UK/CH seller, buyers worldwide
methods:  10, of which 3 recurring
billing:  monthly, one-time, or both
pricing:  plan + variable add-on lines
invoices: yours, sequential, VAT-aware

# If that matches, most of your
# billing code is already written.

Not sure about your case?

Describe your setup in an e-mail and you will get a straight answer, also when that answer is that LarsaSub is not the right fit.

See pricing info@larsasub.eu