Page Comparison

ACC_020_001

Ensure the API effectively retrieves account details when a valid Account & Account Sub-Type combination that is in either Active or Inactive status when the accountId is supplied as a path parameter. The test should confirm that the response includes the correct account information and returns a status code of 200.

AIS_AA001

accountToTest : SME_CurrentAccount_Active

Happy Path - Succeeds with valid CurrentAccount for SME user in Active status for valid accountId as path parameter (accountToTest : SME_CurrentAccount_Active)

200

"Returns a 200 if all headers are valid and returns a record for specified accountId including account type 'SME' and account sub type 'CurrentAccount', for a SME user with status 'Active'"

AIS_AA002

accountToTest : Corporate_Savings_Inactive

Happy Path - Succeeds with valid Savings for corporate user in Inactive status for valid accountId as path parameter (accountToTest : Corporate_Savings_Inactive)

200

"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 'Inactive'"

AIS_AA003

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)

200

"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'"

AIS_AA004

accountToTest : Retail_Savings_Inactive

Happy Path - Succeeds with valid Savings for retail user in Inactive status for valid accountId as path parameter (accountToTest : Retail_Savings_Inactive)

200

"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 'Inactive'"

AIS_AA005

accountToTest: Corporate_CurrentAccount_Active

Happy Path - Succeeds with valid CurrentAccount for Corporate user in Active status for valid accountId as path parameter (accountToTest: Corporate_CurrentAccount_Active)

200

"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 'Active'"

ACC_020_002

Ensure that the API correctly handles the scenario where the accountId path parameter is missing returning an appropriate error response.

AIS_AA006

accountToTest : NoAccount

Negative Test - Fails if accountId path parameter is missing (accountToTest : NoAccount)

401400

"If accountIds path parameter is missing, the API must return a 401 and an error body"

ACC_020_003

Ensure that the API correctly validates mandatory headers.

AIS_AA007

accountToTest : SampleAccount

Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest : SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing with accountId passed as path parameter

AIS_AA008

accountToTest : SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest : SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-api-uri header is missing with accountId passed as path parameter

AIS_AA009

accountToTest : SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest : SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-api-operation header is missing with accountId passed as path parameter

AIS_AA010

accountToTest : SampleAccount

Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (accountToTest : SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing with accountId passed as path parameter

AIS_AA011

accountToTest : SampleAccount

Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest : SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing with accountId passed as path parameter

AIS_AA012

accountToTest : SampleAccount

Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest : SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-provider-id header has an unexpected value with accountId passed as path parameter

AIS_AA013

accountToTest : SampleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (accountToTest : SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-org-id header is missing with accountId passed as path parameter

AIS_AA014

accountToTest : SampleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (accountToTest : SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-client-id header is missing with accountId passed as path parameter

AIS_AA015

accountToTest : SampleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (accountToTest : SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is missing with accountId passed as path parameter

AIS_AA016

accountToTest : SampleAccount

Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (accountToTest : SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-consent-id header is missing with accountId passed as path parameter

AIS_AA017

accountToTest : SampleAccount

Negative Test - Fails if o3-aspsp-id has an invalid value (accountToTest : SampleAccount)

400

"If o3-aspsp-id has an invalid value with accountId passed as path parameter, the API must return a 400 and an error body"

AIS_AA018

accountToTest : SampleAccount

Negative Test - Fails if o3-psu-identifier is not b64 encoded (accountToTest : SampleAccount)

400

"If o3-psu-identifier is not b64 encoded with accountId passed as path parameter, the API must return a 400 and an error body"

AIS_AA019

accountToTest : SampleAccount

Negative Test - Fails if o3-psu-identifier does not evaluate to a json structure (accountToTest : SampleAccount)

400

"If o3-psu-identifier does not evaluate to a json structure with accountId passed as path parameter, the API must return a 400 and an error body"

AIS_AA020

accountToTest : SampleAccount

Negative Test - Fails if o3-psu-identifier does not contain userId (accountToTest : SampleAccount)

400

"If o3-psu-identifier does not contain userId with accountId passed as path parameter, the API must return a 400 and an error body"

AIS_AA021

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)"

400

"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_AA022

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)"

400

"If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is not a string and , the API must return a 400 and an error body"

BAL_010_001

Ensure that valid accountId returns balance details.

AIS_BA001

accountToTest: Valid_Accounts_List

Happy path - Succeeds if valid accountId in path parameter returns balances (accountToTest: Valid_Accounts_List)

200

Valid accountId provided in the path parameter should return a 200 and the accountId must be present in the response with balance details

AIS_BA002

accountToTest: AccountIdWithCreditIndicator

Happy path - Succeeds if valid accountId in path parameter returns balances with positive balance and credit line included (accountToTest: AccountIdWithCreditIndicator)

200

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

AIS_BA003

accountToTest: AccountIdWithZeroCreditIndicator

Happy path - Succeeds if valid accountId in path parameter returns zero balance with creditDebitIndicator value as 'credit' (accountToTest: AccountIdWithZeroCreditIndicator)

200

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

BAL_010_002

Ensure that the API correctly handles missing accountIds path parameter.

AIS_BA004

accountToTest: NoAccount

Negative Test - Fails if accountIds path parameter is missing (accountToTest: NoAccount)

401400

"If accountIds path parameter is missing, the API must return a 401 400 and an error body"

AIS_BA005

accountToTest: Invalid_Single_AccountId

Negative Test - Fails if accountId format is invalid (accountToTest: Invalid_Single_AccountId)

400

"If the accountId format is invalid , the API must return a 400 and an error body"

BAL_010_003

Ensure that the API correctly validates mandatory headers.

AIS_BA006

accountToTest: NoAccount

Negative Test - Mandatory field validation - Fail if both accountId and o3-psu-identifier are missing (accountToTest: NoAccount)

400

The operation must fail with a status of 400 if both the accountId path parameter and the o3-psu-identifier header parameter are missing

AIS_BA007

accountToTest: SampleSingleAccount

Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest: SampleSingleAccount)

400

The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing

AIS_BA008

accountToTest: SampleSingleAccount

Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest: SampleSingleAccount)

400

The operation must fail with a status code 400 and error body if the o3-api-uri header is missing

AIS_BA009

accountToTest: SampleSingleAccount

Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest: SampleSingleAccount)

