A remote sign-up has to prove itself.

What digital onboarding requires in Argentina

Customer sign-up through digital channels is provided for and is common practice in the Argentine financial system. For financial institutions, the BCRA allows fully remote onboarding and sets conditions on how it is done (Communications "A" 6059 and 6223, now incorporated into the consolidated rules on savings deposits and current accounts); for the rest of obligated parties, the requirement comes from the UIF, which defines what has to be known about the customer regardless of the channel through which they come to be known.

The identification standard does not drop because the channel is digital. What changes is how it is proven.

In an in-person onboarding, the evidence is an employee who looked at a document and a person. In a digital onboarding there is no witness: the evidence is the record of the process itself. That is why traceability stops being a technical detail and becomes the central requirement.

A compliant digital sign-up settles four things and leaves a record of each one.

• That the document presented is authentic — full reading and validation of its elements, not just the number.
• That the person is the one on the document — biometric matching of the captured face against the one on the document.
• That this person is present and alive — liveness detection at the moment of capture.
• That the declared data is consistent — cross-checking against the available sources and against the applicable restricted lists.

Added to that are two obligations specific to the digital channel that tend to be treated as a formality:

• Data processing. Everything the sign-up captures, including biometrics, falls under Argentina's personal data protection regime: a specific purpose, a legal basis for processing, notice to the data subject and proportionate security measures. It runs in parallel with the anti-money laundering regime and is not met by meeting the other.
• Retention. The evidence of the process has to remain available to the supervisor for the period the law sets, in a format that can be shown years later.

What VU automates in digital onboarding

VU handles the verification steps of the sign-up and the evidence they leave.

• The verification steps — reading of the Argentine document, biometric matching and liveness detection, within a single flow.
• Orchestration — the order of the steps, retries, timeouts, the quorum between checks and what happens when one does not complete. This is where a remote sign-up breaks down in practice, long before recognition accuracy does.
• The trail — what ran, with what result and when, retained as evidence of the process.
• Continuity into access — the identity verified at sign-up remains available to authenticate that person later, so the first login does not start from scratch again.

And what VU does not do:

• It does not design the commercial flow of the sign-up. What is requested, in what order and what can be deferred is a business and risk decision for the obligated party.
• It does not decide who is accepted. The acceptance policy and the risk matrix are internal, and the law requires them of the obligated party, not of its provider.
• It does not replace consent or the privacy notice. The legal basis for processing the data, the notice to the data subject and the declared purpose are obligations of the data controller.
• It does not retain the regulatory customer file on its own. VU produces evidence; what is retained, where and for how long is decided by compliance.
• It does not, on its own, handle the onboarding of legal entities. Verifying the individuals involved is part of the work; corporate analysis is something else and belongs in AML.

Use cases in Argentina

Where this problem shows up in the real operation of the Argentine market.

• Wallets and accounts opened from a phone. Remote sign-up is the default channel, and competition plays out in the minutes it takes and in how many legitimate users are left out.

• Financial institutions with a dual requirement. They have to satisfy the BCRA and the UIF with the same process, and each one looks at a different part of the same evidence.

• Sign-ups stuck in manual review. The real cost of digital onboarding is not in the happy path but in the exception queue, which grows with every document the flow does not account for.

• Five generations of DNI in circulation. A sign-up that assumes a single document type starts failing with the less common generations and with the newest one at the same time.

• Migrating customers onboarded at a branch. Portfolios signed up when the standard of evidence was different, which have to be updated without forcing anyone back to the counter.

• Sign-ups started and abandoned. Every step that asks for one more attempt loses people, and the design question is which of the checks can be retried without starting everything over.