DOGE Commerce Kit logo DOGE Commerce Kit
POS

Technical details

Technical guidance for builders who want DOGE to work in production.

Client-side wallet generation, payment URIs, local QR rendering, public balance lookup, transaction validation, receipts, and webhook handoffs — organized so you can wire Dogecoin into a real checkout without guessing which piece comes first.

Open Tools Open POS Papers and specs

Start here as a human

Pick the path that matches your job

Merchants usually need wallet → POS → receipt. Website builders need snippets → validation → webhooks. Read the section below that matches you, then open the linked tool when you are ready to try it.

POS wallet flow POS checkout Snippet marketplace FAQ

Wallet generation

Dogecoin key material

The POS Terminal's wallet setup derives compressed Dogecoin mainnet keys in browser JavaScript using secp256k1, WIF prefix 0x9e, and P2PKH address prefix 0x1e.

d = random 256-bit integer, 1 <= d < n
Q = d * G on secp256k1
compressed_pubkey = (0x02 if Qy is even else 0x03) || Qx
hash160 = RIPEMD160(SHA256(compressed_pubkey))
address = Base58Check(0x1e || hash160)
wif = Base58Check(0x9e || d || 0x01)

For serious funds, use a dedicated wallet or hardware wallet and treat this site as watch-only.

Payment URI and QR

Dogecoin request format

The local tools build a URI with the receiving address, optional amount, and memo. Wallet support varies, so test with a small amount before public checkout.

dogecoin:DExampleAddress?amount=25.00000000&message=DOGE%20sale

/qr.svg?data=dogecoin:D...address...

QR images are generated by this Django route, not an external image service.

Lookup and validation

Public blockchain data

Balance lookup uses the public address only. Transaction validation uses txids and public chain metadata to help staff decide whether the confirmation rule has been met. For production, configure a dedicated Dogecoin Blockbook-compatible indexer instead of relying on public demo APIs.

DOGE_BLOCKBOOK_BASE_URL=https://your-dogecoin-indexer.example

GET /api/v2/address/{address}?details=txs&pageSize=10

https://blockchair.com/dogecoin/transaction/{txid}

Never send WIF or private keys to a lookup service.

Webhook/API demo

Standalone Python receiver

The folder doge-pos-webhook-demo/ contains a small Python service with its own Dockerfile and compose file. It receives POS order events and stores them locally so you can attach wallet callbacks or processor webhooks.

cd doge-pos-webhook-demo
docker compose up --build

curl -X POST http://localhost:42100/webhook/payment \
  -H "Content-Type: application/json" \
  -d "{\"order_id\":\"demo-1\",\"status\":\"paid\",\"txid\":\"sample\"}"

Papers and specifications

Technical references for Dogecoin and blockchain systems

Dogecoin does not have a single canonical academic whitepaper like Bitcoin. For Dogecoin-specific details, use Dogecoin Core source/docs and payment specifications; for blockchain fundamentals, start with the papers below.

Dogecoin-specific specs

Payment URIs BIP 21 URI scheme

Reference for URI-style payment requests; Dogecoin wallets commonly adapt this pattern.

Wallet UX DogeConnect protocol

Dogecoin Foundation wallet-connectivity work for safer app-to-wallet interaction patterns.

Foundational blockchain papers

Smart contracts Ethereum Whitepaper

Useful contrast for account-based smart-contract systems compared with DOGE-style payments.

Security posture

Use the site as a commerce helper, not a custody platform