Skip to main content
Deploy your Para integration to production by updating configurations and ensuring secure settings for real users.

​
Prerequisites

You need these components before deploying to production:
  • A working Para integration in development/beta environment
  • Production API credentials from the Para Developer Portal
  • Production domain with HTTPS enabled
  • Latest Para SDK version installed

​
Deployment Steps

1

Upgrade to Latest Para Version

Update your Para SDK to the latest version before going live. Use the newest v2.0 release for all projects to benefit from improvements and fixes.
Check your @getpara/* package versions and update to the latest stable release. Latest SDK versions resolve many integration issues.
Align your project with the current Para releaseto access recent features and security patches for real users.
2

Generate Production API Key

Create a production API key in the Para Developer Portal for your live environment.
3

Update Environment Variables

Replace development credentials with production values in your environment variables.
Update all secrets and URLs in your .env file for production, including callback URLs and API endpoints.
4

Switch to Production Environment

Configure your integration to use the production environment instead of beta/development. Para provides two hosted environments: BETA for testing and PROD for live use.Update your initialization from:
Development
const para = new ParaWeb(Environment.BETA, PARA_API_KEY);
To:
Production
const para = new ParaWeb(Environment.PROD, PARA_API_KEY);
Para’s Beta and Production are separate environments. Wallets and users are not shared between them. Your production environment starts with no users, and requires a distinct production API key.
5

Configure Allowed Origins

Update allowed origin settings in the Para developer portal to include your production domain. This Domain Security setting restricts API usage to specified origins.Add entries like https://yourapp.com and production subdomains to the Allowed Origins list. Remove development URLs like http://localhost:3000 if no longer needed.
HTTPS is required in production. Configuring allowed origins prevents unauthorized domains from using your Para integration.
Allowed Origins are only supported for web integrations, not server or mobile.
6

Configure App Settings

Review your Para integration settings for production, especially user communications and UI:

​
Verification Redirect URL

Set the verification redirect URL to point to your production application’s confirmation page. This URL appears in verification emails Para sends to users. Update from localhost URLs to your live domain.

​
Email Notification Preferences

Choose appropriate email settings for production. Para can send welcome emails and optional backup kit instructions to new users.Configure email templates and branding (logo, app name) for real user emails based on your user experience strategy.

​
Branding and UI Configuration

Customize the Para modal or widget to match your production app’s branding (colors, fonts, icons). Configure theme options through the Para SDK or developer portal’s branding section.
7

Deploy and Validate

Deploy your updated application with production settings and perform end-to-end testing with real scenarios:

​
Test User Sign-Up/Login

Create a new user account using a real email address or phone number. Ensure OTP codes are delivered and users can complete verification and wallet creation.
Test emails like dev@test.getpara.com and dummy phone numbers will not work in production. Production requires real contact information and OTP verification.
Ensure you are signing transactions on the appropriate network.

​
Functionality Check

Verify wallet operations work with production settings. Test retrieving wallet addresses or making test transactions on mainnet to confirm Para’s production environment interacts correctly.Verify session management and security features (persistent login/logout) behave as expected.

​
Monitor and Review

Watch browser console and backend logs for errors like misconfigured API keys or CORS issues. If you encounter CORS or CSP errors, verify the origin matches your deployed URL exactly.

​
Pricing Information

With Para Free Tier your first 1,200 monthly active users are free. Paid plans require billing information to upgrade.

​
Next Steps

Chain Support

Para Pricing