Antiscam SDK (Android)
Platform: Android 10+ (API 29) Language: Kotlin-first Last Updated: April 2026
Overview
Scam Protection SDK for Android helps organizations add scam, fraud, and phishing protection to their own Android apps. It combines production-ready UI, programmable APIs, and platform-integrated protection features so teams can launch quickly or build tailored experiences.
This SDK is designed for organizations embedding protection into an existing Android application, such as banking, telecom, insurance, and digital service apps.
What the SDK Provides
The SDK supports two common integration styles:
Built-in experience: Launch ready-made feature screens and entry points for faster implementation
Custom experience: Use public APIs and reactive data streams to build your own branded UI
You can also combine both approaches in the same app.
Core Protection Features
Safe SMS
Helps protect users from phishing, scam, and spam messages.
Detects suspicious SMS activity and phishing links
Supports advanced scanning for higher-risk messages
Provides threat details such as severity, category, and confidence
Supports user actions such as dismissing threats and reporting false positives
Exposes state and events for custom UI integrations
Safe Call
Helps users identify or block risky incoming calls.
Supports spam and scam call detection
Supports caller identification and call reputation experiences
Provides call history and protection statistics for custom experiences
Supports configurable call protection preferences
Exposes state and events for app-driven workflows
Safe Email
Helps monitor connected mailboxes for phishing and other suspicious content.
Supports Gmail, Outlook, and IMAP-based mailboxes
Supports OAuth-based onboarding for supported providers
Supports mailbox validation and multi-mailbox scenarios
Provides scan counts, threat counts, and mailbox status information
Supports user-controlled preferences for advanced scanning and data settings
AI Assistant
Provides conversational scam detection and security guidance.
Supports natural-language scam and safety questions
Supports file and image scanning flows
Can be used with built-in UI or custom chat experiences
Supports session continuity and guided response options
Dashboard
Provides a central protection summary across enabled features.
Aggregates scan and risk activity across supported protections
Supports built-in UI and custom dashboard development
Supports monthly and per-feature summaries
SDK Highlights
Language
Kotlin-first API with coroutines and Flow
Integration Model
Built-in UI, custom UI, or hybrid
Lifecycle
Lifecycle-aware components with reactive status monitoring
Modularity
Core SDK with optional feature components
Navigation
Built-in deep linking and flexible routing
Branding
Customizable strings, icons, and UI resources using standard Android patterns
Reliability
Consumer ProGuard / R8 support and standard Android packaging workflows
Platform Requirements
Minimum SDK
API 29 (Android 10)
Target SDK
API 36
Compile SDK
API 36
Gradle
8.13.0 or later
Kotlin
2.1.21 or later
Java
JDK 17
Architecture at a Glance
The SDK uses a modular structure with shared core functionality and optional feature areas.
The core SDK manages lifecycle, routing, and feature access. Individual features provide their own APIs, data, and UI surfaces.
What Teams Can Build
Fast Implementation
Use built-in feature screens and standard entry points to add protection quickly with minimal UI work.
Fully Custom Experiences
Build your own Android UI using public interfaces and reactive streams for:
threat lists
call activity and reputation data
mailbox status and scan data
assistant sessions and scam analysis results
aggregated dashboard statistics
Hybrid Experiences
Use built-in UI for some flows and custom UI for others. This is useful when teams want speed in some areas and deeper product customization in others.
Privacy and User Experience Considerations
Scam protection features may require runtime permissions, platform roles, or external account connection depending on the feature being used.
Examples include:
SMS-related permissions for SMS protection
phone and call-related permissions or roles for call protection
mailbox authorization for email protection
Apps integrating the SDK should explain the user value clearly and request permissions only when needed.
Feature Availability
Feature availability can vary by:
integrated modules
platform capabilities
app configuration
commercial agreement or entitlement model
Teams should design the host app to handle cases where some features are enabled and others are not.
Who This Is For
This SDK is intended for organizations embedding scam protection into their own Android apps.
It is not a consumer standalone app, and it is not intended as a general-purpose public mobile library for unrelated use cases.
Get Started
Scam Protection SDK is available for approved integrations.
Typical next steps
Request access
Review the implementation guide
Choose the built-in UI, custom UI, or hybrid integration model
Integrate the required feature modules
Validate permissions, platform behavior, and branding
Recommended companion materials
integration guide
API reference
release notes
support and onboarding documentation
Current SDK Version: 1.3.4 · Last Updated: April 2026
Was this helpful?