Prerequisites

API Access

The nrich API uses HTTP Basic Authentication with two credentials:

• Client ID (username) and
• Client Secret (password)

Each set of credentials is associated with specific access scopes that define your permissions on the nrich platform. Contact us to obtain your dedicated credentials.

Postman Collections

We recommend downloading our Postman Collections to simplify your integration through our pre-configured API requests, allowing you to test endpoints instantly without any manual setup.

Getting Started

Before implementation, review our Widget Integration Guide for best practices and setup instructions.

Problem statement

Dependency

Customers must use our Account Information Service as basis for all our data driven products to access all API features, which is limiting their choice of data providers for the Connectivity space.

Example:

If a customer is searching for an Account Information Provider, that has a wide coverage of connectivity e.g. Yapily, but also provides great data enrichment services such as Qwist does, customers have to decide which provider to use: Yapily has no data enrichment, Qwist has maybe less connectivity coverage. So the customer has to take a lose-lose decision.

Lack of Flexibility

The mandatory use of our Account Information Service restricts customers from using their existing systems, hindering customization and broader adoption.

Example:

Some potential customers might not even need an Account Information Service as they have their own access to account and transaction data, e.g. a bank that has a core banking system. If such customer does not want to build extensive enrichment capabilities, they might be left with max. a handful of providers that can do the enrichment as standalone service.

Integration Complexity

The existing system's requirement to use our Account Information Services adds layers of complexity for customers managing multiple service relationships, complicating integration efforts.

Example:

If a customer is already working with an Account Information Provider e.g. Tink, but want to use Qwists more and more growing data enrichment capabilities, the customer is facing expensive integration efforts to switch provider integrations, especially the customer facing account connection flows. So customers might not use Qwist due to the high cost of switching providers (“lock-in effect”).

Value Proposition

Enhanced Flexibility

Introducing an upload feature allows customers to use any TPP as data source for financial transaction data, but not missing out Qwists comprehensive data enrichment or risk-analysing capabilities.

Standalone Functionality

The upload feature can be used independently from our existing produce suite, broadening appeal and usability.

Customer Autonomy

Customers gain control over data integration, promoting innovation and tailored financial solutions.

Market Expansion

Decoupling our Account Information Service from our data capabilities opens up our services to a wider audience, including users of other existing products.