Dogecoin

Accept DOGE to fresh addresses derived from your xpub or dgub. NoHoldPay watches the chain - no seed phrase, no custody.

Networks

	Mainnet	Testnet
Chain key	`DOGE`	`DOGE_TESTNET`
Wallet key	`xpub` or `dgub`	`tpub` or `xpub`
Address format	`D...` (legacy P2PKH base58check)	`n...` (legacy P2PKH base58check)
Confirmations	40 (~40 minutes)	8 (~8 minutes)
Min invoice	$1.00	$0.10
Payment window	60 minutes	60 minutes
Late-grace revival	12 hours	12 hours
Reorg-grace window	30 minutes	5 minutes (~5 blocks)
RBF (fee bumps)	Not supported	Not supported

NoHoldPay uses legacy Dogecoin P2PKH addresses only (BIP-44 m/44'/3'/0'). No witness-segregation, no P2SH, no MWEB.

Confirmation count note. The 40-confirmation default reflects Dogecoin's historical security profile. At DOGE's 60-second target block time, a confirmed payment takes about 40 minutes wall-clock - longer than Bitcoin's 6 confirmations but appropriate for non-custodial payments where finality matters more than UX latency.

Wallet setup

Dogecoin has fewer merchant-grade wallet options than BTC, LTC, or BCH. Use Dogecoin Core unless you've already tested another wallet with high gap limits and address import.

Wallet	Best for	Notes
Dogecoin Core	Watching and recovery	Best-supported option for finding missing DOGE payments.

Avoid MultiDoge and Electrum-DOGE - they aren't suitable for new merchant setups.

If you already run Hodlall for other coins, it can hold Dogecoin too. Confirm the exported key is an account-level xpub or dgub before pasting it, and use NoHoldPay's gap filler if the wallet stops discovering paid addresses. See Choosing your wallets.

What to paste

Mode	Chain	Paste this	Do not paste
Live	`DOGE`	Account-level `xpub` or `dgub`	Seed phrase, private key, `xpriv`, receive address
Test	`DOGE_TESTNET`	Account-level `tpub` or `xpub`	Seed phrase, private key, `xpriv`, receive address

One account key per NoHoldPay account. An account key can only be bound to one NoHoldPay account at a time. Two accounts on the same key derive byte-identical addresses at the same derivation index, so one customer payment could be credited against an order in each. The second bind is rejected when you add the wallet. If you run more than one account, use a separate account key for each. Retiring a wallet releases its key, so moving your business to a different account still works.

Live setup

Open or create a BIP-44 DOGE wallet that can export an account-level public key.

Export the account-level public key (may start with xpub or dgub).

Screenshot

Dogecoin wallet showing the account-level extended public key

add image at public/images/guides/doge-core-xpub.png

In NoHoldPay, Add Wallet -> choose DOGE -> paste the key.

Create a small live payment and verify the generated D... address matches your wallet.

Dogecoin Core has no simple gap-limit setting - plan to use NoHoldPay's gap filler if your wallet stops discovering paid addresses.

Test setup

Start your Dogecoin wallet in testnet mode and export the account-level testnet public key.

In NoHoldPay, Add Wallet -> choose DOGE_TESTNET -> paste the key.

Fund the wallet, create a test payment, pay it, and wait for 8 confirmations.

Testnet faucet: faucet.doge.toys.

Address verification

The first generated address must match the one your wallet shows at the same derivation path:

Mode	External receive path	Address
Live `DOGE`	`m/44'/3'/0'/0/index`	`D...`
Test `DOGE_TESTNET`	Account key `/0/index`	`n...`

Gap filler

Dogecoin Core has no console command to raise the gap limit. Plan ahead:

Keep payment volume below what your wallet can scan.
Enable NoHoldPay's gap filler before the first warning appears.
Import missing addresses manually into Dogecoin Core if needed.

Fixing a gap:

Option	What happens	Cost
Do it yourself	Import the missing addresses, or build a multi-output send if your wallet supports it.	Miner fee from your wallet.
NoHoldPay handles it	Signed and broadcast by NoHoldPay.	Dust + miner fee + $0.50 platform fee, deducted from Prepaid Credit.

The DOGE miner fee is pass-through (no markup). Automatic fee bumps are not available for DOGE - NoHoldPay broadcasts DOGE gap-filler transactions as non-replaceable and does not run an automatic bump path for this chain, so a stuck transaction cannot be replaced. Contact support if a platform-handled transaction sits unconfirmed for more than an hour.

Multi-transaction payments

If your customer's wallet sends in multiple transactions (e.g., split-utxo wallets, partial payments), NoHoldPay aggregates all confirmed transactions to the same invoice address. The payment confirms once the cumulative amount reaches the expected total AND each contributing transaction reaches the 40-confirmation threshold (8 on testnet).

Underpayment tolerance

Customers who send slightly less than the invoiced amount can still complete the payment without merchant action:

Default tolerance is 0.5% of the invoiced amount (you can change it in Settings).
A customer who sends floor(expected x 0.995) smallest units passes the tolerance check (integer-domain comparison so wallet floor-rounding doesn't cost the customer a cent).
Below the tolerance, the payment lands in underpaid state. The merchant can either accept the shortfall via the Accept this payment action on the payment page OR wait for the customer to top up within the 12-hour late-grace window.

Not supported

MultiDoge
Electrum-DOGE
Custodial or exchange deposit wallets
Automatic RBF fee bumps (not implemented for DOGE)
Paste-transaction-hash claim from the hosted checkout (HD-derived addresses are unambiguous to the watcher, so no claim affordance is needed)

Recovery

Your DOGE seed phrase remains the recovery tool. NoHoldPay only stores your public key.

If your wallet does not show a paid address:

Import the missing address into Dogecoin Core, or restore the wallet and rescan with -keypool=500.
Use the Recovery Kit for derivation details.

DOGE recovery can be more manual than BTC, LTC, or BCH because Dogecoin Core has no change_gap_limit console command. Test your recovery workflow before running high DOGE volume.