Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/pacifica-fi/docs-migrate/llms.txt

Use this file to discover all available pages before exploring further.

Pacifica runs on Solana, and most connectivity issues stem from browser extension conflicts, stale wallet permissions, or incorrect network settings. This page walks through every common problem — from a stuck “Connect Wallet” loop to recovering assets after the embedded-wallet provider migration — so you can get back to trading as quickly as possible.

Wallet Connection Troubleshooting

If you’re seeing a repeated Connect Wallet loop, failed transaction signing, or your wallet extension isn’t loading, work through the steps below in order.

Step 1 — Update Your Wallet Extension

An outdated extension is the most common cause of connection failures.
  1. Open your browser’s extension manager (e.g., chrome://extensions).
  2. Confirm the wallet extension is enabled.
  3. Check for an available update and install it.
  4. Reload the Pacifica page after updating.

Step 2 — Hard Refresh and Clear Cache

A stale browser cache can cause the wallet modal to misbehave.
  • Windows: Ctrl + Shift + R
  • Mac: Cmd + Shift + R
If the problem persists after a hard refresh, clear your browser cache entirely and reload the page.

Step 3 — Disconnect and Reconnect Your Wallet

Stale trusted-site permissions inside your wallet can prevent a clean connection.
  1. Open your wallet extension and navigate to Settings → Trusted Apps.
  2. Find Pacifica in the list and remove it.
  3. Reload the Pacifica page and reconnect your wallet from scratch.

Step 4 — Verify You Are on Solana Mainnet

Pacifica’s deposit and withdrawal layer operates exclusively on Solana Mainnet.
  • Open your wallet and confirm the selected network is Solana Mainnet.
  • If you’re on Devnet or Testnet, switch away and back to Mainnet to reset the RPC connection.
  • Confirm you are not connected to an unsupported custom cluster.

Step 5 — Disable Conflicting Wallet Extensions

Multiple Solana wallet extensions installed in the same browser frequently conflict with one another.
  1. Open your browser’s extension manager.
  2. Temporarily disable all Solana wallet extensions except Phantom.
  3. Attempt to connect again.
If this resolves the issue, re-enable your other extensions one at a time to identify the conflict.

Additional Fallback Steps

If the steps above don’t resolve the issue:
  • Open Pacifica in an incognito / private browsing window (ensure your wallet extension is allowed in incognito).
  • Do a full browser restart.
  • Restart your device to clear any system-level networking state.
If you still can’t connect after all of the above, contact Pacifica support and include your browser name and version, Phantom version, operating system, a screenshot of any error message, and whether you are on desktop or mobile.

CloudFront 403 Error (API Users)

After Pacifica’s infrastructure migration to CloudFront, GET requests that include any request body — even an empty JSON object {} — are rejected with a 403 "The request could not be satisfied" error. This is a breaking change from previous behaviour.
GET requests must not contain a body. Remove any -d '{}' or equivalent payload flag from your requests. Broken — will return 403:
curl -X GET \
  -H "PF-API-KEY: your-api-key" \
  -H "Content-Type: application/json" \
  -d '{}' \
  "https://api.pacifica.fi/api/v1/positions?account=..."
Correct — no request body:
curl -X GET \
  -H "PF-API-KEY: your-api-key" \
  "https://api.pacifica.fi/api/v1/positions?account=..."
Pass all parameters as query string arguments rather than in a request body for GET endpoints.

Deposit & Withdrawal Issues

Deposits and withdrawals on Pacifica use USDC on the Solana network exclusively.
Sending funds via any other network (Ethereum, Arbitrum, etc.) or in any other token (USDT, SOL, etc.) will result in funds that cannot be credited or recovered by Pacifica.
Common deposit issues:
  • Funds not appearing — Confirm the on-chain transaction is finalized on a Solana block explorer before contacting support. Network congestion can cause delays.
  • Deposit below minimum — Deposits under 10 USDC will not be automatically credited. Send additional USDC to the same address to bring the total to the minimum.
Common withdrawal issues:
  • Withdrawal error — Your wallet must have a valid, initialized USDC token account. Ensure your wallet holds a non-zero amount of USDC to initialize the account, then retry.
  • Withdrawal delayed — Solana network congestion can slow processing. Check network status and retry.
Always use the Pacifica front-end for deposits and withdrawals. For large transfers, send a small test transaction first to verify the destination address and network are correct.

Mobile App — Account Deletion

To request deletion of your Pacifica Mobile account, follow these steps:
  1. Join the Pacifica Discord.
  2. Open a support ticket in the appropriate channel.
  3. Include the wallet address associated with your account so the team can identify it.
Never share your private key, seed phrase, password, or any other sensitive wallet credentials in a support ticket or with anyone claiming to be Pacifica staff.
After your request is reviewed, Pacifica will delete or de-identify personal data that is no longer needed to provide the service. Some records may be retained where required for legal, security, anti-fraud, accounting, compliance, dispute-resolution, or regulatory purposes. Note: On-chain wallet activity is public blockchain data and cannot be deleted by Pacifica or any third party.

Recover Assets After Reown → Privy Migration

Pacifica has migrated its embedded and social login flow from Reown to Privy. If you originally signed into Pacifica with a Reown social login (Email, Google, X, etc.), your assets remain in the same on-chain wallet — you just need to export the private key from Reown and import it into a self-custodial wallet to regain full control.
This recovery process applies only to legacy Reown social login users. If you originally connected a self-custody wallet (Phantom, Solflare, Backpack, Ledger), your wallet is unchanged — you do not need this guide.
Never share your private key with anyone, including Pacifica support. Only export it from Reown’s official site, and store it securely offline before proceeding.
A video walkthrough of the full recovery process is available at https://www.youtube.com/watch?v=sdaX-H1bgv4.
1

Go to the Reown Secure Recovery Page

Navigate to https://secure.reown.com/ — this is Reown’s official wallet recovery portal.
2

Sign In with Your Original Social Account

Use the exact same social login method (Email, Google, or X) that you previously used to access Pacifica. This authenticates you as the owner of the embedded wallet.
3

Export Your Private Key

Open the wallet management flow within Reown’s recovery page and follow the prompts to export your private key. Copy and store it in a secure, offline location (e.g., written down and locked away) before leaving the page.
4

Import the Key Into a Self-Custodial Wallet

Import the private key into a supported self-custodial Solana wallet such as Phantom, Solflare, or Backpack. Each wallet’s import flow is typically found under Settings → Import Wallet or Add Account → Private Key.
5

Reconnect to Pacifica

Once the key is imported, open Pacifica and connect using the newly imported wallet. Your on-chain assets and positions will be accessible immediately.

Need Help with the Recovery?

If you run into issues during recovery, contact support via the Pacifica Discord and include:
  • The social login method you originally used (Email, Google, X, etc.)
  • Whether you can still access that same social account
  • A screenshot of any error or blocked step you encounter

Pacifica Discord

Open a support ticket for account, connectivity, or migration help.

Follow on X

Stay updated on platform changes and infrastructure notices.

Build docs developers (and LLMs) love