New to DigiDollar? Start with WHAT_IS_DIGIDOLLAR.md for the friendly introduction, then come back here for quick answers.
Yes. To detect DigiDollar payments you need a DigiByte Core node running a hot wallet (an online wallet that holds the keys to your receive addresses). DigiByte Core v1 has no DigiDollar watch-only mode, so the node that spots your payments must hold the keys itself.
The recommended pattern is to keep only a small balance on that hot wallet and sweep funds to cold storage on a schedule. The operator guide walks through the setup.
You do — it's fully non-custodial. Payments land directly in a DigiByte wallet you control. There's no payment processor, exchange, or company sitting in the middle, and no one can freeze, delay, or claw back your funds.
There are no processor or gateway fees. No Stripe, PayPal, Coinbase Commerce, or BitPay taking a percentage. The only cost is the ordinary DigiByte network (miner) fee, which is tiny — a fraction of a DGB — and, importantly, it's paid by the buyer, not you.
Fast. DigiByte produces a block every 15 seconds, so a typical small payment can be credited in about 90 seconds (6 confirmations). Larger amounts wait for more confirmations (see below), but even those settle in minutes, not hours.
They need a little DGB as well. DigiDollar is exact-dollar value, but the network fee is always paid in DGB — a wallet holding only DigiDollar can't send it. Make this clear in your checkout UI, e.g. "You'll also need ~0.1 DGB for the network fee."
Yes. DigiDollar activated on the DigiByte mainnet in 2026 and is live in production today. You can see it accepted for real at BlockIndex.AI (Pay with Crypto → DigiDollar), running this exact toolkit.
The toolkit re-verifies every payment against the invoice amount and returns a clear status:
- Exact amount → the invoice is marked for credit once it has enough confirmations.
- Underpaid → the invoice reports
underpaid; you can ask the customer to send the difference, or refund and cancel. Don't fulfill the order. - Overpaid → the invoice still credits (the customer paid at least the amount due); handle any excess as a refund per your own policy.
Because 1 DD = $1.00 exactly and all amounts are integer cents, there's no exchange-rate ambiguity about what "the right amount" is.
Yes. The same toolkit handles DigiByte (DGB) payments as well as DigiDollar. DGB is a normal (volatile-price) cryptocurrency, so accepting it involves a price quote at invoice time, whereas DigiDollar is always exact dollars. See ACCEPTING_DIGIDOLLAR_AND_DGB.md for both.
The toolkit picks a sensible default based on the US-dollar value of the payment, and every tier is override-able via environment variables:
| Payment value | Confirmations | Approx. time |
|---|---|---|
| Under $100 | 6 | ~90 seconds |
| $100 – $10,000 | 20 | ~5 minutes |
| Over $10,000 | 60 | ~15 minutes |
Higher-value payments wait for more confirmations because the cost of a reversal is higher. For most everyday products, the 6-confirmation tier is what you'll use.
Refunds are a normal outbound payment: you send DigiDollar (or DGB) from your wallet back to the customer's address, just like any other transaction. Because you control your own funds, there's no processor to request a refund from and no approval to wait on — you simply send the money back. Keep your refund policy clear to customers, since blockchain payments are final and can't be reversed by a third party.
Yes. This code was extracted from BlockIndex.AI's live implementation — the first published DigiDollar acceptance integration anywhere — and it's the same code accepting real payments in production today. It ships with a hermetic unit test suite and a runnable demo merchant. It's MIT-licensed: use it, fork it, and sell things with it.
- Developer chat (Gitter): https://app.gitter.im/#/room/#digidollar:gitter.im
- DigiByte discussions: https://github.com/orgs/DigiByte-Core/discussions
- This toolkit's guides: ACCEPTING_DIGIDOLLAR_AND_DGB.md · ARCHITECTURE.md · RESOURCES.md
Still stuck? The demo merchant boots with no node at all (mock mode) — the fastest way to see the whole flow end to end.