400

The operation must fail with a status code 400 and error body if the o3-api-operation header is missing

AIS_BA010

accountToTest: SampleSingleAccount

Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (accountToTest: SampleSingleAccount)

400

The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing

AIS_BA011

accountToTest: SampleSingleAccount

Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest: SampleSingleAccount)

400

The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing

AIS_BA012

accountToTest: SampleSingleAccount

Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest: SampleSingleAccount)

400

The operation must fail with a status code 400 and error body if the o3-provider-id header has an unexpected value

AIS_BA013

accountToTest: SampleSingleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (accountToTest: SampleSingleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-org-id header is missing

AIS_BA014

accountToTest: SampleSingleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (accountToTest: SampleSingleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-client-id header is missing

AIS_BA015

accountToTest: SampleSingleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (accountToTest: SampleSingleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is missing

AIS_BA016

accountToTest: SampleSingleAccount

Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (accountToTest: SampleSingleAccount)

400

The operation must fail with a status code 400 and error body if the o3-consent-id header is missing

AIS_BA017

accountToTest: SampleSingleAccount

Negative Test - Fails if o3-psu-identifier is not b64 encoded (accountToTest: SampleSingleAccount)

400

"If o3-psu-identifier is not b64 encoded, the API must return a 400 and an error body"

AIS_BA018

accountToTest: SampleSingleAccount

Negative Test - Fails if o3-psu-identifier does not evaluate to a json structure (accountToTest: SampleSingleAccount)

400

"If o3-psu-identifier does not evaluate to a json structure, the API must return a 400 and an error body"

AIS_BA019

accountToTest: SampleSingleAccount

Negative Test - Fails if o3-psu-identifier does not contain userId (accountToTest: SampleSingleAccount)

400

"If o3-psu-identifier does not contain userId, the API must return a 400 and an error body"

AIS_BA020

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is having invalid value (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is having invalid value

AIS_BA021

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)"

400

"If o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined, the API mus

t return a 400 and an error body"

AIS_BA022

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)"

400

"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"

BEN_010_001

Ensure that valid accountId returns beneficiaries with Activated/NotActivate status.

AIS_BE001

accountToTest: AccountIdWithActivatedBeneficiaryType

Happy path - Succeeds if valid accountId in path parameter returns beneficiaries with beneficiaries category Activated in response body (accountToTest: AccountIdWithActivatedBeneficiaryType)

200

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

AIS_BE002

accountToTest: AccountIdWithNotActivatedBeneficiaryType

Happy path - Succeeds if valid accountId in path parameter returns beneficiaries with beneficiaries category NotActivated in response body (accountToTest: AccountIdWithNotActivatedBeneficiaryType)

200

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)

200

Returns a 200 status code with the specified number of accounts in each page and the meta information about the pagination

AIS_BE004

accountToTest: AccountIdWithNoBeneficiaries

Happy path - Succeeds if valid accountId in path parameter returns no beneficiaries (accountToTest: AccountIdWithNoBeneficiaries)

200

Valid accountId provided in the path parameter should return a 200 with an empty array if there are no beneficiaries

AIS_BE005

accountToTest: AccountIdWithActivatedAndNotActivatedBeneficiaryType

Happy path - Succeeds if valid accountId in path parameter returns beneficiaries with beneficiaries category Activated and NotActivated in response body (accountToTest: AccountIdWithActivatedAndNotActivatedBeneficiaryType)

200

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

BEN_010_002

Ensure that the API correctly handles missing/invalid accountId path parameter.

AIS_BE006

Negative Test - Fails if accountIds path parameter is missing

401400

"If accountIds path parameter is missing, the API must return a 401 400 and an error body"

AIS_BE007

accountToTest: Invalid_Single_AccountId

Negative Test - Fails if accountId format is invalid (accountToTest: Invalid_Single_AccountId)

400

"If the accountId format is invalid , the API must return a 400 and an error body"

BEN_010_003

Ensure that the API correctly validates mandatory headers.

AIS_BE008

accountToTest: NoAccount

Negative Test - Mandatory field validation - Fail if both accountId and o3-psu-identifier are missing (accountToTest: NoAccount)

400

The operation must fail with a status of 400 if both the accountId path parameter and the o3-psu-identifier header parameter are missing

AIS_BE009

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing

AIS_BE010

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-api-uri header is missing

AIS_BE011

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-api-operation header is missing

AIS_BE012

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing

AIS_BE013

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing

AIS_BE014

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-provider-id header has an unexpected value

AIS_BE015

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-org-id header is missing

AIS_BE016

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-client-id header is missing

AIS_BE017

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is missing

AIS_BE018

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-consent-id header is missing

AIS_BE019

accountToTest: SampleAccount

Negative Test - Fails if o3-psu-identifier is not b64 encoded (accountToTest: SampleAccount)

400

"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)

400

"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)

400

"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-provider-id header is having invalid value (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-provider-id header is having invalid value

AIS_BE023

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is having invalid value (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is having invalid value

AIS_BE024

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-operation header is having invalid value (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-api-operation header is having invalid value

AIS_BE025

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-uri header is having invalid value (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-api-uri header is having invalid value

AIS_BE026

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)"

400

"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_BE027

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)"

400

"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"

CUS_010_001

Ensure that the API returns the customer details for the user id identified by the o3-psu-identifier header.

AIS_C001

customerType: Delegate_CustomerType

Happy path - Succeeds if customer for PSU identified by o3-psu-identifier header (customerType: Delegate_CustomerType)

200

The API must return the customer for the PSU identified by the o3-psu-identifier header

AIS_C002

Happy path - Succeeds when no customer is found

200

The API must return a success status code 200 with an empty data object if no customer is found

AIS_C003

customerType : Retail_CustomerType

Happy path - Succeeds when valid o3-psu-identifier provided in the header which belongs to a retail user (customerType : Retail_CustomerType)

200

Returns a 200 status code with details of a retail user in the response as per the schema

AIS_C004

customerType : Corporate_CustomerType

Happy path - Succeeds when valid o3-psu-identifier provided in the header which belongs to a corporate user (customerType : Corporate_CustomerType)

200

Returns a 200 status code with details of a corporate user in the response as per the schema

AIS_C005

customerType : SME_CustomerType

Happy path - Succeeds when valid o3-psu-identifier provided in the header which belongs to a SME user (customerType : SME_CustomerType)

200

Returns a 200 status code with details of a SME user in the response as per the schema

CUS_010_002

Ensure that the API correctly validates mandatory headers.

AIS_C006

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing

AIS_C007

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-api-uri header is missing

AIS_C008

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest: SampleAccount)

400

TThe operation must fail with a status code 400 and error body if the o3-api-operation header is missing

AIS_C009

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing

AIS_C010

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing

AIS_C011

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-provider-id header has an unexpected value

AIS_C012

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-org-id header is missing

AIS_C013

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-client-id header is missing

AIS_C014

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is missing

AIS_C015

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-consent-id header is missing

AIS_C016

accountToTest: SampleAccount

Negative Test - Fails if o3-psu-identifier is not b64 encoded (accountToTest: SampleAccount)

400

"If o3-psu-identifier is not b64 encoded, the API must return a 400 and an error body"

AIS_C017C016

accountToTest: SampleAccount

Negative Test - Fails if o3-psu-identifier does not evaluate to a json structure (accountToTest: SampleAccount)

400

"If o3-psu-identifier does not evaluate to a json structure, the API must return a 400 and an error body"

AIS_C018C017

accountToTest: SampleAccount

Negative Test - Fails if o3-psu-identifier does not contain userId (accountToTest: SampleAccount)

400

"If o3-psu-identifier does not contain userId, the API must return a 400 and an error body"

CUS_020_001

Ensure that the API provides associated customer details linked to the accountId.

AIS_CC001

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)

