...
The beneficiaries resource is used by an AISP to retrieve the account beneficiaries information for a specific AccountId or to retrieve the beneficiaries' information in bulk for account(s) that the user/customer has authorised to access.
...
In the case an ASPSP manages beneficiaries at a user/customer level (logged in user), instead of account level:
If a user/customer selects multiple accounts for authorisation, then their beneficiaries apply consistently to all selected accounts (i.e., in the bulk endpoint /beneficiaries).
This is the expected behaviour of the beneficiaries' endpoints, in the case an ASPSP manages beneficiaries at a user/customer level:
The bulk endpoint /beneficiaries will return the unique list of beneficiaries against the user/customer. In this case, the AccountId in the OBReadBeneficiary payload would be set to NULL / empty (even if the user/customer only has one account).
The selected account endpoint /accounts/{AccountId}/beneficiaries will return the beneficiaries that may be accessible to the AccountId, based on the user/customer. In this case, the AccountId will be populated in the payload.
...
These objects must not be returned without the ReadBeneficiariesDetail permission:
OBReadBeneficiary/Data/Beneficiary/CreditorAgent
OBReadBeneficiary/Data/Beneficiary/CreditorAccount
If the ReadBeneficiariesDetail is granted by the user/customer:
OBReadBeneficiary/Data/Beneficiary/CreditorAgent may be returned if applicable to the account and ASPSP (0..1)
OBReadBeneficiary/Data/Beneficiary/CreditorAccount must be returned (1..1)
If the ReadPAN permission is granted by the user/customer, the ASPSP may choose to populate the OBReadBeneficiary/Data/Beneficiary/CreditorAccount/Identification with the unmasked PAN (if the PAN is being populated in the response).
...