Scan NFC Tag to Clock In
Home > Management Mode > Clock-In Records and Management > Clock-In Point Settings > Select Clock-In Point > Scan NFC Tag to Clock InFrom the Management Mode home page, select Clock-In Records and Management, then Clock-In Point Settings and the required clock-in point. Open Scan NFC Tag to Clock In to configure this method.
NFC (Near Field Communication) is designed for short-range confirmation. To clock in, a user (employee) must bring an NFC-enabled phone close to a registered NFC tag. The system then creates a record for the clock-in point associated with that tag.
The actual reading distance depends on the phone, tag, and antenna design and is usually only a few centimeters. NFC can confirm that a user has reached a specified clock-in point, but it does not measure geographic location and is not intended for wide-area positioning or tracking. Enable GPS recording separately if location coordinates are also required.
Feature Overview
- Short-range confirmation: The phone must be close to the specified tag, reducing the chance of selecting the wrong clock-in point.
- Low power use: Passive NFC tags need no battery, and the phone uses NFC only briefly while scanning.
- Fast operation: Users can scan a registered tag without waiting for GPS positioning.
How to Use
- Register an NFC tag: On the clock-in point's NFC settings page, the manager selects ＋ and scans the NFC tag with a phone.
- Clock in: After starting the clock-in process, the user (employee) brings an NFC-enabled phone close to the tag registered for that clock-in point.
- Create the record: The system records the time and corresponding clock-in point. If photo or GPS recording is enabled, the user (employee) must also complete those steps as instructed.
Advantages
- Simplified process: Scanning the specified tag confirms the clock-in point and reduces manual selection errors.
- Fast identification: The system identifies the corresponding clock-in point from the registered tag.
- Immediate records: Managers can review the record in the system after clock-in is completed.
- Easy deployment: Compatible passive NFC tags can be used without installing a dedicated powered reader.
Require a Photo
Home > Management Mode > Clock-In Records and Management > Clock-In Point Settings > Select Clock-In Point > Scan NFC Tag to Clock In > Require a PhotoFrom the Management Mode home page, select Clock-In Records and Management, then Clock-In Point Settings and the required clock-in point. Open Scan NFC Tag to Clock In to configure this method.
When this option is disabled, users (employees) may choose whether to upload a photo. When it is enabled, they must take a photo during clock-in as instructed—for example, a clock, a street number, or another image that a manager can review.
Before using this feature, the organization creator must subscribe to the Premium Storage plan so clock-in photos can be stored in the cloud.
Require GPS Location for Clock-In
Home > Management Mode > Clock-In Records and Management > Clock-In Point Settings > Select Clock-In Point > Scan NFC Tag to Clock In > Require GPS Location for Clock-InFrom the Management Mode home page, select Clock-In Records and Management, then Clock-In Point Settings and the required clock-in point. Open Scan NFC Tag to Clock In to configure this method.
By default, GPS location is not required. Users (employees) can choose whether to submit their GPS coordinates when clocking in. Enable Require GPS Location for Clock-In if every user (employee) must submit GPS coordinates.
Important:
- GPS locations can be spoofed: Requiring GPS coordinates cannot completely prevent users from falsifying a location with technical tools.
- Location data may be missing or inaccurate: Phone hardware, location permissions, indoor conditions, or signal interference can prevent coordinates from being uploaded or reduce their accuracy.
- Use another verification method when appropriate: Depending on your management needs, you can also require a photo and have managers review unusual records.
Add an NFC Tag
Home > Management Mode > Clock-In Records and Management > Clock-In Point Settings > Select Clock-In Point > Scan NFC Tag to Clock In > Add an NFC TagFrom the Management Mode home page, select Clock-In Records and Management, then Clock-In Point Settings and the required clock-in point. Open Scan NFC Tag to Clock In to configure this method.
Select ＋, then follow the on-screen instructions to scan an NFC tag and add it to the list. Each clock-in point can have up to 10 NFC tags.
Notes
Before setup, confirm that the Android phone and iPhone models you plan to use can both read the NFC tag. If necessary, install the NFC Tools app on Android and iPhone and test the tag on both platforms. Actual compatibility depends on the phone hardware, operating system version, and tag specification.
EasyCard and iPASS
Transit cards such as EasyCard and iPASS are not suitable for direct use as SwipePoint NFC tags. Their chips vary in phone compatibility. If a card uses MIFARE Classic, Apple's Core NFC does not support it, and some Android phones may read only limited information.
For Android and iPhone compatibility, use NFC Forum-compliant tags and test them on the phones that will be used before deployment.
NFC Tags
SwipePoint reads NFC tags at close range with a phone. In addition to choosing an NFC Forum-compliant tag, test its reading performance with the actual Android phone and iPhone models that will be used.
Common NFC Tag Types
The NFC Forum has defined Tag Types 1 through 5, but Type 1 was removed from its 2021 technical specification release. Types 2, 4, and 5 are common in phone-based applications, but support still depends on the phone, operating system, and app.
| Tag type | Common examples | Description |
|---|---|---|
| NFC Forum Type 1 | Topaz, Jewel | A legacy type removed from newer NFC Forum technical specifications; it is not recommended for new deployments. |
| NFC Forum Type 2 | NXP NTAG 21x, MIFARE Ultralight | Common and inexpensive; suitable for URLs, identifiers, small amounts of data, and general phone applications. |
| NFC Forum Type 3 | Sony FeliCa | Uses NFC-F technology and is common in Japanese transit cards and related services. |
| NFC Forum Type 4 | MIFARE DESFire, ST25TA | Uses ISO-DEP and is suited to applications that need more capacity or advanced security features. |
| NFC Forum Type 5 | NXP ICODE SLIX, ST25TV | Uses NFC-V/ISO 15693. It can provide a more forgiving read range than some other types, but a phone must still be close to the tag. |
Compatible NFC Tag Families
| Family | Type | Description |
|---|---|---|
| NXP NTAG 213/215/216 | Type 2 | Widely available and suitable for general phone applications; test these first. |
| MIFARE Ultralight | Type 2 | Commonly used for ticketing, access control, and simple identification. |
| STMicroelectronics ST25TA | Type 4 | Supports NDEF, with capacity and protection features that vary by model. |
| Sony FeliCa | Type 3 | Common in Japan; confirm phone and app support before use. |
| NXP ICODE SLIX/STMicroelectronics ST25TV | Type 5 | Supports NFC Forum Type 5; test reading performance on the actual phones before use. |
Recommended NFC Tags
SwipePoint clock-in normally does not require a large amount of stored data. Consider the widely available NTAG 21x family first, then choose a model based on availability and real-device test results.
| Model | User memory | Description |
|---|---|---|
| NTAG213 | 144 bytes | Suitable for short data and general applications. |
| NTAG215 | 504 bytes | Suitable when more data is required. |
| NTAG216 | 888 bytes | Provides the most user memory of these three models. |
Notes
| Item | Description |
|---|---|
| Phone compatibility | The NFC antenna position and reading distance vary by phone. Test the tag on the Android phones and iPhones that will be used before deployment. |
| Tag form factor | Stickers, cards, key fobs, and on-metal tags use different antenna designs. Use an on-metal tag when attaching it to a metal surface. |
| Write protection | If tag data must not be changed, choose an appropriate locking or protection method. Permanent locking usually cannot be reversed, so verify the data first. |
| Data capacity | A large capacity is usually unnecessary for a short identifier. Base the choice on SwipePoint's registration and reading method. |
Frequently Asked Questions
Q1: How do I configure NFC Tag clock-in?
A: From the Management Mode home page, select Clock-In Records and Management > Clock-In Point Settings > the required clock-in point, then open Scan NFC Tag to Clock In. Managers can add NFC tags and choose whether photos or GPS locations are required.
Q2: How is NFC clock-in different from GPS, Wi-Fi, or Bluetooth clock-in?
A: NFC requires the phone to be close to a registered tag, making it suitable for confirming arrival at a specified clock-in point. It does not provide geographic coordinates like GPS and is not intended for wide-area positioning. Enable GPS recording separately if location information is required.
Q3: What is the NFC reading distance?
A: The actual distance depends on the phone, tag, and antenna design and is usually only a few centimeters. Hold the phone's NFC antenna area close to the tag and adjust its position as prompted.
Q4: What are the basic setup and clock-in steps?
A: A manager first selects ＋ at the required clock-in point and scans the NFC tag to register it. During clock-in, the user (employee) scans that tag with an NFC-enabled phone. The system records the time and corresponding clock-in point and requests any enabled photo or GPS steps.
Q5: What does requiring a photo do, and which plan is needed?
A: When enabled, users (employees) must take a photo during clock-in as instructed so a manager can review it. The organization creator must subscribe to the Premium Storage plan before using this feature.
Q6: Can requiring a GPS clock-in location completely prevent location spoofing?
A: No. GPS coordinates can be affected by positioning errors, signals, devices, or location-spoofing tools and should be treated as supporting information. Depending on your management needs, also require a photo and have managers review unusual records.
Q7: How do I add an NFC Tag, and how many can I add?
A: On the Scan NFC Tag to Clock In settings page, select ＋ and follow the on-screen instructions to scan and add the tag. Each clock-in point can have up to 10 NFC tags.
Q8: Can I use EasyCard or iPASS as an NFC Tag?
A: This is not recommended. Transit-card chips vary in phone compatibility. If a card uses MIFARE Classic, Apple Core NFC does not support it, and Android reading capabilities vary by model. Use an NFC Forum-compliant tag and test it on the planned Android phones and iPhones before deployment.
Subscribers receive more responsive support. If you encounter an error or need help using SwipePoint, contact the SwipePoint team through our official LINE account. We will prioritize troubleshooting so your attendance management can continue without interruption. LINE ID:
@nka7729y| Contact the SwipePoint team
This manual strives for accuracy and completeness, but we do not assume any liability for errors, omissions, or updates. The content may be modified at any time without prior notice. We are not responsible for any damages arising from the use of this manual or downloading its contents, including but not limited to system failures, data loss, or infringement of rights. Users assume full responsibility and risk.