This method returns the SCA status of a signing basket's authorisation sub-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
Read the SCA status of the signing basket authorisation
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
- 66
- 67
- 68
- 69
- 70
{
"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"
},
"authorisationId": {
"type": "string",
"description": "Resource identification of the related SCA."
},
"basketId": {
"type": "string",
"description": "Resource identification of the generated signing basket resource."
}
},
"required": [
"X-Request-ID",
"authorisationId",
"basketId"
],
"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
- 27
- 28
- 29
- 30
- 31
- 32
{
"type": "object",
"description": "Body of the JSON response with SCA Status.",
"required": [
"scaStatus"
],
"properties": {
"psuMessage": {
"type": "string",
"description": "Text to be displayed to the PSU."
},
"scaStatus": {
"type": "string",
"description": "This data element is containing information about the status of the SCA method applied.\n\nThe following codes are defined for this data type.\n\n * 'received':\n An authorisation or cancellation-authorisation resource has been created successfully.\n * 'psuIdentified':\n The PSU related to the authorisation or cancellation-authorisation resource has been identified.\n * 'psuAuthenticated':\n The PSU related to the authorisation or cancellation-authorisation resource has been identified and authenticated e.g. by a password or by an access token.\n * 'scaMethodSelected':\n The PSU/TPP has selected the related SCA routine.\n If the SCA method is chosen implicitly since only one SCA method is available,\n then this is the first status to be reported instead of 'received'.\n * 'unconfirmed':\n SCA is technically successfully finalised by the PSU, but the authorisation resource needs a confirmation command by the TPP yet. \n * 'started':\n The addressed SCA routine has been started.\n * 'finalised':\n The SCA routine has been finalised successfully (including a potential confirmation command). \n This is a final status of the authorisation resource.\n * 'failed':\n The SCA routine failed.\n This is a final status of the authorisation resource.\n * 'exempted':\n SCA was exempted for the related transaction, the related authorisation is successful.\n This is a final status of the authorisation resource.\n",
"enum": [
"received",
"psuIdentified",
"psuAuthenticated",
"scaMethodSelected",
"started",
"unconfirmed",
"finalised",
"failed",
"exempted"
]
},
"trustedBeneficiaryFlag": {
"type": "boolean",
"description": "Additional Service: Trusted Benificiaries\nWithin this data element, the ASPSP might optionally communicate towards the TPP whether the creditor was part of the related trusted beneficiary list. \nThis attribute is only contained in case of a final scaStatus.\n"
}
}
}