NFC payload URLs do not match frontend routing patterns, causing broken card navigation

[Ridanshi]

Summary

Generated NFC payload routes are inconsistent with frontend route definitions.

Users scanning NFC-enabled cards can be directed to invalid or non-existent routes.

Affected Files

• nfc.ts
• frontend routing configuration

Root Cause

NFC URL generation and frontend route definitions have diverged.

The generated payload references paths that are not consistently handled by the frontend router.

Reproduction

1. Generate an NFC-enabled card.
2. Scan the NFC payload URL.
3. Follow the generated route.
4. Compare against valid frontend routes.
5. Observe navigation failures or unexpected redirects.

Expected Behavior

NFC payload URLs should resolve correctly within the frontend application.

Actual Behavior

Generated URLs can reference unsupported routes.

Why This Is Difficult To Detect

Most testing focuses on browser navigation rather than NFC workflows.

The issue appears only when using generated NFC payloads.

Production Impact

• Broken NFC experiences
• Failed card sharing
• Navigation errors
• User confusion

Suggested Fix

Align NFC route generation with frontend routing definitions and add route consistency validation.

Severity

Medium

[Ridanshi]

I investigated this issue and would like to work on it.

The current NFC URL generation flow appears inconsistent with frontend routing expectations.

I plan to:

• review NFC payload generation
• align route generation with frontend routing
• preserve existing NFC functionality
• add regression tests validating generated URLs

Please assign this issue to me.