Read the status of an account information consent resource.
643 matches
34 actions
Swiss NextGen Banking API-Framework
34 actions
- Confirmation of funds requestPOSTv1.0.0
- Consent status requestGETv1.0.0
- Create a signing basket resourcePOSTv1.0.0
- Create consentPOSTv1.0.0
- Delete ConsentDELETEv1.0.0
- Delete the signing basketDELETEv1.0.0
- Get consent authorisation sub-resources requestGETv1.0.0
- Get consent requestGETv1.0.0
- Get payment informationGETv1.0.0
- Get payment initiation authorisation sub-resources requestGETv1.0.0
- Get signing basket authorisation sub-resources requestGETv1.0.0
- Payment cancellation requestDELETEv1.0.0
- Payment initiation requestPOSTv1.0.0
- Payment initiation status requestGETv1.0.0
- Read account detailsGETv1.0.0
- Read account listGETv1.0.0
- Read balanceGETv1.0.0
- Read the SCA status of the consent authorisationGETv1.0.0
- Read the SCA status of the payment authorisationGETv1.0.0
- Read the SCA status of the payment cancellation's authorisationGETv1.0.0
- Read the SCA status of the signing basket authorisationGETv1.0.0
- Read the status of the signing basketGETv1.0.0
- Read transaction detailsGETv1.0.0
- Read transaction list of an accountGETv1.0.0
- Returns the content of an signing basket objectGETv1.0.0
- Start the authorisation process for a consentPOSTv1.0.0
- Start the authorisation process for a payment initiationPOSTv1.0.0
- Start the authorisation process for a signing basketPOSTv1.0.0
- Start the authorisation process for the cancellation of the addressed paymentPOSTv1.0.0
- Update PSU Data for consentsPUTv1.0.0
- Update PSU data for payment initiationPUTv1.0.0
- Update PSU data for payment initiation cancellationPUTv1.0.0
- Update PSU data for signing basketPUTv1.0.0
- Will deliver an array of resource identifications to all generated cancellation authorisation sub-resourcesGETv1.0.0
Finance/Swiss NextGen Banking API-Framework
Consent status request
v1.0.0Input
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
- 42
- 43
- 44
- 45
- 46
- 47
- 48
- 49
- 50
- 51
- 52
- 53
- 54
- 55
- 56
- 57
- 58
- 59
- 60
- 61
- 62
- 63
- 64
- 65
{
"type": "object",
"properties": {
"Digest": {
"type": "string"
},
"PSU-Accept": {
"type": "string"
},
"PSU-Accept-Charset": {
"type": "string"
},
"PSU-Accept-Encoding": {
"type": "string"
},
"PSU-Accept-Language": {
"type": "string"
},
"PSU-Device-ID": {
"type": "string"
},
"PSU-Geo-Location": {
"type": "string"
},
"PSU-Http-Method": {
"type": "string",
"enum": [
"GET",
"POST",
"PUT",
"PATCH",
"DELETE"
]
},
"PSU-IP-Address": {
"type": "string",
"format": "ipv4"
},
"PSU-IP-Port": {
"type": "string"
},
"PSU-User-Agent": {
"type": "string"
},
"Signature": {
"type": "string"
},
"TPP-Signature-Certificate": {
"type": "string",
"format": "byte"
},
"X-Request-ID": {
"type": "string"
},
"consentId": {
"type": "string",
"description": "ID of the corresponding consent object as returned by an account information consent request.\n"
}
},
"required": [
"X-Request-ID",
"consentId"
],
"additionalProperties": false
}Output
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
{
"type": "object",
"description": "Body of the JSON response for a successful get status request for a consent.",
"required": [
"consentStatus"
],
"properties": {
"consentStatus": {
"type": "string",
"description": "This is the overall lifecycle status of the consent.\n\nValid values are:\n - 'received': The consent data have been received and are technically correct.\n The data is not authorised yet.\n - 'rejected': The consent data have been rejected e.g. since no successful authorisation has taken place.\n - 'valid': The consent is accepted and valid for GET account data calls and others as specified in the consent object.\n - 'revokedByPsu': The consent has been revoked by the PSU towards the ASPSP.\n - 'expired': The consent expired.\n - 'terminatedByTpp': The corresponding TPP has terminated the consent by applying the DELETE method to the consent resource.\n - 'partiallyAuthorised': The consent is due to a multi-level authorisation, some but not all mandated authorisations have been performed yet.\n\nThe ASPSP might add further codes. These codes then shall be contained in the ASPSP's documentation of the XS2A interface \nand has to be added to this API definition as well.\n",
"enum": [
"received",
"rejected",
"valid",
"revokedByPsu",
"expired",
"terminatedByTpp",
"partiallyAuthorised"
]
},
"psuMessage": {
"type": "string",
"description": "Text to be displayed to the PSU."
}
}
}