D-Logic hardware · Independent distribution & integrationThe right interface. The right reader.

SDK / API / INTEGRATION PATH

Build the card operation your application needs.

Use this route for a custom application built around the manufacturer SDK or API. Local µFR models and Online variants use different software and connection paths; evaluate the required API, card and firmware together.

See the matching models

DEFINE THE APPLICATION

Start with the parts that decide the fit.

Describe the job more precisely than “read NFC”. A card identifier, NDEF record, memory block and authenticated application are different operations. Begin with the card model and desired result. Then match the host library and connection before comparing enclosures or antenna formats.

01

Operation and permissions

Identify what must be read or written and whether the project has the necessary keys or application credentials. Include a sample card and repeatable operation.

02

Host and software

Name your operating system, CPU architecture and programming language. Evaluate the manufacturer library or network API examples in that target environment.

03

Connection variant

USB, serial and network options depend on the ordered model. An interface listed for a family does not mean every finished unit exposes all connectors.

Compare PC/SC, SDK and keyboard input

PROJECT REQUIREMENTS

Start with the data your application needs.

Define the card operation and environment before comparing SDK readers, then plan a sample evaluation.

Illustrative requirement

Write an NDEF URL from a desktop application

Card and result
A tag with a known chip stores an agreed NDEF URL for read-back.
Host and software
Specify the OS, CPU architecture, application language and intended manufacturer library.
Operator workflow
Present a tag, write the record, remove it and verify the data when presented again.

A requirement example, not a device test or compatibility result.

Three decisions before selecting a reader

  1. Define the operation

    Separate UID, NDEF, memory and authenticated application tasks. Identify the exact card and its access conditions.

  2. Choose the software path

    Match the library, firmware and host architecture. Specify local USB or a network API before selecting a configuration.

  3. Agree sample evidence

    Record the expected data, API result and read-back checks. Use authorized samples and agree what counts as acceptance.

Prepare your SDK project brief

Describe your project and unknowns. Keep passwords, production keys and customer data out of the inquiry.

  • Host OS / CPU architecture / language / library and firmware versions: ___
  • Exact card or tag / target data / access permissions (describe without credentials): ___
  • Required operation / read-back after re-presentation / reconnect acceptance: ___
  • Sample and batch quantities / destination / requested schedule: ___

MAKE THE INQUIRY SPECIFIC

Tell us what the project needs.

  • Which card or tag and which read/write operation?
  • Which operating system, architecture and programming language?
  • Which connector, enclosure and estimated quantity?
Get selection advice & a quote

Selection questions

Is a UID keyboard reader a substitute for an SDK reader writer?

A keyboard reader supplies a card identifier. Choose a reader writer and suitable software path when the task requires card data access or writing.

Can I select hardware before checking the SDK?

A practical evaluation checks the card, operation, host library and hardware together. Confirm the software path before committing the installation design.

LET’S FIND YOUR FIT

A reader for your project, not the other way around.

Tell us your card type, platform and quantity. We’ll help narrow the options.

Tell us about your project