Blockchain providers let PD Crypto Pay observe incoming payments. They serve a different purpose from price sources, which calculate how much crypto an invoice requires, and exchange connections, which can convert assets in your own exchange account.

Prepare the right provider connection

Choose a provider that supports the exact network you accept. Ethereum Mainnet and Ethereum Sepolia are different networks even when the provider account is the same. A key for one does not establish visibility on the other.

The module has built-in public endpoints. Your own provider connection can offer a separate request allowance and failover options; it does not remove the need for blockchain confirmations or guarantee a fixed detection time. When the chain has enabled provider entries of a supported type, the module tries that configured pool. It uses the built-in endpoint when there are no such entries; do not assume the public endpoint is automatically added after all configured connections fail.

Add and check a provider

1. Open PD Modules → PD Crypto Pay → Providers → Add a provider.
2. Select the provider and chain supported by the form.
3. Enter its endpoint or API key as requested, matching the intended network.
4. Save, then use Test and read the reported result.
5. If you need failover, add another supported provider for that chain and test it independently.
6. Review provider status alongside the payment timeline when checking detection.

Test checks the selected provider, rather than allowing another connection to make that test pass. Read what the result actually checked: for an Ethereum-compatible provider it reports the latest block; other supported network families use their own lookup. This is not proof that every historical query needed by an older payment will succeed or that an invoice can be credited.

Use the provider’s server-side access restrictions appropriately: requests originate from your billing server, not the customer’s browser. If you restrict by IP, use that server’s actual outbound address. Do not paste a provider key into support messages or screenshots.

Diagnose slow detection

Check Providers for a failing connection, an exhausted allowance or a network mismatch. A second configured connection needs to be healthy to help with failover. Do not change the customer’s wallet or invoice amount merely to repair provider access.

When a shared receiving address also sends funds out, historical account-state reads can matter for detecting native-coin payments on Ethereum-compatible networks. Review the module’s provider guidance if an older request says it could not be checked; verify that the configured service supports the history needed for that request.

If the payment is already Seen or Confirming, provider access and settlement are different questions. Check the configured confirmation requirement and current network state through the payment-timeline guide.

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