How can we help?

Paying with BTC, ETH or SOL

1. Choose a product and coin, read the linked legal documents, and complete the acknowledgements to create a quote.
2. Use native BTC on Bitcoin mainnet, ETH on Ethereum mainnet, or SOL on Solana mainnet. Lightning, testnet coins, stablecoins, wrapped tokens and other networks are not accepted.
3. Copy the receiving address and exact amount from your current quote. Check the full address again in your wallet before sending. Network fees must be paid separately so the recipient receives the quoted amount. Exchange withdrawal fees and delays may prevent an exact, on-time payment.
4. Save your private order reference. The payment must confirm before the displayed deadline; broadcasting alone is not confirmation. Never send against an expired quote.
5. Open the sent transaction in your wallet, copy its transaction ID or signature, return to the same order, and choose Verify payment.

Quotes include an adjustment of up to $0.10 to distinguish orders. Network fees are separate. This checkout uses real mainnet funds even during store testing; creating a quote does not send money.

Background: Bitcoin payment and confirmation FAQ.

Receiving address, transaction ID and order reference

There is no separate “verification address.” The receiving address is the destination you send funds to, shown in the quote. Your own wallet address is the sender address.

The transaction ID (also called a transaction hash, or a signature on Solana) identifies the payment after it is broadcast. Find it in your wallet’s activity or transaction details, sometimes under “View on explorer.” Copy the ID itself into LaunchFix, not the explorer URL, a wallet address or an exchange’s internal withdrawal reference.

The order reference identifies your LaunchFix purchase. Keep it private: it is used to recover access. It is different from the public transaction ID.

Verification checks the selected chain, destination, exact amount, timing and confirmation. A transaction cannot unlock two different orders. Never share a seed phrase or private key; LaunchFix does not request either.

You can inspect a Solana signature using the Solana Explorer.

Pending, expired or incorrect payments

If a payment is pending, check its status in your wallet and verify again after confirmation. Do not send a second payment merely because verification is delayed.

If it confirmed before the quote expired, you can still verify it afterward. If confirmation happened after the deadline, or the amount or network was incorrect, contact support with the order reference, coin, transaction ID and the error shown. Recovery is reviewed manually and is not guaranteed for transfers on unsupported networks.

If you have not paid and the quote expires, create a new quote. If a provider is temporarily unavailable, keep your order details and retry verification later. Never send a separate “verification fee.”

Download, unzip and recover your tools

After successful payment verification, select Download now. The link is single-use and expires after the period shown in checkout. If it expires or the download is interrupted, verify the same paid order with the same transaction ID to obtain a fresh link. Do not pay again.

Keep the ZIP in a private folder, extract it, and start with the relevant README. Downloads include source files, accepted legal documents, an order-specific license identifier and a file-integrity manifest. Keep the receipt and follow the product license; do not post the ZIP or download link publicly.

The order is remembered in the same browser tab when storage is available. Save your order reference separately. If you lose access, email support with the details you retained. Purchase recovery requires review.

Start with Site Trust Rescue

Investigate a website warning with a structured evidence trail. The kit combines a URL and security-header audit with a source-code scanner and a recovery runbook, so you can identify suspicious findings and prepare a clear incident report.

Use it when a site suddenly shows a browser warning or after a suspected compromise. Review scanner matches manually, fix confirmed issues, and follow the recovery checklist. These are focused diagnostics, not a full crawl, malware certification, or a guarantee that a warning will be removed.

Extract the ZIP, read the kit’s README, and run its included self-check or sample in a local test environment. Review configuration and results before applying changes to a live system. Preview sample outputs.

Start with Mail DNS Doctor

Understand how your domain is configured to send and receive mail. Audit published MX, SPF, DKIM and DMARC records, inspect MTA-STS and TLS reporting markers, and work through a staged email-authentication rollout.

Best for domain owners and developers troubleshooting authentication. Supply your domain and known DKIM selectors, then compare findings with your mail provider’s instructions. SPF lookup checks are preliminary; the tool does not verify DKIM signatures, recursively evaluate every SPF include, or guarantee inbox placement.

Extract the ZIP, read the kit’s README, and run its included self-check or sample in a local test environment. Review configuration and results before applying changes to a live system. Preview sample outputs.

Start with the Stripe Webhook Reliability Kit

Build a more dependable path from a Stripe event to an application action. This reference kit includes a raw-body Express handler, signature checks, a Postgres event ledger, retry processing, silence monitoring and a reconciliation starting point.

For developers integrating Stripe with an existing application. Connect your own fulfillment logic, configure secrets, and exercise duplicate, delayed and failed events in Stripe test mode. The kit requires integration; it does not automatically provision your customers or repair application state.

Extract the ZIP, read the kit’s README, and run its included self-check or sample in a local test environment. Review configuration and results before applying changes to a live system. Preview sample outputs.

Start with CSV Rescue

Turn inconsistent vendor and CRM exports into reviewable import files on your own computer. Map headers, clean whitespace and hidden characters, and identify duplicates using a business key you choose. Ambiguous values are separated for review instead of being guessed.

You receive a cleaned CSV, a review CSV and a JSON change report. Work on a copy, configure columns, run the included sample, and inspect the report before importing. Alternate delimiters and whitespace preservation are supported. Processing is in memory; this is deterministic cleanup, not fuzzy matching.

Extract the ZIP, read the kit’s README, and run its included self-check or sample in a local test environment. Review configuration and results before applying changes to a live system. Preview sample outputs.

Use the Builder Rescue Bundle

Keep all four LaunchFix kits together: website incident diagnostics, email DNS auditing, Stripe webhook reliability and local CSV cleanup. Each kit retains its own source code, instructions and examples in one download.

Choose the bundle if you maintain several parts of a small product or business workflow. Start with the README for the relevant kit and run its included self-check before adapting it. Python 3 is needed for the utilities; the Stripe reference also needs Node.js 22+, PostgreSQL and a Stripe account.

Extract the ZIP, read the kit’s README, and run its included self-check or sample in a local test environment. Review configuration and results before applying changes to a live system. Preview sample outputs.