The merchant no longer waits in the dark for block confirmation. The payer no longer sees only an address and an amount. The wallet can inspect vendor details, fixed outputs, line items, fees, and a relay contract before signing.
DogeConnect defines how a vendor sends a detailed payment request to a wallet, and how a Payment Relay validates the signed transaction before it reaches the network.
The authoritative specification lives at connect.dogecoin.org.
Mental model
QR points at request
Envelope proves intent
Relay reports progress
Three parts
The protocol has three pieces that work together, and each piece maps to a page in this debugger.
Payment QR codes
URIs that point at a hosted request, not just an address. dogecoin: adds dc (envelope URL) and h (relay key hash). dogeconnect: drops legacy fallback.
Payment Envelope
Signed JSON (version, payload, pubkey, sig) with vendor branding, line items, taxes, and the exact outputs to pay.
Payment Relay API
relay/pay and relay/status POST endpoints. The wallet submits a signed transaction and polls for accepted, confirmed, or declined.
How a payment moves
Customer wants to buy from a vendor.
Vendor software asks the Payment Relay to start a payment with itemised details.
Relay returns a QR URI and payment ID.
Customer scans the code. The wallet fetches the Payment Envelope from the dc URL.
Wallet checks the h hash against the envelope pubkey to catch tampering.
Wallet verifies the BIP-340 Schnorr signature, shows the itemised total, and asks for confirmation.
Customer signs. Wallet POSTs the transaction to relay/pay.
Relay validates outputs, fee, and size limits, then broadcasts to Dogecoin.
Vendor hears accepted, then confirmed once enough blocks arrive. Confirmation depth is the relay's call.
What merchants get
- Receipts before signing
- Customer sees vendor name, logo, SKUs, tax, and fees in the wallet.
- Fixed outputs
- Amounts and addresses come from the signed envelope, not an editable amount field.
- Earlier feedback
- Relay status beats waiting to spot the transaction on-chain yourself.
- Risk policy you control
- Your relay sets minimum fees, max transaction size, and required confirmations.
- Backward-compatible QR codes
- Legacy wallets still read the embedded address and amount. DogeConnect wallets use the full payload.
What wallet and relay builders get
- URI parsing
- Explicit rules for dogecoin: (dc and h must appear together) and dogeconnect: schemes.
- Cryptographic checks
- Pubkey hash, double-SHA256 payload hash, BIP-340 Schnorr verify.
- Amount encoding
- 8-DP string amounts so JSON floats do not eat precision.
- Idempotent relay/pay
- Retries must not double-charge.
- HTTP semantics
- 400/403 permanent, 500/503 retry with backoff.
- Reference code
- dogeorg/dogeconnect-go on GitHub.
Full specification
This page is a summary. Authoritative detail lives in the official book.
Payment QR-Code
connect.dogecoin.org/qr_codes/qr_codes.htmlPayment Envelope
connect.dogecoin.org/payment_envelope/envelope.htmlPayment Relay
connect.dogecoin.org/payment_relay/relay.htmlSchema Reference
connect.dogecoin.org/schema_reference/schema_reference.htmlPrintable version: connect.dogecoin.org/print.html
Try it here
OnlyDoge DogeConnect Debugger runs locally — no live relay writes unless you opt in.