Paths
/consents/confirmation-of-funds
This method creates a confirmation of funds consent resource at the ASPSP regarding confirmation of funds access to an account specified in this request.
ID of the request, unique to the call, as determined by the initiating party.
Requestbody for a consent confirmation of funds request.
Is contained if and only if the "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.
The certificate used for signing the request, in base64 encoding. Must be contained if a signature is contained.
Client ID of the PSU in the ASPSP client interface. Might be mandated in the ASPSP's documentation. Is not contained if an OAuth2 based authentication was performed in a pre-step or an OAuth2 based SCA was performed in an preceding AIS service in the same session.
Type of the PSU-ID, needed in scenarios where PSUs have several PSU-IDs as access possibility.
Might be mandated in the ASPSP's documentation. Only used in a corporate context.
Might be mandated in the ASPSP's documentation. Only used in a corporate context.
If it equals "true", the TPP prefers a redirect over an embedded SCA approach.
{
"enum": [
"true",
"false"
]
}URI of the TPP, where the transaction flow shall be redirected to after a Redirect.
If this URI is contained, the TPP is asking to redirect the transaction flow to this address instead of the TPP-Redirect-URI in case of a negative result of the redirect SCA method. This might be ignored by the ASPSP.
If it equals "true", the TPP prefers to start the authorisation process separately, e.g. because of the usage of a signing basket.
{
"enum": [
"true",
"false"
]
}The forwarded IP Address header field consists of the corresponding HTTP 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. Examples
- Android: "Myappa/1.2 Dalvik/2.1.0 (Linux; U; Android 6.0.1; vivo 1610 Build/MMB29M)"
- iOS: "MyApp/1 iPhone5,2 iOS/10_1 CFNetwork/808.3 Darwin/16.3.0"
HTTP method used at the PSU ? TPP interface, if available.
{
"enum": [
"GET",
"POST",
"PUT",
"PATCH",
"DELETE"
]
}UUID (Universally Unique Identifier) for a device, which is used by the PSU, if available.
The forwarded Geo Location of the corresponding http request between PSU and TPP if available.
{
"pattern": "GEO:-?[0-9]{1,2}\\.[0-9]{6};-?[0-9]{1,3}\\.[0-9]{6}"
}Bad Request
Unauthorized
Forbidden
Not Found
Method Not Allowed
Not Acceptable
Request Timeout
Conflict
Unsupported Media Type
Too Many Requests
Internal Server Error
Service Unavailable
/consents/confirmation-of-funds/{consentId}/status
Can check the status of an account information consent resource.
ID of the request, unique to the call, as determined by the initiating party.
ID of the corresponding consent object as returned by an Account Information Consent Request.
Is contained if and only if the "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.
The certificate used for signing the request, in base64 encoding. Must be contained if a signature is contained.
The forwarded IP Address header field consists of the corresponding HTTP 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. Examples
- Android: "Myappa/1.2 Dalvik/2.1.0 (Linux; U; Android 6.0.1; vivo 1610 Build/MMB29M)"
- iOS: "MyApp/1 iPhone5,2 iOS/10_1 CFNetwork/808.3 Darwin/16.3.0"
HTTP method used at the PSU ? TPP interface, if available.
{
"enum": [
"GET",
"POST",
"PUT",
"PATCH",
"DELETE"
]
}UUID (Universally Unique Identifier) for a device, which is used by the PSU, if available.
The forwarded Geo Location of the corresponding http request between PSU and TPP if available.
{
"pattern": "GEO:-?[0-9]{1,2}\\.[0-9]{6};-?[0-9]{1,3}\\.[0-9]{6}"
}Get consent status
Bad Request
Unauthorized
Forbidden
Not Found
Method Not Allowed
Not Acceptable
Request Timeout
Conflict
Unsupported Media Type
Too Many Requests
Internal Server Error
/consents/confirmation-of-funds/{consentId}
Returns the content of an account information consent object.
ID of the request, unique to the call, as determined by the initiating party.
ID of the corresponding consent object as returned by an Account Information Consent Request.
Is contained if and only if the "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.
The certificate used for signing the request, in base64 encoding. Must be contained if a signature is contained.
The forwarded IP Address header field consists of the corresponding HTTP 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. Examples
- Android: "Myappa/1.2 Dalvik/2.1.0 (Linux; U; Android 6.0.1; vivo 1610 Build/MMB29M)"
- iOS: "MyApp/1 iPhone5,2 iOS/10_1 CFNetwork/808.3 Darwin/16.3.0"
HTTP method used at the PSU ? TPP interface, if available.
{
"enum": [
"GET",
"POST",
"PUT",
"PATCH",
"DELETE"
]
}UUID (Universally Unique Identifier) for a device, which is used by the PSU, if available.
The forwarded Geo Location of the corresponding http request between PSU and TPP if available.
{
"pattern": "GEO:-?[0-9]{1,2}\\.[0-9]{6};-?[0-9]{1,3}\\.[0-9]{6}"
}Get consent details
Bad Request
Unauthorized
Forbidden
Not Found
Method Not Allowed
Not Acceptable
Request Timeout
Conflict
Unsupported Media Type
Too Many Requests
Internal Server Error
Deletes a given consent.
ID of the request, unique to the call, as determined by the initiating party.
OAuth2 based SCA was performed in the corresponding consent transaction or if OAuth2 has been used in a pre-step.
Contains the resource-ID of the consent to be deleted.
Is contained if and only if the "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.
The certificate used for signing the request, in base64 encoding. Must be contained if a signature is contained.
The forwarded IP Address header field consists of the corresponding HTTP 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. Examples
- Android: "Myappa/1.2 Dalvik/2.1.0 (Linux; U; Android 6.0.1; vivo 1610 Build/MMB29M)"
- iOS: "MyApp/1 iPhone5,2 iOS/10_1 CFNetwork/808.3 Darwin/16.3.0"
HTTP method used at the PSU ? TPP interface, if available.
{
"enum": [
"GET",
"POST",
"PUT",
"PATCH",
"DELETE"
]
}UUID (Universally Unique Identifier) for a device, which is used by the PSU, if available.
The forwarded Geo Location of the corresponding http request between PSU and TPP if available.
{
"pattern": "GEO:-?[0-9]{1,2}\\.[0-9]{6};-?[0-9]{1,3}\\.[0-9]{6}"
}Deletes a given consent.
Bad Request
Unauthorized
Forbidden
Not Found
Method Not Allowed
Not Acceptable
Request Timeout
Conflict
Unsupported Media Type
Too Many Requests
Internal Server Error
Definitions
Content of the body of a consent confirmation of funds request.
{
"type": "object",
"required": [
"account"
],
"properties": {
"account": {
"$ref": "#/definitions/accountReference"
},
"cardNumber": {
"$ref": "#/definitions/cardNumber"
},
"cardExpiryDate": {
"$ref": "#/definitions/cardExpiryDate"
},
"cardInformation": {
"$ref": "#/definitions/cardInformation"
},
"registrationInformation": {
"$ref": "#/definitions/registrationInformation"
}
}
}
Body of the JSON response for a confirmation of funds content request.
{
"type": "object",
"required": [
"account",
"consentStatus"
],
"properties": {
"account": {
"$ref": "#/definitions/accountReference"
},
"cardNumber": {
"$ref": "#/definitions/cardNumber"
},
"cardExpiryDate": {
"$ref": "#/definitions/cardExpiryDate"
},
"cardInformation": {
"$ref": "#/definitions/cardInformation"
},
"registrationInformation": {
"$ref": "#/definitions/registrationInformation"
},
"consentStatus": {
"$ref": "#/definitions/XS2A_Berlin_Consent_Status"
}
}
}
{
"type": "object",
"properties": {
"consentStatus": {
"$ref": "#/definitions/XS2A_Berlin_Consent_Status"
}
},
"required": [
"consentStatus"
]
}
{
"type": "object",
"properties": {
"consentStatus": {
"$ref": "#/definitions/XS2A_Berlin_Consent_Status"
},
"consentId": {
"type": "string",
"description": "Identification of the consent resource as it is used in the API structure. Shall be contained, if a consent resource was generated."
},
"scaMethods": {
"type": "array",
"items": {
"$ref": "#/definitions/XS2A_Sca_Methods"
}
},
"_links": {
"$ref": "#/definitions/XS2A_Berlin_Links"
}
},
"required": [
"consentStatus",
"_links"
]
}
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 an hyperlink of type 'startAuthorisationWithAuthenticationMethodSelection' contained in the response body.
These methods shall be presented towards the PSU for selection by the TPP.
{
"type": "array",
"items": {
"$ref": "#/definitions/authenticationObject"
}
}
Authentication Object
{
"title": "authenticationObject",
"required": [
"authenticationMethodId",
"authenticationType"
],
"type": "object",
"properties": {
"authenticationType": {
"$ref": "#/definitions/authenticationType"
},
"authenticationVersion": {
"type": "string",
"description": "Depending on the \"authenticationType\".\nThis version can be used by differentiating authentication tools used within performing OTP generation in the same authentication type.\nThis version can be referred to in the ASPSP?s documentation."
},
"authenticationMethodId": {
"maxLength": 35,
"type": "string",
"description": "An identification provided by the ASPSP for the later identification of the authentication method selection.",
"example": "myAuthenticationID"
},
"name": {
"type": "string",
"description": "This is the name of the authentication method defined by the PSU in the Online Banking frontend of the ASPSP.\nAlternatively this could be a description provided by the ASPSP like \"SMS OTP on phone +49160 xxxxx 28\".\nThis name shall be used by the TPP when presenting a list of authentication methods to the PSU, if available.",
"example": "SMS OTP on phone +49160 xxxxx 28"
},
"explanation": {
"type": "string",
"description": "Detailed information about the SCA method for the PSU.",
"example": "Detailed information about the SCA method for the PSU."
}
}
}
{
"title": "authenticationType",
"type": "string",
"enum": [
"SMS_OTP",
"CHIP_OTP",
"PHOTO_OTP",
"PUSH_OTP",
"APP_TO_APP_IOS",
"APP_TO_APP_ANDROID",
"SCAREDIRECT"
]
}
{
"type": "object",
"properties": {
"scaRedirect": {
"$ref": "#/definitions/XS2A_Berlin_Href",
"description": "In case of an SCA Redirect Approach, the ASPSP is transmitting the link to which to redirect the PSU browse."
},
"status": {
"$ref": "#/definitions/XS2A_Berlin_Href",
"description": "The link to retrieve the transaction status of the account information consent."
}
},
"required": [
"scaRedirect",
"status"
]
}
{
"type": "object",
"properties": {
"href": {
"type": "string",
"example": "https://api.testbank.com"
}
},
"required": [
"href"
]
}
Authentication status of the consent.
{
"type": "string",
"enum": [
"received",
"valid",
"rejected",
"revokedByPsu",
"expired",
"terminatedByTpp"
]
}
{
"type": "object",
"properties": {
"errorCode": {
"type": "string",
"description": "Optional error code for reporting purposes."
},
"errorDescription": {
"type": "string",
"description": "The description of the error."
}
}
}
NextGenPSD2 specific definition of reporting error information in case of a HTTP error code 400.
{
"title": "Error400_NG_CIS",
"type": "object",
"properties": {
"tppMessages": {
"type": "array",
"items": {
"$ref": "#/definitions/tppMessage400_CIS"
}
},
"_links": {
"$ref": "#/definitions/_linksAll"
}
}
}
NextGenPSD2 specific definition of reporting error information in case of a HTTP error code 401.
{
"title": "Error401_NG_CIS",
"type": "object",
"properties": {
"tppMessages": {
"type": "array",
"items": {
"$ref": "#/definitions/tppMessage401_CIS"
}
},
"_links": {
"$ref": "#/definitions/_linksAll"
}
}
}
NextGenPSD2 specific definition of reporting error information in case of a HTTP error code 403.
{
"title": "Error403_NG_CIS",
"type": "object",
"properties": {
"tppMessages": {
"type": "array",
"items": {
"$ref": "#/definitions/tppMessage403_CIS"
}
},
"_links": {
"$ref": "#/definitions/_linksAll"
}
}
}
NextGenPSD2 specific definition of reporting error information in case of a HTTP error code 404.
{
"title": "Error404_NG_CIS",
"type": "object",
"properties": {
"tppMessages": {
"type": "array",
"items": {
"$ref": "#/definitions/tppMessage404_CIS"
}
},
"_links": {
"$ref": "#/definitions/_linksAll"
}
}
}
NextGenPSD2 specific definition of reporting error information in case of a HTTP error code 405.
{
"title": "Error405_NG_CIS",
"type": "object",
"properties": {
"tppMessages": {
"type": "array",
"items": {
"$ref": "#/definitions/tppMessage405_CIS"
}
},
"_links": {
"$ref": "#/definitions/_linksAll"
}
}
}
NextGenPSD2 specific definition of reporting error information in case of a HTTP error code 406.
{
"title": "Error406_NG_CIS",
"type": "object",
"properties": {
"tppMessages": {
"type": "array",
"items": {
"$ref": "#/definitions/tppMessage406_CIS"
}
},
"_links": {
"$ref": "#/definitions/_linksAll"
}
}
}
NextGenPSD2 specific definition of reporting error information in case of a HTTP error code 409.
{
"title": "Error409_NG_CIS",
"type": "object",
"properties": {
"tppMessages": {
"type": "array",
"items": {
"$ref": "#/definitions/tppMessage409_CIS"
}
},
"_links": {
"$ref": "#/definitions/_linksAll"
}
}
}
NextGenPSD2 specific definition of reporting error information in case of a HTTP error code 429.
{
"title": "Error429_NG_CIS",
"type": "object",
"properties": {
"tppMessages": {
"type": "array",
"items": {
"$ref": "#/definitions/tppMessage429_CIS"
}
},
"_links": {
"$ref": "#/definitions/_linksAll"
}
}
}
{
"title": "tppMessage400_CIS",
"type": "object",
"properties": {
"category": {
"$ref": "#/definitions/tppMessageCategory"
},
"code": {
"$ref": "#/definitions/MessageCode400_CIS"
},
"path": {
"type": "string"
},
"text": {
"description": "Additional explaining text to the TPP.",
"type": "string",
"maxLength": 512
}
},
"required": [
"category",
"code"
]
}
{
"title": "tppMessage401_CIS",
"type": "object",
"properties": {
"category": {
"$ref": "#/definitions/tppMessageCategory"
},
"code": {
"$ref": "#/definitions/MessageCode401_CIS"
},
"path": {
"type": "string"
},
"text": {
"description": "Additional explaining text to the TPP.",
"type": "string",
"maxLength": 512
}
},
"required": [
"category",
"code"
]
}
{
"title": "tppMessage403_CIS",
"type": "object",
"properties": {
"category": {
"$ref": "#/definitions/tppMessageCategory"
},
"code": {
"$ref": "#/definitions/MessageCode403_CIS"
},
"path": {
"type": "string"
},
"text": {
"description": "Additional explaining text to the TPP.",
"type": "string",
"maxLength": 512
}
},
"required": [
"category",
"code"
]
}
{
"title": "tppMessage404_CIS",
"type": "object",
"properties": {
"category": {
"$ref": "#/definitions/tppMessageCategory"
},
"code": {
"$ref": "#/definitions/MessageCode404_CIS"
},
"path": {
"type": "string"
},
"text": {
"description": "Additional explaining text to the TPP.",
"type": "string",
"maxLength": 512
}
},
"required": [
"category",
"code"
]
}
{
"title": "tppMessage405_CIS",
"type": "object",
"properties": {
"category": {
"$ref": "#/definitions/tppMessageCategory"
},
"code": {
"$ref": "#/definitions/MessageCode405_CIS"
},
"path": {
"type": "string"
},
"text": {
"description": "Additional explaining text to the TPP.",
"type": "string",
"maxLength": 512
}
},
"required": [
"category",
"code"
]
}
{
"title": "tppMessage406_CIS",
"type": "object",
"properties": {
"category": {
"$ref": "#/definitions/tppMessageCategory"
},
"code": {
"$ref": "#/definitions/MessageCode406_CIS"
},
"path": {
"type": "string"
},
"text": {
"description": "Additional explaining text to the TPP.",
"type": "string",
"maxLength": 512
}
},
"required": [
"category",
"code"
]
}
{
"title": "tppMessage409_CIS",
"type": "object",
"properties": {
"category": {
"$ref": "#/definitions/tppMessageCategory"
},
"code": {
"$ref": "#/definitions/MessageCode409_CIS"
},
"path": {
"type": "string"
},
"text": {
"description": "Additional explaining text to the TPP.",
"type": "string",
"maxLength": 512
}
},
"required": [
"category",
"code"
]
}
{
"title": "tppMessage429_CIS",
"type": "object",
"properties": {
"category": {
"$ref": "#/definitions/tppMessageCategory"
},
"code": {
"$ref": "#/definitions/MessageCode429_CIS"
},
"path": {
"type": "string"
},
"text": {
"description": "Additional explaining text to the TPP.",
"type": "string",
"maxLength": 512
}
},
"required": [
"category",
"code"
]
}
Category of the TPP message category
{
"title": "tppMessageCategory",
"example": "ERROR",
"type": "string",
"enum": [
"ERROR",
"WARNING"
]
}
Message codes defined for CIS for HTTP Error code 400 (BAD_REQUEST).
{
"title": "MessageCode400_CIS",
"example": "FORMAT_ERROR",
"type": "string",
"enum": [
"FORMAT_ERROR",
"PARAMETER_NOT_CONSISTENT",
"PARAMETER_NOT_SUPPORTED",
"SERVICE_INVALID",
"RESOURCE_UNKNOWN",
"RESOURCE_EXPIRED",
"RESOURCE_BLOCKED",
"TIMESTAMP_INVALID",
"PERIOD_INVALID",
"SCA_METHOD_UNKNOWN",
"CONSENT_UNKNOWN",
"SESSIONS_NOT_SUPPORTED"
]
}
Message codes defined for CIS for HTTP Error code 401 (UNAUTHORIZED).
{
"title": "MessageCode401_CIS",
"example": "CERTIFICATE_INVALID",
"type": "string",
"enum": [
"CERTIFICATE_INVALID",
"CERTIFICATE_EXPIRED",
"CERTIFICATE_BLOCKED",
"CERTIFICATE_REVOKE",
"CERTIFICATE_MISSING",
"SIGNATURE_INVALID",
"SIGNATURE_MISSING",
"CORPORATE_ID_INVALID",
"PSU_CREDENTIALS_INVALID",
"CONSENT_INVALID",
"CONSENT_EXPIRED",
"TOKEN_UNKNOWN",
"TOKEN_INVALID",
"TOKEN_EXPIRED"
]
}
Message codes defined for CIS for HTTP Error code 403 (FORBIDDEN).
{
"title": "MessageCode403_CIS",
"example": "CONSENT_UNKNOWN",
"type": "string",
"enum": [
"CONSENT_UNKNOWN",
"SERVICE_BLOCKED",
"RESOURCE_UNKNOWN",
"RESOURCE_EXPIRED"
]
}
Message codes defined for CIS for HTTP Error code 404 (NOT_FOUND).
{
"title": "MessageCode404_CIS",
"example": "RESOURCE_UNKNOWN",
"type": "string",
"enum": [
"RESOURCE_UNKNOWN"
]
}
Message codes defined for CIS for HTTP Error code 405 (METHOD_NOT_ALLOWED).
{
"title": "MessageCode405_CIS",
"example": "SERVICE_INVALID",
"type": "string",
"enum": [
"SERVICE_INVALID"
]
}
Message codes defined for CIS for HTTP Error code 406 (NOT_ACCEPTABLE).
{
"title": "MessageCode406_CIS",
"example": "REQUESTED_FORMATS_INVALID",
"type": "string",
"enum": [
"REQUESTED_FORMATS_INVALID"
]
}
Message codes defined for CIS for HTTP Error code 409 (CONFLICT).
{
"title": "MessageCode409_CIS",
"example": "STATUS_INVALID",
"type": "string",
"enum": [
"STATUS_INVALID"
]
}
Message codes defined for CIS for HTTP Error code 429 (TOO_MANY_REQUESTS).
{
"title": "MessageCode429_CIS",
"example": "ACCESS_EXCEEDED",
"type": "string",
"enum": [
"ACCESS_EXCEEDED"
]
}
A _link object with all availabel link types
{
"title": "_linksAll",
"type": "object",
"properties": {
"scaRedirect": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"scaApp2AppIOS": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"scaApp2AppAndroid": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"scaOAuth": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"startAuthorisation": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"startAuthorisationWithPsuIdentification": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"updatePsuIdentification": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"startAuthorisationWithProprietaryData": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"updateProprietaryData": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"startAuthorisationWithPsuAuthentication": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"updatePsuAuthentication": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"startAuthorisationWithEncryptedPsuAuthentication": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"updateEncryptedPsuAuthentication": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"startAuthorisationWithAuthenticationMethodSelection": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"selectAuthenticationMethod": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"startAuthorisationWithTransactionAuthorisation": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"authoriseTransaction": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"self": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"status": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"scaStatus": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"account": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"balances": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"transactions": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"transactionDetails": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"cardAccount": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"cardTransactions": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"first": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"next": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"previous": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"last": {
"$ref": "#/definitions/XS2A_Berlin_Href"
},
"download": {
"$ref": "#/definitions/XS2A_Berlin_Href"
}
}
}
Expiry date of the card issued by the PIISP.
{
"type": "string",
"format": "date",
"example": "2018-07-01"
}
Card Number of the card issued by the PIISP. Should be delivered if available.
{
"type": "string",
"maxLength": 35
}
Addtional explanation for the card product.
{
"type": "string",
"maxLength": 140
}
Addtional information about the registration process for the PSU, e. g. a reference to the TPP / PSU contract.
{
"type": "string",
"maxLength": 140
}
Reference to an account by either
- IBAN, of a payment accounts, or
- BBAN, for payment accounts if there is no IBAN, or
- the Primary Account Number (PAN) of a card, can be tokenised by the ASPSP due to PCI DSS requirements, or
- the Primary Account Number (PAN) of a card in a masked form, or
- an alias to access a payment account via a registered mobile phone number (MSISDN).
{
"type": "object",
"properties": {
"iban": {
"$ref": "#/definitions/iban"
},
"currency": {
"$ref": "#/definitions/currencyCode"
}
}
}
IBAN of an account
{
"type": "string",
"pattern": "[A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}",
"example": "FR7612345987650123456789014"
}
ISO 4217 Alpha 3 currency code
{
"type": "string",
"pattern": "[A-Z]{3}",
"example": "EUR"
}