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: iDEAL for the first payment, SEPA Direct Debit after that.

  • Mandates, planning and collection, monthly to yearly, whatever the plan sets
  • Access follows activation, so nobody is locked out while a debit is in transit
  • A first payment whose mandate never registered is repaired on the next run
  • A charged-back debit becomes a new charge the customer can pay again
Payment methods & mandates

Your tenants bill their own customers

A platform where every tenant (a studio, a school, an agency) charges its own end users.

  • Tenants connect their own Mollie account via OAuth, and the money settles there
  • An optional application fee per transaction for you
  • Their customers pay on the tenant's own website profile, and mails can link back to its domain
  • Dual billing: you bill your tenants while they bill their users
Mollie Connect

Your bookkeeper wants real invoices

An immutable invoice for every paid charge, with a PDF your customer can download.

  • Continuous numbering that never resets on 1 January
  • VAT per plan, reverse charge for EU businesses, credit notes on refunds and chargebacks
  • The PDF can ride along on the payment mail, with an optional receipt per collection
  • Mollie payouts can sync back, so a bank-statement reference leads to its payments
Invoicing & VAT

You sell modules, seats or variable amounts

A base subscription plus add-ons the customer switches on and off, prorated per day.

  • Seats: your application keeps the count and puts count × price on a cost line
  • Usage or fees your application works out go on a cost line, or on a charge of their own
  • Modules chosen at sign-up are on the first charge, and your checkout can quote it upfront
  • A changed amount is announced by e-mail, and a standalone charge ten days before it is collected
Cost lines

You sell one-time things, or only that

Workshops, setup fees, hardware, top-ups: single payments live next to subscriptions, or on their own.

  • Nine of the ten payment methods work for one-time payments
  • Optional order lines with VAT per line, an invoice on request, a credit note on refund
  • Your own models, such as an order or a booking, hear about every status change
  • This site runs that way: licenses are sold, invoiced and refunded by LarsaSub
Single payments

You want customers to fix their own failed payments

A direct debit bounces, and the customer settles it from their own dashboard.

  • A pay-now button with a choice of method: iDEAL, Bancontact, card, Apple Pay
  • A first payment that never completed, or a checkout left halfway, gets a retry button
  • An optional reminder series follows up on the days you choose
  • Its last step hands the decision about access to your application
Recurring charges

Your customers do not all speak your language

Plan names, descriptions and content are stored per locale, in as many languages as you configure.

  • Bank statement descriptions, invoices and credit entries follow the customer's language
  • So do all 27 e-mails the customer receives; mails to your own team stay in yours
  • The package's own screens, e-mails and invoice PDFs ship in English and Dutch
  • Set the seller country and zero-rating follows: reverse charge in the EU, 0% outside it
Multilingual plans

Your tenants live in their own databases

Billable owners in per-tenant databases, billing state on a landlord connection.

  • Registrations are scoped per tenant, and the tenant resolves without touching the owner
  • Your tenant context is activated on webhooks, scheduled commands and LarsaSub's own queued jobs
  • One hook switches into each tenant, and back out again before a platform step
Multi-database tenancy

You are moving from another billing system

You already have paying customers, and moving them in must not charge anyone twice.

  • Imported subscriptions keep their start date and billing day
  • Nothing is collected before the date they were paid through
  • Add-ons import with what was already billed, so there is no catch-up charge
  • Your invoice numbering continues where the old system stopped
Migrating subscribers in
Limits

When LarsaSub is not the right fit

A specialized tool should be clear about its edges. These are LarsaSub's, in short:

  • ✗ Your payment provider is not Mollie. Mollie is the only implementation today, and every payment method ships as a Mollie flow.
  • ✗ Your business is registered outside Europe. Mollie onboards sellers in the EEA, the UK and Switzerland. Your customers can be anywhere.
  • ✗ You need built-in usage metering. Your application measures and prices usage, and LarsaSub collects it. Recording and rating usage events is not built in.
  • ✗ Discount codes are central to how you sell. There are no coupon codes: you get a lower plan price, an introduction price, a price for one customer or wallet credit.
  • ✗ You want EU VAT handled end to end. Reverse charge, 0% outside the EU and an opt-in VIES check are built in. Destination-country rates under the One Stop Shop are not.
  • ✗ Your customers pay invoices by bank transfer. Only payments that run through Mollie are booked; there is no mark-as-paid.
  • ✗ You want a merchant of record. You, or your tenant, stay the seller and file your own VAT.
  • ✗ You have one simple plan and no invoice requirements. A generic subscription library is less to install and to learn.

Every limit, with what to do instead: What LarsaSub fits, and what it does not.

the short version
# LarsaSub assumes:
provider: Mollie
market:   EEA/UK/CH seller, buyers worldwide
methods:  10, of which 3 recurring
billing:  monthly to yearly, one-time, or both
pricing:  plan, add-on lines, your own amounts
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.