diff --git a/code/Test_Definitions/NumberVerification_verify.feature b/code/Test_Definitions/NumberVerification_verify.feature
index 5aac7d7..f5ec5df 100644
--- a/code/Test_Definitions/NumberVerification_verify.feature
+++ b/code/Test_Definitions/NumberVerification_verify.feature
@@ -54,7 +54,6 @@ Feature: Camara Number Verification API verify
     And they acquired a valid access token associated with NUMBERVERIFY_VERIFY_MATCH_PHONENUMBER1 through OIDC authorization code flow
     And one of the scopes associated with the access token is number-verification:verify
     When the HTTPS "POST" request is sent
-    And the mobile connection is associated with NUMBERVERIFY_VERIFY_MATCH_PHONENUMBER1
     And the request body has the field phoneNumber with a value of NUMBERVERIFY_VERIFY_MATCH_PHONENUMBER1
     And the response header "x-correlator" has same value as the request header "x-correlator"
     And the response header "Content-Type" is "application/json"
@@ -70,7 +69,6 @@ Feature: Camara Number Verification API verify
     And they acquired a valid access token associated with NUMBERVERIFY_VERIFY_MATCH_PHONENUMBER1 through OIDC authorization code flow
     And one of the scopes associated with the access token is number-verification:verify
     When the HTTPS "POST" request is sent
-    And the mobile connection is associated with NUMBERVERIFY_VERIFY_MATCH_PHONENUMBER1
     And the request body has the field phoneNumber with a value of NUMBERVERIFY_VERIFY_MATCH_PHONENUMBER2
     And the response header "x-correlator" has same value as the request header "x-correlator"
     And the response header "Content-Type" is "application/json"
@@ -85,7 +83,6 @@ Feature: Camara Number Verification API verify
     And they acquired a valid access token associated with NUMBERVERIFY_VERIFY_MATCH_PHONENUMBER1 through OIDC authorization code flow
     And one of the scopes associated with the access token is number-verification:verify
     When the HTTPS "POST" request is sent
-    And the mobile connection is associated with NUMBERVERIFY_VERIFY_MATCH_PHONENUMBER1
     And the request body has NO the field phoneNumber
     And the response header "x-correlator" has same value as the request header "x-correlator"
     And the response header "Content-Type" is "application/json"
@@ -102,7 +99,6 @@ Feature: Camara Number Verification API verify
     And they acquired a valid access token associated with NUMBERVERIFY_VERIFY_MATCH_PHONENUMBER1 through OIDC authorization code flow
     And none of the scopes associated with the access token is number-verification:verify
     When the HTTPS "POST" request is sent
-    And the mobile connection is associated with NUMBERVERIFY_VERIFY_MATCH_PHONENUMBER1
     And the request body has the field phoneNumber with a value of NUMBERVERIFY_VERIFY_MATCH_PHONENUMBER1
     And the response header "x-correlator" has same value as the request header "x-correlator"
     And the response header "Content-Type" is "application/json"
@@ -120,7 +116,6 @@ Feature: Camara Number Verification API verify
     And one of the scopes associated with the access token is number-verification:verify
     When the HTTPS "POST" request is sent
     And the access token has expired
-    And the mobile connection is associated with NUMBERVERIFY_VERIFY_MATCH_PHONENUMBER1
     And the request body has the field phoneNumber with a value of NUMBERVERIFY_VERIFY_MATCH_PHONENUMBER
     And the response header "x-correlator" has same value as the request header "x-correlator"
     And the response header "Content-Type" is "application/json"