A hot wallet gives PD Crypto Pay the ability to send from a supported wallet on your billing server. Use it only when you intend to enable sending, refunds or sweeps. A watch-only receiving wallet does not need this access.

Choose protection deliberately

The module supports hot-wallet sending for Ethereum-compatible and Tron networks. Bitcoin and Litecoin receiving wallets remain watch-only. A hot wallet’s spending key is stored encrypted on your installation, which makes server access and key handling part of your fund-control model.

Automatic protection allows unattended sending. Manual protection requires the spending passphrase for a send and cannot run an unattended sweep that needs that unlock. Do not choose Automatic solely to get past a passphrase prompt without deciding that you want unattended access.

Prepare a supported hot wallet

1. Open PD Crypto Pay → Wallets → Add a wallet and choose the supported hot-wallet option for the intended network.
2. Follow the form for generating or importing that wallet on your own installation. Keep recovery material out of tickets, recordings and shared documents.
3. Check the resulting address and chosen protection mode.
4. Complete your own backup procedure before relying on the wallet. Do not treat a saved module configuration as a wallet backup.

Set safeguards before automation

1. Open Treasury → Spending safeguards → Set safeguards for that wallet.
2. Set the per-transaction and daily limits you intend, checking the asset/unit for native coins and tokens separately.
3. Configure the approved destination addresses and read the security delay before a new address becomes usable.
4. Enable two-person approval if your process requires a second administrator and review Awaiting a second approval for pending sends.
5. Read the effective and pending settings. Stricter settings apply immediately; relaxations are subject to the configured security delay.

These controls apply to sends made through the module. They do not constrain a key exported and used elsewhere. Administrators’ export access and the wallet’s protection mode therefore still matter.

Configure and monitor a sweep

In the wallet’s advanced settings, set the intended auto-sweep destination and threshold. Confirm the network and ownership of the destination and that it is eligible under your safeguards before enabling it. A sweep can move an existing eligible balance; it is not only a response to a new invoice.

Automatic sweeps require Automatic protection and sufficient native network funds for transaction costs. Check Treasury → Recent activity, approval state and any refusal message rather than weakening a limit to force a send.

Reconcile any uncertain send with its recorded transaction before repeating it. Keep this distinct from an exchange conversion rule, which operates on a connected exchange balance.

See the PD Crypto Pay guide for WHMCS for related tasks, or explore the module.