Skip to main content
Use this path when your app owns the screens, copy, layout, and interaction model. Para handles authentication state, key management, embedded wallets, sessions, and signing, while your product decides how users move through the flow.

​
Choose This Path If

  • You want custom auth or wallet screens instead of Para’s modal.
  • You are building with Vue, Svelte, vanilla JavaScript, React Native, Flutter, Swift, or another non-React UI stack.
  • You are building a headless React flow or a direct Web SDK integration.
  • You still want Para to manage authentication, key shares, wallets, sessions, and signing.
Custom UI is a different path from modal customization. Para Modal is React-only. If you are building a React app and only need to style Para’s modal, use Use Para Modal and the modal customization docs.

​
Integration Lifecycle

1

Create a Para project

Create a project and API key in the Developer Portal, then review Developer Portal setup.
2

Choose your SDK surface

Use Custom UI with React hooks for headless React, Custom UI with the Web SDK for framework-agnostic web apps, or the matching mobile setup for React Native, Flutter, or Swift.
3

Build authentication screens

Implement the auth methods your app supports, then connect those screens to Para’s auth state and session lifecycle. For React custom UI, review the v3 configuration model so your screens respect partner-level settings.
4

Build wallet screens

Add wallet creation, wallet selection, address display, signing requests, and post-signing UI using the SDK methods for your platform.
5

Sign and transact

Use Sign with Para or the matching mobile signing guide to confirm the custom UI path end to end.
6

Prepare for launch

Review session management, the Go Live Checklist, and Production Deployment.

​
Next Docs

Custom UI with React hooks

Custom UI with the Web SDK

Svelte setup

Vue setup

React Native setup

Flutter setup

Swift setup

Sessions

Sign with Para