External Regulatory Circular DSP-465 of August 6, 2026, Subject 18: Interoperability of Immediate Low-Value Payment Systems

Board Bulletin of the Bank of the Republic

Number: 20 Date: August 6, 2026 Pages: 3 Content • External Regulatory Circular DSP-465 of August 6, 2026 Subject 18: Interoperability of Immediate Low-Value Payment Systems.

This bulletin is published in development of what is provided in letter a) of article 51 of Law 31 of 1992 and the paragraph of article 108 of Law 510 of 1999. Board Secretariat – Carrera 7 14 78, sixth floor – Bogotá, D. C. – Telephone: +57 (601) 484-9980

Document No: OT/PF/AUG/2026/148649 Page 18 - 00 Recipients: Entities Administering Low-Value Payment Systems that process payment order and/or immediate fund transfer services, Superintendency of Finance of Colombia and Superintendency of the Solidarity Economy.

Subject 18: Interoperability of Immediate Low-Value Payment Systems.

Pages 18-A5-15 and 18-A5-16 of Annex 5 of External Regulatory Circular DSP-465 of March 31, 2026, corresponding to Subject 18: INTEROPERABILITY OF IMMEDIATE LOW-VALUE PAYMENT SYSTEMS, are replaced, with the aim to: • Clarify in letter b) of item 2.2.3. of Annex 5 that the Bank of the Republic is the one that will inform of the unavailability of Participants and/or SPBVI through error codes in messaging or other communications. • Establish that Participants must comply with the obligations of item 2.2.3. of Annex 5 according to the schedule defined by the Bank of the Republic and presented in the Immediate Payments Interoperability Committee, without prejudice to the fact that they may comply with these obligations earlier than planned and from the publication of this Circular.

This Circular takes effect from its publication.

Cordially,

MARCELA OCAMPO Executive Manager

DIONISIO VALDIVIESO BURBANO Deputy Manager of Payment Systems and Banking Operation

EXTERNAL REGULATORY CIRCULAR DSP-465 DEPARTMENT MANUAL PAYMENT SYSTEMS Date: Thursday, August 6, 2026

Document No: OT/PF/AUG/2026/148649 Page 18-A5-15 EXTERNAL REGULATORY CIRCULAR DSP-465 Date: Thursday, August 6, 2026 Subject 18: Interoperability of Immediate Low-Value Payment Systems. and DSP-471 Services Subject 20: Regulation of the Operational Mechanism for Liquidation (MOL), or those that modify or replace them.

Only for non-standardized error events, the SPBVI Administrators (EASPBVI) and their Participants may add proprietary error codes in the messaging. The proprietary error codes of the EASPBVI must be reported by these to the Bank of the Republic according to the guidelines established in the External Operational and Services Circular DSP-471 Subject 20: Regulation of the Operational Mechanism for Liquidation (MOL), or those that modify or replace them.

2.2. Terms and conditions for notifications of failure events to Clients The EASPBVI must require their Participants to comply with the following terms and conditions for notifications to Clients of events by which the processing of a PO/TF does not end successfully:

2.2.1. Failure event notifications must be sent to Clients immediately, whether they originate directly from the Participant or are transmitted from the EASPBVI.

2.2.2. Failure event notifications to Clients must indicate, at a minimum, that the operation could not be processed. Participants may include the error code that identifies the event. When such a code is included, it must also incorporate, a basic description of the event in the notification to the Client.

2.2.3. When a Participant or an SPBVI presents an unavailability that does not allow the processing of Immediate PO/TF, the following guidelines must be followed: a) The Participant presenting the unavailability must inform its Clients, at a minimum, that due to its own unavailability it cannot process Immediate PO/TF as Originator Participant and as Receiver Participant. The foregoing, without prejudice to compliance with requirements or standards in matters of Client information, according to applicable regulations. b) Participants other than the one (those) that present(s) unavailability must inform their Clients, at a minimum, that Immediate PO/TF cannot be processed due to the unavailability of the Participant and/or the respective SPBVI, which has been reported by the Bank of the Republic through error codes in messaging or other communications. Participants may indicate

Document No: OT/PF/AUG/2026/148649 Page 18-A5-16 EXTERNAL REGULATORY CIRCULAR DSP-465 Date: Thursday, August 6, 2026 Subject 18: Interoperability of Immediate Low-Value Payment Systems.

in the message to the Client the name of the Participant and/or SPBVI that presents the unavailability.

Participants must comply with what is provided in this item according to the schedule defined by the Bank of the Republic and presented in the Immediate Payments Interoperability Committee or, in advance, as soon as possible from August 6, 2026.

2.2.4. Initial errors that may occur when the Originator Participant applies its validations to authorize an instruction of an Immediate PO/TF and before generating its routing to the Originator SPBVI, must be managed by said Participant according to its typologies, codes, internal parametrizations and messages to Clients.

2.2.5. Participants will have discretion to convert the error code received from an SPBVI, from the MOL, or from the DICE, with the purpose of communicating such errors to their Clients.

2.2.6. For exception flows due to errors subsequent to the acceptance of the Immediate PO/TF, the notification message to the Client must indicate as a minimum, that the transaction has been processed and the estimated time to complete the transaction. The Client must always be updated regarding the status of the operation.

2.2.7. Once the failure has been overcome, Participants must notify their Client using the different communication channels available to them in order to inform them that the failure has been overcome and that the operation has ended, adding the parameters stipulated in item 6 of section 6.1. of this Circular.

2.3. Terms and conditions for the operational reconciliation process

2.3.1. The cycles in which accounting closings and/or operational reconciliation processes are executed cannot affect the availability of immediate payment services.

2.3.2. Procedures associated with operational reconciliation must be enabled for Participants by the EASPBVI through consultation mechanisms that allow, at a minimum, filters for date and time ranges and cuts. The EASPBVI must indicate the procedure to perform the connection or access to said mechanisms.