The reform arrived with an immediate transitional obligation. Registered PSPCPs already offering the PSPCP-como-Servicio model had 10 business days from 30 April 2026 to report to the BCRA the full list of third-party entities they serve, including each entity's name, CUIT, and a description of the service provided — a disclosure exercise designed to give the regulator visibility into arrangements that had grown up ahead of a dedicated licensing category.
The BCRA has also hardened the PSP registration process itself. Naming of a compliance officer, titular and suplente, before the UIF, together with a sworn declaration of scope, is now required for PSP registration. And the registration decision process will now weigh prior UIF fines or BCRA, CNV, or SSN disqualification, suspension or revocation — a fit-and-proper standard that did not previously attach explicitly to new PSP entrants.
Read together, these three elements describe a central bank moving to close a regulatory gap around embedded-finance and white-label wallet arrangements by formally categorising and regulating the PSPCP-as-Service model, layering compliance-officer, beneficial-ownership and fit-and-proper requirements onto an already-growing digital-wallet market. This is the highest-confidence development of the cycle and the one most likely to reshape how third-party wallet arrangements are structured and reported in Argentina going forward.
Other Developments
The conduct dimension of the reform carries its own liability allocation, distinct from the licensing category itself. End clients acquired through a third-party interface are legally deemed clients of the registered or principal PSPCP, which retains full regulatory responsibility including KYC, information security, and operational continuity. In practice, this means the entity holding the PSPCP-como-Servicio registration cannot delegate away its core conduct obligations merely because the end-user relationship is mediated through a third-party brand or interface.
Local press coverage has characterised A 8432/2026 as the BCRA 'hardening controls' on a fintech market that 'grew rapidly' — a framing that positions the reform as a structural response to the scale digital wallets and embedded-finance intermediaries have reached in the Argentine market, rather than a routine housekeeping update. A separate reading, oriented toward product innovation, treats the same reform as a formal regulatory recognition of the embedded-finance and white-label wallet model: the new PSPCP-como-Servicio figure gives a defined legal home to arrangements that previously operated without a dedicated category, which some commentary frames as validating rather than merely constraining the underlying business model.
Running alongside the conduct reform, and sourced from a separate BCRA communication, is a new settlement-transparency requirement. Comunicación A 8427 created a monthly report of intra-entity immediate transfers for financial institutions and PSPCPs, applying from the August 2026 information period. This reporting obligation is distinct from the PSPCP-como-Servicio conduct changes in A 8432/2026, but it adds to the same broader pattern this cycle: the BCRA extending its visibility into both the structure of third-party wallet arrangements and the transaction flows moving through regulated payment entities.
Cross-Monitor Connections
The new requirement to name a compliance officer before the UIF and file a sworn declaration of scope as part of PSP registration sits at the boundary between payments licensing and financial-crime oversight infrastructure. This cycle's Argentina coverage treats that requirement as a payments-governance hardening measure rather than a first-party anti-money-laundering finding: no dedicated AML/CFT analysis was generated for Argentina this cycle, and no cross-monitor flags were raised linking the PSPCP-como-Servicio reform to illicit-finance activity. Any future assessment of how the UIF-facing compliance-officer requirement interacts with Argentina's broader financial-crime supervision would fall to a dedicated financial-integrity review rather than to this payments-regulatory brief.
Outlook
Two concrete dates anchor the near-term calendar. The disclosure window for registered PSPCPs already operating the served-third-party model has now closed, and the item to watch is the BCRA's follow-through — whether the disclosures prompt further guidance, enforcement action, or a wave of new registrations under the PSPCP-como-Servicio category as previously unregistered arrangements seek to formalise their status.
Further out, the monthly intra-entity immediate-transfer reporting obligation becomes live later this year. Its early filings will be the first practical test of how the BCRA's expanded settlement-transparency layer interacts with the newly categorised PSPCP-como-Servicio population, and whether the two reforms — one aimed at conduct and licensing, the other at transaction reporting — begin to function as a combined supervisory picture of third-party wallet activity.
A further marker for coming cycles is whether the fit-and-proper hardening in the registration process becomes visible in the treatment of new-entrant applications, which would signal that the reform is shaping market entry in practice and not only on paper.