200

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_020_002

Ensure that the API correctly handles missing/invalid accountId path parameter.

AIS_CC002

accountToTest: SampleAccount

Negative Test - Fails if accountId path parameter is missing (accountToTest: SampleAccount)

401400

"If accountIds path parameter is missing, the API must return a 401 400 and an error body"

AIS_CC003

accountToTest: Invalid_Single_AccountId

Negative Test - Fails if accountId format is invalid (accountToTest: Invalid_Single_AccountId)

400

"If the accountId format is invalid , the API must return a 400 and an error body"

CUS_020_003

Ensure that the API correctly validates mandatory headers.

AIS_CC004

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing

AIS_CC005

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-api-uri header is missing

AIS_CC006

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest: SampleAccount)

400

TThe operation must fail with a status code 400 and error body if the o3-api-operation header is missing

AIS_CC007

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing

AIS_CC008

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing

AIS_CC009

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-provider-id header has an unexpected value

AIS_CC010

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-org-id header is missing

AIS_CC011

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-client-id header is missing

AIS_CC012

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is missing

AIS_CC013

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-consent-id header is missing

AIS_CC014

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)"

400

"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_CC015

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)"

400

"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"

DD_010_001

Ensure that valid accountId returns direct-debits.Various tests, such as retrieving direct debits with different statuses and frequencies, have been incorporated.

AIS_DD001

accountToTest: AccountIdWithDirectDebitActiveStatus

Happy path - Succeeds if valid accountId in path parameter returns direct-debits with status Active in response body (accountToTest: AccountIdWithDirectDebitActiveStatus)

200

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

AIS_DD002

accountToTest: AccountIdWithDirectDebitInActiveStatus

Happy path - Succeeds if valid accountId in path parameter returns direct-debits with status Inactive in response body (accountToTest: AccountIdWithDirectDebitInActiveStatus)

200

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)

200

Returns a 200 status code with the specified number of accounts in each page and the meta information about the pagination

AIS_DD004

accountToTest: AccountIdWithDirectDebitAnnualFrequency

Happy path - Succeeds if valid accountId in path parameter returns direct-debits with Annual frequency in response body (accountToTest: AccountIdWithDirectDebitAnnualFrequency)

200

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

AIS_DD005

accountToTest: AccountIdWithDirectDebitDailyFrequency

Happy path - Succeeds if valid accountId in path parameter returns direct-debits with Daily frequency in response body (accountToTest: AccountIdWithDirectDebitDailyFrequency)

200

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

AIS_DD006

accountToTest: AccountIdWithDirectDebitFortnightlyFrequency

Happy path - Succeeds if valid accountId in path parameter returns direct-debits with Fortnightly frequency in response body (accountToTest: AccountIdWithDirectDebitFortnightlyFrequency)

200

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

AIS_DD007

accountToTest: AccountIdWithDirectDebitHalfYearlyFrequency

Happy path - Succeeds if valid accountId in path parameter returns direct-debits with HalfYearly frequency in response body (accountToTest: AccountIdWithDirectDebitHalfYearlyFrequency)

200

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

AIS_DD008

accountToTest: AccountIdWithDirectDebitMonthlyFrequency

