01
API and webhooks
Everything the console does, your system can do. Create applications, score, match, upload documents, query status.
Webhooks signed with HMAC report every status change back.
Available
Integrations
Four ways to come in.
Everyone works differently. One wants a ready-made flow, the next wants our engine behind their own screen. So the platform is open on four sides, and every channel carries your brand instead of ours.
02
The portal as customer front
The complete application flow and customer portal, ready to use. All that is left is to apply your branding.
Available, white label rolling out
03
JS components
A piece of script on your own site, the component: a simulation, a solvability check or the full application, embedded in your existing pages.
In your colours, with your typeface, without the visitor leaving your site.
Rolling out
04
app.adefin.be/my
The portal where your team follows the files, with the rights their role carries. That screen takes on the dealer's or financing partner's colours too.
Rolling out
Start with a single key.
You get a key per source, so it stays visible which channel brought which application in. Partner users sign in with their own token and then see only their own files.
The offers that come out stay limited to the financing partners that partner works with. Their captive is included, the rest of the market is not.
KeyPartner login
# an application from your own system
curl -X POST https://app.adefin.be/api/v1/applications \
-H 'X-API-Key: …' \
-d '{ "applicant": { "vat": "BE0473773635" } }'
# or as a partner user
POST /api/v1/auth/login → Bearer token
GET /api/v1/me → { partner, leasecos }
Your colours, not ours
White label is not a coat of paint.
Colours and a logo are the visible part. Underneath sits the rest: emails that leave from your address, your own domain, the language your customer speaks and copy you can change.
What does not change is the file. However the application comes in, it is the same application with the same checks and the same audit trail.
- Colours, logo, typeface and domain
- Emails in your brand
- Dutch, French and English
- One file, wherever the buyer comes in
A key per channel, and what it does.
Screenshots from the product. Names, numbers and amounts have been replaced.
Per key: the channel, the partner, the webhook and when it was last used.
The questions that go with this.
- How do we connect it to our systems?
Through the API, with a key per source, and webhooks that report every status change back, signed. Anyone who prefers a screen uses the portal. You replace nothing.
- Can we use our own score model?
Yes. Factors on or off, each with its own weight and its own translation from value to strength, and knock-outs you set yourself. Your model sits next to the standard one, so you can compare what a different weighting would do to your portfolio.
- Do I have to install anything first?
No. You can start in the console or in the portal without anything changing at your end. If you want to connect, you get a key for a test environment before anything goes live.
Which side suits you?
Tell us where your customers arrive today, and we will tell you which channel pays off fastest.