Sovereign Pay QR Edition 1.0Public PreviewSimple address scanning · Make a Payment · Create a Pay Page
1Funds to spend
Address(es) to pay from — enter one BSV address per line. You may combine funds held at several addresses. Only confirmed coins that are not already being spent by a pending transaction are included. Advanced: a WIF private key also works. In Edition 1.0, the QR reader accepts one address at a time.
Spendable-coin list (UTXOs) — one coin per line: transaction ID,output number,satoshis,address. A UTXO is a spendable coin from an earlier transaction.
Source address (optional — only for an older three-part coin list that has no address. It lets the tool confirm that the private key matches the coins.)
#
transaction ID : output #
satoshis
Signing on an offline device: find the coins here without entering a private key, carry this list to the same Sovereign Pay file on your offline device, and sign there. Bring only the signed transaction data back online. This helps keep the private key on the offline device.
Network providers (advanced)
These internet services are tried in order to find spendable coins and send signed transactions to the BSV network (broadcasting). This section is intended for advanced users.
2Payments
Destination address
Amount (BSV)
Note (optional — what the payment is for; you can choose below whether to include it in the blockchain transaction)
Payment note — only the highlighted part is yours to fill in
▸ Multiple payments (paste a list)
Enter one payment per line as address;amount;"note". Separate the three parts with semicolons and put the note in quotation marks.
When this list has content, it replaces the single payment above. Every line must pass validation before signing.
3Change & fee
Change address (where leftover funds return; it defaults to the first address you are paying from)
Network fee rate (satoshis per byte of transaction data)
find or paste spendable coins first
4Sign
Private key(s) in WIF format — enter one per line, matching each address you are paying from. Sovereign Pay processes them on this device and does not include them in its internet requests or save them in browser storage.
⚠ Privacy warning — you are paying from more than one address in a single transaction.
Combining coins from different addresses publicly links those addresses in one transaction and may lead observers to infer that one person controls them. Anyone examining the transaction can see the inputs together and compare their public histories. If you keep addresses separate for privacy, spending them together weakens that separation. To avoid this link, pay from one address at a time.
Risk acknowledgment — required before signing.
Sovereign Pay is non-custodial and cannot recover keys, reverse a transaction after it has been sent to the network, or eliminate risks arising from incorrect inputs, compromised devices or software, service-provider behavior, or user error. Review the transaction carefully before signing and again before sending it to the BSV network.
Sovereign Pay checks every new signature before showing the signed result. Technical detail: it uses ECDSA with the BSV-required signature setting ALL|FORKID (0x41). Consider testing a new address, key, or workflow with a small amount first.
5Review & result
Transaction preview — decoded from the signed transaction itself, not copied from the form
Signed transaction data (hexadecimal text)
“Broadcast” in Sovereign Pay means sending the already-signed transaction to a BSV network service so it can reach miners. This does not send your private key. Acceptance by a service does not guarantee that the transaction will be mined or confirmed. Using another service: copy the signed transaction data and submit it to a compatible BSV transaction-broadcast service. Anyone who receives this signed data may also be able to send it to the network.
Create a Pay Page — configure this file as a payment form
Fill in rules, preview, then download a configured copy (this setup UI is stripped from it). Publish or inscribe the copy; payers see your locked values. Locks are guardrails for honest payers — you enforce for real by only honoring on-chain payments with the right address, amount and note.
Form title
Destination address
Amount (BSV)
Note template — write {name} (or any {slot}) where the payer may type; everything else is fixed
Custom rule message (shown when a rule is broken)
Hide from payer
Providers JSON (optional override baked into the copy)
Business/contractor/client logo (optional header-logo substitution only — a contractor may use its own logo or the client’s logo; product names, BSVSearch.com attribution, the fee, and all other license rules stay unchanged)
Confirm sending to the BSV network
Read BSV address QR
QR images are processed on this device. The QR reader does not upload the image, save it in browser storage, or add it to the transaction.
