Sovereign Pay QR Edition 1.6 — Obsidian VaultExpanded payment and signing QR · 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. A QR may contain one address or several addresses, one per line. Advanced: a WIF private key also works.
Balance lookup providers (advanced)
These internet services are tried in order to find spendable coins and check that transaction inputs are still spendable. Payment processors are configured separately below. 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". Amounts use BSV. 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

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.

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

Payment processor

Applies to payments signed here and imported signed transactions. Automatic tries the next processor if a service is unavailable. A pending or rejected response stops automatic retries.

Payment processors (advanced)

Use settings from a processor you trust. Validation checks the configuration on this device; it sends no payment or network request. Browser access must be allowed by the chosen service. Settings apply to this open page; copy them to keep them. Do not put a private key here or distribute a copy containing an API secret.

Connection format reference

Each entry defines name, HTTPS url, headers, request, response and timeoutMs. Request format is json or text. Use the exact string {rawTx} for the signed transaction. Response format is json, text or json-or-text. txidPath is a dot-separated field path; an empty path means the entire response. For processors that return status information, specify statusPath and non-overlapping accepted, pending and rejected arrays. Unknown statuses remain pending. The returned transaction ID must always match the signed transaction. No executable code is supported.