Quick Start
Use this guide to get the Wallet SDK mounted in your React Native application as quickly as possible.
What This Guide Covers
This quick start shows the minimum path to render the SDK in a host app. It is intentionally high level and is designed for external client teams.
Review Installation First
Before testing on a device, make sure your app has completed the installation
steps and native app configuration updates described in the Installation
Guide. That includes camera permission
for QR-based flows and Bluetooth-related permissions when proximity-based
flows are enabled. Your host app must declare the required entries in
AndroidManifest.xml and Info.plist before these flows will work correctly
on device.
Before You Start
Make sure you already have:
- the SDK package installed
react-native-svginstalled- a host app login or authorization flow that can provide an authentication token
- required iOS and Android app permissions configured
Step 1: Wrap Your App
Mount the SDK provider near the top of your application so SDK screens and hooks can access the configured wallet session.
Your host application is responsible for obtaining the authentication token from its own login or authorization flow and passing that token into the SDK configuration before rendering the provider.
import { ActivityIndicator } from 'react-native';
import { VECUProvider } from '@vecu/wallet-react-native-sdk';
function App() {
const authToken = tokenFromYourLoginFlow;
if (!authToken) {
return <ActivityIndicator size='large' />;
}
return (
<VECUProvider
config={{
deploymentStage: 'sandbox',
authToken,
}}
>
<WalletScreen />
</VECUProvider>
);
}
Step 2: Render the Wallet Experience
The simplest integration is to render the main wallet surface in one of your application screens.
import { WalletHub } from '@vecu/wallet-react-native-sdk';
function WalletScreen() {
return <WalletHub />;
}
Step 3: Run the App on Device
Build and run your application in your normal React Native workflow.
Before validating scanner or proximity flows, confirm:
- camera permissions are declared in
AndroidManifest.xmlandInfo.plist - Bluetooth-related permissions are declared in
AndroidManifest.xmlandInfo.plistwhen those flows are enabled - iOS pods have been installed
Step 4: Validate the Integration
At a high level, your quick start is complete when:
- the SDK initializes without startup errors
- the wallet screen renders in your app
- authentication is being passed into the SDK correctly
- required device permissions are already configured in
AndroidManifest.xmlandInfo.plist
Reference Applications
You can review the wallet application and demo application as example host app integrations. Treat them as high-level references rather than implementation templates.
Those example applications include additional host-app concerns such as navigation, theming, callbacks, and other flow-specific wiring. This quick start intentionally shows only the minimum integration path required to mount the SDK.
If your host app needs custom navigation, additional SDK options, or branded styling, continue with Integration Approaches, Configuration, and Theming.