What a licence key is and is not

Most confusion about keys comes from treating one string as though it were the whole purchase. In fact three separate objects are in play: an order, an entitlement and a key. Nearly every my-key-does-not-work ticket is really a question about which of the three is missing, and separating them takes two minutes that save an evening of retyping.

Where the key comes from

Checkout creates an order, and the order stays pending until the payment is verified. Crypto and PayPal both sit in that state until the transfer confirms. Once the order is approved, the licence is issued to the email on the order and appears against that order on the tracking page. Cheats, spoofers and account credentials are issued at that moment. Custom DMA firmware is not, because that line is a build rather than a file, and the site's own copy says it is typically prepared inside 24 to 48 hours. A paid firmware order not yet showing as delivered is usually still inside that window.

Three objects, not one

• The order is the record of a purchase: an ID, a payment state, and a list of items
• The entitlement is the fact that this order owns this product — it lives on the order, not in your hands
• The key is a credential that opens the delivery for that entitlement on the Downloads page
• A delivery item is what the key actually opens: a file, or a route to support

That distinction is the diagnosis. If verification succeeds but the item list comes back empty, your entitlement is confirmed and nothing has been marked ready. That is an order-record problem, and no amount of retyping the key will change it. If verification fails outright, the key or the order is the problem instead. The two failures look similar on screen and have nothing in common underneath, so they need different messages to support.

What bound means here

A key is bound to the order it was issued against, and through that order to the product and the email on it. It is not bound to your machine and it is not a hardware licence. That matters because a second binding lives nearby and the two get conflated constantly. Custom firmware is bound to your card's DNA ID, a property of the FPGA that has nothing to do with your key. One is how a delivery is opened; the other is why an image will not configure somebody else's chip.

Read the state before you open the link

Each delivery item carries a published run state, drawn from the same seven values the status board uses: undetected, testing, at own risk, updating, maintenance, detected or no status. Anything other than undetected asks you to acknowledge it before the link opens, and that prompt is not a formality. Detected means do not launch and updating means wait. No status means nothing usable is published for that item, which is not the same as fine. Undetected on a download row means published as undetected on a date, the same limited claim it makes on the board and no larger.

Reinstalls, new machines and lost keys

Rebuilding Windows does not touch the entitlement. The order still owns the product, the key still opens the same view, and nothing about the purchase is consumed by an install. What a reinstall does invalidate is the machine-specific state around it. A memory map belongs to that Windows install, its RAM layout and its BIOS, so it has to be generated again, and a spoofer's guided sequence is worth re-reading rather than recalling. Firmware is unaffected either way, because it lives in flash on the card where Windows cannot reach it.

One last thing a key is not is a statement about safety. It opens a delivery, and whether the build behind it should be launched today is a separate question that the board answers. The Downloads page prints that answer next to the link precisely so the two never get confused.