From cac1b677bbd902b53c778005985177a29e273aea Mon Sep 17 00:00:00 2001
From: krishvenkatachalam
<110808744+krishvenkatachalam@users.noreply.github.com>
Date: Thu, 27 Jun 2024 10:24:35 +0530
Subject: [PATCH 1/4] Update IMEI Fraud.md
https://github.com/camaraproject/APIBacklog/issues/63
---
documentation/API proposals/IMEI Fraud.md | 21 +++++++++++++++------
1 file changed, 15 insertions(+), 6 deletions(-)
diff --git a/documentation/API proposals/IMEI Fraud.md b/documentation/API proposals/IMEI Fraud.md
index 03a8f94..825aed4 100644
--- a/documentation/API proposals/IMEI Fraud.md
+++ b/documentation/API proposals/IMEI Fraud.md
@@ -5,10 +5,19 @@ IMEI Fraud API submission
| API name | IMEI Fraud|
| API owner | MTN - Waseem Amra |
| Initial API Contributors | MTN - Waseem Amra |
-| API summary | This API allows for the API Consumer to understand if any fraud markers have been associated with the device. Fraud markers may be applied if the device is lost, suspended, stolen, blacklisted, etc. |
-| Technical viability | This API uses IMEI info, usually stored by the MNO, to determine whether any fraud markers are associated with the device |
+| API summary | This API enables the API Consumer to determine whether fraud has been reported for the connected device. It will use the MSISDN or/ IMEI to check if the associated device has been reported as lost, suspended, stolen, blacklisted.
+
+Use case – account takeover, online registration |
+| Technical viability | This API uses IMEI info, usually stored by the MNO, to determine whether any fraud logs are associated with the device.
+
+Input: MSISDN & or IMEI number
+
+Output:
+
+Status: e.g. Blocked, lost,stolen, blacklisted etc
+Date_reported:10-01-2023 |
| Commercial viability | Customer demand has been validated |
-| YAML code available? | No - To be provided |
-| Validated in lab/productive environments? | No |
-| Validated with real customers? | Yes |
-| Validated with operators? | No |
+| YAML code available? | yes Updated yaml provided |
+| Validated in lab/productive environments? | No In Commercial network |
+| Validated with real customers? | YES – Banks from different markets as part of GSMA fintech stream in SA markets |
+| Validated with operators? | yes South African MNOs will support |
From 526b3f312ab97d4ed31059457fe973f0cc488e78 Mon Sep 17 00:00:00 2001
From: krishvenkatachalam
<110808744+krishvenkatachalam@users.noreply.github.com>
Date: Thu, 27 Jun 2024 10:29:13 +0530
Subject: [PATCH 2/4] Add files via upload
https://github.com/camaraproject/APIBacklog/issues/63
---
.../chenosis_mtn_imei_fraud_check_v1.yml | 321 ++++++++++++++++++
1 file changed, 321 insertions(+)
create mode 100644 documentation/SupportingDocuments/chenosis_mtn_imei_fraud_check_v1.yml
diff --git a/documentation/SupportingDocuments/chenosis_mtn_imei_fraud_check_v1.yml b/documentation/SupportingDocuments/chenosis_mtn_imei_fraud_check_v1.yml
new file mode 100644
index 0000000..ff0be37
--- /dev/null
+++ b/documentation/SupportingDocuments/chenosis_mtn_imei_fraud_check_v1.yml
@@ -0,0 +1,321 @@
+openapi: 3.0.1
+info:
+ title: Uganda IMEI Fraud Check API
+ description: |
+ API that allows the client to check the status and authenticity of mobile devices (using IMEI) to see if they have ever been used fraudulently, stolen, lost, or blacklisted.
+ Preprod: https://preprod.api.chenosis.io
+ Prod: https://api.chenosis.io
+ contact:
+ email: engineering@chenosis.io
+ version: "0.1"
+servers:
+- url: https://api.chenosis.io/v1/mtn/imei-information
+security:
+- OAuth2: []
+paths:
+ /status:
+ post:
+ parameters:
+ - name: transactionId
+ in: header
+ schema:
+ type: string
+ requestBody:
+ description: Request body
+ content:
+ application/json:
+ schema:
+ $ref: '#/components/schemas/Request'
+ required: true
+ responses:
+ "200":
+ description: 200 response
+ content:
+ application/json:
+ schema:
+ $ref: '#/components/schemas/Response'
+ "400":
+ description: Bad Request
+ content:
+ application/json:
+ schema:
+ $ref: '#/components/schemas/Error400'
+ "401":
+ description: Unauthorized
+ content:
+ application/json:
+ schema:
+ $ref: '#/components/schemas/Error401'
+ "403":
+ description: Forbidden
+ content:
+ application/json:
+ schema:
+ $ref: '#/components/schemas/Error403'
+ "404":
+ description: Not Found
+ content:
+ application/json:
+ schema:
+ $ref: '#/components/schemas/Error404'
+ "405":
+ description: Not Allowed
+ content:
+ application/json:
+ schema:
+ $ref: '#/components/schemas/Error405'
+ "408":
+ description: Time out
+ content:
+ application/json:
+ schema:
+ $ref: '#/components/schemas/Error408'
+ "412":
+ description: Precondition Failed
+ content:
+ application/json:
+ schema:
+ $ref: '#/components/schemas/Error412'
+ "415":
+ description: Unsupported Media Type
+ content:
+ application/json:
+ schema:
+ $ref: '#/components/schemas/Error415'
+ "500":
+ description: Internal Server Error
+ content:
+ application/json:
+ schema:
+ $ref: '#/components/schemas/Error500'
+ "503":
+ description: Service Unavailable
+ content:
+ application/json:
+ schema:
+ $ref: '#/components/schemas/Error503'
+ x-codegen-request-body-name: body
+components:
+ schemas:
+ Request:
+ required:
+ - imeiNumber
+ type: object
+ properties:
+ imeiNumber:
+ type: string
+ description: imeiNumber
+ example: "35314711751552"
+ Response:
+ type: object
+ properties:
+ statusCode:
+ type: string
+ example: "0000"
+ statusMessage:
+ type: string
+ example: success
+ customerId:
+ type: string
+ description: request imei number
+ example: "35314711751552"
+ data:
+ type: object
+ properties:
+ date:
+ type: string
+ example: 2023-05-23 21:48:42
+ status:
+ type: string
+ example: Blocked
+ enum:
+ - lost
+ - stolen
+ - blacklisted
+ - blocked
+ - IMEI not flagged
+ timestamp:
+ type: string
+ example: 2023-12-05 02:24:57 AM
+ transactionId:
+ type: string
+ example: 279431ae-b38e-4560-85f9-9afc10681687
+ Error400:
+ type: object
+ properties:
+ statusCode:
+ type: string
+ example: "5000"
+ statusMessage:
+ type: string
+ example: Invalid or missing fields in the request body.
+ enum:
+ - Invalid or missing fields in the request body.
+ - Invalid JSON in the request body.
+ transactionId:
+ type: string
+ example: fg545f-cf4gg4fd55-fdg85hg6
+ Error401:
+ type: object
+ properties:
+ statusCode:
+ type: string
+ example: "4000"
+ statusMessage:
+ type: string
+ example: Unauthorised.
+ SupportMessage:
+ type: string
+ example: Did not provide a valid token
+ transactionId:
+ type: string
+ example: rrt-2055955879466555495-a-geu2-23563-1529151-598
+ Error403:
+ type: object
+ properties:
+ statusCode:
+ type: string
+ example: "6000"
+ statusMessage:
+ type: string
+ example: Forbidden
+ SupportMessage:
+ type: string
+ example: Did not provide a valid token
+ transactionId:
+ type: string
+ example: rrt-2055955879466555495-a-geu2-23563-1529151-598
+ Error404:
+ type: object
+ properties:
+ statusCode:
+ type: string
+ example: "5000"
+ statusMessage:
+ type: string
+ example: Not Found
+ SupportMessage:
+ type: string
+ example: Resource not found
+ transactionId:
+ type: string
+ example: rrt-2055955879466555495-a-geu2-23563-1529151-598
+ Error405:
+ type: object
+ properties:
+ statusCode:
+ type: string
+ example: "4001"
+ statusMessage:
+ type: string
+ example: Not Allowed
+ SupportMessage:
+ type: string
+ example: Invalid HTTP method
+ transactionId:
+ type: string
+ example: rrt-2055955879466555495-a-geu2-23563-1529151-598
+ Error408:
+ type: object
+ properties:
+ statusCode:
+ type: string
+ example: "3003"
+ statusMessage:
+ type: string
+ example: The request timed out.
+ SupportMessage:
+ type: string
+ example: The server took too long to respond.
+ transactionId:
+ type: string
+ example: rrt-2055955879466555495-a-geu2-23563-1529151-598
+ Error412:
+ type: object
+ properties:
+ statusCode:
+ type: string
+ example: "3006"
+ statusMessage:
+ type: string
+ example: Precondition failed
+ transactionId:
+ type: string
+ example: fg545f-cf4gg4fd55-fdg85hg6
+ Error415:
+ type: object
+ properties:
+ statusCode:
+ type: string
+ description: HTTP error code extension
+ example: "5000"
+ statusMessage:
+ type: string
+ description: Media type is not supported
+ example: Unsupported Media Type
+ SupportMessage:
+ type: string
+ description: Unsupported Media Type.It should be application/json
+ example: Unsupported Media Type.It should be application/json
+ transactionId:
+ type: string
+ description: Id for tracing.
+ example: rrt-2055955879466555495-a-geu2-23563-1529151-598
+ Error500:
+ type: object
+ properties:
+ statusCode:
+ type: string
+ description: |-
+ HTTP error code extension
+ 3000-Provider API Internal server error.
+ 3001-Processing error
+ 1005-Please retry
+ example: "3000"
+ enum:
+ - "3000"
+ - "3001"
+ - "1005"
+ statusMessage:
+ type: string
+ description: Brief description
+ example: System error
+ SupportMessage:
+ type: string
+ description: |-
+ More information on error
+ 3000-Provider API Internal server error.
+ 3001-Processing error
+ 1005-Please retry
+ example: Provider API Internal server error.
+ transactionId:
+ type: string
+ description: Id for tracing.
+ example: rrt-2055955879466555495-a-geu2-23563-1529151-598
+ Error503:
+ type: object
+ properties:
+ statusCode:
+ type: string
+ description: Service Unavailable
+ example: "5002"
+ statusMessage:
+ type: string
+ description: Service Unavailable
+ example: Service Unavailable
+ SupportMessage:
+ type: string
+ description: Service Unavailable
+ example: Provider API Service Unavailable.
+ transactionId:
+ type: string
+ description: Id for tracing.
+ example: rrt-2055955879466555495-a-geu2-23563-1529151-598
+ securitySchemes:
+ OAuth2:
+ type: oauth2
+ flows:
+ clientCredentials:
+ tokenUrl: https://api.chenosis.io/oauth/client/accesstoken?grant_type=client_credentials
+ scopes: {}
+x-original-swagger-version: "2.0"
From 4692559df95e31ef873d50e3b614c1384fc91490 Mon Sep 17 00:00:00 2001
From: Jorge Garcia Hospital
<129095857+jgarciahospital@users.noreply.github.com>
Date: Fri, 6 Sep 2024 10:41:52 +0200
Subject: [PATCH 3/4] Update documentation/API proposals/IMEI Fraud.md
Co-authored-by: Ricardo Serrano Gutierrez <145554214+TEF-RicardoSerr@users.noreply.github.com>
---
documentation/API proposals/IMEI Fraud.md | 13 ++-----------
1 file changed, 2 insertions(+), 11 deletions(-)
diff --git a/documentation/API proposals/IMEI Fraud.md b/documentation/API proposals/IMEI Fraud.md
index 825aed4..f0f9351 100644
--- a/documentation/API proposals/IMEI Fraud.md
+++ b/documentation/API proposals/IMEI Fraud.md
@@ -5,17 +5,8 @@ IMEI Fraud API submission
| API name | IMEI Fraud|
| API owner | MTN - Waseem Amra |
| Initial API Contributors | MTN - Waseem Amra |
-| API summary | This API enables the API Consumer to determine whether fraud has been reported for the connected device. It will use the MSISDN or/ IMEI to check if the associated device has been reported as lost, suspended, stolen, blacklisted.
-
-Use case – account takeover, online registration |
-| Technical viability | This API uses IMEI info, usually stored by the MNO, to determine whether any fraud logs are associated with the device.
-
-Input: MSISDN & or IMEI number
-
-Output:
-
-Status: e.g. Blocked, lost,stolen, blacklisted etc
-Date_reported:10-01-2023 |
+| API summary | This API enables the API Consumer to determine whether fraud has been reported for the connected device. It will use the MSISDN or/ IMEI to check if the associated device has been reported as lost, suspended, stolen, blacklisted.
Use case – account takeover, online registration |
+| Technical viability | This API uses IMEI info, usually stored by the MNO, to determine whether any fraud logs are associated with the device.
Input: MSISDN & or IMEI number.
Output: Status (e.g. Blocked,lost,stolen, blacklisted etc.) & Date_reported:10-01-2023 |
| Commercial viability | Customer demand has been validated |
| YAML code available? | yes Updated yaml provided |
| Validated in lab/productive environments? | No In Commercial network |
From c0db0510c6d81c80b7e254279533dbe195ec49e5 Mon Sep 17 00:00:00 2001
From: Jorge Garcia Hospital
<129095857+jgarciahospital@users.noreply.github.com>
Date: Fri, 6 Sep 2024 10:41:59 +0200
Subject: [PATCH 4/4] Update documentation/API proposals/IMEI Fraud.md
Co-authored-by: Ricardo Serrano Gutierrez <145554214+TEF-RicardoSerr@users.noreply.github.com>
---
documentation/API proposals/IMEI Fraud.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/documentation/API proposals/IMEI Fraud.md b/documentation/API proposals/IMEI Fraud.md
index f0f9351..aeabc6e 100644
--- a/documentation/API proposals/IMEI Fraud.md
+++ b/documentation/API proposals/IMEI Fraud.md
@@ -12,3 +12,4 @@ IMEI Fraud API submission
| Validated in lab/productive environments? | No In Commercial network |
| Validated with real customers? | YES – Banks from different markets as part of GSMA fintech stream in SA markets |
| Validated with operators? | yes South African MNOs will support |
+| Supporters in API Backlog Working Group | MTN, Chunghwa Telecom |