01
Define the billing event
Your application manages the service, customer and subscription rules.
For SaaS and applications
Your app runs the service.
Lucanto handles the invoices.
Create invoices for your services through the API and work with them in Lucanto. Keep subscriptions, plan changes and payments in the system that already manages them.
For invoicing your own business. Billing on behalf of your platform customers needs a separate setup discussion.
LucantoAPI connection
Your system. Invoices in Lucanto.
Keep your payment system. Connect the data.
- Payment
- Connection
- Invoice
Subscription paymentYour app / payment provider
€29InvoiceFA 2026 / 108
€29ServiceMonthly subscription
The invoice is ready in Lucanto.
Let your app decide what to invoice.
02
Send the invoice data
Your integration calls the API at the right point in the workflow.
03
Work with the document
Access invoices through the API and in Lucanto, alongside your accounting records.
Less admin. More useful tools.
Keep Stripe. Connect your invoicing.
Let Stripe manage subscriptions and payments. A developer can connect payment events to Lucanto through your application, using webhooks and REST API calls.
Decide which system issues the final invoice to avoid two independent invoices for one service. This is a custom integration, not a one-click plug-in.
Stripe
Subscriptions and payments
Your application
Webhook → REST API
Lucanto
Invoicing documents
Other systems can fit too.
The same approach can work with other systems that expose suitable APIs, webhooks or exports. Paddle needs separate consideration: it acts as the Merchant of Record for the customer sale.
Do not automatically create a second customer invoice for a Paddle sale. Agree the document flow and corrections first.
Source
Mapping
Document
API availability and seller responsibilities matter
Build for retries, permissions and volume.
Scope tokens to the company and operations needed. Use Idempotency-Key where supported and record processed source events so retries do not create duplicates.
Check current API limits and supported operations in the documentation. Your app continues to manage subscriptions.
Authorize
Check
Create
Scoped access · event tracking · idempotency
Start with a clear plan
- Choose one concrete billing scenario to connect first.
- Define the source of the final invoice and map customers, items and tax data.
- Handle errors, repeated events and correction documents.
- Estimate document volume and API calls against current limits.
Start small. Add what you need.
Choose a plan around your workload, team and features. Check current allowances and availability on the pricing page.
Your questions, answered
Is the Stripe integration ready to install?
No. A developer or integration partner builds the connection through the API, including data transfer, invoice creation, error handling and corrections.
What if Stripe already issues invoices?
Decide which system is the source of the final document. The goal is not two separate invoices for the same service. Agree numbering and accounting treatment with your accountant.
Is Paddle the same as Stripe Billing?
Not for this workflow. Paddle acts as Merchant of Record for the end-customer sale. Review which documents your business needs instead of automatically issuing another invoice to that customer.
Can I connect something other than Stripe?
Yes, the approach depends on available APIs, webhooks or data exports, not the provider name. Each connection still needs implementation and testing.
Does Lucanto replace subscription management?
No. In this setup your application or payment service continues to manage subscriptions, plan changes and payments. Lucanto provides invoicing and accounting preparation.
Can I offer invoicing to my platform customers?
That is different from billing for your own services. Contact us to discuss company accounts, permissions, your business model and responsibility for documents.