Track2 → NFC
Paste magnetic Track 2 data and emulate contactless MSD on one phone — isolated from Relay, no server required.
- Visa, Mastercard, Maestro, Amex, Discover, JCB, UnionPay
- Live APDU log · card preview · full-screen tap overlay
PROJECT X
Initializing secure shell…
0%
Enterprise NFC infrastructure
PROFESSIONAL TEAMS · DEDICATED INFRASTRUCTURE
Android devices, regional relay nodes and a full web panel — one tenant workspace per subscription. Live sessions, EMV analytics, device provisioning and remote config from anywhere.
[ RELEASE NOTES ]
Track2 NFC, relay HCE improvements and panel polish — August 2026.
Paste magnetic Track 2 data and emulate contactless MSD on one phone — isolated from Relay, no server required.
Wider payment scheme list on Tag — more POS terminals select the app during relay.
Display stays awake while Reader, Tag or External relay is active.
Track2 and Relay cannot run together — relay hot path unchanged when Track2 is off.
Panel preview tabs match sidebar order; faster viewport-sized screenshots.
[ OVERVIEW ]
Complete NFC relay stack — Android app, regional server and operator panel in one subscription.
Phones connect through regional relay nodes. Typical APDU round-trip under 50 ms on tuned EU/US/APAC paths — live RTT dashboard in the app (v5.5.17+). Traffic is scoped per tenant.
Start/stop relay, kick clients, blacklist IPs, maintenance mode, live logs and session exports from one dashboard.
APDU live view, bypass statistics, POS/ATM payment tracking, card BIN enrichment and CSV exports for operations.
[ LATENCY LIVE ]
Built into Relay since v5.5.17 — real round-trip per APDU on Tag and Reader. Tag measures POS → relay → Reader → card → back to POS.
42 ms
Last APDU round-trip (example · Frankfurt node)
FAST avg < 50 ms · target ~1 s POS
OK 50–120 ms · typical 2–3 s POS
SLOW > 120 ms — check WiFi / relay region
Use both phones on stable WiFi and the nearest relay region. Jinkusu Device field units add roughly +15–45 ms vs phone NFC — not hundreds of ms.
[ SETUP ]
From checkout to live relay — what happens after you subscribe.
Subscribe
Monthly or annual via crypto checkout. Choose EU, Americas, APAC or MENA — relay node is assigned to your tenant.
Panel access
You receive panel URL, username and password. Enable TOTP on first login — isolated workspace, no shared admin.
QR Connect
Download APK from panel, scan QR on Reader and Tag. Session # and PIN push remotely — no manual typing on devices.
Relay live
Hit START on dashboard — sessions appear live. Monitor APDU, payments, kick clients, export CSV from one panel.
[ STACK ]
Operation modes, live flow and walkthrough video — relay, bypass, POS, ATM and Jinkusu field capture.
Demo presentation
Step-by-step walkthrough video will be placed here.
Core stack: Android app · Regional relay · Client panel
[ HARDWARE ]
Compact field unit — custom footprint, NFC cap, motion & ambient sensors, relay integrated.
Custom-manufactured · server & app integrated · rechargeable
Shape, dimensions, colors, LED zones, logo — save as JSON and send with your order.
Need a specific length, width or cap diameter? Use the to preview shape, colors and LEDs, save JSON, then send it during onboarding or contact us to specify dimensions, battery profile and NFC cap layout for your deployment.
JINKUSU.DEV[ READER MODES ]
Both use the same relay + Tag flow inside your tenant. Use phone NFC for quick tap, or a custom Jinkusu Device field unit for stable hands-free reads.
| Phone NFC Reader | Jinkusu Device | |
|---|---|---|
| Card source | Physical card or wallet on phone antenna | Contactless read via Jinkusu NFC cap (5 cm field) |
| Best for | Quick tap, mobile wallet relay | Hands-free at terminal, custom enclosure, field telemetry |
| Hardware | Any Android phone with NFC | Custom-built Jinkusu Device (BLE · rechargeable · motion & ambient sensors) |
| Typical latency | ~35–45 ms RTT on regional node | +15–45 ms vs phone NFC (wireless field link) |
| App menu | Relay → Reader | Relay → Jinkusu Device (External) |
Design your Jinkusu Device footprint, colors and LED layout in the customizer above — units are manufactured to your saved specification.
[ PLATFORM ]
Android app, operator panel, security and provisioning — no per-feature upsells.
[ PANEL ]
The same web panel included with every subscription — relay control, live sessions, payments, devices and remote app setup. Browse the screens below to see what your team gets on day one.
[ SECURITY ]
Panel protected with time-based one-time codes — no shared superadmin access for tenants.
Dedicated relay region, tenant token and session scope — traffic never crosses accounts.
Block abusive IPs permanently or allow-only lists when you need strict device control.
UUID blocking, remote kick, maintenance mode — reject new sessions without killing ops mid-flight.
[ REGIONS ]
Isolated regional nodes — EU, Americas, APAC and MENA.
[ PRICING ]
Full platform access — app, panel, relay assignment and Jinkusu support included.
$2,000
per month · billed monthly
$10,000
per year · billed annually
Save $14,000 vs 12× monthly
[ REVIEWS ]
[ FAQ ]
PROJECT X is an enterprise NFC relay stack: an Android application, a regional relay server and a full web operator panel. Your team runs live NFC/APDU sessions, manages connected devices, views EMV traffic, tracks payments and exports operational data — all scoped to your own tenant workspace.
Two plans are available: Monthly — $2,000 USD / month and Annual — $10,000 USD / year (equivalent to $833/month, saving $14,000 compared with 12 monthly payments). Both include the full platform: client panel, Android app provisioning, regional relay assignment, devices/cards/APDU/payments modules and Jinkusu Device software integration.
You submit your work email and chosen plan on the Subscribe page. If crypto checkout (BTCPay) is enabled on the platform, you pay via invoice and provisioning runs automatically when the invoice settles. Otherwise your request is queued for manual confirmation. Once active, you receive panel login credentials (username, password, TOTP secret), a relay region assignment and access to download the APK and QR Connect provisioning from your panel.
Yes. Each subscription creates a separate tenant workspace with its own credentials, tenant token and relay node assignment. Relay sessions, device reports, card data and logs are never mixed with other clients on the platform.
Standard regions include Frankfurt, London, Virginia, Oregon, Singapore, Tokyo, Dubai and São Paulo. Additional live relay nodes appear on the platform map when enabled by the operator. You choose a region at subscription or from your panel; the Annual plan includes priority region selection.
Download the APK from your panel (Download App section), install it on the device, then open QR Connect in the panel and scan the QR code. The app receives host, port, session PIN and TLS settings instantly via remote config — no manual typing required.
From the browser panel you can START/STOP the relay, view live sessions, kick clients and blacklist IPs, enable maintenance mode, block device UUIDs, push QR remote config, monitor cards and payments (with CSV export), stream live APDU, review stats and timeline, configure Telegram alerts/webhooks/schedulers, and use the operations center plus system health views.
The Jinkusu Device is optional field hardware (minimum footprint >4.5×4.5 cm, 7 mm profile, up to 24 h rechargeable battery, NFC within a 5 cm cap radius, motion and ambient sensors). It pairs with the same relay server and Android app inside your tenant. Use the live customizer on this page to design shape, colors and LED zones, then save JSON with your order. Physical units are built to order via JINKUSU.DEV.
Client panel access requires username + password + TOTP (6-digit code from an authenticator app). You can further restrict access with IP blacklist/whitelist, per-device UUID blocking, maintenance mode and a remote app kill-switch pushed through remote config.
With a nearby regional relay and stable WiFi, round-trip is often under 50 ms per APDU (live on Tag since v5.5.17). Total POS time depends on ~18 EMV hops — typically 1–3 seconds on a tuned setup, not tens of seconds.
On the Subscribe page, select Monthly or Annual and enter your work email. When BTCPay is configured on the platform, checkout opens a crypto invoice. If BTCPay is not configured, you submit a subscription request and the platform team confirms provisioning manually. Existing clients sign in at Client Login.
Yes. The panel provides CSV export for payments and sessions, JSON export for cards, and TXT export for relay logs directly from the dashboard and system health pages. The Annual plan includes extended log retention and export capacity for long-running operations.