> For the complete documentation index, see [llms.txt](https://plexo.gitbook.io/rest-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://plexo.gitbook.io/rest-api/reference/3ds-statuses.md).

# 3DS Authentication Statuses

This page lists the current canonical 3DS session statuses used by the backend.

## Status values

| Status             | Meaning                                                                        | Typical integration action                                            |
| ------------------ | ------------------------------------------------------------------------------ | --------------------------------------------------------------------- |
| `init`             | The 3DS session was created but authentication has not started yet.            | Wait for the next 3DS step to begin.                                  |
| `pending`          | Authentication is in progress.                                                 | Wait for the next callback, redirect result, or session update.       |
| `authenticated`    | The cardholder authentication completed successfully.                          | Continue the payment flow.                                            |
| `attempted`        | A 3DS attempt was recorded, but the flow did not end as a full authentication. | Review the payment result and your processor rules before continuing. |
| `step-up-required` | The payer must complete a challenge or additional verification step.           | Present the returned redirect or challenge action to the payer.       |
| `failed`           | Authentication failed or the 3DS flow could not be completed.                  | Ask the payer to retry or use another payment method.                 |

## Notes

* Treat these values as the source of truth for public 3DS session status names.
* Do not rely on legacy aliases such as `not_enrolled`, `rejected`, or `abandoned` when integrating against current backend responses.
* When a payment or session response includes `actions`, those actions describe the next customer-visible step more precisely than the status alone.

## Related resources

* [3D Secure (3DS) Authentication](/rest-api/core-concepts/3ds-authentication.md)
* [3D Secure Integration Guide](/rest-api/payments/3ds-integration.md)
* [Payment and Transaction Lifecycle](/rest-api/core-concepts/transaction-lifecycle.md)