Read the SCA status of the consent authorisation.
POST/api/v1/consents/:consentId/authorisations/:authorisationId
This method returns the SCA status of a consent initiation's authorisation sub-resource.
Request
Path Parameters
ID of the corresponding consent object as returned by an account information consent request.
ID of the corresponding consent object as returned by an account information consent request.
Header Parameters
- GET
- POST
- PUT
- PATCH
- DELETE
ID of the request, unique to the call, as determined by the initiating party.
Is contained if and only if the OpenBankingGateway.Models.AccountInformationService.GetConsentAuthorisationById.GetConsentAuthorisationByIdRequestHeaders.Signature element is contained in the header of the request.
A signature of the request by the TPP on application level. This might be mandated by ASPSP.
A signature of the request by the TPP on application level. This might be mandated by ASPSP.
The forwarded IP Address header field consists of the corresponding http request IP Address field between PSU and TPP. If not available, the TPP shall use the IP Address used by the TPP when submitting this request.
The forwarded IP Port header field consists of the corresponding HTTP request IP Port field between PSU and TPP, if available.
The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available.
The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available.
The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available.
The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available.
The forwarded Agent header field of the HTTP request between PSU and TPP, if available.
Possible values: [GET
, POST
, PUT
, PATCH
, DELETE
]
HTTP method used at the PSU ? TPP interface, if available. Valid values are:
UUID (Universally Unique Identifier) for a device, which is used by the PSU, if available. UUID identifies either a device or a device dependant application installation. In case of an installation identification this ID needs to be unaltered until removal from device.
The forwarded Geo Location of the corresponding http request between PSU and TPP if available.
Responses
- 200
- 401
- 403
Created
Response Headers
X-Request-ID
string
ID of the request, unique to the call, as determined by the initiating party.
- application/json
- Schema
- Example (from schema)
Schema
Possible values: [received
, psuIdentified
, psuAuthenticated
, scaMethodSelected
, unconfirmed
, started
, finalised
, failed
, exempted
]
This data element is containing information about the status of the SCA method applied.
Possible values: <= 500 characters
Text to be displayed to the PSU.
Possible values: <= 140 characters
Name of the PSU. In case of a corporate account, this might be the person acting on behalf of the corporate.
Possible values: <= 140 characters
Name of the PSU. In case of a corporate account, this might be the person acting on behalf of the corporate.
tppMessage
object
Messages to the TPP on operational issues.
Possible values: [error
, warning
]
Category of the TPP message category.
Possible values: non-empty
Code of the TPP message category.
Possible values: <= 500 characters
Additional explaining text to the TPP.
{
"scaStatus": "received",
"psuMessage": "string",
"psuName": "string",
"trustedBeneficiaryFlag": true,
"tppMessage": {
"category": "error",
"code": "string",
"text": "string"
}
}
Unauthorized
Forbidden