You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Possible evolution
SIM SWAP API, as many other current APIs, may be enhanced by a subscription mechanism that will enable different use cases, e.g.:
Antifraud mechanism may require being notified by the operator when a SIM is affected by a swap procedure, implementing different mechanisms to avoid fraud (e.g., warm or confirm with the user).
The proposal includes examples or proposal for input-outputs of such mechanism, to be discussed and aligned with the current service API.
This feature will be managed in the SimSwap API Family.
We have to decide if we want to have the SimSwap Notification Subscription is the same yaml than current one (checkSimSwap.camara.swagger.yaml) or have a separate yaml.
Problem description
Formal inclusion of the GSMA OGW Product WS request to include Subscription/notification mechanism as part of OGW services.
camaraproject/Commonalities#8 (comment)
Possible evolution
SIM SWAP API, as many other current APIs, may be enhanced by a subscription mechanism that will enable different use cases, e.g.:
The proposal includes examples or proposal for input-outputs of such mechanism, to be discussed and aligned with the current service API.
Alternative solution
N/A
Additional context
More details included in the formal request file, attached
Camara Submission - Subscription_Notifications v2.docx
The text was updated successfully, but these errors were encountered: