Offer debt collection right next to the unpaid invoice in your product
When the last reminder doesn't work, your users get a next step without leaving your app. Debitura is the collection infrastructure behind it: a licensed local agency or law firm in the debtor's country, in 180 countries. You choose how much of the experience you build.
Two ways to integrate
Both integrations use the same API key, the same clients and the same cases. The difference is how much of the journey you build and how much Debitura handles for you.
Starter Integration
One API call and a button. Debitura handles everything that comes after.
- You build
POST /collection-requests, a button that opens the returned link, and one webhook- Debitura handles
- Sign-up, approving the connection, agreements, KYC and fixing invoice data
- Your user
- Clicks "Send to collection" and finishes on Debitura's pages, with your logo
Full Integration
Collection built into your own screens, with full control over every step.
- You build
- Client onboarding, pricing previews, case submission and status, across two APIs, plus webhooks
- You handle
- Every onboarding response (201, 202, 409), validation errors and the agreement and KYC links
- Your user
- Stays in your app and leaves only to sign
It's not either/or. Start with Starter. When you need more control, add Full endpoints for the same client, such as pricing previews, status in your own screens or document upload. Nobody is onboarded twice, and an existing case is recognised whichever route created it.
Compare
| Starter Integration | Full Integration | |
|---|---|---|
| Endpoints you call | 2: POST and GET /collection-requests | 8, across the Referral Partner API and the Customer API |
| A new client signs up | On Debitura's hosted pages, opened from the solutionUrl you receive | You call POST /clients and send the user to the returned onboarding URL |
| The client already has a Debitura account | Debitura emails the approval invitation and returns the approval link to you | You handle the 409 responses and deliver the approval URL |
| Invoice data needs correcting | It becomes a draft the client fixes on Debitura | You receive the error response and fix it in your app |
| KYC is required | The case waits; submitting the KYC form releases it | You present the KYC link and resubmit |
| Status in your app | The request status, plus case webhooks | Everything: cases, documents, payments and messages |
| Effort | One endpoint, one button, one webhook | Onboarding, token handling, case submission, error handling and webhooks |
See Who does what for every responsibility, side by side.
Not sure? Answer three questions
The same rules, written out:
| If you… | Use |
|---|---|
| want users to send an invoice with one click and let Debitura handle setup | Starter |
| also want to show the fee before an invoice is sent | Starter, plus POST /cases/preview |
| want case status, documents and partner messages inside your app | Starter, plus Customer API reads with a bearer token |
| want to design your own sign-up and agreement screens | Full |
See it first
The Ledgerline demo shows the whole journey inside a fictional accounting product. Turn on Developer view to see the requests and responses behind each step. To explore case tracking and earnings, sign in to the Partner Dashboard with the code demo.
Business context: see the Referral program overview for what you earn, and What your client sees during onboarding.