AA

Sahamati certification Test Scenarios for Account Aggregator

Scenario ID	Feature Under Test	Description	Expected Result
1001	POST /Consent API with valid details	Verify on sending valid request to POST /Consent API success response is required.	Http Status code should be 200.
1002	POST /Consent API with invalid schematic value for each field	Verify on making valid request to POST /Consent API with schematic error for one field each subcase error response is received.	Http status code should be 400 Error code should be InvalidRequest.
1003	POST /Consent API with incorrect timestamp format	Verify on making valid request to POST /Consent API with incorrect timestamp format error response is received.	Http status code should be 400 Error code should be InvalidRequest.
1004	POST /Consent API with incorrect ver	Verify on making valid request to POST /Consent API with incorrect ver error response is received.	Http status code should be 404 Error code should be NoSuchVersion.
1005	POST /Consent API with incorrect timestamp value	Verify on making valid request to POST /Consent API with +/- 16 min variation in timestamp error response is received.	Http status code should be 400 Error code should be InvalidRequest.
1006	POST /Consent API with incorrect txnid format	Verify on making valid request to POST /Consent API with incorrect txnid format error response is received.	Http status code should be 400 Error code should be InvalidRequest.
1007	POST /Consent API with invalid consent span	Verify on making valid request to POST /Consent API with invalid consent span error response is received.	Http status code should be 400 Error code should be InvalidRequest.
1008	POST /Consent API with invalid dataconsumer Object	Verify on making valid request to POST /Consent API with invalid dataConsumer object error response is received.	Http status code should be 400 Error code should be InvalidRequest.
1009	POST /Consent API with invalid Customer Identifiers object	Verify on making valid request to POST /Consent API with invalid Customer Identifier error response is received.	Http status code should be 400 Error code should be InvalidRequest.
1010	POST /Consent API with invalid purpose Object	Verify on making valid request to POST /Consent API with invalid purpose object error response is received.	Http status code should be 400 Error code should be InvalidConsentPurpose.
1011	POST /Consent API with invalid FIDataRange	Verify on making valid request to POST /Consent API with invalid FIDataRange error response is received.	Http status code should be 400 Error code should be InvalidRequest.
1012	POST /Consent API with invalid DataLife	Verify on making valid request to POST /Consent API with invalid DataLife error response is received.	Http status code should be 400 Error code should be InvalidRequest.
1013	POST /Consent API with invalid Frequency	Verify on making valid request to POST /Consent API with invalid Frequency error response is received.	Http status code should be 400 Error code should be InvalidRequest.
1014	POST /Consent API with invalid DataFilter	Verify on making valid request to POST /Consent API with invalid DataFilter error response is received.	Http status code should be 400 Error code should be InvalidRequest.
1015	POST /Consent/handle API	Verify on making valid request to POST /Consent/handle API after consent is approved, success response is received.	Http status code should be 200 ConsentStatus.status should be APPROVED.
1016	POST /Consent/handle API with invalid consentHandle	Verify on making valid request to POST /Consent/handle API with invalid handle error response is received.	sub-case 1: Removing last char from valid consentHandle Http status code should be 400 Error code should be InvalidConsentHandle sub-case 2: Add a char at the end from valid consentHandle Http status code should be 400 Error code should be InvalidConsentHandle sub-case 3: Generating random consent handle Http status code should be 400 Error code should be InvalidConsentHandle.
1017	POST /Consent/handle API after user rejectes consent from AA	Verify that on making consent handle request after user rejects consent, response with consent status REJECTED is received.	Http status code should be 200 ConsentStatus.status should be REJECTED.
1018	POST /Consent/handle API for expired consent before approving or rejecting by user	Verify that on making consent handle request for consent that is expired before approval or rejection, response with consent status EXPIRED is received.	Http status code should be 200 ConsentStatus.status should be EXPIRED.
1019	POST /Consent/handle API for consent expired after approval	Verify that on making consent handle request for consent that is expired after approvl, response with consent status APPROVED is received.	Http status code should be 200 ConsentStatus.status should be APPROVED.
1020	POST /Consent/handle API for paused consent	Verify that on making consent handle request for consent that is paused, response with consent status APPROVED is received.	Http status code should be 200 ConsentStatus.status should be APPROVED.
1021	POST /Consent/handle API for Revoked consent	Verify that on making consent handle request for consent that is Revoked, response with consent status APPROVED is received.	Http status code should be 200 ConsentStatus.status should be APPROVED.
1022	POST /Consent/handle API after delinking account from the approved consent	Verify that on making consent handle request for consent that is approved and later account is delinked by the user, response with consent status APPROVED is received.	Http status code should be 200 ConsentStatus.status should be APPROVED.
1023	POST /Consent/handle API for PENDING consent after user deregister from AA	Verify that on making consent handle request for a pending consent and user deregistered from AA, error response is recevied.	Http status code should be 400 Error code should be InvalidConsentHandle.
1024	POST /Consent/handle API for Approved consent after user deregister from AA	Verify that on making consent handle request for a Approved consent and user deregistered from AA, error response is recevied.	Http status code should be 400 Error code should be InvalidConsentHandle.
1025	POST /Consent/handle API with an alternate FIU	Verify that on making consent handle request as an alternate FIU for valid handle of regular FIU , error response is recevied.	Http status code should be 400 Error code should be InvalidConsentHandle.
1026	POST /Consent/fetch API with valid details	Verify that on making a POST /Consent/fetch request with valid details, success response is received.	Http status code should be 200.
1027	POST /Consent/fetch API with invalid consentId	Verify that on making a valid POST /Consent/fetch request with invalid consentId, error response is received.	sub-case 1: Empty consentId Http status code should be 400 and error code should be InvalidRequest sub-case 2: Removing last char from valid consentId Http status code should be 400 Error code should be InvalidConsentId sub-case 3:Adding last char to valid consentId Http status code should be 400 Error code should be InvalidConsentId sub-case 4:Random consentId Http status code should be 400 Error code should be InvalidConsentId.
1028	POST /Consent/fetch API with consentId of alternate AA	Verify that on making a valid POST /Consent/fetch request as an alternate FIU for a valid consent Id of regular FIU, error response is received.	Http status code should be 400 Error code should be InvalidConsentId.
1029	POST /Consent/fetch API for expired consent	Verify that on making a valid POST /Consent/fetch API request for expired consent, Success response with EXPIRED status is received.	Http status code should be 200 Consent Status should be EXPIRED.
1030	POST /Consent/fetch API for Paused consent	Verify that on making a valid POST /Consent/fetch API request for Paused consent, Success response with PAUSED status is received.	Http status code should be 200 Consent Status should be PAUSED.
1031	POST /Consent/fetch API for revoked consent	Verify that on making a valid POST /Consent/fetch API request for revoked consent, Success response with REVOKED status is received.	Http status code should be 200 Consent Status should be REVOKED.
1032	POST /Consent/fetch API for consent of which account is delinked	Verify that on making a valid POST /Consent/fetch API request for consent after delinking the account selected in consent, Success response with REVOKED status is received.	Http status code should be 200 Consent Status should be REVOKED.
1033	POST /Consent/fetch API for consent of which user is deregister	Verify that on making a valid POST /Consent/fetch API request for consent after de registering the user from AA, error response is received.	Http status code should be 400 Consent Status should be InvalidConsentUd
1034	POST /Consent API of FIP	Verify that on user accepting consent, AA makes valid POST /Consent request to FIP.	Validate the response received on FIP.
1035	POST /Consent API of FIP	Verify that on user accepting consent with multiple FIP, AA makes valid POST /Consent request to all the FIP.	Validate the response on the request received on alternate FIP and regular FIP.
1036	POST /Consent/Notification API of FIP	Verify that on user changing the status of consent, AA send POST /Consent/Notification request to All FIP involved in Consent.	Validate the response received on FIP.
1037	POST /Consent/Notification API of FIU	Verify that on user changing the status of consent, AA send POST /Consent/Notification request to FIU.	Validate the response received on FIU.
1038	POST /Account/Discover and POST /Account/link API of FIP	Verify that on user linking a new account in AA app, discover, link and token link APIs of FIP is invoked correctly.	Validate the response received on FIP.
1039	POST /Accounts/delink api of FIP	Verify that on user delinking an account in AA app, delink API of FIP is invoked correctly.	Validate the response received on FIP.
1040	POST /Accounts/delink api of FIP	Verify that on user deregistering from AA, delink API of FIP for all linked accounts is invoked.	Validate the response received on FIP.
1041	POST /Consent API with invalid JWS signature	Verify on making valid request to POST /Consent API with invalid JWS signature, error response is received.	Http status code should be 400 Error code should be InvalidRequest/SignatureDoesNotMatch.
1042	POST /Consent/handle API with invalid JWS signature	Verify on making valid request to POST /Consent/handle API with invalid JWS signature, error response is received.	Http status code should be 400 Error code should be InvalidRequest/SignatureDoesNotMatch.
1043	POST /Consent/fetch API with invalid JWS signature	Verify on making valid request to POST /Consent/fetch API with invalid JWS signature, error response is received.	Http status code should be 400 Error code should be InvalidRequest/SignatureDoesNotMatch.
1044	POST /Consent API with invalid Client API key	Verify on making valid request to POST /Consent API with invalid Client API key, error response is received.	Http status code should be 401.
1045	POST /Consent API with Client API	Verify on making valid POST /Consent API request with Client API key of alternate FIU, error response is received.	Http status code should be 400 Error code should be InvalidRequest/SignatureDoesNotMatch.
1046	POST /Consent/handle API with invalid Client API key	Verify on making valid request to POST /Consent/handle API with invalid Client API key, error response is received.	Http status code should be 401.
1047	POST /Consent/handle API with Client API key	Verify on making valid request to POST /Consent/handle API with Client API key of alternate FIU, error response is received.	Http status code should be 400 Error code should be InvalidRequest/SignatureDoesNotMatch.
1048	POST /Consent/fetch API with invalid Client API key	Verify on making valid request to POST /Consent/fetch API with invalid Client API key, error response is received.	Http status code should be 401.
1049	POST /Consent/fetch API with Client API key of alternate FIU, error response is received.	Verify on making valid request to POST /Consent/fetch API with invalid Client API key, error response is received.	Http status code should be 400 Error code should be InvalidRequest/SignatureDoesNotMatch.
1050	POST /Consent/handle API with invalid schematic value for each field	Verify on making valid request to POST /Consent/handle API API with schematic error for one field each subcase error response is received.	Http status code should be 400 Error code should be InvalidRequest.
1051	POST /Consent/fetch API with invalid schematic value for each field	Verify on making valid request to POST /Consent/fetch API with schematic error for one field each subcase error response is received.	Http status code should be 400 Error code should be InvalidRequest.
2001	POST /FI/request API with valid details	Verify that on making a valid request to POST /FI/Request API, success response is received.	Http status code should be 200.
2002	POST /FI/request API with invalid schematic value for each field	Verify on making valid request to POST /FI/Request API with schematic error for one field each subcase error response is received.	Http status code should be 400 Error code should be InvalidRequest.
2003	POST /FI/request API with invalid timestamp format	Verify on making valid request to POST /FI/Request API with invalid timestamp format, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
2004	POST /FI/request API with invalid ver	Verify on making valid request to POST /FI/Request API with invalid ver, error response is received.	Http status code should be 404 Error code should be NoSuchVersion.
2005	POST /FI/request API with incorrect timestamp value	Verify on making valid request to POST /FI/Request API with +/-16 variation in timestamp value, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
2006	POST /FI/request API with incorrect txnid	Verify on making valid request to POST /FI/Request API with invalid txnid, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
2007	POST /FI/request API with invalid FIDataRangeObject	Verify on making valid request to POST /FI/Request API with invalid FIDataRange object, error response is received.	Http status code should be 400 Error code should be InvalidDateRange.
2008	POST /FI/request API with invalid consentId	Verify on making valid request to POST /FI/Request API with invalid consentId, error response is received.	Http status code should be 400 Error code should be InvalidConsentId.
2009	POST /FI/request API with invalid consent digitalSignature	Verify on making valid request to POST /FI/Request API with invalid consent digitalSignature, error response is received.	Http status code should be 400 Error code should be signatureDoesNotMatch.
2010	POST /FI/request API as alternate FIU with valid details of regular FIU	Verify on making valid request to POST /FI/Request API as alternate FIU with valid selected consent details of regular FIU, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
2011	POST /FI/request API with invalid keyMaterials	Verify on making valid request to POST /FI/Request API with invalid keymaterials object, error response is received.	Subcase 1 & Subcase 3 : Http status code should be 400 and Error code should be InvalidKey, Subcase 2 : HTTP status code should be 400 andError code should be InvalidRequest.
2012	POST /FI/request API for Paused consent	Verify on making valid request to POST /FI/Request API for Paused consent, error response is received.	Http status code should be 400 Error code should be InvalidConsentStatus.
2013	POST /FI/request API for Revoked consent	Verify on making valid request to POST /FI/Request API for Revoked consent, error response is received.	Http status code should be 400 Error code should be InvalidConsentStatus.
2014	POST /FI/request API for Expired consent	Verify on making valid request to POST /FI/Request API for Expired consent, error response is received.	Http status code should be 400 Error code should be InvalidConsentStatus.
2015	POST /FI/request API for already used Consent	Verify whether POST /FI/request fails if frequency of request is not according to consent's approved frequency.	Http status code should be 400 Error code should be InvalidConsentUse.
2016	POST /FI/request API for already used ONETIME consent	Verify whether POST /FI/request fails if FI/fetch is already done once for ONETIME consent.	Http status code should be 400 Error code should be InvalidConsentUse.
2017	POST /FI/request of FIP	Verify on making valid POST /FI/request to AA, AA is making FI/request with same details to FIP.	Validate the response received on FIP.
2018	POST /FI/Notification of FIU	Verify on making valid POST /FI/request to AA and AA receving READY notification from FIP, AA send POST /Consent/Notification to FIU.	Validate the POST /FI/Notification received on FIU.
2019	POST /FI/request of FIU	Verify FIP responsding with invalid schematic value for each field of POST /FI/request from AA, FI notification with error status is sent back to FIU.	Validate the following on the FI/Notification received on FIU 1. FIStatusNotification.sessionId should match the session id received in the FI response from AA 2. FIStatusNotification.sessionStatus should be FAILED.
2020	POST /FI/request of FIU	FIP responsding with invalid ver for POST /FI/request from AA, FI notification with error status is sent back to FIU.	Validate the following on the POST/FI/Notification received on FIU 1. FIStatusNotification.sessionId should match the session id received in the FI response from AA 2. FIStatusNotification.sessionStatus should be FAILED.
2021	POST /FI/request of FIU	FIP responsding with invalid timestamp for POST /FI/request from AA, FI notification with error status is sent back to FIU.	Validate the following on the POST/FI/Notification received on FIU 1. FIStatusNotification.sessionId should match the session id received in the FI response from AA 2. FIStatusNotification.sessionStatus should be FAILED.
2022	POST /FI/request of FIU	FIP responsding with invalid txnid for POST /FI/request from AA, FI notification with error status is sent back to FIU.	Validate the following on the POST/FI/Notification received on FIU 1. FIStatusNotification.sessionId should match the session id received in the FI response from AA 2. FIStatusNotification.sessionStatus should be FAILED.
2023	POST /FI/request of FIU	FIP responsding with invalid consenId for POST /FI/request from AA, FI notification with error status is sent back to FIU.	Validate the following on the POST/FI/Notification received on FIU 1. FIStatusNotification.sessionId should match the session id received in the FI response from AA 2. FIStatusNotification.sessionStatus should be FAILED.
2024	POST /FI/request of FIU	FIP responsding with invalid sessionId for POST /FI/request from AA, FI notification with error status is sent back to FIU.	Validate the following on the POST/FI/Notification received on FIU 1. FIStatusNotification.sessionId should match the session id received in the FI response from AA 2. FIStatusNotification.sessionStatus should be FAILED.
2025	POST /FI/fetch with valid details	Verify on making valid request to POST /FI/fetch API, success response is received.	Http status code should be 200.
2026	POST /FI/fetch with Invalid session Id	Verify on making valid request to POST /FI/fetch API with invalid session Id, error response is received.	sub-case 1: Empty sessionId Http-status code should be 400 with InvalidRequest sub-case 2,3 & 4: Http status code should be 400 Error code should be InvalidSessionId.
2027	POST /FI/fetch with session Id of alternate FIU	Verify on making valid request to POST /FI/fetch API as alternate FIU with sessionId od regular FIU error response is received.	Http status code should be 400 Error code should be InvalidSessionId.
2028	POST /FI/fetch before receving Ready notification	Verify on making valid request to POST /FI/fetch API before receving ready notification, error response is received.	Http status code should be 404 Error code should be NoDataFound.
2029	POST /FI/fetch for Paused Consent	Verify on making valid request to POST /FI/fetch API for Paused Consent, error response is received.	Http status code should be 403 Error code should be ConsentPaused.
2030	POST /FI/fetch for revoked Consent	Verify on making valid request to POST /FI/fetch API for Revoked Consent, error response is received.	Http status code should be 403 Error code should be ConsentRevoked.
2031	POST /FI/fetch for Expired Consent	Verify on making valid request to POST /FI/fetch API for Expired Consent, error response is received.	Http status code should be 403 Error code should be ConsentExpired.
2032	POST /FI/fetch of FIU	FIP responsding with invalid schematic value for each field of POST /FI/fetch from AA, FI notification with error status is sent back to FIU.	Validate the following on the POST/FI/Notification received on FIU 1. FIStatusNotification.sessionId should match the session id received in the FI response from AA 2. FIStatusNotification.sessionStatus should be FAILED.
2033	POST /FI/fetch of FIU	FIP responsding with invalid ver for POST /FI/fetch of FIU from AA, FI notification with error status is sent back to FIU.	Validate the following on the POST/FI/Notification received on FIU 1. FIStatusNotification.sessionId should match the session id received in the FI response from AA 2. FIStatusNotification.sessionStatus should be FAILED.
2034	POST /FI/fetch of FIU	FIP responsding with invalid timestamp for POST /FI/fetch from AA, FI notification with error status is sent back to FIU.	Validate the following on the POST/FI/Notification received on FIU 1. FIStatusNotification.sessionId should match the session id received in the FI response from AA 2. FIStatusNotification.sessionStatus should be FAILED.
2035	POST /FI/fetch of FIU	FIP responsding with invalid fip id for POST /FI/fetch from AA, FI notification with error status is sent back to FIU.	Validate the following on the POST/FI/Notification received on FIU 1. FIStatusNotification.sessionId should match the session id received in the FI response from AA 2. FIStatusNotification.sessionStatus should be FAILED.
2036	POST /FI/fetch of FIU	FIP responsding with fip id of alternate fip for POST /FI/fetch from AA, FI notification with error status is sent back to FIU.	Validate the following on the POST/FI/Notification received on FIU 1. FIStatusNotification.sessionId should match the session id received in the FI response from AA 2. FIStatusNotification.sessionStatus should be FAILED.
2037	POST /FI/fetch of FIU	FIP responsding with incorrect Account details for POST /FI/fetch from AA, FI notification with error status is sent back to FIU.	Validate the following on the POST/FI/Notification received on FIU 1. FIStatusNotification.sessionId should match the session id received in the FI response from AA 2. FIStatusNotification.sessionStatus should be FAILED.
2038	POST /FI/fetch of FIU	FIP responsding with Account details of alternate FIP for POST /FI/fetch from AA, FI notification with error status is sent back to FIU.	Validate the following on the POST/FI/Notification received on FIU 1. FIStatusNotification.sessionId should match the session id received in the FI response from AA 2. FIStatusNotification.sessionStatus should be FAILED.
2039	POST /FI/fetch of FIU	FIP responsding with invalid keyMatetrials for POST /FI/fetch from AA, FI notification with error status is sent back to FIU.	Validate the following on the POST/FI/Notification received on FIU 1. FIStatusNotification.sessionId should match the session id received in the FI response from AA 2. FIStatusNotification.sessionStatus should be FAILED.
2040	POST /FI/request API with invalid JWS signature	Verify on making valid request to POST /FI/request API with invalid JWS signature, error response is received.	Http status code should be 400 Error code should be InvalidRequest/SignatureDoesNotMatch.
2041	POST /FI/fetch API with invalid JWS signature	Verify on making valid request to POST /FI/fetch API with invalid JWS signature, error response is received.	Http status code should be 400 Error code should be InvalidRequest/SignatureDoesNotMatch.
2042	POST /FI/fetch API with invalid Client API key	Verify on making valid request to POST /FI/fetch API with invalid Client API key, error response is received.	Http status code should be 401.
2043	POST /FI/fetch API with API key of Alternate FIU	Verify on making valid request to POST /FI/fetch API with Client API key of alternate FIU, error response is received.	Http status code should be 400 Error code should be InvalidRequest/SignatureDoesNotMatch.
2044	POST /FI/request API with valid details and invalid Client API key	Verify on making valid request to POST /FI/Request API with valid consent details and invalid Client API key error response is received.	Http status code should be 401.
2045	POST /FI/request API with Clien API key of alternate FIU	Verify on making valid request to POST /FI/Request API with valid consent details and invalid Client API key of alternate FIU error response is received.	Http status code should be 401 Error code should be InvalidRequest/SignatureDoesNotMatch.
2046	POST /FI/fetch API with invalid schematic value for each field	Verify on making valid request to POST /FI/fetch API with schematic error for one field each subcase error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3001	POST /Consent/Notification API with valid details	Verify on making valid request to POST /Consent/Notification API, success response is received.	Https status code should be 200.
3002	POST /Consent/Notification API with invalid schematic value for each field	Verify on making valid request to POST /Consent/Notification API with schematic error for one field each subcase error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3003	POST /Consent/Notification API with incorrect ver	Verify on making valid request to POST /Consent/Notification API with invalid ver, error response is received.	Http status code should be 404 Error code should be NoSuchVersion.
3004	POST /Consent/Notification API with invalid timestamp	Verify on making valid request to POST /Consent/Notification API with invalid timestamp, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3005	POST /Consent/Notification API with invalid txnid	Verify on making valid request to POST /Consent/Notification API with invalid txnid, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3006	POST /Consent/Notification API with invalid notifier Object	Verify on making valid request to POST /Consent/Notification API with invalid notifier object, error response is received.	Http status code should be 400 Error code should be InvalidNotifier.
3007	POST /Consent/Notification API with invalid consentId	Verify on making valid request to POST /Consent/Notification API with invalid consentId, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3008	POST /Consent/Notification API with consent details of alternate FIP	Verify on making valid POST /Consent/Notification API request as alternate FIP with consent details of regular FIP, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3009	POST /FI/Notification API with valid details	Verify on making valid request to POST /FI/Notification API, success response is received.	Https status code should be 200.
3010	POST /FI/Notification API with invalid schematic value for each field	Verify on making valid request to POST /FI/Notification API with schematic error for one field each subcase error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3011	POST /FI/Notification API with incorrect ver	Verify on making valid request to POST /FI/Notification API with invalid ver, error response is received.	Http status code should be 404 Error code should be NoSuchVersion.
3012	POST /FI/Notification API with invalid timestamp	Verify on making valid request to POST /FI/Notification API with invalid timestamp, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3013	POST /FI/Notification API with invalid txnid	Verify on making valid request to POST /FI/Notification API with invalid txnid, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3014	POST /FI/Notification API with invalid notifier Object	Verify on making valid request to POST /FI/Notification API with invalid notifier object, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3015	POST /FI/Notification API with invalid sessionId	Verify on making valid request to POST /FI/Notification API with invalid sessionId, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3016	POST /FI/Notification API with invalid FIStatusResponse.fipID	Verify on making valid request to POST /FI/Notification API with invalid FIStatusResponse.fipID, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3017	POST /FI/Notification API with invalid FIStatusResponse Accounts linkRefNumber	Verify on making valid request to POST /FI/Notification API with invalid FIStatusResponse Accounts linkRefNumber, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3018	POST /FI/Notification API with FI details of alternate FIP	Verify on making valid POST /FI/Notification API request as alternate FIP with FI details of regular FIP, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3019	POST /FI/Notification API with error FI status	Verify on making valid request to POST /FI/Notification API with error FI status, same FIStatus is sent to FIU.	Validate the following on the POST /FI/Notification received on FIU 1. FIStatusNotification.sessionId should match the session id received in the FI response from AA 2. FIStatusNotification.sessionStatus should be FAILED.
3020	POST /Account/link/Notification API with valid detils	Verify on making valid request to POST /Account/link/Notification API, success response is received.	Http status code should be 200.
3021	POST /Account/link/Notification API with invalid schematic value for each field	Verify on making valid request to POST /Account/link/Notification API with schematic error for one field each subcase error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3022	POST /Account/link/Notification API with incorrect ver	Verify on making valid request to POST /Account/link/Notification API with invalid ver, error response is received.	Http status code should be 404 Error code should be NoSuchVersion.
3023	POST /Account/link/Notification API with invalid timestamp	Verify on making valid request to POST /Account/link/Notification API with invalid timestamp, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3024	POST /Account/link/Notification API with invalid txnid	Verify on making valid request to POST /Account/link/Notification API with invalid txnid, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3025	POST /Account/link/Notification API with invalid notifier object	Verify on making valid request to POST /Account/link/Notification API with invalid notifier object, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3026	POST /Account/link/Notification API with invalid accRefNumber	Verify on making valid request to POST /Account/link/Notification API with invalid accRefNumber, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3027	POST /Account/link/Notification API with invalid customerAddress	Verify on making valid request to POST /Account/link/Notification API with invalid customerAddress, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3028	POST /Account/link/Notification API for deregistered user	Verify on making valid request to POST /Account/link/Notification API for deregistred user, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3029	POST /Account/link/Notification API as alternate FIP with details of regular FIP	Verify on making valid POST /Account/link/Notification API request as alternate FIP with details of regular FIP, error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3030	POST /Consent/Notification API with invalid JWS Signature	Verify on making valid request to POST /Consent/Notification API with invalid JWS Signature, error response is received.	Http status code should be 400 Error code should be InvalidRequest/SignatureDoesNotMatch.
3031	POST /FI/Notification API with invalid JWS Signature	Verify on making valid request to POST /FI/Notification API with invalid JWS Signature, error response is received.	Http status code should be 400 Error code should be InvalidRequest/SignatureDoesNotMatch.
3032	POST /Account/link/Notification API with invalid JWS Signature	Verify on making valid request to POST /Account/link/Notification API with invalid JWS Signature, error response is received.	Http status code should be 400 Error code should be InvalidRequest/SignatureDoesNotMatch.
3033	POST /Consent/Notification API with invalid API	Verify on making valid request to POST /Consent/Notification API with invalid API key error response is received.	Http status code should be 401.
3034	POST /Consent/Notification API with API key	Verify on making valid request to POST /Consent/Notification API with API key of alternate FIP error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3035	POST /FI/Notification API with invalid FIP API	Verify on making valid request to POST /FI/Notification API with invalid FIP API key error response is received.	Http status code should be 401.
3036	POST /FI/Notification API with alternate FIP	Verify on making valid request to POST /FI/Notification API with API key of alternate FIP error response is received.	Http status code should be 400 Error code should be InvalidRequest.
3037	POST /Account/link/Notification API with invalid FIP key	Verify on making valid request to POST /Account/link/Notification API with invalid FIP key error response is received.	Http status code should be 401.
3038	POST /Account/link/Notification API with alternate FIP	Verify on making valid request to POST /Account/link/Notification API with alternate FIP key header error response is received.	Http status code should be 400 Error code should be InvalidRequest.
4001	GET /Heartbeat with FIP	Verify on making valid request to GET /Heartbeat API as an FIP, success response is received.	Http status code should be 200 and status should be Up.
4002	GET /Heartbeat with FIU	Verify on making valid request to GET /Heartbeat API as an FIU, success response is received.	Http status code should be 200 and status should be Up.
5001	Full Flow of AA	Verify that on consent requested to user operating with a single linked account in one FIP, success response is received on all stages of complete flow.	Https status code should be 200 for All API's.
5002	Full Flow of AA	Verify that on consent requested to user currently with no accounts linked, user is able to link account, approve consent and FIU is able to retrive the FI data successfully.	Https status code should be 200 for All API's.
5003	Full Flow of AA	Verify that on consent requested to user operating with a two accounts in one FIP and three accounts in other FIP of three different FIType, FIU is able to retrive the FI data successfully from all five accounts.	Https status code should be 200 for All API's.
5004	Full Flow of AA	Verify that on FIP operating with DIRECT authentication type, AA is able to link FIP and facilitate the FI data retrival for FIU.	Https status code should be 200 for All API's.
5005	Full Flow of AA	Verify that on consent paused and activated back by user, AA is able to facilitate the FI data retrival for FIU.	Https status code should be 200 for All API's.
5006	Full Flow of AA	Verify that on consent requested to user with all possible consent modes, purpose codes, DataLife units with value 0 to 4, consent types combinations, Frequency units with value 1 to 4 and DataFilter type and operator combinations, success response is received on all stages of complete flow.	Https status code should be 200 for All API's.
5007	Full Flow of AA	Verify that on requesting consent with all FITypes, AA is able to facilitate consent approval and retrival of FI data for FIU.	Https status code should be 200 for All API's.