Connect deliberately
Scan or open an invitation, verify the requester, and approve only the scopes you expect.
A wallet built around review, not blind approval.
VelarumPay helps you understand who is asking, what will move, where it will go, and why—before you approve and sign on your own device.
The experience
Four moments where you stay in control.
A connection can request a capability. It does not receive your key or permission to sign.
Read the request
See payment facts and transaction context without letting descriptive copy override the destination.
Approve locally
Confirm the request on your device. Real payments require your approval by default.
Manage access
Review active connections, reject requests, and revoke access when a relationship ends.
What to check
Pause on the facts that cannot be talked away.
If the story and the transaction disagree, stop. A familiar logo, merchant name, or agent message is never a substitute for the actual payment facts.
01
AmountDoes the exact value match what you agreed?
02
Asset and networkAre you paying with the intended asset on the intended rail?
03
RecipientDoes the destination match the verified party?
04
Fee and expiryAre the cost and time boundary acceptable?
Your responsibilities
Non-custodial means your recovery material matters.
VelarumPay cannot recover a lost recovery phrase or reverse a correctly signed irreversible network transaction.
Protect the recovery phrase
Keep it offline, private, and separate from chat, email, cloud notes, screenshots, and support conversations.
Use device protection
Keep your operating system current and use the app's local authentication before sensitive actions.
Treat urgency as a warning
Reject requests that rely on pressure, surprise, mismatched recipients, or instructions to bypass review.
Preview access
Evaluate first.
Preview availability is controlled. App distribution, networks, assets, and live payment support may differ by build and region.
Check current boundariesLearn the approval modelUnderstand requests, facts, context, and connections.
Use only explicitly supported test pathsDo not infer support from a token name, logo, or example.
Do not deposit funds based on Preview copyWait for the exact wallet build and supported-capability labels.
Common questions
Before you begin.
Can an AI agent spend by itself?
No. In the current product boundary, an agent can create and read requests within approved scopes, but real payments require the user to review and sign by default.
Does VelarumPay keep my private key?
No. Seed phrases, private keys, and derived signing material remain on the user's device. Platform services do not sign user transactions.
Can VelarumPay reverse a payment?
VelarumPay cannot promise reversal of an irreversible network transaction. Always verify the facts before signing.
How do I know which networks and assets work?
Use only the support labels shown for your exact Preview build. Examples and documentation are not a promise that every client can sign every network and asset combination.
Ready to evaluate the wallet?
Review Preview availability and safety boundaries before installing or funding any wallet.