> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/guan-li-yu-she-zhi/settings/document-processing/module/bar-code-qr-code-extraction/pagopa.md).

# PagoPA

## 概述

**PagoPA** 是意大利公共行政部门使用的支付二维码标准。意大利公共行政机构（市政厅、大学、医疗机构、税务机关）签发的每张发票都带有 PagoPA 二维码。DocBits 会解码其载荷，并在文档 API 响应中返回全部四个必需的支付字段。

### 功能概述

PagoPA 载荷简洁且结构严格：单行中恰好包含 **五个以竖线分隔的字段**。金额以**分**（整数）编码，提取器会自动将其转换为欧元小数值。`codice_avviso`（18 位支付通知编号）的前导零会予以保留——绝不能将其解析为整数，因为该通知编号是定长标识符。

#### 主要优势

* **覆盖意大利公共行政发票的强制需求**：`codice_avviso` 和债权人税号会提取到具名字段中。
* **安全处理数值**：18 位 `codice_avviso` 会保留前导零；以分为单位的金额也会以欧元浮点值形式提供。

***

### 检测

* 魔数前缀：`PAGOPA|002|`
* 前缀后恰好包含 **5 个以竖线分隔的字段**：`PAGOPA|002|<codice_avviso>|<fiscal_code_creditor>|<amount_cents>|<auth>`
* **仅支持欧元**——根据规范，其他货币均无效

### 提取的字段

所有字段均使用 `pagopa_` 前缀：

| 字段                            | 描述                                         |
| ----------------------------- | ------------------------------------------ |
| `pagopa_codice_avviso`        | 18 位支付通知编号——保留前导零（字符串）                     |
| `pagopa_fiscal_code_creditor` | 11 位债权人税号（字符串）                             |
| `pagopa_amount_cents`         | 以分为单位的金额（整数）                               |
| `pagopa_amount`               | 以欧元为单位的金额（小数，由 `pagopa_amount_cents` 推导得出） |
| `pagopa_auth`                 | 载荷中的可选认证/版本指示符                             |

### 示例 API 响应

```json
{
  "pagopa_codice_avviso": "301234567890123456",
  "pagopa_fiscal_code_creditor": "80012345678",
  "pagopa_amount_cents": 12050,
  "pagopa_amount": 120.50
}
```

***

### 如何启用

PagoPA 解析由通用的**条形码 / 二维码提取**模块开关控制，无需特定标准的配置。

1. **前往设置**：
   * 从仪表板进入**设置**。
   * 选择**文档处理**，然后选择**模块**。
2. **启用该功能**：
   * 向下滚动，找到**条形码 / 二维码提取**选项。
   * 切换滑块以启用该功能。

如需查看支付二维码标准的完整列表，请参阅[概述](/chinese/guan-li-yu-she-zhi/settings/document-processing/module/bar-code-qr-code-extraction.md)页面。


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docbits.com/chinese/guan-li-yu-she-zhi/settings/document-processing/module/bar-code-qr-code-extraction/pagopa.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.