Skip to content
Kreditz Vista
  • There are no suggestions because the search field is empty.

Data Collection Methods

How Consent & Data Collection Works with Kreditz (Vista, iframe & API)

When integrating Kreditz, there are different ways to collect user consent and retrieve financial data. The right option depends on your operational setup, desired user experience, and level of technical involvement.

Below is a simplified overview of the three available approaches.

1. Vista (Manual Request via Kreditz Platform)

Best for: Operational teams who want a managed, no-integration approach.

How it works

  1. You create a manual request directly in the Vista platform.

  2. The end user receives an email or SMS notification.

  3. The notification directs the user to a landing page with bank list.

  4. The user connects their bank and provides consent to complete the process.

UX & Customization

  • Landing pages and email/SMS communication can be customized to align with your brand. 

What this means for you

  • No technical integration required.

  • Ideal for smaller volumes and getting started with speed.

2. iframe Integration (Embedded Flow - Easy & Seamless)

Best for: Maintaining your branded experience while keeping integration simple. The user stays inside your application the entire time.

How It Works

  1. Create a Session via API

    Your backend calls our API to initiate an iframe session.

  2. Embed the Kreditz Flow
    You display the Kreditz Connect page inside your application using an embedded frame (iframe).
    From the user’s perspective, everything happens within your platform.

  3. User Connects Their Bank

    The user securely logs in with their bank and completes the required steps.

  4. Completion - Two Modes

    Once the process is complete, there are two ways your system can be notified:
    Option A: Embedded Notification    The embedded page sends a secure message back to your application when the process is finished. No page reload or redirect is required, the experience remains seamless.
    Option B: Redirect    The user is redirected to a URL that you define once the process is complete.

  5. Backend Confirmation (Webhook)
    Regardless of the option chosen above, your system will receive a secure server-to-server notification confirming completion.
    After receiving this notification, your backend can retrieve the full results from Kreditz using the provided case ID.

UX & Customization

  • Embedded directly in your product.

  • Keeps the user inside your environment.

  • Visual branding can align with your product.

  • Core consent and bank connection flow handled securely by Kreditz.

This is why we describe the iframe as easy to integrate - you avoid building PSD2 connectivity and consent handling from scratch, while still maintaining a seamless user journey.

What this means for you

  • Low frontend effort.

  • Seamless UX.

  • Balanced flexibility and simplicity.

3. Full API Integration (Maximum Flexibility)

Best for: Companies that want full control over the frontend and user journey.

How it works

  1. You build your own frontend flow.

  2. You collect user consent within your own interface.

  3. You use Kreditz APIs to initiate sessions and retrieve financial data.

UX & Customization

  • Full control over UX, branding, and interaction design.

  • Fully customizable consent collection.

  • Complete flexibility in how the user journey is structured.

What this means for you

  • Maximum customization.

  • Higher development effort.

  • Suitable for advanced or highly tailored implementations.

  • Full technical API documentation is available during technical onboarding.