Circular RUNOR 1-1922 R.I. – Card Payment Acquirers

"Year of the Reconstruction of the Argentine Nation" COMMUNICATION "A" 8326 12/09/2025 CARD PAYMENT ACQUIRERS: Ref.: Circular RUNOR 1-1922 R.I. – Card Payment Acquirers.

---

We address you regarding the provisions disseminated in Communication A 8310 related to the reporting regime referenced herein. In this regard, we provide you with the attached ordered text of Section 81 of “Submission of Information to the Central Bank”, which contains the respective operational instructions. We extend our cordial greetings. CENTRAL BANK OF THE ARGENTINE REPUBLIC Mariana A. Diaz (Manager of the Reporting Regime) Estela M. del Pino Suárez (Deputy General Manager of the Reporting Regime and Financial Services User Protection) Functional Position ANNEX

81.1. General Instructions. The information to be submitted monthly shall be recorded in two variable-length files containing the data according to the record designs inserted in point 81.4., taking into account what is provided in point 1.2.3.1 of Section 1 of “Submission of Information to the Central Bank”. The submission shall be carried out through the "MFT File Transfer Service", according to the instructions in point 1.2.2 of the aforementioned regulation. The results of the validation processes will be available as provided in point 1.2.4 of the aforementioned regulation. For the identification of this regime, code 112 shall be used for the regime code, and for the requirement code, the following table shall be considered:

File Name	Requirement Code	Frequency
OPADQUIRENCIA.TXT	1	Monthly
STOCKTPV.TXT	2	Monthly

81.2. Particular Instructions for the “OPADQUIRENCIA.TXT” file. Movements shall be reported by totaling the fields “Total number of operations” and “Total amount in original currency”, covering the month's operations as reached under Section II – Particular Instructions of the NP, Section A. It is highlighted that this requirement will not allow the “OPERA=FALSE” option in the “DETALLE.XML” file. The field “Card issuer entity CUIT” shall be integrated only in operations where the “Card issuance place” field has been integrated with code 201. For the remaining operations, it shall be integrated with a null value (“;;”). The field “PSP registration code of the interoperable wallet in BCRA” shall be integrated only in operations with QR code reading. For the remaining operations, it shall be integrated with a null value (“;;”). The field “Sub-acquirer/aggregator CUIT” shall be integrated only when sub-acquirers/aggregators participate in the operation. For the remaining operations, it shall be integrated with a null value (“;;”).

81.3. Particular Instructions for the “STOCKTPV.TXT” file. The data shall be reported by totaling the number of POS terminals (TPV) for the month under report, according to Section II – Particular Instructions of the NP, Section B. Record(s) with the “POS Usage” code and a “Number of POS terminals” field different from zero (0) shall be saved. In case of not having data to report for any of the “POS Usage” codes, the option “OPERA=FALSE” must be selected in the “DETALLE.XML” file and the file shall not be saved.

B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK Section 81. Card Payment Acquirers. Version: 1st COMMUNICATION "A" 8326 Validity: 01/12/2025 Page 1

B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK Section 81. Card Payment Acquirers. Version: 1st COMMUNICATION "A" 8326 Validity: 01/12/2025 Page 2

B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK Section 81. Card Payment Acquirers. Designation: “OPADQUIRENCIA.TXT” Sheet 1 of 1

No.	Field Name	Type	Max Length (1)	Observations
1	Payment Instrument	Numeric	3	According to Table 1 of the NP.
2	Payment Scheme	Numeric	5	According to Table 2 of the NP.
3	Card Issuance Place	Numeric	3	According to Table 3 of the NP.
4	Card Issuer Entity CUIT	Numeric	11	Issuer entity CUIT, according to point 5 of Section A of the NP.
5	Initiation Method / Access Channel	Numeric	3	According to Table 4 of the NP.
6	Payment Modality	Numeric	3	According to Table 5 of the NP.
7	Business Sector	Numeric	5	According to Table 6 of the NP.
8	PSP Registration Code of the Interoperable Wallet in BCRA	Numeric	5	According to point 8 of Section A of the NP.
9	Sub-Acquirer/Aggregator CUIT	Numeric	11	According to point 1 of Section A of the NP.
10	Original Currency	Numeric	3	SWIFT Code, according to point 11 of Section A of the NP.
11	Total Number of Operations	Numeric	11	In whole units.
12	Total Amount in Original Currency	Numeric	15	In thousands, without decimals.
(1) The delimiter “;” shall be used as a field separator.
Version: 1st COMMUNICATION "A" 8326 Validity:
01/12/2025 Page 3

