Overview

forter's mobile sdks to receive important behavioral and cyber events that contribute greatly to our model's accuracy and ability to identify fraud and suspicious activity throughout the customer journey and during the checkout event integration time our mobile sdks are intentionally lightweight and provide simple methods to allow merchants a simple integration and time to test typical integration time for our mobile sdks is approximately one developer day merchants may spend additional time testing and/or releasing the sdk gradually supported operating systems and frameworks forter has native app sdks for android and ios as well as a react mobile plugin that can be used for merchants on a react framework and a webview integration for integrated mobile webviews which ordertype to send once an event is submitted through the sdk, your backend still needs to tell forter's orders api https //docs forter com/reference/order v3 what kind of order this was via the ordertype field which value to use depends entirely on how the checkout itself is rendered, not just on your app's platform sdk used ordertype yes (native ios) ios yes (native android) android yes (flutter plugin) ios or android yes (react native plugin) ios or android no (webview) web flutter and react native are cross platform frameworks, but the forter plugin still runs natively on top of the device's actual os send ios or android to match the host device, not "flutter" or "react native " see hybrid platform plugins docid\ apq utv0jxajznlrasba for details if your checkout page is rendered in a webview (native app, flutter, or react native alike), send web and use the fortertoken generated by the forter javascript instead of fortermobileuid — see ios webview docid\ heewpzfeujwqowb0dghio and android webview docid\ o3ssus2r8ymp0lz0f1wuz what's included unique ids for native mobile apps, integrate the respective mobile sdks the sdks provide methods that generate a unique identifier for the mobile user based on pre existing, pii compliant persistent device identifiers (idfv identifier for vendor for ios and deviceid for android) event data the sdks also provide simple, methods that merchants can call to asynchronously send forter behavioral events these events include actions like "add to cart", "search", or "accept terms of service" sdk terminology fortersdk the sdk provided by forter which enables easy event submission from your ios application to forter's servers event an occurrence / an interaction from the user that is considered a change in the application's current state an event could be any interaction from the user / a change in the environment sending/'firing' tracking events this term describes the submitting/reporting of an occurrence (event) in the application