Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expiry of accRefNumber should be standardised #29

Open
aypandey opened this issue Aug 6, 2024 · 0 comments
Open

Expiry of accRefNumber should be standardised #29

aypandey opened this issue Aug 6, 2024 · 0 comments

Comments

@aypandey
Copy link

aypandey commented Aug 6, 2024

Problem Statement

On POST /Account/Discovery API call, FIP returns accRefNumber which is to be used in request payload of /Account/Link API post which linkRefNumber is generated. Once account is linked, user can approve consents with already linked accounts. Since there is no expiry set on accRefNumber, AAs are free to call /Account/Link API even after a long time since discovery had occurred due to which FIPs are obliged to keep the discovery responses forever.

Since discovery API is the second largest API invocation in numbers after FI/request, this creates additional cost of storage and large data sets for discovery metadata.

Solution
  1. Once the account is linked, accRefNumber can be expired.
  2. If Account is de-linked, user is obliged to rediscover the account which will end up creating the new accRefNumber.
  3. A new accRefNumber should have a expiry of at least 15-30 days in which /Account/link can be called. If /Account/link is received post 30 days, the request can be discarded.
  4. An expiry on accRefNumber is beneficial for FIPs and they are no longer obliged to keep the responses forever which can save infra cost for them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant