diff --git a/code/API_definitions/number-recycling.yaml b/code/API_definitions/number-recycling.yaml
index 2b3aa31..4ae3d71 100644
--- a/code/API_definitions/number-recycling.yaml
+++ b/code/API_definitions/number-recycling.yaml
@@ -59,6 +59,10 @@ info:
     In cases where personal data is processed by the API and users can exercise their rights through mechanisms such as opt-in and/or opt-out, the use of three-legged access tokens is mandatory. This ensures that the API remains in compliance with privacy regulations, upholding the principles of transparency and user-centric privacy-by-design.
     <!-- CAMARA:MANDATORY:authorization-and-authentication:END -->
 
+    Note: If sending an authentication message in CIBA is based on the MSISDN and the MSISDN was reassigned to a new subscriber, then
+    this defeats the purpose of the number recycling API which is to determine whether the MSISDN was reassigned.
+    If the ASP and the CSP know at onboarding time that User consent is not needed, then JWT-Bearer-Flow with tel-prefix is recommended to be used with number recycling.
+
     # Identifying the phone number from the access token
 
     This API requires the API consumer to identify a phone number as the subject of the API as follows: