Sovereign Pay — QR Edition 1.0 — User Guide

QR Edition 1.0 is the Standard payment workflow plus a deliberately narrow QR reader. Each scan can fill one validated BSV address into an approved address field. It does not scan lists, payment requests, private keys, signing packages, signed transactions, or multipart payloads. Public Preview.

Read Choose Your Tool and Work Safely before using meaningful funds.

Verify before relying on this manual or tool. A copy received through another person, website, storage service, or message may have been modified. Altered code or instructions may differ from the release developed and tested by BSVSearch.com and may produce unexpected or unwanted results. Before entering a private key or using funds, compare the exact file's SHA-256 with the current filename, version, byte count, and TXID published at bsvsearch.com/sovereigntytools.web3. See Verify the file before trusting it for Windows and macOS instructions.

What the QR reader accepts

The reader can propose one mainnet P2PKH address for the source, a manually added source, destination, change, or Pay Page destination field. It rejects unsupported or invalid content without changing the field.

A scan is only a faster form of entry. The tool shows what it decoded and asks for confirmation before applying it. Confirm the address through a channel you trust; a valid checksum does not prove recipient identity.

The camera starts only after a camera action. Close or cancel the scanner when finished. Chrome, Edge, and other browsers may withhold live camera access when a downloaded HTML file is opened directly from a phone's local storage. This is a browser or page-context restriction; it does not disable image-based QR reading. If it occurs, choose a QR image, enter the address manually, or open the exact verified file with a trusted application that permits live camera access. See Live camera access for locally stored HTML files. Treat imported QR images as sensitive if they reveal financial relationships.

The five-step payment flow

1. Source and spendable coins

Enter or scan one or more source addresses, then find confirmed, currently spendable outputs. Unconfirmed incoming outputs, outputs already moving in the mempool, duplicates, and uncertain results are excluded and reported separately.

An offline signer can receive the public list txid,vout,satoshis,address by copy/paste. The QR reader in this edition does not transfer the list.

2. Payments and notes

Enter or scan a destination, then enter a BSV amount with a dot and no more than eight decimal places. Bulk payment rows remain manual text.

On-chain notes are off by default. Leave Embed notes on-chain unticked unless public, permanent disclosure is intentional. Tick it only before signing a transaction whose note you want embedded; otherwise the note remains only in the downloaded journal.

3. Change and fees

Confirm the change address is yours. Review the separate 0.01% Sovereign Pay tool fee and network miner fee.

4. Sign

Enter WIFs manually—QR Edition 1.0 does not scan private keys. Direct WIF entry is an expert, preferably offline workflow. Multi-source signing publicly links the source addresses and requires an extra privacy acknowledgement.

Every new signature is verified before a result is shown. Clear the WIF field promptly after signing; doing so preserves the already signed and verified result.

5. Review and send

Review the transaction decoded from its actual signed bytes. Editing a plan or source field after signing hides the stale result and requires a new review and signature.

For the built-in send action, the tool rechecks every input immediately before submission and compares the provider-returned transaction ID with the locally computed ID. Provider acceptance does not guarantee mining or confirmation.

Offline signing in QR Edition 1.0

Public UTXO text can be pasted into an offline copy and signed hex can be carried back. This edition does not scan those records or verify a returned signed transaction against the original online plan. Those structured workflows belong to QR Edition 1.2.

External submission of copied signed hex does not receive this edition's built-in input recheck or returned-ID comparison. Verify the decoded transaction on the offline signer, protect the hex from premature broadcast, and check the resulting transaction ID independently.

Journal and Pay Page

The CSV journal uses spreadsheet-formula neutralization, but still contains sensitive financial information. Store it accordingly.

#setup can create a configured Pay Page. Its client-side locks are user-interface guardrails, not cryptographic proof; the payer must still review the decoded transaction. QR Edition 1.0 can scan only the Pay Page destination address.

Status, licence, and credits

Provided as-is without warranty. This source-visible Public Preview was originally developed by BSVSearch.com. Embedded Project Nayuki-derived QR encoder material and jsQR 1.4.0 retain their respective licences; WhatsOnChain and Bitails are independent services. “QR Code” is a registered trademark of DENSO WAVE Incorporated.

See the shared Technical and Safety Appendix. Current versions, hashes, transaction IDs, and advisories: https://bsvsearch.com/sovereigntytools.web3.