# Arquitectura de Blerify

### Arquitectura de mDL de Blerify <a href="#id-0-toc-title" id="id-0-toc-title"></a>

El diagrama muestra una arquitectura modular para la solución mDL (Mobile Driver’s License) de Blerify, basada en varias capas y servicios que interactúan con sistemas externos e internos.

<figure><img src="/files/069353d9e0eb2b1afe8417a764eec43ea1650e43" alt=""><figcaption></figcaption></figure>

### Proceso de emisión de mDL <a href="#betterdocs-entry-title" id="betterdocs-entry-title"></a>

El proceso se centra en emitir **mDL** (Mobile Driver’s License) dentro de una arquitectura integrada, que involucra múltiples etapas y componentes técnicos. Aquí tienes un desglose de los puntos clave:

<figure><img src="/files/d7921e03bb95ac72a53be114423b1c5f3b24d750" alt=""><figcaption></figcaption></figure>


---

# 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:

```
GET https://docs.blerify.com/es/productos/digital-credentials/issue/licenses/blerify-architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.