Keys use browser cryptographic randomness with 100 bits per key. Generation does not activate, validate, or revoke a software license. Save the pool before leaving this page.
Generated keys need a real validation system
Choose a format and generate a batch for your own product. Inspect the output before saving it, retain a private copy and check it against any keys already issued by your licensing system. Random text alone is not proof of a purchase and does not activate software. Your application or license server must decide which keys are valid and what access each one grants.
Do not publish the generated batch in a public repository, screenshot or support conversation. Import only unused keys that you are authorized to sell, and choose the correct product in the seller dashboard. Keep development and production batches separate. Product inventory should reflect keys that can actually be delivered; a key reserved for a pending checkout should not be assigned manually to another buyer.
Cartcord's supported key workflow allocates an available key to a paid order and exposes eligible purchases to the authenticated buyer. Software license verification and activation limits require the corresponding configuration. A refund can revoke access without making an already disclosed key safe to sell again. Test generation, import, delivery and verification separately before advertising automatic activation or compatibility with a particular application.