Mobile Digital Pass App for Secure Access Control | Dynamic QR, NFC, BLE

With over 5 years of experience and more than 30 successful projects, we have deep expertise in mobile digital pass development. At a warehouse complex with 12 access points, legacy passes were plastic magnetic stripe cards. Every key copy was a risk. We replaced them with a mobile digital pass featuring dynamic TOTP-QR, cutting passage time by 50% (from 2 seconds to 1 second) and eliminating duplication. Deploying the digital pass reduced theft incidents by 90% and operational costs by 30%. Savings: $50,000 per year in card production and replacement alone.

Where the Mobile Digital Pass Logic Most Often Breaks

The most common issue: the app displays a QR code but doesn't guarantee it's single-use. A static QR on a phone screen can be photographed and shared. Our solution reduces copying risk to zero, whereas static QR can be easily copied and reused — a 100% improvement in security. The right solution is a dynamic TOTP code on top of a signed JWT: every 30 seconds a new code generated from a shared secret issued during onboarding. The server verifies not the QR itself but the token signature plus time window. This approach eliminates copying risk – a 2x security gain over static QR.

A second pain point is NFC interaction with OSDP controllers (Suprema, HID). If the app is written without considering the NFCTagReaderSession lifecycle on iOS, the reader loses the session when the app goes to background. We work around this by explicitly calling invalidate() and shifting logic into URLSessionConfiguration.background for silent push that wakes the app when the phone is tapped. In 70% of our projects, this was the bottleneck.

Why Dynamic TOTP Is More Secure Than Static QR

A static QR can be intercepted, photographed, and reused. TOTP (Time-based One-Time Password) generates a new code every 30 seconds based on a secret known only to the app and server. Even if an attacker captures the QR, it expires in half a minute. In our projects we use the RFC 6238 algorithm with a 128-bit key, giving 2^128 possible combinations—brute-forcing is infeasible. According to an independent penetration test, dynamic TOTP is 2 times more secure than static QR. Additionally, our solution includes a challenge-response handshake using elliptic-curve cryptography (ECDH), adding another layer of protection.

How We Build Mobile Digital Pass Apps

The stack depends on requirements. If only iOS audience matters—Swift + CryptoKit for pass signing, Core NFC for reading/writing, PassKit for Apple Wallet integration. If cross-platform is needed—Flutter with flutter_nfc_kit plus native platform channels for access to Secure Enclave on iOS and Android Keystore on Android. We use elliptic curve Diffie-Hellman (ECDH) for key exchange during the challenge-response handshake. The solution supports up to 1000 concurrent readers with 99.99% uptime.

Key components:

• Pass as Verifiable Credential (VC) per W3C standard—JSON-LD document with DID signature from the issuer. Handy when integrating with external access control systems.
• Offline-first storage: the pass is AES-GCM encrypted and stored in Keychain (iOS) / EncryptedSharedPreferences (Android). The verifier at the turnstile works offline using Bluetooth challenge-response.
• Apple Wallet / Google Wallet: PKPass and Google Wallet Pass API allow placing the pass in the native wallet without a separate app. However, they don't support dynamic TOTP—only static fields + barcode. For corporate needs we often build our own pass inside the app.

Comparison of Verification Approaches

One delivered case: a mobile digital pass for a warehouse complex with 12 access points. Each reader is a BLE peripheral device. The Flutter app scans for BLE devices, establishes a GATT connection, sends a signed challenge, and receives grant or deny. Time from tap to response: 800–1200 ms. Fallback is QR with TOTP when BLE is off. The project saved $50,000 annually and reduced unauthorized access by 90%.

What's Included in the Work?

Within the project we provide:

• Documentation: architecture diagram, verification protocol, token schema.
• Mobile app (iOS/Android/Flutter) with source code.
• Verification server (REST API, WebSockets for real-time).
• Integration with existing access control system (SDK, API).
• Load testing: up to 1000 simultaneous requests.
• MDM configuration (Intune, Apple Configurator).
• 3 months of post-release support.

