Introduction to Qwist Link
each customers without a backend integration. Share a link, users connect their bank in seconds, and artifacts appear in the Qwist Console.
Qwist Link is the no-code path to nrich's data products. Instead of a server-to-server API integration, you construct a static URL containing your client_id and a user identifier, and forward it to your end user - by email, SMS, or as a button on a webpage.
When the user opens the link, they go through the standard nrich Widget flow: bank selection, authentication, and consent. Once complete, the resulting data - accounts, transactions, and any reports your application is configured for - becomes available in the Qwist Console.
Get credentialsSign in to console.qwist.cloud to create an application and get your
client_id.
What this solves
You want to validate a use case before committing to an integration - Running a pilot with real customer data takes weeks if you need a backend integration first. With Qwist Link, you can reach real users in a day with no code.
Your customer volume is low or ad-hoc - For teams managing a smaller portfolio - lenders, advisors, accountants - Qwist Link can be a permanent workflow. Share a link with each customer, collect data via the Console, and process it manually or export as JSON.
You need ad-hoc data collection - Compliance reviews, one-off affordability checks, re-engagement campaigns: any situation where you want to trigger a bank connection for a specific user without provisioning a backend flow.
Your team is not technical - Operations or compliance teams can generate and distribute Qwist Links directly from a spreadsheet or email client. No engineering involvement needed.
Available artifacts
Every successful Qwist Link flow produces a baseline set of artifacts. Additional reports are generated based on your application configuration.
| Artifact | Availability |
|---|---|
accounts | Always |
transactions | Always |
income-report | Based on application configuration |
risk-report | Based on application configuration |
user-insights | Based on application configuration |
Report configurationReports are configured per application during onboarding. To enable additional reports for your application, contact us.
When to use Qwist Link
Collect real bank data before scoping a full API integration. Confirm your business case with actual customers, not synthetic data.
Go live with a small group of users in production. No frontend or backend integration required on your side.
For advisors, lenders, or compliance teams managing a contained customer set - Qwist Link can be a permanent, no-code workflow.
Trigger a bank connection for a specific user via email or SMS without building a dedicated flow in your product.
For high-volume, real-time, or programmatically driven use cases, use the API-based implementation guides for each product.
Coverage
Qwist Link coverage
Available across all nrich Widget-supported countries
Supported account types vary by country and include: payment accounts, savings accounts, depot accounts, credit cards, loans, and insurances.
