dLocal incident

[VR Benefícios] Apparent incident with payment processing in Brazil

Minor Resolved View vendor source →

dLocal experienced a minor incident on June 21, 2026 affecting Brazil - Payment Processors, lasting 1d. The incident has been resolved; the full update timeline is below.

Started
Jun 21, 2026, 01:37 PM UTC
Resolved
Jun 22, 2026, 02:29 PM UTC
Duration
1d
Detected by Pingoru
Jun 21, 2026, 01:37 PM UTC

Affected components

Brazil - Payment Processors

Update timeline

  1. investigating Jun 21, 2026, 01:37 PM UTC

    We have identified some processing issues with Yuno in Brazil. We have contacted the processor and we will provide an update as soon as it becomes available.

  2. investigating Jun 21, 2026, 02:51 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jun 21, 2026, 05:04 PM UTC

    We are checking the incident with the provider. We will provide you with updates as soon as possible

  4. investigating Jun 21, 2026, 07:23 PM UTC

    We are continuing to investigate this issue with the provider, we will provide more updates as soon as we have them

  5. investigating Jun 22, 2026, 01:37 AM UTC

    Processor reached out to VR and are currently awaiting their response, and will keep you posted as soon as we receive an update from their team

  6. investigating Jun 22, 2026, 09:19 AM UTC

    Processor's update : Root cause (VR side): The affected transactions are being declined by the underlying provider (VR Benefícios) due to a document validation error: "Documento inválido: informe um CPF (11), CNO (12), CNPJ (14) válido, ou VRSC (8)". Starting at 08:37 UTC (05:37 BRT) on 21-Jun, the provider began enforcing the customer document (CPF/CNPJ) as a mandatory field, where it was previously accepted as optional. This is what is driving the 0% approval rate; the other provider in Brazil continues to operate normally. We verified that Yuno's payload did not change at 08:37 UTC. The last successful transaction (08:33 UTC, ~4 minutes before the incident) was submitted with the same null document field as the transactions now being rejected, and there were no relevant deployments on our side around that time. We also compared successful vs. declined traces and ruled out our integration as the trigger. The change is on the provider's validation side. Current status: We have raised and escalated this with the provider as urgent and are following up repeatedly to get their confirmation and an ETA. We have not yet received their response and are continuing to push over all channels with them. We will keep you updated as soon as we hear back from VR.

  7. investigating Jun 22, 2026, 12:55 PM UTC

    The processor has been in touch with VR to check the status on their side. We will keep you posted

  8. resolved Jun 22, 2026, 02:29 PM UTC

    This incident has been resolved.