Auto-convert rules can convert supported assets held in your connected exchange account into another supported asset or currency. They act on exchange balances in the background, so review their scope before enabling them.

Before you add a rule

Complete the exchange connection and check which account and trading market it uses. Review the balance already in that account: a rule is not limited to the proceeds of a single new invoice and may become eligible immediately if its threshold is already met.

Decide the asset to convert, the intended target currency or asset and the threshold that matches your own operating policy. Review the saved rule against the operating policy you intend to apply.

The threshold is a trigger, not an amount left behind. When the selected asset’s available exchange balance meets or exceeds it, the rule converts that whole available asset balance. It does not convert only the excess above the threshold or only the proceeds of one invoice.

Set the intended rule

1. Open PD Modules → PD Crypto Pay → Exchange & convert → Auto-convert rules.
2. Add a rule for the intended exchange connection.
3. Select the source asset, target asset/currency and trigger threshold supported by the form.
4. Check that the exchange offers the required market and the API key can place the necessary trade.
5. Review the full balance condition and saved settings before enabling the rule.
6. Monitor Recent conversions and alerts when the background job evaluates it.

A token symbol alone does not establish the market available in your exchange account. The module can work with supported inverse market orientation, but the actual pair still has to be available and allowed by the key.

Check the outcome

Distinguish a recorded attempt from a filled conversion. Read the exchange’s reason for a refusal and compare the resulting balances for a completed operation. Do not place a manual duplicate just because a browser action ended before you reviewed the result.

For a restricted-pair error, review the pair your rule actually uses against the exchange key’s allow-list. For an IP or permission error, check the billing server’s outbound address and the required trading access. Withdrawals are not needed for this conversion connection.

If automation is not running

Check the rule’s enabled state and threshold, the selected account balance, the normal background-job result and Recent conversions. If a prior attempt is uncertain, reconcile it with the exchange record before retrying. Pause the affected rule while investigating if it could otherwise act again.

Converting funds in an exchange and sweeping funds from a hot wallet are different operations. A sweep needs a supported sending wallet and destination; a conversion rule uses assets already held by the connected exchange account.

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