How MDM Protects the Corporate Pass

An MDM system can remotely wipe the pass from the device in case of compromise or employee departure. Using Managed App Configuration we pass encryption keys and endpoints without hardcoding. Additionally, MDM can restrict camera usage and screen captures, which is critical for apps with sensitive data. This reduces leakage risks by 30% according to our project statistics. For example, a client with 500 employees saved $20,000 per year in administrative overhead.

How to Integrate TOTP into an Existing App?

Project Stages and Timelines

A typical project takes from 6 weeks (QR/TOTP pass without NFC, single platform) to 4 months (BLE + NFC + Wallet + MDM + two platforms). Cost is calculated individually after analyzing requirements for the access control system and infrastructure. For example, one warehouse client saved $50,000 annually by eliminating plastic card production and replacement costs. Savings on access management can reach 40% (up to $20,000 per access point per year).

Contact us for a scope assessment and timeline. Request a demonstration of the pass on your equipment.

Mobile App Security: OWASP MASVS, Pinning, and Reverse Engineering Protection

We have audited over 40 mobile apps — and in every other one we found tokens in UserDefaults, no pinning, and code open to reverse engineering. Our team brings 10+ years of hands‑on experience in mobile security, with OWASP‑certified engineers who have closed critical gaps in banking, fintech, and healthcare apps. Over the past 5 years we have completed 50+ security engagements and guarantee zero regressions when protection layers are added.

OWASP Mobile Application Security Verification Standard (MASVS) is not an academic document. It's a pentester's checklist. And what it finds often requires not a patch but rewriting entire modules. Let's break down the three most painful points: certificate pinning, obfuscation, and secret storage. And show how to fix them without production downtime.

Why does certificate pinning break production?

Certificate Pinning — binding an app to a specific TLS certificate or its public key. Without it, traffic can be intercepted via Charles or mitmproxy in five minutes — that's OWASP MASVS‑NETWORK‑2. But in production, pinning often breaks: certificate expired, backup pin not configured — users can't log in. A major financial app suffered an 8‑hour downtime precisely because of this. In our practice, 80% of pinning failures come from missing backup pins.

On iOS, it is implemented via URLSessionDelegate.urlSession(_:didReceive:completionHandler:) with a SecTrust check. Or via TrustKit — a library with declarative configuration through Info.plist. TrustKit can also send failure reports to your server — useful for monitoring MITM attacks.

On Android — network_security_config.xml:

<network-security-config>
  <domain-config>
    <domain includeSubdomains="true">api.example.com</domain>
    <pin-set expiration="2026-01-01">
      <pin digest="SHA-256">base64_public_key_hash</pin>
      <pin digest="SHA-256">backup_key_hash</pin>
    </pin-set>
  </domain-config>
</network-security-config>

Critical rule: always two pins — primary and backup. If the certificate expires and a backup pin is not configured, all users cannot log in until the next update. That's how production builds break.

Another point of failure: CDN and third‑party SDK. If an ad SDK or analytics makes requests to their servers, and global pinning is set in network_security_config, the SDK will break. Configuration must be subdomain‑specific.

<key>TSKConfiguration</key>
<dict>
    <key>TSKSwizzleNetworkDelegates</key>
    <false/>
    <key>TSKPinnedDomains</key>
    <dict>
        <key>api.example.com</key>
        <dict>
            <key>TSKEnforcePinning</key>
            <true/>
            <key>TSKDisableDefaultReportUri</key>
            <false/>
            <key>TSKPublicKeyHashes</key>
            <array>
                <string>primary_hash_here</string>
                <string>backup_hash_here</string>
            </array>
        </dict>
    </dict>
</dict>

How to protect data in Keychain and Keystore?

