InitiatePaymentResponse
Body of the response for a successful payment initiation request.
- 1056
- 5768.2
- -1.50
- 5877.78
- 1056
- 5768.2
- -1.50
- 5877.78
- 1056
- 5768.2
- -1.50
- 5877.78
- 1056
- 5768.2
- -1.50
- 5877.78
Array [
]
-
'scaRedirect': In case of an SCA Redirect Approach, the ASPSP is transmitting the link to which to redirect the PSU browser.
-
'scaOAuth': In case of a SCA OAuth2 Approach, the ASPSP is transmitting the URI where the configuration of the Authorisation Server can be retrieved.The configuration follows the OAuth 2.0 Authorisation Server Metadata specification.
-
'confirmation': Might be added by the ASPSP if either the "scaRedirect" or "scaOAuth" hyperlink is returned in the same response message. This hyperlink defines the URL to the resource which needs to be updated with
-
a confirmation code as retrieved after the plain redirect authentication process with the ASPSP authentication server or
-
an access token as retrieved by submitting an authorization code after the integrated OAuth based authentication process with the ASPSP authentication server.
-
-
'startAuthorisationWithPsuIdentification': The link to the authorisation end-point, where the authorisation sub-resource has to be generated while uploading the PSU identification data.
-
'startAuthorisationWithPsuAuthentication': The link to the authorisation end-point, where the authorisation sub-resource has to be generated while uploading the PSU authentication data.
- 'startAuthorisationWithEncryptedPsuAuthentication': Same as startAuthorisactionWithPsuAuthentication where the authentication data need to be encrypted on application layer in uploading.
-
'startAuthorisationWithAuthenticationMethodSelection': The link to the authorisation end-point, where the authorisation sub-resource has to be generated while selecting the authentication method. This link is contained under exactly the same conditions as the data element "scaMethods".
-
'startAuthorisationWithTransactionAuthorisation': The link to the authorisation end-point, where the authorisation sub-resource has to be generated while authorising the transaction e.g. by uploading an OTP received by SMS.
-
'self': The link to the payment initiation resource created by this request. This link can be used to retrieve the resource data.
-
'status': The link to retrieve the transaction status of the payment initiation.
-
'scaStatus': The link to retrieve the scaStatus of the corresponding authorisation sub-resource. This link is only contained, if an authorisation sub-resource has been already created.
Array [
]
Possible values: [accc, accp, acsc, acsp, actc, acwc, rcvd, pdng, rjct, canc, acfc, patc, part]
The transaction status is filled with codes of the ISO 20022
Possible values: non-empty
PaymentId
transactionFees
object
Base Model for amount.
Possible values: non-empty, Value must match regular expression [A-Z]{3}
Currency Code.
Possible values: non-empty, Value must match regular expression -?[0-9]{1,14}(\.[0-9]{1,3})?
The amount given with fractional digits, where fractions must be compliant to the currency definition. Up to 14 significant figures. Negative amounts are signed by minus. The decimal separator is a dot.
Example Valid representations for EUR with up to two decimals are:
currencyConversionFee
object
Base Model for amount.
Possible values: non-empty, Value must match regular expression [A-Z]{3}
Currency Code.
Possible values: non-empty, Value must match regular expression -?[0-9]{1,14}(\.[0-9]{1,3})?
The amount given with fractional digits, where fractions must be compliant to the currency definition. Up to 14 significant figures. Negative amounts are signed by minus. The decimal separator is a dot.
Example Valid representations for EUR with up to two decimals are:
estimatedTotalAmount
object
Base Model for amount.
Possible values: non-empty, Value must match regular expression [A-Z]{3}
Currency Code.
Possible values: non-empty, Value must match regular expression -?[0-9]{1,14}(\.[0-9]{1,3})?
The amount given with fractional digits, where fractions must be compliant to the currency definition. Up to 14 significant figures. Negative amounts are signed by minus. The decimal separator is a dot.
Example Valid representations for EUR with up to two decimals are:
estimatedInterbankSettlementAmount
object
Base Model for amount.
Possible values: non-empty, Value must match regular expression [A-Z]{3}
Currency Code.
Possible values: non-empty, Value must match regular expression -?[0-9]{1,14}(\.[0-9]{1,3})?
The amount given with fractional digits, where fractions must be compliant to the currency definition. Up to 14 significant figures. Negative amounts are signed by minus. The decimal separator is a dot.
Example Valid representations for EUR with up to two decimals are:
If equals 'true', the transaction will involve specific transaction cost as shown by the ASPSP in their public price list or as agreed between ASPSP and PSU. If equals 'false', the transaction will not involve additional specific transaction costs to the PSU unless the fee amount is given specifically in the data elements transactionFees and/or currencyConversionFees. If this data element is not used, there is no information about transaction fees unless the fee amount is given explicitly in the data element transactionFees and/or currencyConversionFees.
scaMethods
object[]
nullable
Authentication object.
This data element might be contained, if SCA is required and if the PSU has a choice between different authentication methods.
Depending on the risk management of the ASPSP this choice might be offered before or after the PSU has been identified with the first relevant factor,
or if an access token is transported.
If this data element is contained, then there is also a hyperlink of type 'startAuthorisationWithAuthenticationMethodSelection' contained in the response body.
These methods shall be presented towards the PSU for selection by the TPP.
Possible values: [smS_OTP, chiP_OTP, photO_OTP, pusH_OTP, smtP_OTP]
Type of the authentication method.
Depending on the "authenticationType". This version can be used by differentiating authentication tools used within performing OTP generation in the same authentication type. This version can be referred to in the ASPSP?s documentation.
Possible values: non-empty and <= 35 characters
An identification provided by the ASPSP for the later identification of the authentication method selection.
This is the name of the authentication method defined by the PSU in the Online Banking frontend of the ASPSP. Alternatively this could be a description provided by the ASPSP like "SMS OTP on phone +49160 xxxxx 28". This name shall be used by the TPP when presenting a list of authentication methods to the PSU, if available.
Detailed information about the SCA method for the PSU.
chosenScaMethod
object
Authentication object.
Possible values: [smS_OTP, chiP_OTP, photO_OTP, pusH_OTP, smtP_OTP]
Type of the authentication method.
Depending on the "authenticationType". This version can be used by differentiating authentication tools used within performing OTP generation in the same authentication type. This version can be referred to in the ASPSP?s documentation.
Possible values: non-empty and <= 35 characters
An identification provided by the ASPSP for the later identification of the authentication method selection.
This is the name of the authentication method defined by the PSU in the Online Banking frontend of the ASPSP. Alternatively this could be a description provided by the ASPSP like "SMS OTP on phone +49160 xxxxx 28". This name shall be used by the TPP when presenting a list of authentication methods to the PSU, if available.
Detailed information about the SCA method for the PSU.
challengeData
object
It is contained in addition to the data element 'chosenScaMethod' if challenge data is needed for SCA.
In rare cases this attribute is also used in the context of the 'startAuthorisationWithPsuAuthentication' link.
PNG data(max. 512 kilobyte) to be displayed to the PSU, Base64 encoding, cp. [RFC4648]. This attribute is used only, when PHOTO_OTP or CHIP_OTP is the selected SCA method.
A collection of strings as challenge data.
A link where the ASPSP will provides the challenge image for the TPP.
The maximal length for the OTP to be typed in by the PSU.
Possible values: [characters, integer]
The format type of the OTP to be typed in. The admitted values are "characters" or "integer".
Additional explanation for the PSU to explain e.g. fallback mechanism for the chosen SCA method. The TPP is obliged to show this to the PSU
Possible values: <= 500 characters
Text to be displayed to the PSU.
_links
object
required
A list of hyperlinks to be recognised by the TPP. The actual hyperlinks used in the response depend on the dynamical decisions of the ASPSP when processing the request.
Remark: All links can be relative or full links, to be decided by the ASPSP.
Type of links admitted in this response, (further links might be added for ASPSP defined extensions):
scaRedirect
object
Link to a resource.
href Entry.
scaOAuth
object
Link to a resource.
href Entry.
confirmation
object
Link to a resource.
href Entry.
startAuthorisation
object
Link to a resource.
href Entry.
startAuthorisationWithPsuIdentification
object
Link to a resource.
href Entry.
startAuthorisationWithPsuAuthentication
object
Link to a resource.
href Entry.
startAuthorisationWithAuthenticationMethodSelection
object
Link to a resource.
href Entry.
startAuthorisationWithTransactionAuthorisation
object
Link to a resource.
href Entry.
self
object
Link to a resource.
href Entry.
scaStatus
object
Link to a resource.
href Entry.
status
object
Link to a resource.
href Entry.
tppMessages
object[]
nullable
TPP messages.
Possible values: [error, warning]
Category of the TPP message category.
Possible values: [warning, beneficiarY_WHITELISTING_REQUIRED]
Message codes for HTTP Codes 201 to a Payment Initiation Request.
Possible values: <= 500 characters
Additional explaining text to the TPP.