An exchange connection lets PD Crypto Pay read balances and perform supported conversions in your own exchange account. It is separate from the receiving-wallet address used on an invoice. PD Crypto Pay does not become the custodian of the exchange account; the exchange holds funds deposited there.

Create a limited connection

Use a dedicated exchange API key for this integration. It needs the read/balance and trading permissions required by the supported operations. Leave withdrawals disabled. For example, Kraken documents its separate API permissions, including balance queries, order placement and withdrawals.

If you apply IP restrictions, allow the billing server’s outbound address, not the portable connection or browser used to administer it. Binance’s API-key guidance explains why its trading permissions may depend on suitable IP restrictions. Keep restrictions that match the integration rather than broadly disabling them to make a test pass.

Save the exchange in the module

1. Open PD Modules → PD Crypto Pay → Exchange & convert → Connect an exchange.
2. Enter a recognisable connection name and select Kraken, Binance or Coinbase.
3. Enter the key and secret in the requested fields, preserving the format supplied by the exchange.
4. For a current Coinbase key, preserve its full key name and signing secret. Do not invent a passphrase when that key type has none.
5. Save, then choose Test and read the result.

A successful connection test establishes the tested access; it is not a completed conversion and does not prove that every intended trading pair or permission is available.

Configure receiving separately

If customers should pay into your exchange account, obtain a deposit address from that account for the exact network/asset supported by the exchange. Add it under Wallets as receiving information. A successful trading connection does not itself create or validate a receiving-wallet setup.

Confirm the address, network and any deposit requirements with your exchange before offering it. Do not use an address for a different network simply because the token ticker is the same.

Resolve a refused test or conversion

Read the reported reason and Recent conversions when relevant. Check the key format, required permissions, account and outbound-IP restriction. A pair-restriction error calls for reviewing the intended allowed market, not enabling withdrawals.

After the connection is understood, use the auto-convert guide to configure a deliberate rule. Do not enable a rule merely as a connection test: it can place a real trade when its balance condition is met.

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