---
title: "Verify PSD2 challenge ID"
method: GET
path: "/v1/psd2/challenges/{psd2_challenge_id}"
tags: ["PSD2 account payment and consent"]
---

# Verify PSD2 challenge ID

`GET /v1/psd2/challenges/{psd2_challenge_id}`

This endpoint validates the `psd2_challenge_id` for a customer. Before allowing the customer to log in, you can use this endpoint to verify that the customer is coming from Solaris and that the session is still valid.<br> If the request fails, the customer should see an error message and must restart the process from the TTP's application.<br> Expected error messages: <ol> <li>401 - Unauthorized: The Challenge ID is expired.</li> <li>404 - Not found: The Challenge ID doesn't exist.</li> </ol>

## Path parameters

- `psd2_challenge_id` string, required

## Response `200`

The operation was successful.

- SolarisDecoratorsPSD2Challenge
  - `person_id` string — The Solaris person ID associated with the PSD2 request.
  - `redirect_url` string — The redirect URL where you must send the customer after authentication.

## Other responses

- `400` — Invalid request.
- `401` — The challenge expired.
- `403` — You are not authorized to perform this action.
- `404` — The requested resource could not be found.
- `500` — Internal server error.

---

[API](https://skmtc.net/solarisgroup/apis/compliance-features.md) · [All operations](https://skmtc.net/solarisgroup/apis/compliance-features/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/solarisgroup/compliance-features/revisions/61701b027c74/schema)