NFC & Smart Card Application Development
From a reader on the desk to a working business workflow.
A reader and a card do nothing on their own. Software reads the card, checks it against a database and carries out a business action, such as marking attendance, allowing entry or recording a payment. BSD Infotech helps you plan, develop or integrate that software around compatible NFC and smart card readers, cards, SDKs, databases, APIs and the systems you already use.
Need Only a Reader, or the Whole System?
Some customers need just a reader, some a reader and SDK, some help connecting the reader to existing software, and some a complete application. Tell us which, and what the card has to do.
How Readers, Cards, SDKs and Software Fit Together
Reader hardware
An NFC/contactless or contact smart card reader connected by USB or Bluetooth. See NFC and contactless readers.
Card or tag
The card technology decides what can be read, written or protected, for example MIFARE, DESFire or NFC tags.
Driver, PC/SC and SDK
The interface your software uses to talk to the reader. See the smart card and NFC reader SDK guide.
Application
The software that reads the card and decides what happens next.
Database and API
Where records are kept, and how other systems receive the data.
Business workflow
The result: attendance marked, entry allowed, payment recorded or a member identified.
What Can We Build?
Possible project areas. BSD solution page means BSD already has a page describing that solution; project-based development means the scope is defined and quoted for your project. These are not all finished products.
NFC Card Issuance
Possible workflows:
- Card registration
- Card-to-user assignment
- Card activation and deactivation
- Card replacement
- Card status management
- Bulk issuance workflows
Card issue, recharge and blocking already appear in BSD solutions such as canteen management and the parking application.
NFC Card Personalization
Possible workflows:
- Card identification
- Reading or writing supported card data
- Personalization and validation
- Card initialization, where the card type supports it
- Card lifecycle workflows
Which operations are possible depends on the card type: a MIFARE Classic card, a DESFire card and an NFC tag do not support the same commands. For printed (visual) personalization, see card printing.
NFC Attendance
Possible workflows:
- Card tap and person identification
- Timestamp recording
- Location association
- Attendance reporting
- Integration with existing attendance software
See BSD’s school attendance and crowd control solution.
NFC Access Control
Possible workflows:
- Card-based authorization
- Access permissions
- Entry records
- Integration with compatible access-control equipment
A desktop NFC reader on its own does not open a door or gate: automatic entry also needs a controller, door or gate hardware, and integration. See NFC access control and access control solutions.
NFC Cashless and Stored-Value Workflows
Possible workflows:
- Card identification
- Transaction initiation
- Balance-related workflows and recharge
- Transaction recording
- POS integration
A card or reader is not a secure wallet by itself: the transaction system, card technology, security design and any applicable payment requirements decide the implementation. See cashless solutions, e-purse and POS hardware and software.
Membership and Club Applications
Possible workflows:
- Member identification
- Membership status
- Access rights
- Facility usage
- Integration with membership software
See BSD’s club and membership management software and smart card membership cards.
NFC Visitor Management
Possible workflows:
- Visitor identification
- Temporary card assignment
- Host association
- Check-in and check-out
- Expiry of temporary access
See BSD’s visitor management system.
NFC Parking
Possible workflows:
- Card-based identification
- Parking entitlements and monthly passes
- Entry and exit recording
- Integration with the parking application
See BSD’s parking application page.
NFC Asset Identification
Possible workflows:
- NFC tag identification
- Asset records and location
- Ownership and inspection history
- Maintenance records
The asset identification or tracking software usually has to be developed or integrated. For RFID-based tracking, see asset management software.
NFC Authentication
Possible workflows:
- Application-level user identification
- Operator authentication in your software
This is identification inside an application. It is not Windows domain or Active Directory login.
NFC Kiosk and Self-Service Applications
Possible workflows:
- User identification
- Account lookup
- Registration
- Other authorized self-service actions
For kiosk hardware, see the POS kiosk.
Library and Institutional Card Applications
Possible workflows:
- Member identification
- Issue and return workflows
- Integration with library software
For RFID-based libraries, see RFID library automation.
Custom NFC Integration
Possible workflows:
- Reader and card evaluation
- SDK and operating-system check
- Database and API integration
- Your business workflow
BSD evaluates the reader, card, SDK, operating system, database, API and workflow before quoting. See custom software development.
How an NFC or Smart Card Project Works
Requirement
What the card must do, how many users and locations, and which systems are involved.
Evaluation
Reader, card, SDK and operating-system check; tests with your own cards where possible.
Scope and quote
Hardware, development and integration are quoted separately.
Development
Application, database and integration work for the agreed scope.
Testing and deployment
Testing with real cards and machines, then rollout and training.
DESFire Application Development
BSD Infotech can evaluate and undertake custom application development for projects involving compatible DESFire cards and NFC readers. The development scope depends on the selected card, reader capabilities, available SDK/documentation, required development resources, and security architecture.
Depending on the project, potential requirements may include card initialization, application/file configuration, authentication workflows, key-management workflows, personalization, card issuance, validation, and integration with the customer’s software or database.
Each DESFire requirement is evaluated individually before confirming technical feasibility, scope, timeline, or commercial terms.
Which ACS readers list DESFire support: see MIFARE DESFire support on NFC readers. Technical background: DESFire on the SDK page.
Readers and SDKs We Work With
BSD supplies genuine ACS readers. For product details and developer resources, see:
Compatibility depends on the reader, card, driver and SDK for your operating system; it is confirmed for each project.
Frequently Asked Questions
Tell Us What Your Card Needs to Do
Share the card type, reader (if chosen), operating system, number of users and the system it must connect to. We will tell you what is feasible and how we would approach it.
Sales
Email: info@bsdinfotech.com