Open APIs

Hi Team,

We have some scenarios where we use OTP SMS.

1. While an User logging to application, to authenticate the user we send OTP to User mobile number.
2. Another scenario where Agents trying to close the Complaint raised by customer and before closing the complaint an OTP to be triggered to customer as Agent need to take customer confirmation to close the Complaint. 
3. Another scenario where Agent is serving the customer to subscribe to a package and triggering OTP to customer considering it as customer consent taken to add package to the subscription.

Please suggest which API best suits for these scenarios. Do we need to prefer TMF720 (Digital Identity) considering these as Customer or Agent Authentications or Do we need to use TMF681 (Communication Management) treating these as SMS communications.

Thanks,

Kiran.Ch

It's a good question. Currently, the API that is used for unsolicited communication with a customer (or other party role) is indeed TMF681, which basically is intended to wrap and abstract the actual way in which a message is sent (via SMS, voice message, email, other). But perhaps for sending OTPs the TMF681 API is over--qualified.

On the other hand, if you want a record of the fact that OTPs were sent, and flexibility in how they were sent, you'll end up re-inventing TMF681.

Interesting to hear what @Bruno Fernandes (lead for Digital ID API) has to say about this.

Hi Team,

We have some scenarios where we use OTP SMS.

1. While an User logging to application, to authenticate the user we send OTP to User mobile number.
2. Another scenario where Agents trying to close the Complaint raised by customer and before closing the complaint an OTP to be triggered to customer as Agent need to take customer confirmation to close the Complaint. 
3. Another scenario where Agent is serving the customer to subscribe to a package and triggering OTP to customer considering it as customer consent taken to add package to the subscription.

Please suggest which API best suits for these scenarios. Do we need to prefer TMF720 (Digital Identity) considering these as Customer or Agent Authentications or Do we need to use TMF681 (Communication Management) treating these as SMS communications.

Thanks,

Kiran.Ch

TMF720 version 5, which is soon to be published, supports your requirement through the use of the Credential resource.

It's a good question. Currently, the API that is used for unsolicited communication with a customer (or other party role) is indeed TMF681, which basically is intended to wrap and abstract the actual way in which a message is sent (via SMS, voice message, email, other). But perhaps for sending OTPs the TMF681 API is over--qualified.

On the other hand, if you want a record of the fact that OTPs were sent, and flexibility in how they were sent, you'll end up re-inventing TMF681.

Interesting to hear what @Bruno Fernandes (lead for Digital ID API) has to say about this.

Hi Team,

We have some scenarios where we use OTP SMS.

1. While an User logging to application, to authenticate the user we send OTP to User mobile number.
2. Another scenario where Agents trying to close the Complaint raised by customer and before closing the complaint an OTP to be triggered to customer as Agent need to take customer confirmation to close the Complaint. 
3. Another scenario where Agent is serving the customer to subscribe to a package and triggering OTP to customer considering it as customer consent taken to add package to the subscription.

Please suggest which API best suits for these scenarios. Do we need to prefer TMF720 (Digital Identity) considering these as Customer or Agent Authentications or Do we need to use TMF681 (Communication Management) treating these as SMS communications.

Thanks,

Kiran.Ch

Thanks Bruno,

For now can we implement with the current v4 anyways or we can only implement after v5 publishing ? Please suggest.

TMF720 version 5, which is soon to be published, supports your requirement through the use of the Credential resource.

It's a good question. Currently, the API that is used for unsolicited communication with a customer (or other party role) is indeed TMF681, which basically is intended to wrap and abstract the actual way in which a message is sent (via SMS, voice message, email, other). But perhaps for sending OTPs the TMF681 API is over--qualified.

On the other hand, if you want a record of the fact that OTPs were sent, and flexibility in how they were sent, you'll end up re-inventing TMF681.

Interesting to hear what @Bruno Fernandes (lead for Digital ID API) has to say about this.

Hi Team,

We have some scenarios where we use OTP SMS.

1. While an User logging to application, to authenticate the user we send OTP to User mobile number.
2. Another scenario where Agents trying to close the Complaint raised by customer and before closing the complaint an OTP to be triggered to customer as Agent need to take customer confirmation to close the Complaint. 
3. Another scenario where Agent is serving the customer to subscribe to a package and triggering OTP to customer considering it as customer consent taken to add package to the subscription.

Please suggest which API best suits for these scenarios. Do we need to prefer TMF720 (Digital Identity) considering these as Customer or Agent Authentications or Do we need to use TMF681 (Communication Management) treating these as SMS communications.

Thanks,

Kiran.Ch