Test: createDomesticPaymentsConsents_withNonExistentDebtorAccount_v3_1_10 was disabled when moving to the RCS Consent Store.
The IG/IDM solution had a custom backoffice filter to do some validation here, this has not been implemented in the RS with the new consent store.
This logic provides fail fast behaviour, if the debtorAccount in the payment request is not known to the ASPSP then it is rejected immediately. It could still be the case that the PSU is not the owner of the accound.
Without this logic, a consent can be created with an invalid debtorAccount, the failure will occur at a later step when the PSU authorisation is done.
The reason that this logic wasn't ported over to the RS is because we were short on time, and it was assessed to be a nice to have feature.
Test: createDomesticPaymentsConsents_withNonExistentDebtorAccount_v3_1_10 was disabled when moving to the RCS Consent Store.
The IG/IDM solution had a custom backoffice filter to do some validation here, this has not been implemented in the RS with the new consent store.
This logic provides fail fast behaviour, if the debtorAccount in the payment request is not known to the ASPSP then it is rejected immediately. It could still be the case that the PSU is not the owner of the accound.
Without this logic, a consent can be created with an invalid debtorAccount, the failure will occur at a later step when the PSU authorisation is done.
The reason that this logic wasn't ported over to the RS is because we were short on time, and it was assessed to be a nice to have feature.