Open jh-a opened 6 years ago
This picks up from #3
This requirement assumes that the client application will have complete consents (i.e. covering all available permissions as defined at https://openbanking.atlassian.net/wiki/spaces/DZ/pages/127009546/Account+and+Transaction+API+Specification+-+v2.0.0#AccountandTransactionAPISpecification-v2.0.0-Permissions
The client application should call all of the resources defined at https://openbanking.atlassian.net/wiki/spaces/DZ/pages/127009546/Account+and+Transaction+API+Specification+-+v2.0.0#AccountandTransactionAPISpecification-v2.0.0-Endpoints as they are available per bank brand.
These calls should be logically split by
Brand AccountType (PCA / BCA) Resource
and response times recorded.
These calls should also feed information to the availability monitoring solution
This picks up from #3
This requirement assumes that the client application will have complete consents (i.e. covering all available permissions as defined at https://openbanking.atlassian.net/wiki/spaces/DZ/pages/127009546/Account+and+Transaction+API+Specification+-+v2.0.0#AccountandTransactionAPISpecification-v2.0.0-Permissions
The client application should call all of the resources defined at https://openbanking.atlassian.net/wiki/spaces/DZ/pages/127009546/Account+and+Transaction+API+Specification+-+v2.0.0#AccountandTransactionAPISpecification-v2.0.0-Endpoints as they are available per bank brand.
These calls should be logically split by
Brand AccountType (PCA / BCA) Resource
and response times recorded.
These calls should also feed information to the availability monitoring solution