Introduction to Verify and Pay

Verify and Pay

Verify and Pay provides you with a set of rules to define restrictions that are validated during the payment process once a user selects an account. By analyzing the selected account's transactions, the system generates a report that provides the necessary data to validate these rules.

You can automatically block payments if the account does not meet the criteria defined by your rules. This enables a payment flow focused on control and pre-validation, giving you deeper insights into the user's financial health while reducing the risk of unreliable transactions.

📘
Get credentials
Sign in to console.qwist.cloud to generate sandbox credentials instantly.

Prerequisites

Complete these steps before starting the implementation guide.

Step 1

Get your API credentials

Sign in to the nrich Console to generate sandbox credentials instantly. No approval needed. The sandbox includes a demo bank for end-to-end testing. Production credentials can be requested directly from the Console once you are ready to go live.

Open Console →

Step 2

Review the Widget Integration Guide

Most nrich products use a Widget UI for bank selection and authentication. Understanding how to embed it before you start will save you time.

Widget Integration Guide →

How it works

You create a Widget link - call POST /verify-and-pay with your configuration.
The user authenticates - the nrich Widget guides them through bank selection and SCA.
You can verify the rules - in case the verification failed, you can check in the failed-rules query parameter which one failed in the process.
You can retrieve the risk report - no matter if the validation passed or not, you will be able to retrieve the risk report through the GET /artifacts/{artifact-id}?artifact_type=risk-report endpoint. The artifact-id is retrieved in the redirect under the flow-id key.

Name-matching algorithm

nrich's algorithm handles common name variations automatically:

Different orderings: "Müller, Maria" vs "Maria Müller" → HIGH
Umlauts and special characters: "Hans Muller" vs "Hans Müller" → HIGH
Exact match: "Maria Müller" vs "Maria Müller" → VERY_HIGH
No overlap: "Maria Müller" vs "Thomas Schmidt" → LOW

📘
Recommended threshold
For most use cases, treat VERY_HIGH and HIGH as a successful match. MEDIUM and LOW should trigger manual review or rejection.