Rule · BANREP · 20 Nov 2026
Entities Administering Immediate Low-Value Payment Systems (EASPBVI) processing Intra-SPBVI and Inter-SPBVI Operations must comply with this Circular's technical and operational processes. Immediate Payment Orders and/or Funds Transfers using one debit Payment Instrument, initiated by Key or QR Code, processed within twenty (20) seconds and not exceeding one thousand (1.000) UVB, must go through DICE and MOL; higher-value orders may not use these modules, the Resolución Externa No. 6 de 2023 Keys, or the Bre-B seal. EASPBVI must maintain 99,8-% minimum monthly Federated Directory availability, enforce Key and QR Code rules, and report via Annex 4 messages.
Bulletin of the Board of Directors of the Banco de la República
Number: 29
Date: 20 November 2026
Pages: 101
Content
[*] This bulletin is published in accordance with the provisions of literal a) of article 51 of Law 31 of 1992 and the paragraph of article 108 of Law 510 of 1999.
Secretary Board of Directors – Carrera 7 14 78, sixth floor – Bogotá, D. C. – Telephones: +57 (601) 484-9980
PAYMENT SYSTEMS DEPARTMENT MANUAL
Date: Friday, 20 November 2026
Addressees: Entities Administering Low-Value Payment Systems that process immediate payment order and/or fund transfer services, Financial Superintendence of Colombia and Superintendence of the Solidarity Economy.
External Regulatory Circular DSP-465 of 15 May 2025, of 3 September 2025, of 6 March 2026, of 31 March 2026 and of 6 August 2026, corresponding to Subject 18: INTEROPERABILITY OF IMMEDIATE LOW-VALUE PAYMENT SYSTEMS, is replaced in its entirety.
The changes are made, mainly, to:
Update the classifications of Immediate Payment Orders and/or Fund Transfers and include the definition of payment to legal persons.
Include the definition of "Certification", "Payment Reference" and "Value-Added Services".
Include the field "Beneficiary Customer", which indicates the category of the Customer receiving the funds subject to each Immediate Payment Order and/or Fund Transfer.
Include the field "Trade Name of the legal person Customer", which indicates the trade name of the legal person Customer that has this information.
Include rules for the security of the data obtained in the Key Resolution and for the blocking of Keys in fraud events.
Include rules regarding service availability and the certification process of the SPBVI.
Update Annex 2 "Clearing and Settlement Processes".
Modify Annex 3 "Customer Experience" to include the guidelines for the Customer experience of legal persons and the functionality of "Payment Reference".
Update Annex 5 "Operational and Messaging Standards for the Processing of Immediate Payment Orders and/or Fund Transfers (OP/TF)".
Modify Annex 6 "Manual for the use of the seal/mark" to include additional rules on the use of the Bre-B seal/mark.
Modify Annex 7 "Transitional Measures" to include new transition rules.
PAYMENT SYSTEMS DEPARTMENT MANUAL
Date: Friday, 20 November 2026
Addressees: Entities Administering Low-Value Payment Systems that process immediate payment order and/or fund transfer services, Financial Superintendence of Colombia and Superintendence of the Solidarity Economy.
This Circular is effective from its publication.
Cordially,
MARCELA OCAMPO
Executive Manager
DIONISIO VALDIVIESO BURBANO
Deputy Manager of Payment Systems and
Banking Operation
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
This Circular regulates External Resolution No. 6 of 31 October 2023 issued by the Board of Directors of the Banco de la República (JDBR) on the interoperability of low-value payment systems that provide services related to Immediate Payment Orders and/or Fund Transfers.
The Circular shall be mandatory for the Entities Administering Immediate Low-Value Payment Systems (EASPBVI) that process Intra-SPBVI and Inter-SPBVI Operations.
The terms that appear in uppercase in this Circular, regardless of whether they are expressed in singular or plural, have the meaning attributed to them in External Resolution No. 6 of 2023 and in this Circular.
a. Acquirer: These are the agents defined in numeral 2 of article 2.17.1.1.1. of Single Regulatory Decree 2555 of 2010 and article 2.11.14.3. of Decree 1068 of 2015, or the norms that replace, modify or regulate them.
b. Certification: Process by which the Banco de la República confirms that an EASPBVI, or an EASPBVI confirms that a Participant, complies with the requirements and technical specifications defined for the Key Resolution and management processes, the processing of Immediate Payment Orders and/or Fund Transfers, as well as the other requirements and technical specifications to guarantee Interoperability.
c. Timestamp: Date and time information that the EASPBVI and the Participants must include in the messages required to carry out, among others, the Key management and Resolution processes, and the Clearing and Settlement of Immediate Payment Orders and/or Fund Transfers.
d. Immediate Payment Orders and/or Fund Transfers: Instruction given in the SPBVI by a Payer on any day and time to debit funds from its Payment Method and credit them to the Payment Method of a Beneficiary in real time, in accordance with the provisions of numeral 3 of this Circular.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
e. Payment Service Provider: These are the agents defined in numeral 20 of article 2.17.1.1.1. of Single Regulatory Decree 2555 of 2010, or the norms that replace or modify it.
f. Time-Out: Maximum time to complete or decline the process.
g. Payment Reference: Numeric or alphanumeric code(s) associated with an Immediate Payment Order and/or Funds Transfer, which allows identifying the good, service or concept associated with it. It may be used for any of the classifications established in numeral 3.3 of this Circular.
h. Value-Added Services: Complementary functionalities that may be implemented by the EASPBVI or their Participants, in order to facilitate, complement or improve the initiation or completion of Immediate Payment Orders and/or Funds Transfers, for any of the classifications established in numeral 3.3 of this Circular, without modifying the technical and operational processes defined by the Banco de la República for their processing.
The EASPBVI must comply with the technical and operational processes indicated in this Circular to process Immediate Payment Orders and/or Funds Transfers. In the regulations of the Immediate Low-Value Payment Systems (SPBVI), the EASPBVI must require that Participants comply with these provisions, for which they may perform one or several of their functions through Payment Service Providers under the same terms established in Decreto Único Reglamentario 2555 de 2010 or the rules that replace or modify it.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
Immediate Payment Orders and/or Funds Transfers that comply with the following characteristics must be processed through the Centralized Directory (DICE) and the Operational Settlement Mechanism (MOL):
a. Only one Payment Instrument is used to debit and one or several Payment Instruments to credit the funds.
b. It is initiated by entering a Key or the reading and/or use of a QR Code.
c. It is initiated by the Payer on any day and at any time.
d. It is processed within a maximum period of twenty (20) seconds. The parameters for compliance with this provision are detailed in Annex 5 of this Circular.
e. Its maximum value does not exceed that established in numeral 3.2 of this Circular.
Immediate Payment Orders and/or Funds Transfers that exceed the maximum value referred to in subparagraph e. of this numeral may not be processed through the centralized modules administered by the Banco de la República (BR), DICE and MOL. Nor may they use the Keys referred to in subparagraph l. of article 2 of Resolución Externa No. 6 de 2023, nor the Bre-B seal/mark referred to in Annex 6 of this Circular.
Immediate Payment Orders and/or Funds Transfers in which the Payer and the Beneficiary are Clients of the same Participant and that comply with the characteristics described in the first paragraph of this numeral may be processed through DICE and MOL when the Participant so determines.
The maximum value of each Immediate Payment Order and/or Funds Transfer shall be equivalent in current legal currency to one thousand (1.000) Basic Value Units – UVB.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
Participants may define a maximum value lower than that indicated above or other types of limits, for example, number of transactions originated per day, exclusively to originate an Immediate Payment Order and/or Funds Transfer and provided that such limits respond to their risk management policies. The Participant must inform its Clients, clearly and visibly, at the time of origination of the Immediate Payment Order and/or Funds Transfer, that such limit has been established by said Participant. Participants may also allow the configuration of limits by Clients, for example, by value or number of transactions.
The limits referred to in the preceding paragraph may not be different from those that the Participant establishes for payment orders or funds transfers made between its Clients or between its Clients and the Clients of other issuers of Payment Instruments.
In accordance with article 8 of Resolución Externa No. 6 de 2023 of the JDBR, Immediate Payment Orders and/or Funds Transfers are classified as follows:
a. Payment to Natural Person: Immediate Payment Order and/or Funds Transfer in which the Beneficiary is a natural person who may or may not have the status of merchant.
b. Payment to Legal Person: Immediate Payment Order and/or Funds Transfer in which the Beneficiary is a legal person who may or may not have the status of merchant. Legal persons may be of a public or private nature.
The Payers of Immediate Payment Orders and/or Funds Transfers are natural persons and legal persons of a public or private nature.
For the incorporation of other classifications of Immediate Payment Orders and/or Funds Transfers, the BR may take into account the recommendations of the Committee for Interoperability of Immediate Payments.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
The Access Technologies that allow initiating Immediate Payment Orders and/or Fund Transfers for the classification provided in numeral 3.3. of this Circular are the Keys and the QR Codes. For the use of Access Technologies by Customers, Participants may integrate additional technologies compatible with the rules and standards applicable to Access Technologies and to the processing of Immediate Payment Orders and/or Fund Transfers set forth in this Circular.
The EASPBVI shall require their Participants that the management of the Keys be subject to the following rules:
a. A Payment Method may be associated with several Keys.
b. A Key shall be associated with a single Payment Method.
c. A Key associated with a Payment Method may not be repeated in a Federated Directory.
d. A Key may not be repeated in the Centralized Directory.
e. The Participant shall define for each Key the SPBVI through which it will perform synchronization for the Key management processes with the Centralized Directory. The SPBVI shall define the operational or technological mechanism for Participants to indicate the Federated Directory selected to synchronize the information with the Centralized Directory.
f. Participants linked to more than one SPBVI that use in said systems the same classification of Immediate Payment Orders and/or Fund Transfers as provided in numeral 3.3. of this Circular may register in the Federated Directories of each of said SPBVI all or some of the Keys of the shared classification.
Participants that decide to register the same Key in the Federated Directories of each of said SPBVI shall guarantee that the updating of the information derived from the Key management processes is first performed in the Federated Directory of the SPBVI chosen to synchronize with the Centralized Directory. Once the Participant has a response
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
positive from said Federated Directory, it shall update the information immediately in the Federated Directories of the other applicable SPBVI.
g. Customers may not edit or customize the content of the Key.
h. When a Customer updates any of its data and said data is being used as a Key, the Participant shall require it to perform the Key modification process.
The EASPBVI shall ensure compliance with these rules.
The types of Keys for initiating Immediate Payment Orders and/or Fund Transfers are the following:
a. Identity document number: Refers to any of the following identification numbers of the Customer registered in the onboarding process with the Participant at which the Customer has its Payment Method: citizenship card, foreigner card, Unique Personal Identification Number (NUIP), identity card, Tax Identification Number (NIT) or passport.
b. Mobile phone number: Refers to the national mobile phone number(s) of the Customer registered with the Participant at which it has its Payment Method.
c. Email address: Refers to the email address(es) of the Customer registered with the Participant at which it has its Payment Method.
d. Alphanumeric: Refers to the Key(s) generated by the Participant where the Customer has its Payment Method, which begin(s) with the @ symbol, followed by a combination of numbers and/or letters. For the generation of this/these Key(s), the Participant shall use characteristic information of the Customer, so that it/they are easy to remember. Examples of alphanumeric Keys are the following: @3191234567, @AP1234567 and @MargaritaP
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
e. Merchant establishment code: Refers to the identification code(s) assigned by the Acquirer(s) to the merchant establishment. Merchant establishments may have multiple codes assigned by one or several Acquirers. The assignment of the Merchant establishment code by the Acquirer shall follow the structure for this type of Key provided in Table 1 of this Circular.
The SPBVI shall define procedures for changing Acquirer, whether or not retaining the Key. In the case of a change of Acquirer retaining the Key, the Key cancellation and registration process shall be performed in accordance with the provisions of Annex 1 of this Circular. These procedures may not have a duration exceeding twenty-four (24) hours.
Keys that incorporate letters shall not distinguish between uppercase and lowercase.
The options of types of Keys offered to Customers that are natural persons or legal persons that do not have the status of merchant shall be: the identity document, the mobile phone number, the email address and alphanumeric.
The options of types of Keys offered to Customers that are natural or legal persons that have the status of merchant shall be: the identity document, the mobile phone number, the email address, the alphanumeric and the merchant establishment code.
The Participant may limit the number of Keys that may be associated with a Payment Method or a Customer based on, among others, security criteria.
The EASPBVI may only incorporate in their Federated Directories the information on the Keys taking into account the following structure:
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
Table 1. Structure of the Keys to initiate Immediate Payment Orders and/or Fund Transfers
| Type | Key | Number and type of characters | Observations |
|---|---|---|---|
| Identity Document | XXXXXXXXXX Identity document number | Maximum 18 alphanumeric characters | Citizenship card, foreigner ID card, identity card, NUIP, NIT, or Passport used to open the Payment Method. It cannot include hyphens, spaces or periods. |
| National mobile phone number | XXXXXXXXXX National mobile phone number | 10 numeric characters | Does not include country code and always starts with the number 3. It cannot include spaces. |
| Email address | xxxxxxxxxxxxxxxx@xxxx.xxx.xx xxxxxxxxxxxxxxxx@xxxx.xxx | Up to a maximum of 30 characters before the @ symbol and 61 characters after. | It has an @ symbol just before the domain. |
| Alphanumeric | @xxxxxxxxxxxxxxxxxxx | Minimum 5 and maximum 20 alphanumeric characters after the @ symbol | Starts with the @ symbol, followed by a combination of letters and/or numbers. The @ symbol is only used at the beginning of the Key. The alphanumeric Key is generated by the Participant where the Customer has their Payment Method. It cannot include spaces, accents or the character ñ. |
| Code assigned to the commercial establishment | XXXXXXXXXXXXXX | 10 numeric characters | Identification code of the commercial establishment assigned by the Acquirer. It starts with double zero (00). The following 8 digits may be numbers between 0 and 9. It cannot include spaces. |
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
The EASPBVI must incorporate in their regulations the obligation of Participants to adapt the Service Provision Channels arranged to carry out all the Key management processes described below, following the guidelines of each process established in Annex 1 of this Circular.
a. Registration: Operation carried out by the Customer to choose the Key(s) and associate it/them with their Payment Method, after authentication of the Customer in the terms defined by the Participant and authorization for the processing of their personal data.
This process must be executed even when the national mobile phone number is used as the Payment Method number.
The registration of Keys must be carried out directly and exclusively by the Customer, except in the following cases:
1. Alphanumeric Key registration: From the start of the MOL operation, Participants may assign an alphanumeric Key to the Payment Methods of their Customers who are natural persons not merchants and register said Key in the Federated Directories, when any of the following cases occurs:
i. The Participant creates a new Payment Method for the respective Customer or activates a Payment Method that was inactive.
ii. The Participant links for the first time to an SPBVI, without having been previously linked to another SPBVI(s).
The assignment of the alphanumeric Key may only be made for active Payment Methods and the registration of said Keys in the Federated Directories and the Centralized Directory must comply with the operational guidelines defined by the BR.
For the purposes of this provision, a Payment Method is considered active when any operation has been carried out on it during a period of six (6) consecutive months. Operation is understood as provided in numeral 1.2.2. of Chapter III, Title I, Part II of the Basic Legal Circular of the Financial Superintendence of Colombia.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
2. Registration of the Key type commercial establishment code: Participants who, by virtue of the acquiring relationship, assign commercial establishment codes to their Customers who are natural or legal persons that have the status of merchants, may register said code(s) as Key(s) in the Federated Directories.
b. Modification: Operation carried out by the Customer to modify their registered Key(s) for another Key(s) of the same type or another type, and/or the Payment Method associated with it/them for another Payment Method of the Participant where the Key is registered.
c. Cancellation: Operation carried out by the Customer to cancel the registration of the registered Key(s).
d. Portability: Operation carried out by the Customer to transfer their Key(s) and associate it/them with another Payment Method at a different Participant.
e. Blocking: Operation carried out by the Customer to temporarily suspend the use of the Key(s).
f. Reactivation: Operation carried out by the Customer to activate the use of a previously blocked Key.
g. Inquiry: Operation carried out by the Customer to know the Key(s) they have registered with the Participant from which the Inquiry is made.
The Participant must enable the execution of Immediate Payment Orders and/or Fund Transfers within a maximum period of two (2) hours from the moment the Customer has received the successful process message of the registration, modification, portability, or reactivation of the Key. The information derived from the processes described above must be included and updated in the Federated Directory administered by the EASPBVI and in the Centralized Directory in real time.
a. The EASPBVI must include in their Regulations that Participants must block their Customers' Keys when:
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
i. Identify fraud and impersonation events or risks in accordance with their administration and risk management systems.
ii. Receive the blocking request from the Client holding the Key when the Client cannot manage the blocking directly in the Bre-B Zone.
iii. It is required in accordance with the guidelines defined by the BR for the management of security events in Bre-B.
b. The EASPBVI must include in their Regulations that Participants may block their Clients' Keys when:
i. The Payment Method associated with the Key(s) is classified as inactive, in accordance with the applicable regulatory provisions.
ii. The Payment Method associated with the Key(s) is blocked.
iii. Identify an event or risk other than those referred to in numeral i. of literal a., in accordance with their administration and risk management systems.
For literals a. and b., Participants must evaluate the permanence of the Key blocking and its reactivation in accordance with their policies and procedures.
c. The EASPBVI must include in their Regulations that Participants may cancel their Clients' Keys exclusively when:
i. The Client's Payment Method associated with the Key(s) is cancelled.
ii. Receive information about the death or liquidation of the holder of the Payment Method.
iii. It is identified that the inactivity of the Payment Method referred to in numeral i. of literal b. persists for six (6) additional consecutive months. In this case, the Participant must inform the Client and the EASPBVI.
For literals a., b. and c., Participants must inform the EASPBVI about the event so that it performs the blocking, reactivation or cancellation of the Key(s) in the Federated Directory. Once the EASPBVI are notified, they must inform the Centralized Directory in real time so that it performs the corresponding update. Likewise, Participants must notify the Client about the blocking, reactivation or cancellation of the Key(s).
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
The EASPBVI must have the necessary mechanisms that allow the processing of Immediate Payment Orders and/or Fund Transfers through the Keys and incorporate in their regulation the obligation of Participants to adapt the Service Provision Channels arranged to initiate these operations, using the Keys. The EASPBVI must require in their regulations compliance with the following obligations by Participants:
a. Inform their Clients about the characteristics and uses of the Keys, as well as the terms and conditions of the management processes.
b. Send the information of the Key management processes to the EASPBVI in real time.
c. Comply with the rules related to data protection and habeas data, in particular, Law 1581 of 2012, Decree 1074 of 2015 and other rules that modify, replace, add to or regulate it, including the authorization of their Clients that allows the processing of personal data related to the Keys.
d. Follow the activities defined in Annex 1 of this Circular for the Key management processes.
e. Adopt the necessary actions so that the Clients' data obtained through the Key Resolution process is not accessed by unauthorized third parties or by technological automations developed by them. For this purpose, Participants, among others, must: i) show the Client only the fields described in literal e. of numeral 6 of this Circular, ii) refrain from storing information other than that described in literal e. of numeral 6 of this Circular in any technological component of the Service Provision Channels enabled to initiate the Immediate Payment Order and/or Fund Transfer, and iii) implement controls to mitigate the risks that may affect the security of information in transit and at rest.
The EASPBVI will require their Participants to implement the functionality of generation, reading and/or use of static and dynamic QR Codes to initiate Immediate Payment Orders and/or Fund Transfers, as indicated in numeral 3.4.7 of this Circular.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
The regulation of the SPBVI must incorporate the following conditions:
a. The QR Codes used to initiate Immediate Payment Orders and/or Fund Transfers must comply with the technical standards indicated in the Basic Legal Circular issued by the Financial Superintendence of Colombia.
b. Allow the Client to choose the Key that will be incorporated in the fields of the QR Codes to associate it with their Payment Method.
The EASPBVI must have the necessary mechanisms that allow the processing of Immediate Payment Orders and/or Fund Transfers through the QR Codes. Likewise, they must incorporate in their regulation the obligation of Participants to adapt the Channels arranged to initiate these operations using the QR Codes, as established below:
a. Allow the reading and/or use of static and dynamic QR Codes to initiate Immediate Payment Orders and/or Fund Transfers.
b. Generate QR Codes to receive the resources coming from Immediate Payment Orders and/or Fund Transfers, which may be static or dynamic.
c. Allow the incorporation in the QR Code of the Key selected by the Client and the information corresponding to the Payment Reference(s), when applicable.
EASPBVI shall require their Participants that, in the generation of QR Code representations for non-merchant natural persons, the Participant's Client may only include the value of the Payment Order and/or Immediate Funds Transfer and/or the Payment Reference when this applies.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Inmediatos.
SPBVI shall consult the Federated Directory for Key Resolution.
EASPBVI shall comply with the following obligations in relation to the administration of the Federated Directory:
a. Process the information following the structure indicated in this Circular.
b. Update the Federated Directory once they receive the information from a Key management process by a Participant in accordance with the provisions of Annex 1 of this Circular.
c. Employ a connection standard based on API-REST between their Participants and the Federated Directory. The messaging format to be used shall be implemented in accordance with the provisions of Annex 5 of this Circular.
d. Have the necessary technical and operational mechanisms to validate compliance with the rules related to the Keys defined in section 3.4.1. and the Key management processes defined in section 3.4.3. of this Circular.
e. Have continuity plans.
f. Process the personal data of Clients, under the terms set forth in Law 1581 of 2012 and other rules that amend, replace, supplement, or regulate it.
g. Require its Participants to have a personal data processing and protection policy and the authorization of its Clients that allows the processing of the personal data required for the interoperability of the SPBVI provided for in this Circular, under the terms set forth in Law 1581 of 2012, Decree 1074 of 2015 and other rules that modify, replace, supplement or regulate them.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Inmediatos.
h. Establish the operating procedure to be followed to receive the Keys of a Participant that joins the SPBVI and to remove the Keys of a Participant that leaves the SPBVI or that requests it.
i. Maintain a minimum monthly availability level of 99,8-%. The BR will indicate the guidelines for its calculation in the CEOS DSP-470 Subject 19: Regulation of the Centralized Directory (DICE) or those that modify or replace it.
The minimum information that the Federated Directories must include is the following:
a. Key Type and Key: As provided in section 3.4.2 of this Circular, the Keys may correspond to: identity document, mobile phone number, email address, alphanumeric, or the establishment code, as applicable.
The Keys must have the structure and number of fields described in Table No. 1 of this Circular.
In the case of the national mobile phone number in the structure of the Federated Directory, ten (10) fields must be enabled.
In the case of the identity document Key type, the Federated Directories and the Centralized Directory will not allow the registration of the same identity document number, even if the identification type is different.
b. Type of identification and number: The types of identification are classified as follows:
1. Citizenship Card (C.C.).
2. Foreigner ID Card (C.E.).
3. Unique Personal Identification Number (NUIP).
4. Identity Card (TDI).
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Inmediatos.
5. Temporary Protection Permit (PPT).
6. Número de Identificación Tributaria (NIT) without verification digit.
7. Special Stay Permit (PEP).
8. Passport Number (PAS).
The maximum number of alphanumeric characters for the types of identification shall be eighteen (18).
c. Type and names of the Client: In the case of natural persons, it corresponds to the names and surnames registered by the Client in the Participant in which it has its Payment Method. In the case of legal persons, it corresponds to the corporate name registered by them in the Participant in which it has its Payment Method. The names and surnames may have a maximum of forty (40) alphabetic characters each and in the case of the corporate name of the legal person the number of alphanumeric characters shall be a maximum of one hundred forty (140).
d. Identification of the Issuing Entity: It corresponds to the NIT without the verification number of the Participant in which the Client has the Payment Method or to the code assigned by the BR. The maximum number of characters for the NIT or code assigned by the BR shall be nine (9).
e. Payment Method and associated number: The Payment Methods are the following:
1. Cuentas de ahorro,
2. Cuentas corrientes,
3. Low-amount deposits,
4. Ordinary deposits, and
5. Inclusive low-amount deposits.
The maximum number of characters for the number associated with the Payment Method shall be thirty-four (34).
f. Immediate Low-Value Payment System Receiver: It corresponds to the assigned identification of the SPBVI that each Participant selects to receive the funds.
CIRCULAR REGLAMENTARIA EXTERNA DSP-465
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Inmediatos.
g. Date and time of the Key registration: Field that stores the date and time on which the Key registration is made in the Federated Directory under the structure defined for this field.
h. Date and time of Key management processes other than registration: Field that stores the date and time on which the last modification, suspension (due to blocking or portability) or reactivation of the Key is made in the Federated Directory under the structure defined for this field.
i. Type of Key status: Indicates the activity status of the Key, according to the specifications contained in Annex 5 of this Circular.
j. Beneficiary Customer: Indicates the category of the Customer receiving the funds subject to each Immediate Payment Order and/or Funds Transfer, in accordance with the following classification:
P (Person): Corresponds to a natural person who does not have the status of merchant.
C (Commerce): Corresponds to a natural or legal person who has the status of merchant.
E (Entity): Corresponds to a legal person who does not have the status of merchant.
G (Government): Corresponds to a legal person of a public nature.
k. Trade Name of the legal person Customer: Field that stores the trade name of the legal person Customer. If the Customer does not have a trade name, the field must not be filled in at the time of Key registration.
In the case of a Participant that does not offer Payment Methods and carries out the activity of merchant aggregation, this field must be used to store the name of its aggregated customer.
The Trade Name of the legal person Customer field may have a maximum number of one hundred forty (140) alphanumeric characters.
The Federated Directories must maintain, under the terms established in article 96 of the Organic Statute of the Financial System, a record of the modifications of the stored Keys, including those that have been cancelled.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Inmediatos.
For the assignment of the SPBVI identification mentioned in literal f., the provisions of the technical specifications defined by the BR must be followed.
Participants may update information in the Federated Directories as a result of updating their Customers' information in the following fields: Type of identification and number, Type and names of the Customer. They may also update the field Receiving Immediate Low-Value Payment System.
The following table shows the column structure that the Federated Directory must follow, with the information described in the preceding literals:
Table 2.
Information of the Federated Directory that will be reported to the Centralized Directory
When the Key is resolved in the Federated Directory and, in accordance with the “SPBVI Receptor” field, this SPBVI is different from the originating SPBVI that is performing the Key Resolution, the Immediate Payment Order and/or Funds Transfer will be processed as an Inter-SPBVI Operation, following the provisions of Annex 2 of this Circular.
When the Key Resolution is not carried out in the Federated Directory, it must be carried out in the Centralized Directory.
The Centralized Directory will be interconnected only with the Federated Directories and will contain exclusively the information supplied by the EASPBVI to the Centralized Directory, following
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Inmediatos.
the minimum structure of the Federated Directory. With respect to the Centralized Directory, the EASPBVI must:
a. Process the queries and claims submitted by Customers under the terms set forth in Law 1328 of 2009, Law 1480 of 2011, the Basic Legal Circular of the Financial Superintendence of Colombia, or in Law 1755 of 2015, and in accordance with the provisions of Law 1581 of 2012 and Decree 1074 of 2015, and other rules that modify, replace, add to or regulate them.
b. Use a connection standard based on API-REST between the Federated Directory and the Centralized Directory. The messaging format to be used must be implemented in accordance with the provisions of Annex 5 of this circular.
c. Have operational, technical and security rules and standards for the development of its operations and those of its Participants, under conditions of security, transparency and efficiency.
d. Have operational and technical rules and standards that allow the sending of information on Keys, Payment Methods and other information that must be supplied to the Centralized Directory and its subsequent consultation.
e. Require its Participants to have a personal data processing and protection policy and the authorization of their Customers that allows the processing of personal data required for the interoperability of the SPBVI provided for in this Circular, under the terms set forth in Law 1581 of 2012, Decree 1074 of 2015 and other rules that modify, replace, add to, or regulate them.
f. Determine the type of Key from the Key sent by the Participant and send both data to the Centralized Directory for each Key Resolution.
g. Obtain the Test Certification of the Centralized Directory, in accordance with the provisions of CEOS DSP-470 Subject 19: Regulation of the Centralized Directory (DICE) or those that modify or replace it, prior to the entry into production of the SPBVI.
h. Update the Test Certification of the Centralized Directory, in accordance with the provisions of CEOS DSP-470 Subject 19: Regulation of the Centralized Directory (DICE) or those that
Reference No: CRE DSP46520112026 Hoja 18 - 20 CIRCULAR REGLAMENTARIA EXTERNA DSP-465 Fecha: viernes, 20 de noviembre de 2026 Asunto 18: Interoperabilidad de los Sistemas de Pago de Bajo Valor Inmediatos. modify or replace; and obtain any additional Certification required by the BR to guarantee Interoperability; i. Certify all Participants of the SPBVI, prior to their entry into production, with respect to the Resolution and Key Management processes and any other aspect that the BR requires to guarantee Interoperability; and update such Certification when the BR so requires; j. Inform the BR, on the terms that it defines in CEOS DSP-470 Asunto 19: Reglamento del Directorio Centralizado (DICE) or those that modify or replace it, of any functional or non-functional adjustment that it will make to its SPBVI with potential impact on Interoperability, the Resolution and Key Management processes or on the use of the Centralized Directory. The BR may request additional information and require tests for the updating of the SPBVI Certification prior to the implementation of such adjustments. 4.2.2. Structure of the Centralized Directory The organization of the information that the Centralized Directory will store will follow the minimum structure of the Federated Directory. The Centralized Directory will not store transactional information of Clients or other types of data that are not necessary for the processing of Payment Orders and/or Immediate Fund Transfers. The following table shows the structure that the Centralized Directory will follow, replicating the information reported from the Federated Directory:
Fecha: viernes, 20 de noviembre de 2026
Asunto 18: Interoperabilidad de los Sistemas de Pago de Bajo Valor Inmediatos.
Table 3. Information of the Centralized Directory
a. For the operation of the Centralized Directory, EASPBVIs shall: Supply the Centralized Directory with the Keys and associated information of the Participants' Clients registered in the Federated Directories.
b. Consult the Centralized Directory in the event of registration or modification of a Key in their Federated Directories, to ensure that such Key is not associated with another Payment Method. Once the Centralized Directory has carried out this process, the Key may be registered in the Federated Directory of the respective SPBVI.
c. Update the Keys and associated information in their Federated Directories, according to the Key management processes carried out by the Participants' Clients. For this purpose, they shall comply with the connection standards and message formatting defined by the BR and report these updates to the Centralized Directory.
In cases where a Participant decides to disassociate from an SPBVI and associate with another(s), or where, while maintaining its association with an SPBVI, it decides to simultaneously associate with another(s), the SPBVI to which the Participant is associating may request the BR to carry out, from the Centralized Directory, the operational procedure for the delivery of the Participant's Keys. This procedure shall be carried out following the operational guidelines defined by the BR.
CIRCULAR REGLAMENTARIA EXTERNA DSP-465
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Inmediatos.
To carry out the Compensation and Settlement process for Immediate Payment Orders and/or Fund Transfers, EASPBVI must comply with the following:
a. Process Immediate Payment Orders and/or Fund Transfers and implement the necessary risk controls for their acceptance following the provisions of Annex 2 of this circular, only for those that have completed the Key Resolution process.
b. Use a connection standard based on API-REST, as well as the ISO 20022 messaging standard for electronic data exchange with the MOL by the SPBVI, as well as between SPBVI in their duty to interoperate. The messaging format to be used must be implemented in accordance with the provisions of Annex 5 of this circular.
c. Have operational, technical, and security rules and standards for the development of their operations and those of their Participants, under conditions of security, transparency, and efficiency.
d. Require their Participants, through their Regulations, to have security rules and standards for the administration, management, prevention, and control of fraud risk.
e. Comply with the maximum time of twenty (20) seconds. The technical aspects of this provision are detailed in Annex 5 of this Circular. This parameter must be met in at least 99.5% of the Immediate Payment Orders and/or Fund Transfers originated in the SPBVI. Likewise, incorporate and require their Participants through their Regulations, compliance with the terms and conditions for the registration, control, and standard of Time Stamps in accordance with the provisions of Annex 5 of this circular.
f. Establish monitoring mechanisms to periodically track compliance with the maximum time established for the Beneficiary to receive the funds in their Payment Method.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Inmediatos.
g. Implement and require their Participants to make adjustments if necessary to comply with the maximum time established for the Beneficiary to receive the funds in their Payment Method.
h. Have an operational reconciliation process for Immediate Payment Orders and/or Fund Transfers. Likewise, incorporate and require its Participants, through its Regulation, to comply with the terms and conditions of said process in accordance with the provisions of Annex 5 of this circular.
i. Require its Participants, through its Regulation, to provision in the deposit accounts the necessary resources for the settlement of Immediate Payment Orders and/or Fund Transfers in the MOL provided in numeral 5.3. of this Circular.
j. Maintain a minimum monthly availability level of 99.8% in its processing of Immediate Payment Orders and/or Fund Transfers. The BR shall indicate the guidelines for its calculation in CEOS DSP-471 Subject 20: Regulation of the Operating Mechanism for Settlement or those that modify or replace it.
k. Obtain the MOL test Certification, in accordance with the provisions of CEOS DSP-471 Subject 20: Regulation of the Operating Mechanism for Settlement or those that modify or replace it, prior to the entry into production of the SPBVI.
l. Update the MOL test Certification, in accordance with the provisions of CEOS DSP-471 Subject 20: Regulation of the Operating Mechanism for Settlement or those that modify or replace it; and obtain any additional Certification required by the BR to guarantee Interoperability.
m. Certify all Participants of the SPBVI, prior to their entry into production, regarding the processing of Immediate Payment Orders and/or Fund Transfers and any other aspect that the BR requires to guarantee Interoperability; and update said Certification when the BR requires it.
n. Inform the BR, in the terms defined by the latter in CEOS DSP-471 Subject 20: Regulation of the Operating Mechanism for Settlement or those that modify or replace it, of any functional or non-functional adjustment that it will make to its SPBVI with potential impact on the
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
Interoperability, the Clearing and Settlement process, the processing of Immediate Payment Orders and/or Fund Transfers or the use of the MOL. The BR may request additional information and require tests for the update of the SPBVI Certification prior to the implementation of said adjustments.
To carry out the Clearing of Immediate Payment Orders and/or Fund Transfers, the provisions of Annex 2 of this Circular must be followed.
During the Clearing process, before the acceptance of Immediate Payment Orders and/or Fund Transfers, the EASPBVI or their Participants must reject the Immediate Payment Orders and/or Fund Transfers if the risk controls established by the EASPBVI in accordance with article 2.17.2.1.17. of Decree 2555 of 2010 are not met, as well as the technical and operational validations, in accordance with the provisions of numeral 2 of Annex 5 of this Circular.
The EASPBVI must define in their regulation the procedures to mitigate the occurrence of these grounds for rejection in applicable cases and in any case ensure the recording and traceability when they occur.
The Settlement of Immediate Payment Orders and/or Fund Transfers shall be executed in the MOL on a gross basis and in real time.
To carry out the Settlement of Immediate Payment Orders and/or Fund Transfers, the provisions of Annex 2 of this Circular must be followed.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
In the event that an Immediate Payment Order and/or Fund Transfer has been accepted and is not to be completed within the maximum processing time due to technical, operational or technological failures, the EASPBVI must follow the guidelines of the exception flows defined by the BR in the Operational and Services Circular DSP-471 Subject 20: MOL Regulation or those that modify or replace it.
The EASPBVI must incorporate in their Regulation the terms and conditions for the notification to the Participants and their Clients in accordance with the provisions of Annex 5 of this circular.
The BR shall define the operational guidelines for the attention of frauds, errors and petitions, complaints and claims on the processing of Immediate Payment Orders and/or Fund Transfers that must be followed, considering the recommendations made by the Immediate Payments Interoperability Committee.
The EASPBVI must incorporate in their regulation the obligation of the Participants to attend and manage the petitions, complaints and claims for the processing of Immediate Payment Orders and/or Fund Transfers, following the provisions of Law 1328 of 2009, Law 1480 of 2011, the Basic Legal Circular of the Financial Superintendence of Colombia, or, failing that, Law 1755 of 2015, and other norms that replace, modify, add or regulate them, and to comply with the provisions of Annex 4 of this Circular for the procedures of return and reversal of Immediate Payment Orders and/or Fund Transfers.
The EASPBVI and their Participants must include in the financial education campaigns they carry out on Bre-B, specific material focused on the prevention of the risk of fraud and scams associated with Immediate Payment Orders and/or Fund Transfers.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
The EASPBVI must require, through their Regulations, the following obligations of their Participants:
a. Make available the accesses in the Service Provision Channels that they will enable to initiate Immediate Payment Orders and/or Fund Transfers, using the seal/mark referred to in article 18 of External Resolution No. 6 of 2023 issued by the JDBR, following the provisions of Annex 3 of this Circular.
b. Carry out the processing of Immediate Payment Orders and/or Fund Transfers from their initiation to their completion in a simple, secure, frictionless manner, using clear and precise language.
c. Require from the Customer only the entry of the Key or the reading of the QR Code and, where applicable, the amount or value of the Immediate Payment Order and/or Fund Transfer for its processing and/or the information of the Payment Reference(s), following the guidelines defined by the BR.
Participants must enable an additional space for the Customer to select the Payment Method from which the funds will be debited, where applicable.
d. Establish a uniform procedure to process Immediate Payment Orders and/or Fund Transfers regardless of the Receiving Participant.
e. Inform the Customer, before confirming the Immediate Payment Order and/or Fund Transfer, of the masked name or corporate name of the Beneficiary, as well as the unmasked trade name, if any, for example, as follows: VeterXXX RamXXXX SAS – Perros y Gatos or –AnXXXa PXXez.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
When the Beneficiary carries out the activity of merchant aggregation, the Customer must be informed of the masked corporate name of the Beneficiary (Aggregator) and the trade name of the aggregated merchant. For example, as follows: PagosXXX – Mascotas or PagosXXX – AnXXXa PXXez.
If the aggregated merchant does not have a trade name, the Customer must be informed of the masked corporate name of the Beneficiary (Aggregator) and the name or corporate name of the aggregated merchant. For example, as follows: PagosXXX –VeterXXX SAS or PagosXXX –AnXXXa PXXez. Participants may additionally show the name of the Receiving Participant of the Immediate Payment Order and/or Fund Transfer.
f. Inform the Customer, through a downloadable receipt, once the Immediate Payment Order and/or Fund Transfer is completed, at a minimum, the name of the Beneficiary and the information referred to in numeral 3.1.4.6. of Part I, Title III, Chapter I of the Basic Legal Circular of the Financial Superintendence of Colombia.
The Bre-B seal/mark may be accompanied by the brand or distinctive sign of the EASPBVI, of the SPBVI it administers and/or of its Participants.
The BR will determine the name and image and the terms and conditions of its use in Annex 3 of this Circular, considering the recommendations made for this purpose by the Immediate Payments Interoperability Committee.
The Immediate Payments Interoperability Committee (CIPI) will operate through technical working groups convened by the BR in its role as Secretary, in which the EASPBVI and the entities administering low-value payment systems described in numeral 7 of article 2.17.1.1.1 of Decree 2555 of 2010, their Participants, the payment service providers to
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
which numeral 20 of article 2.17.1.1.1 of Decree 2555 of 2010 refers, and other related agents may participate.
The regulatory and supervisory authorities of the payments industry, among other authorities, may be invited to the technical working groups.
The Secretariat of the CIPI will determine the subject matter and composition of the technical working groups and may convene them directly or through the sector's trade associations, seeking representativeness of the payments industry.
The functions of the CIPI will be the following:
1. Recommend and/or disseminate rules, operating standards and other matters related to the Interoperability of Immediate Payment Orders and/or Fund Transfers.
2. Recommend actions to promote the development of low-value payment systems.
3. Develop studies and technical documents on the payments industry.
The recommendations of the technical working groups may contain different positions on the topics put to the consideration of the CIPI.
The BR will exercise the Secretariat of the CIPI. The functions of the Secretariat will be the following:
1. Form, convene and coordinate the technical working groups of the CIPI as required in order to receive recommendations and/or disseminate matters related to the processing and promotion of Immediate Payment Orders and/or Fund Transfers. For this purpose, it will define the deadlines within which they will meet and deliver their recommendations.
2. Receive the recommendations and studies of the CIPI and present them to the technical areas of the BR for their consideration and analysis, as applicable.
3. Convene the payments industry broadly at least once a year to inform the CIPI's work agenda and its progress.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
4. Determine cases in which the topics under study or discussion are confidential and establish processes for the handling of information and participation of the entities.
5. Issue the compliance policy on free competition for the operation of the CIPI.
The Secretariat shall be the sole channel for the disclosure of the information produced in the technical working groups.
The implementation of the provisions set forth in External Resolution No. 6 of 2023 issued by the Board of Directors of the BR and in this Circular shall be carried out gradually in the following phases:
Phase 1: Within the month following the entry into force of the aforementioned Resolution, the BR shall convene the Immediate Payments Interoperability Committee.
Phase 2: Within the five (5) months following the end of Phase 1, the BR, through general regulations, shall define:
a. the standards and technical and control conditions of the time stamps for the processing of Immediate Payment Orders and/or Fund Transfers;
b. the processes for operational reconciliation and notification of failure events related to the processing of Immediate Payment Orders and/or Fund Transfers;
c. the messaging format for the Clearing and Settlement process of Immediate Payment Orders and/or Fund Transfers;
d. the operational guidelines for addressing fraud, errors and requests, complaints and claims regarding the processing of Immediate Payment Orders and/or Fund Transfers, and
e. the messaging format of the Federated Directories and the standards and technical and control conditions of the time stamps related to the registration of the Keys and other events related to their use.
The foregoing, taking into consideration the recommendations made for this purpose by the Immediate Payments Interoperability Committee.
CIRCULAR REGLAMENTARIA EXTERNA DSP-465
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
Phase 3: Within the fourteen (14) months following the completion of Phase 2, the EASPBVI and their Participants must implement the adjustments to enable Access Technologies, the Customer experience and, in general, all adaptations required to process Immediate Payment Orders and/or Fund Transfers.
In this phase, the BR, through general regulations, shall define the image and name of the seal referred to in article 18 of the aforementioned Resolution and its user manual; the foregoing taking into consideration the recommendations made for this purpose by the Immediate Payments Interoperability Committee.
Phase 4: In the two (2) months following the end of Phase 3, the EASPBVI and their Participants must carry out the process of collection and storage of the Keys in accordance with the guidelines defined by the BR.
Phase 5: As of the end of Phase 4, the EASPBVI and their Participants must have enabled the Key management processes, in accordance with the provisions of this Circular, and shall process the Immediate Payment Orders and/or Fund Transfers in accordance with the guidelines defined by the BR.
Paragraph one. The BR, through general regulations, may bring forward the start of Phases 3, 4 and 5 depending on their development.
Paragraph two. The EASPBVI must submit to the Superintendencia Financiera de Colombia the regulations and their amendments of the SPBVI they administer during Phase 3, without this conditioning the implementation of the following phases.
The Value-Added Services provided by the EASPBVI and their Participants must comply with the technical and operational processes defined by the BR for the processing of Immediate Payment Orders and/or Fund Transfers from the sending of the payment instruction by the originating SPBVI to the MOL, in accordance with the technical specifications of said mechanism, and until the MOL confirms the Settlement to the originating SPBVI and the receiving SPBVI. The EASPBVI and their
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
Participants that provide Value-Added Services may implement processes, functionalities and mechanisms related to the Customer experience to initiate an Immediate Payment Order and/or Fund Transfer, when this is not specifically regulated in Annex 3 of this Circular. This faculty may include, among other aspects, origination, the interface, data capture and the mechanisms to report its completion. The Customer experience must be simple, secure, clear and frictionless, using precise and understandable language.
The EASPBVI and their Participants that provide Value-Added Services may continue offering them and must adjust to the standards and conditions established by the BR, in accordance with the transition regime defined by the BR. The BR may establish the standards and technical and operational conditions for the provision of Value-Added Services, such as payment initiation, payment requests and electronic commerce. For this purpose, the BR may take into account the recommendations of the Immediate Payments Interoperability Committee.
The EASPBVI and their Participants must inform the BR of the new Value-Added Services they wish to provide, at least thirty (30) calendar days prior to their offering or implementation. For these purposes, they must request a review session from the BR through the email pagosinmediatos@banrep.gov.co. The BR may request additional information and shall communicate to the EASPBVI or their Participants, as applicable, its observations within the ten (10) calendar days following the holding of said session or the delivery of the additional information requested.
CIRCULAR REGLAMENTARIA EXTERNA DSP-465
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
1. The Participant performs the Customer authentication procedure.
2. The Customer requests from the Participant with which it has its Payment Instrument the registration of the Key through any of the Service Provision Channels available to it for the provision of services related to Immediate Payment Orders and/or Fund Transfers.
3. The Participant provides information to its Customers about the options for types of Keys they can choose and the structure of each option, in accordance with the provisions of numeral 3.4.2 of this Circular.
The Customer selects only one Key in each registration process. The registration process must be carried out following the Customer experience described in Annex 3 of this Circular.
4. The Participant obtains authorization from the Customer to be able to share the information with the Federated Directory and the Centralized Directory.
5. The Participant makes available the fields for the Customer to link its Key and associate it with the chosen Payment Instrument, following the standards according to the type of Key and the information structure defined for the Federated Directory. The Participant must validate the information, using any of the strong authentication mechanisms established in the Basic Legal Circular of the Financial Superintendence of Colombia.
6. The Participant sends the Key registration request to the SPBVI in which it participates so that it can be validated as not repeated in the Federated Directory:
a. If it already exists, the SPBVI informs the Participant of the existence of the Key.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
b. If it does not exist, the SPBVI sends the request to the Centralized Directory for the respective validation.
i. If the Key is not registered, the Centralized Directory registers the Key and communicates it to the SPBVI, so that it in turn performs the registration in its Federated Directory and informs the Participant.
ii. If the Key is registered, the Centralized Directory communicates to the SPBVI the pre-existence of the Key so that it informs the Participant.
The result of the processes described above must be reported by the Participants to the Customer in real time.
7. Once the Key registration is successful, the Customer may receive Immediate Payment Orders and/or Fund Transfers within the period established by the Participant, which may not exceed two (2) hours.
8. The registration of the Key may be carried out by the Customer on any day and at any time.
9. To originate an Immediate Payment Order and/or Fund Transfer, the registration of the Key of the ordering Customer shall not be required.
1. The Participant performs the Customer authentication procedure.
2. The Customer requests from the Participant the modification of the Key or of the Payment Instrument associated with it, through the Service Provision Channels available for the provision of services related to Immediate Payment Orders and/or Fund Transfers.
3. The Participant makes available the options for the Customer to modify its Key for another Key of the same or another type and/or modify the Payment Instrument associated with the Key for another Payment Instrument of the Participant where the Key is registered, following the standards defined according to the type of Key.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
4. The Participant sends the Key modification request to the SPBVI in which it participates so that it verifies that it is not repeated in the Federated Directory:
a. If it exists, the SPBVI informs the Participant of the pre-existence of the Key.
b. If it does not exist, the SPBVI sends the request to the Centralized Directory for the respective validation.
i. If the Key is not registered, the Centralized Directory registers the Key and communicates it to the SPBVI, so that it in turn performs the registration in its Federated Directory and informs the Participant.
ii. If the Key is registered, the Centralized Directory communicates to the SPBVI the pre-existence of the Key so that it informs the Participant.
The result of the processes described above must be reported by the Participants to the Customer in real time.
5. Once the modification of the Key and/or the Payment Instrument is successful, the Customer may initiate Immediate Payment Orders and/or Fund Transfers within the period established by the Participant, which must not exceed two (2) hours.
6. Requests for modification of the Key and/or the Payment Instrument may be made by the Customer on any day and at any time.
1. The Participant performs the Customer authentication procedure.
2. The Customer requests from the Participant the cancellation of the Key through any of the Service Provision Channels available for the provision of services related to Immediate Payment Orders and/or Fund Transfers.
3. The Participant provides the fields for the Customer to cancel its Key.
4. The Participant sends the Key cancellation request to the SPBVI in which it participates.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
5. Confirmation of the successful cancellation process must be communicated to the Customer in real time.
6. The Client may request the cancellation of the Key and/or the Payment Method at any day and time.
7. Cancellation may also be requested by the Participant in the cases indicated in item 3.4.4 of this Circular. In this case, the Participant shall inform the EASPBVI of the new development so that it cancels the Key in the Federated Directory and requests the respective update from the Centralized Directory.
8. The Key of a natural person who is not a merchant that is cancelled shall be released for reuse in the Federated Directory immediately.
9. In cases of Key cancellation due to a change of Acquirer when the Merchant decides to keep the Key, the Acquirer performing such cancellation shall allow the Key to be reused immediately. This shall be contemplated in the Acquirer change procedure that the SPBVI must create, in accordance with what is defined in item e. of item 3.4.2. of this Circular.
The portability process may be executed once the BR issues the technical specifications for this process.
1. The Participant performs the Client authentication procedure.
2. The Client requests the Participant to block their Key through any of the Service Provision Channels made available for the provision of services related to Payment Orders and/or Immediate Fund Transfers.
3. The Participant provides the fields for the Client to block their Key and shall notify them of the terms associated with this process.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
4. The Participant sends the Key blocking request to the SPBVI in which it participates.
5. The EASPBVI records the blocking new development in its Federated Directory and requests the respective update from the Centralized Directory.
6. The Key shall be blocked for a period of up to thirty (30) business days.
7. Once the initial thirty (30) business days of the blocking have elapsed, the Client may extend this period by an additional thirty (30) business days or otherwise the Participant shall cancel the Key.
8. Confirmation of the successful blocking process and of the eventual cancellation shall be communicated to the Client in real time.
9. The blocking may also be performed by the Participant entity in the cases indicated in item 3.4.4 of this Circular.
1. The Participant performs the Client authentication procedure.
2. The Client requests the Participant to reactivate their blocked Key through any of the Service Provision Channels made available for the provision of services related to Payment Orders and/or Immediate Fund Transfers.
3. The Participant provides the fields for the Client to reactivate their Key.
4. The Participant sends the Key reactivation request to the SPBVI in which it participates.
5. The EASPBVI requests the respective update from the Centralized Directory:
a. If the reactivation is successful, the Centralized Directory informs the SPBVI so that the EASPBVI records the new development in its Federated Directory and informs the Participant.
b. If the reactivation is not successful, the Centralized Directory informs the SPBVI so that the EASPBVI informs the Participant.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
6. Confirmation of the reactivation process shall be communicated to the Client in real time, indicating that from that moment on the Key may be used.
Reactivation may also be performed by the Participant entity when it has blocked the Key in accordance with what is established in item 3.4.4. of this Circular.
1. The Participant performs the Client authentication procedure.
2. The Client requests the Participant to inquire about the Key(s) associated with their Payment Methods, through any of the Service Provision Channels made available for the provision of services related to Payment Orders and/or Immediate Fund Transfers.
3. The Participant shall display, in real time and as a result of the inquiry, at a minimum the following information: the Keys that the Client has registered with the Participant through which the inquiry is being made and that are active or blocked, the associated Payment Methods and their registration dates.
4. The Client may perform the Key inquiry any day and at any time.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
The following describes the Compensation and Settlement processes of Payment Orders and/or Immediate Fund Transfers for Intra-SPBVI and Inter-SPBVI Operations.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
1. The Originating Participant must reserve funds in its Client's Payment Method to guarantee acceptance of the Payment Orders and/or Immediate Fund Transfers.
2. The Originating Participant sends the Payment Order and/or Immediate Fund Transfer to the originating SPBVI.
3. The originating SPBVI applies its risk controls to authorize the Payment Order and/or Immediate Fund Transfer and subsequently sends it to the MOL.
4. The MOL validates the status of the deposit accounts of the Originator and Receiver Participants and carries out the funds reservation of the Originator Participant, to guarantee the Acceptance of the Payment Order and/or Immediate Funds Transfer.
5. The MOL sends the Payment Order and/or Immediate Funds Transfer to the receiving SPBVI, which confirms to the latter the existence of sufficient funds to guarantee its acceptance.
6. The receiving SPBVI applies its risk controls to authorize the Payment Order and/or Immediate Funds Transfer and sends the payment instruction to the Receiver Participant.
7. The Receiver Participant validates the status of its Client's Payment Method, to guarantee the Acceptance of the Payment Order and/or Immediate Funds Transfer.
8. The Receiver Participant sends a message to the receiving SPBVI, confirming the result of the validations for the clearing of the Payment Order and/or Immediate Funds Transfer.
9. The receiving SPBVI sends a message to the MOL, confirming the result of the validations for the clearing of the Payment Order and/or Immediate Funds Transfer.
10. The MOL forwards the message from the receiving SPBVI to the originating SPBVI, confirming the result of the validations for the clearing of the Payment Order and/or Immediate Funds Transfer.
11. The originating SPBVI declares the acceptance of the Payment Order and/or Immediate Funds Transfer.
12. The MOL executes the Settlement of the Payment Order and/or Immediate Funds Transfer and confirms the result to the originating and receiving SPBVI.
13. The originating and receiving SPBVI confirm to the Originator Participant and Receiver Participant, respectively, that they can execute the debit and credit of the funds in their Clients' Payment Methods.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
1. The Originator Participant must reserve funds from its Client's Payment Method, to guarantee the acceptance of the Payment Order and/or Immediate Funds Transfer.
2. The Originator Participant sends the Payment Order and/or Immediate Funds Transfer to the SPBVI.
3. The originating SPBVI applies its risk controls to authorize the Payment Order and/or Immediate Funds Transfer and subsequently send it to the MOL.
4. The MOL validates the status of the deposit accounts of the Originator and Receiver Participants and carries out the funds reservation of the Originator Participant, to guarantee the acceptance of the Payment Order and/or Immediate Funds Transfer.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Low-Value Payment Systems Immediate.
5. The MOL forwards the Immediate Payment Order and/or Funds Transfer to the receiving SPBVI, which confirms to the latter the existence of sufficient funds to guarantee its acceptance.
6. The receiving SPBVI sends the Immediate Payment Order and/or Funds Transfer to the Receiving Participant.
7. The Receiving Participant validates the status of its Client's Payment Instrument, to guarantee the acceptance of the Immediate Payment Order and/or Funds Transfer.
8. The Receiving Participant sends a message to the receiving SPBVI, confirming the result of the validations for the clearing of the Immediate Payment Order and/or Funds Transfer.
9. The receiving SPBVI sends a message to the MOL, confirming the result of the validations for the clearing of the Immediate Payment Order and/or Funds Transfer.
10. The MOL forwards the message to the SPBVI in the role of Originator, confirming the result of the validations for the clearing of the Immediate Payment Order and/or Funds Transfer.
11. The originating SPBVI declares the acceptance of the Immediate Payment Order and/or Funds Transfer.
12. The MOL executes the Settlement of the Immediate Payment Order and/or Funds Transfer and confirms the result to the originating SPBVI and receiving SPBVI.
13. The SPBVI confirms to the Originating and Receiving Participants that they may execute the debit and credit of the resources in their Clients' Payment Instruments, respectively.
This Annex describes the contents and requirements regarding the Customer experience that the Administrating Entities of Immediate Low-Value Payment Systems (EASPBVI) must require of their Participants for the provision of Intra-SPBVI and Inter-SPBVI Immediate Payment Orders and/or Funds Transfers (OP/TF).
For the provision of the service, the EASPBVI must require the Participants of their SPBVI to use the terminology provided in External Resolution No. 6 of 2023 issued by the Board of Directors of the Banco de la República (JDBR) and in External Regulatory Circular DSP-465 of 30 April 2024 of the BR and its amendments.
The illustrations used in this document are references that seek to facilitate understanding of the provisions on Customer experience. Participants must adapt the required contents in accordance with their brand identity, digital environments and Service Provision Channels available to provide the service, including those of digital correspondent services. Likewise, Participants may include explanatory and guidance messages for their Customers that facilitate carrying out the different processes.
The rules defined in this annex shall apply to the classifications defined in numeral 3.3. of this Circular. In any case, the Participants may innovate on the Customer experience of the Immediate Payment Orders and/or Fund Transfers in compliance with the provisions of numeral 12 of this Annex.
In cases where the use of the seal/brand is mentioned, the Participants must implement it in accordance with the provisions of the Bre-B Usage Manual.
The Participants must comply with the provisions herein, without prejudice to compliance with the requirements or standards regarding the security and authentication of their Customers, in accordance with applicable regulations.
Date: Friday, 20 November 2026
Subject 18: Interoperability of immediate low-value payment systems
The SPBVI must require their Participants to enable the Bre-B Zone in the Service Provision Channels arranged to make Immediate Payment Orders and/or Fund Transfers.
The Bre-B Zone must be accessible from the first level or the screen immediately following the Customer authentication screen and be identified with the image defined by the BR following its Usage Manual for this purpose.
If the Participant decides to keep other menus, submenus, or functionalities related to payments or transfers, in the field where access is enabled to make Immediate Payment Orders and/or Fund Transfers, it must use the graphic image or the name of Bre-B defined by the BR following its Usage Manual for this purpose.
In the case of reading a QR Code, the Participant must enable the option to make Immediate Payment Orders and/or Fund Transfers and may use the graphic image or the name of Bre-B defined by the BR following its Usage Manual for this purpose.
Date: Friday, 20 November 2026
Subject 18: Interoperability of immediate low-value payment systems
The Participant may enable for its legal entity Customers the Bre-B Zone in its business portals or other Service Provision Channels arranged to make Immediate Payment Orders and/or Fund Transfers, following the guidelines described in this Annex.
In any case, the Participant must enable, at a minimum, in its Service Provision Channels established for the processing of Immediate Payment Orders and/or Fund Transfers, from the first level or the screen immediately following the Customer authentication screen, the functionalities of “Payments and transfers” and “Key processes”, and must use the graphic image or the name of Bre-B defined by the BR following its Usage Manual for this purpose.
Date: Friday, 20 November 2026
Subject 18: Interoperability of immediate low-value payment systems
The Bre-B Zone must include at a minimum the following functionalities:
1. Payments and transfers
a. With the Key
b. With the QR Code:
- Read
- Generate
c. Payments with Reference
- With the Key
- With the QR Code
2. Key processes
a. Registration
b. Modification
c. Cancellation
d. Portability
e. Blocking
f. Reactivation
g. Inquiry
3. Transaction history
a. History
b. Refund request
c. Reversal request
4. Petitions, complaints and Claims
5. Other functionalities (related to the service of Immediate Payment Orders and/or Fund Transfers)
The Payments with Reference functionality must allow the Customer of the Originating Participant, who has the Payment Reference information, to initiate Immediate Payment Orders and/or Fund Transfers through the use of Access Technologies.
Date: Friday, 20 November 2026
Subject 18: Interoperability of immediate low-value payment systems
The Participants must adapt the required functionalities, in accordance with their brand identity, the digital environments and Service Provision Channels they have available to provide the service of Immediate Payment Orders and/or Fund Transfers, preserving the characteristics of simplicity, security, without friction, and using clear and precise language. These same characteristics must be observed in the event that the Participant includes other functionalities in the Bre-B Zone.
Date: Friday, 20 November 2026
Subject 18: Interoperability of immediate low-value payment systems
Once the Customer enters the immediate payment or transfer functionality with Key, from the Bre-B Zone, the Participants must guarantee the following experience:
1. Display only the following fields:
Key (space enabled to write the Key of the Receiving Customer)
Amount (space enabled to write the amount of the payment or transfer)
Payment Reference (space enabled to write the Payment Reference), when applicable.
The Participants must enable an additional space for the Customer to select the Payment Method from which the funds will be debited, when applicable.
2. Inform the Customer, before confirming the Immediate Payment Order and/or Fund Transfer, of the provisions in literal e. of numeral 6.1 of this Circular.
3. Once the Immediate Payment Order and/or Funds Transfer is completed, the Participant must inform the Customer, through a downloadable receipt, of the provisions in literal e. of numeral 6.1 of this Circular, the Payment Reference and the information referred to in numeral 3.1.4.6. of Part I, Title III, Chapter I of the Basic Legal Circular of the Financial Superintendence of Colombia and may include the name of the SPBVI through which the Immediate Payment Order and/or Funds Transfer was made.
In the event that the Immediate Payment Order and/or Funds Transfer cannot be completed correctly, the Participant must follow the provisions of Annex 2 and inform the Customer of said situation.
Date: Friday, 20 November 2026
Subject 18: Interoperability of immediate low-value payment systems
Access to Immediate Payment Orders and/or Funds Transfers through other menus, submenus or functionalities must be at the same level of navigation and access as the other options for payments and transfers, including those that do not meet the characteristics of immediacy.
The access where the initiation of Immediate Payment Orders and/or Funds Transfers is enabled must be identified with the Bre-B seal/brand, following its User Manual for this purpose.
Once the Customer enters the payment or transfer functionality with Key, the originating Customer must have the same experience described in numeral 4 of this Annex.
Date: Friday, 20 November 2026
Subject 18: Interoperability of immediate low-value payment systems
Once the Customer enters the immediate payment or transfer functionality with QR Code, through the Bre-B Zone, the Participants must guarantee the following experience:
1. Enable the reading of the QR Code
1.1. Enable the field(s) to include the amount of the payment or transfer and/or the Payment Reference(s), in case they are not included.
The Participants must enable an additional space for the Customer to select the Payment Method from which the funds will be debited, when applicable.
2. Inform the Customer, before confirming the Immediate Payment Order and/or Funds Transfer, of the provisions in literal e. of numeral 6.1 of this Circular.
3. Once the Immediate Payment Order and/or Funds Transfer is completed, inform the Customer, through a downloadable receipt, of the provisions in literal e. of numeral 6.1 of this Circular, the Payment Reference, and the information referred to in numeral 3.1.4.6. of Part I, Title III, Chapter I of the Basic Legal Circular of the Financial Superintendence of Colombia.
Date: Friday, 20 November 2026
Subject 18: Interoperability of immediate low-value payment systems
4. The downloadable receipt may include the name of the SPBVI through which the Immediate Payment Order and/or Funds Transfer was made.
5. Enable the generation of static QR Codes to receive funds from Immediate Payment Orders and/or Funds Transfers.
6. Additionally, they may include the functionality to generate dynamic QR Codes.
Reference No: CRE DSP46520112026 Sheet 18-A3-10 EXTERNAL REGULATORY CIRCULAR DSP-465 Date: Friday, 20 November 2026 Subject 18: Interoperability of immediate low-value payment systems 7. Experience for making an Immediate Payment Order and/or Funds Transfer using the QR Code in other menus or functionalities Access to Immediate Payment Orders and/or Funds Transfers through other menus, submenus or functionalities using the QR Code must follow the following guidelines: 1. The access must be at the same level of navigation and access as the other options for payments and transfers, including those that do not meet the characteristics of immediacy. 2. This access must be identified with Bre-B as determined by the BR following its User Manual for this purpose. 3. The Participants must guarantee the same experience described in steps 1, 2 and 3 of numeral 6 of this Annex.
Reference No: CRE DSP46520112026 Sheet 18-A3-11 EXTERNAL REGULATORY CIRCULAR DSP-465 Date: Friday, 20 November 2026 Subject 18: Interoperability of immediate low-value payment systems 8. Experience for making an Immediate Payment Order and/or Funds Transfer using the QR Code in a direct access In the event that the Participant has a direct access for reading the QR Code, the following experience must be guaranteed: 1. Enable the reading of the QR Code and an additional space to enter the amount of the payment or immediate transfer and the Payment Reference when applicable, in case they are not contained in the QR Code. 2. The Participants must enable an additional space for the Customer to select the Payment Method from which the funds will be debited, when applicable. 3. Follow steps 2, 3, 4 and 5 described in numeral 6 of this Annex.
Date: Friday, 20 November 2026
Subject 18: Interoperability of immediate low-value payment systems
The Participants must enable in the Bre-B Zone the functionality related to the Key management Processes, following the following indications:
1. Registration
a. Key options (space enabled to choose the Customer's preferred Key). All types of Keys must be displayed under equal conditions and in accordance with the provisions of numeral 3.4.2. of this Circular.
i. Identity document number
ii. Mobile phone number
iii. Email address
iv. Alphanumeric
v. Code of the commercial establishment assigned by the Acquirer (applies only to merchants).
b. Payment Method with which the Key is to be associated.
Participants present the Key options based on the information registered for their Customers. In any case, the Customer may update such information following the policies established for these purposes by the issuers of the Payment Methods. The Customer selects only one Key in each registration process.
2. Modification
3. Cancellation
4. Portability
5. Blocking
6. Reactivation
7. Inquiry
The Key processes must be carried out in accordance with the provisions of Annex 1 of this Circular.
Date: Friday, 20 November 2026
Subject 18: Interoperability of immediate low-value payment systems
Participants must enable in the Bre-B Zone the functionality for inquiring the Transaction History, complying with the following characteristics:
1. Allow the display of immediate payments and/or transfers made at least in the last 30 calendar days.
2. Enable the options to carry out the return and reversal processes described in Annex 4 of this Circular for immediate payments and/or transfers of the last 30 calendar days.
Date: Friday, 20 November 2026
Subject 18: Interoperability of immediate low-value payment systems
Participants must enable in the Bre-B Zone the Requests, Complaints and Claims functionality.
This functionality must be enabled so that the Customers of the SPBVI Participants can file before the entity that issued their payment method and follow up on Requests, Complaints and Claims related to the service of Immediate Payment Orders and/or Fund Transfers.
Requests, complaints and claims must be processed in accordance with the provisions of Law 1328 of 2009, Law 1480 of 2011, Basic Legal Circular of the Financial Superintendence or, failing that, Law 1755 of 2015 and other rules that modify, replace, add to or regulate them.
The operational guidelines for the attention of frauds, errors and requests, complaints and claims of the processing of Immediate Payment Orders and/or Fund Transfers Intra-SPBVI and Inter-SPBVI that the EASPBVI must require of their Participants are described.
For the attention of frauds, errors and requests, complaints and claims of the processing of Immediate Payment Orders and/or Fund Transfers, the following Return and Reversal procedures are regulated:
1.1 The funds of the Immediate Payment Orders and/or Fund Transfers that may be subject to the Return or Reversal procedures must have been previously credited to the Payment Method of the receiving Customer.
1.2 The Return and Reversal procedures must be enabled in the Bre-B Zone following the provisions of Annex 3 of this Circular and may be enabled in other channels provided by the SPBVI Participants.
1.3 The states of the return and reversal procedures are: in process or finalized. These states must be reflected when consulting the "Transaction History" in the Bre-B Zone, so that the Customer can track their requests.
1.4 In the "Transaction History" functionality of the Bre-B Zone, the Immediate Payment Orders and/or Fund Transfers that are subject to a return or reversal procedure must be identified and may not be subject to new return or reversal procedures.
1.5 The return procedure applies to the classifications Person-to-Person Payments and Payments to Merchants.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
1.6 The reversal procedure applies to the classification Payments to Merchants.
1.7 The request for Return or Reversal procedures through the Bre-B Zone does not exhaust the Customer's right to initiate any procedure before other instances or channels provided by the Participant that issues their Payment Method or before other competent authorities.
1.8 The EASPBVI must require their Participants to inform Customers of the operational guidelines for the attention of frauds, errors and requests, complaints and claims of the processing of Immediate Payment Orders and/or Fund Transfers.
An originating Customer may request the return of an Immediate Payment Order and/or Fund Transfer in accordance with the following procedure:
2.1 The originating Customer requests the return from the Originating Participant, within thirty (30) calendar days following the execution of the Immediate Payment Order and/or Fund Transfer, indicating from the "Transaction History" functionality, the transaction subject to return and the cause thereof, within the following options:
Transfer sent to wrong receiving Customer
Wrong transfer amount
Transfer sent twice
The return request may be for the total amount of the Immediate Payment Order and/or Fund Transfer or may be partial. In the latter case, the amount of the request must always be less than that of the original transaction and the Originating Participant must enable a field for its Customer to enter the value whose return is requested.
The Originating Participant must send a message to its Customer informing it that advancing the Return procedure does not guarantee a positive response to the request and that the response to the Return procedure is strictly voluntary on the part of the receiving Customer.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
2.2. The Originating Participant informs the Receiving Participant of the request through the SPBVI. The Receiving Participant shall verify the status of the Payment Instrument, and if it identifies that the Payment Instrument is canceled, attached, blocked by court order, due to a deceased receiver or another cause, it must inform the Originating Participant through the SPBVI and the latter its Customer that the transaction could not be processed because the Payment Instrument of the receiving Customer is not available, concluding the Return request through this functionality.
2.3 If the Receiving Participant determines that the Payment Instrument is enabled to carry out the Return, it shall inform the receiving Customer immediately of the request received and the latter shall have five (5) calendar days to inform the Receiving Participant of its decision.
2.4 If the Receiving Customer accepts to carry out the Return of the funds, the Receiving Participant shall immediately initiate a new Immediate Payment Order and/or Funds Transfer, identifying the transaction subject to return and debiting the funds from its Customer's Payment Instrument, provided that sufficient funds exist in the Payment Instrument.
2.5 Once the Return is completed, the Receiving Participant must immediately inform its Customer and the Originating Participant of the operation through the SPBVI, identifying the operation subject to Return, so that the Originating Participant informs the originating Customer about the return. In the "Transaction History" it must be identified that the Immediate Payment Order and/or Funds Transfer was subject to Return and this request must have the status "completed", both for the originating Customer and for the receiving Customer.
2.6 In the event that the charge is partial because the funds in the Receiving Customer's Payment Instrument are insufficient, the Receiving Participant shall inform the Originating Participant through the SPBVI so that the latter informs its Customer and concludes the procedure through the Bre-B Zone. The Customer may make new claims regarding the non-restored balance before other instances or channels provided by the Originating Participant or before other competent authorities.
2.7 If the receiving Customer rejects the return or does not respond within the established period, the Receiving Participant must inform said rejection to the Originating Participant through
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
the SPBVI and the latter to its Customer immediately, concluding the return procedure.
2.8 In the "Transaction History" it must be identified that the Immediate Payment Order and/or Funds Transfer was subject to a Return request and this request has the status "completed", both for the originating Customer and for the receiving Customer.
The suggested messages to use in this case are:
Request rejected. Process completed.
Claim period for return exceeded, without response. Process completed.
Payment Instrument not available. Process completed.
For cases in which the receiving Customer of a payment rejects an Immediate Payment Order and/or Funds Transfer and wishes to return it, in whole or in part, the following procedure must be followed:
3.1 The Return is initiated by the receiving Customer, before the Receiving Participant, within thirty (30) calendar days following the execution of the Immediate Payment Order and/or Funds Transfer, indicating from the "Transaction History" functionality the transaction subject to Return and the reason for it, among the following options:
Payment/Transfer received from an unknown originating Customer.
Wrong payment/transfer value.
Payment/transfer received twice.
3.2 The Receiving Participant, once the Return order is received, shall immediately initiate a new Immediate Payment Order and/or Funds Transfer, identifying it as a Return operation, debiting the funds from the receiving Customer's Payment Instrument.
The Receiving Participant must enable the options for its receiving Customer to define the amount to return, as follows:
Total return.
Partial return (Space to enter the value).
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
3.3 The Originating Participant shall verify the status of the Payment Instrument. If it identifies that the Payment Instrument is canceled, attached, blocked by court order, due to a deceased receiver or another cause, it must inform the Receiving Participant through the SPBVI, and the latter its Customer, that the transaction could not be processed because the Payment Instrument of the originating Customer is not available, concluding the Return process through this functionality.
3.4 Once the Return has been completed, the Receiving Participant must immediately inform the receiving Client and the Originating Participant through the SPBVI, identifying the transaction subject to Return, so that the latter proceeds to inform the originating Client about it, thereby concluding the procedure.
3.5 In the "Transaction History" it must be identified that the Immediate Payment Order and/or Funds Transfer was subject to a return and this request has the status "completed".
The funds of an Immediate Payment Order and/or Funds Transfer may be subject to a Return, total or partial, when there is fraud in events other than the acquisition of products or services through electronic commerce mechanisms.
4.1 The Originating/Receiving Participant that identifies the fraud must inform the Receiving/Originating Participant of the situation through the EASPBVI. The Participants must follow their processes for fraud confirmation, including the information relevant to the Clients. The maximum investigation time may not exceed ten (10) calendar days.
4.2 In the event the fraud is confirmed, the receiving Participant shall return the funds charged to the receiving Client's Payment Method within the following (2) business days after its confirmation. The Return shall be made provided that there are funds in the Payment Method to carry it out.
4.3 The Participant shall verify only once the existence of funds in the Payment Method and the charge may be partial in the event that these are not sufficient. According to the
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
results of the fraud confirmation processes, the Originating/Receiving Participant may, at its own expense, carry out the return of the missing funds.
4.4 Once the Return has been completed, the Originating/Receiving Participant must immediately inform the originating Client and the Receiving/Originating Participant through the EASPBVI, identifying the transaction subject to Return, so that the latter proceeds to inform the originating Client about it, thereby concluding the procedure.
4.5 In the "Transaction History" it must be identified that the Immediate Payment Order and/or Funds Transfer was subject to a Return and this request has the status "completed".
In cases where it is the Clients who detect a transaction they do not recognize, they must inform the Originating or Receiving Participant so that the latter determines whether it is an Immediate Payment Order and/or Funds Transfer resulting from fraud and thus follow the procedure described above. Once the Participant has been notified by its Client, it shall be responsible for processing the request and reporting it during and upon completion of the procedure.
The funds of an Immediate Payment Order and/or Funds Transfer may be subject to a Return, total or partial, when there is an operational technology failure, identified by the Clients or by the Participants.
5.1 The Originating/Receiving Participant that identifies the technological failure must inform the Receiving/Originating Participant through the SPBVI. The Participants must follow the established processes for confirmation of the technological failure. The maximum investigation time may not exceed ten (10) calendar days counted from the date of notification by the SPBVI.
5.2 In the event the technological failure is confirmed, the Receiving Participant shall be informed, so that it makes the Return of the funds charged to the receiving Client's Payment Method. The return shall be made provided that there are funds in the Payment Method to carry it out.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
5.3 In the event that the charge of the funds in the receiving Client's Payment Method is partial, the Participant responsible for the technological failure must complete the missing funds of the Payment Order and/or Immediate Funds Transfer, so that the originating Client receives the total return of the funds subject to the failure.
5.4 If there are no funds in the receiving Client's Payment Method, the party responsible for the technological failure must make the Return of the funds to the originating Client during the following business day, after the failure has been identified, and subsequently make the charge to the receiving Client's Payment Method.
5.5 Once the cases of numerals 5.3 or 5.4 have occurred, the Receiving Participant may verify as many times as necessary the existence of funds in the receiving Client's Payment Method, until recovering the entirety of the funds subject to Return that it assumed.
5.6 Once the Return has been completed, the Receiving Participant must immediately inform the receiving Client and the Originating Participant through the EASPBVI, identifying the transaction subject to Return, so that the latter proceeds to inform the originating Client about it, thereby concluding the procedure.
5.7 In the "Transaction History" it must be identified that the Immediate Payment Order and/or Funds Transfer was subject to a Return and this request has the status "completed".
In cases where it is the Clients who detect a transaction they do not recognize, they must inform the Originating Participant or the Receiving Participant so that the latter determines whether it is an Immediate Payment Order and/or Funds Transfer resulting from a technological failure and follow the procedure described above.
When the sales of goods or services are made on a non-present basis through electronic commerce mechanisms, via an immediate payment order, this may be subject to a request for the total or partial reversal procedure by the Customer. For this case, the following procedure must be applied:
6.1 To initiate a reversal process, the originating Customer must access through the Bre-B Zone the Transaction History functionality and identify the transaction subject to reversal.
6.2 The originating Customer shall have up to five (5) business days following knowledge of the occurrence of the cause to file a request for reversal of an immediate payment order before its Originating Participant, providing for this purpose the following:
a. Identification of the transaction made in the "Transaction History".
b. Indication of any of the following causes:
i. Fraud
ii. Unsolicited operation
iii. Product purchased was not received
iv. Product delivered does not correspond to what was requested
v. Product delivered defective
c. Amount for which the reversal is requested (total or partial).
The Originating Participant must enable the options for its originating Customer to define the reversal amount, as follows:
Total reversal.
Partial reversal. (Space to enter the amount).
d. Proof of the complaint filed with the provider.
6.3 The Originating Participant must receive the originating Customer's statement indicating the fact of having returned the good when applicable and the support of the complaint filed with the receiving Customer.
6.4 The Originating Participant must send a message to its Customer informing it that proceeding with the reversal procedure will depend on compliance with the legal requirements and on the evaluation thereof made by the parties involved.
6.5 In the event of non-compliance with the provisions of numeral 6.3, the Originating Participant shall inform its Customer and shall consider the process through this functionality terminated.
6.6 In the event of compliance with the provisions previously set forth, the Originating Participant shall manage the Reversal request and shall inform of said request through the SPBVI to the Receiving Participant and this in turn to the receiving Customer.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
6.7 The Receiving Participant shall initiate the Reversal of the payment for the amount requested by the originating Customer, provided that sufficient resources exist in the Receiving Customer's Payment Method, originating a new Immediate Payment Order and/or Funds Transfer in favor of the originating Customer. The Receiving Participant shall verify the existence of resources only once and the charge may be partial in the event that these are not sufficient. In the latter case, the receiving Customer may originate a new Immediate Payment Order and/or Funds Transfer to reimburse the missing amount to the originating Customer.
6.8 Once the Reversal is completed, the Receiving Participant must immediately inform its Customer and the Originating Participant of the operation through the SPBVI, identifying the operation subject to Reversal, so that the latter proceeds to inform the originating Customer about the Reversal.
6.9 In the "Transaction History" it must be identified that the Immediate Payment Order and/or Funds Transfer was subject to Reversal and this request must have the status "completed", both for the originating Customer and for the receiving Customer.
The EASPBVI may define through their regulations policies and rules for the efficient and timely management of Reversal requests.
The Reversal procedure for Immediate Payment Orders and/or Funds Transfers reflects the process established in Law 1480 of 2011 and Decree 587 of 2016 and the norms that replace, modify, add to or regulate them. The characteristics not mentioned in this procedure must follow the provisions of the aforementioned norms.
The Participants of the EASPBVI must address petitions, complaints and claims regarding the processing of Immediate Payment Orders and/or Funds Transfers following the provisions of Law 1328 of 2009, Law 1480 of 2011, the Basic Legal Circular of the Financial Superintendence of Colombia, or Law 1755 of 2015 and the other norms that replace, modify, add to or regulate them.
1.1.1. The clocks of the systems of the Immediate Low-Value Payment System Administrators (EASPBVI) and their Participants responsible for the processing of an Immediate OP/TF must maintain permanent synchronization with the Legal Time service of the National Metrology Institute of Colombia (INM). The EASPBVI and their Participants must use the domains provided by the INM for synchronization.
1.1.2. In each new message generated within the clearing and settlement flow of an Immediate OP/TF, the EASPBVI and the Participants must preserve the time stamp information that comes from the immediately preceding received message. Likewise, the EASPBVI and the Participants shall add the corresponding new time stamps.
1.1.3. When the ISO20022 standard is used in the messaging for the clearing of Immediate OP/TF, the time stamps must be incorporated in accordance with the technical specifications defined by the BR in External Operational and Services Circular DSP-471 Subject 20: Regulation of the Operating Mechanism for Settlement (MOL) or those that modify or replace it.
1.1.4. In the case where a standard other than ISO20022 is used in the connections between the Participants and the EASPBVI, the EASPBVI must guarantee that the timestamps are incorporated in the messaging.
The EASPBVI and their Participants must include in the messaging the names and timestamps in accordance with the technical specifications defined by the BR
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
in the External Operational and Services Circular DSP- 471 Subject 20: Regulation of the Operating Mechanism for Settlement (MOL) or those that modify or replace it.
1.2.1. With respect to compliance with the 20 seconds for 99.5% of the Immediate OP/TF originated in the SPBVI referred to in literal d of numeral 5.1 of this Circular, the EASPBVI must consider the following parameters:
1.2.1.1. Its calculation must be performed on a weekly basis for all operations completed between Monday and Sunday.
1.2.1.2. For Intra-SPBVI operations, in order to guarantee compliance with the 20 seconds in 99.5% of the operations, the EASPBVI may define Service Level Agreements with their Participants on the intermediate times.
1.2.1.3. The EASPBVI must retain and store at least weekly descriptive statistics associated with the calculation of the total times and the intermediate times of the compensation and settlement flow of Immediate Payment Orders and/or Transfers.
1.3.1. The Time-out applicable to the processing of an Immediate OP/TF corresponds to forty-five (45) seconds, according to the technical specifications defined by the BR in the External Operational and Services Circular DSP- 471 Subject 20: Regulation of the Operating Mechanism for Settlement (MOL) or those that modify, replace or add to it.
1.3.2. The Time-out applicable to the processing of the Immediate OP/TF must be controlled in real time by the Originating SPBVI, the MOL and the Receiving SPBVI, in accordance with the technical specifications defined by the BR in the External Operational and Services Circular DSP- 471 Subject 20: Regulation of the Operating Mechanism for Settlement (MOL) or those that modify or replace it.
When the Time-Out defined for any of the steps of the Compensation and Settlement flow of an Immediate OP/TF is met, the Originating SPBVI, the MOL, or the Receiving SPBVI, as the case may be, must report this Time-Out in the flow responses. The EASPBVI and their Participants in each exception case must send a PACS.028 inquiry message to the MOL in order to know the status of the transaction, in accordance with the technical specifications defined by the BR in the External Operational and Services Circular DSP- 471 Subject 20: Regulation of the Operating Mechanism for Settlement (MOL) or those that modify or replace it.
1.3.3. When the Time-out is declared by the EASPBVI, it must notify its Participants and the MOL in accordance with the technical specifications defined by the BR in the External Operational and Services Circular DSP- 471 Subject 20: Regulation of the Operating Mechanism for Settlement (MOL) or those that modify or replace it. The Originating Participant must immediately notify the Ordering Party, indicating at least that the transaction could not be completed because the maximum processing time was exceeded.
1.4.1. The clocks of the systems of the EASPBVI and their Participants in charge of the Key management and resolution processes must maintain permanent synchronization with the Legal Time service of the National Institute of Metrology of Colombia (INM). The EASPBVI and their Participants must use the domains provided by the INM for synchronization.
1.4.2. The Timestamps related to the Key management and resolution processes in the Federated Directories and the Centralized Directory must be incorporated in the messaging between the Federated Directories and the Centralized Directory, in accordance with the technical specifications defined by the BR in the External Operational and Services Circular DSP- 470 Subject 19: Regulation of the Centralized Directory (DICE) or those that modify or replace it.
1.4.3. In the connections between the Participants and the EASPBVI, the EASPBVI must guarantee that the Timestamps related to the Key management and Resolution processes are incorporated in the messaging.
1.4.4.1. The Key resolution, which constitutes one of the processes prior to the compensation and settlement flow of an Immediate OP/TF, must be executed in a maximum time of five (5) seconds counted from the moment in which the Participant receives the Key Resolution request from the Ordering Party, for 99.5% of the Key Resolution requests.
1.4.4.2. The Time-out for the Key resolution is ten (10) seconds and must be controlled by the EASPBVI and the Participant, in accordance with the technical specifications defined by the BR in the External Operational and Services Circular DSP- 470 Subject 19: Regulation of the Centralized Directory (DICE) or those that modify or replace it.
In the event that the Time-out materializes, the Participant must immediately notify the Client with a message that at least indicates that the Immediate OP/TF could not be processed.
1.4.4.3. The EASPBVI and their Participants must store and collect the Timestamps of the Key resolution process in accordance with the technical specifications defined by the BR in External Operational and Services Circular DSP-470 Subject 19: Regulation of the Centralized Directory (DICE) or those that modify or replace it.
1.4.4.4. The EASPBVI must keep and store, at a minimum, weekly descriptive statistics associated with the calculation of the total times and the intermediate times of the Key resolution process that is executed both in the Federated Directories and in the Centralized Directory.
EXTERNAL REGULATORY CIRCULAR DSP-465
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
1.4.5.1. The request for a Key management process must be carried out immediately by the EASPBVI and their Participants.
The EASPBVI and their Participants must store and collect the Timestamps for Key management in accordance with the technical specifications defined by the BR in External Operational and Services Circular DSP-470 Subject 19: Regulation of the Centralized Directory (DICE) or those that modify or replace it.
1.4.5.2. The EASPBVI must keep and store, at a minimum, weekly descriptive statistics associated with the calculation of the total times and the intermediate times of the Key registration management process.
2.1.1. Error codes between the MOL and the SPBVI
a) The list of typologies and error codes for the validations performed by the MOL is the one indicated in External Operational and Services Circular DSP-471 Subject 20: Regulation of the Operational Mechanism for Settlement (MOL) or those that modify or replace it.
b) During the Clearing and Settlement process of Immediate OP/TF, the MOL validation errors will be reported to the SPBVI through ISO20022 messaging.
c) For the registration of error codes within ISO20022 messaging, the technical specifications defined by the BR in External Operational and Services Circular DSP-471 Subject 20: Regulation of the Operational Mechanism for Settlement (MOL) or those that modify or replace it must be followed.
d) The error codes from the SPBVI to the MOL must be transmitted immediately.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
a) The error codes generated between the EASPBVI and the Participants must be transmitted through the messaging standard that exists between them, and immediately.
b) The EASPBVI and their Participants must adopt the list of standardized error codes in the Clearing and Settlement flows of Immediate OP/TF that the BR defines in External Operational and Services Circular DSP-471 Subject 20: Regulation of the Operational Mechanism for Settlement (MOL), or those that modify or replace it.
Only for non-standardized error events, the EASPBVI and their Participants may add proprietary error codes in the messaging. The proprietary error codes of the EASPBVI must be reported by them to the BR according to the guidelines established in External Operational and Services Circular DSP-471 Subject 20: Regulation of the Operational Mechanism for Settlement (MOL), or those that modify or replace it.
The EASPBVI must require their Participants to comply with the following terms and conditions for notifications to Clients of the events by which the processing of an OP/TF does not conclude successfully:
2.2.1. Notifications of failure events must be sent to Clients immediately, whether they originate directly in the Participant or are transmitted from the EASPBVI.
2.2.2. Notifications of failure events 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 code is included, a basic description of the event must also be incorporated 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 OP/TF, the following guidelines must be followed:
a) The Participant that presents the unavailability must inform its Clients, at a minimum, that due to its own unavailability it cannot process Immediate OP/TF as Originating Participant and as Receiving Participant. The
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
foregoing, without prejudice to compliance with the requirements or standards regarding information to the Client, in accordance with applicable regulations.
b) Participants other than the one(s) presenting unavailability must inform their Clients, at a minimum, that the Immediate OP/TF cannot be processed due to the unavailability of the respective Participant and/or SPBVI, which has been reported through error codes in the messaging or other communications. Participants may indicate in the message to the Client the name of the Participant and/or SPBVI that presents the unavailability.
2.2.4. Initial errors that may occur when the Originating Participant applies its validations to authorize an instruction for an Immediate OP/TF and before generating its routing to the Originating SPBVI, must be managed by said Participant according to its typologies, codes, internal parameterizations and messages to the Client.
2.2.5. Participants shall have discretion to perform a conversion of the error code received from an SPBVI, the MOL or the DICE, for the purpose of communicating such errors to their Clients.
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. The procedures associated with operational reconciliation must be enabled for Participants by the EASPBVI through query mechanisms that allow, at a minimum, filters for time slots and date and time cut-offs. The EASPBVI must indicate the procedure to make the connection or access to said mechanisms.
2.3.3. The EASPBVI must instruct their Participants to execute, at a minimum, operational reconciliation processes on a daily basis every day of the week and for all transactions, regardless of their status.
2.3.4. The EASPBVI must indicate the procedure that their Participants may follow in the event of finding any discrepancy or inconsistency with respect to the processed Immediate OP/TFs.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
2.3.5. The EASPBVI must have customer service channels so that Participants can communicate in case of problems or issues when consulting the information sources necessary to execute the operational reconciliation process and/or to report issues resulting from said process.
2.3.6. The EASPBVI and the Participants must incorporate into their operational reconciliation process the procedure defined by the BR in the technical specifications for EASPBVI and Participants.
The list of typologies and error codes for the validations performed by the Centralized Directory will be incorporated in the technical specifications defined by the BR in External Operational and Services Circular DSP- 470 Subject 19: Regulation of the Centralized Directory (DICE) or those that modify or replace it.
3.1.1. The standard for the data exchange format to be used in the API-REST type interconnection referred to in literal c. of numeral 4.1.1. of this Circular must be JSON.
3.1.2. The field names and encodings to be incorporated in the body of the messaging between the Federated Directories and the Centralized Directory will be those defined by the BR in External Operational and Services Circular DSP- 470 Subject 19: Regulation of the Centralized Directory (DICE) or those that modify or replace it.
3.1.3. The connection to the Centralized Directory by the EASPBVI must follow the technical specifications defined by the BR in External Operational and Services Circular DSP- 471 Subject 20: Regulation of the Operational Mechanism for Settlement (MOL) or those that modify or replace it.
EXTERNAL REGULATORY CIRCULAR DSP-465
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
3.2.1. The standard for the data exchange format to be used in the API-REST type interconnection referred to in literal b. of numeral 5.1. of this Circular must be JSON.
3.2.2. In line with what is stated in literal b. of numeral 5.1. of this Circular regarding the use of the ISO20022 standard, the EASPBVI must implement the messaging with its respective version, according to the technical specifications defined by the BR in External Operational and Services Circular DSP-471 Subject 20: Regulation of the Operational Mechanism for Settlement (MOL) or those that modify or replace it.
3.2.3. The connection to the MOL by the EASPBVI must follow the technical specifications established by the BR in External Operational and Services Circular DSP-471 Subject 20: Regulation of the Operational Mechanism for Settlement (MOL) or those that modify or replace it.
This Annex includes the guidelines and implementation specifications for the use of the Bre-B seal/mark, developing the following aspects:
I. Objective
II. General usage guidelines
III. The Bre-B seal/mark in Digital Service Provision Channels
IV. Presentation of the Bre-B seal/mark in the QR
V. Use of the Bre-B seal/mark accompanied by images or logos of third parties
VI. Toolbox of the Bre-B seal/mark
VII. Incorrect uses of the Bre-B seal/mark.
The BR determined that to identify the provision of services related to Immediate Payment Orders and/or Fund Transfers (Immediate OP/TF) there will be a seal/mark called Bre-B, written as shown and read as “breve”, without including spaces, variations or changes in uppercase and lowercase letters.
Bre-B
The Bre-B seal is protected by industrial property1, since Bre-B (name and image) is registered as a trademark (word and mixed) before the Superintendence of Industry and Commerce - Directorate of Distinctive Signs. Registered trademarks grant the BR the exclusive right of use, as well as the power to prevent third parties from using them in deviation from the guidelines of the Bre-B regulation.
This manual has been developed with the objective that the EASPBVI and their Participants use the Bre-B seal/brand, following the guidelines and specifications established to unify the visual identity that will be used to identify, socialize, train, educate, advertise and/or promote the provision of services related to Immediate OP/TF in virtual media,
[1] External Resolution of the Board of Directors No. 6 of 2023, Article 18. Seal. (...) First paragraph. The Board of Directors shall determine the name and image of the seal and may determine the industrial property protection of the seal (...).
EXTERNAL REGULATORY CIRCULAR DSP-465
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
audiovisual and printed. For the provision of such services, the EASPBVI and their Participants must use only the name and image of the Bre-B seal/brand indicated herein.
The Bre-B seal/brand (name or image) must be present in the Service Provision Channels provided by the Participants of the SPBVI to carry out Immediate OP/TF and when communication, financial education and socialization campaigns for the services are carried out. The seal/brand may be accompanied by the logo or distinctive sign of the EASPBVI, its Participants or the latter two, taking into account the indications of this manual.
The image of the Bre-B seal/brand is made up of a typographic composition in which the uppercase "B" is slightly transformed to evoke the shape of an arrow and thus emphasize the concepts of speed, rapidity and dynamism.
The color version of the Bre-B seal/brand contains a horizontal gradient from blue to electric green from left to right.
This color version (horizontal gradient from blue to electric green) must be used only with solid backgrounds in white, violet (HEX #32005E, R50 | G0 | B94) or black:
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
Below, the minimum size allowed for the color version (horizontal gradient from blue to electric green) of the Bre-B seal/brand is indicated
Minimum printed size
Minimum digital size
The black and white versions of the Bre-B seal/brand are as follows:
Below, the minimum size allowed for the black and white versions of the Bre-B seal/brand is indicated:
Minimum printed size
Minimum digital size
Additionally, the clearance area of the Bre-B seal/brand must be complied with and respected, where the distance of the clearance area will be defined by the square shown in the diagram, with "x" being its side measurement. This means that no element external to the image of the Bre-B seal/brand may cross this area. This applies to all versions of the seal/brand, regardless of its color:
The digital color palette that will accompany the use of the Bre-B seal/brand and that must be used for all digital media, such as web pages, audiovisual, applications, presentations, among others, is the following:
The printed color palette that must be used in graphic pieces, regardless of the type of substrate or printing mechanism where the Bre-B seal/brand is used, corresponds to the following:
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
Considering the indicated palettes, other uses of the Bre-B seal/brand will be valid, both for printed and digital pieces, seeking an appropriation, as presented below:
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
The Bre-B seal/brand (image) or only its name must be incorporated in the Service Provision Channels provided by the Participants of the SPBVI to initiate an Immediate OP/TF, following the recommendations indicated in section 2. General guidelines for the use of the seal/brand of this manual.
In the location of the Bre-B zone, the image of the seal/brand for use in the digital Service Provision Channel may not be accompanied by other images or logos.
The versions of the seal/brand in solid colors such as violet (HEX #5E, R50 | G0 | B94), blue (Blue HEX #00C4FF, R0 | G196 | B255), green (HEX #00FF6D, R0 | G255 | B109), white and black may be used only in digital channels, as long as the minimum size and solid backgrounds in white, violet (HEX #32005E, R50 | G0 | B94) or black indicated below are maintained:
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
An example of the use of this version is included:
[Nota:] Note: these illustrations are references for the use of the seal/brand, therefore the shape of the container, its location, background color and size may vary as long as the clearance area and the minimum digital size indicated in section 2. General guidelines for the use of the seal/brand of this manual are maintained.
For use in digital Service Provision Channels, the clearance area and the minimum digital size indicated in section 2. General guidelines for the use of the seal/brand of this manual must also be maintained for the color version (horizontal gradient from blue to electric green):
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
[Nota:] Note: these illustrations are references for the use of the seal/mark, therefore the shape of the container, its location, background color and size may vary as long as the reserve area and the minimum digital size indicated in section 2. General guidelines for the use of the seal/mark of this manual are maintained.
Even for cases of additional menus, submenus or functionalities where the execution of Immediate OP/TF is enabled, only the name Bre-B must be included, as shown below:
[Nota:] Note: these illustrations are references for the use of the seal/mark, therefore the shape of the container, its location, background color and size may vary as long as the reserve area and the minimum digital size indicated in section 2. General guidelines for the use of the seal/mark of this manual are maintained.
EXTERNAL REGULATORY CIRCULAR DSP-465
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
The presentation piece of the QR Code must include the color version of the Bre-B seal/mark (horizontal gradient from blue to electric green) indicated in section 2. General guidelines for the use of the seal/mark of this manual, preserving the reserve area, regardless of its substrate or printing mechanism. In any case, the Bre-B seal/mark must occupy at least 5% of the total area of the piece.
[Nota:] Note: the illustrations are references for the use of the seal/mark and the presentation of a QR Code, therefore the locations, background color and sizes may vary as long as the reserve area and the minimum size of 5% for the Bre-B image are maintained.
In this presentation of the QR Code, the Bre-B seal/mark may be accompanied only by the image or logo of the Acquirer and/or the SPBVI. The size of the Bre-B seal/mark must always be greater than or equal to that of the other image or logo included.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
Note: the illustrations are references for the use of the seal/mark and the presentation of a QR Code, therefore the locations, background color and sizes may vary as long as the reserve area and the minimum size of 5% for the Bre-B image are maintained.
For other types of "talkers" or "tent-cards" in which Keys are displayed instead of the QR Code, the same guidelines for the use of Bre-B incorporated in this section must be followed.
When the Bre-B seal/mark is required to be accompanied by one or more images or logos of third parties, said images or logos must be located to the right side or below the Bre-B seal, as applicable, respecting the reserve indicated in numeral 2. General guidelines for the use of the seal/mark of this manual.
The size of the Bre-B seal/mark must be greater than or equal to that of the other images or logos that accompany it, depending on the graphic piece in which they are applied. If the image or logo of the Participant and of the SPBVI is incorporated, the latter must be presented in the same proportion and scale.
When the Bre-B seal/mark is accompanied by the image or logo of the Acquirer and/or the SPBVI horizontally, the latter must have at most the same height as Bre-B. When they accompany it vertically, they must have at most the same width as Bre-B.
Example of the Bre-B seal/mark accompanied by a single image or logo, horizontal arrangement:
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
Example of the Bre-B seal/mark accompanied by a single image or logo, vertical arrangement:
Example of the Bre-B seal/mark accompanied by more than one image or logo, horizontal arrangement:
Example of the Bre-B seal/mark accompanied by more than one image or logo, vertical arrangement:
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
The Bre-B seal/mark may be used in the pieces designed or developed to support education, dissemination, promotion campaigns and other communication initiatives of the Immediate OP/TF service by the EASPBVI and their Participants. When the Bre-B seal/mark is accompanied by other images or logos, the guidelines and specifications indicated in this manual must be implemented and followed.
When the pieces include the distinctive image or logo of the EASPBVI or of the Participants supervised by the Superintendencia Financiera de Colombia, the provisions of Annex 1 of Chapter I of Title III of Part I of the Basic Legal Circular of the aforementioned Superintendencia must be complied with.
Below are some examples of pieces with the use of the Bre-B seal/mark accompanied by other images or logos:
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
The EASPBVI and their Participants will use the Bre-B seal/mark, taking into account the following:
6.1.1. Use the Bre-B seal/mark, including the resources of the toolbox, as established by the official documentation and this Manual of Use.
6.1.2. In the event that the Bre-B seal/mark is used by the EASPBVI, its Participants and/or their allies or related third parties, such use must be to identify or relate the functionality and Access Technologies that allow people in Colombia to make payments or transfers immediately and interoperably, clearly differentiating it from the good or service offered by the Participant, its allies or related third parties, in such a way that no confusion is generated among customers between the nature of the good or service offered and the Immediate Payment Order or Funds Transfer identified with the Bre-B seal/mark.
6.1.3. In general, in advertising strategies, use the Bre-B seal/mark in such a way that, for customers and users, it is clearly identifiable with the functionality of immediate and interoperable payments or transfers, including its Access Technologies.
6.1.4. Do not use expressions that, together with the Bre-B seal/mark, suggest or give the appearance that the BR or Bre-B has alliances, links or commercial agreements with third parties, customers or merchants, or that in any way endorse them.
6.1.5. Do not make modifications, transformations or additions to the logo or name of the Bre-B seal/mark.
6.1.6. Extend the above indications on the use of the Bre-B seal/mark to its merchants, customers, allies or related third parties, verifying that improper uses that confuse or may confuse the public are avoided.
6.1.7. Take reasonable steps to seek the correction or cessation of uses of the Bre-B seal/mark contrary to the guidelines set forth in this Manual, carried out by the EASPBVI, its Participants and/or their allies or related third parties.
The toolkit is a set of resources, guidelines and design elements that allow the correct implementation and use of this manual by the EASPBVI and its Participants. The BR will deliver the Bre-B seal/mark toolkit to the EASPBVI, who in turn will forward it to their Participants guaranteeing its proper use. In
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
the event of updates to the toolkit, the BR will inform the EASPBVI and will deliver the updated resources or elements to them.
The Bre-B seal/mark may not be subject to any of the following alterations, which are considered improper uses of the seal/mark:
Alter the typography, size or composition.
Tilt, distort, invert or change the direction of any graphic element.
Change or invert the colors of any graphic element.
Rotate, spin, or animate, changing the arrangement of any graphic element.
Add borders or additional elements to the Bre-B seal/mark.
Use the Bre-B seal/mark at a size smaller than allowed.
Incorrectly use the resources provided in the toolkit and, consequently, affect the quality and sharpness of the Bre-B seal/mark.
Use low-contrast backgrounds.
Excess transparency.
Below are some improper uses of the Bre-B seal/mark:
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
For the purposes of this Annex, the following definition shall be taken into account, regardless of whether the term is used in the singular or plural:
Identifier: is that linked to a Payment Method in immediate payment services through an SPBVI, prior to the start of operation of the Centralized Directory, and that coincides with any of the types of Keys described in numeral 3.4.2. of this Circular.
Phases 3, 4 and 5 mentioned in this Annex are those provided in numeral 9 of this Circular.
The following are the guidelines for the transitional application of some provisions of Regulatory Circular DSP-465 and its Annexes:
1.1. During Phase 4, once the Centralized Directory enters operation, the processes for registration, modification and cancellation of Keys must be available, following the guidelines described in Annex 1 of this Circular, for Person-to-Person Payments and Payments to Merchants. The other Key management processes described in Annex 1 of this Circular shall only be enabled as of Phase 5.
1.2. During Phase 4, once the Centralized Directory enters operation, and during the first seven (7) months of Phase 5, Participants may enable all or some of the types of Keys to process Payments to Merchants. All types of Keys must be enabled for Payments to Merchants no later than seven (7) months after the start of Phase 5, following the schedule defined by the BR and presented in the Immediate Payments Interoperability Committee.
1.3. The SPBVI must register in their Federated Directories the Keys of the Payment Orders and/or Funds Transfers they process according to the classification provided in numeral 3.3. of this Circular. This guideline shall apply during the first six (6) months after the start of Phase 5.
1.4. In the first two (2) months of the start of Phase 5, the Participant must define, for each classification of Immediate Payment Orders and/or Funds Transfers, in accordance
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
with the provisions of numeral 3.3. of this Circular, the SPBVI through which it will perform synchronization for the Key management processes with the Centralized Directory. The SPBVI must define the operational or technological mechanism for Participants to indicate the selected Federated Directory to synchronize information with the Centralized Directory.
After these (2) two months, the Participant must comply with the guideline of literal f. of numeral 3.4.1 of this Circular.
1.5. The EASPBVI must require their Participants to implement the developments for the blocking of Keys and their associated activities, as described in literal a. of numeral 3.4.4. of this Circular no later than 31 March 2027.
1.6. The provisions referred to in literals j. and k. of subnumeral 4.1.2. of this Circular, related to the structure of the Federated Directory, must be implemented in accordance with the operational and technical guidelines and the schedule defined by the BR within the framework of the Immediate Payments Interoperability Committee. This implementation must be completed no later than 30 September 2027.
1.7. The provisions referred to in literal e. of numeral 3.4.5. of this Circular, related to the rules for providing security to Customer data obtained through the Key Resolution process, must be complied with no later than 31 March 2027.
2.1. The obligations established in point 1 of numeral 3.4.7 of this Circular must be complied with no later than seven (7) months after the start of Phase 5, following the schedule defined by the BR and presented at the Immediate Payments Interoperability Committee.
2.2. The replacement of QR Code representations in use must be carried out no later than eighteen (18) months after the start of Phase 5 to incorporate:
a. The Bre-B image, in accordance with the specifications of numeral 4 of Annex 6 of this Circular.
b. The Keys, in the fields of the QR Code, in accordance with the specifications of Table 1 of this Circular.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
2.3. During the time of the replacement process referred to in the previous numeral, the SPBVI and their Participants must guarantee the reading of the QR Code, recognizing the specifications of Table 1 of this Circular.
2.4 All new QR Code representations generated from Phase 5 onwards must include the Bre-B image, in accordance with the specifications of numeral 4 of Annex 6 of this Circular, and the Keys, in the fields of the QR Code, in accordance with the specifications of Table 1 of this Circular. In any case, only from Phase 5 onwards may the Bre-B image be displayed in such representations.
3.1. During Phase 4, once the Centralized Directory enters into operation, the only functionality that must be available in the Bre-B Zone shall be that associated with the Key management processes. Such processes must be enabled in accordance with the provisions of numeral 1.1. of this Annex.
3.2. The requests, complaints and claims functionality described in Annex 3 of this Circular must be available to Customers in the Bre-B Zone eight (8) months after the start of Phase 5.
The Return and Reversal procedures described in Annex 4 of this Circular must be implemented according to the technical specifications, conditions and schedule defined by the BR.
In any case, Participants must manage returns, reversals, and requests, complaints and claims through the procedures they currently have established.
3.3. The provisions referred to in literal b. of numeral 2.2.3. of Annex 5 of this Circular, related to the terms and conditions for notifications of failure events to Customers, must be complied with by Participants according to the schedule defined by the BR and presented at the Immediate Payments Interoperability Committee or, in advance, as soon as possible from 6 August 2026.
3.4. The provisions referred to in the final paragraph of numeral 2 of Annex 3, related to the experience of the Customer that is a legal entity, must be complied with by Participants no later than 30 June 2027.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
3.5. The provision referred to in the second paragraph of numeral 3.2 of this Circular, related to the notification to the Customer of the limits established by the Participants, must be complied with by the Participants no later than 30 June 2027.
3.6. The provision referred to in the third paragraph of numeral 3.2 of this Circular, related to the homologation of the limits established by the Participants, must be complied with by the Participants no later than 30 November 2027.
3.7. The provisions referred to in literal e. of numeral 6 and Annex 3 of this Circular, related to the provision of the trade name to Customers, must be complied with by the Participants no later than 30 September 2027.
During Phase 4, once the Centralized Directory enters into operation, the Key registration process must follow the provisions of numeral 9 of Annex 3 of this Circular. The registration of Keys for Person-to-Person Payments must be carried out directly and exclusively by the Customer, except in the case provided for in numeral 4.1.1 of this Annex. For Person-to-Person Payments, the Key registration process may only be carried out from the entry into operation of the Centralized Directory in Phase 4.
In order to give continuity to the Immediate Payment Orders and/or Fund Transfers of Clients that have used immediate payment services through a SPBVI prior to the start of operation of the Centralized Directory, the following transition measures are designed:
If prior to the start of operation of the Centralized Directory the Client has one or several Identifiers that match the type of alphanumeric Key and its structure described in numeral 3.4.2. and in Table 1 of this Circular, during Phase 4, the Participant may request the SPBVIs that have the databases of the Identifiers to upload the Identifiers as Keys, in accordance with the following terms:
a. The registration will be carried out for the Identifiers that meet the following conditions:
i. Be associated with a single Payment Method.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
ii. Have been used to originate or receive at least one (1) operation in the six (6) months prior to the entry into operation of the Centralized Directory.
b. The EASPBVI will validate that the registration is carried out only for the Identifiers that meet the conditions established in literal a. of this numeral.
c. The Identifiers will be registered as Keys in the Federated Directory and in the Centralized Directory.
d. The SPBVI must register one Identifier at a time and sequentially, following the times and operational guidelines defined by the BR.
e. During the process described in this numeral, the application of the rule established in literal d. of numeral 3.4.1 of this Circular will be guaranteed.
f. The Participants must promptly inform the respective Clients of the Identifiers that were registered as Keys in Bre-B.
g. After the registration is made, the Clients may carry out the other Key management processes, as established in numeral 1.1 of this Annex.
If prior to the start of operation of the Centralized Directory the Client has one or several Identifiers that match the types of Key and their structure described in numeral 3.4.2. and in Table 1 of this Circular and did not register them as a Key during Phase 4, nor were they subject to the registration described in numeral 4.1.1 of this Annex, the Participant may request the SPBVIs that have the databases of the Identifiers to upload the Identifiers as Keys in Phase 5, before the entry into operation of the Operational Mechanism for Settlement, in accordance with the following terms:
a. The registration will be carried out for the Identifiers that meet the following conditions:
i. Be associated with a single Payment Method.
ii. Have been used to originate or receive at least one (1) operation in the six (6) months prior to the day of the start of Phase 5.
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
b. The EASPBVI will validate that the registration is carried out only for the Identifiers that meet the conditions established in literal a. of this numeral.
c. The Identifiers will be registered as Keys in the Federated Directory and in the Centralized Directory.
d. The SPBVI must register one Identifier at a time and sequentially, following the times and operational guidelines defined by the BR.
e. During the process described in this numeral, the application of the rule established in literal d. of numeral 3.4.1 of this Circular will be guaranteed.
f. The Participants must promptly inform the respective Clients of the Identifiers that were registered as Keys in Bre-B.
g. After the registration is made, the Clients may carry out the other Key management processes, as established in numeral 1.1 of this Annex.
Once the registration of Identifiers as Keys of numeral 4.1.2. of this Annex is completed and before the entry into operation of the Operational Mechanism for Settlement, each Participant may assign an alphanumeric Key to the active Payment Methods for which the Client did not register a Key as of the entry into operation of the Centralized Directory during Phase 4 and which were also not subject to the registration of Identifiers as Keys as described in numerals 4.1.1. and 4.1.2.
For the purposes of this provision, a Payment Method is considered active when any operation has been carried out on it in the six (6) months prior to the start of Phase 5. Operation is understood as provided in numeral 1.2.2. of Chapter III, Title I, Part II of the Basic Legal Circular of the Financial Superintendence of Colombia.
The assignment and registration of alphanumeric Keys for Person-to-Person Payments will be carried out in accordance with the following terms:
a. The alphanumeric Key must comply with the structure defined for this type of Key in Table 1 of this Circular.
b. The alphanumeric Keys will be registered in the Federated Directory and in the Centralized Directory.
c. During the process described in this numeral, the application of the rule established in literal d. of numeral 3.4.1 of this Circular will be guaranteed.
d. The BR will define the times and operational guidelines necessary for the registration of the alphanumeric Keys.
e. After the registration has been made, Clients may proceed with the other Key management processes, as established in numeral 1.1 of this Annex.
The processes indicated in numerals 4.1.1. and 4.1.2. of this Annex are excepted from the provisions established in literal e. of numeral 3.4.1. of this Circular and therefore each SPBVI shall carry out the registration of Identifiers as Keys for the population of the Centralized Directory, according to the operational guidelines defined by the BR.
In any case, once each of these processes has ended and prior to the start of the operation of the Operational Mechanism for Settlement, when a Participant is linked to more than one SPBVI and uses in said systems the same classification of Payment Orders and/or Fund Transfers in accordance with the provisions of numeral 3.3. of this Circular, the Participant must guarantee that the Federated Directories of these SPBVIs are updated with the applicable Keys.
During Phase 3, the EASPBVIs and/or their Participants may carry out education and socialization processes regarding Bre-B with respect to its general characteristics. In the same Phase, the BR shall define the guidelines related to the promotion strategy applicable to Phases 4 and 5, for which it may take into account the recommendations of the Immediate Payments Interoperability Committee.
In these education and socialization processes, all types of Keys must be promoted under equal conditions.
CIRCULAR REGLAMENTARIA EXTERNA DSP-465
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
The SPBVIs must participate in the tests and dry runs associated with the Operational Mechanism for Settlement and the Centralized Directory prior to the start of Phase 5, in accordance with the times and guidelines established by the BR.
The provisions referred to in literals c. of subnumerals 3.4.7. and 6.1., related to the Payment Reference, and those included in Annex 3 of this Circular regarding this functionality, must be implemented in accordance with the operational and technical guidelines and the schedule defined by the BR within the framework of the Immediate Payments Interoperability Committee. This implementation shall be completed no later than 31 August 2027.
The provisions referred to in the fourth paragraph of numeral 10 of this Circular, related to the information to the BR on new Value-Added Services, shall apply as of 1 January 2027.
The EASPBVIs must comply with the provisions referred to in literal i. of numeral 4.1.1. and j. of numeral 5.1. of this Circular as of 1 June 2027.
The EASPBVIs must require in their Regulations that their Participants that do not offer Payment Methods, whether or not they are supervised by the Superintendencia Financiera de Colombia or the Superintendencia de la Economía Solidaria, comply with the regulation on Interoperability and, additionally, the following obligations:
a. Not having a Bre-B Zone.
b. Carrying out the management processes of the Key(s) in their name from the Service Provision Channels made available by the Participant that offers Payment Methods of which this Participant is a Client, or through the EASPBVI to which this Participant is linked. The Key(s) must be associated with the Payment Methods of which this Participant is the holder and must include in the field "Identification of the Issuing Entity" the NIT of the Participant that does not offer Payment Methods.
c. When a Participant that does not offer Payment Methods acts as Beneficiary of an Immediate Payment Order and/or Fund Transfer, it must clearly and precisely inform its Clients of the Key data, amount and Payment Reference, where applicable, or the possibility of reading the QR Code, under the terms of this Circular, so that the Ordering Client initiates the Immediate Payment Order and/or Fund Transfer from the Bre-B Zone or the functionalities made available by its Originating Entity.
d. When a Participant that does not offer Payment Methods carries out the activity of merchant aggregation, it must inform its Clients, allies and/or linked third parties, clearly and transparently, that the service for processing Immediate Payment Orders and/or Fund Transfers is provided through Bre-B, using a Key associated with the Payment Method owned by this Participant.
e. Participants that do not offer Payment Methods may be Ordering Parties and/or Beneficiaries of Immediate Payment Orders and/or Fund Transfers, from and to, a Payment Method of which they are the holder, in accordance with their business model.
f. For purposes of the Settlement of Immediate Payment Orders and/or Fund Transfers of Participants that do not offer Payment Methods, these shall have the status
Date: Friday, 20 November 2026
Subject 18: Interoperability of Immediate Low-Value Payment Systems.
of Indirect Participants under the terms provided in the Circular Externa Operativa y de Servicios DSP-471 and must comply with the corresponding technical and operational requirements. The foregoing, without prejudice to compliance with the other provisions applicable to them regarding the interoperability of immediate low-value payment systems.
The EASPBVI must ensure compliance with the provisions set forth in the preceding subparagraphs.
Note from RegAlert. AI assistants can read this document in full, and search 70,000+ more, through the RegAlert MCP connector (https://mcp.regalert.today/mcp). Free with an account. How to connect ChatGPT, Claude or Cursor.
RegAlert holds no document that amends or replaces this one. This is not a check that it is in force: confirm with the regulator.
“This Circular regulates External Resolution No. 6 of 31 October 2023 issued by the Board of Directors of the Banco de la República”
“This bulletin is published in accordance with the provisions of literal a) of article 51 of Law 31 of 1992”
“and the paragraph of article 108 of Law 510 of 1999.”
More like this from BANREP
BANREP published 6 documents in the last 30 days. We email you each new one the day it's published.
Source: Banco de la Republica Colombia — original document · Summary generated with machine assistance and checked by an AI reviewer before publication; the authoritative text is the regulator's original document. How RegAlert works
In RegAlert: added