Sovereign Pay — QR Edition 1.2

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. A QR may contain one address or several addresses, one per line. Advanced: a WIF private key also works.

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)

▸ 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.

Include notes in the blockchain transaction (if mined, the notes may become publicly visible and difficult to remove). This is off by default. Tick it only when public, permanent note disclosure is intentional; otherwise the notes remain only in the journal you choose to download.

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

Offline signing transfer — optional advanced workflow

Take payment details to the offline device

The signing package contains the spendable coins, payments, change address, fee setting, and note choice. It contains no private keys.

Bring the signed transaction back online

Keep the same signing package or payment plan loaded online. Before enabling network submission, Sovereign Pay checks that the returned transaction matches that plan and that every signature is valid.

Large QR transfers: Sovereign Pay may split large data into several QR codes. Scan every part. This detects missing or accidentally mixed parts, but it does not prove who created them; Sovereign Pay separately checks the completed package or transaction.

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. A WIF QR image is a plaintext copy of the private key; scan it only on a trusted offline device. Private keys are accepted from a single QR only, never multipart TKQR1.

Private-key QR warning — single QR only. The image contains the spend-capable key in plaintext. Never retain it in screenshots, camera rolls, cloud backups, or other untrusted storage. Multipart TKQR1 private-key transfers are rejected.

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.

I have read this notice. I understand and accept the disclosed risks and potential consequences of using Sovereign Pay, and I accept responsibility for verifying this transaction.

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.

1Funds to spend

2Payments

3Change & fee

Offline signing transfer — optional advanced workflow

Take payment details to the offline device

Bring the signed transaction back online

4Sign

5Review & result

Create a Pay Page — configure this file as a payment form

Confirm sending to the BSV network