PAFA
Argentine Open Finance Profile
Decree 353/2025 created the Open Finance System and left it to the BCRA, the central bank, to define its standards; however, there is still no official regulation. PAFA is an independent proposal that seeks to translate what other countries have learned into a regulatory framework that could apply in Argentina.
Read the introduction to PAFA →Actors
Ecosystem participants
Each country names them differently —data holder, ASPSP, instituição transmissora—, but the roles are the same. PAFA describes itself using a generic taxonomy.
Read the introduction to PAFA →In the exchange
-
01
Data owner
The person who owns the data. The one who grants and revokes permissions.
-
02
Transmitting entity
Holds the data and shares it with the owner’s prior consent. For example, a bank or a digital wallet.
-
03
Receiving entity
Requests that data to analyse it, possibly in order to offer the owner a new product or service.
Holding it up
-
04
Directory
The technical register: who takes part, with which role, in what status and with which keys.
-
05
Certification authority
Issues the certificates with which each entity proves it belongs to the system.
-
06
Regulator
Sets the standards and requirements. In Argentina, the BCRA (Decree 353/2025).
The profile proposes that the participant is always the entity, so, for the purposes of the profile, a technology provider is not an active actor.
Architecture
Five layers
The protocols already exist and are proven —OAuth 2.0, OpenID Connect, FAPI 2.0, mTLS—; what each country decides is how they are combined. PAFA arranges those decisions in five layers, trying to answer the questions that come up in each one.
-
Layer 5
Governance
Who admits participants, under which rules, and how disputes will be handled. In Argentina, the BCRA.
-
Layer 4
Observability
Observability is not just counting active consents or API calls: it is measuring the impact on the system.
-
Layer 3
Resources
What is exposed about an account and in which format, such as the standardized identifiers that will be used.
-
Layer 2
Authentication, consent and authorization
How the data owner gives consent, with what scope and for how long, and how they revoke it.
-
Layer 1
Identity and trust between participants
How two entities that do not know each other prove they belong to the system: the directory, the roles and the certification authorities.
Audit · What gets recorded? Not only must every action be attributable to an entity and recorded so that it cannot be altered: it must also be possible to rebuild the history when there is a dispute.
FAQs
Is PAFA official?
No. It is independent work, with no ties to the BCRA or to any entity. Regulation is the BCRA’s job; PAFA is a contribution to that discussion.
Why write it before the rule?
Because after the rule the design is no longer discussed, only compliance is. A proposal is useful while the decisions are still open.
Why not adopt another country’s profile?
Protocols get adopted; decisions, not entirely. Each profile answers to its own regulation, and part of what other countries had to solve, Argentina has already solved, such as the UIF’s remote identification. PAFA looks at Brazil, the United Kingdom, Australia, Chile, Colombia, Peru and India, among others, and tries to adapt them to the Argentine ecosystem.
Is it ready to implement?
A test environment is being built; the first entities to integrate with it are being sought.
How to take part?
Ideas, feedback and issues in the repository are all welcome.
Contact
The technical side of the profile lives in a public repository, open to review. Any contribution, question or correction is welcome.