Sovereign Pay — Standard Edition 1.0

1Source & UTXOs

Source address(es) — one per line. You can spend several wallets at once. (A WIF also works; its address is derived.) Only confirmed coins that are not already being spent by a pending transaction are included.

Network providers (advanced)

Tried in order for finding spendable coins and sending signed transactions to the BSV network (broadcasting). Edit freely — if one service disappears, point to another. WhatsOnChain-compatible APIs use type "woc"; Bitails-style use "bitails".

2Payments

Destination address

Amount (BSV)

Note (optional — what this payment is for; can go on-chain below)

▸ Multiple payments (paste a list)

One payment per line: address;amount;"note" — semicolon separators, note in quotes (single/double/curly all accepted; semicolons inside quotes are treated as note text). Designed for bulk text pasted from a spreadsheet via a text editor.

When this list has content, it replaces the single payment above. Every line must pass validation before signing.

Embed notes on-chain (OP_RETURN — included in the signed transaction and, if mined, potentially visible through blockchain explorers). 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 (defaults to the source address — every satoshi not sent or paid as fee returns here)

Fee rate (sat/byte)

scan or paste UTXOs first

4Sign

Private key(s) (WIF) — one per line; one for each source wallet. The signing code processes these values locally. Sovereign Pay does not include them in its network requests or write them to browser storage.

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.

Signing uses ECDSA with the BSV-required sighash ALL|FORKID (0x41). Every signature is independently re-verified before the signed result is displayed. Consider testing a new address, key, or workflow with a small amount first.

5Review & result

Decoded preview — read from the actual signed bytes, not the form

Signed raw transaction (hex)

“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 hex and submit it to a compatible BSV transaction-broadcast service. Anyone who receives the signed hex may also be able to send it to the network.