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
O2 currently have an extra verification step when a user attempts to send a webtext from a foreign country.
A page is presented to the user asking to click a link to send a verification code
The user receives a text message containing a code
The user enters the code into the O2 website
The user can now send webtexts like normal
This process will work very similar to how SwiftSMS manages Vodafone international webtexts. We can present the user with a dialog box allowing them to enter the verification code. Hopefully there is a cookie affect whereby the user only needs to enter this code once per day/login.
I haven't looked into this very much yet but I think the verification page is presented before attempting to send a webtext therefore (like the Vodafone int'l webtext) we can present the dialog after the user presses the send button.
Possible solution,
User sends webtext like normal
In doSend detect if the verification page is being presented
Automatically click the to send the verification code
Present the user with a dialog to enter the code
The user enters the verification code in SwiftSMS
POST the verification code to O2 website
Continue with standard send procedure
The text was updated successfully, but these errors were encountered:
O2 currently have an extra verification step when a user attempts to send a webtext from a foreign country.
This process will work very similar to how SwiftSMS manages Vodafone international webtexts. We can present the user with a dialog box allowing them to enter the verification code. Hopefully there is a cookie affect whereby the user only needs to enter this code once per day/login.
I haven't looked into this very much yet but I think the verification page is presented before attempting to send a webtext therefore (like the Vodafone int'l webtext) we can present the dialog after the user presses the send button.
Possible solution,
The text was updated successfully, but these errors were encountered: