The Solaris person ID associated with the PSD2 challenge.
Compliance features (1.0)
https://docs.solarisgroup.com/_mock/api-reference/onboarding/compliance/
Request
This endpoint updates the status of a psd2_challenge_id
. After a customer enters their credentials on your login screen, use this endpoint to update the status of the psd2_challenge_id
and include the person_id
in the payload.
If successful, the API returns a redirect_URL
for the second-factor authentication (done by Solaris). You have to redirect the customer to this URL to perform the 2FA.
Expected error messages:
- 401 - Unauthorized: The ChallengeID is expired.
- 404 - Not found: The ChallengeID doesn't exist.
- 400 - General Bad Request: The IBAN requested by the TPP does not belong to the specified person.
- Mock Server
https://docs.solarisgroup.com/_mock/api-reference/onboarding/compliance/v1/psd2/challenges/{psd2_challenge_id}
- Payload
- cURL
- Java
- Python
- Node.js
- Go
- Ruby
- PHP
{ "person_id": "dc1a6812a14f6cc338cd084208535bcdcper" }
{ "person_id": "dc1a6812a14f6cc338cd084208535bcdcper", "redirect_url": "http://my.sb.de/consent?consent_challenge=cc1234" }
Request
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.
If the request fails, the customer should see an error message and must restart the process from the TTP's application.
Expected error messages:
- 401 - Unauthorized: The Challenge ID is expired.
- 404 - Not found: The Challenge ID doesn't exist.
- Mock Server
https://docs.solarisgroup.com/_mock/api-reference/onboarding/compliance/v1/psd2/challenges/{psd2_challenge_id}
- Payload
- cURL
- Java
- Python
- Node.js
- Go
- Ruby
- PHP
No request payload
{ "person_id": "null", "redirect_url": "null" }