How checkout/checkout-3ds-sdk-android works
This repository snapshot contains only a README, so the graph reflects documented behavior rather than inspected implementation. The principal workflow is app setup, authentication request, SDK-managed device collection and issuer communication, any required challenge, and an authentication result returned to the app. The README also documents customizable native challenge presentation, localization/accessibility, and optional 3DS1 fallback; internal call ownership and implementation boundaries cannot be verified.
Main entry points: README.md 3DS SDK
Components 11
App integration
- SDK setup
README.md - Authentication parameters
README.md - Authentication result
README.md
Authentication flow
- 3DS SDK
README.md - Device data collection
README.md - 3DS1 fallback
README.md - 3DS protocols
README.md
Customer experience
- Native challenge
README.md - Styling and localization
README.md
Other components
- Integrating app
- Card issuer
Connections 11
- Integrating app → SDK setup: initializes
README.md - Integrating app → Authentication parameters: configures
README.md - Integrating app → 3DS SDK: requests authentication
README.md - 3DS SDK → Device data collection: collects
README.md - 3DS SDK → Card issuer: communicates with
README.md - 3DS SDK → Native challenge: presents when required
README.md - Native challenge → Styling and localization: uses options
README.md - 3DS SDK → 3DS1 fallback: may fall back
README.md - 3DS SDK → 3DS protocols: supports
README.md - 3DS SDK → Authentication result: returns
README.md - Authentication result → Integrating app: continues payment flow
README.md