Happy path - Succeeds if valid accountId in path parameter returns direct-debits with Monthly frequency in response body (accountToTest: AccountIdWithDirectDebitMonthlyFrequency)

200

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

AIS_DD009

accountToTest: AccountIdWithEmptyDirectDebits

Happy path - Succeeds if valid accountId provided in the path parameter which has a empty direct debits (accountToTest: AccountIdWithEmptyDirectDebits)

200

Valid accountId provided in the path parameter should return a 200 with an empty array if there are no direct-debits

DD_010_002

Ensure that the API correctly handles missing/invalid accountId path parameter.

AIS_DD010

accountToTest: Missing_AccountId

Negative Test - Fails if accountToTest path parameter is missing (accountToTest: Missing_AccountId)

401400

"If accountToTest path parameter is missing, the API must return a 401 400 and an error body"

AIS_DD011

accountToTest: Invalid_Single_AccountId

Negative Test - Fails if accountId format is invalid (accountToTest: Invalid_Single_AccountId)

400

"If the accountId format is invalid , the API must return a 400 and an error body"

DD_010_003

Ensure that the API correctly validates mandatory headers.

AIS_DD012

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing

AIS_DD013

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-api-uri header is missing

AIS_DD014

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest: SampleAccount)

400

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)

400

The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing

AIS_DD016

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing

AIS_DD017

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest: SampleAccount)

400

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)

400

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)

400

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)

400

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)

400

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)

400

"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)

400

"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)

400

"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)

400

"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)

400

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 - Fails if o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined (accountToTest: SampleAccount)"

400

"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_DD028

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)"

400

"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"

PRD_010_001

Ensure that valid accountId returns product details.

AIS_P001

accountToTest: Products_SampleAccount

Happy path - Succeeds if valid accountId provided in the path parameter which has products (accountToTest: Products_SampleAccount)

200

The operation must return a status code 200 and the products of the valid accountId

AIS_P002

accountToTest: AccountIdWithEmptyProducts

Happy path - Succeeds valid accountId provided in the path parameter which has an empty products (accountToTest: AccountIdWithEmptyProducts)

200

The operation must return a status code 200 and an empty array if the accountId has no products

PRD_010_002

Ensure that the API correctly handles missing/invalid accountId path parameter.

AIS_P003

accountToTest: NoAccount

Negative Test - Fails if accountIds path parameter is missing (accountToTest: NoAccount)

401400

"If accountIds path parameter is missing, the API must return a 401 400 and an error body"

AIS_P004

accountToTest: Invalid_Single_AccountId

Negative Test - Fails if accountId format is invalid (accountToTest: Invalid_Single_AccountId) (accountToTest: Invalid_Single_AccountId)

400

"If the accountId format is invalid , the API must return a 400 and an error body"

PRD_010_003

Ensure that the API correctly validates mandatory headers.

AIS_P005

accountToTest: NoAccount

Negative Test - Mandatory field validation - Fail if both accountId and o3-psu-identifier are missing (accountToTest: NoAccount)

400

The operation must fail with a status of 400 if both the accountId path parameter and the o3-psu-identifier header parameter are missing

AIS_P006

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing

AIS_P007

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-api-uri header is missing

AIS_P008

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-api-operation header is missing

AIS_P009

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing

AIS_P010

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing

AIS_P011

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-provider-id header has an unexpected value

AIS_P012

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-org-id header is missing

AIS_P013

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-client-id header is missing

AIS_P014

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is missing

AIS_P015

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-consent-id header is missing

AIS_P016

accountToTest: SampleAccount

Negative Test - Fails if o3-aspsp-id has an invalid value (accountToTest: SampleAccount)

400

"If o3-aspsp-id has an invalid value, the API must return a 400 and an error body"

AIS_P017

accountToTest: SampleAccount

Negative Test - Fails if o3-psu-identifier is not b64 encoded (accountToTest: SampleAccount)

400

"If o3-psu-identifier is not b64 encoded, the API must return a 400 and an error body"

AIS_P018

accountToTest: SampleAccount

Negative Test - Fails if o3-psu-identifier does not evaluate to a json structure (accountToTest: SampleAccount)

400

"If o3-psu-identifier does not evaluate to a json structure, the API must return a 400 and an error body"

AIS_P019

accountToTest: SampleAccount

Negative Test - Fails if o3-psu-identifier does not contain userId (accountToTest: SampleAccount)

400

"If o3-psu-identifier does not contain userId, the API must return a 400 and an error body"

AIS_P020

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)"

400

"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_P021

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)"

400

"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"

STO_010_001

Ensure that valid accountId returns standing-orders with active/inactive status and various types

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)

200

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

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)

200

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)

200

Returns a 200 status code with the specified number of accounts in each page and the meta information about the pagination

AIS_SO004

accountToTest: BetweenMyAccounts_StandingOrder

Happy path - Succeeds if valid accountId in path parameter returns standing-orders of BetweenMyAccounts type (accountToTest: BetweenMyAccounts_StandingOrder)

200

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

AIS_SO005

accountToTest: SameBankTransfer_StandingOrder

Happy path - Succeeds if valid accountId in path parameter returns standing-orders of SameBankTransfer type (accountToTest: SameBankTransfer_StandingOrder)

200

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

AIS_SO006

accountToTest: LocalBankTransfer_StandingOrder

Happy path - Succeeds if valid accountId in path parameter returns standing-orders of LocalBankTransfer type (accountToTest: LocalBankTransfer_StandingOrder)

200

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

AIS_SO007

accountToTest: AccountIdWithEmptyStandingOrders

Happy path - Succeeds if valid accountId in path parameter returns no standing-orders (accountToTest: AccountIdWithEmptyStandingOrders)

200

Valid accountId provided in the path parameter should return a 200 with an empty array if there are no standing-orders

STO_010_002

Ensure that the API correctly handles missing/invalid accountId path parameter.

AIS_SO008

Negative Test - Fails if accountIds path parameter is missing

401400

"If accountIds path parameter is missing, the API must return a 401 400 and an error body"

AIS_SO009

accountToTest: Invalid_Single_AccountId

Negative Test - Fails if accountId format is invalid (accountToTest: Invalid_Single_AccountId)

400

"If the accountId format is invalid , the API must return a 400 and an error body"

STO_010_003

Ensure that the API correctly validates mandatory headers.

AIS_SO010

accountToTest: NoAccount

Negative Test - Mandatory field validation - Fail if both accountId and o3-psu-identifier are missing (accountToTest: NoAccount)

400

The operation must fail with a status of 400 if both the accountId path parameter and the o3-psu-identifier header parameter are missing

AIS_SO011

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing

AIS_SO012

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-api-uri header is missing

AIS_SO013

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest: SampleAccount)

400

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)

400

The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing

AIS_SO015

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing

AIS_SO016

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest: SampleAccount)

400

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)

400

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)

400

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)

400

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)

400

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-psu-identifier is not b64 encoded (accountToTest: SampleAccount)

400

"If o3-psu-identifier is not b64 encoded, the API must return a 400 and an error body"

AIS_SO022

accountToTest: SampleAccount

Negative Test - Fails if o3-psu-identifier does not evaluate to a json structure (accountToTest: SampleAccount)

400

"If o3-psu-identifier does not evaluate to a json structure, the API must return a 400 and an error body"

AIS_SO023

accountToTest: SampleAccount

Negative Test - Fails if o3-psu-identifier does not contain userId (accountToTest: SampleAccount)

400

"If o3-psu-identifier does not contain userId, the API must return a 400 and an error body"

AIS_SO024

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)"

400

"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_SO025

(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)"

400

"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"

TXN_010_001

Ensure that valid accountId returns transaction details.

AIS_T001

accountToTest: Transactions_SampleAccount

Happy Path - Succeeds if valid accountId in path parameter returns transactions (accountToTest: Transactions_SampleAccount)

200

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

AIS_T002

accountToTest: AccountIdWithEmptyTransactions

Happy path - Succeeds if valid accountId in path parameter returns no transactions (accountToTest: AccountIdWithEmptyTransactions)

200

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)

200

Returns a 200 status code with the specified number of accounts in each page and the meta information about the pagination

AIS_T004

accountToTest: Transactions_SampleAccount

Happy Path - Filter transactions based on fromBookingDateTime query param (accountToTest: Transactions_SampleAccount)

200

Returns a 200 with list of transactions from fromBookingDateTime until latest available transaction

AIS_T005

accountToTest: Transactions_SampleAccount

Happy Path - Filter transactions based on toBookingDateTime query param (accountToTest: Transactions_SampleAccount)

200

Returns a 200 with list of transactions from the earliest available transaction till toBookingDateTime

AIS_T006

accountToTest: Transactions_SampleAccount

Happy Path - Filter transactions based on fromBookingDateTime and toBookingDateTime query params (accountToTest: Transactions_SampleAccount)

200

Returns a 200 with list of transactions within fromBookingDateTime and toBookingDateTime query params

TXN_010_002

Ensure API returns error from date query params are not valid

AIS_T007

accountToTest: SampleAccount

Negative Test - Fails if toBookingDateTime is before fromBookingDateTime (accountToTest: SampleAccount)

400

"If toBookingDateTime is before fromBookingDateTime, the API must return a 400 and an error body"

TXN_010_003

Ensure that the API correctly handles missing/invalid accountId path parameter.

AIS_T008

accountToTest: SampleAccount

Negative Test - Fails if accountIds path parameter is missing (accountToTest: SampleAccount)

401400

"If accountIds path parameter is missing, the API must return a 401 400 and an error body"

AIS_T009

accountToTest: Invalid_Single_AccountId

Negative Test - Fails if accountId format is invalid (accountToTest: Invalid_Single_AccountId)

400

"If the accountId format is invalid , the API must return a 400 and an error body"

TXN_010_004

Ensure that the API correctly validates mandatory headers.

AIS_T010

accountToTest: NoAccount

Negative Test - Mandatory field validation - Fail if both accountId and o3-psu-identifier are missing (accountToTest: NoAccount)

400

The operation must fail with a status of 400 if both the accountId path parameter and the o3-psu-identifier header parameter are missing

AIS_T011

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing

AIS_T012

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-api-uri header is missing

AIS_T013

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest: SampleAccount)

400

TThe operation must fail with a status code 400 and error body if the o3-api-operation header is missing

AIS_T014

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing

AIS_T015

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing

AIS_T016

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-provider-id header has an unexpected value

AIS_T017

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-org-id header is missing

AIS_T018

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-client-id header is missing

AIS_T019

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-caller-software-statement-id header is missing

AIS_T020

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-consent-id header is missing

AIS_T021

accountToTest: SampleAccount

Negative Test - Fails if o3-psu-identifier is not b64 encoded (accountToTest: SampleAccount)

400

"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)

400

"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)

400

"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 o3-psu-identifier header is invalid - the decoded value is valid JSON, but userId is null, empty or undefined (accountToTest: SampleAccount)"

400

"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_T025

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)"

400

"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"

SCP_010_001

Ensure that valid accountId returns scheduled-payments. Multiple tests are included to cover various types and handle the scenario to run empty response when no SPs are found.

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)

200

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

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)

200

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)

200

Returns a 200 status code with the specified number of accounts in each page and the meta information about the pagination

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)

200

Valid accountId provided in the path parameter should return a 200 and the scheduled-payments must have the correct creditor account identification IBAN

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)

200

