Skip to main content

1) Secure Capture — Real-Time, On-Device, No Storage

1) SIM Change Detection (Android)

Subtitle:Purpose
Analyze Detectframes SIMfrom swapsthe infront-facing realcamera timeentirely on device to protectenhance sessionfraud integritydetection—no andimages preventare accountstored takeover.

or

Overviewtransmitted; only metadata/results are sent
A lightweight background service monitors the device’s SIM state and reports changes to your STS backend. Typical statuses: NO_CHANGE, SIM_CHANGED, UNKNOWN.

How it works

  • TheApp SDKdecides periodically checks SIM state (with backoffwhen to respectactivate OS(e.g., limits)after login, during a transfer, or only in high-risk flows).

  • OnstartCapture() change,checks itcamera sendspermission aand minimal,begins signedperiodic payloadframe (statusanalysis +locally.

    device/app
    • metadata)

  • Frames are processed on device; images are deleted immediately after analysis.

  • Only analysis results/metadata are sent to your backend.

  • YourCapture riskends enginewhen appliesthe rulesapp (e.g.,calls step-upstopCapture(). auth,

    session revoke, temporary hold).

    Secure_Capture_Feature_V1

SDKRequired &permission Permissions(AndroidManifest.xml)

    <uses-permission 
  • android:name="android.permission.CAMERA"/>

    Android
    • telephony
    state
    permissions
    per
    OEM/OS version.

  • Event callbacks & webhook destinations configurable in STS Admin.

Security & Privacy

  • No sensitive content—only status and non-PII metadata.

  • Pseudonymize device identifiers; follow data-minimization policies.

Compatibility & Limitations

  • Android only; background restrictions apply on Android 10+.

  • Dual-SIM devices may require extra logic.

  • Not available on iOS.

Key Metrics (KPIs)

  • SIM change rate per 1,000 MAU.

  • Detection-to-action time (ms).

  • False-positive rate on Dual-SIM.

Integration Steps

  1. Enable SIM Change Detection in STS Admin.

  2. Add the STS SDK module + required permissions.

  3. Implement the webhook endpoint to receive events.

  4. Configure risk rules (e.g., block high-risk transactions within 24–72h after a SIM change).

  5. Test on single-SIM and dual-SIM devices.

2) Secure Call Verification

Subtitle: Verify bank-initiated calls to stop social-engineering and number spoofing.

Overview
Before the user answers, the SDK checks whether an incoming call was initiated by your bank and is safe. It returns: CALL_APPROVED, UNAPPROVED_RECENT_CALL, NO_RECENT_CALL, UNKNOWN.

Reference Architecture
Bank Call Center → STS Secure Call Backend → Mobile App SDK

  • API: POST /api/v1/ReportCall with phone_number, uid, and context.

  • SDK method: CheckCallStatus() returning one of the statuses above.

UI Guidance

  • Approved: Green banner/badge + concise explanation.

  • Unapproved/Recently flagged: Yellow warning with “Verify identity.”

  • Unknown: Neutral gray with safety tips.

Security & Privacy

  • Transmit only minimal metadata needed for verification.

  • Log decisions for audit; avoid storing raw audio.

Use Cases

  • Confirming outbound bank calls before sharing sensitive info.

  • Closing the loop on suspected spoofing.

Key Metrics (KPIs)

  • % auto-approved vs. challenged calls.

  • Reduction in social-engineering incidents.

  • Decision latency (ms).

Integration Steps

  1. Register call numbers & policies in STS Admin.

  2. Integrate the SDK and show inline banners based on status.

  3. Send ReportCall events to backend analytics.

  4. Configure push alerts for “approved call in progress.”

  5. Add in-app education (tooltips) about verified calls.

3) Secure Capture (Front Camera, Real-Time, No Storage)

Subtitle: On-device camera analysis with zero image storage and privacy-first design.

Overview
Secure Capture analyzes frames from the front-facing camera on-device and never stores or uploads images. Only analysis metadata is sent to your backend.

SDK Methodsmethods & returns

  • startCapture() —→ startSUCCESS local| analysis.MISSING_PERMISSIONS

  • stopCapture() —→ stop analysis and clear buffers immediately.SUCCESS

UXUsage &example Permissions(Kotlin)

    val 
  • result 
    Display= acollectorAgent.startCapture()
clearif purpose(result statement== "MISSING_PERMISSIONS") {
    // Request CAMERA permission before capture.retrying
}
// ... perform secured flow ...
collectorAgent.stopCapture()

    • UI guidance (pre-permission message)}

  • Request“To cameraenhance permissionsecurity, just-in-time.the app will analyze images from your device’s front-facing camera. No images are stored or uploaded.”

Security & Privacyprivacy notes

  • No imageimages transmission—ever leave the device; only metadata.minimal metadata/results are transmitted.

  • Immediate buffer deletion after analysis.analysis; follow data minimization best practices.

UseCommon Casesscenarios

  • PassivePost-login livenessenvironment signals for step-up auth.validation

  • SessionExtra anomalycheck detectionduring standard transfers

  • High-risk events (multiplenew faces,payee, occlusions,unusually spooflarge cues).amount)

KeyNext Metrics (KPIs)

  • On-device inference latency (ms).

  • Metadata event throughput (events/min).

  • False-positive rate on real users.

Integration Stepssteps

  1. Enable Secure Capture in STS Admin.

  2. Add the SDK module and declare cameraCAMERA permission.

  3. Implement2) handlersExplain purpose to receive analysis metadata.users.

  4. Tune3) thresholds/heuristicsIntegrate bystartCapture()/stopCapture() clientin profile.the chosen flow(s).

  5. Provide4) aHandle concisepermission “Privacygracefully. Note”5) explainingRoll on-deviceout processing.gradually and monitor analytics. 



Back to top