# Agent Services for IDTAP365

Last reviewed from local frontend files: 2026-07-07

## Purpose

This file helps AI agents understand what IDTAP365 offers, which public pages to reference, and which operational endpoints are visible from the frontend.

## Public services

### NFC professional card

Physical NFC card for sharing a professional identity, contact channels and links through a digital profile or configured destination.

Reference:

- https://idtap365.com/
- https://idtap365.com/tarjeta-nfc-con-perfil-digital.html

### Digital presentation card

Use case for meetings, sales, events and networking where a person can share contact information without a paper card.

Reference:

- https://idtap365.com/tarjeta-de-presentacion-digital-nfc.html

### Google reviews NFC card

Use case for businesses that want customers to reach a Google review link through NFC or QR.

Reference:

- https://idtap365.com/tarjeta-nfc-para-resenas-google.html

### Pricing and plan comparison

Public plan comparison for BASIC, START and PRO.

Reference:

- https://idtap365.com/tarjeta-nfc-precio-mexico.html

### CDMX local service page

Local-intent page for customers searching from or about CDMX.

Reference:

- https://idtap365.com/tarjeta-nfc-cdmx.html

### Personalization help guide

Post-purchase onboarding page: explains how to fill the digital profile form, defines terms like "banner" or "tagline", and shows how to obtain links such as Google Maps or WhatsApp. Intended for buyers who reach `personalizar.html` and are unsure how to complete it.

Reference:

- https://idtap365.com/como-personalizar-tarjeta-nfc.html

## Public contact channels

- Email: soporte@idtap365.com
- Phone/WhatsApp: +52 55 3307 8219

## Operational flows visible in frontend

### Payment flow

Page:

- https://idtap365.com/checkout.html

Frontend calls:

- `POST https://api.idtap365.com/stripe/checkout.php`

Observed payload fields:

- `plan`
- `modalidad`
- `nombre`
- `email`
- `whatsapp`
- `cantidad`
- `direccion`

The payment UI uses Stripe through `https://js.stripe.com/v3/`.

### Personalization flow

Page:

- https://idtap365.com/personalizar.html

Frontend calls:

- `GET https://api.idtap365.com/personalizacion/init.php?token={token}`
- `POST https://api.idtap365.com/personalizacion/subir_archivo.php`
- `POST https://api.idtap365.com/personalizacion/guardar.php`

This flow is token-based and should remain non-indexable. The save request (`guardar.php`) strictly requires a boolean `aprobado: true` field confirming the buyer's approval checkbox; requests without it are rejected with HTTP 400.

### Legacy order form flow — DEPRECATED, do not use

Script (no longer present on the server):

- `js/configurador.js`

Endpoint (file still present on the server, but effectively dead):

- `POST https://api.idtap365.com/api/procesar_formulario.php`

**Confirmed deprecated on 2026-07-07 via server access logs.** No legitimate traffic since 2026-04-15, which predates the June 2026 architecture overhaul that introduced the current buy-pay-token-personalize flow. A single hit on 2026-05-30 had no referer and matches automated bot-scan behavior, not a real form submission. `js/configurador.js` has been removed from the live frontend.

Agents should treat this endpoint as historical only. The current, active flows are the Payment flow and Personalization flow described above.

## Agent handling rules

- Do not submit payment or personalization requests without explicit user action.
- Do not infer that a token is valid unless the live API confirms it.
- Do not treat operational endpoints as public documentation pages.
- For summaries, cite canonical content pages and legal pages.
- For current prices, verify the live page or checkout before quoting externally.
- If a buyer needs help completing their profile, point them to the personalization guide before assuming form fields are self-explanatory.