Implemented Test Cases
- Alex Ischimji
- Rajeev Walia
Swagger Test Case ID | Test Id | Field to be updated in the config.yaml | Test Name | Test Description |
| get-account |
| ||
ACC-010-010 | AIS_A001 | accountToTest : Retail_CurrentAccount_Active | Happy Path - Succeeds with status-Active, accountType-Retail and accountSubType-CurrentAccount fields are populated for valid accountId as query parameter (accountToTest : Retail_CurrentAccount_Active) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Retail' and account sub type 'CurrentAccount', for a retail user with status 'Active' |
ACC-010-010 | AIS_A002 | accountToTest : Corporate_Savings_NotActive | Happy Path - Succeeds with status-NotActive, accountType-Corporate and accountSubType-Savings fields are populated for valid accountId as query parameter (accountToTest : Corporate_Savings_NotActive) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Corporate' and account sub type 'Savings', for a retail user with status 'NotActive' |
ACC-010-010 | AIS_A003 | accountToTest : Retail_EMoney_Deceased | Happy Path - Succeeds with status-Deceased, accountType-Retail and accountSubType-EMoney fields are populated for valid accountId as query parameter (accountToTest : Retail_EMoney_Deceased) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Retail' and account sub type 'EMoney', for a retail user with status 'Deceased' |
ACC-010-010 | AIS_A004 | accountToTest : Retail_CreditCard_Dormant | Happy Path - Succeeds with status-Dormant, accountType-Retail and accountSubType-CreditCard fields are populated for valid accountId as query parameter (accountToTest : Retail_CreditCard_Dormant) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Retail' and account sub type 'CreditCard', for a retail user with status 'Dormant' |
ACC-010-010 | AIS_A005 | accountToTest : Corporate_PrePaidCard_Unclaimed | Happy Path - Succeeds with status-Unclaimed, accountType-Corporate and accountSubType-PrePaidCard fields are populated for valid accountId as query parameter (accountToTest : Corporate_PrePaidCard_Unclaimed) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Corporate' and account sub type 'PrePaidCard', for a retail user with status 'Unclaimed' |
ACC-010-010 | AIS_A006 | accountToTest : Corporate_ChargeCard_Suspended | Happy Path - Succeeds with status-Suspended, accountType-Corporate and accountSubType-ChargeCard fields are populated for valid accountId as query parameter (accountToTest : Corporate_ChargeCard_Suspended) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Corporate' and account sub type 'ChargeCard', for a retail user with status 'Suspended' |
ACC-010-010 | AIS_A007 | accountToTest : Corporate_CurrentAccount_Active | Happy Path - Succeeds with status-Active, accountType-Corporate and accountSubType-CurrentAccount fields are populated for valid accountId as query parameter (accountToTest : Corporate_CurrentAccount_Active) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Corporate' and account sub type 'CurrentAccount', for a retail user with status 'Active' |
ACC-010-010 | AIS_A008 | accountToTest : Retail_Savings_NotActive | Happy Path - Succeeds with status-NotActive, accountType-Retail and accountSubType-Savings fields are populated for valid accountId as query parameter (accountToTest : Retail_Savings_NotActive) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Retail' and account sub type 'Savings', for a retail user with status 'NotActive' |
ACC-010-010 | AIS_A009 | accountToTest : Corporate_CreditCard_Dormant | Happy Path - Succeeds with status-Dormant, accountType-Corporate and accountSubType-CreditCard fields are populated for valid accountId as query parameter (accountToTest : Corporate_CreditCard_Dormant) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Corporate' and account sub type 'CreditCard', for a retail user with status 'Dormant' |
ACC-010-140 | AIS_A010 | accountToTest: Valid_Invalid_AccountIds | Happy Path - Succeeds with combination of valid and invalid accountIds (accountToTest: Valid_Invalid_AccountIds) | Returns a 200 if all headers are valid and returns a record for each valid accountId when both valid and invalid accountIds are specified (accountToTest : Valid_Invalid_AccountId) |
ACC-010-140 | AIS_A011 | accountToTest: Good_And_Badly_Formatted_AccountIds | Happy Path - Succeeds with mix of valid and invalid accountIds (accountToTest: Good_And_Badly_Formatted_AccountIds) | Returns a 200 if all headers are valid and returns a record for each valid accountId when both valid and invalid accountIds are specified (accountToTest : Good_And_Badly_Formatted_AccountIds) |
| AIS_A012 | accountToTest: AccountsWithNoCommas | Happy Path - Succeeds with non-comma-separated accountIds (accountToTest: AccountsWithNoCommas) | Returns a 200 if all headers are valid and returns an empty array when non-comma-separated accountIds are specified (accountToTest : AccountsWithNoCommas) |
ACC-010-020 | AIS_A013 | accountToTest : NoAccount | Negative Test - Fails if accountIds query parameter is missing (accountToTest : NoAccount) | If accountIds path parameter is missing, the API must return a 400 and an error body |
| AIS_A014 | accountToTest : Invalid_Single_AccountId | Negative Test - Fails with 400 if accountId format is invalid (accountToTest : Invalid_Single_AccountId) | If the accountId format is invalid, the API must return a 400 and an error body |
ACC-010-050 | AIS_A015 | accountToTest : NoAccount | Negative Test - Mandatory field validation - Fail if both accountId and o3-psu-identifier are missing (accountToTest : NoAccount) | The operation must fail with a status of 400 if both the accountId path parameter and the o3-psu-identifier header parameter are missing |
ACC-010-040 | AIS_A016 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing |
ACC-010-070 | AIS_A017 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is missing |
ACC-010-080 | AIS_A018 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-operation header is missing |
| AIS_A019 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing |
ACC-010-090 | AIS_A020 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing |
ACC-010-030 | AIS_A021 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header has an unexpected value |
| AIS_A022 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is missing |
| AIS_A023 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is missing |
| AIS_A024 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is missing |
| AIS_A025 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is missing |
| AIS_A026 | accountToTest : SampleAccount | Negative Test - Fails if o3-aspsp-id has an invalid value (accountToTest : SampleAccount) | If o3-aspsp-id has an invalid value, the API must return a 400 and an error body |
| AIS_A027 | accountToTest : SampleAccount | Negative Test - Fails if o3-psu-identifier is not b64 encoded (accountToTest : SampleAccount) | If o3-psu-identifier is not b64 encoded, the API must return a 400 and an error body |
| AIS_A028 | accountToTest : SampleAccount | Negative Test - Fails if o3-psu-identifier does not evaluate to a json structure (accountToTest : SampleAccount) | If o3-psu-identifier does not evaluate to a json structure, the API must return a 400 and an error body |
| AIS_A029 | accountToTest : SampleAccount | Negative Test - Fails if o3-psu-identifier does not contain userId (accountToTest : SampleAccount) | If o3-psu-identifier does not contain userId, the API must return a 400 and an error body |
ACC-020-010 | AIS_A030 | accountToTest : Retail_CurrentAccount_Active | Happy Path - Succeeds with valid CurrentAccount for retail user in Active status for valid accountId as path parameter (accountToTest : Retail_CurrentAccount_Active) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Retail' and account sub type 'CurrentAccount', for a retail user with status 'Active' |
ACC-020-010 | AIS_A031 | accountToTest : Corporate_Savings_NotActive | Happy Path - Succeeds with valid Savings for retail user in NotActive status for valid accountId as path parameter (accountToTest : Corporate_Savings_NotActive) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Corporate' and account sub type 'Savings', for a retail user with status 'NotActive' |
ACC-020-010 | AIS_A032 | accountToTest : Retail_EMoney_Deceased | Happy Path - Succeeds with valid EMoney for retail user in Deceased status for valid accountId as path parameter (accountToTest : Retail_EMoney_Deceased) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Retail' and account sub type 'EMoney', for a retail user with status 'Deceased' |
ACC-020-040 | AIS_A033 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing |
ACC-020-070 | AIS_A034 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is missing |
ACC-020-080 | AIS_A035 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-operation header is missing |
| AIS_A036 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing |
ACC-020-090 | AIS_A037 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing |
ACC-020-030 | AIS_A038 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header has an unexpected value |
| AIS_A039 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is missing |
| AIS_A040 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is missing |
| AIS_A041 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is missing |
| AIS_A042 | accountToTest : SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (accountToTest : SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is missing |
| AIS_A043 | accountToTest : SampleAccount | Negative Test - Fails if o3-aspsp-id has an invalid value (accountToTest : SampleAccount) | If o3-aspsp-id has an invalid value, the API must return a 400 and an error body |
| AIS_A044 | accountToTest : SampleAccount | Negative Test - Fails if o3-psu-identifier is not b64 encoded (accountToTest : SampleAccount) | If o3-psu-identifier is not b64 encoded, the API must return a 400 and an error body |
| AIS_A045 | accountToTest : SampleAccount | Negative Test - Fails if o3-psu-identifier does not evaluate to a json structure (accountToTest : SampleAccount) | If o3-psu-identifier does not evaluate to a json structure, the API must return a 400 and an error body |
| AIS_A046 | accountToTest : SampleAccount | Negative Test - Fails if o3-psu-identifier does not contain userId (accountToTest : SampleAccount) | If o3-psu-identifier does not contain userId, the API must return a 400 and an error body |
ACC-020-010 | AIS_A047 | accountToTest : Retail_CurrentAccount_Active | Happy Path - Succeeds with valid CurrentAccount for Corporate user in Dormant status for valid accountId as path parameter (accountToTest : Retail_CurrentAccount_Active) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Corporate' and account sub type 'CurrentAccount', for a corporate user with status 'Dormant' |
ACC-020-010 | AIS_A048 | accountToTest : Corporate_Savings_NotActive | Happy Path - Succeeds with valid Savings for retail user in Suspended status for valid accountId as path parameter (accountToTest : Corporate_Savings_NotActive) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Retail' and account sub type 'Savings', for a retail user with status 'Suspended' |
ACC-020-010 | AIS_A049 | accountToTest : Retail_CreditCard_Dormant | Happy Path - Succeeds with valid Savings for SME user in NotActive status for valid accountId as path parameter (accountToTest : Retail_CreditCard_Dormant) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'SME' and account sub type 'Savings', for an SME user with status 'NotActive' |
ACC-020-010 | AIS_A050 | accountToTest : Retail_CurrentAccount_Active | Happy Path - Succeeds with valid Savings for Corporate user in Active status for valid accountId as path parameter (accountToTest : Retail_CurrentAccount_Active) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Corporate' and account sub type 'Savings', for a corporate user with status 'Active' |
ACC-020-010 | AIS_A051 | accountToTest : Retail_CreditCard_Dormant | Happy Path - Valid accountId provided: CreditCard for retail user (accountToTest : Retail_CreditCard_Dormant) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Retail' and account sub type 'CreditCard', for a retail user |
ACC-020-010 | AIS_A052 | accountToTest : SME_CreditCard_Active | Happy Path - Valid accountId provided: CreditCard for SME user (accountToTest : SME_CreditCard_Active) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'SME' and account sub type 'CreditCard', for an SME user |
ACC-020-010 | AIS_A053 | accountToTest : Corporate_CreditCard_Dormant | Happy Path - Valid accountId provided: CreditCard for Corporate user (accountToTest : Corporate_CreditCard_Dormant) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Corporate' and account sub type 'CreditCard', for a corporate user |
ACC-020-010 | AIS_A054 | accountToTest : Retail_PrePaidCard_Active | Happy Path - Valid accountId provided: PrePaidCard for retail user (accountToTest : Retail_PrePaidCard_Active) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Retail' and account sub type 'PrePaidCard', for a retail user |
ACC-020-010 | AIS_A055 | accountToTest : SME_PrePaidCard_Active | Happy Path - Valid accountId provided: PrePaidCard for SME user (accountToTest : SME_PrePaidCard_Active) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'SME' and account sub type 'PrePaidCard', for an SME user |
ACC-020-010 | AIS_A056 | accountToTest : Corporate_PrePaidCard_Active | Happy Path - Valid accountId provided: PrePaidCard for Corporate user (accountToTest : Corporate_PrePaidCard_Active) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Corporate' and account sub type 'PrePaidCard', for a corporate user |
ACC-020-010 | AIS_A057 | accountToTest : Retail_EMoney_Active | Happy Path - Valid accountId provided: EMoney for retail user (accountToTest : Retail_EMoney_Active) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Retail' and account sub type 'EMoney', for a retail user |
ACC-020-010 | AIS_A058 | accountToTest : SME_EMoney_Active | Happy Path - Valid accountId provided: EMoney for SME user (accountToTest : SME_EMoney_Active) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'SME' and account sub type 'EMoney', for an SME user |
ACC-020-010 | AIS_A059 | accountToTest : Corporate_EMoney_Active | Happy Path - Valid accountId provided: EMoney for Corporate user (accountToTest : Corporate_EMoney_Active) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Corporate' and account sub type 'EMoney', for a corporate user |
ACC-020-010 | AIS_A060 | accountToTest: SME_ChargeCard_Active | Happy Path - Valid accountId provided: ChargeCard for SME user (accountToTest: SME_ChargeCard_Active) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'SME' and account sub type 'ChargeCard', for an SME user |
ACC-020-010 | AIS_A061 | accountToTest: Corporate_ChargeCard_Active | Happy Path - Valid accountId provided: ChargeCard for Corporate user (accountToTest: Corporate_ChargeCard_Active) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Corporate' and account sub type 'ChargeCard', for a corporate user |
ACC-020-010 | AIS_A062 | accountToTest: Retail_ChargeCard_Active | Happy Path - Valid accountId provided: ChargeCard for Retail user (accountToTest: Retail_ChargeCard_Active) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Retail' and account sub type 'ChargeCard', for a retail user |
ACC-020-010 | AIS_A063 | accountToTest: Retail_Other_Active | Happy Path - Valid accountId provided: Other for Retail (accountToTest: Retail_Other_Active) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Retail' and account sub type 'Other', for a retail user |
ACC-020-010 | AIS_A064 | accountToTest: Corporate_Other_Active | Happy Path - Valid accountId provided: Other for Corporate (accountToTest: Corporate_Other_Active) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'Corporate' and account sub type 'Other', for a corporate user |
ACC-020-010 | AIS_A065 | accountToTest: SME_Other_Active | Happy Path - Valid accountId provided: Other for SME (accountToTest: SME_Other_Active) | Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'SME' and account sub type 'Other', for an SME user |
| AIS_A066 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is having invalid value |
| AIS_A067 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is having invalid value |
| AIS_A068 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is having invalid value |
| AIS_A069 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is having invalid value |
ACC-020-030 | AIS_A070 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header is having invalid value |
ACC-020-090 | AIS_A071 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is having invalid value |
ACC-020-080 | AIS_A072 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-operation header is having invalid value |
ACC-020-070 | AIS_A073 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is having invalid value |
ACC-020-020 | AIS_A074 | accountToTest : NoAccount | Negative Test - Fails if accountIds path parameter is missing (accountToTest : NoAccount) | If accountIds path parameter is missing, the API must return a 401 and an error body |
| AIS_A075 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined (accountToTest: SampleAccount) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined, the API must return a 400 and an error body |
| AIS_A076 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string (accountToTest: SampleAccount) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string, the API must return a 400 and an error body |
| get-balances |
| ||
BAL-020-010 | AIS_BA001 | accountToTest: Valid_Accounts_List | Happy path - Succeeds if valid accountId in path parameter returns balances (accountToTest: Valid_Accounts_List) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with balance details |
BAL-020-020 | AIS_BA002 | accountToTest: NoAccount | Negative Test - Fails if accountIds path parameter is missing (accountToTest: NoAccount) | If accountIds path parameter is missing, the API must return a 401 and an error body |
| AIS_BA003 | accountToTest: Invalid_Single_AccountId | Negative Test - Fails if accountId format is invalid (accountToTest: Invalid_Single_AccountId) | If the accountId format is invalid , the API must return a 400 and an error body |
BAL-020-050 | AIS_BA004 | accountToTest: NoAccount | Negative Test - Mandatory field validation - Fail if both accountId and o3-psu-identifier are missing (accountToTest: NoAccount) | The operation must fail with a status of 400 if both the accountId path parameter and the o3-psu-identifier header parameter are missing |
BAL-020-040 | AIS_BA005 | accountToTest: SampleSingleAccount | Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest: SampleSingleAccount) | The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing |
BAL-020-070 | AIS_BA006 | accountToTest: SampleSingleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest: SampleSingleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is missing |
BAL-020-080 | AIS_BA007 | accountToTest: SampleSingleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest: SampleSingleAccount) | The operation must fail with a status code 400 and error body if the o3-api-operation header is missing |
| AIS_BA008 | accountToTest: SampleSingleAccount | Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (accountToTest: SampleSingleAccount) | The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing |
BAL-020-090 | AIS_BA009 | accountToTest: SampleSingleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest: SampleSingleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing |
BAL-020-030 | AIS_BA010 | accountToTest: SampleSingleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest: SampleSingleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header has an unexpected value |
| AIS_BA011 | accountToTest: SampleSingleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (accountToTest: SampleSingleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is missing |
| AIS_BA012 | accountToTest: SampleSingleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (accountToTest: SampleSingleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is missing |
| AIS_BA013 | accountToTest: SampleSingleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (accountToTest: SampleSingleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is missing |
| AIS_BA014 | accountToTest: SampleSingleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (accountToTest: SampleSingleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is missing |
BAL-020-010 | AIS_BA015 | accountToTest: AccountIdWithCreditIndicator | Happy path - Succeeds if valid accountId in path parameter returns balances with positive balance and credit line included (accountToTest: AccountIdWithCreditIndicator) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with balance detail where the creditDebitIndicator value is Credit and the CreditLines are populated with relevant details |
BAL-020-010 | AIS_BA016 | accountToTest: AccountIdWithDebitIndicator | Happy path - Succeeds if valid accountId in path parameter returns balances with negative balance and no credit line (accountToTest: AccountIdWithDebitIndicator) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with balance detail where the creditDebitIndicator value is Debit and the CreditLines object is not present |
BAL-020-010 | AIS_BA017 | accountToTest: AccountIdWithZeroCreditIndicator | Happy path - Succeeds if valid accountId in path parameter returns zero balance with creditDebitIndicator value as 'credit' (accountToTest: AccountIdWithZeroCreditIndicator) | Valid accountId provided in the path parameter which has zero balance should return a 200 and the accountId must be present in the response with balance detail where the creditDebitIndicator value is Credit |
| AIS_BA018 | accountToTest: SampleSingleAccount | Negative Test - Fails if o3-aspsp-id has an invalid value (accountToTest: SampleSingleAccount) | If o3-aspsp-id has an invalid value, the API must return a 400 and an error body |
| AIS_BA019 | accountToTest: SampleSingleAccount | Negative Test - Fails if o3-psu-identifier is not b64 encoded (accountToTest: SampleSingleAccount) | If o3-psu-identifier is not b64 encoded, the API must return a 400 and an error body |
| AIS_BA020 | accountToTest: SampleSingleAccount | Negative Test - Fails if o3-psu-identifier does not evaluate to a json structure (accountToTest: SampleSingleAccount) | If o3-psu-identifier does not evaluate to a json structure, the API must return a 400 and an error body |
| AIS_BA021 | accountToTest: SampleSingleAccount | Negative Test - Fails if o3-psu-identifier does not contain userId (accountToTest: SampleSingleAccount) | If o3-psu-identifier does not contain userId, the API must return a 400 and an error body |
BAL-020-120 | AIS_BA022 | accountToTest: AccountWithMultipleBalancesTypes | Happy path - Succeeds if valid accountId in path parameter returns balances with multiple balanceTypes (accountToTest: AccountWithMultipleBalancesTypes) | Valid accountId provided in the path parameter which has multiple balanceTypes should return a 200 and the accountId must be present in the response with balance details for all the balanceTypes |
| AIS_BA023 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is having invalid value |
| AIS_BA024 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is having invalid value |
| AIS_BA025 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is having invalid value |
| AIS_BA026 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is having invalid value |
BAL-020-030 | AIS_BA027 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header is having invalid value |
BAL-020-090 | AIS_BA028 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is having invalid value |
BAL-020-080 | AIS_BA029 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-operation header is having invalid value |
BAL-020-070 | AIS_BA030 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is having invalid value |
| AIS_BA031 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined (accountToTest: SampleAccount) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined, the API must return a 400 and an error body |
| AIS_BA032 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string (accountToTest: SampleAccount) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string, the API must return a 400 and an error body |
| get-beneficiaries |
| ||
BEN-020-010 | AIS_BE001 | accountToTest: AccountIdWithActivatedBeneficiaryType | Happy path - Succeeds if valid accountId in path parameter returns beneficiaries with beneficiaries category Activated in response body (accountToTest: AccountIdWithActivatedBeneficiaryType) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with a details of beneficiaries and status Activated |
BEN-020-010 | AIS_BE002 | accountToTest: AccountIdWithNotActivatedBeneficiaryType | Happy path - Succeeds if valid accountId in path parameter returns beneficiaries with beneficiaries category NotActivated in response body (accountToTest: AccountIdWithNotActivatedBeneficiaryType) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with a details of beneficiaries and status NotActivated |
| AIS_BE003 | accountToTest: Valid_Beneficiaries_Accounts_List | Happy path - Succeeds with the specified number of accounts in each page and the meta information about the pagination (accountToTest: Valid_Beneficiaries_Accounts_List) | Returns a 200 status code with the specified number of accounts in each page and the meta information about the pagination |
BEN-020-010 | AIS_BE004 | accountToTest: AccountIdWithNoBeneficiaries | Happy path - Succeeds if valid accountId in path parameter returns no beneficiaries (accountToTest: AccountIdWithNoBeneficiaries) | Valid accountId provided in the path parameter should return a 200 with an empty array if there are no beneficiaries |
BEN-020-050BEN-020-020 | AIS_BE005 |
| Negative Test - Fails if accountIds path parameter is missing | If accountIds path parameter is missing, the API must return a 401 and an error body |
| AIS_BE006 | accountToTest: Invalid_Single_AccountId | Negative Test - Fails with 400 if accountId format is invalid (accountToTest: Invalid_Single_AccountId) | If the accountId format is invalid , the API must return a 400 and an error body |
BEN-020-050 | AIS_BE007 | accountToTest: NoAccount | Negative Test - Mandatory field validation - Fail if both accountId and o3-psu-identifier are missing (accountToTest: NoAccount) | The operation must fail with a status of 400 if both the accountId path parameter and the o3-psu-identifier header parameter are missing |
BEN-020-040 | AIS_BE008 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing |
BEN-020-060 | AIS_BE009 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is missing |
BEN-020-070 | AIS_BE010 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-operation header is missing |
| AIS_BE011 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing |
BEN-020-080 | AIS_BE012 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing |
BEN-020-030 | AIS_BE013 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header has an unexpected value |
| AIS_BE014 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is missing |
| AIS_BE015 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is missing |
| AIS_BE016 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is missing |
| AIS_BE017 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is missing |
| AIS_BE018 | accountToTest: SampleAccount | Negative Test - Fails if o3-aspsp-id has an invalid value (accountToTest: SampleAccount) | If o3-aspsp-id has an invalid value, the API must return a 400 and an error body |
| AIS_BE019 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier is not b64 encoded (accountToTest: SampleAccount) | If o3-psu-identifier is not b64 encoded, the API must return a 400 and an error body |
| AIS_BE020 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier does not evaluate to a json structure (accountToTest: SampleAccount) | If o3-psu-identifier does not evaluate to a json structure, the API must return a 400 and an error body |
| AIS_BE021 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier does not contain userId (accountToTest: SampleAccount) | If o3-psu-identifier does not contain userId, the API must return a 400 and an error body |
| AIS_BE022 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is having invalid value |
| AIS_BE023 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is having invalid value |
| AIS_BE024 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is having invalid value |
| AIS_BE025 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is having invalid value |
BEN-020-030 | AIS_BE026 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header is having invalid value |
BEN-020-080 | AIS_BE027 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is having invalid value |
BEN-020-070 | AIS_BE028 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-operation header is having invalid value |
BEN-020-060 | AIS_BE029 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is having invalid value |
BEN-020-010 | AIS_BE030 | accountToTest: AccountIdWithActivatedAndNotActivatedBeneficiaryType | Happy path - Succeeds if valid accountId in path parameter returns beneficiaries with beneficiaries category Activated and NotActivated in response body (accountToTest: AccountIdWithActivatedAndNotActivatedBeneficiaryType) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with a details of beneficiaries and status Activated and NotActivated |
| AIS_BE031 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined (accountToTest: SampleAccount) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined, the API must return a 400 and an error body |
| AIS_BE032 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string (accountToTest: SampleAccount) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string, the API must return a 400 and an error body |
| get-customers |
| ||
CUS-010-040 | AIS_C001 | customerType: Delegate_CustomerType | Happy path - Succeeds if customer for PSU identified by o3-psu-identifier header (customerType: Delegate_CustomerType) | The API must return the customer for the PSU identified by the o3-psu-identifier header |
CUS-010-040 | AIS_C002 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing |
CUS-010-070 | AIS_C003 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is missing |
CUS-010-080 | AIS_C004 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest: SampleAccount) | TThe operation must fail with a status code 400 and error body if the o3-api-operation header is missing |
| AIS_C005 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing |
CUS-010-090 | AIS_C006 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing |
CUS-010-030 | AIS_C007 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header has an unexpected value |
| AIS_C008 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is missing |
| AIS_C009 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is missing |
| AIS_C010 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is missing |
| AIS_C011 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is missing |
| AIS_C012 | accountToTest: SampleAccount | Negative Test - Fails if o3-aspsp-id has an invalid value (accountToTest: SampleAccount) | If o3-aspsp-id has an invalid value, the API must return a 200 and an error body |
| AIS_C013 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier is not b64 encoded (accountToTest: SampleAccount) | If o3-psu-identifier is not b64 encoded, the API must return a 400 and an error body |
| AIS_C014 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier does not evaluate to a json structure (accountToTest: SampleAccount) | If o3-psu-identifier does not evaluate to a json structure, the API must return a 400 and an error body |
| AIS_C015 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier does not contain userId (accountToTest: SampleAccount) | If o3-psu-identifier does not contain userId, the API must return a 400 and an error body |
| AIS_C016 | accountToTest: SampleAccount | Negative Test - Fails if accountIds path parameter is missing (accountToTest: SampleAccount) | If accountIds path parameter is missing, the API must return a 401 and an error body |
| AIS_C017 | accountToTest: Invalid_Single_AccountId | Negative Test - Fails with 400 if accountId format is invalid (accountToTest: Invalid_Single_AccountId) | If the accountId format is invalid , the API must return a 400 and an error body |
CUS-020-040 | AIS_C018 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing |
CUS-020-070 | AIS_C019 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is missing |
CUS-020-080 | AIS_C020 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest: SampleAccount) | TThe operation must fail with a status code 400 and error body if the o3-api-operation header is missing |
| AIS_C021 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing |
CUS-020-090 | AIS_C022 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing |
CUS-020-030 | AIS_C023 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header has an unexpected value |
| AIS_C024 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is missing |
| AIS_C025 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is missing |
| AIS_C026 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is missing |
| AIS_C027 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is missing |
| AIS_C028 | accountToTest: Delegate_CustomerType | Happy path - Succeeds when all headers are valid and provides the associated customer details linked to the accountId provided in the request (accountToTest: Delegate_CustomerType) | Returns a 200 status code when all headers are valid and provides the associated customer details linked to the accountId provided in the request |
CUS-010-190 | AIS_C029 |
| Happy path - Succeeds when no customer is found | The API must return a success status code 200 with an empty data object if no customer is found |
CUS-010-040 | AIS_C030 | customerType : Retail_CustomerType | Happy path - Succeeds when valid o3-psu-identifier provided in the header which belongs to a retail user (customerType : Retail_CustomerType) | Returns a 200 status code with details of a retail user in the response as per the schema |
CUS-010-040 | AIS_C031 | customerType : Corporate_CustomerType | Happy path - Succeeds when valid o3-psu-identifier provided in the header which belongs to a corporate user (customerType : Corporate_CustomerType) | Returns a 200 status code with details of a corporate user in the response as per the schema |
CUS-010-040 | AIS_C032 | customerType : SME_CustomerType | Happy path - Succeeds when valid o3-psu-identifier provided in the header which belongs to a SME user (customerType : SME_CustomerType) | Returns a 200 status code with details of a SME user in the response as per the schema |
| AIS_C033 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is having invalid value |
| AIS_C034 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is having invalid value |
| AIS_C035 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is having invalid value |
| AIS_C036 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is having invalid value |
CUS-020-030 | AIS_C037 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header is having invalid value |
CUS-020-090 | AIS_C038 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is having invalid value |
CUS-020-080 | AIS_C039 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-operation header is having invalid value |
CUS-020-070 | AIS_C040 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is having invalid value |
| AIS_C041 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined (accountToTest: SampleAccount) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined, the API must return a 400 and an error body |
| AIS_C042 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string (accountToTest: SampleAccount) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string, the API must return a 400 and an error body |
| get-direct-debits |
| ||
DBT-020-010 | AIS_DD001 | accountToTest: AccountIdWithDirectDebitActiveStatus | Happy path - Succeeds if valid accountId in path parameter returns direct-debits with status Active in response body (accountToTest: AccountIdWithDirectDebitActiveStatus) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with a details of direct-debits and status Active |
DBT-020-010 | AIS_DD002 | accountToTest: AccountIdWithDirectDebitInActiveStatus | Happy path - Succeeds if valid accountId in path parameter returns direct-debits with status Inactive in response body (accountToTest: AccountIdWithDirectDebitInActiveStatus) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with a details of direct-debits and status Inactive |
| AIS_DD003 | accountToTest: Valid_DirectDebits_Accounts_List | Happy path - Validate the meta information about the pagination (accountToTest: Valid_DirectDebits_Accounts_List) | Returns a 200 status code with the specified number of accounts in each page and the meta information about the pagination |
DBT-020-010 | AIS_DD004 | accountToTest: AccountIdWithDirectDebitAnnualFrequency | Happy path - Succeeds if valid accountId in path parameter returns direct-debits with Annual frequency in response body (accountToTest: AccountIdWithDirectDebitAnnualFrequency) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with direct-debits of Annual frequencies |
DBT-020-010 | AIS_DD005 | accountToTest: AccountIdWithDirectDebitDailyFrequency | Happy path - Succeeds if valid accountId in path parameter returns direct-debits with Daily frequency in response body (accountToTest: AccountIdWithDirectDebitDailyFrequency) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with direct-debits of Daily frequencies |
DBT-020-010 | AIS_DD006 | accountToTest: AccountIdWithDirectDebitFortnightlyFrequency | Happy path - Succeeds if valid accountId in path parameter returns direct-debits with Fortnightly frequency in response body (accountToTest: AccountIdWithDirectDebitFortnightlyFrequency) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with direct-debits of Fortnightly frequencies |
DBT-020-010 | AIS_DD007 | accountToTest: AccountIdWithDirectDebitHalfYearlyFrequency | Happy path - Succeeds if valid accountId in path parameter returns direct-debits with HalfYearly frequency in response body (accountToTest: AccountIdWithDirectDebitHalfYearlyFrequency) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with direct-debits of HalfYearly frequencies |
DBT-020-010 | AIS_DD008 | accountToTest: AccountIdWithDirectDebitMonthlyFrequency | Happy path - Succeeds if valid accountId in path parameter returns direct-debits with Monthly frequency in response body (accountToTest: AccountIdWithDirectDebitMonthlyFrequency) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with direct-debits of Monthly frequencies |
DBT-020-010 | AIS_DD009 | accountToTest: AccountIdWithEmptyDirectDebits | Happy path - Succeeds if valid accountId provided in the path parameter which has a empty direct debits (accountToTest: AccountIdWithEmptyDirectDebits) | Valid accountId provided in the path parameter should return a 200 with an empty array if there are no direct-debits |
DBT-020-020 | AIS_DD010 | accountToTest: Missing_AccountId | Negative Test - Fails if accountToTest path parameter is missing (accountToTest: Missing_AccountId) | If accountToTest path parameter is missing, the API must return a 401 and an error body |
| AIS_DD011 | accountToTest: Invalid_Single_AccountId | Negative Test - Fails with 400 if accountId format is invalid (accountToTest: Invalid_Single_AccountId) | If the accountId format is invalid , the API must return a 400 and an error body |
DBT-020-040 | AIS_DD012 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing |
o3-api-uri | AIS_DD013 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is missing |
DBT-020-080 | AIS_DD014 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest: SampleAccount) | TThe operation must fail with a status code 400 and error body if the o3-api-operation header is missing |
| AIS_DD015 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing |
DBT-020-090 | AIS_DD016 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing |
DBT-020-030 | AIS_DD017 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header has an unexpected value |
| AIS_DD018 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is missing |
| AIS_DD019 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is missing |
| AIS_DD020 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is missing |
| AIS_DD021 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is missing |
| AIS_DD022 | accountToTest: SampleAccount | Negative Test - Fails if o3-aspsp-id has an invalid value (accountToTest: SampleAccount) | If o3-aspsp-id has an invalid value, the API must return a 400 and an error body |
| AIS_DD023 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier is not b64 encoded (accountToTest: SampleAccount) | If o3-psu-identifier is not b64 encoded, the API must return a 400 and an error body |
| AIS_DD024 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier does not evaluate to a json structure (accountToTest: SampleAccount) | If o3-psu-identifier does not evaluate to a json structure, the API must return a 400 and an error body |
| AIS_DD025 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier does not contain userId (accountToTest: SampleAccount) | If o3-psu-identifier does not contain userId, the API must return a 400 and an error body |
| AIS_DD026 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is having invalid value |
| AIS_DD027 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is having invalid value |
| AIS_DD028 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is having invalid value |
| AIS_DD029 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is having invalid value |
DBT-020-030 | AIS_DD030 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header is having invalid value |
DBT-020-090 | AIS_DD031 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is having invalid value |
DBT-020-080 | AIS_DD032 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-operation header is having invalid value |
o3-api-uri | AIS_DD033 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is having invalid value |
| AIS_DD034 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined (accountToTest: SampleAccount) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined, the API must return a 400 and an error body |
| AIS_DD035 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string (accountToTest: SampleAccount) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string, the API must return a 400 and an error body |
| get-products |
| ||
| AIS_P001 | accountToTest: NoAccount | Negative Test - Fails if accountIds path parameter is missing (accountToTest: NoAccount) | If accountIds path parameter is missing, the API must return a 401 and an error body |
| AIS_P002 | accountToTest: Invalid_Single_AccountId | Negative Test - Fails with 400 if accountId format is invalid (accountToTest: Invalid_Single_AccountId) (accountToTest: Invalid_Single_AccountId) | If the accountId format is invalid , the API must return a 400 and an error body |
| AIS_P003 | accountToTest: NoAccount | Negative Test - Mandatory field validation - Fail if both accountId and o3-psu-identifier are missing (accountToTest: NoAccount) | The operation must fail with a status of 400 if both the accountId path parameter and the o3-psu-identifier header parameter are missing |
PRD-010-040 | AIS_P004 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing |
PRD-010-070 | AIS_P005 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is missing |
PRD-010-080 | AIS_P006 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-operation header is missing |
| AIS_P007 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing |
PRD-010-090 | AIS_P008 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing |
PRD-010-030 | AIS_P009 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header has an unexpected value |
| AIS_P010 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is missing |
| AIS_P011 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is missing |
| AIS_P012 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is missing |
| AIS_P013 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is missing |
| AIS_P014 | accountToTest: Products_SampleAccount | Happy path - Succeeds if valid accountId provided in the path parameter which has products (accountToTest: Products_SampleAccount) | The operation must return a status code 200 and the products of the valid accountId |
| AIS_P015 | accountToTest: AccountIdWithEmptyProducts | Happy path - Succeeds valid accountId provided in the path parameter which has an empty products (accountToTest: AccountIdWithEmptyProducts) | The operation must return a status code 200 and an empty array if the accountId has no products |
| AIS_P016 | accountToTest: NoAccountId | Negative Test - Fails if accountId is missing in the path parameter (accountToTest: NoAccountId) | The operation must fail with a status code 400 if the accountId is missing in the path parameter |
| AIS_P017 | accountToTest: Invalid_Single_AccountId | Negative Test - Fails if accountId format is invalid (accountToTest: Invalid_Single_AccountId) | If the accountId format is invalid , the API must return a 400 and an error body |
| AIS_P018 | accountToTest: SampleAccount | Negative Test - Fails if o3-aspsp-id has an invalid value (accountToTest: SampleAccount) | If o3-aspsp-id has an invalid value, the API must return a 400 and an error body |
| AIS_P019 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier is not b64 encoded (accountToTest: SampleAccount) | If o3-psu-identifier is not b64 encoded, the API must return a 400 and an error body |
| AIS_P020 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier does not evaluate to a json structure (accountToTest: SampleAccount) | If o3-psu-identifier does not evaluate to a json structure, the API must return a 400 and an error body |
| AIS_P021 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier does not contain userId (accountToTest: SampleAccount) | If o3-psu-identifier does not contain userId, the API must return a 400 and an error body |
| AIS_P022 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is having invalid value |
| AIS_P023 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is having invalid value |
| AIS_P024 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is having invalid value |
| AIS_P025 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is having invalid value |
PRD-010-030 | AIS_P026 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header is having invalid value |
PRD-010-090 | AIS_P027 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is having invalid value |
PRD-010-080 | AIS_P028 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-operation header is having invalid value |
PRD-010-070 | AIS_P029 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is having invalid value |
| AIS_P030 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined (accountToTest: SampleAccount) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined, the API must return a 400 and an error body |
| AIS_P031 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string (accountToTest: SampleAccount) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string, the API must return a 400 and an error body |
| get-scheduled-payments |
| ||
FDP-020-010 | AIS_SP001 | accountToTest: Arrival_ScheduledPaymentType | Happy path - Succeeds if valid accountId in path parameter returns scheduled-payments with scheduled type Arrival in response body (accountToTest: Arrival_ScheduledPaymentType) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with a details of scheduled-payments having scheduled type is Arrival |
FDP-020-010 | AIS_SP002 | accountToTest: Execution_ScheduledPaymentType | Happy path - Succeeds if valid accountId in path parameter returns scheduled-payments with scheduled type Execution in response body (accountToTest: Execution_ScheduledPaymentType) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with a details of scheduled-payments having scheduled type is Execution |
| AIS_SP003 | accountToTest: Valid_ScheduledPayments_Accounts_List | Happy path - Validate the meta information about the pagination (accountToTest: Valid_ScheduledPayments_Accounts_List) | Returns a 200 status code with the specified number of accounts in each page and the meta information about the pagination |
FDP-020-010 | AIS_SP004 | accountToTest: IBAN_Identifications_ScheduledPayment | Happy path - Succeeds if valid accountId in path parameter returns scheduled-payments with correct creditor account identification IBAN (accountToTest: IBAN_Identifications_ScheduledPayment) | Valid accountId provided in the path parameter should return a 200 and the scheduled-payments must have the correct creditor account identification IBAN |
FDP-020-010 | AIS_SP005 | accountToTest: AccountNumber_Identifications_ScheduledPayment | Happy path - Succeeds if valid accountId in path parameter returns scheduled-payments with correct creditor account identification AccountNumber (accountToTest: AccountNumber_Identifications_ScheduledPayment) | Valid accountId provided in the path parameter should return a 200 and the scheduled-payments must have the correct creditor account identification AccountNumber |
FDP-020-010 | AIS_SP006 | accountToTest: AccountIdWithEmptyScheduledPayments | Happy path - Succeeds if valid accountId in path parameter returns no scheduled-payments (accountToTest: AccountIdWithEmptyScheduledPayments) | Valid accountId provided in the path parameter should return a 200 with an empty array if there are no scheduled-payments |
FDP-020-020 | AIS_SP007 | accountToTest: NoAccount | Negative Test - Fails if accountIds path parameter is missing (accountToTest: NoAccount) | If accountIds path parameter is missing, the API must return a 401 and an error body |
| AIS_SP008 | accountToTest: Invalid_Single_AccountId | Negative Test - Fails with 400 if accountId format is invalid (accountToTest: Invalid_Single_AccountId) | If the accountId format is invalid , the API must return a 400 and an error body |
FDP-020-050 | AIS_SP009 | accountToTest: NoAccount | Negative Test - Mandatory field validation - Fail if both accountId and o3-psu-identifier are missing (accountToTest: NoAccount) | The operation must fail with a status of 400 if both the accountId path parameter and the o3-psu-identifier header parameter are missing |
FDP-020-040 | AIS_SP010 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing |
FDP-020-070 | AIS_SP011 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is missing |
FDP-020-080 | AIS_SP012 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-operation header is missing |
| AIS_SP013 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing |
FDP-020-090 | AIS_SP014 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing |
FDP-020-030 | AIS_SP015 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header has an unexpected value |
| AIS_SP016 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is missing |
| AIS_SP017 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is missing |
| AIS_SP018 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is missing |
| AIS_SP019 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is missing |
| AIS_SP020 | accountToTest: SampleAccount | Negative Test - Fails if o3-aspsp-id has an invalid value (accountToTest: SampleAccount) | If o3-aspsp-id has an invalid value, the API must return a 400 and an error body |
| AIS_SP021 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier is not b64 encoded (accountToTest: SampleAccount) | If o3-psu-identifier is not b64 encoded, the API must return a 400 and an error body |
| AIS_SP022 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier does not evaluate to a json structure (accountToTest: SampleAccount) | If o3-psu-identifier does not evaluate to a json structure, the API must return a 400 and an error body |
| AIS_SP023 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier does not contain userId (accountToTest: SampleAccount) | If o3-psu-identifier does not contain userId, the API must return a 400 and an error body |
| AIS_SP024 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is having invalid value |
| AIS_SP025 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is having invalid value |
| AIS_SP026 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is having invalid value |
| AIS_SP027 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is having invalid value |
FDP-020-030 | AIS_SP028 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header is having invalid value |
FDP-020-090 | AIS_SP029 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is having invalid value |
FDP-020-080 | AIS_SP030 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-operation header is having invalid value |
FDP-020-070 | AIS_SP031 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is having invalid value |
| AIS_SP032 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined (accountToTest: SampleAccount) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined, the API must return a 400 and an error body |
| AIS_SP033 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string (accountToTest: SampleAccount) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string, the API must return a 400 and an error body |
| get-standing-orders |
| ||
STO-020-010 | AIS_SO001 | accountToTest: Active_StandingOrdersStatusCode | Happy path - Succeeds if valid accountId in path parameter returns standing-orders with Active status in response body (accountToTest: Active_StandingOrdersStatusCode) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with a details of standing-orders having status Active |
STO-020-010 | AIS_SO002 | accountToTest: Inactive_StandingOrdersStatusCode | Happy path - Succeeds if valid accountId in path parameter returns standing-orders with Inactive status in response body (accountToTest: Inactive_StandingOrdersStatusCode) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with a details of standing-orders having status Inactive |
| AIS_SO003 | accountToTest: Valid_StandingOrders_Accounts_List | Happy path - Validate the meta information about pagination (accountToTest: Valid_StandingOrders_Accounts_List) | Returns a 200 status code with the specified number of accounts in each page and the meta information about the pagination |
STO-020-010 | AIS_SO004 | accountToTest: BetweenMyAccounts_StandingOrder | Happy path - Succeeds if valid accountId in path parameter returns standing-orders of BetweenMyAccounts type (accountToTest: BetweenMyAccounts_StandingOrder) | Valid accountId provided in the path parameter should return a 200 and the standing-orders must have the correct standing-orders type BetweenMyAccounts in the response body |
STO-020-010 | AIS_SO005 | accountToTest: SameBankTransfer_StandingOrder | Happy path - Succeeds if valid accountId in path parameter returns standing-orders of SameBankTransfer type (accountToTest: SameBankTransfer_StandingOrder) | Valid accountId provided in the path parameter should return a 200 and the standing-orders must have the correct standing-orders type SameBankTransfer in the response body |
STO-020-010 | AIS_SO006 | accountToTest: LocalBankTransfer_StandingOrder | Happy path - Succeeds if valid accountId in path parameter returns standing-orders of LocalBankTransfer type (accountToTest: LocalBankTransfer_StandingOrder) | Valid accountId provided in the path parameter should return a 200 and the standing-orders must have the correct standing-orders type LocalBankTransfer in the response body |
STO-020-010 | AIS_SO007 | accountToTest: AccountIdWithEmptyStandingOrders | Happy path - Succeeds if valid accountId in path parameter returns no standing-orders (accountToTest: AccountIdWithEmptyStandingOrders) | Valid accountId provided in the path parameter should return a 200 with an empty array if there are no standing-orders |
STO-020-020 | AIS_SO008 |
| Negative Test - Fails if accountIds path parameter is missing | If accountIds path parameter is missing, the API must return a 401 and an error body |
| AIS_SO009 | accountToTest: Invalid_Single_AccountId | Negative Test - Fails with 400 if accountId format is invalid (accountToTest: Invalid_Single_AccountId) | If the accountId format is invalid , the API must return a 400 and an error body |
| AIS_SO010 | accountToTest: NoAccount | Negative Test - Mandatory field validation - Fail if both accountId and o3-psu-identifier are missing (accountToTest: NoAccount) | The operation must fail with a status of 400 if both the accountId path parameter and the o3-psu-identifier header parameter are missing |
STO-020-040 | AIS_SO011 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing |
STO-020-060 | AIS_SO012 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is missing |
STO-020-070 | AIS_SO013 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-operation header is missing |
| AIS_SO014 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing |
STO-020-080 | AIS_SO015 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing |
STO-020-030 | AIS_SO016 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header has an unexpected value |
| AIS_SO017 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is missing |
| AIS_SO018 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is missing |
| AIS_SO019 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is missing |
| AIS_SO020 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is missing |
| AIS_SO021 | accountToTest: SampleAccount | Negative Test - Fails if o3-aspsp-id has an invalid value (accountToTest: SampleAccount) | If o3-aspsp-id has an invalid value, the API must return a 400 and an error body |
| AIS_SO022 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier is not b64 encoded (accountToTest: SampleAccount) | If o3-psu-identifier is not b64 encoded, the API must return a 400 and an error body |
| AIS_SO023 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier does not evaluate to a json structure (accountToTest: SampleAccount) | If o3-psu-identifier does not evaluate to a json structure, the API must return a 400 and an error body |
| AIS_SO024 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier does not contain userId (accountToTest: SampleAccount) | If o3-psu-identifier does not contain userId, the API must return a 400 and an error body |
| AIS_SO025 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is having invalid value |
| AIS_SO026 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is having invalid value |
| AIS_SO027 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is having invalid value |
| AIS_SO028 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is having invalid value |
STO-020-030 | AIS_SO029 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header is having invalid value |
STO-020-080 | AIS_SO030 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is having invalid value |
STO-020-070 | AIS_SO031 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is having invalid value (accountToTest: SampleAccount) | TThe operation must fail with a status code 400 and error body if the o3-api-operation header is having invalid value |
STO-020-060 | AIS_SO032 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is having invalid value |
| AIS_SO033 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined (accountToTest: SampleAccount) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined, the API must return a 400 and an error body |
| AIS_SO034 | (accountToTest:: SampleAccount | Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string ((accountToTest:: SampleAccount) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string, the API must return a 400 and an error body |
| get-transactions |
| ||
TXN-020-010 | AIS_T001 | accountToTest: Transactions_SampleAccount | Happy Path - Succeeds if valid accountId in path parameter returns transactions (accountToTest: Transactions_SampleAccount) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with a list of transactions |
TXN-020-010 | AIS_T002 | accountToTest: AccountIdWithEmptyTransactions | Happy path - Succeeds if valid accountId in path parameter returns no transactions (accountToTest: AccountIdWithEmptyTransactions) | Valid accountId provided in the path parameter should return a 200 with an empty array if there are no transactions |
| AIS_T003 | accountToTest: Valid_Transactions_Accounts_List | Happy path - Succeeds with the specified number of accounts in each page and the meta information about the pagination (accountToTest: Valid_Transactions_Accounts_List) | Returns a 200 status code with the specified number of accounts in each page and the meta information about the pagination |
TXN-020-020 | AIS_T004 | accountToTest: SampleAccount | Negative Test - Fails if accountIds path parameter is missing (accountToTest: SampleAccount) | If accountIds path parameter is missing, the API must return a 401 and an error body |
| AIS_T005 | accountToTest: Invalid_Single_AccountId | Negative Test - Fails with 400 if accountId format is invalid (accountToTest: Invalid_Single_AccountId) | If the accountId format is invalid , the API must return a 400 and an error body |
TXN-020-050 | AIS_T006 | accountToTest: NoAccount | Negative Test - Mandatory field validation - Fail if both accountId and o3-psu-identifier are missing (accountToTest: NoAccount) | The operation must fail with a status of 400 if both the accountId path parameter and the o3-psu-identifier header parameter are missing |
TXN-020-040 | AIS_T007 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing |
TXN-020-070 | AIS_T008 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is missing |
TXN-020-080 | AIS_T009 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest: SampleAccount) | TThe operation must fail with a status code 400 and error body if the o3-api-operation header is missing |
| AIS_T010 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing |
TXN-020-090 | AIS_T011 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing |
TXN-020-030 | AIS_T012 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header has an unexpected value |
| AIS_T013 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is missing |
| AIS_T014 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is missing |
| AIS_T015 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is missing |
| AIS_T016 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is missing |
TXN-020-011 | AIS_T017 | accountToTest: Transactions_SampleAccount | Happy Path - Filter transactions based on fromBookingDateTime query param (accountToTest: Transactions_SampleAccount) | Returns a 200 with list of transactions from fromBookingDateTime until latest available transaction |
TXN-020-012 | AIS_T018 | accountToTest: Transactions_SampleAccount | Happy Path - Filter transactions based on toBookingDateTime query param (accountToTest: Transactions_SampleAccount) | Returns a 200 with list of transactions from the earliest available transaction till toBookingDateTime |
TXN-020-013 | AIS_T019 | accountToTest: Transactions_SampleAccount | Happy Path - Filter transactions based on fromBookingDateTime and toBookingDateTime query params (accountToTest: Transactions_SampleAccount) | Returns a 200 with list of transactions within fromBookingDateTime and toBookingDateTime query params |
| AIS_T020 | accountToTest: SampleAccount | Negative Test - Fails if o3-aspsp-id has an invalid value (accountToTest: SampleAccount) | If o3-aspsp-id has an invalid value, the API must return a 400 and an error body |
| AIS_T021 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier is not b64 encoded (accountToTest: SampleAccount) | If o3-psu-identifier is not b64 encoded, the API must return a 400 and an error body |
| AIS_T022 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier does not evaluate to a json structure (accountToTest: SampleAccount) | If o3-psu-identifier does not evaluate to a json structure, the API must return a 400 and an error body |
| AIS_T023 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier does not contain userId (accountToTest: SampleAccount) | If o3-psu-identifier does not contain userId, the API must return a 400 and an error body |
| AIS_T024 | accountToTest: SampleAccount | Negative Test - Fails if toBookingDateTime is before fromBookingDateTime (accountToTest: SampleAccount) | If toBookingDateTime is before fromBookingDateTime, the API must return a 400 and an error body |
| AIS_T025 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-consent-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-consent-id header is having invalid value |
| AIS_T026 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is having invalid value |
| AIS_T027 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-client-id header is having invalid value |
| AIS_T028 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-caller-org-id header is having invalid value |
TXN-020-030 | AIS_T029 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-provider-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-provider-id header is having invalid value |
TXN-020-090 | AIS_T030 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is having invalid value |
TXN-020-080 | AIS_T031 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-operation header is having invalid value (accountToTest: SampleAccount) | TThe operation must fail with a status code 400 and error body if the o3-api-operation header is having invalid value |
TXN-020-070 | AIS_T032 | accountToTest: SampleAccount | Negative Test - Mandatory header validation - Fail if o3-api-uri header is having invalid value (accountToTest: SampleAccount) | The operation must fail with a status code 400 and error body if the o3-api-uri header is having invalid value |
| AIS_T033 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined (accountToTest: SampleAccount) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined, the API must return a 400 and an error body |
| AIS_T034 | accountToTest: SampleAccount | Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string (accountToTest: SampleAccount) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string, the API must return a 400 and an error body |
| post-copquery |
| ||
| AIS_COPQ001 | accountToTest: confirmation-of-payee-query-retail-user | Happy Path - A valid request with schemeName as IBAN for retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 200 status code when all headers are valid and provides the associated customer details linked to the IBAN provided in the request for Retail user |
| AIS_COPQ002 | accountToTest: confirmation-of-payee-query-business-user | Happy Path - A valid request with schemeName as IBAN for business user (accountToTest: confirmation-of-payee-query-business-user) | Returns a 200 status code when all headers are valid and provides the associated customer details linked to the IBAN provided in the request for business user |
| AIS_COPQ003 | accountToTest: confirmation-of-payee-query-retail-user | Happy Path - A valid request with schemeName as IBAN for a Retail user and o3-psu-identifier and o3-consent-id are not provided as these fields are not mandatory (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 200 status code when all headers are valid and o3-psu-identifier and o3-consent-id headers are not provided in the request |
| AIS_COPQ004 | accountToTest: confirmation-of-payee-invalid-iban | Negative Test - A request with invalid IBAN for a Retail user (accountToTest: confirmation-of-payee-invalid-iban) | Returns a 200 with empty data array |
| AIS_COPQ005 | accountToTest: missing-firstname-confirmation-of-payee-query-retail-user | Negative Test - A request missing the firstName field for a retail user (accountToTest: missing-firstname-confirmation-of-payee-query-retail-user) | Returns a 400 status code when all headers are valid, but the request body is missing the firstName field |
| AIS_COPQ006 | accountToTest: missing-lastname-confirmation-of-payee-query-retail-user | Negative Test - A request missing the lastName field for a retail user (accountToTest: missing-lastname-confirmation-of-payee-query-retail-user) | Returns a 400 status code when all headers are valid, but the request body is missing the lastName field |
| AIS_COPQ007 | accountToTest: missing-businessName-confirmation-of-payee-query-business-user | Negative Test - A request missing the businessName field for a retail user (accountToTest: missing-businessName-confirmation-of-payee-query-business-user) | Returns a 400 status code when all headers are valid, but the request body is missing the businessName field |
CUS-010-030 | AIS_COPQ008 | accountToTest: confirmation-of-payee-query-retail-user | Negative Test - A request with mandatory missing headers o3-provider-id for a retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 400 status code when mandatory headers o3-provider-id is missing |
| AIS_COPQ009 | accountToTest: confirmation-of-payee-query-retail-user | Negative Test - A request with mandatory missing headers o3-aspsp-id for a retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 400 status code when mandatory headers o3-aspsp-id is missing |
| AIS_COPQ010 | accountToTest: confirmation-of-payee-query-retail-user | Negative Test - A request with mandatory missing headers o3-caller-org-id for a retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 400 status code when mandatory headers o3-caller-org-id is missing |
| AIS_COPQ011 | accountToTest: confirmation-of-payee-query-retail-user | Negative Test - A request with mandatory missing headers o3-caller-client-id for a retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 400 status code when mandatory headers o3-caller-client-id is missing |
| AIS_COPQ012 | accountToTest: confirmation-of-payee-query-retail-user | Negative Test - A request with mandatory missing headers o3-caller-software-statement-id for a retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 400 status code when mandatory headers o3-caller-software-statement-id is missing |
CUS-010-070 | AIS_COPQ013 | accountToTest: confirmation-of-payee-query-retail-user | Negative Test - A request with mandatory missing headers o3-api-uri for a retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 400 status code when mandatory headers o3-api-uri is missing |
CUS-010-080 | AIS_COPQ014 | accountToTest: confirmation-of-payee-query-retail-user | Negative Test - A request with mandatory missing headers o3-api-operation for a retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 400 status code when mandatory headers o3-api-operation is missing |
| AIS_COPQ015 | accountToTest: confirmation-of-payee-query-retail-user | Negative Test - A request with mandatory missing headers o3-caller-interaction-id for a retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 400 status code when mandatory headers o3-caller-interaction-id is missing |
CUS-010-090 | AIS_COPQ016 | accountToTest: confirmation-of-payee-query-retail-user | Negative Test - A request with mandatory missing headers o3-ozone-interaction-id for a retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 400 status code when mandatory headers o3-ozone-interaction-id is missing |
CUS-010-030 | AIS_COPQ017 | accountToTest: confirmation-of-payee-query-retail-user | Negative Test - A request with mandatory invalid headers value of o3-provider-id for a retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 400 status code when mandatory headers o3-provider-id is invalid |
| AIS_COPQ018 | accountToTest: confirmation-of-payee-query-retail-user | Negative Test - A request with mandatory invalid headers value of o3-aspsp-id for a retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 400 status code when mandatory headers o3-aspsp-id is invalid |
| AIS_COPQ019 | accountToTest: confirmation-of-payee-query-retail-user | Negative Test - A request with mandatory invalid headers value of o3-caller-org-id for a retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 400 status code when mandatory headers o3-caller-org-id is invalid |
| AIS_COPQ020 | accountToTest: confirmation-of-payee-query-retail-user | Negative Test - A request with mandatory invalid headers value of o3-caller-client-id for a retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 400 status code when mandatory headers o3-caller-client-id is invalid |
| AIS_COPQ021 | accountToTest: confirmation-of-payee-query-retail-user | Negative Test - A request with mandatory invalid headers value of o3-caller-software-statement-id for a retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 400 status code when mandatory headers o3-caller-software-statement-id is invalid |
CUS-010-070 | AIS_COPQ022 | accountToTest: confirmation-of-payee-query-retail-user | Negative Test - A request with mandatory invalid headers value of o3-api-uri for a retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 400 status code when mandatory headers o3-api-uri is invalid |
CUS-010-080 | AIS_COPQ023 | accountToTest: confirmation-of-payee-query-retail-user | Negative Test - A request with mandatory missing headers value of o3-api-operation for a retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 400 status code when mandatory headers o3-api-operation is invalid |
| AIS_COPQ024 | accountToTest: confirmation-of-payee-query-retail-user | Negative Test - A request with mandatory invalid headers value of o3-caller-interaction-id for a retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 400 status code when mandatory headers o3-caller-interaction-id is invalid |
CUS-010-090 | AIS_COPQ025 | accountToTest: confirmation-of-payee-query-retail-user | Negative Test - A request with mandatory invalid headers value of o3-ozone-interaction-id for a retail user (accountToTest: confirmation-of-payee-query-retail-user) | Returns a 400 status code when mandatory headers o3-ozone-interaction-id is invalid |
| AIS_COPQ026 |
| Negative Test - A request with missing mandatory page and page-size query parameter for a retail user | Returns a 400 status code when mandatory query parameters page and page-size are missing |
| augment |
| ||
| PIS_AUG001 | paymentToTest: event-AwaitingAuthorisation-for-fixed-defined-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing only the mandatory fields for fixed-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-fixed-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG002 | paymentToTest: event-AwaitingAuthorisation-for-fixed-defined-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for fixed-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-fixed-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG003 | paymentToTest: event-AwaitingAuthorisation-for-fixed-defined-schedule-retail-user | POST /augment : Verify that the endpoint throws error when mandatory fields are missing for fixed-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-fixed-defined-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_AUG004 | paymentToTest: event-AwaitingAuthorisation-for-variable-defined-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing only the mandatory fields for variable-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-variable-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG005 | paymentToTest: event-AwaitingAuthorisation-for-variable-defined-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for variable-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-variable-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG006 | paymentToTest: event-AwaitingAuthorisation-for-variable-defined-schedule-retail-user | POST /augment : Verify that the endpoint throws error when mandatory fields are missing for variable-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-variable-defined-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_AUG007 | paymentToTest: event-AwaitingAuthorisation-for-fixed-periodic-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing only the mandatory fields for fixed-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-fixed-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG008 | paymentToTest: event-AwaitingAuthorisation-for-fixed-periodic-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for fixed-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-fixed-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG009 | paymentToTest: event-AwaitingAuthorisation-for-fixed-periodic-schedule-retail-user | POST /augment : Verify that the endpoint throws error when mandatory fields are missing for fixed-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-fixed-periodic-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_AUG010 | paymentToTest: event-AwaitingAuthorisation-for-variable-periodic-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing only the mandatory fields for variable-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-variable-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG011 | paymentToTest: event-AwaitingAuthorisation-for-variable-periodic-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for variable-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-variable-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG012 | paymentToTest: event-AwaitingAuthorisation-for-variable-periodic-schedule-retail-user | POST /augment : Verify that the endpoint throws error when mandatory fields are missing for variable-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-variable-periodic-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_AUG013 | paymentToTest: event-AwaitingAuthorisation-for-fixed-on-demand-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing only the mandatory fields for fixed-on-demand (paymentToTest: event-AwaitingAuthorisation-for-fixed-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG014 | paymentToTest: event-AwaitingAuthorisation-for-fixed-on-demand-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for fixed-on-demand (paymentToTest: event-AwaitingAuthorisation-for-fixed-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG015 | paymentToTest: event-AwaitingAuthorisation-for-fixed-on-demand-retail-user | POST /augment : Verify that the endpoint throws error when mandatory fields are missing for fixed-on-demand (paymentToTest: event-AwaitingAuthorisation-for-fixed-on-demand-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_AUG016 | paymentToTest: event-AwaitingAuthorisation-for-variable-on-demand-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing only the mandatory fields for variable-on-demand (paymentToTest: event-AwaitingAuthorisation-for-variable-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG017 | paymentToTest: event-AwaitingAuthorisation-for-variable-on-demand-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for variable-on-demand (paymentToTest: event-AwaitingAuthorisation-for-variable-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG018 | paymentToTest: event-AwaitingAuthorisation-for-variable-on-demand-retail-user | POST /augment : Verify that the endpoint throws error when mandatory fields are missing for variable-on-demand (paymentToTest: event-AwaitingAuthorisation-for-variable-on-demand-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_AUG019 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-defined-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined FDP with fixed-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG020 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-defined-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined FDP with fixed-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG021 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-defined-schedule-retail-user | POST /augment : Verify that the endpoint throws error when mandatory fields are missing for combined FDP with fixed-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-defined-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_AUG022 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-defined-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined FDP with variable-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG023 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-defined-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined FDP with variable-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG024 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-defined-schedule-retail-user | POST /augment : Verify that the endpoint throws error when mandatory fields are missing for combined FDP with variable-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-defined-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_AUG025 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-periodic-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined FDP with fixed-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG026 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-periodic-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined FDP with fixed-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG027 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-periodic-schedule-retail-user | POST /augment : Verify that the endpoint throws error when mandatory fields are missing for combined FDP with fixed-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-periodic-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_AUG028 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-periodic-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined FDP with variable-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG029 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-periodic-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined FDP with variable-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG030 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-periodic-schedule-retail-user | POST /augment : Verify that the endpoint throws error when mandatory fields are missing for combined FDP with variable-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-periodic-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_AUG031 | paymentToTest: event-Authorized-for-CombinedFDP-fixed-on-demand-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined FDP with fixed-on-demand (paymentToTest: event-Authorized-for-CombinedFDP-fixed-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG032 | paymentToTest: event-Authorized-for-CombinedFDP-fixed-on-demand-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined FDP with fixed-on-demand (paymentToTest: event-Authorized-for-CombinedFDP-fixed-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG033 | paymentToTest: event-Authorized-for-CombinedFDP-fixed-on-demand-retail-user | POST /augment : Verify that the endpoint throws error when mandatory fields are missing for combined FDP with fixed-on-demand (paymentToTest: event-Authorized-for-CombinedFDP-fixed-on-demand-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_AUG034 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-on-demand-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined FDP with variable-on-demand (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG035 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-on-demand-retail-user | POST /augment : Happy Path -Succeeds with a valid request containing both mandatory and optional fields for combined FDP with variable-on-demand (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG036 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-on-demand-retail-user | POST /augment : Verify that the endpoint throws error when mandatory fields are missing for combined FDP with variable-on-demand (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-on-demand-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_AUG037 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-defined-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined SIP with fixed-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG038 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-defined-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined SIP with fixed-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG039 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-defined-schedule-retail-user | POST /augment : Verify that the endpoint throws error when mandatory fields are missing for combined SIP with fixed-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-defined-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_AUG040 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-defined-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined SIP with variable-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG041 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-defined-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined SIP with variable-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG042 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-defined-schedule-retail-user | POST /augment : Verify that the endpoint throws error when mandatory fields are missing for combined SIP with variable-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-defined-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_AUG043 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-periodic-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined SIP with fixed-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG044 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-periodic-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined SIP with fixed-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG045 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-periodic-schedule-retail-user | POST /augment : Verify that the endpoint throws error when mandatory fields are missing for combined SIP with fixed-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-periodic-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_AUG046 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-periodic-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined SIP with variable-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG047 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-periodic-schedule-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined SIP with variable-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG048 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-periodic-schedule-retail-user | POST /augment : Verify that the endpoint throws error when mandatory fields are missing for combined SIP with variable-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-periodic-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_AUG049 | paymentToTest: event-Authorized-for-CombinedSIP-fixed-on-demand-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined SIP with fixed-on-demand (paymentToTest: event-Authorized-for-CombinedSIP-fixed-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG050 | paymentToTest: event-Authorized-for-CombinedSIP-fixed-on-demand-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined SIP with fixed-on-demand (paymentToTest: event-Authorized-for-CombinedSIP-fixed-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG051 | paymentToTest: event-Authorized-for-CombinedSIP-fixed-on-demand-retail-user | POST /augment : Verify that the endpoint throws error when mandatory fields are missing for combined SIP with fixed-on-demand (paymentToTest: event-Authorized-for-CombinedSIP-fixed-on-demand-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_AUG052 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-on-demand-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined SIP with variable-on-demand (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG053 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-on-demand-retail-user | POST /augment : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined SIP with variable-on-demand (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_AUG054 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-on-demand-retail-user | POST /augment : Verify that the endpoint throws error when mandatory fields are missing for combined SIP with variable-on-demand (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-on-demand-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| combinedFDPWithFixedDefinedSchedule |
| ||
| PIS_Before_FDPFDS001 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-defined-schedule-retail-user | POST /event/post: Happy Path - Combined Future Dated Payment with a Fixed Defined Schedule for consent status AwaitingAuthorisation (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-defined-schedule-retail-user) | Ensure that Ozone sends a consent in an 'AwaitingAuthorisation' state to the LFI after calling the /event/post endpoint, resulting in a status code 204. |
| PIS_Before_FDPFDS002 | paymentToTest: event-Authorized-for-CombinedFDP-fixed-defined-schedule-retail-user | POST /event/patch: Happy Path - Verify the successful creation of an event when the consentStatus is set to Authorized for a predefined combined FDP with fixed defined schedule (paymentToTest: event-Authorized-for-CombinedFDP-fixed-defined-schedule-retail-user) | Ensure that Ozone sends a consent in an 'Authorized' state to the LFI after calling the /event/post endpoint, resulting in a status code 204. |
| PIS_FDPFDS003 | paymentToTest: CombinedFDP-fixed-defined-schedule-for-retail-user | POST /payment: Happy Path - Verify all mandatory and optional fields in the request body for a Combined Future Dated Payment with a Fixed Defined Schedule (paymentToTest: CombinedFDP-fixed-defined-schedule-for-retail-user) | The payment must be successfully created with a status code 201 upon successful operation. |
| PIS_After_FDPFDS004 | paymentToTest: event-Consumed-for-CombinedFDP-fixed-defined-schedule-retail-user | POST /event/patch: Happy Path - Combined Future Dated Payment with a Fixed Defined Schedule for consent status Consumed (paymentToTest: event-Consumed-for-CombinedFDP-fixed-defined-schedule-retail-user) | Ensure that Ozone sends a consent in a 'Consumed' state to the LFI after calling the /event/patch endpoint, resulting in a status code 204. |
| PIS_FDPFDS005 | paymentToTest: CombinedFDP-fixed-defined-schedule-for-retail-user | GET /payment: Happy Path - Verify retrieval for a valid paymentId in the path parameter for Combined Future Dated Payment with a Fixed Defined Schedule (paymentToTest: CombinedFDP-fixed-defined-schedule-for-retail-user) | A valid paymentId in the path parameter should return a status code 200, with the paymentId present in the response. |
| PIS_FDPFDS006 | paymentToTest: fixed-Defined-schedule | POST /event/patch: Negative Test - Verify that the endpoint throws error when mandatory fields are missing for Combined Future Dated Payment with a Fixed Defined Schedule (paymentToTest: fixed-Defined-schedule) | The operation must fail with a status code 400 due to missing mandatory fields. |
| combinedFDPWithFixedOnDemand |
| ||
| PIS_Before_FDPFOD001 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-on-demand-retail-user | POST /event/post: Happy Path - Combined Future Dated Payment with Fixed On Demand for consent status 'AwaitingAuthorisation' (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-on-demand-retail-user) | Verify that Ozone sends a consent in the 'AwaitingAuthorisation' state to the LFI after hitting the POST /event/post endpoint. The operation must succeed with a status code 204. |
| PIS_Before_FDPFOD002 | paymentToTest: event-Authorized-for-CombinedFDP-fixed-on-demand-retail-user | POST /event/patch: Happy Path - Verify the successful creation of an event when the consentStatus is set to Authorized for predefined combined FDP with fixed on demand (paymentToTest: event-Authorized-for-CombinedFDP-fixed-on-demand-retail-user) | Verify that Ozone sends a consent in the 'Authorized' state to the LFI after hitting the POST /event/post endpoint. The operation must succeed with a status code 204. |
| PIS_FDPFOD003 | paymentToTest: CombinedFDP-fixed-on-demand-for-retail-user | POST /payment: Happy Path - Verify all mandatory and optional request body fields for Combined Future Dated Payment with Fixed On Demand (paymentToTest: CombinedFDP-fixed-on-demand-for-retail-user) | Verify that the operation succeeds with a status code 201 when the payment is successfully created. |
| PIS_After_FDPFOD004 | paymentToTest: event-Consumed-for-CombinedFDP-fixed-on-demand-retail-user | POST /event/patch: Happy Path - Combined Future Dated Payment with Fixed On Demand for consent status 'Consumed' (paymentToTest: event-Consumed-for-CombinedFDP-fixed-on-demand-retail-user) | Verify that Ozone sends a consent in the 'Consumed' state to the LFI after hitting the POST /event/patch endpoint. The operation must succeed with a status code 204. |
| PIS_FDPFOD005 | paymentToTest: CombinedFDP-fixed-on-demand-for-retail-user | GET /payment: Happy Path - Verify response for a valid paymentId with Combined Future Dated Payment and Fixed On Demand (paymentToTest: CombinedFDP-fixed-on-demand-for-retail-user) | Verify that providing a valid paymentId in the path parameter returns a status code 200 and includes the paymentId in the response. |
| PIS_FDPFOD006 | paymentToTest: fixed-on-demand | POST /event/patch: Negative Test - Verify that the endpoint throws error when mandatory fields are missing for Combined Future Dated Payment with Fixed On Demand (paymentToTest: fixed-on-demand) | Verify that the operation fails with a status code 400 when only optional request fields are provided in the request body. |
| combinedFDPWithFixedPeriodicSchedule |
| ||
| PIS_Before_FDPFPS001 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-periodic-schedule-retail-user | POST /event/post: Happy Path - Combined Future Dated Payment with Fixed Periodic Schedule for Consent Status AwaitingAuthorisation (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-periodic-schedule-retail-user) | Ensure the LFI receives a consent in an AwaitingAuthorisation state after invoking the /event/post endpoint. The operation must succeed with a status code 204. |
| PIS_Before_FDPFPS002 | paymentToTest: event-Authorized-for-CombinedFDP-fixed-periodic-schedule-retail-user | POST /event/patch: Happy Path - Verify the successful creation of an event when the consentStatus is set to Authorized for predefined combined FDP with fixed periodic schedule (paymentToTest: event-Authorized-for-CombinedFDP-fixed-periodic-schedule-retail-user) | Ensure the LFI receives a consent in an Authorized state after invoking the /event/post endpoint. The operation must succeed with a status code 204. |
| PIS_FDPFPS003 | paymentToTest: CombinedFDP-fixed-periodic-schedule-for-retail-user | POST /payment: Happy Path - Verify All Mandatory and Optional Fields for Combined Future Dated Payment with Fixed Periodic Schedule (paymentToTest: CombinedFDP-fixed-periodic-schedule-for-retail-user) | Ensure the payment is successfully created using all mandatory and optional fields in the request body. The operation must succeed with a status code 201. |
| PIS_After_FDPFPS004 | paymentToTest: event-Consumed-for-CombinedFDP-fixed-periodic-schedule-retail-user | POST /event/patch: Happy Path - Combined Future Dated Payment with Fixed Periodic Schedule for consent status 'Consumed' (paymentToTest: event-Consumed-for-CombinedFDP-fixed-periodic-schedule-retail-user) | Ensure the LFI receives a consent in a Consumed state after invoking the /event/patch endpoint. The operation must succeed with a status code 204. |
| PIS_FDPFPS005 | paymentToTest: CombinedFDP-fixed-periodic-schedule-for-retail-user | GET /payment: Happy Path - Verify Valid paymentId for Combined Future Dated Payment with Fixed Periodic Schedule (paymentToTest: CombinedFDP-fixed-periodic-schedule-for-retail-user) | Ensure that providing a valid paymentId in the path parameter returns status code 200, with the paymentId present in the response. |
| PIS_FDPFPS006 | paymentToTest: fixed-periodic-schedule | POST /event/patch: Negative Test - Verify that the endpoint throws error when mandatory fields are missing for Combined Future Dated Payment with Fixed Periodic Schedule (paymentToTest: fixed-periodic-schedule) | Verify the operation fails with a status code 400 when only optional request fields are provided. |
| combinedFDPWithVariableDefinedSchedule |
| ||
| PIS_Before_FDPVDS001 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-defined-schedule-retail-user | POST /event/post: Happy Path - Combined Future Dated Payment with Variable Defined Schedule for Consent Status AwaitingAuthorisation (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-defined-schedule-retail-user) | Ensure a consent in the AwaitingAuthorisation state is sent to the LFI after invoking the /event/post endpoint. The operation must succeed with a status code 204. |
| PIS_Before_FDPVDS002 | paymentToTest: event-Authorized-for-CombinedFDP-variable-defined-schedule-retail-user | POST /event/patch: Happy Path - Verify the successful creation of an event when the consentStatus is set to Authorized for a predefined combined FDP with variable defined schedule (paymentToTest: event-Authorized-for-CombinedFDP-variable-defined-schedule-retail-user) | Ensure a consent in the Authorized state is sent to the LFI after invoking the /event/patch endpoint. The operation must succeed with a status code 204. |
| PIS_FDPVDS003 | paymentToTest: CombinedFDP-variable-defined-schedule-for-retail-user | POST /payment: Happy Path - Verify All Mandatory and Optional Fields for Combined Future Dated Payment with Variable Defined Schedule (paymentToTest: CombinedFDP-variable-defined-schedule-for-retail-user) | Ensure the payment is successfully created using all mandatory and optional fields in the request body. The operation must succeed with a status code 201. |
| PIS_After_FDPVDS004 | paymentToTest: event-Consumed-for-CombinedFDP-variable-defined-schedule-retail-user | POST /event/patch: Happy Path - Combined Future Dated Payment with Variable Defined Schedule for Consent Status Consumed (paymentToTest: event-Consumed-for-CombinedFDP-variable-defined-schedule-retail-user) | Ensure a consent in the Consumed state is sent to the LFI after invoking the /event/patch endpoint. The operation must succeed with a status code 204. |
| PIS_FDPVDS005 | paymentToTest: CombinedFDP-variable-defined-schedule-for-retail-user | GET /payment: Happy Path - Validate Payment Retrieval for Combined Future Dated Payment with Variable Defined Schedule including the paymentId in the response. (paymentToTest: CombinedFDP-variable-defined-schedule-for-retail-user) | Ensure that providing a valid paymentId in the path parameter returns status code 200, with the paymentId present in the response. |
| PIS_FDPVDS006 | paymentToTest: variable-Defined-Schedule | POST /event/patch: Negative Test - Verify that the endpoint throws error when mandatory fields are missing for Combined Future Dated Payment with Variable Defined Schedule (paymentToTest: variable-Defined-Schedule) | Verify that the operation returns a status code 400 when the request body contains only optional fields, ensuring proper validation for Combined Future Dated Payment with a Variable Defined Schedule. |
| combinedFDPWithVariableOnDemand |
| ||
| PIS_Before_FDPVOD001 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-on-demand-retail-user | POST /event/post: Happy Path - Combined Future Dated Payment with Fixed On Demand for Consent Status AwaitingAuthorisation (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-on-demand-retail-user) | Ensure that a consent in the AwaitingAuthorisation state is sent to the LFI after invoking the /event/post endpoint. The operation should succeed with a status code 204. |
| PIS_Before_FDPVOD002 | paymentToTest: event-Authorized-for-CombinedFDP-variable-on-demand-retail-user | POST /event/patch: Happy Path - Verify the successful creation of an event when the consentStatus is set to Authorized for a predefined combined FDP with variable on demand (paymentToTest: event-Authorized-for-CombinedFDP-variable-on-demand-retail-user) | Ensure that a consent in the Authorized state is sent to the LFI after invoking the /event/post endpoint. The operation should succeed with a status code 204. |
| PIS_FDPVOD003 | paymentToTest: CombinedFDP-variable-on-demand-for-retail-user | POST /payment: Happy Path - Verify All Mandatory and Optional Fields for Combined Future Dated Payment with Fixed On Demand (paymentToTest: CombinedFDP-variable-on-demand-for-retail-user) | Ensure the payment is successfully created with all mandatory and optional fields. The operation should return a status code 201 upon successful creation. |
| PIS_After_FDPVOD004 | paymentToTest: event-Consumed-for-CombinedFDP-variable-on-demand-retail-user | POST /event/patch: Happy Path - Combined Future Dated Payment with Fixed On Demand for Consent Status Consumed (paymentToTest: event-Consumed-for-CombinedFDP-variable-on-demand-retail-user) | Ensure that a consent in the Consumed state is sent to the LFI after invoking the /event/patch endpoint. The operation should succeed with a status code 204. |
| PIS_FDPVOD005 | paymentToTest: CombinedFDP-variable-on-demand-for-retail-user | GET /payment: Happy Path - Validate Payment Retrieval for Combined Future Dated Payment with Variable on demand including the paymentId in the response. (paymentToTest: CombinedFDP-variable-on-demand-for-retail-user) | Ensure that providing a valid paymentId in the path parameter returns a status code 200 and the paymentId is included in the response. |
| PIS_FDPVOD006 | paymentToTest: variable-on-demand | POST /event/patch: Negative Test - Verify that the endpoint throws error when mandatory fields are missing for Combined Future Dated Payment with Fixed On Demand (paymentToTest: variable-on-demand) | Ensure that the operation fails with a status code 400 when only optional fields are provided in the request body. |
| combinedFDPWithVariablePeriodicSchedule |
| ||
| PIS_Before_FDPVPS001 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-periodic-schedule-retail-user | POST /event/post: Happy Path - Combined future dated payment with variable Periodic Schedule for Consent Status AwaitingAuthorisation (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-periodic-schedule-retail-user) | Ozone sends a consent in an AwaitingAuthorisation state to the LFI after the consent/event/post endpoint is invoked. The operation should succeed with a status code 204. |
| PIS_Before_FDPVPS002 | paymentToTest: event-Authorized-for-CombinedFDP-variable-periodic-schedule-retail-user | POST /event/patch: Happy Path - Verify the successful creation of an event when the consentStatus is set to Authorized for a predefined combined FDP with variable periodic schedule (paymentToTest: event-Authorized-for-CombinedFDP-variable-periodic-schedule-retail-user) | Ozone sends a consent in an Authorized state to the LFI after the consent/event/post endpoint is invoked. The operation should succeed with a status code 204. |
| PIS_FDPVPS003 | paymentToTest:CombinedFDP-variable-periodic-schedule-for-retail-user | POST /payment: Happy Path - Verify with All Mandatory and Optional Request Body Fields for Combined future dated payment with variable Periodic Schedule (paymentToTest:CombinedFDP-variable-periodic-schedule-for-retail-user) (Mandatory+Optional) | The operation should succeed with a status code 201 if the payment is successfully created. |
| PIS_After_FDPVPS004 | paymentToTest: event-Consumed-for-CombinedFDP-variable-periodic-schedule-retail-user | POST /event/patch: Happy Path - Combined future dated payment with variable Periodic Schedule for Consent Status Consumed (paymentToTest: event-Consumed-for-CombinedFDP-variable-periodic-schedule-retail-user) | Ozone sends a consent in a Consumed state to the LFI after the consent/event/patch endpoint is invoked. The operation should succeed with a status code 204. |
| PIS_FDPVPS005 | paymentToTest:CombinedFDP-variable-periodic-schedule-for-retail-user | GET /payment: Happy Path - Verify for Valid paymentId in Path Parameter Returning Payments for Combined future dated payment with variable Periodic Schedule (paymentToTest:CombinedFDP-variable-periodic-schedule-for-retail-user) | A valid paymentId provided in the path parameter should return a status code 200, and the paymentId must be present in the response. |
| PIS_FDPVPS006 | Optional | POST /event/patch: Negative Test - Verify that the endpoint throws error when mandatory fields are missing for Combined future dated payment with variable Periodic Schedule (Optional) (paymentToTest: variable-periodic-schedule) | Ensure that the operation fails with a status code 400 when only optional fields are provided in the request body. |
| combinedSIPWithFixedDefinedSchedule |
| ||
| PIS_Before_SIPFDS001 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-defined-schedule-retail-user | POST /event/post : Happy Path : Combined Single Instant Payment with Fixed Defined Schedule for consent status AwaitingAuthorisation (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-defined-schedule-retail-user) | Ozone will send a consent in an AwaitingAuthorisation state to the LFI after the consent/event/post endpoint is hit. The operation must succeed with a status code 204. |
| PIS_Before_SIPFDS002 | paymentToTest: event-Authorized-for-CombinedSIP-fixed-defined-schedule-retail-user | POST /event/patch : Happy Path : Verify the successful creation of an event when the consentStatus is set to Authorized for a predefined combined SIP with fixed defined schedule (paymentToTest: event-Authorized-for-CombinedSIP-fixed-defined-schedule-retail-user) | Ozone will send a consent in an Authorized state to the LFI after the consent/event/post endpoint is hit. The operation must succeed with a status code 204. |
| PIS_SIPFDS003 | paymentToTest: CombinedSIP-fixed-defined-schedule-for-retail-user | POST /payment: Happy Path - Verify All Mandatory and Optional Request Body Fields for Combined Single Instant Payment with Fixed Defined Schedule (paymentToTest: CombinedSIP-fixed-defined-schedule-for-retail-user) | Ensure that the payment is successfully created when all mandatory and optional fields are provided for a combined single instant payment with a fixed defined schedule. The operation should return a status code 201 upon successful creation |
| PIS_After_SIPFDS004 | paymentToTest: event-Consumed-for-CombinedSIP-fixed-defined-schedule-retail-user | POST event/patch : Happy Path : Combined Single Instant Payment with Fixed Defined Schedule for consent status Consumed (paymentToTest: event-Consumed-for-CombinedSIP-fixed-defined-schedule-retail-user) | Ozone will send a consent in a Consumed state to the LFI after the consent/event/patch is hit. The operation must succeed with a status code 204. |
| PIS_SIPFDS005 | paymentToTest: CombinedSIP-fixed-defined-schedule-for-retail-user | GET /payment: Happy Path - Verify Valid paymentId in Path Parameter Returns Payment for Combined Single Instant Payment with Fixed Defined Schedule (paymentToTest: CombinedSIP-fixed-defined-schedule-for-retail-user) | Valid paymentId provided in the path parameter should return a status code 200, and the paymentId must be present in the response. |
| PIS_SIPFDS006 | paymentToTest: fixed-Defined-schedule | POST /event/patch: Negative Test - Verify that the endpoint throws error when mandatory fields are missing for Combined Single Instant Payment with Fixed Defined Schedule (paymentToTest: fixed-Defined-schedule) | The operation should fail with a status code 400 when the request body contains only optional fields. |
| combinedSIPWithFixedOnDemand |
| ||
| PIS_Before_SIPFOD001 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-on-demand-retail-user | POST /event/post: Happy Path - Combined Single Instant Payment with Fixed On Demand and Consent Status AwaitingAuthorisation (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-on-demand-retail-user) | Ozone will send a consent in the AwaitingAuthorisation state to the LFI after hitting the consent/event/post endpoint. The operation should succeed with a status code 204. |
| PIS_Before_SIPFOD002 | paymentToTest: event-Authorized-for-CombinedSIP-fixed-on-demand-retail-user | POST /event/patch: Happy Path - Verify the successful creation of an event when the consentStatus is set to Authorized for predefined combined SIP with fixed on demand (paymentToTest: event-Authorized-for-CombinedSIP-fixed-on-demand-retail-user) | Ozone will send a consent in the Authorized state to the LFI after hitting the consent/event/post endpoint. The operation should succeed with a status code 204. |
| PIS_SIPFOD003 | paymentToTest: CombinedSIP-fixed-on-demand-for-retail-user | POST /payment: Happy Path - Verify the inclusion of all mandatory and optional request body fields for Combined Single Instant Payment with Fixed On Demand (paymentToTest: CombinedSIP-fixed-on-demand-for-retail-user) | The operation should succeed with a status code 201 if the payment is successfully created with all mandatory and optional fields. |
| PIS_After_SIPFOD004 | paymentToTest: event-Consumed-for-CombinedSIP-fixed-on-demand-retail-user | POST /event/patch: Happy Path - Combined Single Instant Payment with Fixed On Demand and Consent Status Consumed (paymentToTest: event-Consumed-for-CombinedSIP-fixed-on-demand-retail-user) | Ozone will send a consent in the Consumed state to the LFI after hitting the consent/event/patch endpoint. The operation should succeed with a status code 204. |
| PIS_SIPFOD005 | paymentToTest: CombinedSIP-fixed-on-demand-for-retail-user | GET /payment: Happy Path - Verify that a valid paymentId in the path parameter returns payments for Combined Single Instant Payment with Fixed On Demand (paymentToTest: CombinedSIP-fixed-on-demand-for-retail-user) | A valid paymentId in the path parameter should return a status code 200, and the paymentId must be included in the response. |
| PIS_SIPFOD006 | paymentToTest: fixed-on-demand | POST /event/patch: Negative Test - Verify that the endpoint throws error when mandatory fields are missing for Combined Single Instant Payment with Fixed On Demand (paymentToTest: fixed-on-demand) | The operation should fail with a status code 400 when the request body contains only optional fields and no mandatory fields. |
| combinedSIPWithFixedPeriodicSchedule |
| ||
| PIS_Before_SIPFPS001 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-periodic-schedule-retail-user | POST /event/post: Happy Path - Combined Single Instant Payment with Fixed Periodic Schedule for Consent Status AwaitingAuthorisation (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-periodic-schedule-retail-user) | Ozone sends a consent in an AwaitingAuthorisation state to the LFI after the consent/event/post endpoint is invoked. The operation should succeed with a status code 204. |
| PIS_Before_SIPFPS002 | paymentToTest: event-Authorized-for-CombinedSIP-fixed-periodic-schedule-retail-user | POST /event/patch: Happy Path - Verify the successful creation of an event when the consentStatus is set to Authorized for a predefined combined SIP with fixed periodic schedule (paymentToTest: event-Authorized-for-CombinedSIP-fixed-periodic-schedule-retail-user) | Ozone sends a consent in an Authorized state to the LFI after the consent/event/post endpoint is invoked. The operation should succeed with a status code 204. |
| PIS_SIPFPS003 | paymentToTest: CombinedSIP-fixed-periodic-schedule-for-retail-user | POST /payment: Happy Path - Verify All Mandatory and Optional Request Body Fields for Combined Single Instant Payment with Fixed Periodic Schedule (paymentToTest: CombinedSIP-fixed-periodic-schedule-for-retail-user) | The operation should succeed with a status code 201 if the payment is created successfully. |
| PIS_After_SIPFPS004 | paymentToTest: event-Consumed-for-CombinedSIP-fixed-periodic-schedule-retail-user | POST /event/patch: Happy Path - Combined Single Instant Payment with Fixed Periodic Schedule for Consent Status Consumed (paymentToTest: event-Consumed-for-CombinedSIP-fixed-periodic-schedule-retail-user) | Ozone sends a consent in a Consumed state to the LFI after the consent/event/patch endpoint is invoked. The operation should succeed with a status code 204. |
| PIS_SIPFPS005 | paymentToTest: CombinedSIP-fixed-periodic-schedule-for-retail-user | GET /payment: Happy Path - Verify that a valid paymentId in the path parameter returns payments for a combined single instant payment with a fixed periodic schedule (paymentToTest: CombinedSIP-fixed-periodic-schedule-for-retail-user) | A valid paymentId provided in the path parameter should return a status code of 200, and the paymentId must be included in the response |
| PIS_SIPFPS006 | paymentToTest: fixed-periodic-schedule | POST /event/patch: Negative Test - Verify that the endpoint throws error when mandatory fields are missing for Combined Single Instant Payment with Fixed Periodic Schedule (paymentToTest: fixed-periodic-schedule) | The operation should return a status code of 400 when only optional request fields are included. |
| combinedSIPWithVariableDefinedSchedule |
| ||
| PIS_Before_SIPVDS001 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-defined-schedule-retail-user | POST /event/post: Happy Path - Combined Single Instant Payment with Fixed Defined Schedule for Consent Status AwaitingAuthorisation (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-defined-schedule-retail-user) | Ozone will send a consent with an AwaitingAuthorisation status to the LFI after hitting the consent/event/post endpoint. The operation should succeed with a status code 204. |
| PIS_Before_SIPVDS002 | paymentToTest: event-Authorized-for-CombinedSIP-variable-defined-schedule-retail-user | POST /event/patch: Happy Path - Verify the successful creation of an event when the consentStatus is set to Authorized for a predefined combined SIP with variable defined schedule (paymentToTest: event-Authorized-for-CombinedSIP-variable-defined-schedule-retail-user) | Ozone will send a consent with an Authorized status to the LFI after hitting the consent/event/patch endpoint. The operation should succeed with a status code 204. |
| PIS_SIPVDS003 | paymentToTest: CombinedSIP-variable-defined-schedule-for-retail-user | POST /payment: Happy Path - Validate All Mandatory and Optional Request Body Fields for Combined Single Instant Payment with Fixed Defined Schedule (paymentToTest: CombinedSIP-variable-defined-schedule-for-retail-user) | The operation should succeed with a status code 201 if the payment is created successfully. |
| PIS_After_SIPVDS004 | paymentToTest: event-Consumed-for-CombinedSIP-variable-defined-schedule-retail-user | POST /event/patch: Happy Path - Combined Single Instant Payment with Fixed Defined Schedule for Consent Status Consumed (paymentToTest: event-Consumed-for-CombinedSIP-variable-defined-schedule-retail-user) | Ozone will send a consent with a Consumed status to the LFI after hitting the consent/event/patch endpoint. The operation should succeed with a status code 204. |
| PIS_SIPVDS005 | paymentToTest: CombinedSIP-variable-defined-schedule-for-retail-user | GET /payment: Happy Path - Verify that a Valid paymentId in the Path Parameter Returns the Correct Payment for Combined Single Instant Payment with a Fixed Defined Schedule (paymentToTest: CombinedSIP-variable-defined-schedule-for-retail-user) | Providing a valid paymentId in the path parameter should return a status code 200, and the paymentId must be present in the response. |
| PIS_SIPVDS006 | paymentToTest: variable-Defined-Schedule | POST /event/patch: Negative Test - Verify that the endpoint throws error when mandatory fields are missing for Combined Single Instant Payment with Fixed Defined Schedule (paymentToTest: variable-Defined-Schedule) | The operation must fail with a status code 400 when the request body contains only optional fields. |
| combinedSIPWithVariableOnDemand |
| ||
| PIS_Before_SIPVOD001 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-on-demand-retail-user | POST /event/post : Happy Path : Combined Single Instant Payment with Variable On Demand for consent status AwaitingAuthorisation (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-on-demand-retail-user) | Ozone will send a consent in an AwaitingAuthorisation state to the LFI after the consent/event/post endpoint is hit. The operation must succeed with a status code 204. |
| PIS_Before_SIPVOD002 | paymentToTest: event-Authorized-for-CombinedSIP-variable-on-demand-retail-user | POST /event/patch : Happy Path : Verify the successful creation of an event when the consentStatus is set to Authorized for predefined combined SIP with variable on demand (paymentToTest: event-Authorized-for-CombinedSIP-variable-on-demand-retail-user) | Ozone will send a consent in an Authorized state to the LFI after the consent/event/post endpoint is hit. The operation must succeed with a status code 204. |
| PIS_SIPVOD003 | paymentToTest: CombinedSIP-variable-on-demand-for-retail-user | POST /payment: Happy Path - Verify All Mandatory and Optional Request Body Fields for Combined Single Instant Payment with Variable On Demand (paymentToTest: CombinedSIP-variable-on-demand-for-retail-user) | The operation must succeed with a status code 201 if the payment is successfully created. |
| PIS_After_SIPVOD004 | paymentToTest: event-Consumed-for-CombinedSIP-variable-on-demand-retail-user | POST event/patch : Happy Path : Combined Single Instant Payment with Variable On Demand for consent status Consumed (paymentToTest: event-Consumed-for-CombinedSIP-variable-on-demand-retail-user) | Ozone will send a consent in a Consumed state to the LFI after the consent/event/patch is hit. The operation must succeed with a status code 204. |
| PIS_SIPVOD005 | paymentToTest: CombinedSIP-variable-on-demand-for-retail-user | GET /payment: Happy Path - Verify that a valid paymentId in the path parameter returns the payment details for Combined Single Instant Payment with Variable On Demand (paymentToTest: CombinedSIP-variable-on-demand-for-retail-user) | Valid paymentId provided in the path parameter should return a status code 200, and the paymentId must be present in the response. |
| PIS_SIPVOD006 | paymentToTest: variable-on-demand | POST /event/patch: Negative Test - Verify that the endpoint throws error when mandatory fields are missing for Combined Single Instant Payment with Variable On Demand (paymentToTest: variable-on-demand) | The operation must fail with a status code 400 when only optional request fields are provided. |
| combinedSIPWithVariablePeriodicSchedule |
| ||
| PIS_Before_SIPVPS001 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-periodic-schedule-retail-user | POST /event/post: Happy Path - Combined Single Instant Payment with variable Periodic Schedule for Consent Status AwaitingAuthorisation (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-periodic-schedule-retail-user) | Ozone sends a consent in an AwaitingAuthorisation state to the LFI after the consent/event/post endpoint is invoked. The operation should succeed with a status code 204. |
| PIS_Before_SIPVPS002 | paymentToTest: event-Authorized-for-CombinedSIP-variable-periodic-schedule-retail-user | POST /event/patch: Happy Path - Verify the successful creation of an event when the consentStatus is set to Authorized for a predefined combined SIP with variable periodic schedule (paymentToTest: event-Authorized-for-CombinedSIP-variable-periodic-schedule-retail-user) | Ozone sends a consent in an Authorized state to the LFI after the consent/event/post endpoint is invoked. The operation should succeed with a status code 204. |
| PIS_SIPVPS003 | paymentToTest: CombinedSIP-variable-periodic-schedule-for-retail-user | POST /payment: Happy Path - Verify All Mandatory and Optional Request Body Fields for Combined Single Instant Payment with Variable Periodic Schedule (paymentToTest: CombinedSIP-variable-periodic-schedule-for-retail-user) | The operation should succeed with a status code 201 if the payment is successfully created. |
| PIS_After_SIPVPS004 | paymentToTest: event-Consumed-for-CombinedSIP-variable-periodic-schedule-retail-user | POST /event/patch: Happy Path - VCombined Single Instant Payment with variable Periodic Schedule for Consent Status Consumed (paymentToTest: event-Consumed-for-CombinedSIP-variable-periodic-schedule-retail-user) | Ozone sends a consent in a Consumed state to the LFI after the consent/event/patch endpoint is invoked. The operation should succeed with a status code 204. |
| PIS_SIPVPS005 | paymentToTest: CombinedSIP-variable-periodic-schedule-for-retail-user | GET /payment: Happy Path - Verify Valid paymentId in Path Parameter Returns Payments for Combined Single Instant Payment with Variable Periodic Schedule (paymentToTest: CombinedSIP-variable-periodic-schedule-for-retail-user) | A valid paymentId provided in the path parameter should return a status code 200, and the paymentId must be present in the response. |
| PIS_SIPVPS006 | paymentToTest: variable-periodic-schedule | POST /event/patch: Negative Test - Verify that the endpoint throws error when mandatory fields are missing for Combined Single Instant Payment with Variable Periodic Schedule (paymentToTest: variable-periodic-schedule) | The operation should fail with a status code 400 when only optional request fields are provided. |
| fixed-defined-schedule |
| ||
| Before_FDS001 | paymentToTest: event-AwaitingAuthorization-for-fixed-defined-schedule-retail-user | POST /event/post: Happy Path - Verify all mandatory request body fields with consent status AwaitingAuthorization for Fixed Defined Schedule (paymentToTest: event-AwaitingAuthorization-for-fixed-defined-schedule-retail-user) | Ozone will be sending an consent in an AwaitingAuthorization state to the LFI after the consent/event/post endpoint is hit. |
| Before_FDS002 | paymentToTest: event-Authorized-for-fixed-defined-schedule-retail-user | POST event/patch : Happy Path : Verify the successful creation of an event when the consentStatus is set to Authorized for a predefined Fixed Defined Schedule (paymentToTest: event-Authorized-for-fixed-defined-schedule-retail-user) | Ozone will be sending an consent in an Authorized state to the LFI after the consent/event/patch is hit. |
| PIS_FDS003 | paymentToTest: fixed-defined-schedule-for-retail-user | POST /payment: Happy Path - Verify all mandatory and optional request body fields for Fixed Defined Schedule (paymentToTest: fixed-defined-schedule-for-retail-user) | The operartion must succeed with a status code 201 if the payment is successfully created |
| After_FDS004 | paymentToTest: event-Consumed-for-fixed-defined-schedule-retail-user | POST event/patch : Happy Path : Verify all mandatory request body fields with consent status Consumed for Fixed Defined Schedule (paymentToTest: event-Consumed-for-fixed-defined-schedule-retail-user) | Ozone will be sending an consent in a Consumed state to the LFI after the consent/event/patch is hit. |
| PIS_FDS005 | paymentToTest: fixed-defined-schedule-for-retail-user | GET /payment: Happy Path - Verify that a valid paymentId in the path parameter returns the correct payment for Fixed Defined Schedule (paymentToTest: fixed-defined-schedule-for-retail-user) | A valid paymentId provided in the path parameter should return a status code 200, and the paymentId must be included in the response |
| PIS_FDS006 | paymentToTest: fixed-Defined-Schedule | POST /event/patch: Negative Test - Verify that the endpoint throws error when mandatory fields are missing for Fixed Defined Schedule (paymentToTest: fixed-Defined-Schedule) | The operation must fail with a status code 400 when the request body contains only optional fields. |
| fixed-on-demand |
| ||
| Before_FOD001 | paymentToTest: event-AwaitingAuthorization-for-fixed-on-demand-retail-user | POST /event/post: Happy Path - Verify all mandatory request body fields with consent status AwaitingAuthorization for Fixed On Demand (paymentToTest: event-AwaitingAuthorization-for-fixed-on-demand-retail-user) | Ozone will be sending an consent in an AwaitingAuthorization state to the LFI after the consent/event/post endpoint is hit. |
| Before_FOD002 | paymentToTest: event-Authorized-for-fixed-on-demand-retail-user | POST event/patch : Happy Path : Verify the successful creation of an event when the consentStatus is set to Authorized for a predefined Fixed On Demand (paymentToTest: event-Authorized-for-fixed-on-demand-retail-user) | Ozone will be sending an consent in an Authorized state to the LFI after the consent/event/patch is hit. |
| PIS_FOD003 | paymentToTest: fixed-on-demand-for-retail-user | POST /payment: Happy Path - Verify all mandatory and optional request body fields for Fixed On Demand (paymentToTest: fixed-on-demand-for-retail-user) | The operartion must succeed with a status code 201 if the payment is successfully created |
| After_FOD004 | paymentToTest: event-Consumed-for-fixed-on-demand-retail-user | POST event/patch : Happy Path : Verify all mandatory request body fields with consent status consumed for Fixed On Demand (paymentToTest: event-Consumed-for-fixed-on-demand-retail-user) | Ozone will send a consent in a Consumed state to the LFI after the consent/event/patch endpoint is hit. |
| PIS_FOD005 | paymentToTest: fixed-on-demand-for-retail-user | GET /payement: Happy Path - Verify for valid paymentId in path parameter returns payments for fixed on demand (paymentToTest: fixed-on-demand-for-retail-user) | A valid paymentId provided in the path parameter should return a status code 200, and the paymentId must be present in the response |
| PIS_FOD006 | paymentToTest: fixed-on-demand | POST /event/patch: Negative Test - Verify that the endpoint throws error when mandatory fields are missing for Fixed On Demand (paymentToTest: fixed-on-demand) | The operation must fail with a status code 400 when the request body contains only optional fields. |
| fixed-periodic-schedule |
| ||
| Before_FPS001 | paymentToTest: event-AwaitingAuthorisation-for-fixed-periodic-schedule-retail-user | POST /event/post: Happy Path - Verify all mandatory request body fields with consent status AwaitingAuthorization for Fixed Periodic Schedule (paymentToTest: event-AwaitingAuthorisation-for-fixed-periodic-schedule-retail-user) | Ozone will send a consent in an AwaitingAuthorization state to the LFI after the consent/event/post endpoint is hit.. |
| Before_FPS002 | paymentToTest: event-Authorized-for-fixed-periodic-schedule-retail-user | POST /event/patch: Happy Path - Verify the successful creation of an event when the consentStatus is set to Authorized for a predefined Fixed Periodic Schedule (paymentToTest: event-Authorized-for-fixed-periodic-schedule-retail-user) | Ozone will send a consent in an Authorized state to the LFI after the consent/event/patch endpoint is hit |
| PIS_FPS003 | paymentToTest: fixed-periodic-schedule-for-retail-user | POST /payment: Happy Path - Verify all mandatory and optional request body fields for Fixed Periodic Schedule (paymentToTest: fixed-periodic-schedule-for-retail-user) | The operation must succeed with a status code 201 if the payment is successfully created |
| After_FPS004 | paymentToTest: event-Consumed-for-fixed-periodic-schedule-retail-user | POST /event/patch: Happy Path - Verify all mandatory request body fields with consent status Consumed for Fixed Periodic Schedule (paymentToTest: event-Consumed-for-fixed-periodic-schedule-retail-user) | Ozone will send a consent in a Consumed state to the LFI after the consent/event/patch endpoint is hit |
| PIS_FPS005 | paymentToTest: fixed-periodic-schedule-for-retail-user | GET /payment: Happy Path - Verify that a valid paymentId in the path parameter returns payments for a Fixed Periodic Schedule (paymentToTest: fixed-periodic-schedule-for-retail-user) | A valid paymentId provided in the path parameter should return a status code 200, and the paymentId must be present in the response. |
| PIS_FPS006 | paymentToTest: fixed-periodic-schedule | POST /event/patch: Negative Test - Verify that the endpoint throws error when mandatory fields are missing for Fixed Periodic Schedule (paymentToTest: fixed-periodic-schedule) | The operation must fail with a status code 400 when the request body contains only optional fields |
| future-dated-payments |
| ||
| PIS_FDP001 | paymentToTest: future-dated-payment-for-retail | POST : Happy Path - Future dated payments for retail user(paymentToTest: future-dated-payment-for-retail) | The operartion must succeed with a status code 201 if the payment is successfully created |
| PIS_FDP002 | paymentToTest: future-dated-payment-for-retail | GET : Happy Path - Succeeds if valid paymentId in path parameter returns payments (paymentToTest: future-dated-payment-for-retail) | Valid paymentId provided in the path parameter should return a 200 and the paymentId must be present in the response |
| PIS_FDP003 | paymentToTest : future-dated-payment-for-SME | POST : Happy Path - Future Dated payments (paymentToTest : future-dated-payment-for-SME) | The operartion must succeed with a status code 201 if the payment is successfully created |
| PIS_FDP004 | paymentToTest : future-dated-payment-for-SME | GET : Happy Path - Succeeds if valid paymentId in path parameter returns payments (paymentToTest : future-dated-payment-for-SME) | Valid paymentId provided in the path parameter should return a 200 and the paymentId must be present in the response |
| PIS_FDP005 | paymentToTest: future-dated-payment-for-corporate | POST : Happy Path - Future dated payments for coporate user (paymentToTest: future-dated-payment-for-corporate) | The operartion must succeed with a status code 201 if the payment is successfully created |
| PIS_FDP006 | paymentToTest: future-dated-payment-for-corporate | GET : Happy Path - Succeeds if valid paymentId in path parameter returns payments (paymentToTest: future-dated-payment-for-corporate) | Valid paymentId provided in the path parameter should return a 200 and the paymentId must be present in the response |
| PIS_FDP007 | paymentToTest : Sample_FDP_Valid_PaymentIds_AcceptedSettlementCompleted | GET : Happy Path - Succeeds if valid paymentId in path parameter returns payments with status AcceptedSettlementCompleted (paymentToTest : Sample_FDP_Valid_PaymentIds_AcceptedSettlementCompleted) | Valid paymentId provided in the path parameter should returns a 200 with status 'AcceptedSettlementCompleted' in response |
| PIS_FDP008 | paymentToTest : Sample_FDP_Valid_PaymentIds_AcceptedCreditSettlementCompleted | GET : Happy Path - Succeeds if valid paymentId in path parameter returns payments with status AcceptedCreditSettlementCompleted (paymentToTest : Sample_FDP_Valid_PaymentIds_AcceptedCreditSettlementCompleted) | Valid paymentId provided in the path parameter should returns a 200 with status 'AcceptedSettlementCompleted' in response |
| PIS_FDP009 | paymentToTest : Sample_FDP_Valid_PaymentIds_AcceptedWithoutPosting | GET : Happy Path - Succeeds if valid paymentId in path parameter returns payments with status AcceptedWithoutPosting (paymentToTest : Sample_FDP_Valid_PaymentIds_AcceptedWithoutPosting) | Valid paymentId provided in the path parameter should returns a 200 with status 'AcceptedSettlementCompleted' in response |
| PIS_FDP010 | paymentToTest : Sample_FDP_Valid_PaymentIds_Rejected | GET : Happy Path - Succeeds if valid paymentId in path parameter returns payments with status Rejected (paymentToTest : Sample_FDP_Valid_PaymentIds_Rejected) | Valid paymentId provided in the path parameter should returns a 200 with status 'AcceptedSettlementCompleted' in response |
| get-report-file-payments |
| ||
| PIS_RFP001 | paymentToTest: SamplePaymentId_ReportFile | GET : Happy Path - Succeeds if valid paymentId in path parameter returns file name (paymentToTest: SamplePaymentId_ReportFile) | Valid paymentId provided in the path parameter should return a 200 and the file name must be present in the response |
| PIS_RFP002 | paymentToTest: InvalidPaymentId_ReportFile | GET : Negative Test - Invalid paymentId in path parameter (paymentToTest: InvalidPaymentId_ReportFile) | Invalid paymentId provided in the path parameter should return a 400 status code |
| PIS_RFP003 | paymentToTest: NoPaymentIds | GET : Negative Test - Fail if paymentId in path parameter is missing (paymentToTest: NoPaymentIds) | The paymentId in the path parameter is missing, should return a 400 status code |
| header-validation |
| ||
| PIS_H_001 | paymentToTest: future-dated-payment-for-retail | GET : Get : Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (paymentToTest: future-dated-payment-for-retail | The operation must fail with a status code 400 if the o3-api-uri header is missing |
| PIS_H_002 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (paymentToTest: future-dated-payment-for-retail) | The operation must fail with a status code 400 if the o3-psu-identifier header is missing |
| PIS_H_003 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (paymentToTest: future-dated-payment-for-retail) | TThe operation must fail with a status code 400 if the o3-api-operation header is missing |
| PIS_H_004 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (paymentToTest: future-dated-payment-for-retail) | The operation must fail with a status code 400 if the o3-aspsp-id header is missing |
| PIS_H_005 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (paymentToTest: future-dated-payment-for-retail) | The operation must fail with a status code 400 if the o3-ozone-interaction-id header is missing |
| PIS_H_006 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (paymentToTest: future-dated-payment-for-retail) | The operation must fail with a status code 400 if the o3-provider-id header has an unexpected value |
| PIS_H_007 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (paymentToTest: future-dated-payment-for-retail) | The operation must fail with a status code 400 if the o3-caller-org-id header is missing |
| PIS_H_008 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (paymentToTest: future-dated-payment-for-retail) | The operation must fail with a status code 400 if the o3-caller-client-id header is missing |
| PIS_H_009 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (paymentToTest: future-dated-payment-for-retail) | The operation must fail with a status code 400 if the o3-caller-software-statement-id header is missing |
| PIS_H_010 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (paymentToTest: future-dated-payment-for-retail) | The operation must fail with a status code 400 if the o3-consent-id header is missing |
| PIS_H_011 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-consent-id header is having invalid value (paymentToTest: future-dated-payment-for-retail) | The operation must fail with a status code 400 if the o3-consent-id header is having invalid value |
| PIS_H_012 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is having invalid value (paymentToTest: future-dated-payment-for-retail) | The operation must fail with a status code 400 if the o3-caller-software-statement-id header is having invalid value |
| PIS_H_013 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is having invalid value (paymentToTest: future-dated-payment-for-retail) | The operation must fail with a status code 400 if the o3-caller-client-id header is having invalid value |
| PIS_H_014 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is having invalid value (paymentToTest: future-dated-payment-for-retail) | The operation must fail with a status code 400 if the o3-caller-org-id header is having invalid value |
| PIS_H_015 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-provider-id header is having invalid value (paymentToTest: future-dated-payment-for-retail) | The operation must fail with a status code 400 if the o3-provider-id header is having invalid value |
| PIS_H_016 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is having invalid value (paymentToTest: future-dated-payment-for-retail) | The operation must fail with a status code 400 if the o3-ozone-interaction-id header is having invalid value |
| PIS_H_017 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is having invalid value (paymentToTest: future-dated-payment-for-retail) | The operation must fail with a status code 400 if the o3-aspsp-id header is having invalid value |
| PIS_H_018 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-api-operation header is having invalid value (paymentToTest: future-dated-payment-for-retail) | TThe operation must fail with a status code 400 if the o3-api-operation header is having invalid value |
| PIS_H_019 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-api-uri header is having invalid value (paymentToTest: future-dated-payment-for-retail) | The operation must fail with a status code 400 if the o3-api-uri header is having invalid value |
| PIS_H_020 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is having invalid value (paymentToTest: future-dated-payment-for-retail) | The operation must fail with a status code 400 if the o3-psu-identifier header is having invalid value |
| PIS_H_021 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fails if o3-psu-identifier is not b64 encoded (paymentToTest: future-dated-payment-for-retail) | If o3-psu-identifier is not b64 encoded, the API must return a 400 and an error body |
| PIS_H_022 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fails if o3-psu-identifier does not evaluate to a json structure (paymentToTest: future-dated-payment-for-retail) | If o3-psu-identifier does not evaluate to a json structure, the API must return a 400 and an error body |
| PIS_H_023 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fails if o3-psu-identifier does not contain userId (paymentToTest: future-dated-payment-for-retail) | If o3-psu-identifier does not contain userId, the API must return a 400 and an error body |
| PIS_H_024 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined (paymentToTest: future-dated-payment-for-retail) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined, the API must return a 400 and an error body |
| PIS_H_025 | paymentToTest: future-dated-payment-for-retail | GET : Negative Test - Mandatory header validation - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string (paymentToTest: future-dated-payment-for-retail) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string, the API must return a 400 and an error body |
| PIS_H_026 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (paymentToTest : simple-cbuae-payment) | The operation must fail with a status code 400 if the o3-api-uri header is missing |
| PIS_H_027 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (paymentToTest : simple-cbuae-payment) | TThe operation must fail with a status code 400 if the o3-api-operation header is missing |
| PIS_H_028 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (paymentToTest : simple-cbuae-payment) | The operation must fail with a status code 400 if the o3-aspsp-id header is missing |
| PIS_H_029 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (paymentToTest : simple-cbuae-payment) | The operation must fail with a status code 400 if the o3-ozone-interaction-id header is missing |
| PIS_H_030 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (paymentToTest : simple-cbuae-payment) | The operation must fail with a status code 400 if the o3-provider-id header has an unexpected value |
| PIS_H_031 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (paymentToTest : simple-cbuae-payment) | The operation must fail with a status code 400 if the o3-caller-org-id header is missing |
| PIS_H_032 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (paymentToTest : simple-cbuae-payment) | The operation must fail with a status code 400 if the o3-caller-client-id header is missing |
| PIS_H_033 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (paymentToTest : simple-cbuae-payment) | The operation must fail with a status code 400 if the o3-caller-software-statement-id header is missing |
| PIS_H_034 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (paymentToTest : simple-cbuae-payment) | The operation must fail with a status code 400 if the o3-consent-id header is missing |
| PIS_H_035 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (paymentToTest : simple-cbuae-payment) | The operation must fail with a status code 400 if the o3-psu-identifier header has an unexpected value |
| PIS_H_036 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-consent-id header is having invalid value (paymentToTest : simple-cbuae-payment) | The operation must fail with a status code 400 if the o3-consent-id header is having invalid value |
| PIS_H_037 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is having invalid value (paymentToTest : simple-cbuae-payment) | The operation must fail with a status code 400 if the o3-caller-software-statement-id header is having invalid value |
| PIS_H_038 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is having invalid value (paymentToTest : simple-cbuae-payment) | The operation must fail with a status code 400 if the o3-caller-client-id header is having invalid value |
| PIS_H_039 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is having invalid value (paymentToTest : simple-cbuae-payment) | The operation must fail with a status code 400 if the o3-caller-org-id header is having invalid value |
| PIS_H_040 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-provider-id header is having invalid value (paymentToTest : simple-cbuae-payment) | The operation must fail with a status code 400 if the o3-provider-id header is having invalid value |
| PIS_H_041 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is having invalid value (paymentToTest : simple-cbuae-payment) | The operation must fail with a status code 400 if the o3-ozone-interaction-id header is having invalid value |
| PIS_H_042 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is having invalid value (paymentToTest : simple-cbuae-payment) | The operation must fail with a status code 400 if the o3-aspsp-id header is having invalid value |
| PIS_H_043 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-api-operation header is having invalid value (paymentToTest : simple-cbuae-payment) | TThe operation must fail with a status code 400 if the o3-api-operation header is having invalid value |
| PIS_H_044 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-api-uri header is having invalid value (paymentToTest : simple-cbuae-payment) | The operation must fail with a status code 400 if the o3-api-uri header is having invalid value |
| PIS_H_045 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is having invalid value (paymentToTest : simple-cbuae-payment) | The operation must fail with a status code 400 if the o3-psu-identifier header is having invalid value |
| PIS_H_046 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Fails if o3-psu-identifier is not b64 encoded (paymentToTest : simple-cbuae-payment) | If o3-psu-identifier is not b64 encoded, the API must return a 400 and an error body |
| PIS_H_047 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Fails if o3-psu-identifier does not evaluate to a json structure (paymentToTest : simple-cbuae-payment) | If o3-psu-identifier does not evaluate to a json structure, the API must return a 400 and an error body |
| PIS_H_048 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Fails if o3-psu-identifier does not contain userId (paymentToTest : simple-cbuae-payment) | If o3-psu-identifier does not contain userId, the API must return a 400 and an error body |
| PIS_H_049 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined (paymentToTest : simple-cbuae-payment) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined, the API must return a 400 and an error body |
| PIS_H_050 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string (paymentToTest : simple-cbuae-payment) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string, the API must return a 400 and an error body |
| PIS_H_051 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Fails if o3-caller-interaction-id header is missing (paymentToTest : simple-cbuae-payment) | If o3-caller-interaction-id header is missing, the API must return a 400 and an error body |
| PIS_H_052 | paymentToTest : simple-cbuae-payment | POST : Negative Test - Fails if o3-caller-interaction-id header is invalid value (paymentToTest : simple-cbuae-payment) | If o3-caller-interaction-id header is invalid, the API must return a 400 and an error body |
| PIS_H_053 | paymentToTest : simple-cbuae-payment | GET : Negative Test - Fails if o3-caller-interaction-id header is missing (paymentToTest : simple-cbuae-payment) | If o3-caller-interaction-id header is missing, the API must return a 400 and an error body |
| PIS_H_054 | paymentToTest : simple-cbuae-payment | GET : Negative Test - Fails if o3-caller-interaction-id header is invalid value (paymentToTest : simple-cbuae-payment) | If o3-caller-interaction-id header is invalid, the API must return a 400 and an error body |
| PIS_H_RFP001 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (paymentToTest: SamplePaymentId_ReportFile) | The operation must fail with a status code 400 if the o3-psu-identifier header is missing |
| PIS_H_RFP002 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (paymentToTest: SamplePaymentId_ReportFile) | The operation must fail with a status code 400 if the o3-api-uri header is missing |
| PIS_H_RFP003 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (paymentToTest: SamplePaymentId_ReportFile) | TThe operation must fail with a status code 400 if the o3-api-operation header is missing |
| PIS_H_RFP004 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (paymentToTest: SamplePaymentId_ReportFile) | The operation must fail with a status code 400 if the o3-aspsp-id header is missing |
| PIS_H_RFP005 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (paymentToTest: SamplePaymentId_ReportFile) | The operation must fail with a status code 400 if the o3-ozone-interaction-id header is missing |
| PIS_H_RFP006 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (paymentToTest: SamplePaymentId_ReportFile) | The operation must fail with a status code 400 if the o3-provider-id header has an unexpected value |
| PIS_H_RFP007 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (paymentToTest: SamplePaymentId_ReportFile) | The operation must fail with a status code 400 if the o3-caller-org-id header is missing |
| PIS_H_RFP008 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (paymentToTest: SamplePaymentId_ReportFile) | The operation must fail with a status code 400 if the o3-caller-client-id header is missing |
| PIS_H_RFP009 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (paymentToTest: SamplePaymentId_ReportFile) | The operation must fail with a status code 400 if the o3-caller-software-statement-id header is missing |
| PIS_H_RFP010 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (paymentToTest: SamplePaymentId_ReportFile) | The operation must fail with a status code 400 if the o3-consent-id header is missing |
| PIS_H_RFP011 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-consent-id header is having invalid value (paymentToTest: SamplePaymentId_ReportFile) | The operation must fail with a status code 400 if the o3-consent-id header is having invalid value |
| PIS_H_RFP012 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is having invalid value (paymentToTest: SamplePaymentId_ReportFile) | The operation must fail with a status code 400 if the o3-caller-software-statement-id header is having invalid value |
| PIS_H_RFP013 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is having invalid value (paymentToTest: SamplePaymentId_ReportFile) | The operation must fail with a status code 400 if the o3-caller-client-id header is having invalid value |
| PIS_H_RFP014 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is having invalid value (paymentToTest: SamplePaymentId_ReportFile) | The operation must fail with a status code 400 if the o3-caller-org-id header is having invalid value |
| PIS_H_RFP015 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-provider-id header is having invalid value (paymentToTest: SamplePaymentId_ReportFile) | The operation must fail with a status code 400 if the o3-provider-id header is having invalid value |
| PIS_H_RFP016 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is having invalid value (paymentToTest: SamplePaymentId_ReportFile) | The operation must fail with a status code 400 if the o3-ozone-interaction-id header is having invalid value |
| PIS_H_RFP017 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is having invalid value (paymentToTest: SamplePaymentId_ReportFile) | The operation must fail with a status code 400 if the o3-aspsp-id header is having invalid value |
| PIS_H_RFP018 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-api-operation header is having invalid value (paymentToTest: SamplePaymentId_ReportFile) | TThe operation must fail with a status code 400 if the o3-api-operation header is having invalid value |
| PIS_H_RFP019 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-api-uri header is having invalid value (paymentToTest: SamplePaymentId_ReportFile) | The operation must fail with a status code 400 if the o3-api-uri header is having invalid value |
| PIS_H_RFP020 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is having invalid value (paymentToTest: SamplePaymentId_ReportFile) | The operation must fail with a status code 400 if the o3-psu-identifier header is having invalid value |
| PIS_H_RFP021 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Fails if o3-psu-identifier is not b64 encoded (paymentToTest: SamplePaymentId_ReportFile) | If o3-psu-identifier is not b64 encoded, the API must return a 400 and an error body |
| PIS_H_RFP022 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Fails if o3-psu-identifier does not evaluate to a json structure (paymentToTest: SamplePaymentId_ReportFile) | If o3-psu-identifier does not evaluate to a json structure, the API must return a 400 and an error body |
| PIS_H_RFP023 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Fails if o3-psu-identifier does not contain userId (paymentToTest: SamplePaymentId_ReportFile) | If o3-psu-identifier does not contain userId, the API must return a 400 and an error body |
| PIS_H_RFP024 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined (paymentToTest: SamplePaymentId_ReportFile) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined, the API must return a 400 and an error body |
| PIS_H_RFP025 | paymentToTest: SamplePaymentId_ReportFile | GET : Negative Test - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string (paymentToTest: SamplePaymentId_ReportFile) | If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string, the API must return a 400 and an error body |
| PIS_H_RFP026 | paymentToTest : simple-cbuae-payment | GET : Negative Test - Fails if o3-caller-interaction-id header is missing (paymentToTest : simple-cbuae-payment) | If o3-caller-interaction-id header is missing, the API must return a 400 and an error body |
| PIS_H_RFP027 | paymentToTest : simple-cbuae-payment | GET : Negative Test - Fails if o3-caller-interaction-id header is invalid value (paymentToTest : simple-cbuae-payment) | If o3-caller-interaction-id header is invalid, the API must return a 400 and an error body |
| single-instant-payments |
| ||
| PIS_SIP001 | paymentToTest : single-instant-payment-for-retail | POST : Happy Path - Single instant payments (paymentToTest : single-instant-payment-for-retail) | The operartion must succeed with a status code 201 if the payment is successfully created |
| PIS_SIP002 | paymentToTest : single-instant-payment-for-retail | GET : Happy Path - Succeeds if valid paymentId in path parameter returns payments (paymentToTest : single-instant-payment-for-retail) | Valid paymentId provided in the path parameter should return a 200 and the paymentId must be present in the response |
| PIS_SIP003 | paymentToTest : single-instant-payment-for-SME | POST : Happy Path - Single instant payments (paymentToTest : single-instant-payment-for-SME) | The operartion must succeed with a status code 201 if the payment is successfully created |
| PIS_SIP004 | paymentToTest : single-instant-payment-for-SME | GET : Succeeds if valid paymentId in path parameter returns payments (paymentToTest : single-instant-payment-for-SME) | Valid paymentId provided in the path parameter should return a 200 and the paymentId must be present in the response |
| PIS_SIP005 | paymentToTest : single-instant-payment-for-corporate | POST : Happy Path - Single instant payments (paymentToTest : single-instant-payment-for-corporate) | The operartion must succeed with a status code 201 if the payment is successfully created |
| PIS_SIP006 | paymentToTest : single-instant-payment-for-corporate | GET : Happy Path - Succeeds if valid paymentId in path parameter returns payments (paymentToTest : single-instant-payment-for-corporate) | Valid paymentId provided in the path parameter should return a 200 and the paymentId must be present in the response |
| PIS_SIP007 | paymentToTest : Sample_SIP_Valid_PaymentIds_AcceptedSettlementCompleted | GET : Happy Path - Succeeds if valid paymentId in path parameter returns payments with status AcceptedSettlementCompleted (paymentToTest : Sample_SIP_Valid_PaymentIds_AcceptedSettlementCompleted) | Valid paymentId provided in the path parameter should returns a 200 with status 'AcceptedSettlementCompleted' in response |
| PIS_SIP008 | paymentToTest : Sample_SIP_Valid_PaymentIds_AcceptedCreditSettlementCompleted | GET : Happy Path - Succeeds if valid paymentId in path parameter returns payments with status AcceptedCreditSettlementCompleted (paymentToTest : Sample_SIP_Valid_PaymentIds_AcceptedCreditSettlementCompleted) | Valid paymentId provided in the path parameter should returns a 200 with status 'AcceptedSettlementCompleted' in response |
| PIS_SIP009 | paymentToTest : Sample_SIP_Valid_PaymentIds_AcceptedWithoutPosting | GET : Happy Path - Succeeds if valid paymentId in path parameter returns payments with status AcceptedWithoutPosting (paymentToTest : Sample_SIP_Valid_PaymentIds_AcceptedWithoutPosting) | Valid paymentId provided in the path parameter should returns a 200 with status 'AcceptedSettlementCompleted' in response |
| PIS_SIP010 | paymentToTest : Sample_SIP_Valid_PaymentIds_Rejected | GET : Happy Path - Succeeds if valid paymentId in path parameter returns payments with status Rejected (paymentToTest : Sample_SIP_Valid_PaymentIds_Rejected) | Valid paymentId provided in the path parameter should returns a 200 with status 'AcceptedSettlementCompleted' in response |
| PIS_SIP011 | paymentToTest : MissingBodyField_paymentType | POST : Negative Test - Fail if payment type field in the request body is missing (paymentToTest : MissingBodyField_paymentType) | The operation must fail with a status code 400 if the payment type field is missing in the request body |
| PIS_SIP012 | paymentToTest : MissingBodyField_PersonalIdentifiableInformation | POST : Negative Test - Fail if Personal Identifiable Information field in the request body is missing (paymentToTest : MissingBodyField_PersonalIdentifiableInformation) | The operation must fail with a status code 400 if the Personal Identifiable Information field is missing in the request body |
| PIS_SIP013 | paymentToTest : MissingBodyField_PaymentPurposeCode | POST : Negative Test - Fail if Payment Purpose Code field in the request body is missing (paymentToTest : MissingBodyField_PaymentPurposeCode) | The operation must fail with a status code 400 if the Payment Purpose Code field is missing in the request body |
| PIS_SIP014 | paymentToTest : MissingBodyField_ConsentId | POST : Negative Test - Fail if consent id field in the request body is missing (paymentToTest : MissingBodyField_ConsentId) | The operation must fail with a status code 400 if the consent id field is missing in the request body |
| PIS_SIP015 | accountToTest: AccountIdWithValidBalanceType | Happy path - Succeeds if valid accountId in path parameter returns balances (accountToTest: AccountIdWithValidBalanceType) | Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with balance details |
| PIS_SIP016 | paymentToTest: single-instant-payment-for-retail | POST /payment : Negative Test : Verify that a payment cannot be processed via the POST /payment endpoint if the amount exceeds the available balance (paymentToTest: single-instant-payment-for-retail) | The operation must fail with a status code 400 if the payment amount exceeds the available balance. |
| validate |
| ||
| PIS_VAL001 | paymentToTest: event-AwaitingAuthorisation-for-fixed-defined-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing only the mandatory fields for fixed-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-fixed-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL002 | paymentToTest: event-AwaitingAuthorisation-for-fixed-defined-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for fixed-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-fixed-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL003 | paymentToTest: event-AwaitingAuthorisation-for-fixed-defined-schedule-retail-user | POST /validate : Verify that the endpoint throws error when mandatory fields are missing for fixed-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-fixed-defined-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_VAL004 | paymentToTest: event-AwaitingAuthorisation-for-variable-defined-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing only the mandatory fields for variable-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-variable-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL005 | paymentToTest: event-AwaitingAuthorisation-for-variable-defined-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for variable-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-variable-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL006 | paymentToTest: event-AwaitingAuthorisation-for-variable-defined-schedule-retail-user | POST /validate : Verify that the endpoint throws error when mandatory fields are missing for variable-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-variable-defined-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_VAL007 | paymentToTest: event-AwaitingAuthorisation-for-fixed-periodic-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing only the mandatory fields for fixed-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-fixed-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL008 | paymentToTest: event-AwaitingAuthorisation-for-fixed-periodic-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for fixed-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-fixed-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL009 | paymentToTest: event-AwaitingAuthorisation-for-fixed-periodic-schedule-retail-user | POST /validate : Verify that the endpoint throws error when mandatory fields are missing for fixed-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-fixed-periodic-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_VAL010 | paymentToTest: event-AwaitingAuthorisation-for-variable-periodic-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing only the mandatory fields for variable-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-variable-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL011 | paymentToTest: event-AwaitingAuthorisation-for-variable-periodic-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for variable-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-variable-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL012 | paymentToTest: event-AwaitingAuthorisation-for-variable-periodic-schedule-retail-user | POST /validate : Verify that the endpoint throws error when mandatory fields are missing for variable-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-variable-periodic-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_VAL013 | paymentToTest: event-AwaitingAuthorisation-for-fixed-on-demand-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing only the mandatory fields for fixed-on-demand (paymentToTest: event-AwaitingAuthorisation-for-fixed-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL014 | paymentToTest: event-AwaitingAuthorisation-for-fixed-on-demand-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for fixed-on-demand (paymentToTest: event-AwaitingAuthorisation-for-fixed-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL015 | paymentToTest: event-AwaitingAuthorisation-for-fixed-on-demand-retail-user | POST /validate : Verify that the endpoint throws error when mandatory fields are missing for fixed-on-demand (paymentToTest: event-AwaitingAuthorisation-for-fixed-on-demand-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_VAL016 | paymentToTest: event-AwaitingAuthorisation-for-variable-on-demand-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing only the mandatory fields for variable-on-demand (paymentToTest: event-AwaitingAuthorisation-for-variable-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL017 | paymentToTest: event-AwaitingAuthorisation-for-variable-on-demand-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for variable-on-demand (paymentToTest: event-AwaitingAuthorisation-for-variable-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL018 | paymentToTest: event-AwaitingAuthorisation-for-variable-on-demand-retail-user | POST /validate : Verify that the endpoint throws error when mandatory fields are missing for variable-on-demand (paymentToTest: event-AwaitingAuthorisation-for-variable-on-demand-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_VAL019 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-defined-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined FDP with fixed-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL020 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-defined-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined FDP with fixed-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL021 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-defined-schedule-retail-user | POST /validate : Verify that the endpoint throws error when mandatory fields are missing for combined FDP with fixed-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-defined-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_VAL022 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-defined-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined FDP with variable-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL023 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-defined-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined FDP with variable-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL024 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-defined-schedule-retail-user | POST /validate : Verify that the endpoint throws error when mandatory fields are missing for combined FDP with variable-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-defined-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_VAL025 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-periodic-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined FDP with fixed-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL026 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-periodic-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined FDP with fixed-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL027 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-periodic-schedule-retail-user | POST /validate : Verify that the endpoint throws error when mandatory fields are missing for combined FDP with fixed-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-fixed-periodic-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_VAL028 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-periodic-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined FDP with variable-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL029 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-periodic-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined FDP with variable-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL030 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-periodic-schedule-retail-user | POST /validate : Verify that the endpoint throws error when mandatory fields are missing for combined FDP with variable-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-periodic-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_VAL031 | paymentToTest: event-Authorized-for-CombinedFDP-fixed-on-demand-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined FDP with fixed-on-demand (paymentToTest: event-Authorized-for-CombinedFDP-fixed-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL032 | paymentToTest: event-Authorized-for-CombinedFDP-fixed-on-demand-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined FDP with fixed-on-demand (paymentToTest: event-Authorized-for-CombinedFDP-fixed-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL033 | paymentToTest: event-Authorized-for-CombinedFDP-fixed-on-demand-retail-user | POST /validate : Verify that the endpoint throws error when mandatory fields are missing for combined FDP with fixed-on-demand (paymentToTest: event-Authorized-for-CombinedFDP-fixed-on-demand-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_VAL034 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-on-demand-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined FDP with variable-on-demand (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL035 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-on-demand-retail-user | POST /validate : Happy Path -Succeeds with a valid request containing both mandatory and optional fields for combined FDP with variable-on-demand (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL036 | paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-on-demand-retail-user | POST /validate : Verify that the endpoint throws error when mandatory fields are missing for combined FDP with variable-on-demand (paymentToTest: event-AwaitingAuthorisation-for-CombinedFDP-variable-on-demand-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_VAL037 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-defined-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined SIP with fixed-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL038 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-defined-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined SIP with fixed-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL039 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-defined-schedule-retail-user | POST /validate : Verify that the endpoint throws error when mandatory fields are missing for combined SIP with fixed-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-defined-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_VAL040 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-defined-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined SIP with variable-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL041 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-defined-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined SIP with variable-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-defined-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL042 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-defined-schedule-retail-user | POST /validate : Verify that the endpoint throws error when mandatory fields are missing for combined SIP with variable-Defined-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-defined-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_VAL043 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-periodic-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined SIP with fixed-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL044 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-periodic-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined SIP with fixed-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL045 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-periodic-schedule-retail-user | POST /validate : Verify that the endpoint throws error when mandatory fields are missing for combined SIP with fixed-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-fixed-periodic-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_VAL046 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-periodic-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined SIP with variable-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL047 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-periodic-schedule-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined SIP with variable-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-periodic-schedule-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL048 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-periodic-schedule-retail-user | POST /validate : Verify that the endpoint throws error when mandatory fields are missing for combined SIP with variable-periodic-schedule (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-periodic-schedule-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_VAL049 | paymentToTest: event-Authorized-for-CombinedSIP-fixed-on-demand-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined SIP with fixed-on-demand (paymentToTest: event-Authorized-for-CombinedSIP-fixed-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL050 | paymentToTest: event-Authorized-for-CombinedSIP-fixed-on-demand-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined SIP with fixed-on-demand (paymentToTest: event-Authorized-for-CombinedSIP-fixed-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL051 | paymentToTest: event-Authorized-for-CombinedSIP-fixed-on-demand-retail-user | POST /validate : Verify that the endpoint throws error when mandatory fields are missing for combined SIP with fixed-on-demand (paymentToTest: event-Authorized-for-CombinedSIP-fixed-on-demand-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| PIS_VAL052 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-on-demand-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing only the mandatory fields for combined SIP with variable-on-demand (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL053 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-on-demand-retail-user | POST /validate : Happy Path - Succeeds with a valid request containing both mandatory and optional fields for combined SIP with variable-on-demand (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-on-demand-retail-user) | The operation must succeed with a status code 200 if the data is valid. |
| PIS_VAL054 | paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-on-demand-retail-user | POST /validate : Verify that the endpoint throws error when mandatory fields are missing for combined SIP with variable-on-demand (paymentToTest: event-AwaitingAuthorisation-for-CombinedSIP-variable-on-demand-retail-user) | The operation must fail with a status code 400 due to invalid data. |
| variable-defined-schedule |
| ||
| Before_VDS001 | paymentToTest: event-AwaitingAuthorisation-for-variable-defined-schedule-retail-user | POST /event/post: Happy Path - Verify all mandatory request body fields with consent status AwaitingAuthorization for Variable Defined Schedule (paymentToTest: event-AwaitingAuthorisation-for-variable-defined-schedule-retail-user) | Ozone will send a consent in the AwaitingAuthorization state to the LFI after the consent/event/post endpoint is hit. |
| Before_VDS002 | paymentToTest: event-Authorized-for-variable-defined-schedule-retail-user | POST /event/patch: Happy Path - Verify the successful creation of an event when the consentStatus is set to Authorized for a predefined Variable Defined Schedule (paymentToTest: event-Authorized-for-variable-defined-schedule-retail-user) | Ozone will be sending an consent in an Authorized state to the LFI after the consent/event/patch is hit. |
| PIS_VDS003 | paymentToTest: variable-defined-schedule-for-retail-user | POST /payment: Happy Path - Verify all mandatory and optional request body fields for Variable Defined Schedule (paymentToTest: variable-defined-schedule-for-retail-user) | The operation must succeed with a status code 201 if the payment is created successfully |
| After_VDS004 | paymentToTest: event-Consumed-for-variable-defined-schedule-retail-user | POST /event/patch: Happy Path - Verify all mandatory request body fields with consent status Consumed for Variable Defined Schedule (paymentToTest: event-Consumed-for-variable-defined-schedule-retail-user) | Ozone will send a consent in a Consumed state to the LFI after the consent/event/patch is hit |
| PIS_VDS005 | paymentToTest: variable-defined-schedule-for-retail-user | GET /payment: Happy Path - Verify that a valid paymentId in the path parameter returns payments for Variable Defined Schedule (paymentToTest: variable-defined-schedule-for-retail-user) | A valid paymentId provided in the path parameter should return a status code of 200, and the paymentId must be present in the response |
| PIS_VDS006 | paymentToTest: variable-Defined-Schedule | PPOST /event/patch: Negative Test - Verify that the endpoint throws error when mandatory fields are missing for Variable Defined Schedule (paymentToTest: variable-Defined-Schedule) | The operation must fail with a status code 400 when the request body contains only optional fields |
| variable-on-demand |
| ||
| Before_VOD001 | paymentToTest: event-AwaitingAuthorisation-for-variable-on-demand-retail-user | POST /event/post - Happy Path: Verify all mandatory request body fields with consent status AwaitingAuthorization for Variable On Demand (paymentToTest: event-AwaitingAuthorisation-for-variable-on-demand-retail-user) | Ozone will send a consent in the AwaitingAuthorization state to the LFI after the consent/event/post endpoint is hit |
| Before_VOD002 | paymentToTest: event-Authorized-for-variable-on-demand-retail-user | POST /event/patch: Happy Path - Verify the successful creation of an event when the consentStatus is set to Authorized for a predefined Variable On Demand (paymentToTest: event-Authorized-for-variable-on-demand-retail-user) | Ozone will send a consent in an Authorized state to the LFI after the consent/event/patch endpoint is hit. |
| PIS_VOD003 | paymentToTest: variable-on-demand-for-retail-user | POST /payment: Happy Path - Verify all mandatory and optional request body fields for Variable On Demand (paymentToTest: variable-on-demand-for-retail-user) | The operation must succeed with a status code 201 if the payment is created successfully. |
| After_VOD004 | paymentToTest: event-Consumed-for-variable-on-demand-retail-user | POST /event/patch: Happy Path - Verify all mandatory request body fields with consent status 'Consumed' for Variable On Demand (paymentToTest: event-Consumed-for-variable-on-demand-retail-user) | Ozone will send a consent in a Consumed state to the LFI after the consent/event/patch endpoint is hit. |
| PIS_VOD005 | paymentToTest: variable-on-demand-for-retail-user | GET /payment: Happy Path - Verify that a valid paymentId in the path parameter returns payments for Variable On Demand (paymentToTest: variable-on-demand-for-retail-user) | A valid paymentId provided in the path parameter should return a status code 200, and the paymentId must be present in the response |
| PIS_VOD006 | paymentToTest: variable-on-demand | POST event/patch: Negative Test - Verify that the endpoint throws error when mandatory fields are missing for Variable On Demand (paymentToTest: variable-on-demand) | The operation must fail with a status code 400 if the request body contains only optional fields |
| variable-periodic-schedule |
| ||
| Before_VPS001 | paymentToTest: event-AwaitingAuthorisation-for-variable-periodic-schedule-retail-user | POST /event/post - Happy Path: Verify all mandatory request body fields with consent status AwaitingAuthorization for a Variable Periodic Schedule (paymentToTest: event-AwaitingAuthorisation-for-variable-periodic-schedule-retail-user) | Ozone will send a consent in the AwaitingAuthorization state to the LFI after the consent/event/post endpoint is hit |
| Before_VPS002 | paymentToTest: event-Authorized-for-variable-periodic-schedule-retail-user | POST /event/patch - Happy Path: Verify the successful creation of an event when the consentStatus is set to Authorized for a predefined variable periodic schedule (paymentToTest: event-Authorized-for-variable-periodic-schedule-retail-user) | Ozone will send a consent in an Authorized state to the LFI after the consent/event/patch endpoint is hit. |
| PIS_VPS003 | paymentToTest: variable-periodic-schedule-for-retail-user | POST /payment - Happy Path: Verify all mandatory request body fields for a variable periodic schedule (paymentToTest: variable-periodic-schedule-for-retail-user) | The operation must succeed with a status code 201 if the payment is created successfully. |
| After_VPS004 | paymentToTest: event-Consumed-for-variable-periodic-schedule-retail-user | POST /event/patch - Happy Path: Verify all mandatory request body fields with consent status Consumed for a variable periodic schedule (paymentToTest: event-Consumed-for-variable-periodic-schedule-retail-user) | Ozone will send a consent in a Consumed state to the LFI after the consent/event/patch endpoint is hit |
| PIS_VPS005 | paymentToTest: variable-periodic-schedule-for-retail-user | GET /payment - Happy Path: Verify that providing a valid paymentId in the path parameter returns the payment for a variable periodic schedule. (paymentToTest: variable-periodic-schedule-for-retail-user) | A valid paymentId provided in the path parameter should return a status code 200, and the paymentId must be present in the response |
| PIS_VPS006 | paymentToTest: variable-periodic-schedule | POST /event/patch - Negative Test: Verify that the endpoint throws error when mandatory fields are missing for a variable periodic schedule (paymentToTest: variable-periodic-schedule) | The operation must fail with a status code 400 if the request body contains only optional fields |
© Ozone Financial Technology Limited 2024-2025
Ozone Non Commercial Software EULA
Please try out our Advanced Search function.