3DS Authentication Failure

What to do

• Check whether you use Marqeta 3DS. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 4m it lasted.

  Anything that failed between 2026-10-14 09:20 UTC and 2026-10-14 10:24 UTC may need a replay.

• Subscribe to Marqeta's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=marqeta works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

We are actively investigating the root cause and will provide another update as soon as more information becomes available.

Updates from Marqeta 2

1. investigatingOct 14, 2026, 9:20 AM UTC

   Marqeta engineers have identified an issue where 3DS authentication requests are missing the user token field across a subset of customer programs. While frictionless authentications are succeeding, authentications requiring a challenge may fail. We are actively investigating the root cause and will provide another update as soon as more information becomes available.

   provider

2. resolvedOct 14, 2026, 10:24 AM UTC

   Marqeta engineers identified the root cause as a recent change, which has since been reverted. All 3DS authentication flows are operating normally with no further impact.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.