Remove guides content duplicating references

Author: diegotid

v0/catalog/devicelocation/devicelocation.md

@@ -65,28 +65,3 @@ As a standardized API, it allows seamless integration into your applications wit
 
 ### Footprint for your identity service
 The API's standardization ensures uniform access across multiple telecom providers, expanding your business reach and ensuring consistent functionality across different carriers.
-
-## General Informations
-
-> ⚙️ Problem Solved
->
-> You want to verify that a device is where you expect it to be. The expected location can be the reported GPS coordinates, safe places to operate from (e.g. home address, workplace), etc.
-
-
-> ⚙️ How it works 
->
-> By providing latitude and longitude, it is checked whether the device is in that location.
-
-
-> ⚙️ Parameters sent in the request 
->
-> - msisdn (mobile phone number in the format: +551199999999) 
-> - latitude (latitude in the format: -23.5042623)
-> - longitude (longitude in the format -46.8575631)
-> - accuracy (precision of the radius of the circle in km: 2)
-
-
-> ⚙️ Data received in the response
->
-> If the device is not in the expected location, it returns verificationResult: false . If the device is in the expected location, the value is verificationResult: true .
-

v0/catalog/devicestatus/devicestatus.md

@@ -66,23 +66,3 @@ Since it is a standardized API, integration is straightforward and doesn’t req
 ### Unified Access to Telecom Functions
 
 The standardized API provides uniform access to other telecom capabilities, such as detecting if a user is roaming, through a single interface. This ensures consistency and flexibility across different carriers and markets.
-
-
-## General Informations
-
-> ⚙️ Problem Solved ? 
->
-> Check if a device is roaming or not.
-
-
-> ⚙️ Parameters sent in the request 
->
-> - msisdn (mobile phone number in the format - +551199999999) 
-> - eventType (Select the various events - In one of these patterns: ROAMING_STATUS or ROAMING_ON or ROAMING_OFF or ROAMING_CHANGE_COUNTRY )
-
-
-> ⚙️ Data received in the response
->
-> - If the device is roaming, it returns "roaming": true ;
-> - If the device is not roaming, returns "roaming": false.
-

v0/catalog/knowyourcustomer/knowyourcustomer.md

@@ -58,116 +58,3 @@ By using a standardized API, you can effortlessly incorporate the KYC-Match proc
 ### Footprint for your Identify Service​
 
 The standardized API provides uniform access to multiple telecom companies, broadening your business reach and ensuring consistent and flexible operations across different providers.