Valid accountId provided in the path parameter should return a 200 and the scheduled-payments must have the correct creditor account identification AccountNumber

AIS_SP006

accountToTest: AccountIdWithEmptyScheduledPayments

Happy path - Succeeds if valid accountId in path parameter returns no scheduled-payments (accountToTest: AccountIdWithEmptyScheduledPayments)

200

Valid accountId provided in the path parameter should return a 200 with an empty array if there are no scheduled-payments

SCP_010_002

Ensure that the API correctly handles missing/invalid accountId path parameter.

AIS_SP007

accountToTest: NoAccount

Negative Test - Fails if accountIds path parameter is missing (accountToTest: NoAccount)

401400

"If accountIds path parameter is missing, the API must return a 401 400 and an error body"

AIS_SP008

accountToTest: Invalid_Single_AccountId

Negative Test - Fails if accountId format is invalid (accountToTest: Invalid_Single_AccountId)

400

"If the accountId format is invalid , the API must return a 400 and an error body"

SCP_010_003

Ensure that the API correctly validates mandatory headers.

AIS_SP009

accountToTest: NoAccount

Negative Test - Mandatory field validation - Fail if both accountId and o3-psu-identifier are missing (accountToTest: NoAccount)

400

The operation must fail with a status of 400 if both the accountId path parameter and the o3-psu-identifier header parameter are missing

AIS_SP010

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-psu-identifier header is missing

AIS_SP011

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-api-uri header is missing

AIS_SP012

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (accountToTest: SampleAccount)

400

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)

400

The operation must fail with a status code 400 and error body if the o3-aspsp-id header is missing

AIS_SP014

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (accountToTest: SampleAccount)

400

The operation must fail with a status code 400 and error body if the o3-ozone-interaction-id header is missing

AIS_SP015

accountToTest: SampleAccount

Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (accountToTest: SampleAccount)

400

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)

400

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)

400

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)

400

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)

400

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-psu-identifier is not b64 encoded (accountToTest: SampleAccount)

400

"If o3-psu-identifier is not b64 encoded, the API must return a 400 and an error body"

AIS_SP021

accountToTest: SampleAccount

Negative Test - Fails if o3-psu-identifier does not evaluate to a json structure (accountToTest: SampleAccount)

400

"If o3-psu-identifier does not evaluate to a json structure, the API must return a 400 and an error body"

AIS_SP022

accountToTest: SampleAccount

Negative Test - Fails if o3-psu-identifier does not contain userId (accountToTest: SampleAccount)

400

"If o3-psu-identifier does not contain userId, the API must return a 400 and an error body"

AIS_SP023

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)"

400

"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_SP024

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)"

400

"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"

RFD_010_001

Ensure that the payment refund process for fixed-defined schedules operates correctly when a valid request is made.

The tests include consent event and action calls with respect to refund process.

PIS_PRVAL001

paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user

POST /validate : Happy Path - Succeeds with a valid request containing all the valid details for fixed-Defined-schedule (paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user)

200

The operation must succeed with a status code 200 if the data is valid.

PIS_PRAUG002

paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user

POST /augment : Happy Path - Verify augmentation of additional information in consent for fixed-Defined-schedule (paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user)

200

The operation must succeed with a status code 200 if the data is valid.

Before_PREV003

POST /event/patch: Happy Path - Succeed if the event is successfully sent to notify that the consent is created in the Authorized state with an empty response body for fixed defined schedule

204

Ozone will successfully send an event to notify that the consent is created in the Authorized state with an empty response body (status code 204) after hitting the /event/post endpoint

PIS_PR004

GET /refund: Happy Path - Verify that the payment refund endpoint successfully returns a response when a valid consentId is provided

200

"Ensure that when a valid consentId is provided as a path parameter, the payment refund endpoint returns a 200 status code, and the response contains details of the debtor."

PIS_PR005

GET /refund: Happy Path - Verify that the payment refund endpoint successfully returns an empty response when an invalid consentId is provided

200

"Ensure that when an invalid consentId is provided as a path parameter, the payment refund endpoint returns a 200 status code, and the response contains an empty data object."

RFD_010_002

Ensure that the API returns error when consentId path param is missing

PIS_PR006

GET /refund: Negative Test - Verify that the payment refund endpoint fails when the consentId path parameter is missing

401400

Ensure the endpoint fails with a 401 400 status code when the consentId path parameter is missing.

RFD_010_003

Ensure that the API correctly validates mandatory headers.

PIS_PR007

GET /refund : Negative Test - Mandatory header validation - Fail if o3-api-uri header is missing (paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user

400

The operation must fail with a status code 400 if the o3-api-uri header is missing

PIS_PR008

paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user

GET /refund : Negative Test - Mandatory header validation - Fail if o3-psu-identifier header is missing (paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user)

400

The operation must fail with a status code 400 if the o3-psu-identifier header is missing

PIS_PR009

paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user

GET /refund : Negative Test - Mandatory header validation - Fail if o3-api-operation header is missing (paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user)

400

TThe operation must fail with a status code 400 if the o3-api-operation header is missing

PIS_PR010

paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user

GET /refund : Negative Test - Mandatory header validation - Fail if o3-aspsp-id header is missing (paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user)

400

The operation must fail with a status code 400 if the o3-aspsp-id header is missing

PIS_PR011

paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user

GET /refund : Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user)

400

The operation must fail with a status code 400 if the o3-ozone-interaction-id header is missing

PIS_PR012

paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user

GET /refund : Negative Test - Mandatory header validation - Fail if o3-provider-id header is missing (paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user)

400

The operation must fail with a status code 400 if the o3-provider-id header has an unexpected value

PIS_PR013

paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user

GET /refund : Negative Test - Mandatory header validation - Fail if o3-caller-org-id header is missing (paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user)

