VEY LORAH.

HELP & ONBOARDING

Start with
your keys.

Understand your wallet, track a payment and keep control of your funds.

Release preparation: signed Windows, Android and iPhone apps are not published here. The software package contains development source. Do not use an unverified app for valuable funds.

PERSONAL WALLET

Create. Back up. Verify.

  1. Use a verified release for your device and compare its published checksum before installation.
  2. Create a wallet locally with a strong, unique wallet password. The password protects the wallet file. Your recovery words restore the wallet.
  3. Write recovery words down privately and keep them offline. Anyone with these words can control your funds. Support never needs them.
  4. Before receiving valuable funds, test restoration and a small send/receive transaction on the intended network.
  5. Check the node and network identity. A Veylorah wallet does not become a Monero or Ethereum wallet by changing an RPC URL.
Why does my balance show unavailable or zero?

The wallet must scan the correct blockchain. Check its connection, synchronization progress and restore height. A restore height that is too recent can miss older receipts. An unavailable node is not proof that your money is gone.

Why can I see funds but not spend all of them?

New receipts can require more blocks before they unlock. Early legacy outputs may lack enough matching decoys. The wallet keeps these funds visible and explains the restriction. Never mark an unfamiliar public node as trusted just to bypass a message.

What happens when I lock the app?

Locking closes the active wallet. Open it again with its local password. The device and operating system also need a strong lock. Closing the app does not erase backups or protect an already compromised device.

BUSINESS ONBOARDING

Track receipts.
Keep spending separate.

  1. Create and back up your owner wallet on a device you control.
  2. Prepare a separate watch-only wallet for the merchant service. A private view key exposes financial receipt information even though it cannot spend funds. Treat it as confidential.
  3. Run authenticated wallet RPC on loopback, then configure the merchant service for the exact frozen genesis. Never open wallet RPC to the public internet.
  4. Use the operator dashboard to create an invoice with an exact Veylorah amount and expiry.
  5. Share its unique checkout link. The checkout shows a receiving address and payment status. It never asks the customer for recovery words.
  6. Wait for the required confirmations and unlocked payment state before treating the invoice as paid. Partial, late and excess payments need review.
  7. Export accounting records from your authenticated dashboard. Coin amounts are not fiat valuations and are not a complete tax calculation.
Does watch-only mean no financial information is exposed?

No. The service can identify incoming receipts for the watch-only wallet. It does not need the private spending key or owner recovery words. Restrict access to the service, its database, its view key and its backups.

Can a paid invoice become unsettled?

Yes. A chain reorganisation can remove or reduce confirmations. Payment tracking rechecks chain observations. For higher-value orders, use an appropriate confirmation policy and review network conditions.

OWNER APPROVAL

Refunds are real payments.

A merchant refund request is an instruction for review, not permission for the server to spend. Confirm the customer's receiving address through your normal customer-service process. Do not derive a refund address from transaction inputs.

  1. Create a refund request against the invoice.
  2. Import or review its destination and exact amount in the owner wallet.
  3. Review the fee and total again, then explicitly approve submission.
  4. Keep the transaction record. A typed transaction hash alone does not prove a refund reached the customer.
  5. Where supported, supply a transaction proof tied to the refund request. Verification and confirmation tracking establish its recorded payment state.

A payment request can be altered before it reaches you. Independently confirm the recipient and amount before signing. Cancelling a request does not reverse a transaction already sent.

TECHNICAL SUPPORT

Share the problem.
Keep the keys.

For a support request, record the app/service version, device platform, approximate time, synchronization status and a brief description of what happened. Share only the information needed to investigate.

Do not attach recovery words, spending keys, private view keys, wallet files, passwords, authentication tokens or unreviewed raw logs. Screenshots may contain addresses, amounts or customer information.

The merchant dashboard provides a limited diagnostic export. Review it before sharing. There is no automatic upload or external support submission.

Project security contact: Ashar Iqbal. A verified public support channel and staffed response schedule have not yet been published.

What should I do if I suspect a wallet or device compromise?

Stop entering recovery material into that device. Use a separate trusted device and a verified wallet release to assess recovery. Never send secrets to someone who offers to “repair” or “synchronize” your wallet.