> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.
# APIX 002
> On-demand Pix data submission to BACEN (Document 1202) — 12 months of transaction dimensions kept on hand, with format defined per request.
Pix participants must deliver detailed transaction data to BACEN whenever the regulator requests it. Reporter helps you keep that data structured and ready for ad-hoc extraction.
This guide covers the **APIX 002** report (Document 1202) — what to store, how to organize it, and how to respond when BACEN sends a request.
Unlike APIX 001, APIX 002 has no fixed XML format or XSD schema. Each request defines its own format, dimensions, and deadline. The institution remains responsible for extracting accurate data and meeting the deadline set by the regulator.
## What is APIX 002?
***
The **APIX 002** is an on-demand regulatory submission to the Brazilian Central Bank, defined by Normative Instruction BCB nº 32/2020. Unlike the monthly APIX 001, it is sent only when BACEN explicitly requests it, with the format specified per request.
### APIX 001 vs APIX 002
| Aspect | APIX 001 | APIX 002 |
| ----------------- | ---------------------------------------- | -------------------- |
| **Frequency** | Monthly (mandatory) | On-demand |
| **Deadline** | 15th business day of the following month | Defined per request |
| **Format** | XML (fixed XSD) | Defined per request |
| **Layout / XSD** | Available (version 2.5) | Not applicable |
| **Validation** | Pre + post submission | Post-submission only |
| **Document code** | 1201 | 1202 |
### Who must report
| Participant type | Must report? |
| ------------------------------------------------------- | ------------------------------------------- |
| Direct participant (transactional account provider) | Yes |
| Special settler | Yes |
| Indirect participant (settled via BTG, Itaú, or others) | No — consolidated by the direct participant |
Indirect participants do not report APIX 002 directly. The direct participant consolidates the data on their behalf. However, indirect participants must still *keep the underlying data available* for the direct participant to aggregate when BACEN makes a request.
### Submission attributes
| Field | Value |
| ------------------ | ---------------------------------------------------------- |
| Document name | On-demand Pix participant data |
| Document code | 1202 |
| STA code | APIX002 |
| Frequency | Non-periodic (on-demand) |
| Format | Defined per request |
| Validation | Post-submission |
| Autran transaction | SPIXP001 |
| Reference window | Monthly data covering up to 12 months prior to the request |
## Why APIX 002 has no fixed format
***
The normative explicitly defines the submission format as *"to be defined per demand"* ("Formato para Remessa: a definir para cada demanda"). This has four direct implications:
1. **No standard XSD** is published for APIX 002 — you cannot pre-build a single template.
2. **BACEN sets the format** at the moment of the request, including dimensions, granularity, and file structure.
3. **The institution extracts data** matching whatever dimensions are specified.
4. **The deadline is set per request**, with no standard turnaround time.
To stay ready, your data store needs to support flexible queries across all dimensions BACEN may ask for.
## Data dimensions to store
***
Participants must keep the data described in **Annex II of IN 32/2020** for at least 12 months. The data is organized across three groups: internally settled transactions, all transactions (internal and interbank), and cross-dimensional combinations.
### Internally settled transactions
These dimensions apply to transactions where both payer and receiver belong to the same institution.
| Field | Description | Values |
| ------------------------ | --------------------------------------------------------- | ------------------------------------------------------------- |
| **Scheduled** | Whether the transaction was scheduled | Yes / No |
| **Suspected fraud** | Transactions analyzed past the fraud detection time limit | Yes / No |
| **Not settled in time** | Transactions that exceeded 40 seconds | Yes / No |
| **Rejected** | Whether the transaction was rejected | Yes / No |
| **Rejection reason** | Per arts. 38 and 39 of Resolution BCB nº 1/2020 | Specific codes |
| **Initiation procedure** | How the transaction was initiated | 1) Manual; 2) Pre-stored values |
| **Initiation mechanism** | Mechanism used to start the transaction | 1) Pix key; 2) Dynamic QR; 3) Static QR; 4) Payment initiator |
| **Payer nature** | Person type | 1) Natural person; 2) Legal person |
| **Receiver nature** | Person type | 1) Natural person; 2) Legal person |
| **Initiator** | ISPB of the payment initiator | ISPB code (8 digits) |
### All transactions (internal and interbank)
These dimensions apply to the full transaction set, including interbank settlements via SPI.
| Field | Description | Example |
| ---------------------- | ----------------------------- | -------------------------------------------------------------- |
| **Year** | Reference year | 2026 |
| **Period** | Reference month | 01–12 |
| **Transaction count** | Total count | 1,250,000 |
| **Financial amount** | Sum of values | R\$ 985,000,000.00 |
| **Initiation channel** | Where the transaction started | 1) App; 2) Internet banking; 3) Call center; 4) ATM; 5) Branch |
### Cross-dimensional queries
BACEN may request combinations of multiple dimensions. Examples:
* Count of transactions that are **scheduled** AND **suspected fraud**
* Value of **rejected** transactions by **specific reason** AND **legal person**
* Transactions by **initiation channel** AND **initiation mechanism**
Structure your storage so any combination of these dimensions can be aggregated efficiently. A wide, denormalized table or a columnar store works better than highly normalized models for this type of regulatory query.
## Submission process
***
### System and transaction
| Item | Value |
| ------------------ | ------------------------------------------ |
| System | STA (Sistema de Transferência de Arquivos) |
| File code | APIX002 |
| Autran transaction | SPIXP001 |
| Document number | 1202 |
### Six-step flow
1. **Wait for the BACEN request** — there is no proactive submission.
2. **Review the format and deadline** specified by the regulator.
3. **Extract the data** matching the requested dimensions.
4. **Generate the file** in the specified format.
5. **Submit through STA** using the `APIX002` file code.
6. **BACEN runs post-submission validation** on the received data.
There is no pre-submission validation for APIX 002. BACEN validates the data only after you submit it. Make sure your extraction is accurate before sending.
## Implementation recommendations
***
### Data model
A flat, dimension-rich table simplifies on-demand extraction. The minimum recommended schema:
```sql theme={null}
CREATE TABLE pix_transactions (
id UUID PRIMARY KEY,
occurred_at TIMESTAMP NOT NULL,
year SMALLINT NOT NULL,
month SMALLINT NOT NULL,
amount NUMERIC(18, 2) NOT NULL,
settlement_type VARCHAR(16) NOT NULL, -- INTERNAL / SPI
scheduled BOOLEAN NOT NULL DEFAULT FALSE,
suspected_fraud BOOLEAN NOT NULL DEFAULT FALSE,
not_settled_in_time BOOLEAN NOT NULL DEFAULT FALSE,
rejected BOOLEAN NOT NULL DEFAULT FALSE,
rejection_reason VARCHAR(8),
initiation_procedure SMALLINT NOT NULL, -- 1=Manual, 2=Pre-stored
initiation_mechanism SMALLINT NOT NULL, -- 1=Key, 2=Dynamic QR, 3=Static QR, 4=Initiator
payer_nature SMALLINT NOT NULL, -- 1=Natural, 2=Legal
receiver_nature SMALLINT NOT NULL, -- 1=Natural, 2=Legal
initiation_channel SMALLINT NOT NULL, -- 1=App, 2=Web, 3=Call, 4=ATM, 5=Branch
initiator_ispb VARCHAR(8),
created_at TIMESTAMP NOT NULL DEFAULT NOW()
);
```
The `settlement_type` column distinguishes internally settled transactions (both parties at the same institution) from interbank transactions settled via SPI. This distinction matters because some dimensions only apply to internal settlements.
### Required capabilities
* [ ] Store transaction data for at least 12 months prior to any request
* [ ] Query by any single dimension or combination of dimensions
* [ ] Aggregate count and financial amount over arbitrary periods
* [ ] Export to multiple formats (CSV, XML, JSON) as BACEN may specify any
* [ ] Generate cross-dimensional reports efficiently
## Regulatory references
***
### Normatives
| Document | Description |
| ------------------------ | ------------------------------------------------- |
| IN BCB nº 32/2020 | Main normative establishing APIX 001 and APIX 002 |
| IN BCB nº 174/2021 | Updates to Annexes I and III of IN 32 |
| IN BCB nº 126/2021 | Earlier updates to IN 32 |
| IN BCB nº 383/2023 | Updates effective from 2024-02-01 |
| Resolution BCB nº 1/2020 | Pix regulation (arts. 38, 39, and 99) |
### Supporting documents
| Document | Description |
| --------------------------- | ------------------------------------------------------- |
| APIX 002 instructions (PDF) | Guidance on preparing and submitting on-demand requests |
| Pix Time Manual | Reference for Pix time limits |
| BACEN submission portal | Instructions and XSD for APIX 001 |
| STA system | File Transfer System access |
| STA instructions | How to use the system |
| Sisbacen / Autran | Transaction lookup |
### BACEN contacts
| Topic | Email |
| ------------------- | ----------------------------------------------------------------- |
| Submission delivery | [suporte.ti@bcb.gov.br](mailto:suporte.ti@bcb.gov.br) |
| Document content | [estatisticas.spb@bcb.gov.br](mailto:estatisticas.spb@bcb.gov.br) |
This page is based on regulation in force as of January 2026. Always check the latest BACEN publications for current requirements.
Unlike APIX 001 which can be fully automated with a Reporter template, APIX 002 requires manual intervention — you must wait for BACEN's specific request, understand the format they define, and build the extraction accordingly. Reporter can help generate the output file, but the template must be created per request.