From 03b18109455bea6ce46f8ee03105b2edc31719a1 Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Thu, 9 Oct 2025 18:48:13 +0500 Subject: [PATCH 01/22] Create APIproposal_Voice OTP Call MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- documentation/API proposals/APIproposal_Voice OTP Call | 1 + 1 file changed, 1 insertion(+) create mode 100644 documentation/API proposals/APIproposal_Voice OTP Call diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call new file mode 100644 index 00000000..8b137891 --- /dev/null +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -0,0 +1 @@ + From 2bd5b64383762ab6c944875e8645fa048795c455 Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Thu, 16 Oct 2025 17:59:27 +0500 Subject: [PATCH 02/22] Update APIproposal_Voice OTP Call --- .../API proposals/APIproposal_Voice OTP Call | 36 +++++++++++++++++++ 1 file changed, 36 insertions(+) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index 8b137891..3305e44f 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -1 +1,37 @@ +Description +API family name +Authentication and Fraud Prevention +API Name +Voice One-Time Password (OTP) Call +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 +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 +There are not specific cloud requirements related to proposed API. +YAML code available? +YES +Validated in lab/productive environments? +Validated in Lab environment +Validated with real customers? +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 +• 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. From 92d5b5bac1ac618a97cc6c25d1db1c90860740fd Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Fri, 17 Oct 2025 12:52:11 +0500 Subject: [PATCH 03/22] Update APIproposal_Voice OTP Call --- .../API proposals/APIproposal_Voice OTP Call | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index 3305e44f..1382657c 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -1,11 +1,11 @@ Description -API family name +### API family name Authentication and Fraud Prevention -API Name +### API Name Voice One-Time Password (OTP) Call -API family owner +### API family owner Heksagon -API summary +### 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. @@ -21,8 +21,8 @@ Validated in lab/productive environments? Validated in Lab environment Validated with real customers? 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 +### 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 • Online Banking: To authenticate users during login and transactions, ensuring secure access to financial accounts. From 2874f4169f3d2038a1822c22a0a4c048d8fb7ff3 Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Mon, 3 Nov 2025 12:17:38 +0500 Subject: [PATCH 04/22] Apply suggestion from @albertoramosmonagas Co-authored-by: Alberto Ramos Monagas --- documentation/API proposals/APIproposal_Voice OTP Call | 1 - 1 file changed, 1 deletion(-) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index 1382657c..7feb829d 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -1,4 +1,3 @@ -Description ### API family name Authentication and Fraud Prevention ### API Name From 1ea62cd22818f944b06305a4962f4763d8d1e8fe Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Mon, 3 Nov 2025 12:18:16 +0500 Subject: [PATCH 05/22] Apply suggestion from @albertoramosmonagas Co-authored-by: Alberto Ramos Monagas --- documentation/API proposals/APIproposal_Voice OTP Call | 1 + 1 file changed, 1 insertion(+) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index 7feb829d..5752be90 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -1,5 +1,6 @@ ### API family name Authentication and Fraud Prevention + ### API Name Voice One-Time Password (OTP) Call ### API family owner From 3f7c0de5c55e3b1e278f0a6f5f880857f1a5e131 Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Mon, 3 Nov 2025 12:18:39 +0500 Subject: [PATCH 06/22] Apply suggestion from @albertoramosmonagas Co-authored-by: Alberto Ramos Monagas --- documentation/API proposals/APIproposal_Voice OTP Call | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index 5752be90..f8abb0cf 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -11,7 +11,7 @@ Voice OTP Call API performs real-time checks to verify that the user possessed t 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 +### Technical viability 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 There are not specific cloud requirements related to proposed API. From 66e7e5b371c9e1592ec3ffeddebc716ad73d2a21 Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Mon, 3 Nov 2025 12:19:41 +0500 Subject: [PATCH 07/22] Apply suggestion from @albertoramosmonagas Co-authored-by: Alberto Ramos Monagas --- documentation/API proposals/APIproposal_Voice OTP Call | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index f8abb0cf..9f251521 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -13,7 +13,7 @@ The recipient then uses this code or password as an additional layer of security ### Technical viability 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 +### Commercial viability There are not specific cloud requirements related to proposed API. YAML code available? YES From 369e1728be6558e0602126616fb7f29371fa7e1c Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Mon, 3 Nov 2025 12:21:22 +0500 Subject: [PATCH 08/22] Apply suggestion from @albertoramosmonagas Co-authored-by: Alberto Ramos Monagas --- documentation/API proposals/APIproposal_Voice OTP Call | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index 9f251521..b1dbbbf8 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -15,7 +15,7 @@ The recipient then uses this code or password as an additional layer of security 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 There are not specific cloud requirements related to proposed API. -YAML code available? +### YAML code available? YES Validated in lab/productive environments? Validated in Lab environment From 68a16e0db78dc3a19308f48624953e7bfb03ff3b Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Mon, 3 Nov 2025 12:22:01 +0500 Subject: [PATCH 09/22] Apply suggestion from @albertoramosmonagas Co-authored-by: Alberto Ramos Monagas --- documentation/API proposals/APIproposal_Voice OTP Call | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index b1dbbbf8..be714e02 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -18,7 +18,7 @@ There are not specific cloud requirements related to proposed API. ### YAML code available? YES Validated in lab/productive environments? -Validated in Lab environment +YES, Lab environment Validated with real customers? 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? From 30f744f15a57c20f7a928f43a6d479a730a47808 Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Wed, 26 Nov 2025 20:48:50 +0500 Subject: [PATCH 10/22] Apply suggestion from @albertoramosmonagas Co-authored-by: Alberto Ramos Monagas --- documentation/API proposals/APIproposal_Voice OTP Call | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index be714e02..06b7a7a6 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -1,3 +1,7 @@ +# API Proposal Template +This template captures all the information that a partner should fill out when proposing a new API (or API family) to CAMARA. + + ### API family name Authentication and Fraud Prevention From 992df410d6c48fa37271f31e950f6927b93b0619 Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Wed, 26 Nov 2025 20:49:25 +0500 Subject: [PATCH 11/22] Apply suggestion from @albertoramosmonagas Co-authored-by: Alberto Ramos Monagas --- documentation/API proposals/APIproposal_Voice OTP Call | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index 06b7a7a6..a647486f 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -3,7 +3,7 @@ This template captures all the information that a partner should fill out when p ### API family name -Authentication and Fraud Prevention +Voice One-Time Password (OTP) Call ### API Name Voice One-Time Password (OTP) Call From e9cb367ad6f313e7fd847d9665df74a5123c695d Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Wed, 26 Nov 2025 20:49:51 +0500 Subject: [PATCH 12/22] Apply suggestion from @albertoramosmonagas Co-authored-by: Alberto Ramos Monagas --- documentation/API proposals/APIproposal_Voice OTP Call | 2 -- 1 file changed, 2 deletions(-) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index a647486f..d9742cc0 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -5,8 +5,6 @@ This template captures all the information that a partner should fill out when p ### API family name Voice One-Time Password (OTP) Call -### API Name -Voice One-Time Password (OTP) Call ### API family owner Heksagon ### API summary From 03461b5dec750a2f18433988ff0a7cb57edd048d Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Wed, 26 Nov 2025 20:50:04 +0500 Subject: [PATCH 13/22] Apply suggestion from @albertoramosmonagas Co-authored-by: Alberto Ramos Monagas --- documentation/API proposals/APIproposal_Voice OTP Call | 1 + 1 file changed, 1 insertion(+) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index d9742cc0..a05b5414 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -7,6 +7,7 @@ Voice One-Time Password (OTP) Call ### 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. From 03399a43adcbbe53b9b64537281b09cf938bc901 Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Wed, 26 Nov 2025 20:52:47 +0500 Subject: [PATCH 14/22] Apply suggestion from @albertoramosmonagas Co-authored-by: Alberto Ramos Monagas --- documentation/API proposals/APIproposal_Voice OTP Call | 1 + 1 file changed, 1 insertion(+) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index a05b5414..a271a50a 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -16,6 +16,7 @@ The recipient then uses this code or password as an additional layer of security ### Technical viability 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 There are not specific cloud requirements related to proposed API. ### YAML code available? From af8316acfef47c2461bb228d9e1b40b7fb0c51cb Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Wed, 26 Nov 2025 20:53:02 +0500 Subject: [PATCH 15/22] Apply suggestion from @albertoramosmonagas Co-authored-by: Alberto Ramos Monagas --- documentation/API proposals/APIproposal_Voice OTP Call | 1 + 1 file changed, 1 insertion(+) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index a271a50a..90dcb033 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -19,6 +19,7 @@ API represents an attempt to standardize interfaces between OTP Call solutions d ### Commercial viability There are not specific cloud requirements related to proposed API. + ### YAML code available? YES Validated in lab/productive environments? From 92a07b104980c2e4bcbf615a81e860aedcc9f216 Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Wed, 26 Nov 2025 20:56:07 +0500 Subject: [PATCH 16/22] Apply suggestion from @albertoramosmonagas Co-authored-by: Alberto Ramos Monagas --- documentation/API proposals/APIproposal_Voice OTP Call | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index 90dcb033..5753058e 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -22,7 +22,8 @@ There are not specific cloud requirements related to proposed API. ### YAML code available? YES -Validated in lab/productive environments? + +### Validated in lab/productive environments? YES, Lab environment Validated with real customers? NO. API has not been deployed real use yet but we are in communication with several interested parties and expect PoC by Q1 2026 From c1da7c6198bcdce28fb2fb6cb2b79f4f045f8382 Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Wed, 26 Nov 2025 20:58:31 +0500 Subject: [PATCH 17/22] Apply suggestion from @albertoramosmonagas Co-authored-by: Alberto Ramos Monagas --- documentation/API proposals/APIproposal_Voice OTP Call | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index 5753058e..3ff615f6 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -25,7 +25,8 @@ YES ### Validated in lab/productive environments? YES, Lab environment -Validated with real customers? + +### Validated with real customers? 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 From ae8875e6090d0f946669096380ca39ecec6a69bc Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Wed, 26 Nov 2025 20:58:42 +0500 Subject: [PATCH 18/22] Apply suggestion from @albertoramosmonagas Co-authored-by: Alberto Ramos Monagas --- documentation/API proposals/APIproposal_Voice OTP Call | 1 + 1 file changed, 1 insertion(+) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index 3ff615f6..34141bf7 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -28,6 +28,7 @@ YES, Lab environment ### Validated with real customers? 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 From 85c677cb649be4f1c354afc528ec6dca0765821a Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Wed, 26 Nov 2025 21:02:27 +0500 Subject: [PATCH 19/22] Update APIproposal_Voice OTP Call --- .../API proposals/APIproposal_Voice OTP Call | 23 +++++++++---------- 1 file changed, 11 insertions(+), 12 deletions(-) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index 34141bf7..9ffc57f5 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -13,6 +13,17 @@ The “Voice One Time Password Call” API is used to send short-lived one time 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. +Use cases +• 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. ### Technical viability 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. @@ -31,15 +42,3 @@ NO. API has not been deployed real use yet but we are in communication with seve ### 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 -• 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. From e98cc0ef976d8bb50a2e3a05a9812e47f5cce763 Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Wed, 26 Nov 2025 21:10:22 +0500 Subject: [PATCH 20/22] Update APIproposal_Voice OTP Call --- documentation/API proposals/APIproposal_Voice OTP Call | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call index 9ffc57f5..51590425 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call +++ b/documentation/API proposals/APIproposal_Voice OTP Call @@ -42,3 +42,7 @@ NO. API has not been deployed real use yet but we are in communication with seve ### 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 + +### Supporters in API Backlog Working Group +List of supporters. +*NOTE: That shall be added by the Working Group. Supporting an API proposal means that the supporting company must provide at least 1 (one) Maintainer at the time of the Sub Project creation.* From 0e9981097de865470aeac9b4c81728309014a8aa Mon Sep 17 00:00:00 2001 From: mbkhanhex Date: Wed, 26 Nov 2025 21:15:41 +0500 Subject: [PATCH 21/22] Rename APIproposal_Voice OTP Call to APIproposal_Voice OTP Call.md --- .../{APIproposal_Voice OTP Call => APIproposal_Voice OTP Call.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename documentation/API proposals/{APIproposal_Voice OTP Call => APIproposal_Voice OTP Call.md} (100%) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call b/documentation/API proposals/APIproposal_Voice OTP Call.md similarity index 100% rename from documentation/API proposals/APIproposal_Voice OTP Call rename to documentation/API proposals/APIproposal_Voice OTP Call.md From 924cc4a5afe66ad1f58da9d38535c4ed77826492 Mon Sep 17 00:00:00 2001 From: Muhammad Bilal Khan Date: Fri, 26 Dec 2025 10:36:01 +0100 Subject: [PATCH 22/22] change voice otp .md file --- documentation/API proposals/APIproposal_Voice OTP Call.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/documentation/API proposals/APIproposal_Voice OTP Call.md b/documentation/API proposals/APIproposal_Voice OTP Call.md index 51590425..ec560a73 100644 --- a/documentation/API proposals/APIproposal_Voice OTP Call.md +++ b/documentation/API proposals/APIproposal_Voice OTP Call.md @@ -11,13 +11,13 @@ 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. +Voice OTP Call API is a secure method for providing one-time access to an application or performing a single transaction. 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. Use cases • 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. +• Two-Factor Authentication (2FA): To enhance security for sensitive applications by requiring a second verification step via call 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. @@ -29,7 +29,7 @@ The One Time Password Call API has several benefits for the API consumer: 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 -There are not specific cloud requirements related to proposed API. +For user registration, part of 2FA, dynamic verification codes, payment confirmation, and other scenarios. ### YAML code available? YES