diff --git a/features/proof/findProofByPresentationId.feature b/features/proof/findProofByPresentationId.feature
index 3f79e64fd13c201d7770d7cb9ffc43c4b7d539bb..caf940c26dd123afebe3a854be78493c4f300de7 100644
--- a/features/proof/findProofByPresentationId.feature
+++ b/features/proof/findProofByPresentationId.feature
@@ -3,27 +3,32 @@ Feature: Get Proof Presentation By Id
 
 Scenario: Provide valid presentation id
     Given The presentation id is available on agent database.
+    # controller.ts-> Rest API with GET method -> find-by-presentation-id
     When  provide valid presentation id.
     Then  should return proof presentation details.
 
 Scenario: Provide invalid presentation id
     Given The presentation id available.
+    # controller.ts-> Rest API with GET method -> find-by-presentation-id
     When  provide invalid presentation id.
     Then  should return no data found with status code 404.
 
 Scenario: Provide validated page and pageSize
     Given proof presentation data available on OCM database. 
+    # controller.ts-> Rest API with GET method -> find-proof-presentation
     When  passed valid page.
     And   passed valid pageSize.
     Then  should get proof presentation list.
 
 Scenario: Provide validated page and pageSize
     Given proof presentation data is not available on OCM database.
+    # controller.ts-> Rest API with GET method -> find-proof-presentation
     When  passed valid page.
     And   passed valid pageSize.
     Then  should get http status 404.
     
 Scenario: Not provide a presentation id
     Given The presentation id available.
+    # controller.ts-> Rest API with GET method -> find-by-presentation-id
     When  not provide presentation id.
     Then  should return presentation request required following attributes ( presentation_id ) with status code 400.
\ No newline at end of file
diff --git a/features/proof/sendOutOfBandPresentationRequest.feature b/features/proof/sendOutOfBandPresentationRequest.feature
index b8c631cd566f1c2ef4bdd0cd413f428a57dd7fa9..6a47aafabde592bdd974b33fc912b80b8f1a7d08 100644
--- a/features/proof/sendOutOfBandPresentationRequest.feature
+++ b/features/proof/sendOutOfBandPresentationRequest.feature
@@ -3,6 +3,7 @@ As a OCM Admin
 
 Scenario: OCM admin verify credentials
     Given PCM user should hold credentials in there wallet.
+    # controller.ts-> Rest API with Post method -> send-out-of-band-presentation-request
     When  OCM verifer orgnization sends a proof presentation request with following fields ( schemaId or credentialDefId, attributes ) to PCM user.
     And   PCM user share the attributes from requested credentials to OCM verifer.
     And   OCM verifer verify the presentation acknowledgement.    
@@ -10,5 +11,16 @@ Scenario: OCM admin verify credentials
 
 Scenario: OCM admin verify credentials
     Given PCM user should hold credentials in there wallet.
+    # controller.ts-> Rest API with Post method -> accept-presentation
     When  OCM admin send a credential request to PCM user.
-    And   PCM user decline the credential request witch will requested from OCM admin.   
+    And   PCM user decline the credential request witch will requested from OCM admin. 
+
+
+    Scenario: OCM admin verify credentials agenst credentialType
+    Given PCM user should hold credentials in there wallet.
+    # controller.ts-> Rest API with Post method -> out-of-band-proof
+    When  OCM verifer orgnization sends a proof presentation request with following fields ( schemaId or credentialDefId, attributes ) to PCM user.
+    And   provide credentialType
+    And   PCM user share the attributes from requested credentials to OCM verifer.
+    And   OCM verifer verify the presentation acknowledgement.    
+    Then  Presentation request should be in 'verified' state.  
diff --git a/features/proof/sendPresentationRequest.feature b/features/proof/sendPresentationRequest.feature
index ad11156844ffbd25faba9d8ac50ae257d7dfc80b..b5b8a433669863359da1d6bc92ced360b3f4831c 100644
--- a/features/proof/sendPresentationRequest.feature
+++ b/features/proof/sendPresentationRequest.feature
@@ -4,6 +4,7 @@ As a OCM Admin
 Scenario: OCM admin verify credentials
     Given PCM user should hold credentials in there wallet.
     And   PCM user connection must be in trusted state with verifer.
+    # controller.ts-> Rest API with Post method -> send-presentation-request
     When  OCM verifer orgnization sends a proof presentation request with following fields ( connectionId, schemaId or credentialDefId, attributes ) to PCM user.
     And   PCM user share the attributes from requested credentials to OCM verifer.
     And   OCM verifer verify the presentation acknowledgement.    
diff --git a/features/proof/sendPrincipalCredentialPresentationRequest.feature b/features/proof/sendPrincipalCredentialPresentationRequest.feature
index fd68ed18adb523db49393e5dd4e4ba386c9c4ddc..c2f1aecd35dae64de219dd48d5a6fd89cdf0b935 100644
--- a/features/proof/sendPrincipalCredentialPresentationRequest.feature
+++ b/features/proof/sendPrincipalCredentialPresentationRequest.feature
@@ -4,6 +4,7 @@ Feature: I am able to prove as GAIA-X ecosystem member.
 Scenario: Make the existing connection trusted
     Given PCM user should hold principal membership credentials in there wallet.
     And   PCM user connection must be in complete state with verifer.
+    # Nats call on topic 'PROOF_MANAGER_SERVICE/sendMembershipProofRequest'
     When  OCM verifer orgnization sends a proof presentation request with following fields ( schemaId, attributes ) to PCM user.
     And   PCM user share the attributes from requested credentials to OCM verifer.
     And   OCM verifer verify the presentation acknowledgement.