1. Introduction to MikroTik Voucher Systems
If you sell internet access by the hour, the day, or by a data allowance, you already know the hard part is not the router. It is the paperwork around it. Who got which login? Which logins have been used? Which ones are still sitting in a drawer? A MikroTik voucher system answers those questions by turning access into something you can create in bulk, print, hand over, and track.
At its core, a mikrotik voucher system is a way to sell time limited internet access through a hotspot. Each voucher is a login that carries rules: how long it works, how much data it allows, and when it stops being valid. The guest connects, sees a login page, enters the voucher, and gets online until the rules run out. You never have to create an account by hand while a customer waits at the counter.
Small hotspot operators like this model because it keeps selling simple. You create a batch of logins ahead of time, activate the right profile for each one, print them, and distribute them. Then you watch how they get used and clean up when they expire. Those are the moving parts this guide covers: creating, activating, printing, and managing batches of voucher logins. If you would rather handle those tasks from a dedicated voucher management platform, the underlying ideas are the same ones explained below.
By the end, you will understand how a mikrotik hotspot voucher moves from creation to login to expiry, so you can run a reliable setup with fewer surprises.
2. Role of User Manager in Voucher Handling
The MikroTik User Manager is the part of the system that keeps track of your voucher users and the rules attached to them. Think of it as the record keeper and the rule enforcer. The hotspot is the front door guests walk through, and the mikrotik user manager is the desk that checks whether their voucher is allowed in and for how long.
For voucher handling, User Manager does a few jobs. It stores the users you create, links each one to a profile, remembers usage, and tells the hotspot whether a login is acceptable. This is the same foundation behind broader MikroTik hotspot user management, and it is what makes batch voucher sales practical. In this section we stay on concepts and workflow, not setup steps.
2.1 Built In RADIUS Function for Hotspot and PPP
User Manager includes a built in RADIUS function. RADIUS is a standard way for a network device to ask a central place, “Is this person allowed on, and under what rules?” The device that handles the connection asks the question, and the RADIUS server answers.
Because this function is built in, you do not need a separate server to hold your voucher users. It supports the Hotspot service, which is what most voucher operators use, and it also covers PPP authentication concepts. In plain terms, the same record keeping approach can answer login questions for hotspot guests and for PPP style connections. For voucher sales, the Hotspot side is the one that matters most, and the idea behind mikrotik RADIUS hotspot authentication is simply that the router asks and User Manager replies.
2.2 How User Manager Connects to Hotspot Service
The Hotspot service is the part of the router that catches new guests and asks them to log in. For vouchers to work, that service needs to hand the guest’s credentials to User Manager and wait for an answer.
In general terms, the Hotspot service is pointed at the RADIUS function, so login checks go to User Manager instead of being decided locally. That link is what lets one central list of voucher users control access. When a guest enters a voucher, the Hotspot service passes it along, User Manager checks it against its records and profile rules, and the answer comes back as approve or reject.
2.3 Where Vouchers Sit in the Authentication Flow
Vouchers sit in the middle of the authentication flow. The guest connects to the network first. The Hotspot service intercepts that connection and presents a login. The guest enters the voucher credentials, and the Hotspot service sends them to User Manager.
User Manager then checks several things: does this user exist, is the voucher still valid, and do the profile limits allow a new session? If everything checks out, the session is approved and the guest gets access. If not, the guest sees a rejection and stays blocked. Understanding this order helps when you troubleshoot. A failed login can come from the guest typing the wrong code, from the voucher being past its validity, or from limits already used up.
3. User Profiles and Access Control Behind Vouchers
If User Manager is the desk, mikrotik user profiles are the rulebook. A profile describes what a voucher user is allowed to do. For voucher selling, that means three main ideas: time limits, data limits, and validity.
Profiles keep your offers consistent. Instead of deciding the rules voucher by voucher, you define an offer once and apply it to every user that should follow it. That saves effort and prevents mistakes, because every voucher sold under the same offer behaves the same way.
3.1 Creating Profiles for Time and Data Limits
When people ask how to set time and data limits for mikrotik vouchers, the answer starts with the profile. A profile is where you describe the allowance for an offer. A time limit controls how long a guest can stay online. A data limit controls how much traffic the guest can use. You can think about an offer built around time, an offer built around data, or a mix of both, depending on what you sell.
Here is a simple way to plan it. Imagine you run a small cafe and want a light daily offer for casual visitors, and a bigger offer for people who work there for long stretches. Those are two different profiles. Decide the allowance, give each profile a clear name you will recognize later, and keep the list short enough that your staff can tell them apart at a glance.
3.2 Assigning Profiles to Voucher Users
A profile does nothing until it is attached to users. Assigning a profile to a voucher user is what makes the limits apply. When you create voucher users, you choose which profile they belong to, and from that point their sessions follow that profile’s rules.
Pay attention here, because this is where many operators slip. If a batch is created against the wrong profile, every voucher in that batch carries the wrong allowance. Check the profile choice before you print, not after customers have the vouchers. This is the heart of how to create voucher users in mikrotik user manager in a way that behaves correctly: the user, the profile, and the intended offer must match.
3.3 Profile Activation and Validity Rules
Activation and validity decide when a voucher’s clock starts and how long the voucher stays usable. A voucher can be created today and sold weeks later, so you need to know whether its allowance begins at creation or when the guest first uses it. Operators who sell from stock generally want the clock to start when the voucher is actually used, so unsold vouchers do not quietly age in the drawer.
Validity rules also set the outer boundary. Even if a guest has time or data left, the voucher can stop working once its validity ends. These validity rules matter for reliable operation because they keep your inventory predictable. When you understand when a voucher becomes active and when it stops being valid, you can promise customers the right thing and avoid disputes about “lost” time.
4. Batch Creation of Voucher Users
Selling one login at a time does not scale. Batch creation lets you produce many voucher users in one go, so you can prepare stock before the busy period instead of during it. This is the idea behind mikrotik batch voucher creation: you decide what the batch should look like, create it, check it, and then distribute it.
Operators usually think about a batch as one product run. Which offer is it for? How many do I expect to sell? How will I recognize these vouchers later? Answering those questions before you create anything keeps your records tidy.
4.1 Setting Batch Size and Naming Pattern
Batch size is about matching stock to demand. Create enough to cover your expected sales without leaving huge piles that are hard to track. If you are unsure, it is easier to create another batch later than to manage a surplus of unused vouchers.
The naming pattern is just as important, even though it looks minor. A consistent pattern makes a batch easy to find, sort, and report on. If your batches are named in a way that reflects the offer or the period they were made for, you can later tell at a glance which vouchers belong together. This is the practical side of how to create batch vouchers in mikrotik: think of the batch as a labeled package, not a random pile of logins.
4.2 Assigning Shared Credentials Across a Batch
Sometimes a batch uses shared credentials, meaning the users in the batch share a common element so they are easier to hand out or recognize. This pattern fits situations where you want simplicity and are comfortable with a looser setup, such as a controlled event or a group where everyone is treated the same way.
The tradeoff is traceability. When credentials are shared, it is harder to tell individual users apart, so you give up some precision in tracking. Use shared credentials when ease of distribution matters more than per-person detail, and use unique credentials when you need to follow each voucher individually.
4.3 Reviewing Created Users Before Distribution
Always review a batch before it leaves your hands. A short check now saves a lot of frustration later. At a general level, confirm that the users were created, that they carry the correct profile, that the naming pattern looks right, and that the credentials are readable and complete.
Treat this like checking a delivery before signing for it. If something is wrong, fixing it in the system costs you a few minutes. Fixing it after printed vouchers are in guests’ hands costs you trust.
5. Voucher Code Formats and Login Credentials
A voucher is only useful if guests can read it and type it correctly. This section covers the credential ideas behind printed vouchers, in plain language and without inventing formats.
5.1 Username and Password Pairs
The pair based approach is the most familiar. Each voucher has a username and a password, and the guest enters both on the login page. This is the mikrotik voucher username and password login style. Because the two parts work together, it feels like a normal account login, and it adds a small barrier against someone guessing a valid code.
The cost is a bit more typing for the guest. On a phone, entering two fields takes slightly more effort, so clear printing matters.
5.2 Single Code Login Options
A single code voucher is the simplified alternative. Instead of a pair, the voucher has one code, and the guest enters just that. This is the mikrotik single code voucher login concept. It is quick for guests and easy to explain at the counter: “Type this code and you are in.”
Single code logins suit busy, casual sales where speed matters. The tradeoff is that there is only one thing to protect, so it is worth thinking about how the code is generated and how carefully vouchers are handled before sale.
5.3 Password Handling and Readability Choices
Whatever style you choose, readability decides how many support questions you get. Printed vouchers get read in poor light, on small screens, and by people in a hurry. Choose credentials that are easy to read and easy to copy. Think about characters that look alike and could be mistaken for each other, and prefer a format your guests can type without second guessing.
On the handling side, treat unsold vouchers like cash. Keep printed stock secure, hand them out deliberately, and avoid sharing credentials in ways that make them easy to copy. A readable voucher that is handled carefully is the combination that keeps a voucher system trustworthy.
6. Exporting Vouchers for Printing
Once a batch is created and reviewed, you need to get it onto paper or into a form you can distribute. Export for printing is the step that turns database records into something a person can hold. Conceptually, you pick what you want to print, produce an output, and prepare it for handing out.
If you are wondering how to export mikrotik vouchers for printing, think of it as three moves: choose the batch, choose the output, and prepare the result. The next sections walk through each one.
6.1 Selecting User Batches for Export
Start by selecting the right batch. This is where your naming pattern pays off. If batches are labeled clearly, you can find the one you want without scanning through unrelated users.
Be deliberate about what you select. Exporting the wrong batch, or a mix of batches with different profiles, leads to vouchers that do not match what you plan to sell. Keep each print run tied to one clear offer so the printed stock stays organized.
6.2 Export File Formats and Layout Options
Exports come in different file formats and layout options, and the right choice depends on how you will use the result. Some formats suit quick printing, while others suit editing or archiving. Layout options affect how many vouchers fit on a page, how large the text is, and how easy each voucher is to cut out.
Keep the guest in mind when you choose. A layout that is clean and uncluttered, with text large enough to read, will beat a cramped layout that squeezes in more vouchers. Test with a small print first so you can check readability before committing to a full run.
6.3 Preparing Printed Vouchers for Distribution
After printing, organize the vouchers before they reach customers. Sort them by offer so staff do not mix them up. Cut and stack them neatly, and keep a simple record of which batch each stack came from. If you hand vouchers to resellers or staff, note who received what and when.
This is the physical side of inventory control. A tidy stack with a label is much easier to account for than loose papers, and it makes the later job of tracking used and unused vouchers far simpler.
7. Hotspot Login Flow Using a Voucher
Now let us follow a guest from the moment they connect to the moment they are browsing. This is the end to end workflow, and it ties together everything above: the profile, the batch, the printed voucher, and the authentication check. It also mirrors the general RouterOS hotspot authentication flow that sits underneath voucher logins.
Understanding this flow helps you support guests. When someone says “it will not let me in,” you can place the problem at the right stage instead of guessing.
7.1 Captive Portal Presentation on Connection
The guest joins your wireless network and tries to open a page. Instead of reaching the internet, they are redirected to a captive portal, the login page served by the Hotspot service. This is how the router tells the guest that access requires a voucher.
If a guest connects but never sees the portal, the issue is usually on the device side, such as the page not being redirected properly. Reminding guests to open a page after connecting is often enough to bring the portal up.
7.2 Entering Voucher Credentials
On the portal, the guest enters the credentials printed on the voucher. For a pair based voucher, that means the username and the password. For a single code voucher, it means the one code. This is the mikrotik hotspot login step from the guest’s point of view.
Most failed logins at this stage are simple typing mistakes, such as look-alike characters or a stray space. This is exactly why readable printing and clear instructions matter. A short note on the voucher telling guests where to type each part can prevent many repeat questions.
7.3 Authentication and Session Start
When the guest submits the credentials, the Hotspot service passes them to User Manager. This is mikrotik voucher authentication in action. User Manager checks that the voucher exists, that it is still valid, and that the profile limits allow a session. If the checks pass, the answer comes back as approved.
An approved login starts a session. From that moment, the guest has access, and the profile’s time and data limits are tracked against that session. If the checks fail, the guest stays at the portal and sees that the login was not accepted. Knowing this sequence of connect, portal, credentials, check, and session gives you a clear map for diagnosing problems.
8. Monitoring Active Voucher Sessions
Selling vouchers is only half the job. You also need to see what is happening on your network. Monitoring tells you who is online, how much of their allowance remains, and how your stock is being used. If you want to go deeper on the topic, a guide on how to monitor active hotspot users covers the broader picture, while this section stays on the voucher side.
Regular monitoring turns your voucher system from a black box into something you can trust. It also helps you spot odd patterns early, such as a voucher being used when it should not be.
8.1 Viewing Connected Users and Remaining Time
At a general level, monitoring starts with a view of active sessions: which voucher users are connected right now and how much time or allowance they have left. This is how to monitor active mikrotik voucher sessions without guessing.
Use this view during busy periods to check that sessions look normal. If a guest says their time ran out early, you can look at the session and see what actually happened, which makes it easier to resolve the conversation fairly.
8.2 Disconnecting or Extending Sessions
Sometimes you need to step in. Disconnecting a session ends a guest’s access on the spot, which is useful if a voucher was misused or a session needs to be stopped. Extending a session gives a guest more time or allowance, which can be a goodwill gesture or a fix for a genuine problem.
These are operational controls, so use them with care and keep notes. If you extend a session as a favor, you want to remember that when you compare usage against sales later.
8.3 Tracking Used and Unused Vouchers
Inventory management depends on knowing which vouchers have been used and which have not. Used vouchers represent sales that have been redeemed. Unused vouchers represent stock still waiting to be sold or redeemed.
Check this regularly. If many vouchers from a batch remain unused, you may have printed too many, or distribution may be uneven. If vouchers are being used faster than expected, it is time to prepare another batch before you run out. This simple habit keeps you from running short during busy times.
9. Voucher Expiry Reuse and Removal
Every voucher has a life cycle: it is created, distributed, used, and eventually expires. Managing that life cycle well keeps your records clean and your guests clear on what they bought. For a broader look at the topic, this session expiry handling guide is a helpful companion, and the sections below stay focused on vouchers.
Think of expiry, reuse, and removal as the final stages of the same story. Planning for them from the start prevents clutter later.
9.1 What Happens When Validity Ends
People often ask what happens when a mikrotik voucher expires. The answer is simple: access ends. When the voucher’s validity runs out, or its allowance is used up, the session expires and the guest is no longer allowed online. If they try to log in again with the same voucher, the authentication check fails because the voucher is no longer valid.
This is by design. Session expiry is what makes time limited internet access meaningful. It is also worth telling guests clearly what they bought, so an expired voucher does not come as a surprise.
9.2 Reusing or Renewing Voucher Accounts
Reuse and renewal come down to a business decision. Some operators treat each voucher as a one time product and issue fresh vouchers for new sales. Others prefer to renew an existing voucher account so a returning guest can keep using familiar credentials.
Either approach can work. What matters is that you pick one on purpose and apply it consistently, so your records show clearly which accounts are fresh and which have been renewed. Mixing the two without a plan makes tracking harder.
9.3 Removing Expired Voucher Users
Over time, expired voucher users pile up. Removing them is cleanup, and it keeps your list focused on vouchers that still matter. This is how to remove expired mikrotik voucher users in general terms: identify the ones that are no longer valid, confirm you do not need their records, and remove them.
Before you delete anything, make sure you have the usage information you need. Once records are gone, they are gone. A regular, deliberate cleanup keeps the system easy to read and your monitoring views uncluttered.
10. FAQ
10.1 How does a voucher user differ from a regular hotspot user?
A voucher user is typically created in a batch and tied to a profile that sets time limited access, such as a time allowance, a data allowance, and a validity period. A regular hotspot user is usually a single account made for an ongoing relationship. Vouchers are built for selling access in bulk, while regular users suit long term or individual access.
10.2 Where are voucher profiles configured?
Voucher profiles live in User Manager, as user profiles. That is where you define the time limits, data limits, and validity rules, and then assign the profile to your voucher users so the limits apply.
10.3 How are many vouchers created at once?
Through batch creation. You decide the batch size and naming pattern, choose the profile, create the users together, and then review them before distribution. This is how mikrotik batch voucher creation saves time compared with making users one by one.
10.4 How are vouchers prepared for printing?
You select the right user batch, choose an export format and layout that is easy to read, and then print. After printing, sort and label the stacks so they are organized for distribution. This is the export for printing workflow in short.
10.5 How does a guest log in with a voucher?
The guest connects to the network and is shown the captive portal. They enter the voucher credentials, either a username and password pair or a single code. The Hotspot service passes them to User Manager, and if they check out, the session starts and the guest gets access.
10.6 What happens after a voucher expires?
When validity ends, the session expires and access stops. The voucher can no longer authenticate. After that, you can renew it if that fits your approach, or remove the expired voucher user as part of regular cleanup.