Skip to main content
A charge that carries your own 3DS provider’s evidence is rejected — either the evidence itself is wrong, or your outlet isn’t allowed to submit it this way.
TL;DR — Confirm enablement first; re-authenticate with your provider rather than resubmitting the same evidence; never charge on an unconfirmed result.

When this happens

  • The acquirer requires 3DS for this channel and the three_ds you sent doesn’t show an authentication — 422 urn:radiumone:payment-gateway:three-ds:authentication-required. That includes no three_ds at all, mode: "unauthenticated", a NOT_AUTHENTICATED RadiumOne reference, and a result from your own 3D Secure provider that isn’t a successful authentication for the card’s scheme: no cavv, an eci that means failed or not authenticated (for example 07 or 00), an eci from another scheme’s table, or any result on a Discover, UnionPay, or unrecognized card (charge those with a RadiumOne 3D Secure reference instead). The requirement never applies to standalone refunds.
  • Your outlet isn’t enabled to submit your own provider’s evidence — 422 urn:radiumone:payment-gateway:three-ds:external-auth-not-permitted. This path is off by default: request enablement for each outlet that uses it.
  • None of the terminals that could take the payment is enabled for card details — 409 routing:raw-card-not-permitted. Nothing is sent or charged; request enablement for card details on your terminals.
  • The three_ds evidence object has a missing, too-long, or unrecognized field, or doesn’t hold together — 400 validation-error. For example: result fields without mode: "external_auth", a missing eci, ds_transaction_id, or version, authentication_status: "Y" without a cavv, or an authentication_status or cavv that doesn’t fit the card’s scheme (pointer /three_ds/authentication_status or /three_ds/cavv; the value is never echoed).

What you see

What to do

1

Confirm enablement before you rely on this path

See Use your own 3DS provider: before you begin. Without enablement, the charge is rejected.
2

Re-authenticate rather than resubmit the same evidence

A urn:radiumone:payment-gateway:three-ds:authentication-required result means the charge needs a fresh, successful authentication from your provider — resubmitting the same (failed or missing) evidence won’t change the outcome.
3

Never charge on an unconfirmed result

Charge only after your own provider has returned a verified result for this specific attempt — see Server policy.
4

Fix the evidence shape for a validation error

Check field lengths and that you’re not sending an unrecognized key inside the three_ds object (API reference):

Use your own 3DS provider

The full guide, including ECI values and limitations.

Authentication results

The full 3DS error reference with HTTP codes and remedies.

Problem format and retries

The error shape, status guide, and retry rules.
Last modified on October 30, 2026