Get user info

The /v3/data-connections/{connection_id}/user-info endpoint returns the account holder's name as held by their financial provider. This enables you to verify that the name of the person connecting their account matches the expected account holder name on file at the bank.

This endpoint must be called within the 5-minute SCA (Strong Customer Authentication) window after the user completes authentication. Outside this window, you will receive a 403 error. This means that you cannot create a connection with the info scope which also has the data_access type of recurring.

You can use this for:

• Account ownership verification: Confirm that the person connecting their account is the account holder before processing sensitive transactions or granting access to services.
• KYC (Know Your Customer) processes: Enhance customer onboarding flows by retrieving verified identity information directly from the user's financial provider.
• Seller verification: Verify marketplace sellers or service providers by matching their registered business or personal name with their bank account details.

Authentication

This endpoint requires OAuth 2.0 authentication with Data API scopes. You need:

• A Bearer access token with the data scope
• The connection_id that you want to investigate, as a path parameter, with the info scope.

You may also want to provide the IP address of the end user as a header. This confirms that your user is present when the request is made, enabling you to bypass rate limiting.

Make a GET request with the connection_id as a path parameter.

Response

If successful, you receive an object in the response that contains the user's name.

{
  "name": "Jane Smith"
}

This is the account holder's name as their bank stores it.

This field is optional and may not be returned if the provider does not supply this data or if it is unavailable.

If you do not call this endpoint within 5 minutes of the user authenticating with their bank, you will receive a 403 access_denied error.