> For the complete documentation index, see [llms.txt](https://docs.qrpay.pe/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qrpay.pe/introduccion.md).

# Introducción

## API Pago QR – Comercio

Esta documentación describe los webservices del **módulo QR-Comercio** para la generación, consulta, bloqueo y notificación de pagos mediante códigos QR.

* **Sistema QR-Comercio**
  * Pública para webservices para:
    * Generar QRs de cobro.
    * Consultar el estado de un QR.
    * Bloquear un QR para evitar nuevos pagos.
* **Sistema Interno del Comercio**
  * Publica servicios que:
    * Reciben la confirmación de pagos realizados a los QR.
    * En algunos proyectos, proveen servicios para integración mediante Iframe (consulta de deudas y confirmación de pago).
* **Capa de seguridad**
  * Basada en:
    * Canales seguros (HTTPS/VPN)
    * Firma digital usando estándar **JWS (JSON Web Signature)**.
    * Opcionalmente, consumo plano (sin firma ni cifrado) para ambientes de desarrollo o pruebas controladas.
* **Ambiente de pruebas**
  * Incluye:
    * Aplicación web **Admin-QR** para seguimiento de QR y pagos.
    * Aplicación móvil de prueba para lectura y pago de QR en ambiente de test.

### Características generales de la API


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.qrpay.pe/introduccion.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.