Product Documentation Menu

Hostwinds Product Documentation

Tools and instructions enabling you to maximize the potential of your Hostwinds product and service experience.

Search results for:


Table of Contents


Important: Before Sending a Cryptocurrency Payment
Example of an Exact Stripe Crypto Payment
Supported Cryptocurrency Payments
Wallet Options Are Not Accepted Currencies
Do Not Send Unsupported Assets
Paying From an Exchange
Exact Amount Requirement
Checkout Session and Expiration
What Happens If the Timer Expires?
Connected Wallet Payments
Direct Deposit via QR Code or Address
Processing Time
If Your Crypto Payment Does Not Apply
What to Expect During a Payment Review
Failed, Expired, or Incomplete Cryptocurrency Payments
Unsupported or Incorrect Cryptocurrency Transfers
What Hostwinds Can and Cannot Do
Refunds and Account Credits
Avoiding Duplicate Payments
Best Practices
Related Articles
Important: Before Sending a Cryptocurrency Payment
Example of an Exact Stripe Crypto Payment
Supported Cryptocurrency Payments
Wallet Options Are Not Accepted Currencies
Do Not Send Unsupported Assets
Paying From an Exchange
Exact Amount Requirement
Checkout Session and Expiration
What Happens If the Timer Expires?
Connected Wallet Payments
Direct Deposit via QR Code or Address
Processing Time
If Your Crypto Payment Does Not Apply
What to Expect During a Payment Review
Failed, Expired, or Incomplete Cryptocurrency Payments
Unsupported or Incorrect Cryptocurrency Transfers
What Hostwinds Can and Cannot Do
Refunds and Account Credits
Avoiding Duplicate Payments
Best Practices
Related Articles

Managing Cryptocurrency Payments

Hostwinds accepts cryptocurrency payments through Stripe Crypto for eligible invoices. Stripe Crypto allows customers to complete payments using supported stablecoins and blockchain networks displayed during Stripe checkout.

Cryptocurrency payments must be initiated manually from an unpaid invoice in your Hostwinds Client Area. Cryptocurrency payments are not available for automatic recurring billing.

Important: Before Sending a Cryptocurrency Payment

Please read this section carefully before sending any cryptocurrency payment.

Cryptocurrency payments must be sent exactly as instructed by Stripe during checkout. This includes the exact token, network, amount, destination address, and checkout time window shown by Stripe.

Payment completion is determined by Stripe, not Hostwinds. A cryptocurrency transaction is considered paid only when Stripe confirms that the payment was completed, accepted, matched, and settled for the correct Stripe payment attempt.

A cryptocurrency transaction showing as successful on a public blockchain explorer does not automatically mean the payment was accepted, matched, recovered, or settled by Stripe to Hostwinds.

If Stripe does not receive payment in accordance with its exact requirements, the customer risks payment failure, delayed service activation, non-payment of invoices, and possible loss of funds.

Hostwinds can only mark an invoice paid, issue account credit, or review any payment adjustment when Stripe confirms that the payment was successfully completed, settled, recovered, or otherwise associated with the correct Stripe payment attempt.

If Stripe cannot confirm receipt, recovery, reconciliation, or settlement of the transaction, Hostwinds cannot manually apply the payment, issue account credit, or issue a refund for the transaction.

Unsupported tokens, unsupported networks, incorrect token contracts, expired checkout sessions, reused payment addresses, incorrect payment amounts, or manual transfers outside the active Stripe checkout flow may result in funds being unrecoverable.

To avoid payment loss, always confirm the following before sending:

  • The token matches exactly what Stripe shows.
  • The network matches exactly what Stripe shows.
  • The amount matches exactly what Stripe shows.
  • The address or QR code is from the current Stripe checkout session.
  • The payment is completed before the Stripe checkout session expires.
  • You are not reusing an old address or QR code.
  • You are not sending one payment for multiple invoices.
  • You are not sending cryptocurrency manually outside the Stripe checkout flow.

If you are unsure whether your token, network, wallet, or exchange withdrawal method is supported, do not send the payment. Use another payment method or contact Hostwinds Support before proceeding.

Example of an Exact Stripe Crypto Payment

The following example is for illustration only. Customers must always follow the exact payment details shown during their own Stripe checkout session.

Example invoice:

Stripe Checkout Field

Example Value

Invoice amount

$9.99 USD

Token required by Stripe

USDC

Network required by Stripe

Polygon

Amount to send

9.99 USDC

Destination address

Address shown by Stripe during checkout

Payment window

Before the Stripe checkout timer expires