400

The operation must fail with a status code 400 if the o3-caller-org-id header is missing

PIS_PR014

paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user

GET /refund : Negative Test - Mandatory header validation - Fail if o3-caller-client-id header is missing (paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user)

400

The operation must fail with a status code 400 if the o3-caller-client-id header is missing

PIS_PR015

paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user

GET /refund : Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user)

400

The operation must fail with a status code 400 if the o3-caller-software-statement-id header is missing

PIS_PR016

paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user

GET /refund : Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user)

400

The operation must fail with a status code 400 if the o3-consent-id header is missing

PIS_PR017

paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user

GET /refund : Negative Test - Mandatory header validation - Fail if o3-caller-interaction-id header is missing (paymentToTest: event-Authorized-payment-refund-for-fixed-defined-schedule-retail-user)

400

The operation must fail with a status code 400 if the o3-caller-interaction-id header is missing

RPF_010_001

Ensure the API returns success response for a valid paymentId

PIS_RFP001

paymentToTest: SamplePaymentId_ReportFile

GET : Happy Path - Succeeds if valid paymentId in path parameter returns file name (paymentToTest: SamplePaymentId_ReportFile)

200

Valid paymentId provided in the path parameter should return a 200 and the file name must be present in the response

RPF_010_002

Ensure the API returns error response for an invalid/missing paymentId

PIS_RFP002

paymentToTest: InvalidPaymentId_ReportFile

GET : Negative Test - Invalid paymentId in path parameter (paymentToTest: InvalidPaymentId_ReportFile)

400

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)

401400

The paymentId in the path parameter is missing, should return a 401 400 status code

INS_010_001

Ensure the API returns success response for GET /motor-insurance-policies/{InsurancePolicyId}/customer-payment-details

The tests also also cover consent action and even calls related to the insurance payment details

INS_VAL001

insuranceToTest: event_insurance-AwaitingAuthorization-all-permissions

"POST /validate : Happy Path : Success when consent data is valid, allowing creation of consent in the AwaitingAuthorization state for a insurance data sharing(insuranceToTest: event_insurance-AwaitingAuthorization-all-permissions)"

200

The operation must succeed with a status code 200 if the consent data is valid

INS_AUG002

insuranceToTest: event_insurance-AwaitingAuthorization-all-permissions

POST /augment: Happy Path - Success when the augment endpoint is invoked for an insurance consent in AwaitingAuthorisation state (insuranceToTest: event_insurance-AwaitingAuthorization-all-permissions)

200

TThe operation should succeed with a status code 200 if the response contains the necessary fields to augment the consent

INS_EV003

insuranceToTest: event_insurance-AwaitingAuthorization-all-permissions

POST /event/post: Happy Path - Succeed if the event is successfully sent to notify that the consent is created in the AwaitingAuthorisation state with an empty response body for a insurance data sharing(insuranceToTest: event_insurance-AwaitingAuthorization-all-permissions)

204

Ozone will successfully send an event to notify that the consent is created in the AwaitingAuthorisation state with an empty response body (status code 204) after hitting the /event/post endpoint.

INS_EV004

insuranceToTest: event_insurance-Authorized-all-permissions

POST /event/patch: Happy Path - Succeed if the event is successfully sent to notify that the consent is created in the Authorized state with an empty response body for a insurance data sharing (insuranceToTest: event_insurance-Authorized-all-permissions)

204

Ozone will successfully send an event to notify that the consent is created in the Authorized state with an empty response body (status code 204) after hitting the /event/patch endpoint

INS_005

insuranceToTest: valid_insurancePolicyId-all-permissions

GET /motor-insurance-policies/{InsurancePolicyId}/customer-payment-details : Happy Path : Succeeds if a valid insurance policy ID is provided and returns the correct customer payment details (insuranceToTest: valid_insurancePolicyId-all-permissions)

200

The endpoints returns a status code of 200 and the correct customer payment details when a valid InsurancePolicyId is provided in the request path

INS_010_002

Ensure the API returns error response for GET /motor-insurance-policies/{InsurancePolicyId}/customer-payment-details with an invalid insurancePolicyId

INS_006

insuranceToTest: Invalid-insurancePolicyId-all-permissions

"GET /motor-insurance-policies/{InsurancePolicyId}/customer-payment-details: Negative Test - Returns an error response if a invalid InsurancePolicyId, with a length greater than 128 characters, is provided in the path (insuranceToTest: Invalid-insurancePolicyId-all-permissions)"

400

Returns a status code of 400 with the appropriate error details for an invalid InsuranceId with a length greater than the maximum specified

INS_007

insuranceToTest: no-insurancePolicyId-all-permissions

GET /motor-insurance-policies/{InsurancePolicyId}/customer-payment-details: Negative Test - Returns an error response if a InsurancePolicyId path parameter is missing (insuranceToTest: no-insurancePolicyId-all-permissions)

401400

Returns a status code of 401 400 for a missing insurance policy ID as path parameter

INS_010_003

Ensure API returns error mandatory fields are missing for consent event patch related to customer payment details

INS_EV008

insuranceToTest: event_insurance-AwaitingAuthorization-all-permissions

POST event/patch: Negative Test - Verify that the endpoint throws error when mandatory fields are missing for insurance data sharing (insuranceToTest: event_insurance-AwaitingAuthorization-all-permissions)

400

The endpoint responds with a 400 status code when mandatory fields are missing from the request payload

INS_010_004

Ensure the API returns success response for GET /motor-insurance-policies

INS_009

GET /motor-insurance-policies: Happy Path - Succeeds if the list of insurance policies for a valid o3-consent-id provided in the header

200

"The request returns a status code of 200, and the data object should be an array containing the list of insurance policies corresponding to the provided o3-consent-id in the header"

