Sovereign Pay — Standard Edition 1.0 — User Guide

Standard Edition is the lean, self-contained payment builder and signer with deliberate manual entry and no camera or QR scanner. It holds no account or balance and does not provide key recovery. 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.

Before you begin

• Complete the external file-verification procedure above before opening the application.
• Use a trusted device and begin with fabricated data or a tiny amount you can afford to lose.
• Have the source address, destination address, and controlling WIF available through a secure process.
• Remember that direct WIF entry is an expert workflow. Prefer an offline signing device when practical.

The five-step payment flow

1. Source and spendable coins

Enter one or more source addresses and ask the tool to find confirmed, currently spendable outputs. Unconfirmed incoming outputs, outputs already being spent by a pending transaction, duplicates, and results without a safe confirmed status are excluded from the available total and reported separately.

For an offline signer, copy the public UTXO list in the form txid,vout,satoshis,address and paste it into the same edition on the offline device. Satoshi amounts are integers, not BSV decimal amounts.

2. Payments and notes

Enter a mainnet P2PKH destination and a BSV amount using a dot and at most eight decimal places. A valid Base58Check address detects many typing errors, but does not prove who owns the address.

For several payments, use the bulk list and correct every line-numbered error before continuing.

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 journal you choose to download.

3. Change and fees

Confirm the change address is yours. Inputs are consumed whole; value not assigned to a payment, the tool fee, or change becomes miner fee.

Sovereign Pay adds a 0.01% tool fee—one basis point of the amount sent, rounded up to a whole satoshi. The network miner fee is separate. Review both amounts before signing.

4. Sign

Enter one WIF for each source address, tick the risk acknowledgement only after reviewing the plan, and sign. Combining several source addresses in one transaction publicly links them; the tool requires an additional privacy acknowledgement.

The page verifies each new signature before displaying the result. After signing, clear the WIF field promptly. Clearing the WIF does not discard the already signed and verified result.

5. Review and send

Review the transaction decoded from the actual signed bytes: inputs, recipients, amounts, public notes, the Sovereign Pay fee, change, miner fee, and transaction ID. If a destination, source, amount, note, change, or fee setting is edited after signing, the visible result is invalidated and you must review and sign again.

For the built-in send action, the tool rechecks each input immediately before submission and rejects a provider-returned transaction ID that does not match the locally computed ID. A provider accepting the transaction does not guarantee that it will be mined or confirmed.

Offline signing in Standard Edition

Standard Edition can carry public UTXO text to an offline device and carry signed transaction hex back. It does not import a returned transaction and verify it against the original online plan. That exact-plan returned-transaction workflow is a QR Edition 1.2 feature.

If signed hex from Standard Edition is submitted through an external service, that path does not receive Standard Edition's built-in pre-submission input recheck or returned-ID comparison. Reconfirm the decoded transaction on the offline signer, protect the signed hex from alteration or premature broadcast, and verify the resulting transaction ID independently.

Payment journal

The result can be downloaded as CSV. The current release neutralizes spreadsheet-formula prefixes before ordinary CSV quoting. The journal can still reveal addresses, amounts, dates, transaction IDs, and notes; store it as sensitive financial information and open only a file you created or trust.

Create a Pay Page

The #setup workflow can create a self-contained payment form with configured destination, amount, and note behavior. Client-side locks are user-interface guardrails, not cryptographic proof. The payer must still verify the decoded signed transaction, and the 0.01% tool fee remains visible and applicable.

Common problems

All providers failed. Wait and retry, or paste public UTXO details manually. Do not paste a WIF into a provider website.

No matching key. The entered WIF does not control one or more source addresses, or the wrong compression form was used.

Insufficient funds. Reduce the payment or add spendable coins. The plan must cover payments, the tool fee, and the miner fee.

A result disappeared after an edit. This is the stale-result safety guard. Review and sign the changed plan again.

Status, licence, and credits

Provided as-is without warranty. The user is responsible for key custody and transaction verification. This source-visible Public Preview was originally developed by BSVSearch.com. Its embedded Project Nayuki-derived QR encoder retains its own licence. WhatsOnChain and Bitails are independent services with no affiliation implied. 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.