Check the transaction status of a payment initiation.
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
Payment initiation 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
- 66
- 67
- 68
- 69
- 70
- 71
- 72
- 73
- 74
- 75
- 76
- 77
- 78
- 79
- 80
- 81
- 82
- 83
- 84
- 85
- 86
- 87
- 88
- 89
{
"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"
},
"payment-product": {
"type": "string",
"enum": [
"domestic-swiss-credit-transfers-isr",
"domestic-swiss-credit-transfers",
"domestic-swiss-credit-transfers-qr",
"domestic-swiss-foreign-credit-transfers",
"swiss-sepa-credit-transfers",
"swiss-cross-border-credit-transfers",
"pain.001-sepa-credit-transfers",
"pain.001-cross-border-credit-transfers",
"pain.001-swiss-six-credit-transfers"
]
},
"payment-service": {
"type": "string",
"enum": [
"payments",
"bulk-payments",
"periodic-payments"
]
},
"paymentId": {
"type": "string",
"description": "Resource identification of the generated payment initiation resource."
}
},
"required": [
"X-Request-ID",
"payment-product",
"payment-service",
"paymentId"
],
"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
- 33
- 34
- 35
- 36
- 37
{
"type": "object",
"description": "Body of the response for a successful payment initiation status request in case of an JSON based endpoint.",
"required": [
"transactionStatus"
],
"properties": {
"fundsAvailable": {
"type": "boolean",
"description": "Equals true if sufficient funds are available at the time of the request, false otherwise.\n\nThis datalemenet is allways contained in a confirmation of funds response.\n\nThis data element is contained in a payment status response, \nif supported by the ASPSP, if a funds check has been performed and \nif the transactionStatus is \"ACTC\", \"ACWC\" or \"ACCP\".\n"
},
"psuMessage": {
"type": "string",
"description": "Text to be displayed to the PSU."
},
"transactionStatus": {
"type": "string",
"description": "The transaction status is filled with codes of the ISO 20022 data table:\n- 'ACCC': 'AcceptedSettlementCompleted' -\n Settlement on the creditor's account has been completed.\n- 'ACCP': 'AcceptedCustomerProfile' -\n Preceding check of technical validation was successful.\n Customer profile check was also successful.\n- 'ACSC': 'AcceptedSettlementCompleted' -\n Settlement on the debtoro?=s account has been completed.\n\n **Usage:** this can be used by the first agent to report to the debtor that the transaction has been completed.\n\n **Warning:** this status is provided for transaction status reasons, not for financial information.\n It can only be used after bilateral agreement.\n- 'ACSP': 'AcceptedSettlementInProcess' -\n All preceding checks such as technical validation and customer profile were successful and therefore the payment initiation has been accepted for execution.\n- 'ACTC': 'AcceptedTechnicalValidation' -\n Authentication and syntactical and semantical validation are successful.\n- 'ACWC': 'AcceptedWithChange' -\n Instruction is accepted but a change will be made, such as date or remittance not sent.\n- 'ACWP': 'AcceptedWithoutPosting' -\n Payment instruction included in the credit transfer is accepted without being posted to the creditor customero?=s account.\n- 'RCVD': 'Received' -\n Payment initiation has been received by the receiving agent.\n- 'PDNG': 'Pending' -\n Payment initiation or individual transaction included in the payment initiation is pending.\n Further checks and status update will be performed.\n- 'RJCT': 'Rejected' -\n Payment initiation or individual transaction included in the payment initiation has been rejected.\n- 'CANC': 'Cancelled'\n Payment initiation has been cancelled before execution\n Remark: This codeis accepted as new code by ISO20022.\n- 'ACFC': 'AcceptedFundsChecked' -\n Preceding check of technical validation and customer profile was successful and an automatic funds check was positive .\n Remark: This code is accepted as new code by ISO20022.\n- 'PATC': 'PartiallyAcceptedTechnical'\n Correct The payment initiation needs multiple authentications, where some but not yet all have been performed. Syntactical and semantical validations are successful.\n Remark: This code is accepted as new code by ISO20022.\n- 'PART': 'PartiallyAccepted' -\n A number of transactions have been accepted, whereas another number of transactions have not yet achieved 'accepted' status.\n Remark: This code may be used only in case of bulk payments. It is only used in a situation where all mandated authorisations have been applied, but some payments have been rejected.\n",
"enum": [
"ACCC",
"ACCP",
"ACSC",
"ACSP",
"ACTC",
"ACWC",
"ACWP",
"RCVD",
"PDNG",
"RJCT",
"CANC",
"ACFC",
"PATC",
"PART"
]
}
}
}