
The user initiates the onboarding by submitting a registration request via the frontend

Basic user or company details are captured.

The backend triggers KYC verification through integrated services or internal checks.

User identity or company data is validated based on predefined KYC rules.

If KYC is Passed

Proceed to Authentication.

Terminate the flow and return an error (user cannot proceed further).

The user is authenticated using credentials or oAuth-based methods.

Secure authentication ensures that the identity matches the registered record.

Once authenticated, the user gains access to a sandbox environment or real Open Banking services (depending on the stage).

API access is typically enabled at this point for next steps.

The Registration process ends here successfully, with the user now onboarded.

The onboarded user or application makes a request to retrieve account data via the frontend.

The system verifies whether the user has already approved the necessary consent for account access.

If KYC is Passed

Proceed to next step

Redirect user to Approve Consent screen.

Once approved, loop back to account request handling.

Account broker microservice securely retrieves approved user account data from the bank.

This ensures secure abstraction between the client and core open banking services.

The system fetches the user's account ID(s) from the account broker response.

These IDs are then used to retrieve or display further banking details.

The flow ends successfully with account data now accessible to the user or application.