In this example, the customer must send exactly 9.99 USDC on the Polygon network to the destination address shown by Stripe before the checkout timer expires.

The following would be incorrect and may cause the payment to fail or become unrecoverable:

  • Sending 9.98 USDC.
  • Sending 10.00 USDC.
  • Sending 9.99 USDT instead of USDC.
  • Sending ETH instead of USDC.
  • Sending USDC on Ethereum when Stripe showed Polygon.
  • Sending USDC on Binance Smart Chain, Arbitrum, Optimism, or another unsupported network.
  • Sending payment after the Stripe checkout timer expires.
  • Sending payment to an old address from a previous checkout attempt.
  • Sending one payment intended to cover multiple separate invoices.
  • Sending manually outside the active Stripe checkout flow.

The token, network, amount, address, and time window must all match Stripe's instructions. Matching only some of the details is not enough.

For example, sending USDC to the wrong network is not sufficient. Sending the correct network is not sufficient if the amount is wrong. A public blockchain confirmation is not sufficient if Stripe cannot match the transaction to the active payment attempt.

Your Hostwinds invoice will be updated only after Stripe confirms the payment.

Supported Cryptocurrency Payments

Hostwinds cryptocurrency payments are processed through Stripe Crypto. Stripe Crypto supports only select stablecoin payments.

The exact token and network options available for your payment are shown during the Stripe checkout process. You must use only the token and network Stripe shows for that payment.

Supported stablecoin options may include:

Token

Supported Networks

USDC

Ethereum, Solana, Polygon, Base

USDP

Ethereum, Solana

USDG

Ethereum



Other cryptocurrencies, networks, or token contracts are not supported unless Stripe specifically displays them during checkout.

Examples of unsupported cryptocurrencies or payment types include, but are not limited to:

  • Bitcoin, BTC
  • Ethereum, ETH
  • Tether, USDT
  • USDT0
  • Tron, TRX
  • Litecoin, LTC
  • Dogecoin, DOGE
  • Bridged or wrapped token versions not shown by Stripe
  • Unsupported token contracts
  • Unsupported networks
  • Any asset not shown by Stripe during checkout

If you hold an unsupported cryptocurrency, you must convert it to one of the supported token and network options shown by Stripe before sending payment.

Wallet Options Are Not Accepted Currencies

During Stripe Crypto checkout, Stripe may display wallet options such as Coinbase Wallet, MetaMask, Phantom, Trust Wallet, OKX Wallet, Ledger, Crypto.com Pay, or Blockchain.com.

These are wallet providers or connection methods. They do not mean that every cryptocurrency supported by that wallet is accepted by Hostwinds.

For example, selecting a Blockchain.com wallet option does not mean Bitcoin is accepted. Selecting MetaMask does not mean native ETH or every ERC-20 token is accepted.

Only the token and network displayed by Stripe for your specific payment are valid.

Do Not Send Unsupported Assets

Sending an unsupported asset may result in permanent loss of funds.

Unsupported assets cannot be manually applied to your Hostwinds invoice, even if the transaction appears successful in a public blockchain explorer.

If Stripe cannot accept, match, recover, or settle the transaction, Hostwinds cannot mark the invoice as paid, issue account credit, or issue a refund.

Examples of unsupported transfers include:

  • Sending ETH when Stripe requested USDC.
  • Sending USDT when Stripe requested USDC.
  • Sending USDC on the wrong network.
  • Sending a bridged or wrapped version of USDC not shown by Stripe.
  • Sending funds after the checkout session expired.
  • Sending funds to an old or reused address.
  • Sending a manual transfer instead of completing the active Stripe checkout flow.

Paying From an Exchange

We strongly recommend using a private wallet that you control when paying with cryptocurrency.

Examples may include MetaMask, Phantom, Coinbase Wallet, Trust Wallet, or another supported self-custodied wallet compatible with the token and network shown by Stripe.

Payments sent directly from centralized exchanges, such as Binance, Kraken, Coinbase Exchange, Crypto.com, or similar platforms, may be more difficult to verify or recover if there is an issue with the payment.

If a supported transaction is rejected or returned, the funds may be routed back to the originating sending address. When using a centralized exchange, that address may belong to the exchange rather than to your personal account. Hostwinds cannot retrieve funds from an exchange's internal wallet system.

If you choose to send from an exchange, you are responsible for ensuring:

  • The exchange supports the exact token shown by Stripe.
  • The exchange supports the exact network Stripe shows.
  • The exchange sends the exact amount required by Stripe after any withdrawal fees.
  • The exchange completes the withdrawal before the Stripe checkout session expires.
  • You can work with the exchange if a return or recovery issue occurs.

