What stays public?
The goal is to receive payments without directly exposing your everyday business wallet. This build uses simulated payments.
Public wallet → private balance
In real payments, the payer address, token, amount, time, and interaction with RAILGUN may be public on-chain. The merchant’s everyday wallet and full private balance are not directly shown at checkout.
Checkout software needs the private receiving address to construct a payment. Hiding it on the page does not mean the payer cannot learn it. The application stores invoice details, payer addresses, and transaction hashes.
Local wallet & reconciliation
The planned integration keeps wallet credentials and payment scanning on the merchant’s device. Local reconciliation requires opening the workspace.
Payment confirmation and spendability are separate. Private POI can keep balances pending. These checks are not bypassed.
Receipts & withdrawals
Anyone with a receipt link can view the invoice amount and description. Transaction hashes may reveal the payer. Withdrawals to public wallets expose the destination and amount.
Private transfers and Broadcaster payments are not implemented. This application does not promise anonymity or untraceability.
Mock previewPayments, balances, and transaction hashes are simulated. Real receiving is not enabled.