-
Notifications
You must be signed in to change notification settings - Fork 46
Create APIproposal_Voice OTP Call #263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 3 commits
03b1810
2bd5b64
92d5b5b
2874f41
1ea62cd
3f7c0de
66e7e5b
369e172
68a16e0
30f744f
992df41
e9cb367
03461b5
03399a4
af8316a
92a07b1
c1da7c6
ae8875e
85c677c
e98cc0e
0e99810
924cc4a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,37 @@ | ||
| Description | ||
| ### API family name | ||
| Authentication and Fraud Prevention | ||
mbkhanhex marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| ### API Name | ||
mbkhanhex marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| Voice One-Time Password (OTP) Call | ||
mbkhanhex marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| ### API family owner | ||
| Heksagon | ||
| ### API summary | ||
| The “Voice One Time Password Call” API is used to send short-lived one time passwords (OTP) to a phone number via voice call and validate it afterwards, in order to provide a proof of possession of the phone number. | ||
| Voice OTP Call API performs real-time checks to verify that the user possessed the device that carries the indicated mobile phone number. It provides a frequent method of verifying possession of the device by delivering an OTP through voice call and validating it afterwards. | ||
| Voice OTP Call API is a secure method for providing one-time access to an application or performing a single transaction. As compared to One Time Password SMS API, it is fast and more secure. It is possible to deliver OTP code in different languages including regional and local languages in different countries. Upon answering the voice call, the recipient would hear OTP code two to three times in different supported languages e.g. English-German-Spanish, English-Hindi-Urdu etc. | ||
| The recipient then uses this code or password as an additional layer of security to login to a service, website or app. | ||
|
|
||
| Technical viability | ||
mbkhanhex marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| API represents an attempt to standardize interfaces between OTP Call solutions deployed by MNOs or external providers and their enterprise users. As such the API is not bound to any specific cloud platform or specific solution but aims to encourage vendors providing MNO or enterprise solution to support this API format and assure interoperability between different solutions. | ||
| Commercial viability | ||
mbkhanhex marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| There are not specific cloud requirements related to proposed API. | ||
| YAML code available? | ||
mbkhanhex marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| YES | ||
| Validated in lab/productive environments? | ||
mbkhanhex marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| Validated in Lab environment | ||
mbkhanhex marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| Validated with real customers? | ||
mbkhanhex marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| NO. API has not been deployed real use yet but we are in communication with several interested parties and expect PoC by Q1 2026 | ||
| ### Validated with operators? | ||
| Not yet. It is one of our new products and hence we didn’t get an opportunity to get it validated with some telco operators. We are expecting some PoC to start by Q1 2026 | ||
|
|
||
| Use cases | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This would go inside the API summary; these points are not part of the template.
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @albertoramosmonagas moved to API summary, please check
|
||
| • Online Banking: To authenticate users during login and transactions, ensuring secure access to financial accounts. | ||
| • Account Registration: To confirm user identity during account creation by sending a verification code to their mobile device. | ||
| • Password Recovery: To securely verify users when they request to reset their passwords, ensuring only the rightful owner can make changes. | ||
| • Two-Factor Authentication (2FA): To enhance security for sensitive applications by requiring a second verification step via SMS after entering a password. | ||
| Benefits | ||
| The One Time Password Call API has several benefits for the API consumer: | ||
| • Enhanced Security: OTPs provide an additional layer of security beyond passwords, reducing the risk of unauthorized access. | ||
| • User Verification: Ensures that the user has access to the registered mobile device, confirming their identity. | ||
| • Cost-Effective: Reduces the need for complex authentication systems while providing strong security. | ||
| • User Trust: Increases user confidence in the security of the platform, leading to higher user satisfaction. | ||
mbkhanhex marked this conversation as resolved.
Show resolved
Hide resolved
|
||
Uh oh!
There was an error while loading. Please reload this page.