Exact Amount Requirement

Stripe Crypto requires the exact payment amount shown during checkout.

Do not round up, round down, or alter the payment amount unless your wallet or exchange requires you to account for withdrawal fees to ensure the exact amount arrives.

The amount Stripe receives must match the amount required for the invoice payment. Sending too little or too much may prevent Stripe from automatically matching the payment to your invoice.

If your wallet or exchange charges withdrawal fees, make sure the final amount arriving at the Stripe-provided destination is the exact amount Stripe requires.

Before confirming payment, compare every detail shown by Stripe against your wallet or exchange withdrawal screen:

  • Token
  • Network
  • Amount
  • Destination address
  • Checkout expiration timer

Do not send the payment unless all details match exactly.

Checkout Session and Expiration

Stripe Crypto uses a time-limited checkout session.

To complete a payment:

  1. Open the unpaid invoice in your Hostwinds Client Invoice Area.
  2. Select the cryptocurrency or Stripe Crypto payment option.
  3. Continue to the Stripe-hosted checkout page.
  4. Review the token, network, amount, address, and expiration timer.
  5. Send the exact payment before the checkout session expires.
  6. Wait for Stripe to confirm the payment.
  7. Return to your Hostwinds invoice after payment completion.

If the checkout session expires before the payment is completed, the invoice will remain unpaid.

Do not send funds after the Stripe checkout session expires. Start a new payment attempt from the unpaid invoice instead.

What Happens If the Timer Expires?

If the Stripe checkout timer expires, the original payment attempt may no longer be valid.

Depending on the token, network, timing, and Stripe payment flow, a late supported payment may be rejected or returned by Stripe. However, return or recovery is not guaranteed in every situation.

If the payment was sent using an unsupported token, an unsupported network, an incorrect token contract, an old address, a reused QR code, or otherwise outside Stripe's instructions, the funds may be unrecoverable.

If your invoice remains unpaid after sending a cryptocurrency transaction, open a Billing ticket before attempting a duplicate payment.

Connected Wallet Payments

Stripe Crypto may allow you to connect a supported browser extension or mobile wallet.

When using a connected wallet:

  • Scan the connection QR code or approve the wallet connection.
  • Review the payment details inside your wallet.
  • Confirm that the token, network, and amount match Stripe's checkout page.
  • Approve the transaction only if all details are correct.
  • Wait for Stripe to process the payment.

Connecting a wallet does not complete payment by itself. You must still approve and submit the transaction through your wallet when prompted.

Direct Deposit via QR Code or Address

Stripe may provide a direct deposit address or QR code during checkout.

When using direct deposit:

  • Copy the address exactly.
  • Confirm the network exactly matches what Stripe shows.
  • Send only the token shown by Stripe.
  • Send the exact amount Stripe shows.
  • Complete the payment before the checkout session expires.
  • Do not reuse the address later.
  • Do not send multiple invoice payments to the same address unless Stripe specifically instructs you to do so.

A QR code may represent either a wallet connection request or a direct deposit address. Make sure you understand which option Stripe is displaying before sending funds.

Processing Time

Most valid cryptocurrency payments are applied automatically after Stripe confirms the transaction.

However, blockchain confirmation alone does not guarantee that your Hostwinds invoice has been paid. Your invoice is officially paid only after Stripe validates the payment and Hostwinds receives a successful payment confirmation.

Some payments may remain pending while Stripe processes the transaction. If your payment remains pending, Hostwinds may need to wait for Stripe to complete or fail the payment attempt.

If Your Crypto Payment Does Not Apply

If your blockchain explorer shows a successful transaction but your Hostwinds invoice remains unpaid, open a Billing ticket and provide the following:

  • Hostwinds invoice number
  • Transaction hash, TXID, or signature
  • Token sent
  • Network used
  • Exact amount sent
  • Destination address
  • Date and time sent
  • Wallet or exchange used
  • Screenshot of the Stripe checkout page, if available
  • Screenshot of the wallet or exchange confirmation
  • Any error message shown by Stripe, your wallet, or your exchange

Hostwinds will review the information provided and may escalate the transaction details to Stripe Support.

Providing blockchain proof does not guarantee that the payment can be applied, credited, refunded, recovered, or reconciled.

What to Expect During a Payment Review

If a cryptocurrency payment does not automatically apply to your invoice, Hostwinds may review the invoice, Stripe payment records, and the blockchain transaction details you provide.

In some cases, Hostwinds may escalate the transaction details to Stripe Support to determine whether:

  • The transaction can be associated with a Stripe payment attempt.
  • Stripe received or recognized the transfer.
  • The payment can be completed, recovered, returned, or reconciled.
  • The transaction was sent using an unsupported token or network.
  • The payment attempt expired before completion.
  • The amount, address, token, or network did not match Stripe's requirements.

Payment reviews are not instant and may take time. Hostwinds cannot guarantee that Stripe will be able to recover, reconcile, return, or confirm the payment.

Hostwinds may withhold service activation, renewal, credit, or refund review until Stripe confirms the payment was completed, settled, recovered, or otherwise associated with the correct payment attempt.

Failed, Expired, or Incomplete Cryptocurrency Payments

A Stripe Crypto payment may fail, expire, or remain incomplete if:

  • The checkout session expired before payment was completed.
  • The wallet connection was started, but the transaction was never approved.
  • The payment was sent using the wrong token.
  • The payment was sent using the wrong network.
  • The payment was sent using an unsupported token contract.
  • The payment amount did not match Stripe's required amount.
  • The payment was sent after the checkout session expired.
  • An old address or QR code was reused.
  • The payment was sent outside the active Stripe checkout flow.
  • One transaction was sent for multiple separate invoices.
  • The payment was sent from an exchange in a way that did not satisfy Stripe's payment requirements.

If Stripe marks the payment attempt as failed, expired, or incomplete, the invoice will remain unpaid unless Stripe later confirms that the transaction was received, matched, recovered, or settled.

Unsupported or Incorrect Cryptocurrency Transfers

Unsupported or incorrect cryptocurrency transfers may be unrecoverable.

This includes payments sent using:

  • Unsupported cryptocurrencies
  • Unsupported stablecoins
  • Unsupported networks
  • Incorrect token contracts
  • Expired checkout sessions
  • Reused deposit addresses
  • Incorrect payment amounts
  • Manual transfers outside Stripe checkout
  • Transfers to addresses not generated for the current payment attempt

If Stripe cannot recover, refund, reconcile, or confirm settlement of the transaction, Hostwinds cannot mark the invoice paid, issue account credit, or refund the transaction.

In these situations, a new payment must be submitted through a new Stripe checkout session using one of the supported tokens and network options shown during checkout.

What Hostwinds Can and Cannot Do

Hostwinds can:

  • Review your invoice and payment attempt.
  • Check whether Stripe reported a completed payment.
  • Review the transaction details you provided.
  • Escalate eligible payment issues to Stripe Support.
  • Update your invoice if Stripe confirms the payment was completed or settled.
  • Provide next steps if Stripe confirms a recovery or reconciliation path.

Hostwinds cannot:

  • Manually force Stripe to complete an expired payment attempt.
  • Manually match an on-chain transaction to a Stripe payment attempt without Stripe confirmation.
  • Refund cryptocurrency funds that were not received or settled to Hostwinds.
  • Apply account credit for a transaction Stripe cannot confirm.
  • Recover unsupported tokens or wrong-network transfers.
  • Retrieve funds sent from or returned to an exchange-controlled wallet.
  • Guarantee recovery of funds sent outside Stripe's instructions.

Refunds and Account Credits

Cryptocurrency payments are non-refundable.

Refund or account credit availability depends on whether Stripe successfully completed, settled, recovered, or otherwise confirmed receipt of the payment.

If Stripe confirms that a payment was successfully completed and a refund or credit is available under Hostwinds policies, Hostwinds may review the account for eligible options.

If Stripe does not confirm receipt, recovery, reconciliation, or settlement of the transaction, Hostwinds cannot issue a refund or apply account credit.

If an unsupported or incorrect transfer is unrecoverable, the invoice will remain unpaid, and a new payment must be submitted using a supported payment method.

Avoiding Duplicate Payments

If your cryptocurrency payment has not updated your invoice, do not immediately submit a duplicate payment unless instructed by Hostwinds Support.

Open a Billing ticket first so our team can review the payment status.

If Stripe confirms that the original payment failed, expired, or cannot be recovered, you may need to submit a new payment through a new Stripe checkout session.

Best Practices

To prevent payment issues:

  • Start every cryptocurrency payment from the unpaid Hostwinds invoice.
  • Use only the active Stripe checkout session.
  • Use only the token and network shown by Stripe.
  • Send the exact amount Stripe requires.
  • Complete payment before the checkout session expires.
  • Do not reuse addresses or QR codes.
  • Do not send unsupported tokens.
  • Do not send one payment for multiple invoices.
  • Avoid direct exchange withdrawals when possible.
  • Save your transaction hash and screenshots.
  • Contact Hostwinds Support before sending if anything looks unclear.

Related Articles