➤ Introduction

This service allows you to retrieve the connected PSU's identity who has given you their consent to do so (who is not necessarely the customer having the account).

➤ Prerequisites

To proceed with this request, it is necessary to fulfill the eligibility prerequisites and to have retrieved the OAUTH2 access token (see in the section "Overview"  > "Get your access token").

To get the PSU's identity, you need :

• The authorization to transmit this identity information to the TPP must have been transmitted to us via the setting to true of the "psuIdentity" attribute of the PUT /consents method and must not have since been revoked (i.e. not cancel and replace via PUT /consents with a "psuIdentity" attribute set to false);

• The URI to access this method is given through the "_links": {"endUserIdentity": {"href": ...}} item as a result to the GET /accounts request.
  

➤ Request

Method GET /end-user-identity

 See also specification STET V1.4.2.17 / Part II / section 4.6.4 / page 43 

Mandatory or optional settings of the body required to call this service

Mandatory settings : PSU-IP-ADDRESS => to inform if the PSU is connected.

➤ Returned result 

This call allows you to get the identity of the end customer

A self link will also be available to return to the page obtained after execution of the request.

Your access to this method are limited to a maximum of 4 batch accesses per calendar day, for a customer. However, when it is the connected customer who directly interrogates his current accounts, the number of accesses is not limited.

➤ Example 

You can find an example of this request in section "Test our API" and then "Use our sandbox".

 See also specification STET V1.4.2.17 / Part III / Section 6.3 / page 8

➤ Acceptance tests

These test cases are intended to allow you to perform a minimum of tests to get started with this API and access it from your application.