# Acquirers: ORC API Testing source: https://developer.mastercard.com/onboard-risk-check/documentation/testing/orc/index.md ### Test scenarios {#test-scenarios}
Note: For more details on ICA, please refer to [Glossary](https://developer.mastercard.com/onboard-risk-check/documentation/glossary/index.md). ## Initiate Inquiry API endpoint {#initiate-inquiry-api-endpoint} | **Scenario No.** | **Scenario** | **Key Data** | **Sample Action** | **Pass Criteria** | |------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| | 1 | To ensure that the customer is onboarded to use the ORC API and able to make a valid POST Inquiries request for cyberHealth. | - cyberHealth specified in the options parameter - Requesting ICA - BusinessInfo populated with Merchant Name and Merchant URL - Auth header. | Make a request to the POST Endpoint /inquiries. | A response will be generated and a unique Inquiry Request Number will be returned with a HTTP status of 202. | | 2 | To ensure that the customer is onboarded to use the ORC API and able to make a valid POST Inquiries request for sanctionsScreening. | - sanctionsScreening specified in the options parameter - Requesting ICA - Mandatory fields in the businessInfo principalInfo criteria populated - Auth header. | Make a request to the POST Endpoint /inquiries. | A response will be generated and a unique Inquiry Request Number will be returned with a HTTP status of 202. | | 3 | To ensure that the customer is onboarded to use the ORC API and able to make a valid POST Inquiries request for businessIdentity. | - businessIdentity specified in the options parameter - Requesting ICA - Mandatory fields in the businessInfo criteria populated - Auth header. | Make a request to the POST Endpoint /inquiries. | A response will be generated and a unique Inquiry Request Number will be returned with a HTTP status of 202. | | 4 | To ensure that the customer is onboarded to use the ORC API and able to make a valid POST Inquiries request for cyberHealth, sanctionsScreening, and businessIdentity. | - cyberHealth, sanctionsScreening, and businessIdentity specified in the options parameter - Requesting ICA - Mandatory fields in the businessInfo principalInfo criteria populated - Auth header. | Make a request to the POST Endpoint /inquiries. | A response will be generated and a unique Inquiry Request Number will be returned with a HTTP status of 202. | | 5 | To ensure the customer is using valid fields and values. | - Options - Criteria - Requesting ICA. | Make a request to the POST Endpoint /inquiries. | A response will be generated for the following invalid or missing fields: - Requesting ICA - Options - Criteria 400 -- Bad Request. | | 6 | To ensure that the customer is using a valid ICA/CID. | - Consumer_Id header - Requesting ICA. | Make a request to the POST Endpoint /inquiries. | A response will be generated for the invalid ICA/CID with a HTTP status of 404 (NOT FOUND). | | | | | | | ## Retrieve Inquiry API endpoint {#retrieve-inquiry-api-endpoint} | **Scenario No.** | **Scenario** | **Key Data** | **Sample Action** | **Pass Criteria** | |------------------|-----------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| | 1 | To ensure that the customer is onboarded to use the ORC API and is able to make a valid Get Inquiries Request call. | You will need a valid IRN from an inquiry initiated in the past either from ORC or [MATCH](https://developer.mastercard.com/onboard-risk-check/documentation/glossary/index.md). Below is a valid IRN for a sandbox environment: ORC-09287349023423423. | Make a request to the Get endpoint to inquiries/IRN (inquiry reference number). | A response will be generated for the IRN with a HTTP status of 200 OK. | | 2 | To ensure that the customer is using a valid consumer key to pass authentication. | 1. Valid consumer key generated through Mastercard Developers project. 2. Valid IRN - ORC-09287349023423423. 3. Customer onboarding unsuccessful or incomplete. | Make a request to the Get endpoint to inquiries/IRN (inquiry reference number). | A response will be generated for the Invalid IRN with a HTTP status of 404 (NOT FOUND) since an approved consumer key was not found. | | 3 | To ensure that the customer is using a valid IRN. The IRN must be from a past inquiry initiated by the same customer. | 1. Valid consumer key generated through Mastercard Developers project. 2. Successful onboarding. 3. Invalid IRN, or, an IRN that doesn't belong to the same customer. For example, ORC-0928734902342342. | Make a request to the Get endpoint to inquiries/IRN (inquiry reference number). | A response will be generated for the Invalid IRN with a HTTP status of 404 (NOT FOUND) since an approved consumer key was not found. | | | | | | | ### Error codes and format {#error-codes-and-format} For details about the error format, refer to [Acquirers: Code and Formats](https://developer.mastercard.com/onboard-risk-check/documentation/code-and-formats/orc/index.md).