JAVACARD NATIVE
ML-KEM
ML-DSA
SLH-DSA
NIST FIPS 203 / 204 / 205
Developer Services
jNet develops production JavaCard applets for payment, identity, wallets, ePassports, and PKI use cases — built to match customer specifications, certification requirements, and secure deployment environments.
Built for JavaCard applet development, certification-aligned delivery, and NFC/mobile SDK integration.
MOBILE & APPLET DEVELOPMENT
Secure applications for certified platforms
jNet develops JavaCard applets, NFC mobile integrations, and secure application components for identity, payment, wallet, ePassport, and PKI use cases — built around platform constraints, certification requirements, and production deployment needs.
JavaCard Applet Development
Built around platform constraints
APDU, security, and certification constraints. jNet supports custom applet development across payment, identity, wallet, ePassport, PKI, and post-quantum use cases.
The work is scoped around the target operating system, secure element, GlobalPlatform setup, and expected certification path. This includes interface behavior, lifecycle handling, key management, and integration with the surrounding platform.
The goal is to reduce late-stage rework by aligning implementation decisions with deployment and evaluator requirements from the beginning.
APPLET VERTICALS
Payment
MChip Advance, qVSDC, payWave
ePassport
ICAO Doc 9303 BAC/PACE/EAC
Crypto wallet
BIP32/44, ECDSA, EdDSA
PKI middleware
PKCS#11 / PKCS#15
eIDAS 2.0
WSCA / WSCD
PQC hybrid applets
ML-KEM/ML-DSA
PIV / CAC
NIST SP 800-73-4/5
FIDO2
CTAP 2.3 authenticator
OpenPGP 3.4
sign, decrypt, SSH
OTP / OATH
TOTP / HOTP
CCC Digital Key
3.1
Custom protocols
on request
Certification-Aligned Development
Written to be evaluated, not retrofitted
The cost of discovering a certification gap during lab evaluation — rather than during development — is typically measured in months. jNet structures applet development around the target evaluation scheme from the first design session.
Common Criteria
CC EAL5+ Applets
Common Criteria applet development requires mapped security behavior, formal interface specifications, and evaluator-ready test evidence.
SFP documentation
ADV_FSP / ADV_TDS specs
ATE_COV / ATE_FUN test evidence
Pen-test surface pre-analysis
Level 2 / Level 3
FIPS 140-3 Applets
FIPS 140-3 applets require approved algorithm use, defined cryptographic boundaries, and traceable key-management behavior.
ACVP-aligned algorithm usage
Key Management coverage
FSM coverage for applet operations
Power-on KAT self-test hooks
Contact · Contactless
EMVCo Applets
EMVCo applets require transaction-flow coverage, kernel behavior validation, and contact/contactless test readiness before lab submission.
EMV Book 2 / Book 3 flows
Kernel 2 / 3 / 4 compliance
ARQC / ARPC validation
EMVCo-certified test room support
Mobile Application Development
Mobile apps for secure-element workflows
jNet builds iOS and Android application layers that connect JavaCard applets with real user workflows — credential issuance, authentication, PIN lifecycle, provisioning, and status visibility. The mobile app becomes the visible interface for secure-element operations, while sensitive key material remains protected inside the secure element.
The application layer handles NFC communication, secure-channel setup, user interaction, and backend-connected lifecycle flows. This makes it possible to provision, update, and manage credentials remotely without requiring physical access to each deployed token.
Together, the applet and mobile layers create a complete user experience for secure credentials — combining hardware-backed security with clear onboarding, biometric interaction, transaction confirmation, and operational visibility.
iOS SDK — Swift 5.7+ / iOS 15+
Core NFC ISO 7816 APDU transport layer
GlobalPlatform SCP03 secure channel over NFC
FIDO2 passkey and hardware authenticator integration
PIV credential management — PIN change, certificate read
Secure Enclave attestation bridge
In-app provisioning and OTA applet update flows
Android SDK — API 28+ / Kotlin / Java
HCE + NFC reader APDU transport
FIDO2 CTAP 2.3 client implementation
NFC card activation with PIN management UI
BLE pairing for secure-element devices
Android Keystore attestation integration
Crypto wallet transaction signing UI with hardware confirmation
WHAT NFC CONNECTIVITY ENABLES
Credential issuance, PIN lifecycle, and status display
Authentication events and policy alerts
OTA applet provisioning without physical card retrieval
Biometric-first UX backed by hardware key operations
Cloud connectivity for revocation, audit, and compliance logging
ENGAGEMENT MODEL
How a development engagement works
01
Specification & Scoping
Requirements, target silicon, OS version, and certification goals are reviewed before development begins.
02
Development & Validation
Applet and mobile components are built iteratively, with APDU testing, integration checks, and functional sign-off throughout the process.
03
Certification Package
Documentation and test evidence are prepared for the target scheme — CC, FIPS, or EMVCo — in the format evaluators expect.