Step-by-step guide for integrating the Para Swift SDK into your iOS application
The Para Swift SDK enables you to integrate secure wallet features including creation, passkey-based authentication, and transaction signing into your iOS applications. This guide covers all necessary steps from installation to implementing authentication flows.
To use Para, you need an API key. This key authenticates your requests to Para services and is essential for integration.
Donโt have an API key yet? Request access to the Developer Portal to create API keys, manage billing, teams, and more.
Add the Para Swift SDK Package
https://github.com/getpara/swift-sdk
0.0.1 < 1.0.0
Configure Associated Domains for Passkeys
To enable passkeys on iOS, you need to configure Associated Domains:
A1B2C3D4E5.com.example.yourapp
Without properly registering your domain with Para, passkey authentication flows will fail. Contact Para support if you encounter issues with passkey registration.
Beta Testing Credentials In the BETA
Environment, you can use any email ending in @test.getpara.com
(like
dev@test.getpara.com) or US phone numbers (+1) in the format (area code)-555-xxxx
(like (425)-555-1234). Any OTP
code will work for verification with these test credentials. These credentials are for beta testing only. You can
delete test users anytime in the beta developer console to free up user slots.
First, you need to initialize the Para manager in your app. Below is an example of initializing the SDK in a SwiftUI application:
Para supports email and phone authentication methods. Each method uses a secure, passkey-first approach for seamless biometric logins via Face ID or Touch ID.
Email authentication verifies users via a one-time password (OTP) sent to their email address and then sets up a biometric-enabled passkey for future logins.
Check User Existence
First, check if the user already exists in the Para system:
For Existing Users: Login with Passkey
If the user exists, trigger the passkey login flow:
For New Users: Create Account
If the user does not exist, initiate the account creation process:
Generate Passkey and Create Wallet
After verification, generate a passkey and create a wallet:
Email authentication verifies users via a one-time password (OTP) sent to their email address and then sets up a biometric-enabled passkey for future logins.
Check User Existence
First, check if the user already exists in the Para system:
For Existing Users: Login with Passkey
If the user exists, trigger the passkey login flow:
For New Users: Create Account
If the user does not exist, initiate the account creation process:
Generate Passkey and Create Wallet
After verification, generate a passkey and create a wallet:
Phone authentication verifies users via SMS OTP and sets up a biometric-enabled passkey for future logins.
Check User Existence
First, check if the user already exists by phone number:
For Existing Users: Login with Passkey
If the user exists, trigger the passkey login flow:
For New Users: Create Account
If the user does not exist, initiate the account creation process:
Generate Passkey and Create Wallet
After verification, generate a passkey and create a wallet:
After initial setup, users can log in using their passkey, which triggers biometric authentication:
This will prompt the user for Face ID or Touch ID verification before granting access to their wallets.
You can check if a user is already authenticated:
To sign out a user and clear their session:
After successful authentication, you can perform wallet operations:
For detailed transaction signing with specific blockchains (EVM, Solana, Cosmos), please refer to the respective blockchain integration guides.
For a complete implementation example, check out our Swift SDK example app:
After integrating Para into your Flutter app, you can explore other features and integrations to enhance your Para experience.
Step-by-step guide for integrating the Para Swift SDK into your iOS application
The Para Swift SDK enables you to integrate secure wallet features including creation, passkey-based authentication, and transaction signing into your iOS applications. This guide covers all necessary steps from installation to implementing authentication flows.
To use Para, you need an API key. This key authenticates your requests to Para services and is essential for integration.
Donโt have an API key yet? Request access to the Developer Portal to create API keys, manage billing, teams, and more.
Add the Para Swift SDK Package
https://github.com/getpara/swift-sdk
0.0.1 < 1.0.0
Configure Associated Domains for Passkeys
To enable passkeys on iOS, you need to configure Associated Domains:
A1B2C3D4E5.com.example.yourapp
Without properly registering your domain with Para, passkey authentication flows will fail. Contact Para support if you encounter issues with passkey registration.
Beta Testing Credentials In the BETA
Environment, you can use any email ending in @test.getpara.com
(like
dev@test.getpara.com) or US phone numbers (+1) in the format (area code)-555-xxxx
(like (425)-555-1234). Any OTP
code will work for verification with these test credentials. These credentials are for beta testing only. You can
delete test users anytime in the beta developer console to free up user slots.
First, you need to initialize the Para manager in your app. Below is an example of initializing the SDK in a SwiftUI application:
Para supports email and phone authentication methods. Each method uses a secure, passkey-first approach for seamless biometric logins via Face ID or Touch ID.
Email authentication verifies users via a one-time password (OTP) sent to their email address and then sets up a biometric-enabled passkey for future logins.
Check User Existence
First, check if the user already exists in the Para system:
For Existing Users: Login with Passkey
If the user exists, trigger the passkey login flow:
For New Users: Create Account
If the user does not exist, initiate the account creation process:
Generate Passkey and Create Wallet
After verification, generate a passkey and create a wallet:
Email authentication verifies users via a one-time password (OTP) sent to their email address and then sets up a biometric-enabled passkey for future logins.
Check User Existence
First, check if the user already exists in the Para system:
For Existing Users: Login with Passkey
If the user exists, trigger the passkey login flow:
For New Users: Create Account
If the user does not exist, initiate the account creation process:
Generate Passkey and Create Wallet
After verification, generate a passkey and create a wallet:
Phone authentication verifies users via SMS OTP and sets up a biometric-enabled passkey for future logins.
Check User Existence
First, check if the user already exists by phone number:
For Existing Users: Login with Passkey
If the user exists, trigger the passkey login flow:
For New Users: Create Account
If the user does not exist, initiate the account creation process:
Generate Passkey and Create Wallet
After verification, generate a passkey and create a wallet:
After initial setup, users can log in using their passkey, which triggers biometric authentication:
This will prompt the user for Face ID or Touch ID verification before granting access to their wallets.
You can check if a user is already authenticated:
To sign out a user and clear their session:
After successful authentication, you can perform wallet operations:
For detailed transaction signing with specific blockchains (EVM, Solana, Cosmos), please refer to the respective blockchain integration guides.
For a complete implementation example, check out our Swift SDK example app:
After integrating Para into your Flutter app, you can explore other features and integrations to enhance your Para experience.