INS_010_005

Ensure the API returns error response for GET /motor-insurance-policies when page and page-size are missing

INS_010

GET /motor-insurance-policies: Negative Test - Verify the endpoint throws an error if the page and page-size query parameters are missing

400

The request returns a status code of 400 with the appropriate error details when the page and page-size query parameters are missing

INS_010_006

Ensure the API returns success response for GET /motor-insurance-policies/{InsurancePolicyId}

INS_011

insuranceToTest: valid_insurancePolicyId-all-permissions

GET /motor-insurance-policies/{InsurancePolicyId} : Happy Path : Succeeds if a valid insurance policy ID as path parameter is provided (insuranceToTest: valid_insurancePolicyId-all-permissions)

200

The endpoints returns a status code of 200 when a valid InsurancePolicyId is provided in the request path

INS_010_007

Ensure the API returns error response for GET /motor-insurance-policies/{InsurancePolicyId} for an invalid InsurancePolicyId

INS_012

insuranceToTest: Invalid-insurancePolicyId-all-permissions

"GET /motor-insurance-policies/{InsurancePolicyId}: Negative Test - Returns an error response if a invalid InsurancePolicyId, with a length greater than 128 characters, is provided in the path (insuranceToTest: Invalid-insurancePolicyId-all-permissions)"

400

Returns a status code of 400 with the appropriate error details for an invalid InsuranceId with a length greater than the maximum specified

INS_010_008

Ensure the API returns error response for GET /motor-insurance-policies/{InsurancePolicyId} for a missing InsurancePolicyId

INS_013

insuranceToTest: no-insurancePolicyId-all-permissions

GET /motor-insurance-policies/{InsurancePolicyId}: Negative Test - Returns an error response if a InsurancePolicyId path parameter is missing (insuranceToTest: no-insurancePolicyId-all-permissions)

401400

Returns a status code of 400 for a missing insurance policy ID as path parameter

INS_010_009

Ensure the API returns error for missing / invalid mandatory field validations

INS_014

GET /motor-insurance-policies/{InsurancePolicyId}/customer-payment-details : Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (insuranceToTest: valid_insurancePolicyId-all-permissions

400

The operation must fail with a status code 400 if the o3-ozone-interaction-id header is missing

INS_015

insuranceToTest: valid_insurancePolicyId-all-permissions

GET /motor-insurance-policies/{InsurancePolicyId}/customer-payment-details : Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (insuranceToTest: valid_insurancePolicyId-all-permissions)

400

The operation must fail with a status code 400 if the o3-consent-id header is missing

INS_016

insuranceToTest: valid_insurancePolicyId-all-permissions

GET /motor-insurance-policies/{InsurancePolicyId}/customer-payment-details : Negative Test - Mandatory header validation - Fail if o3-caller-interaction-id header is missing (insuranceToTest: valid_insurancePolicyId-all-permissions)

400

TThe operation must fail with a status code 400 if the o3-caller-interaction-id header is missing

INS_017

insuranceToTest: valid_insurancePolicyId-all-permissions

GET /motor-insurance-policies/{InsurancePolicyId}/customer-payment-details : Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (insuranceToTest: valid_insurancePolicyId-all-permissions)

400

The operation must fail with a status code 400 if the o3-caller-software-statement-id header is missing

INS_018

GET /motor-insurance-policies : Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (insuranceToTest: valid_insurancePolicyId-all-permissions

400

The operation must fail with a status code 400 if the o3-ozone-interaction-id header is missing

INS_019

insuranceToTest: valid_insurancePolicyId-all-permissions

GET /motor-insurance-policies : Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (insuranceToTest: valid_insurancePolicyId-all-permissions)

400

The operation must fail with a status code 400 if the o3-consent-id header is missing

INS_020

insuranceToTest: valid_insurancePolicyId-all-permissions

GET /motor-insurance-policies : Negative Test - Mandatory header validation - Fail if o3-caller-interaction-id header is missing (insuranceToTest: valid_insurancePolicyId-all-permissions)

400

TThe operation must fail with a status code 400 if the o3-caller-interaction-id header is missing

INS_021

insuranceToTest: valid_insurancePolicyId-all-permissions

GET /motor-insurance-policies : Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (insuranceToTest: valid_insurancePolicyId-all-permissions)

400

The operation must fail with a status code 400 if the o3-caller-software-statement-id header is missing

INS_022

GET /motor-insurance-policies/{InsurancePolicyId} : Negative Test - Mandatory header validation - Fail if o3-ozone-interaction-id header is missing (insuranceToTest: valid_insurancePolicyId-all-permissions

400

The operation must fail with a status code 400 if the o3-ozone-interaction-id header is missing

INS_023

insuranceToTest: valid_insurancePolicyId-all-permissions

GET /motor-insurance-policies/{InsurancePolicyId} : Negative Test - Mandatory header validation - Fail if o3-consent-id header is missing (insuranceToTest: valid_insurancePolicyId-all-permissions)

400

The operation must fail with a status code 400 if the o3-consent-id header is missing

INS_024

insuranceToTest: valid_insurancePolicyId-all-permissions

GET /motor-insurance-policies/{InsurancePolicyId} : Negative Test - Mandatory header validation - Fail if o3-caller-interaction-id header is missing (insuranceToTest: valid_insurancePolicyId-all-permissions)

400

TThe operation must fail with a status code 400 if the o3-caller-interaction-id header is missing

INS_025

insuranceToTest: valid_insurancePolicyId-all-permissions

GET /motor-insurance-policies/{InsurancePolicyId} : Negative Test - Mandatory header validation - Fail if o3-caller-software-statement-id header is missing (insuranceToTest: valid_insurancePolicyId-all-permissions)

400

The operation must fail with a status code 400 if the o3-caller-software-statement-id header is missing