Payment troubleshooting guide

How crypto payment confirmations affect VPS activation

A crypto VPS invoice is normally fulfilled only after the payment is detected on the correct network and reaches the confirmation threshold shown by the active invoice or processor. Broadcasting a transaction or seeing “sent” in a wallet is not the same as final settlement, and required confirmations can vary by asset, network, amount, and current risk controls.

Key facts

Source of truth
The active invoice and its selected network
Pending means
Detected or expected, but not yet settled for fulfillment
Safe support data
Invoice ID and public transaction ID
Never disclose
Seed phrase, private key, password, or recovery code

Check five fields before authorizing

Verify the asset, blockchain network, destination address, exact amount, and invoice expiry. The ticker alone is not sufficient because an asset may exist on multiple networks. Compare the first and last characters of the address on a trusted wallet screen to reduce clipboard-replacement risk, and include any memo or destination tag exactly when the invoice requires one.

Generate a new invoice for a new payment. Do not reuse an address from history, email, chat, or a previous order. Send early enough for the wallet or exchange to broadcast before expiry, while understanding that the quote and processor rules decide how a late transaction is handled.

  • Confirm you are signed in on the authentic VPSEverywhere.com domain.
  • Choose an appropriate network fee rather than the minimum blindly.
  • Save the invoice ID before leaving checkout.

Diagnose a pending payment

Open an appropriate block explorer independently and search for the public transaction ID. Confirm it exists on the network named by the invoice, sends to the displayed destination, carries the expected amount, and is gaining confirmations. An exchange withdrawal ID is not always the blockchain transaction ID; obtain the on-chain identifier from the exchange when necessary.

A transaction can remain unconfirmed because it has not propagated, the fee is low relative to current demand, or the sending service has not broadcast it. Do not send a duplicate payment unless the processor or qualified support explicitly instructs you. Wallet fee-bumping methods vary and can create a new transaction ID.

  • Wallet “complete” labels can describe the wallet's workflow, not merchant settlement.
  • Block time is variable and is not an activation guarantee.
  • Chain reorganizations are one reason processors wait for depth.

Handle amount, network, and expiry mismatches

Underpayments can happen when a wallet subtracts its fee from the amount. Overpayments, multiple transfers, and payments after expiry may not match automatically. A payment on the wrong network is more serious: the destination may not be controlled in a recoverable way on that network, even if the visible address format looks similar.

Contact support through the authenticated channel with the invoice ID, transaction ID, asset, network, amount, and approximate time. Do not publish these details or send secrets. Recovery, credit, or refund may be impossible and can depend on processor capability, service terms, applicable law, and network fees.

  • Do not ask anyone to import a private key for recovery.
  • Do not alter screenshots to hide a payment mismatch.
  • Keep lawful transaction records for accounting and disputes.

Separate payment settlement from provisioning

A settled invoice can still require automated or manual service checks, inventory allocation, fraud screening, or account review. No-routine-KYC means no standard identity-document step, but legal, payment, fraud, sanctions, account-security, or serious-abuse controls remain possible.

If the payment is confirmed but the order is not active, use the invoice status and official support channel. Never grant wallet or server access to a person who contacts you unsolicited and claims they can accelerate confirmations.

Sources

  1. OxaPay — Payment Status Table
  2. OxaPay — Supported Currencies and Networks
Frequently asked questions

Frequently asked questions

How many confirmations are required?

Use the number shown by the live invoice or processor. It can vary and this guide intentionally does not publish a permanent threshold.

Can support speed up a blockchain confirmation?

Support generally cannot control block production. They can confirm invoice detection or advise on processor-specific handling, but you must never share wallet secrets.

What if I paid after the invoice expired?

Do not pay again immediately. Send the invoice and transaction IDs through the authenticated support channel so the payment can be assessed under current terms.