3DS Mobile SDKs

The mobile app should setup the Forter 3DS SDK upon launch by calling the setup method. This step will initialize the SDK and will collect the required data to perform a 3DS2 flow, if needed.
App user finishes checkout flow and sends the params to the server, which will decide if a 3DS flow is required.
If a 3DS flow is required, the server should return the 3DS version and the required dsId for this transaction.
The mobile app should call the createTransaction method. This method will collect the required params for generating a challenge on the server side. Forter's server expects this params encoded in base64. This can be done by encoding the required params on the merchant side or by using the toBase64 method for the generated FTRTransaction.
If the server decides to present a challenge, the app should call the doChallenge method with the required params, provided by the server along side additional params - the previously generated FTRTransaction, Context/Delegate, etc.
After the user completes the challenge, the app should pass the challenge result to the server to completed the transaction.