Skip to content
Sign Up For Free
BatchKeys License Key SaaS
  • Pricing
  • Try Demo
  • Docs
  • SupportExpand
    • Tickets
  • AboutExpand
    • Contact
  • Dashboard
BatchKeys License Key SaaS

Getting Started

11
  • Setting Up An Account
  • Your Dashboard
  • Generating Keys
  • Viewing And Editing Keys
  • Viewing/Editing An Individual Key’s Details
  • Bulk Deleting Keys
  • Importing Keys
  • Encoding And Decoding PHP
  • Handling Refunds
  • Unbanning A Valid End User
  • Requesting An Enterprise or Custom Plan

Integrations

14
  • Inserting Code Into Your App
  • Making API Calls
  • Receiving A Response
  • Example JSON Response
  • Assigning Keys To A Domain Name
  • Generating Unique UUIDs
  • Assigning Keys To A UUID
  • Checking Keys Daily Using A Cron Job
  • Checking Keys At Startup
  • Consuming And Topping Up Tokens For Token-Based Keys
  • Server-Side Proxy For Client-Side JavaScript Connections
  • Forms To Collect A Key
  • Adding BatchKeys To A WordPress Plugin
  • Adding BatchKeys To A WordPress Theme

Best Practices

13
  • Using Domain/UUID Settings To Upsell Your App
  • Staying Within Rate Limits
  • Handling Errors
  • Dealing With Connection Failures And Rechecks
  • Securing Keys
  • Working Around Hardware Changes With V5 UUIDs
  • Working Around V4 UUID Security Concerns
  • Creating Good Validation Forms
  • How We Use UUIDs To Secure Keys
  • A Note About Example Codes
  • Can We Create Custom Code For You?
  • Maximum Key Limits Per Plan
  • Using A License Key Service In A Mobile App
  • Home
  • Docs
  • Best Practices
  • Creating Good Validation Forms

Creating Good Validation Forms

A license key form is the easiest way to initially collect the key from your end user. These forms should be intuitive and easy to use for an ideal end user experience.

Form Best Practices #

For technical details on creating forms, see our documentation on form building in various languages. There are also several code examples you can build off of.

No matter what language your form is built in, a simple input where the key will go and a submit button is all you need. Anything beyond this simple design is up to you.

You could collect information at the same time the key is checked and store that information in a local file or database. An example might include asking a user for their birthday or full name.

However, KISS really applies here. Users don’t want to fill out tedious forms, so ask as little as you need or prefill the form fields with available information you already have, like their billing email or username.

Think Of The User Experience #

End users are accustomed to adding license keys to newly bought software and as long as you design a nice form they likely won’t have any issues. Adding keys to a simple and clean form is ubiquitous to modern digital purchases.

Keep your forms simple and avoid creating forms with a wall of inputs with multiple questions and options to choose from….especially if they already answers most of these questions during checkout.

Keeping your license key forms simple and clean improves customer satisfaction. If you must collect more information prefill as much as you can, or consider only collecting the data you must have at installation and ask for more info later after the user has spent some time inside your app.

This makes the end user feel like the installation process is smooth and efficient.

Was this Helpful?
Still stuck? How can we help?

How can we help?

Updated on April 4, 2024
Working Around V4 UUID Security ConcernsHow We Use UUIDs To Secure Keys

Powered by BetterDocs

Table of Contents
  • Form Best Practices
  • Think Of The User Experience
  • Get Early Access
  • Try Demo
  • Status
  • API Tester
  • Docs
  • Support
  • Feature Request
  • Feedback
  • About
  • Contact
  • Sitemap
  • Coupons

TOS

Privacy Policy

SLA

© 2025 Batch Keys | Created and maintained by Kayce Media Group

  • Pricing
  • Try Demo
  • Docs
  • Support
    • Tickets
  • About
    • Contact
  • Dashboard