|
Access Method Type |
PIN saved? |
SCA flow exists? |
Auto-Sync enabled? |
Reason |
|---|---|---|---|---|
|
psd2 API |
YES |
YES (new register or with invalid consent) |
YES
|
For psd2 API accesses, due to the concept of consents and oAuth tokens, regardless of the PIN is saved or not, these accounts are added to auto-sync schedules. |
|
psd2 API |
NO |
NO (with valid consent) |
||
|
FINTS or SCRAPING |
YES |
NO |
YES |
Non-API access is added to auto-sync schedule, when the PIN is stored and no SCA is required during the sync flow, which means without user interaction can be synced automatically. |
|
FINTS or SCRAPING |
NO |
YES |
NO |
Since account connection requires SCA, it might be similarly for each sync attempt, therefore these accounts are not added to auto-sync schedules to avoid sending unattended SCA notifications to end users. |
|
FINTS or SCRAPING |
YES |
YES |
NO |
|
|
FINTS or SCRAPING |
NO |
NO |
NO |
Even SCA is not required, connectivity requires PIN while accessing FINTS and SCRAPING providers, therefore once it’s not stored, these accounts are not added to auto-sync schedules to avoid invalid login attempts during auto-sync attempts. |
When is an account added to auto-sync schedule?
Comments
0 comments
Please sign in to leave a comment.