-
-
-
-## General Informations
-
-> ⚙️ Problem Solved ? 
->
-> Check if the user data is true or false.
-
-
-> ⚙️ Parameters sent in the request 
->
-> - idDocumentMatch (Indicates whether the ID number associated with the customer's ID document matches the one in the OB systems. Possible values: true, false, not_available)
-> - nameMatch (Indicates whether the customer's full name matches the one in the OB systems. Possible values: true, false, not_available)
-> - givenNameMatch (Indicates whether the customer's first name matches the one in the OB systems. Possible values: true, false, not_available)
-> - familyNameMatch (Indicates whether the customer's last name matches the one in the OB systems. Possible values: true, false, not_available)
-> - nameKanaHankakuMatch (Indicates whether the customer's full name in Hankaku-Kana format (name reading) for Japan matches the one in the OB systems. Possible values: true, false, not_available)
-> - nameKanaZenkakuMatch (Indicates whether the customer's full name in Zenkaku-Kana format (name reading) for Japan matches the one in the OB systems. Possible values: true, false, not_available)
-> - middleNamesMatch (Indicates whether the customer's middle names match the ones in the OB systems. Possible values: true, false, not_available)
-> - familyNameAtBirthMatch (Indicates whether the customer's family name at birth matches the one in the OB systems. Possible values: true, false, not_available)
-> - addressMatch (Indicates whether the customer's complete address matches the one in the OB systems. Possible values: true, false, not_available)
-> - streetNameMatch (Indicates whether the customer's street name matches the one in the OB systems. Possible values: true, false, not_available)
-> - streetNumberMatch (Indicates whether the customer's street number matches the one in the OB systems. Possible values: true, false, not_available)
-> - postalCodeMatch (Indicates whether the customer's postal code matches the one in the OB systems. Possible values: true, false, not_available)
-> - regionMatch (Indicates whether the region of the customer's address matches the one in the OB systems. Possible values: true, false, not_available)
-> - localityMatch (Indicates whether the locality of the customer's address matches the one in the OB systems. Possible values: true, false, not_available)
-> - countryMatch (Indicates whether the country of the customer's address matches the one in the OB systems. Possible values: true, false, not_available)
-> - houseNumberExtensionMatch (Indicates whether the house number extension of the customer's address matches the one in the OB systems. Possible values: true, false, not_available)
-> - birthdateMatch (Indicates whether the customer's birthdate matches the one in the OB systems. Possible values: true, false, not_available)
-> - emailMatch (Indicates whether the customer's email address matches the one in the OB systems. Possible values: true, false, not_available)
-> - genderMatch (Indicates whether the customer's gender matches the one in the OB systems. Possible values: true, false, not_available)
-
-
-
-> ⚙️ Data received in the response
->
-> - If the ID number associated with the customer's ID document matches the one in the OB systems, it returns "idDocumentMatch": true;
-> - If the ID number does not match, it returns "idDocumentMatch": false;
-> - If the ID number is not available, it returns "idDocumentMatch": not_available.
-
-> - If the customer's full name matches the one in the OB systems, it returns "nameMatch": true;
-> - If the full name does not match, it returns "nameMatch": false;
-> - If the full name is not available, it returns "nameMatch": not_available.
-
-> - If the customer's first name matches the one in the OB systems, it returns "givenNameMatch": true;
-> - If the first name does not match, it returns "givenNameMatch": false;
-> - If the first name is not available, it returns "givenNameMatch": not_available.
-
-> - If the customer's last name matches the one in the OB systems, it returns "familyNameMatch": true;
-> - If the last name does not match, it returns "familyNameMatch": false;
-> - If the last name is not available, it returns "familyNameMatch": not_available.
-
-> - If the customer's full name in Hankaku-Kana format (name reading) for Japan matches the one in the OB systems, it returns "nameKanaHankakuMatch": true;
-> - If the full name in Hankaku-Kana format does not match, it returns "nameKanaHankakuMatch": false;
-> - If the full name in Hankaku-Kana format is not available, it returns "nameKanaHankakuMatch": not_available.
-
-> - If the customer's full name in Zenkaku-Kana format (name reading) for Japan matches the one in the OB systems, it returns "nameKanaZenkakuMatch": true;
-> - If the full name in Zenkaku-Kana format does not match, it returns "nameKanaZenkakuMatch": false;
-> - If the full name in Zenkaku-Kana format is not available, it returns "nameKanaZenkakuMatch": not_available.
-
-> - If the customer's middle names match the ones in the OB systems, it returns "middleNamesMatch": true;
-> - If the middle names do not match, it returns "middleNamesMatch": false;
-> - If the middle names are not available, it returns "middleNamesMatch": not_available.
-
-> - If the customer's family name at birth matches the one in the OB systems, it returns "familyNameAtBirthMatch": true;
-> - If the family name at birth does not match, it returns "familyNameAtBirthMatch": false;
-> - If the family name at birth is not available, it returns "familyNameAtBirthMatch": not_available.
-
-> - If the customer's complete address matches the one in the OB systems, it returns "addressMatch": true;
-> - If the complete address does not match, it returns "addressMatch": false;
-> - If the complete address is not available, it returns "addressMatch": not_available.
-
-> - If the customer's street name matches the one in the OB systems, it returns "streetNameMatch": true;
-> - If the street name does not match, it returns "streetNameMatch": false;
-> - If the street name is not available, it returns "streetNameMatch": not_available.
-
-> - If the customer's street number matches the one in the OB systems, it returns "streetNumberMatch": true;
-> - If the street number does not match, it returns "streetNumberMatch": false;
-> - If the street number is not available, it returns "streetNumberMatch": not_available.
-
-> - If the customer's postal code matches the one in the OB systems, it returns "postalCodeMatch": true;
-> - If the postal code does not match, it returns "postalCodeMatch": false;
-> - If the postal code is not available, it returns "postalCodeMatch": not_available.
-
-> - If the region of the customer's address matches the one in the OB systems, it returns "regionMatch": true;
-> - If the region does not match, it returns "regionMatch": false;
-> - If the region is not available, it returns "regionMatch": not_available.
-
-> - If the locality of the customer's address matches the one in the OB systems, it returns "localityMatch": true;
-> - If the locality does not match, it returns "localityMatch": false;
-> - If the locality is not available, it returns "localityMatch": not_available.
-
-> - If the country of the customer's address matches the one in the OB systems, it returns "countryMatch": true;
-> - If the country does not match, it returns "countryMatch": false;
-> - If the country is not available, it returns "countryMatch": not_available.
-
-> - If the house number extension of the customer's address matches the one in the OB systems, it returns "houseNumberExtensionMatch": true;
-> - If the house number extension does not match, it returns "houseNumberExtensionMatch": false;
-> - If the house number extension is not available, it returns "houseNumberExtensionMatch": not_available.
-
-> - If the customer's birthdate matches the one in the OB systems, it returns "birthdateMatch": true;
-> - If the birthdate does not match, it returns "birthdateMatch": false;
-> - If the birthdate is not available, it returns "birthdateMatch": not_available.
-
-> - If the customer's email address matches the one in the OB systems, it returns "emailMatch": true;
-> - If the email address does not match, it returns "emailMatch": false;
-> - If the email address is not available, it returns "emailMatch": not_available.
-
-> - If the customer's gender matches the one in the OB systems, it returns "genderMatch": true;
-> - If the gender does not match, it returns "genderMatch": false;
-> - If the gender is not available, it returns "genderMatch": not_available.
-
-

v0/catalog/numberverification/numberverification.md

@@ -57,40 +57,3 @@ In today's digital landscape, verifying phone number ownership is critical to pr
 The Number Verification API utilizes telco mechanisms to authenticate users seamlessly based on their device's connection to the network. This method contrasts with traditional authentication solutions by enhancing user convenience and security. Unlike manual processes or plain-text codes, network-based validation requires no user interaction, bolstering protection against unauthorized access.
 
 This API verifies that the provided mobile phone number (MSISDN) matches the device initiating data communication, ensuring users interact with digital services from authenticated devices.
-
-
-## General Informations
-
-> ⚙️ Problem Solved ? 
->
-> When you want to validate the user's digital identity.
-
-
-> ⚙️ How it works 
->
-> - Check if the registered phone number matches the number provided by the operator
-> -  Excellent resource to reduce the number of steps when validating an application.
-
-
-> ⚙️ Parameters sent in the request 
->
-> - phoneNumber: “34612345678” (mobile phone number in the format - +551199999999)
-
-
-> ⚙️ Data received in the response
->
-> - POST 
->
->  {
->		"devicePhoneNumberVerified": true
->  }
->
-> - GET
->
->	{
->		"devicePhoneNumber": "+34612345678"
->	}
->
->
-
-

v0/catalog/simswap/simswap.md

@@ -72,34 +72,3 @@ This is where SIM swap fraud becomes dangerous. The "new" mobile phone can be us
 To safeguard against SIM swap fraud, it is crucial to be aware of how your personal and financial information is used and protected. Use strong, unique passwords for your accounts, enable two-factor authentication, and monitor your accounts for any suspicious activity. Always be cautious of unsolicited requests for personal information, whether over the phone, via SMS, or through email.
 
 By understanding the mechanics of SIM swap fraud and taking proactive steps to protect your accounts, you can significantly reduce the risk of falling victim to this type of cybercrime.
-
-
-## General Informations
-
-> ⚙️ Problem Solved ? 
->
-> When was the last SIM change?
-
-
-> ⚙️ How it works 
->
-> Checks when the last SIM Card exchange was carried out on a mobile line or if this exchange was carried out within a specific period
-
-> ⚙️ Parameters sent in the request 
->
-> - phoneNumber: Cell phone number that will be verified for exchange
-> -  maxAge: period of hours to be checked for SIM change (minimum 1 hour / maximum 2400 hours / default 240 hours)  
-
-
-> ⚙️ Data received in the response
->
-> Returns swapped true if the SIM Card was changed and swapped false if it was not changed 
-
-
-
-
-
-
-
-
-