Architecture
The Vrtx Mobile SDK follows a managed embedded finance architecture. The host app launches the SDK experience, while Vrtx manages regulated financial logic, compliance controls, backend processing, and financial data synchronization.
Architecture Model
Host App: Hosts the SDK entry point, passes approved configuration values, and handles setup callbacks.
One backend, always in sync
All SDK capabilities run on a shared Vrtx financial backend. This keeps onboarding status, wallet balances, card states, and transaction records synchronized across the user lifecycle.
Modular Architecture
The SDK is built as a modular embedded finance solution. Modules can be enabled based on the client’s business needs, rollout priorities, and approved regulatory scope.
Customer Onboarding
Streamlined identity verification and KYC journeys aligned with applicable regulatory requirements.
Wallet Operations
Native interfaces for balance visibility and wallet-related operations.
Card Controls
Management of virtual and physical cards, including issuance, activation, PIN setup, and freezing.
Transaction Visibility
Clear transaction visibility across money movement flows.
Shared SDK Concepts
The iOS SDK, Android SDK, React Native wrapper, and Flutter wrapper follow the same core integration model.
Single Setup Model
SDKs are initialized through a setup method that receives credentials, environment, language, appearance, and callbacks.
Client Credentials
The SDK authenticates with Vrtx using the client credentials assigned to the client application.
Native SDK Experience
The SDK launches a native wallet experience inside the host app.
Callbacks
The host app receives success and error callbacks to react to SDK launch status.
Session Management
Token and session renewal are managed by the SDK where possible.
Customization
Branding, language, theme, and font configuration are handled through approved SDK configuration.
Architecture Principles
The SDK follows a managed architecture model.
- The SDK is embedded inside the client mobile app.
- The SDK provides the mobile experience layer.
- Financial logic is not owned by the client device.
- Compliance decisioning is not handled locally.
- Wallet balances are not stored locally by the host app.
- Financial records are fetched from Vrtx backend systems.
- Regulated workflows remain controlled by Vrtx.
No local financial decisioning
The SDK does not place financial logic, compliance decisioning, or ledger ownership on the client device. These controls remain managed by Vrtx.
User Request Flow
When a user performs an action such as onboarding, viewing a balance, or managing a card, the request follows a managed flow through the SDK and Vrtx backend.
Open SDK Flow
The host app opens the relevant SDK flow.
Send Secure Request
The SDK sends the request securely to Vrtx backend systems.
Process on Vrtx
Vrtx handles validation, compliance checks, account updates, ledger recording, and transaction processing.
Return Result
The result is returned to the SDK and displayed to the user inside the host app.
Data Management
The host app does not store financial balances, compliance decisions, or regulated financial records locally. Financial data is fetched from Vrtx systems to maintain accuracy, security, and audit readiness.
Balances
Fetched from Vrtx systems and not owned by the host app.
Transaction Records
Retrieved from Vrtx backend systems for accurate transaction visibility.
Card Status
Sourced from Vrtx to reflect the current card state.
Onboarding Status
Managed by Vrtx based on approved KYC and compliance workflows.
SDK Scope
| In Scope | Description |
|---|---|
| Native iOS SDK | Native SDK experience for iOS applications |
| Native Android SDK | Native SDK experience for Android applications |
| React Native wrapper | Cross-platform wrapper built on top of the native SDKs |
| Flutter wrapper | Cross-platform wrapper built on top of the native SDKs |
| User onboarding and KYC | Embedded onboarding and identity verification flows |
| Wallet and balance display | Wallet experience and balance visibility |
| Transaction history | User transaction records displayed through the SDK |
| Card issuance and controls | Card-related flows including issuance and management |
| Branding customization | Approved UI and brand configuration |
| Secure session management | SDK-managed authentication and session handling |
Out of Scope
| Out of Scope | Description |
|---|---|
| Direct backend access by clients | Clients do not directly control Vrtx backend financial systems |
| API-only integration | This section covers the mobile SDK and wrappers, not standalone API integration |
| Client-owned compliance logic | Compliance workflows and decisioning remain managed by Vrtx |
| Changes to regulatory workflows | Regulated steps cannot be skipped, removed, or modified by the client |
| Local financial data ownership | Balances, transaction records, and decisions are not stored locally by the host app |