Wallet Preview
Questions about requests, review, supported capabilities, recovery boundaries, or app behavior.
Start with the right support path.
Wallet questions, business pilots, integration issues, and security concerns require different context. Never send a recovery phrase, private key, authentication token, production customer data, or signing material.
Business pilot
Propose a merchant, application, or agent integration for selected Preview evaluation.
Developer help
Check the Quickstart, API, protocol, and MCP guides before reporting an integration issue.
Security report
Report a potential vulnerability without including live secrets or sensitive user records.
Availability
Support follows the exact build and capability label.
A documented schema or example does not mean that every mobile client can sign every asset and network combination.
App availability
Android Preview distribution may be invitation-based. iOS availability may use a controlled TestFlight path. Do not install packages from an unverified source.
Network and asset availability
Use only capabilities explicitly shown as supported for the exact wallet build. Unsupported combinations should fail closed.
Business availability
Selected Preview pilots begin with sandbox and test flows. Live project onboarding and general pricing are not open.
Regional availability
Product and regulatory availability depends on the operating entity, user location, business model, and actual value flow.
Before contacting support
Share evidence, not secrets.
Useful reports are specific enough to reproduce while keeping credentials and personal information out of the message.
| Safe to include | App version, operating system version, approximate time, test or sandbox environment, screen name, redacted request ID, expected behavior, and observed behavior. |
|---|---|
| Do not include | Seed phrase, private key, authentication token, API key, complete wallet backup, production customer record, unredacted personal data, or signing material. |
| Payment concern | Stop before signing if the amount, asset, network, recipient, fee, or context is unexpected. Do not rely on a support message to override transaction facts. |
| Security concern | Use the security channel and begin with a minimal impact description. Wait for a coordinated method before sending sensitive proof. |
Legal and release status
Preview language is intentionally limited.
The current site explains a product direction and evaluation program. It does not announce general availability or make a jurisdiction-independent regulatory claim.
Terms and notices remain release-gatedFinal user terms, privacy notices, supported regions, fees, dispute boundaries, and live-service commitments must correspond to the released artifact and operating entity before live availability.
Frequently asked
Preview support basics.
Can support recover my seed phrase or private key?
No. VelarumPay support should never ask for a recovery phrase or private key, and the server does not hold user signing material.
Where can I download the app?
Use only the distribution path provided for your approved Preview build. General app-store and direct-download availability is not announced on this site yet.
Can a merchant or agent approve a request for me?
No. The current product boundary requires user review and local signing for real payments by default.
Does a pilot request create a production account?
No. It begins an evaluation conversation. Production access remains subject to product, legal, security, operational, and release decisions.
Still need help?
Send a concise, redacted description through the support path that matches your question.