How it works
Three decisions. Then you sell.
Lernaura is one commercial system. Before you build on it, decide who should be the seller, how you want to build, and what you need to verify.
Who should be the seller?
This decides who carries the legal and tax responsibility for each sale. It is a trade, not a tier.
Merchant of Record
Lernaura is the seller for Merchant of Record transactions and operates tax, payments, invoicing, collection, disputes and payouts. One service; the rate depends on whether your customer pays by card or by invoice.
Direct
Your company stays the seller, on your own entity and VAT number. Lernaura runs contracts, subscriptions, invoicing, collection and revenue data around you. Priced by conversation.
You can move between them later without rebuilding — the commercial record stays in place.
How do you want to build?
The same commercial system underneath, whichever way you connect to it.
No integration
Creator platform
Courses, communities, newsletters, coaching and podcasts in one European platform. Build the offer without writing code.
Your own product
API and webhooks
Products, checkout, subscriptions, usage and invoices over a REST API, with signed webhooks for the events you subscribe to.
With your coding agent
MCP-assisted integration
Point your coding agent at the Lernaura MCP server. It discovers the platform, creates a sandbox and builds the integration with you.
What should you verify first?
Check the evidence before you commit. Each of these is a page, not a promise.
EU sovereignty
Where the data and infrastructure live, and who controls them.
Compliance
Policies, sub-processors and the controls behind them.
Pricing
One Merchant of Record offer with two payment-method rates; Direct by conversation.
Comparisons
Where the alternatives are strongest, and where Lernaura differs.
Developer evidence
The API surface, sandbox and webhooks you would actually integrate.