B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK Section 81. Card Payment Acquirers. Version: 1st COMMUNICATION "A" 8326 Validity: 01/12/2025 Page 4 Designation: “STOCKTPV.TXT” Sheet 1 of 1

No.	Field Name	Type	Max Length (1)	Observations
1	POS Usage	Numeric	3	According to Table 7 of the NP.
2	Number of POS Terminals	Numeric	11	In whole units.
(1) The delimiter “;” shall be used as a field separator.

81.4. Record Design. B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK Section 81. Card Payment Acquirers. Version: 1st COMMUNICATION "A" 8326 Validity: 01/12/2025 Page 5

B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK Section 81. Card Payment Acquirers. Version: 1st COMMUNICATION "A" 8326 Validity: 01/12/2025 Page 6

Code	Legend	Cause
01	FILE “OPADQUIRENCIA.TXT” AND/OR “STOCKTPV.TXT” NOT FOUND	- The file “OPADQUIRENCIA.TXT” and/or “STOCKTPV.TXT” was omitted from saving, or the reported file does not correspond to the record design, or

• “OPERA=FALSE” was declared in the “DETALLE.XML” file for the “OPADQUIRENCIA.TXT” file. | | 02 | SUBJECT CODE INCORRECTLY REPORTED | The subject code does not correspond to one authorized for this regime. | | 03 | REPORTING DATE INCORRECT OR ADVANCED | - Information corresponding to a non-existent date was submitted, or
• A period was reported with the previous one not found to be valid. | | 04 | INFORMATION ALREADY SUBMITTED AND ACCEPTED | Information corresponding to a validated period was submitted. | | 05 | CORRECTIVE INFORMATION INCORRECTLY REPORTED | Corrective information corresponding to a non-validated period was submitted. | B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK Section 81. Card Payment Acquirers. Version: 1st COMMUNICATION "A" 8326 Validity: 01/12/2025 Page 7

B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK Section 81. Card Payment Acquirers. Version: 1st COMMUNICATION "A" 8326 Validity: 01/12/2025 Page 8

Code	Legend	Cause
06	FORMAT ERROR – RECORD XXX	- The file(s) “XXXXX.TXT” do not respect the instructions provided in point 81.1 of these instructions.

• The detailed fields were not saved according to the record design in point 81.4, as follows: Design | Field | Admitted Value “OPADQUIRENCIA.TXT” | 1, 2, 3, 5, 6 and 7 | Codes admitted according to NP Tables. 11 and 12 | Numeric values: - Does not admit zero (0) - Does not admit negative sign “-” “STOCKTPV.TXT” | 1 | Codes admitted according to Table 7 of the NP. 2 | Numeric values: - Does not admit zero (0) - Does not admit negative sign “-” | B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK Section 81. Card Payment Acquirers. Version: 1st COMMUNICATION "A" 8326 Validity: 01/12/2025 Page 9 | Code | Legend | Cause | |---|---|---| | 07 | INCORRECTLY REPORTED CUIT (APPLICABLE TO “OPADQUIRENCIA.TXT” FILE) | The reported identification number does not correspond to a valid Unique Taxpayer Identification Key (CUIT). | | 08 | INCORRECTLY REPORTED BCRA REGISTRATION CODE (APPLICABLE TO “OPADQUIRENCIA.TXT” FILE) | The code reported in the field “PSP registration code of the interoperable wallet in BCRA” does not correspond to a valid wallet code. | | 09 | DUPLICATED NOVELTY (DUPLICATE RECORD) | “OPADQUIRENCIA.TXT” file: More than one record with the identical combination of fields 1 to 10 was reported. “STOCKTPV.TXT” file: More than one record for the same POS Usage code (Table 7 of the NP) was reported. | | 10 | INCORRECTLY REPORTED ORIGINAL CURRENCY | The code reported in the “Original currency code” field does not match any of the enabled SWIFT Currency Codes. | | 11 | INCONSISTENCY BETWEEN FIELDS CARD ISSUANCE PLACE AND CARD ISSUER ENTITY CUIT | - Having reported code 201 in the “Card Issuance Place” field, the “Card Issuer Entity CUIT” field was not integrated, or
• Having reported code 202 in the “Card Issuance Place” field, the “Card Issuer Entity CUIT” field was not integrated with a null value (;;). | | 12 | INCONSISTENCY BETWEEN FIELDS PAYMENT INSTRUMENT AND PAYMENT MODALITY | Having reported code 102 in the “Payment Instrument” field, the “Payment Modality” field was integrated with a code different from 401. |