Skip to main content

LDS data management (retention, personal data, GDPR)

Maxime avatar
Written by Maxime
Updated over 4 months ago

Personal Data scopes

Personal data can be identified in the following data domains (and underlying LDS tables)

BankAccount domain- contains first name, last name, and address of account holder (PSU)

  • BankAccount

  • PSD2bankAccount

Transaction domain- contains personal details of debtor and creditor (PSU and “shadow party”)

  • Transaction

  • TransactionDetail

Transaction domain- can contain personal details of sender and recipient (PSU and “shadow party”)

  • Payment

User domain- can contain personal details of PSU and user identifiers

  • AspNetUsers

GDPR tickets handling

to be completed

Data deletion/deactivation methods

This section walks through the different methods of od data deletion/deactivation split by data domains. Functional aspects of the operation have been present in blue

Bank

Deletion of given bank account

The deletion of the bankaccount removes account and its transactions from LDS

  • DELETE​/api​/v2​/bank​/{idType}​/{idValue}​/bankAccountDelete bank accounts.

  • DELETE​/api​/v2​/bank​/{bankId}​/bankAccountDelete bank accounts.

Both methods delete account from bankaccount table together with corresponding records in:

  • PSD2BankAccount

  • Transaction

  • PSD2Transaction

  • BankAccountBalance

  • BalanceHistory

This method removes an account and transactions from LDS

Aggregation of new accounts- those

  • POST​/api​/v2​/bank​/{bankId}​/authorizePosts authorization form to further APIs.

  • POST​/api​/v2​/bank​/{idType}​/{idValue}​/authorizePosts authorization form to further APIs.

  • POST​/api​/v2​/bank​/{bankId}​/syncSynchronize user accounts for specified bank

  • POST​/api​/v2​/bank​/{idType}​/{idValue}​/syncSynchronize user accounts for specified swiftCode

Those methods control an AIS flow by adding new bank accounts (BankAccount-Transaction

BankAccount

POST​/api​/v2​/bankaccount​/{accountId}Update a bank account.

POST​/api​/v2​/bankaccount​/{idType}​/{idValue}Update a bank account. <param name="idType">Type of identifier</param><param name="idValue">Value of identifier</param>

PUT​/api​/v2​/bankaccount Update bank accounts.

POST​/api​/v2​/bankaccount​/{accountId}​/deleteDeletes a bank account.

POST​/api​/v2​/bankaccount​/{idType}​/{idValue}​/deleteDeletes a bank account.

Callback

POST​/api​/v2​/callback​/{flow}​/{authType}​/urlPost Redirect to authorization

This method controls an AIS flow by adding new bank accounts (BankAccount-Transaction

Consent cannot be deleted via API. Consent can be only deactivated (not deleted from DB)

The deactivation of the consent can work in 2 modes (depends on DeactivateAccounts flag value):

  • if DeactivateAccounts flag value=TRUE - all consented accounts will be deleted

  • if DeactivateAccounts flag value=FALSE - all consented accounts will be kept in LDS as active

DELETE​/api​/v2​/consent​/{consentId}Delete user consent.

DELETE​/api​/v2​/consentDelete user consents for a given bank.

DELETE​/api​/v2​/consent​/{idType}​/{idValue}Delete user consents for a given bank.

Country

The domain cannot be changed, deleted via API.

Image

DELETE​/api​/v2​/image​/{bankAccountId}- deletes an image assigned to bankaccount

POST​/api​/v2​/image​/{bankAccountId}

Payment

Initated payment record cannot be deleted from LDS

Transaction

The domain cannot be changed, deleted via API.

User

The deletion of the User removes all consents, consented accounts, and transactions from LDS.

127
usuniecie usera kasuje wszystko a info o tym odklada się w raportach
usuniecie zgody nie kasuje nic, oprócz samej zgody (dezaktywuje natomiast podpiete konta do tej zgody flaga isActive = 0) można podać parametr żeby zostały aktywne. Co ważne taka zgoda nie zostaje jużzwrócona z API bo w bazie jest kasowana. W mongo natomiast jest jako isDeleted = true
usuniecie konta usuwa to konto i transakcje podpiete do tego konta122 i 116
usuniecie usera zmienia jego externalID na DELETED_Stara nazwa, a podpiete dane zostają jako nieaktywne
usuniecie zgody nie kasuje nic, oprócz samej zgody (dezaktywuje natomiast podpiete konta do tej zgody flaga isActive = 0), można podać parametr żeby zostały aktywne. Co ważne taka zgoda nie zostaje jużzwrócona z API bo w bazie jest kasowana. W mongo natomiast jest jako isDeleted = true
usuniecie konta usuwa to konto i transakcje podpiete do tego konta (edited)

DELETE​/api​/v2​/user​/{userId}

PUT​/api​/v2​/user​/{userId}Modify User by Api

POST​/api​/v2​/userCreate User by Api

Data retention

By default, data is not removed from LDS except direct DELETE API calls as above.

Did this answer your question?