# One-Time Connect Flow
source: https://developer.mastercard.com/open-finance-europe/documentation/unlicensed/insights/one-time-connect-flow/index.md

## Overview {#overview}

For Insights services, the One-Time Connect Flow can be used. When end users sign up for Mastercard Open Finance and connect to your service, they will first need to give consent and connect their banks. With our one-time flow, end users have the option of performing a one-time connect and share flow, which will then delete all their data within a 24-hour period. This is useful if you only need to receive data from the user once, and you want to avoid the Hub account creation steps from the onboarding flow.

The One-Time Connect Flow is embedded within the Insights API and you do not need to call a separate endpoint to enable this. Pass the redirectURL (i.e. the link to the site or application where you would like the PSU to return after completing the flow) in the initial Submit Insights Request. In the response, you will receive the connectURL (i.e. the link which will take the PSU to our one-time flow and allow them to begin the user journey) which you can make available to the PSU on your site.

## Steps {#steps}

### Step 1 {#step-1}

In the first step, the end user is notified that your service uses Mastercard Open Finance Service. Here, the end user gives us consent to retrieve and share bank data with your service, and that the bank data will be deleted within 24 hours. This is also where the end user accepts our terms of use and privacy policy. The consent wording in the grey box can vary according to the combination of Insights products used in line with PSD2 consent management.

The image below is an example of a consent screen for the Account Owner Verification standalone user journey.
![](https://static.developer.mastercard.com/content/open-finance-europe/uploads/insights/insights-one-time-step1a.png)

### Step 2 {#step-2}

In the next step, the end user has progressed to the bank selection screen. Here, the end user will choose the bank provider they wish to use.

If you would like to select the default country which is displayed to the end user, you can use the preselectedCountry field in the Submit Insights Requests (coming soon).
![](https://static.developer.mastercard.com/content/open-finance-europe/uploads/insights/insights-one-time-step2a.png)

### Step 3 {#step-3}

Now the end user needs to log in to their bank account using one of the available log-in methods.
![](https://static.developer.mastercard.com/content/open-finance-europe/uploads/insights/insights-one-time-step3a.png)

### Step 4 {#step-4}

The end user will be presented with a list of possible bank accounts that will be shared with your service through our service. If the end user has selected one account whilst active in their mobile banking application, then the selected account will be confirmed in this screen.

When the end user clicks on the **Authorize** button, they will be confirming the account selected.
![](https://static.developer.mastercard.com/content/open-finance-europe/uploads/insights/insights-one-time-step4a.png)

### Step 5 {#step-5}

In the last step, we'll show the end user a success screen. When the end user clicks on the **Finish** button, they will be sent back to your service using the redirectURL you have provided. This is also where end users can claim their Hub account, if they wish to do so.
![](https://static.developer.mastercard.com/content/open-finance-europe/uploads/insights/insights-one-time-step5a.png)

## Next steps {#next-steps}

* Refer to the [Quick Start guide](https://developer.mastercard.com/open-finance-europe/documentation/unlicensed/insights/quickstart/index.md) for the API integration steps.