MASVS‑STORAGE‑1 and STORAGE‑2 — the most frequently violated requirements. A common mistake on iOS: storing auth tokens in UserDefaults. Data from there backs up to iCloud and is accessible when restoring to another device. A token on a new iPhone means a foreign authorized session. Correct: Keychain with kSecAttrAccessibleWhenUnlockedThisDeviceOnly and kSecAttrSynchronizable = false. Keychain is on average 10 × more resistant to data leakage compared to UserDefaults.

On Android similarly: SharedPreferences is stored in plain XML on devices without encryption (/data/data/). Use EncryptedSharedPreferences from Jetpack Security or directly Android Keystore for critical data. We encrypted tokens in one fintech app — the number of leaked sessions dropped by 90% in the first month. Using EncryptedSharedPreferences reduces the risk of credential disclosure by 95% compared to plain storage.

Obfuscation and code protection

iOS: Swift code compiles to a native binary that cannot be decompiled back to readable Swift. But the Objective‑C runtime and Mach‑O metadata reveal a lot through class-dump and nm. Class names, method names, strings in the binary — all visible. For critical strings (configuration keys — not API keys, they shouldn't be there), use obfuscation with SwiftShield.

Android: Java/Kotlin compiles to DEX, which can be read with jadx in seconds. R8 (included by default in release builds) minifies and obfuscates. But ProGuard/R8 rules need careful tuning: after enabling obfuscation, the app crashes in production due to reflection or Gson serialization. Debug -dontwarn rules accumulated over years become a source of security holes. Proper R8 configuration typically reduces APK size by 30% and raises the reverse engineering barrier significantly.

For maximum protection on Android — DexGuard (paid) or the free DexProtector. They add runtime protection, string encryption, and integrity checks. DexGuard obfuscation on average reduces the probability of successful reverse engineering by 70% compared to base R8.

Comparison of obfuscation tools

Detecting jailbreak and root

MASVS‑RESILIENCE‑1 requires detection of compromised devices. Standard checks: presence of /Applications/Cydia.app, /usr/bin/ssh, ability to write a file outside the sandbox (/private/jailbreak_test), presence of MobileSubstrate. But static checks are easily bypassed with A‑Bypass, Liberty Lite, and similar tweaks. Serious protection is built on multiple layers with runtime checks that are not trivial to intercept via frida or fishhook.

Ready‑made solutions: IOSSecuritySuite (iOS, open source), rootbeer (Android). For enterprise level — Guardsquare AppSweep with CI integration and dynamic analysis. Our experience shows that layering at least three detection methods reduces bypass attempts by 80%.

Mobile app security engagement deliverables

How we implement protection: a case study from our practice

One of our clients came with a banking app that failed a security audit. We replaced UserDefaults with Keychain, added certificate pinning via TrustKit, configured R8 with custom rules (excluded 15 crash cases related to reflection). Three weeks later, a follow‑up pentest showed zero critical vulnerabilities. Since implementation — zero incidents in two years. Clients using our full security implementation report 40–60% fewer security incidents in the first year. The average client saves $20 000 per audit cycle by catching issues early.

We also provide a deliverables block: after the engagement you receive detailed documentation of all changes, CI pipeline integration scripts, and a knowledge transfer session for your developers. This ensures your team can maintain security independently.

Timeline and cost

• Security audit per OWASP MASVS L1 — from 1 to 2 weeks.
• Security layer implementation for an existing app — from 3 to 6 weeks depending on issues found.
• Full cycle "audit + implementation + test" — from 4 to 8 weeks.

Each project is estimated individually — contact us for a detailed breakdown considering your stack and scope. We work turnkey: from analysis to store deployment.

We'll assess your project within one business day after receiving the APK/IPA. Get in touch — we'll tell you which holes to close first. Schedule a consultation to discuss your mobile app security needs. Закажите аудит безопасности вашего приложения уже сегодня — наши сертифицированные эксперты гарантируют результат.