Commercial + product guide
nexID without jargon: connected products, evidence and after-sales in one tap
We do not sell loose chips or blockchain as a trend. We create a layer that validates tag messages, displays declared product data and activates governed warranty, benefits and digital certificates.
Open labSimple architecture
Architecture in one sentence
A declared product reference receives a digital identity; each tap validates the available tag message, displays bounded evidence and opens the next policy-approved step.
Declared reference + batch + images
Secure NFC or QR
Tap with a clear result
Passport, warranty, benefits and certificate
Real tabs to move validation into a pilot
Snippets use the canonical endpoint and tenant-scoped server credentials. The API key never reaches the browser, and the same contract works in a backend, POS or ERP.
Minimum contract received by the backend
1export NEXID_API_BASE="https://api.nexid.lat"2export NEXID_API_KEY="<SERVER_SIDE_API_KEY>"3export NEXID_TENANT_SLUG="mi-marca"4export NEXID_BID="NXD-LOTE-001"5export NEXID_PICC_DATA="<PICC_DATA_HEX>"6export NEXID_ENC="<ENC_HEX>"7export NEXID_CMAC="<CMAC_HEX>"89curl -X POST "$NEXID_API_BASE/api/v1/sdk/verify" \10 -H "x-nexid-api-key: $NEXID_API_KEY" \11 -H "x-nexid-tenant-slug: $NEXID_TENANT_SLUG" \12 -H "Content-Type: application/json" \13 --data-binary @- <<JSON14{15 "bid": "$NEXID_BID",16 "picc_data": "$NEXID_PICC_DATA",17 "enc": "$NEXID_ENC",18 "cmac": "$NEXID_CMAC"19}20JSONProduction validation is finalized server-side: replay, tenant policy, ownership and warranty do not live in the client.
Connect this page with the rest of the site
Product thesis
- • BASIC line (NTAG215): volume UX and operational control.
- • SECURE line (NTAG 424 DNA): cryptographic message authentication and verifiable tag evidence. TagTamper reports circuit state when correctly integrated.
- • nexID OS: issuance + verification API + dashboard + webhooks + reseller channel.
- • Marker-agnostic architecture: NFC + QR fallback from day one.
What to sell with each chip
NTAG215
✓ Events, activations, loyalty, warranties, tap-to-web.
⚠ Do not position as premium anti-fraud.
NTAG 424 DNA
✓ Authenticated SUN/SDM messages, secure vouchers and documents.
⚠ Do not claim native cold-chain sensing.
NTAG 424 DNA TagTamper
✓ Packaging circuit-state evidence where reported open/closed status matters.
⚠ Do not force into rigid credentials where tamper loop adds little value.
Enterprise API
Routes for health, cryptographic validation, CRM capture, operational events and multi-tenant orchestration.
GET /health
Backend health and uptime checks.
GET Passport validation
SDM/SUN secure validation; exact endpoint redacted in public docs.
POST /assistant/chat
Sales BotIA for leads/tickets/orders.
GET/POST Private CRM endpoint
CRM-lite pipeline for super-admin; internal route not published.
POST Sandbox pack loader
Load vertical packs in a controlled sandbox environment.
POST Sandbox validation runner
Run a simulated NFC validation for commercial QA without treating it as production evidence.
nexID SDK & APIs
Ofrecemos un SDK base, contratos API y webhooks para integraciones propias. Adaptadores para Shopify, WooCommerce, mobile o POS se definen por proyecto hasta que estén publicados como paquetes versionados.
Prioritized sellable packs
- • 1) Wine Secure.
- • 2) Events Basic + Events Secure.
- • 3) Docs & Presence Secure.
- • Immediate expansion: Cosmetics Secure. Regulatory expansion: DPP-ready exporters.
Operational standard for serious pilots and rollouts
- • Create one batch per customer/campaign with batch_id, SKU, expected volume and security profile defined up front.
- • Give suppliers a closed spec: chip, URL template, key custody, CSV manifest format, visual bank fields (image_url/label_image_url/model_url/gallery_urls) and activation criteria.
- • Import manifests only when the file batch_id exactly matches the batch created in platform.
- • Track planned / imported / active states to catch supplier mismatches before scaling to 10k/50k units.
Revenue model
- • Setup/Pilot fee.
- • Hardware margin.
- • Recurring SaaS/usage.
- • White-label channel rev-share.
Technical roadmap
- • Now: NTAG215 + NTAG 424 DNA; TagTamper where reported circuit state adds value.
- • Next: middle tier with StatusDetect capabilities.
- • Always: NFC + QR fallback + DPP-ready data model.
Enterprise trust layer
Tenant Vault shows evidence, manifests, QA and hashes; it does not expose internal secrets.
Supplier Encoding Pack sends encoding keys only per sub-batch through an encrypted channel; factories never receive KMS or database URLs.
IOTA can anchor selected supply-chain evidence as hashes or Merkle roots when audit policy requires it. We do not put private data or every individual tap on-chain.
Polygon can record a digital ownership title and wallet control after identity, purchase evidence and policy approval. The transaction does not prove physical ownership, custody or authenticity, and it is not used for every tap.
Enterprise trust FAQ
Official partnerships?
No. Polygon and IOTA are technologies the architecture can integrate with; do not claim an official partnership unless there is a signed public agreement.
Does every tap go on-chain?
No. Taps are validated server-side. Chains are used only for approved ownership, certificates, claims, transfers or batched proof anchors.
Is IOTA zero-fee here?
No. We position IOTA as an optional proof/audit layer for hashes, Merkle roots, DPP and logistics evidence, without zero-fee claims.
Do customers need a wallet?
No. Consumer UX stays mobile-first. Custodial or wallet flows are optional and policy-driven.
Does NTAG 424 DNA work offline?
The chip can generate a fresh SUN/SDM response without internet. A normal browser still needs connectivity for the backend verdict on the message, replay and policy; industrial offline validation needs a controlled app or reader with scoped keys.
Can we build an offline verifier app or reader?
Yes, but it must use device-scoped, batch-scoped and expiring keys. Never embed tenant master keys in a consumer app. Its local message result is provisional until backend replay and policy checks; ownership and warranty use separate evidence.
Is private data stored on-chain?
No. Private data and raw UIDs stay off-chain; proofs use hashes, salts, policy checks and tenant-scoped records.
Internal technical notes for due diligence
Available to qualified buyers and partners; public claims stay conservative until releases and agreements are signed.
Short FAQ to make the value clear
Video explainer
Original institutional cutA useful English FAQ companion for buyers who want the story before entering the guided environment.＋What problem does this solve for a premium brand?
It presents digital evidence per unit, records where a read was reported, reduces fraud risk and opens an after-sales relationship. Impact must be measured in the pilot.
＋What does the end customer see?
A simple screen: NFC message result, declared origin and batch data, TT state when available, warranty, benefits and, when relevant, a digital certificate or ownership record.
＋How can a company start without a huge project?
With a pilot on one line, batch or edition: product photos, claim rules, tags or QR, mobile portal, dashboard and usage metrics.
＋Does nexID sell NFC chips?
No. nexID provides infrastructure to issue and operate digital identities associated with declared references, and to validate messages from NFC or QR carriers.
＋Is this only anti-fraud?
No. It also enables digital ownership, access, warranty, vouchers, traceability and analytics.
＋Are tokenization and authentication the same?
No. Cryptographic validation checks the tag message and its rules; tokenization records digital rights. Neither proves the physical object by itself.
＋Can it work with QR?
Yes. A single backend can run NFC plus QR fallback.
＋Is this only for wine?
No. It also fits events, documents, credentials, cosmetics, luxury and public sector workflows.
New strategic guides
We added two pages to clearly separate anti-fraud, passport and programmable rights, and to tailor the pitch by buyer profile.