Documentation · Integrations

Four ways to connect

How you can connect to the Xaver platform, who takes on which task, and where the effort lies.

Experience the platform live →Book a meeting

Most integrations follow one of four routes. They differ less in the technology than in who does what: who carries the brand, who holds the customer relationship, who is the product provider, and which systems are touched.

We settle which route fits in the first technical conversation. It decides the effort more than the interface itself does. How much more Xaver takes on (individual building blocks, individual products or the platform end to end) is set out in the partnership model. What the interface covers is described in the API documentation.

Last updated: 26 October 2026

Four routes

Four ways, one platform

Under your brand, run by Xaver

Xaver runs the advice journeys and portals as a separate application under your brand. Your existing systems stay untouched at first.

Suited to: Market entry, pilot journeys and campaigns where speed matters more than depth of system integration.
What you bring: Your brand, your customer access and your campaigns, sign-off on content, and a subdomain or entry point.
What Xaver brings: Advice and completion journeys, customer and adviser portals, investment backend and operations.
Where the effort lies: The lowest effort of the four routes: no changes to your existing systems. Data comes back to you as an export or through an interface.

Inside your website or app

The journeys run embedded in your website, portal or app, under your brand, with the signed-in session handed over.

Suited to: Partners with their own digital channel and an existing login who want pensions to be part of their own offering.
What you bring: Front-end embedding, login and session handover, design specifications and your approval process.
What Xaver brings: The embedded journeys under your brand, the completion journey and servicing in the background.
Where the effort lies: Moderate effort. Front-end embedding and session handover need a technical conversation first.

Through a bank or savings bank

Distribution runs through your bank or savings bank, while product and processing sit with the regulated product provider. Xaver is the layer in between for advice, completion and operations.

Suited to: Branch and digital distribution with a connected product provider, where advice, product and processing sit with different institutions.
What you bring: Distribution and the customer relationship, the adviser workplace and the product provider's requirements.
What Xaver brings: Advice and completion journey, allowance and operating processes, and portals and reporting for both sides.
Where the effort lies: The most coordination: several institutions, several approvals, one shared process.

Who carries which regulatory obligation is set out in the contract for each project.

Your existing customers and contracts

Your existing customer and contract data is taken over, reconciled and kept in sync. This is what you need to activate existing customers and offer switching services at scale.

Suited to: Projects where your existing customer base is what matters: activating existing customers, a Riester switching service.
What you bring: Data access and data model, subject-matter contacts, and clarification of the data protection basis.
What Xaver brings: Initial migration, reconciliation and quality checks, ongoing synchronisation and event feedback.
Where the effort lies: The effort lies in data quality, not in the interface, which is why the work always starts with a data assessment.

Keep reading

A slowly turning, desaturated globe with relief coastlines, a few marked nodes and fine connecting lines.

Walk through your use case with us.

We show you the modules that matter for your case
With Max Bachem, founder & CEO
No obligation, no preparation needed

Book a meeting Experience the platform live →

Would you rather ask something first?