Endpoint entorno Integracion
Paths
/api-entrada-xs2a/services/{aspsp}/{version}/consents/{consent-id}/authorisations/{authorisation-id}
Update PSU data in case of Consent of Information on Accounts
This message is sent by the TPP to the ASPSP through the HUB to inform the SCA method selected by the PSU.
Identificador consumidor APIS
Nombre del ASPSP al que desea realizar la petición.(BBVA, Banco Santander ...)
{
"enum": [
"redsys",
"bankia",
"BBVA",
"BBVAPT",
"BBVABE",
"BBVAFR",
"BBVAEUK",
"caixabank",
"BancSabadell",
"bancosantander",
"bancamarch",
"bankoa",
"cajamar",
"arquia",
"BFF",
"colonya",
"eurocajarural",
"evobanco",
"fiarebancaetica",
"bancopichincha",
"unicajabanco",
"cajasur",
"kutxabank",
"bankinter",
"renta4",
"BCE",
"laboralkutxa",
"mediolanum",
"openbank",
"ibercaja",
"selfbank",
"inversis",
"andbank",
"wizink"
]
}Service version
application/json
Identificador único de la transacción asignado por el TPP. Ej: X-Request-ID: 1b3ab8e8-0fd5-43d2-946e-d75958b172e7
Bearer Token. Obtenido en una autenticación previa sobre Auth2. Ej: Authorization: Bearer 2YotnFZFEjr1zCsicMWpAA
{
"default": "Bearer 6yBnsqnMQQ"
}Este dato es contenido si la transacción de inicio de pago forma parte de una sesión (combinación de AIS/PIS). Contendrá el consentId del consentimiento AIS que se realizó previo al inicio de pago. . Ej: Consent-ID: 123-qwer-456
Dirección IP de la petición HTPP entre el PSU y el TPP. Si no está disponible, el TPP debe usar la dirección IP usada por el TPP cuando envía esta petición. Ej: Ej: PSU-IP-Address: 192.168.16.5
Puerto IP de la petición HTTP entre el PSU y el TPP si está disponible. Ejemplo: PSU-IP-Port: 443
Accept header de la petición HTTP entre PSU y el TPP. Ej: PSU-Accept: application/json
Accept charset header de la petición HTTP entre PSU y el TPP. PSU-Accept-Charset: utf-8
Accept encoding header de la petición HTTP entre PSU y el TPP. PSU-Accept-Language: gzip
Accept language header de la petición HTTP entre PSU y el TPP. PSU-Accept-Language: es-ES
Navegador o sistema operativo de la petición HTTP entre el PSU y el TPP. Ejemplo: PSU-User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)
Método HTTP usado en la interfaz entre PSU y TPP. Valores permitidos: POST. Ej: PSU-Http-Method: POST
{
"default": "POST"
}UUID (Universally Unique Identifier) para un dispositivo. El UUID identifica al dispositivo o a una instalación de una aplicación en un dispositivo. Este ID no debe ser modificado hasta la desinstalación de la aplicación del dispositivo. Ej: PSU-Device-ID: 5b3ab8e8-0fd5-43d2-946e-d75958b172e7
Localización correspondiente a la petición HTTP entre el PSU y el TPP. Ej: PSU-Geo-Location: GEO:90.023856;25.345963
Si es "true", el TPP ha comunicado al HUB que prefiere SCA por redirección. Si es "false", el TPP ha comunicado al HUB que prefiere no ser redireccionado para SCA y el procedimiento será por flujo desacoplado. Si el parámetro no es usado, el ASPSP elegirá el flujo SCA a aplicar dependiendo del método SCA elegido por el TPP/PSU.
URI del TPP donde el flujo de la transacción debe ser redirigido después de alguna de las fases del SCA. Es recomendado usar siempre este campo de cabecera.En el futuro, este campo podría cambiar a obligatorio. Ej: TPP-Redirect-URI: https://www.tpp.com/cb
Si esta URI es contenida, el TPP está solicitando redirigir el flujo de la transacción a esta dirección en vez de al TPP-Redirect-URI en caso de un resultado negativo del método de SCA por redirección. "TPP-Nok-Redirect-URI":"https://www.tpp.com/cb/nok"
Es contenido si viaja el campo Signature. Ej: Digest: SHA-256=NzdmZjA4YjY5M2M2NDYyMmVjOWFmMGNmYTZiNTU3MjVmNDI4NTRlMzJkYzE3ZmNmMDE3ZGFmMjhhNTc5OTU3OQ==
Firma de la petición por el TPP.
Certificado del TPP usado para firmar la petición, en base64, sin cabecera, pie ni saltos de linea. Ej: TPP-Signature-Certificate: MIIHgzCCBmugAwIBAgIIZzZvBQlt0UcwDQYJ………….KoZIhvcNAQELBQAwSTELMAkGA1UEBhMCVVMxEzARBgNVBA
Respuesta a la operación
Endpoint in case of Consent of Information on Accounts
Message sent by the TPP to the ASPSP through the Hub to request the SCA status of an authorization sub-resource
Identificador consumidor APIS
Nombre del ASPSP al que desea realizar la petición.(BBVA, Banco Santander ...)
{
"enum": [
"redsys",
"bankia",
"BBVA",
"BBVAPT",
"BBVABE",
"BBVAFR",
"BBVAEUK",
"caixabank",
"BancSabadell",
"bancosantander",
"bancamarch",
"bankoa",
"cajamar",
"arquia",
"BFF",
"colonya",
"eurocajarural",
"evobanco",
"fiarebancaetica",
"bancopichincha",
"unicajabanco",
"cajasur",
"kutxabank",
"bankinter",
"renta4",
"BCE",
"laboralkutxa",
"mediolanum",
"openbank",
"ibercaja",
"selfbank",
"inversis",
"andbank",
"wizink"
]
}Service version
application/json
Identificador único de la transacción asignado por el TPP. Ej: X-Request-ID: 1b3ab8e8-0fd5-43d2-946e-d75958b172e7
Bearer Token. Obtenido en una autenticación previa sobre Auth2. Ej: Authorization: Bearer 2YotnFZFEjr1zCsicMWpAA
{
"default": "Bearer 6yBnsqnMQQ"
}Este dato es contenido si la transacción de inicio de pago forma parte de una sesión (combinación de AIS/PIS). Contendrá el consentId del consentimiento AIS que se realizó previo al inicio de pago. . Ej: Consent-ID: 123-qwer-456
Dirección IP de la petición HTPP entre el PSU y el TPP. Si no está disponible, el TPP debe usar la dirección IP usada por el TPP cuando envía esta petición. Ej: Ej: PSU-IP-Address: 192.168.16.5
Puerto IP de la petición HTTP entre el PSU y el TPP si está disponible. Ejemplo: PSU-IP-Port: 443
Accept header de la petición HTTP entre PSU y el TPP. Ej: PSU-Accept: application/json
Accept charset header de la petición HTTP entre PSU y el TPP. PSU-Accept-Charset: utf-8
Accept encoding header de la petición HTTP entre PSU y el TPP. PSU-Accept-Language: gzip
Accept language header de la petición HTTP entre PSU y el TPP. PSU-Accept-Language: es-ES
Navegador o sistema operativo de la petición HTTP entre el PSU y el TPP. Ejemplo: PSU-User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)
Método HTTP usado en la interfaz entre PSU y TPP. Valores permitidos: POST. Ej: PSU-Http-Method: POST
{
"default": "POST"
}UUID (Universally Unique Identifier) para un dispositivo. El UUID identifica al dispositivo o a una instalación de una aplicación en un dispositivo. Este ID no debe ser modificado hasta la desinstalación de la aplicación del dispositivo. Ej: PSU-Device-ID: 5b3ab8e8-0fd5-43d2-946e-d75958b172e7
Localización correspondiente a la petición HTTP entre el PSU y el TPP. Ej: PSU-Geo-Location: GEO:90.023856;25.345963
Si es "true", el TPP ha comunicado al HUB que prefiere SCA por redirección. Si es "false", el TPP ha comunicado al HUB que prefiere no ser redireccionado para SCA y el procedimiento será por flujo desacoplado. Si el parámetro no es usado, el ASPSP elegirá el flujo SCA a aplicar dependiendo del método SCA elegido por el TPP/PSU.
URI del TPP donde el flujo de la transacción debe ser redirigido después de alguna de las fases del SCA. Es recomendado usar siempre este campo de cabecera.En el futuro, este campo podría cambiar a obligatorio. Ej: TPP-Redirect-URI: https://www.tpp.com/cb
Si esta URI es contenida, el TPP está solicitando redirigir el flujo de la transacción a esta dirección en vez de al TPP-Redirect-URI en caso de un resultado negativo del método de SCA por redirección. "TPP-Nok-Redirect-URI":"https://www.tpp.com/cb/nok"
Es contenido si viaja el campo Signature. Ej: Digest: SHA-256=NzdmZjA4YjY5M2M2NDYyMmVjOWFmMGNmYTZiNTU3MjVmNDI4NTRlMzJkYzE3ZmNmMDE3ZGFmMjhhNTc5OTU3OQ==
Firma de la petición por el TPP.
Certificado del TPP usado para firmar la petición, en base64, sin cabecera, pie ni saltos de linea. Ej: TPP-Signature-Certificate: MIIHgzCCBmugAwIBAgIIZzZvBQlt0UcwDQYJ………….KoZIhvcNAQELBQAwSTELMAkGA1UEBhMCVVMxEzARBgNVBA
Respuesta a la operación
/api-entrada-xs2a/services/{aspsp}/{version}/consents/{consent-id}/authorisations
Start of the authorization process in case of Consent of Information on Accounts
The process of initiating authorization is a process required to create a new authorization sub-resource (if it has not been created implicitly).
Identificador consumidor APIS
Service version
application/json
Identificador único de la transacción asignado por el TPP. Ej: X-Request-ID: 1b3ab8e8-0fd5-43d2-946e-d75958b172e7
Bearer Token. Obtenido en una autenticación previa sobre Auth2. Ej: Authorization: Bearer 2YotnFZFEjr1zCsicMWpAA
{
"default": "Bearer 6yBnsqnMQQ"
}Este dato es contenido si la transacción de inicio de pago forma parte de una sesión (combinación de AIS/PIS). Contendrá el consentId del consentimiento AIS que se realizó previo al inicio de pago. . Ej: Consent-ID: 123-qwer-456
Dirección IP de la petición HTPP entre el PSU y el TPP. Si no está disponible, el TPP debe usar la dirección IP usada por el TPP cuando envía esta petición. Ej: Ej: PSU-IP-Address: 192.168.16.5
Puerto IP de la petición HTTP entre el PSU y el TPP si está disponible. Ejemplo: PSU-IP-Port: 443
Accept header de la petición HTTP entre PSU y el TPP. Ej: PSU-Accept: application/json
Accept charset header de la petición HTTP entre PSU y el TPP. PSU-Accept-Charset: utf-8
Accept encoding header de la petición HTTP entre PSU y el TPP. PSU-Accept-Language: gzip
Accept language header de la petición HTTP entre PSU y el TPP. PSU-Accept-Language: es-ES
Navegador o sistema operativo de la petición HTTP entre el PSU y el TPP. Ejemplo: PSU-User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)
Método HTTP usado en la interfaz entre PSU y TPP. Valores permitidos: POST. Ej: PSU-Http-Method: POST
{
"default": "POST"
}UUID (Universally Unique Identifier) para un dispositivo. El UUID identifica al dispositivo o a una instalación de una aplicación en un dispositivo. Este ID no debe ser modificado hasta la desinstalación de la aplicación del dispositivo. Ej: PSU-Device-ID: 5b3ab8e8-0fd5-43d2-946e-d75958b172e7
Localización correspondiente a la petición HTTP entre el PSU y el TPP. Ej: PSU-Geo-Location: GEO:90.023856;25.345963
Si es "true", el TPP ha comunicado al HUB que prefiere SCA por redirección. Si es "false", el TPP ha comunicado al HUB que prefiere no ser redireccionado para SCA y el procedimiento será por flujo desacoplado. Si el parámetro no es usado, el ASPSP elegirá el flujo SCA a aplicar dependiendo del método SCA elegido por el TPP/PSU.
URI del TPP donde el flujo de la transacción debe ser redirigido después de alguna de las fases del SCA. Es recomendado usar siempre este campo de cabecera.En el futuro, este campo podría cambiar a obligatorio. Ej: TPP-Redirect-URI: https://www.tpp.com/cb
Si esta URI es contenida, el TPP está solicitando redirigir el flujo de la transacción a esta dirección en vez de al TPP-Redirect-URI en caso de un resultado negativo del método de SCA por redirección. "TPP-Nok-Redirect-URI":"https://www.tpp.com/cb/nok"
Es contenido si viaja el campo Signature. Ej: Digest: SHA-256=NzdmZjA4YjY5M2M2NDYyMmVjOWFmMGNmYTZiNTU3MjVmNDI4NTRlMzJkYzE3ZmNmMDE3ZGFmMjhhNTc5OTU3OQ==
Firma de la petición por el TPP.
Certificado del TPP usado para firmar la petición, en base64, sin cabecera, pie ni saltos de linea. Ej: TPP-Signature-Certificate: MIIHgzCCBmugAwIBAgIIZzZvBQlt0UcwDQYJ………….KoZIhvcNAQELBQAwSTELMAkGA1UEBhMCVVMxEzARBgNVBA
Respuesta a la operación
Obtain sub-resources of the authorization in case of Consent of Information on Accounts
Will provide an array of resource identifiers for all generated authorization sub-resources
Identificador consumidor APIS
Nombre del ASPSP al que desea realizar la petición.(BBVA, Banco Santander ...)
Service version
Identificador del recurso que referencia a la iniciación de pago o consentimiento.
application/json
Identificador único de la transacción asignado por el TPP. Ej: X-Request-ID: 1b3ab8e8-0fd5-43d2-946e-d75958b172e7
Bearer Token. Obtenido en una autenticación previa sobre Auth2. Ej: Authorization: Bearer 2YotnFZFEjr1zCsicMWpAA
{
"default": "Bearer 6yBnsqnMQQ"
}Este dato es contenido si la transacción de inicio de pago forma parte de una sesión (combinación de AIS/PIS). Contendrá el consentId del consentimiento AIS que se realizó previo al inicio de pago. . Ej: Consent-ID: 123-qwer-456
Dirección IP de la petición HTPP entre el PSU y el TPP. Si no está disponible, el TPP debe usar la dirección IP usada por el TPP cuando envía esta petición. Ej: Ej: PSU-IP-Address: 192.168.16.5
Puerto IP de la petición HTTP entre el PSU y el TPP si está disponible. Ejemplo: PSU-IP-Port: 443
Accept header de la petición HTTP entre PSU y el TPP. Ej: PSU-Accept: application/json
Accept charset header de la petición HTTP entre PSU y el TPP. PSU-Accept-Charset: utf-8
Accept encoding header de la petición HTTP entre PSU y el TPP. PSU-Accept-Language: gzip
Accept language header de la petición HTTP entre PSU y el TPP. PSU-Accept-Language: es-ES
Navegador o sistema operativo de la petición HTTP entre el PSU y el TPP. Ejemplo: PSU-User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)
Método HTTP usado en la interfaz entre PSU y TPP. Valores permitidos: POST. Ej: PSU-Http-Method: POST
{
"default": "POST"
}UUID (Universally Unique Identifier) para un dispositivo. El UUID identifica al dispositivo o a una instalación de una aplicación en un dispositivo. Este ID no debe ser modificado hasta la desinstalación de la aplicación del dispositivo. Ej: PSU-Device-ID: 5b3ab8e8-0fd5-43d2-946e-d75958b172e7
Localización correspondiente a la petición HTTP entre el PSU y el TPP. Ej: PSU-Geo-Location: GEO:90.023856;25.345963
Si es "true", el TPP ha comunicado al HUB que prefiere SCA por redirección. Si es "false", el TPP ha comunicado al HUB que prefiere no ser redireccionado para SCA y el procedimiento será por flujo desacoplado. Si el parámetro no es usado, el ASPSP elegirá el flujo SCA a aplicar dependiendo del método SCA elegido por el TPP/PSU.
URI del TPP donde el flujo de la transacción debe ser redirigido después de alguna de las fases del SCA. Es recomendado usar siempre este campo de cabecera.En el futuro, este campo podría cambiar a obligatorio. Ej: TPP-Redirect-URI: https://www.tpp.com/cb
Si esta URI es contenida, el TPP está solicitando redirigir el flujo de la transacción a esta dirección en vez de al TPP-Redirect-URI en caso de un resultado negativo del método de SCA por redirección. "TPP-Nok-Redirect-URI":"https://www.tpp.com/cb/nok"
Es contenido si viaja el campo Signature. Ej: Digest: SHA-256=NzdmZjA4YjY5M2M2NDYyMmVjOWFmMGNmYTZiNTU3MjVmNDI4NTRlMzJkYzE3ZmNmMDE3ZGFmMjhhNTc5OTU3OQ==
Firma de la petición por el TPP.
Certificado del TPP usado para firmar la petición, en base64, sin cabecera, pie ni saltos de linea. Ej: TPP-Signature-Certificate: MIIHgzCCBmugAwIBAgIIZzZvBQlt0UcwDQYJ………….KoZIhvcNAQELBQAwSTELMAkGA1UEBhMCVVMxEzARBgNVBA
Respuesta a la operación
/api-entrada-xs2a/services/{aspsp}/{version}/consents/{consent-id}
Information on the status of a consent request
This service allows the TPP to know the status of a previously initiated consent request.
Identificador consumidor APIS
Name of the ASPSP to which you wish to make the request.
Service version
Unique identifier of the transaction assigned by the TPP. Ex: X-Request-ID: 1b3ab8e8-0fd5-43d2-946e-d75958b172e7
Bearer Token. Obtained in a previous authentication on Auth2. Ex: Authorization: Bearer 2YotnFZFEjr1zCsicMWpAA
{
"default": "Bearer 6yBnsqnMQQ"
}IP address of the HTPP request between the PSU and the TPP. If not available, the TPP must use the IP address used by the TPP when sending this request. Ex: Ex: PSU-IP-Address: 192.168.16.5
IP port of the HTTP request between the PSU and the TPP if available. Example: PSU-IP-Port: 443
Accept header of the HTTP request between PSU and TPP. Ex: PSU-Accept: application / json
Accept charset header of the HTTP request between PSU and TPP. PSU-Accept-Charset: utf-8
Accept encoding header of the HTTP request between PSU and TPP. PSU-Accept-Language: gzip
Accept language header of the HTTP request between PSU and TPP. PSU-Accept-Language: en-ES
Browser or operating system of the HTTP request between the PSU and the TPP. Example: PSU-User-Agent: Mozilla / 5.0 (Windows; U; Windows NT 6.1; en-US; rv: 1.9.1.5) Gecko / 20091102 Firefox / 3.5.5 (.NET CLR 3.5.30729)
HTTP method used in the interface between PSU and TPP. Allowed values: POST. Ex: PSU-Http-Method: POST
{
"default": "GET"
}UUID (Universally Unique Identifier) for a device. The UUID identifies the device or an installation of an application on a device. This ID should not be modified until the device application is uninstalled. Ex: PSU-Device-ID: 5b3ab8e8-0fd5-43d2-946e-d75958b172e7
Location corresponding to the HTTP request between the PSU and the TPP. Ex: PSU-Geo-Location: GEO: 90.023856; 25.345963
If it is "true", the TPP has informed the HUB that it prefers SCA by redirection. If it is "false", the TPP has informed the HUB that it prefers not to be redirected to SCA and the procedure will be by decoupled flow. If the parameter is not used, the ASPSP will choose the SCA flow to be applied depending on the SCA method chosen by the TPP / PSU.
TPP URI where the transaction flow must be redirected after one of the SCA phases. It is recommended to always use this header field. In the future, this field may change to mandatory. Ex: TPP-Redirect-URI: https://www.tpp.com/cb
{
"default": "www.example.com"
}If this URI is contained, the TPP is requesting to redirect the flow of the transaction to this address instead of the TPP-Redirect-URI in case of a negative result of the SCA method by redirection. "TPP-Nok-Redirect-URI": "https://www.tpp.com/cb/nok"
{
"default": "www.example.com"
}It is content if the Signature field travels. Ex: Digest: SHA-256 = NzdmZjA4YjY5M2M2NDYyMmVjOWFmMGNmYTZiNTU3MjVmNDI4NTRlMzJkYzE3ZmNmMDE3ZGFmMjhhNTc5OTU3OQ ==
Signature of the petition by the TPP.
TPP certificate used to sign the petition, in base64, without header, footer or line breaks. Ex: TPP-Signature-Certificate: MIIHgzCCBmugAwIBAgIIZzZvBQlt0UcwDQYJ ………… .KoZIhvcNAQELBQAwSTELMAkGA1UEBhMCVVMxEzARBgNVBA
Operation response
Delete a consent request
This service allows the TPP to eliminate a request for consent
Identificador consumidor APIS
Name of the ASPSP to which you wish to make the request.
Service version
Unique identifier of the transaction assigned by the TPP. Ex: X-Request-ID: 1b3ab8e8-0fd5-43d2-946e-d75958b172e7
Bearer Token. Obtained in a previous authentication on Auth2. Ex: Authorization: Bearer 2YotnFZFEjr1zCsicMWpAA
{
"default": "Bearer 6yBnsqnMQQ"
}IP address of the HTPP request between the PSU and the TPP. If not available, the TPP must use the IP address used by the TPP when sending this request. Ex: Ex: PSU-IP-Address: 192.168.16.5
IP port of the HTTP request between the PSU and the TPP if available. Example: PSU-IP-Port: 443
Accept header of the HTTP request between PSU and TPP. Ex: PSU-Accept: application / json
Accept charset header of the HTTP request between PSU and TPP. PSU-Accept-Charset: utf-8
Accept encoding header of the HTTP request between PSU and TPP. PSU-Accept-Language: gzip
Accept language header of the HTTP request between PSU and TPP. PSU-Accept-Language: en-ES
Browser or operating system of the HTTP request between the PSU and the TPP. Example: PSU-User-Agent: Mozilla / 5.0 (Windows; U; Windows NT 6.1; en-US; rv: 1.9.1.5) Gecko / 20091102 Firefox / 3.5.5 (.NET CLR 3.5.30729)
HTTP method used in the interface between PSU and TPP. Allowed values: POST. Ex: PSU-Http-Method: POST
{
"default": "DELETE"
}UUID (Universally Unique Identifier) for a device. The UUID identifies the device or an installation of an application on a device. This ID should not be modified until the device application is uninstalled. Ex: PSU-Device-ID: 5b3ab8e8-0fd5-43d2-946e-d75958b172e7
Location corresponding to the HTTP request between the PSU and the TPP. Ex: PSU-Geo-Location: GEO: 90.023856; 25.345963
If it is "true", the TPP has informed the HUB that it prefers SCA by redirection. If it is "false", the TPP has informed the HUB that it prefers not to be redirected to SCA and the procedure will be by decoupled flow. If the parameter is not used, the ASPSP will choose the SCA flow to be applied depending on the SCA method chosen by the TPP / PSU.
TPP URI where the transaction flow must be redirected after one of the SCA phases. It is recommended to always use this header field. In the future, this field may change to mandatory. Ex: TPP-Redirect-URI: https://www.tpp.com/cb
{
"default": "www.example.com"
}If this URI is contained, the TPP is requesting to redirect the flow of the transaction to this address instead of the TPP-Redirect-URI in case of a negative result of the SCA method by redirection. "TPP-Nok-Redirect-URI": "https://www.tpp.com/cb/nok"
{
"default": "www.exampleNOK.com"
}It is content if the Signature field travels. Ex: Digest: SHA-256 = NzdmZjA4YjY5M2M2NDYyMmVjOWFmMGNmYTZiNTU3MjVmNDI4NTRlMzJkYzE3ZmNmMDE3ZGFmMjhhNTc5OTU3OQ ==
Signature of the petition by the TPP.
TPP certificate used to sign the petition, in base64, without header, footer or line breaks. Ex: TPP-Signature-Certificate: MIIHgzCCBmugAwIBAgIIZzZvBQlt0UcwDQYJ ………… .KoZIhvcNAQELBQAwSTELMAkGA1UEBhMCVVMxEzARBgNVBA
Operation response
/api-entrada-xs2a/services/{aspsp}/{version}/consents/{consent-id}/status
Information on the status of a consent request
This service allows the TPP to know the status of a previously initiated consent request.
Identificador consumidor APIS
Name of the ASPSP to which you wish to make the request.
Service version
Unique identifier of the transaction assigned by the TPP. Ex: X-Request-ID: 1b3ab8e8-0fd5-43d2-946e-d75958b172e7
Bearer Token. Obtained in a previous authentication on Auth2. Ex: Authorization: Bearer 2YotnFZFEjr1zCsicMWpAA
{
"default": "Bearer 6yBnsqnMQQ"
}IP address of the HTPP request between the PSU and the TPP. If not available, the TPP must use the IP address used by the TPP when sending this request. Ex: Ex: PSU-IP-Address: 192.168.16.5
IP port of the HTTP request between the PSU and the TPP if available. Example: PSU-IP-Port: 443
Accept header of the HTTP request between PSU and TPP. Ex: PSU-Accept: application / json
Accept charset header of the HTTP request between PSU and TPP. PSU-Accept-Charset: utf-8
Accept encoding header of the HTTP request between PSU and TPP. PSU-Accept-Language: gzip
Accept language header of the HTTP request between PSU and TPP. PSU-Accept-Language: en-ES
Browser or operating system of the HTTP request between the PSU and the TPP. Example: PSU-User-Agent: Mozilla / 5.0 (Windows; U; Windows NT 6.1; en-US; rv: 1.9.1.5) Gecko / 20091102 Firefox / 3.5.5 (.NET CLR 3.5.30729)
HTTP method used in the interface between PSU and TPP. Allowed values: POST. Ex: PSU-Http-Method: POST
{
"default": "GET"
}UUID (Universally Unique Identifier) for a device. The UUID identifies the device or an installation of an application on a device. This ID should not be modified until the device application is uninstalled. Ex: PSU-Device-ID: 5b3ab8e8-0fd5-43d2-946e-d75958b172e7
Location corresponding to the HTTP request between the PSU and the TPP. Ex: PSU-Geo-Location: GEO: 90.023856; 25.345963
If it is "true", the TPP has informed the HUB that it prefers SCA by redirection. If it is "false", the TPP has informed the HUB that it prefers not to be redirected to SCA and the procedure will be by decoupled flow. If the parameter is not used, the ASPSP will choose the SCA flow to be applied depending on the SCA method chosen by the TPP / PSU.
TPP URI where the transaction flow must be redirected after one of the SCA phases. It is recommended to always use this header field. In the future, this field may change to mandatory. Ex: TPP-Redirect-URI: https://www.tpp.com/cb
{
"default": "www.example.com"
}If this URI is contained, the TPP is requesting to redirect the flow of the transaction to this address instead of the TPP-Redirect-URI in case of a negative result of the SCA method by redirection. "TPP-Nok-Redirect-URI": "https://www.tpp.com/cb/nok"
{
"default": "www.exampleNOK.com"
}It is content if the Signature field travels. Ex: Digest: SHA-256 = NzdmZjA4YjY5M2M2NDYyMmVjOWFmMGNmYTZiNTU3MjVmNDI4NTRlMzJkYzE3ZmNmMDE3ZGFmMjhhNTc5OTU3OQ ==
Signature of the petition by the TPP.
TPP certificate used to sign the petition, in base64, without header, footer or line breaks. Ex: TPP-Signature-Certificate: MIIHgzCCBmugAwIBAgIIZzZvBQlt0UcwDQYJ ………… .KoZIhvcNAQELBQAwSTELMAkGA1UEBhMCVVMxEzARBgNVBA
{
"default": "TestTPPCertificate"
}Operation response
/api-entrada-xs2a/services/{aspsp}/{version}/consents
Request for consent
With this service, a TPP through the HUB can request a consent to access the PSU accounts. This request can be about indicated accounts or not.
Identificador consumidor APIS
Name of the ASPSP to which you wish to make the request.
Unique identifier of the transaction assigned by the TPP. Ex: X-Request-ID: 1b3ab8e8-0fd5-43d2-946e-d75958b172e7
Service version
Bearer Token. Obtained in a previous authentication on Auth2. Ex: Authorization: Bearer 2YotnFZFEjr1zCsicMWpAA
{
"default": "Bearer 6yBnsqnMQQ"
}IP address of the HTPP request between the PSU and the TPP. If not available, the TPP must use the IP address used by the TPP when sending this request. Ex: Ex: PSU-IP-Address: 192.168.16.5
IP port of the HTTP request between the PSU and the TPP if available. Example: PSU-IP-Port: 443
Accept header of the HTTP request between PSU and TPP. Ex: PSU-Accept: application / json
Accept charset header of the HTTP request between PSU and TPP. PSU-Accept-Charset: utf-8
Accept encoding header of the HTTP request between PSU and TPP. PSU-Accept-Language: gzip
Accept language header of the HTTP request between PSU and TPP. PSU-Accept-Language: en-ES
Browser or operating system of the HTTP request between the PSU and the TPP. Example: PSU-User-Agent: Mozilla / 5.0 (Windows; U; Windows NT 6.1; en-US; rv: 1.9.1.5) Gecko / 20091102 Firefox / 3.5.5 (.NET CLR 3.5.30729)
HTTP method used in the interface between PSU and TPP. Allowed values: POST. Ex: PSU-Http-Method: POST
{
"default": "POST"
}UUID (Universally Unique Identifier) for a device. The UUID identifies the device or an installation of an application on a device. This ID should not be modified until the device application is uninstalled. Ex: PSU-Device-ID: 5b3ab8e8-0fd5-43d2-946e-d75958b172e7
Location corresponding to the HTTP request between the PSU and the TPP. Ex: PSU-Geo-Location: GEO: 90.023856; 25.345963
If it is "true", the TPP has informed the HUB that it prefers SCA by redirection. If it is "false", the TPP has informed the HUB that it prefers not to be redirected to SCA and the procedure will be by decoupled flow. If the parameter is not used, the ASPSP will choose the SCA flow to be applied depending on the SCA method chosen by the TPP / PSU.
TPP URI where the transaction flow must be redirected after one of the SCA phases. It is recommended to always use this header field. In the future, this field may change to mandatory. Ex: TPP-Redirect-URI: https://www.tpp.com/cb
{
"default": "www.example.com"
}If this URI is contained, the TPP is requesting to redirect the flow of the transaction to this address instead of the TPP-Redirect-URI in case of a negative result of the SCA method by redirection. "TPP-Nok-Redirect-URI": "https://www.tpp.com/cb/nok"
{
"default": "www.exampleNOK.com"
}It is content if the Signature field travels. Ex: Digest: SHA-256 = NzdmZjA4YjY5M2M2NDYyMmVjOWFmMGNmYTZiNTU3MjVmNDI4NTRlMzJkYzE3ZmNmMDE3ZGFmMjhhNTc5OTU3OQ ==
Signature of the petition by the TPP.
TPP certificate used to sign the petition, in base64, without header, footer or line breaks. Ex: TPP-Signature-Certificate: MIIHgzCCBmugAwIBAgIIZzZvBQlt0UcwDQYJ ………… .KoZIhvcNAQELBQAwSTELMAkGA1UEBhMCVVMxEzARBgNVBA
Access requested to services. Only sub attributes with tags "accounts", "balances" and "transactions" are accepted. Additionally, the ASPSP can support the "availableAccounts" or "allPsd2" sub attributes with the value "all-accounts".
Operation response
/api-entrada-xs2a/services/{aspsp}/{version}/consents/confirmation-of-funds
Consent for confirmation of funds
With this service, a TPP through the HUB can request a consent to access the PSU accounts. This request can be about indicated accounts or not.
Identificador consumidor APIS
Name of the ASPSP to which you wish to make the request.
Service version
Unique identifier of the transaction assigned by the TPP. Ex: X-Request-ID: 1b3ab8e8-0fd5-43d2-946e-d75958b172e7
Bearer Token. Obtained in a previous authentication on Auth2. Ex: Authorization: Bearer 2YotnFZFEjr1zCsicMWpAA
{
"default": "Bearer 6yBnsqnMQQ"
}IP address of the HTPP request between the PSU and the TPP. If not available, the TPP must use the IP address used by the TPP when sending this request. Ex: Ex: PSU-IP-Address: 192.168.16.5
IP port of the HTTP request between the PSU and the TPP if available. Example: PSU-IP-Port: 443
Accept header of the HTTP request between PSU and TPP. Ex: PSU-Accept: application / json
Accept charset header of the HTTP request between PSU and TPP. PSU-Accept-Charset: utf-8
Accept encoding header of the HTTP request between PSU and TPP. PSU-Accept-Language: gzip
Accept language header of the HTTP request between PSU and TPP. PSU-Accept-Language: en-ES
Browser or operating system of the HTTP request between the PSU and the TPP. Example: PSU-User-Agent: Mozilla / 5.0 (Windows; U; Windows NT 6.1; en-US; rv: 1.9.1.5) Gecko / 20091102 Firefox / 3.5.5 (.NET CLR 3.5.30729)
HTTP method used in the interface between PSU and TPP. Allowed values: POST. Ex: PSU-Http-Method: POST
{
"default": "GET"
}UUID (Universally Unique Identifier) for a device. The UUID identifies the device or an installation of an application on a device. This ID should not be modified until the device application is uninstalled. Ex: PSU-Device-ID: 5b3ab8e8-0fd5-43d2-946e-d75958b172e7
Location corresponding to the HTTP request between the PSU and the TPP. Ex: PSU-Geo-Location: GEO: 90.023856; 25.345963
If it is "true", the TPP has informed the HUB that it prefers SCA by redirection. If it is "false", the TPP has informed the HUB that it prefers not to be redirected to SCA and the procedure will be by decoupled flow. If the parameter is not used, the ASPSP will choose the SCA flow to be applied depending on the SCA method chosen by the TPP / PSU.
TPP URI where the transaction flow must be redirected after one of the SCA phases. It is recommended to always use this header field. In the future, this field may change to mandatory. Ex: TPP-Redirect-URI: https://www.tpp.com/cb
{
"default": "www.example.com"
}If this URI is contained, the TPP is requesting to redirect the flow of the transaction to this address instead of the TPP-Redirect-URI in case of a negative result of the SCA method by redirection. "TPP-Nok-Redirect-URI": "https://www.tpp.com/cb/nok"
{
"default": "www.example.com"
}It is content if the Signature field travels. Ex: Digest: SHA-256 = NzdmZjA4YjY5M2M2NDYyMmVjOWFmMGNmYTZiNTU3MjVmNDI4NTRlMzJkYzE3ZmNmMDE3ZGFmMjhhNTc5OTU3OQ ==
Signature of the petition by the TPP.
TPP certificate used to sign the petition, in base64, without header, footer or line breaks. Ex: TPP-Signature-Certificate: MIIHgzCCBmugAwIBAgIIZzZvBQlt0UcwDQYJ ………… .KoZIhvcNAQELBQAwSTELMAkGA1UEBhMCVVMxEzARBgNVBA
Message body
/api-entrada-xs2a/services/{aspsp}/{version}/consents/confirmation-of-funds/{consent-id}/status
Status of the fund confirmation consent
This service allows the TPP, through the Hub, to know the status in which a resource for confirming funds is in the ASPSP.
Identificador consumidor APIS
Name of the ASPSP to which you wish to make the request.
Service version
Consent-id of the request
Unique identifier of the transaction assigned by the TPP. Ex: X-Request-ID: 1b3ab8e8-0fd5-43d2-946e-d75958b172e7
Bearer Token. Obtained in a previous authentication on Auth2. Ex: Authorization: Bearer 2YotnFZFEjr1zCsicMWpAA
{
"default": "Bearer 6yBnsqnMQQ"
}IP address of the HTPP request between the PSU and the TPP. If not available, the TPP must use the IP address used by the TPP when sending this request. Ex: Ex: PSU-IP-Address: 192.168.16.5
IP port of the HTTP request between the PSU and the TPP if available. Example: PSU-IP-Port: 443
Accept header of the HTTP request between PSU and TPP. Ex: PSU-Accept: application / json
Accept charset header of the HTTP request between PSU and TPP. PSU-Accept-Charset: utf-8
Accept encoding header of the HTTP request between PSU and TPP. PSU-Accept-Language: gzip
Accept language header of the HTTP request between PSU and TPP. PSU-Accept-Language: en-ES
Browser or operating system of the HTTP request between the PSU and the TPP. Example: PSU-User-Agent: Mozilla / 5.0 (Windows; U; Windows NT 6.1; en-US; rv: 1.9.1.5) Gecko / 20091102 Firefox / 3.5.5 (.NET CLR 3.5.30729)
HTTP method used in the interface between PSU and TPP. Allowed values: POST. Ex: PSU-Http-Method: POST
{
"default": "GET"
}UUID (Universally Unique Identifier) for a device. The UUID identifies the device or an installation of an application on a device. This ID should not be modified until the device application is uninstalled. Ex: PSU-Device-ID: 5b3ab8e8-0fd5-43d2-946e-d75958b172e7
Location corresponding to the HTTP request between the PSU and the TPP. Ex: PSU-Geo-Location: GEO: 90.023856; 25.345963
If it is "true", the TPP has informed the HUB that it prefers SCA by redirection. If it is "false", the TPP has informed the HUB that it prefers not to be redirected to SCA and the procedure will be by decoupled flow. If the parameter is not used, the ASPSP will choose the SCA flow to be applied depending on the SCA method chosen by the TPP / PSU.
TPP URI where the transaction flow must be redirected after one of the SCA phases. It is recommended to always use this header field. In the future, this field may change to mandatory. Ex: TPP-Redirect-URI: https://www.tpp.com/cb
{
"default": "www.example.com"
}If this URI is contained, the TPP is requesting to redirect the flow of the transaction to this address instead of the TPP-Redirect-URI in case of a negative result of the SCA method by redirection. "TPP-Nok-Redirect-URI": "https://www.tpp.com/cb/nok"
{
"default": "www.example.com"
}It is content if the Signature field travels. Ex: Digest: SHA-256 = NzdmZjA4YjY5M2M2NDYyMmVjOWFmMGNmYTZiNTU3MjVmNDI4NTRlMzJkYzE3ZmNmMDE3ZGFmMjhhNTc5OTU3OQ ==
Signature of the petition by the TPP.
TPP certificate used to sign the petition, in base64, without header, footer or line breaks. Ex: TPP-Signature-Certificate: MIIHgzCCBmugAwIBAgIIZzZvBQlt0UcwDQYJ ………… .KoZIhvcNAQELBQAwSTELMAkGA1UEBhMCVVMxEzARBgNVBA
/api-entrada-xs2a/services/{aspsp}/{version}/consents/confirmation-of-funds/{consent-id}
Status of the fund confirmation consent
This service allows the TPP, through the Hub, to know the status in which a resource for confirming funds is in the ASPSP.
Identificador consumidor APIS
Name of the ASPSP to which you wish to make the request.
Service version
Consent-id of the request
Unique identifier of the transaction assigned by the TPP. Ex: X-Request-ID: 1b3ab8e8-0fd5-43d2-946e-d75958b172e7
Bearer Token. Obtained in a previous authentication on Auth2. Ex: Authorization: Bearer 2YotnFZFEjr1zCsicMWpAA
{
"default": "Bearer 6yBnsqnMQQ"
}IP address of the HTPP request between the PSU and the TPP. If not available, the TPP must use the IP address used by the TPP when sending this request. Ex: Ex: PSU-IP-Address: 192.168.16.5
IP port of the HTTP request between the PSU and the TPP if available. Example: PSU-IP-Port: 443
Accept header of the HTTP request between PSU and TPP. Ex: PSU-Accept: application / json
Accept charset header of the HTTP request between PSU and TPP. PSU-Accept-Charset: utf-8
Accept encoding header of the HTTP request between PSU and TPP. PSU-Accept-Language: gzip
Accept language header of the HTTP request between PSU and TPP. PSU-Accept-Language: en-ES
Browser or operating system of the HTTP request between the PSU and the TPP. Example: PSU-User-Agent: Mozilla / 5.0 (Windows; U; Windows NT 6.1; en-US; rv: 1.9.1.5) Gecko / 20091102 Firefox / 3.5.5 (.NET CLR 3.5.30729)
HTTP method used in the interface between PSU and TPP. Allowed values: POST. Ex: PSU-Http-Method: POST
{
"default": "GET"
}UUID (Universally Unique Identifier) for a device. The UUID identifies the device or an installation of an application on a device. This ID should not be modified until the device application is uninstalled. Ex: PSU-Device-ID: 5b3ab8e8-0fd5-43d2-946e-d75958b172e7
Location corresponding to the HTTP request between the PSU and the TPP. Ex: PSU-Geo-Location: GEO: 90.023856; 25.345963
If it is "true", the TPP has informed the HUB that it prefers SCA by redirection. If it is "false", the TPP has informed the HUB that it prefers not to be redirected to SCA and the procedure will be by decoupled flow. If the parameter is not used, the ASPSP will choose the SCA flow to be applied depending on the SCA method chosen by the TPP / PSU.
TPP URI where the transaction flow must be redirected after one of the SCA phases. It is recommended to always use this header field. In the future, this field may change to mandatory. Ex: TPP-Redirect-URI: https://www.tpp.com/cb
{
"default": "www.example.com"
}If this URI is contained, the TPP is requesting to redirect the flow of the transaction to this address instead of the TPP-Redirect-URI in case of a negative result of the SCA method by redirection. "TPP-Nok-Redirect-URI": "https://www.tpp.com/cb/nok"
{
"default": "www.example.com"
}It is content if the Signature field travels. Ex: Digest: SHA-256 = NzdmZjA4YjY5M2M2NDYyMmVjOWFmMGNmYTZiNTU3MjVmNDI4NTRlMzJkYzE3ZmNmMDE3ZGFmMjhhNTc5OTU3OQ ==
Signature of the petition by the TPP.
TPP certificate used to sign the petition, in base64, without header, footer or line breaks. Ex: TPP-Signature-Certificate: MIIHgzCCBmugAwIBAgIIZzZvBQlt0UcwDQYJ ………… .KoZIhvcNAQELBQAwSTELMAkGA1UEBhMCVVMxEzARBgNVBA
Status of the fund confirmation consent
This service allows the TPP, through the Hub, to know the status in which a resource for confirming funds is in the ASPSP.
Identificador consumidor APIS
Name of the ASPSP to which you wish to make the request.
Service version
Consent-id of the request
Unique identifier of the transaction assigned by the TPP. Ex: X-Request-ID: 1b3ab8e8-0fd5-43d2-946e-d75958b172e7
Bearer Token. Obtained in a previous authentication on Auth2. Ex: Authorization: Bearer 2YotnFZFEjr1zCsicMWpAA
{
"default": "Bearer 6yBnsqnMQQ"
}IP address of the HTPP request between the PSU and the TPP. If not available, the TPP must use the IP address used by the TPP when sending this request. Ex: Ex: PSU-IP-Address: 192.168.16.5
IP port of the HTTP request between the PSU and the TPP if available. Example: PSU-IP-Port: 443
Accept header of the HTTP request between PSU and TPP. Ex: PSU-Accept: application / json
Accept charset header of the HTTP request between PSU and TPP. PSU-Accept-Charset: utf-8
Accept encoding header of the HTTP request between PSU and TPP. PSU-Accept-Language: gzip
Accept language header of the HTTP request between PSU and TPP. PSU-Accept-Language: en-ES
Browser or operating system of the HTTP request between the PSU and the TPP. Example: PSU-User-Agent: Mozilla / 5.0 (Windows; U; Windows NT 6.1; en-US; rv: 1.9.1.5) Gecko / 20091102 Firefox / 3.5.5 (.NET CLR 3.5.30729)
HTTP method used in the interface between PSU and TPP. Allowed values: POST. Ex: PSU-Http-Method: POST
{
"default": "GET"
}UUID (Universally Unique Identifier) for a device. The UUID identifies the device or an installation of an application on a device. This ID should not be modified until the device application is uninstalled. Ex: PSU-Device-ID: 5b3ab8e8-0fd5-43d2-946e-d75958b172e7
Location corresponding to the HTTP request between the PSU and the TPP. Ex: PSU-Geo-Location: GEO: 90.023856; 25.345963
If it is "true", the TPP has informed the HUB that it prefers SCA by redirection. If it is "false", the TPP has informed the HUB that it prefers not to be redirected to SCA and the procedure will be by decoupled flow. If the parameter is not used, the ASPSP will choose the SCA flow to be applied depending on the SCA method chosen by the TPP / PSU.
TPP URI where the transaction flow must be redirected after one of the SCA phases. It is recommended to always use this header field. In the future, this field may change to mandatory. Ex: TPP-Redirect-URI: https://www.tpp.com/cb
{
"default": "www.example.com"
}If this URI is contained, the TPP is requesting to redirect the flow of the transaction to this address instead of the TPP-Redirect-URI in case of a negative result of the SCA method by redirection. "TPP-Nok-Redirect-URI": "https://www.tpp.com/cb/nok"
{
"default": "www.example.com"
}It is content if the Signature field travels. Ex: Digest: SHA-256 = NzdmZjA4YjY5M2M2NDYyMmVjOWFmMGNmYTZiNTU3MjVmNDI4NTRlMzJkYzE3ZmNmMDE3ZGFmMjhhNTc5OTU3OQ ==
Signature of the petition by the TPP.
TPP certificate used to sign the petition, in base64, without header, footer or line breaks. Ex: TPP-Signature-Certificate: MIIHgzCCBmugAwIBAgIIZzZvBQlt0UcwDQYJ ………… .KoZIhvcNAQELBQAwSTELMAkGA1UEBhMCVVMxEzARBgNVBA
Correct cancellation
Definitions
{
"properties": {
"scaRedirect": {
"type": "string",
"example": "\/aspsp-name\/v1\/payments\/sepa-credit-transfers\/1234-qwer-5678"
},
"selectAuthenticationMethod": {
"properties": [],
"type": "string",
"example": "\/aspsp-name\/v1\/payments\/sepa-credit-transfers\/1234-qwer-5678"
},
"scaStatus": {
"properties": [],
"type": "string",
"example": "\/aspsp-name\/v1\/payments\/sepa-credit-transfers\/1234-qwer-5678"
}
},
"additionalProperties": false
}
{
"properties": {
"tppMessage": {
"$ref": "#\/definitions\/_tppMessage",
"description": "Mensaje para el TPP"
},
"_links": {
"$ref": "#\/definitions\/Links_ActualizarDatosPSU",
"description": "Lista de hipervínculos para ser reconocidos por el HUB. Tipos soportados en esta respuesta: • scaRedirect: en caso de SCA por redirección. Link donde el navegador del PSU debe ser redireccionado por el TPP. • scaStatus: link para consultar el estado SCA correspondiente al sub-recurso de autorización. Este link es solo contenido si un sub-recurso de autorización ha sido creado."
},
"scaStatus": {
"properties": [],
"type": "string",
"description": "Estado SCA"
},
"psuMessage": {
"properties": [],
"type": "string",
"description": "Texto enviado al TPP a través del HUB para ser mostrado al PSU."
}
},
"additionalProperties": false
}
{
"properties": {
"authenticationMethodId": {
"type": "string",
"description": "Identificador del método de autenticación"
}
},
"additionalProperties": false
}
{
"properties": {
"scaRedirect": {
"type": "string",
"example": "\/aspsp-name\/v1\/payments\/sepa-credit-transfers\/1234-qwer-5678"
},
"selectAuthenticationMethod": {
"properties": [],
"type": "string",
"example": "\/aspsp-name\/v1\/payments\/sepa-credit-transfers\/1234-qwer-5678"
},
"scaStatus": {
"properties": [],
"type": "string",
"example": "\/aspsp-name\/v1\/payments\/sepa-credit-transfers\/1234-qwer-5678"
}
}
}
{
"properties": {
"authenticationType": {
"type": "string",
"description": "Tipo del método de autenticación. Valores posibles: • SMS_OTP • CHIP_OTP • PHOTO_OTP • PUSH_OTP Ver anexo 6.6 Tipos de autenticación para más información."
},
"authenticationVersion": {
"properties": [],
"type": "string",
"description": "Versión de la herramienta asociada al authenticationType."
},
"authenticationMethodId": {
"properties": [],
"type": "string",
"description": "Id del método de autenticación proporcionado por el ASPSP."
},
"name": {
"properties": [],
"type": "string",
"description": "Nombre del método de autenticación definido por el PSU en la banca online del ASPSP."
}
},
"additionalProperties": false
}
{
"type": "array",
"items": {
"$ref": "#\/definitions\/AuthenticationObject"
}
}
{
"properties": {
"scaStatus": {
"type": "string",
"description": "Estado SCA"
},
"authorisationId": {
"properties": [],
"type": "string",
"description": "Identificador del recurso que referencia al sub-recurso de autorización creado"
},
"scaMethods": {
"properties": [],
"description": "Este elemento es contenido si SCA es requerido y si el PSU puede elegir entre diferentes métodos de autenticación. Si este dato es contenido también se informará el link \"selectAuthenticationM ethod”. Estos métodos deberán ser presentados al PSU. Nota: Solo si ASPSP soporta selección del método SCA",
"$ref": "#\/definitions\/ListAuthenticationObject"
},
"_links": {
"properties": [],
"description": "Lista de hipervínculos para ser reconocidos por el TPP. Tipos soportados en esta respuesta: scaRedirect: en caso de SCA por redirección. Link donde el navegador del PSU debe ser redireccionado por el TPP. selectAuthenticatio nMethod: link al sub-recurso de autorización o de autorización de cancelación donde el método SCA seleccionado será informado. • scaStatus: link para consultar el estado SCA correspondiente al sub-recurso de autorización.",
"$ref": "#\/definitions\/Links_AutorizacionInicioPago"
},
"psuMessage": {
"properties": [],
"type": "string",
"description": "Texto enviado al TPP a través del HUB para ser mostrado al PSU."
},
"tppMessages": {
"properties": [],
"type": "string",
"description": "Mensaje para el TPP enviado a través del HUB."
}
},
"additionalProperties": false,
"required": [
"scaStatus",
"authorisationId",
"_links"
]
}
{
"properties": {
"authorisationIds": {
"type": "array",
"items": {
"type": "string"
},
"description": "Array de authorisationIds."
},
"cancellationIds": {
"properties": [],
"type": "array",
"description": "Array de cancellationIds conectados al recurso de pago. Nota: obligatorio si se trata de una cancelación",
"items": {
"type": "string"
}
}
},
"additionalProperties": false
}
{
"properties": {
"accounts": {
"items": {
"type": "string"
},
"$ref": "#\/definitions\/_accountList"
}
},
"additionalProperties": false
}
{
"type": "array",
"items": {
"$ref": "#\/definitions\/_AccountDetails"
}
}
{
"properties": {
"trustedBeneficiaries": {
"description": "Está solicitando acceso a los beneficiarios de confianza de la cuenta referenciada y relacionada al PSU. si se informa será ignorado por el ASPSP.",
"x-ibm-languages": {
"description": {
"en": "You are requesting access to the trusted beneficiaries of the account referenced and related to the PSU. if it is reported it will be ignored by the ASPSP."
}
},
"$ref": "#\/definitions\/_accountReferenceList"
},
"ownerName": {
"description": "Si se informa será ignorado por el ASPSP",
"x-ibm-languages": {
"description": {
"en": "If reported it will be ignored by ASPSP"
}
},
"$ref": "#\/definitions\/_accountReferenceList"
}
}
}
{
"type": "array",
"items": {
"$ref": "#\/definitions\/_AccountReference"
}
}
{
"properties": {
"accounts": {
"$ref": "#\/definitions\/_accountList",
"description": "Indica las cuentas sobre las que pedir información detallada. Si la lista está vacía, el TPP está solicitando todas las cuentas accesibles.",
"x-ibm-languages": {
"description": {
"en": "Indicates the accounts on which to request detailed information. If the list is empty, the TPP is requesting all accessible accounts. "
}
}
},
"balances": {
"properties": [],
"$ref": "#\/definitions\/_accountList",
"description": "Indica las cuentas sobre las que pedir saldos. Si la lista está vacía, el TPP está solicitando los saldos de todas las listas de cuentas accesibles.",
"x-ibm-languages": {
"description": {
"en": "Indicates the accounts to request balances. If the list is empty, the TPP is requesting the balances of all lists of accessible accounts. "
}
}
},
"transactions": {
"properties": [],
"$ref": "#\/definitions\/_accountList",
"description": "Indica las cuentas sobre las que pedir transacciones. Si la lista está vacía, el TPP está solicitando las transacciones de todas las listas de cuentas accesibles.",
"x-ibm-languages": {
"description": {
"en": "Indicates the accounts on which to request transactions. If the list is empty, the TPP is requesting transactions from all lists of accessible accounts. "
}
}
},
"additionalInformation": {
"properties": [],
"$ref": "#\/definitions\/_AccountInformationAccess",
"description": "la información contenida en este objeto será ignorada por el ASPSP.",
"x-ibm-languages": {
"description": {
"en": "the information contained in this object will be ignored by the ASPSP."
}
}
},
"availableAccounts": {
"properties": [],
"type": "string",
"description": "Solo el valor “allAccounts” es admitido",
"x-ibm-languages": {
"description": {
"en": "Only the \"allAccounts\" value is supported"
}
},
"example": "allAccounts"
},
"allPsd2": {
"properties": [],
"type": "string",
"example": "allAccounts",
"description": "Solo el valor “allAccounts” es admitido",
"x-ibm-languages": {
"description": {
"en": "Only the \"allAccounts\" value is supported"
}
}
}
},
"additionalProperties": false
}
{
"properties": {
"iban": {
"properties": [],
"type": "string",
"description": "IBAN de la cuenta",
"x-ibm-languages": {
"description": {
"en": "Account IBAN"
}
}
},
"bban": {
"properties": [],
"type": "string",
"description": "BBAN de la cuenta, cuando esta no tiene IBAN.",
"x-ibm-languages": {
"description": {
"en": "Account BBAN, when it does not have IBAN."
}
}
},
"msisdn": {
"properties": [],
"type": "string",
"description": "Alias para acceder a una cuenta de pago a través de un número de teléfono móvil registrado.",
"x-ibm-languages": {
"description": {
"en": "Alias to access a payment account through a registered mobile phone number."
}
}
},
"currency": {
"properties": [],
"type": "string",
"description": "Tipo de moneda",
"x-ibm-languages": {
"description": {
"en": "Currency type"
}
}
}
},
"additionalProperties": false,
"example": ""
}
{
"type": "object",
"properties": {
"currency": {
"type": "string",
"example": "EUR"
},
"content": {
"type": "string",
"example": "150.03"
}
}
}
{
"type": "object",
"properties": {
"iban": {
"type": "string",
"example": "ES1111111111111111111111",
"description": "IBAN de la cuenta",
"x-ibm-languages": {
"description": {
"en": "Account IBAN"
}
}
},
"bban": {
"type": "string",
"description": "BBAN de la cuenta, cuando esta no tiene IBAN.",
"x-ibm-languages": {
"description": {
"en": "Account BBAN, when it does not have IBAN."
}
},
"example": "20385778983000760236"
},
"pan": {
"type": "string",
"description": "Número de la tarjeta de la cuenta. Puede ser tokenizado por el ASPSP para cumplir los requerimientos de PCI DSS.Campo no soportado por el HUB.",
"x-ibm-languages": {
"description": {
"en": "Account card number. It can be tokenized by the ASPSP to meet the requirements of PCI DSS. Field not supported by the HUB."
}
},
"example": "1234567891234567"
},
"maskedPan": {
"type": "string",
"description": "Número de la tarjeta de la cuenta de forma enmascarda. Campo no soportado por el HUB.",
"x-ibm-languages": {
"description": {
"en": "Account card number masked. Field not supported by the HUB."
}
},
"example": "123456******4567"
},
"msisdn": {
"type": "string",
"description": "Alias para acceder a una cuenta de pago a través de un número de teléfono móvil registrado.",
"x-ibm-languages": {
"description": {
"en": "Alias to access a payment account through a registered mobile phone number."
}
},
"example": "1549951988"
},
"currency": {
"type": "string",
"description": "Tipo de moneda.",
"x-ibm-languages": {
"description": {
"en": "Type of currency."
}
},
"example": "EUR"
}
}
}
{
"properties": {
"category": {
"type": "string",
"example": "OK"
},
"code": {
"properties": [],
"type": "string",
"example": "ACCESS_OK"
},
"text": {
"properties": [],
"type": "string",
"example": "Acceso OK"
},
"path": {
"properties": [],
"type": "string",
"example": "\/example\/path"
}
},
"additionalProperties": false
}
{
"type": "object",
"properties": {
"access": {
"x-ibm-languages": {
"description": {
"en": "Access requested to services. Only sub attributes with tags \"accounts\", \"balances\" and \"transactions\" are accepted. Additionally, the ASPSP can support the \"availableAccounts\" or \"allPsd2\" sub attributes with the value \"all-accounts\". "
}
},
"$ref": "#\/definitions\/_AccountAccess"
},
"recurringIndicator": {
"type": "boolean",
"description": "true: acceso recurrente a la cuenta. false: un solo acceso.",
"x-ibm-languages": {
"description": {
"en": "true: recurring access to the account. false: a single access. "
}
},
"example": "true"
},
"validUntil": {
"type": "string",
"description": "Fecha hasta la que el consentimiento solicita acceso. Para crear el consentimiento con el máximo tiempo de acceso posible se debe usar el valor: 9999-12-31 Cuando se recupere el consentimiento, la fecha máxima posible vendrá ajustada.",
"x-ibm-languages": {
"description": {
"en": "Date until the consent requests access. To create the consent with the maximum possible access time the value must be used: 9999-12-31 When the consent is recovered, the maximum possible date will be set. "
}
},
"example": "2020-05-17"
},
"frequencyPerDay": {
"type": "integer",
"description": "Indica la frecuencia de acceso a la cuenta por día. 1 si es de un solo acceso.",
"x-ibm-languages": {
"description": {
"en": "Indicates the frequency of access to the account per day. 1 if it is single access."
}
},
"example": "4"
},
"combinedServiceIndicator": {
"type": "boolean",
"description": "Indica que un inicio de pago se realizará en la misma sesión. De momento el HUB no implementará servicios combinados por lo que este campo deberá tomar el valor de falso. De momento el HUB no implementará servicios combinados por lo que este campo deberá tomar el valor de falso.",
"x-ibm-languages": {
"description": {
"en": "Indicates that a payment start will be made in the same session. At the moment the HUB will not implement combined services so this field should take the value of false. At the moment the HUB will not implement combined services so this field should take the value of false."
}
},
"example": "false"
}
},
"additionalProperties": true,
"required": [
"access"
]
}
{
"properties": {
"psuMessage": {
"type": "string",
"example": "Texto de ejemplo",
"description": "Texto a mostrar al PSU.",
"x-ibm-languages": {
"description": {
"en": "Text to display to the PSU."
}
}
},
"tppMessage": {
"description": "Mensaje para el TPP.",
"x-ibm-languages": {
"description": {
"en": "Message for the TPP."
}
},
"$ref": "#\/definitions\/_tppMessage"
},
"consentStatus": {
"type": "string",
"description": "Estado de la transacción. Valores definidos en anexos.",
"x-ibm-languages": {
"description": {
"en": "Status of the transaction. Values defined in annexes."
}
},
"example": "ACCP"
},
"consentId": {
"type": "string",
"description": "Identificador del recurso que referencia al consentimiento. Debe ser contenido si se generó un consentimiento.",
"x-ibm-languages": {
"description": {
"en": "Identifier of the resource that references the consent. It must be contained if a consent was generated."
}
},
"example": "123-QWE-456"
},
"scaMethods": {
"$ref": "#\/definitions\/_authentication_object_list",
"description": "Este elemento es contenido si SCA es requerido y si el PSU puede elegir entre diferentes métodos de autenticación.",
"x-ibm-languages": {
"description": {
"en": "This element is content if SCA is required and if the PSU can choose between different authentication methods."
}
}
},
"_links": {
"description": "Lista de hipervínculos para ser reconocidos por el TPP. Tipos soportados en esta respuesta: redirect, oAuth, self, status",
"x-ibm-languages": {
"description": {
"en": "List of hyperlinks to be recognized by the TPP. Types supported in this response: redirect, oAuth, self, status"
}
},
"$ref": "#\/definitions\/_links"
}
}
}
{
"properties": {
"psuMessage": {
"type": "string",
"description": "Mensaje para mostrar",
"x-ibm-languages": {
"description": {
"en": "Message to display"
}
},
"example": "Informacion para PSU"
},
"tppMessage": {
"description": "Mensaje para el TPP",
"x-ibm-languages": {
"description": {
"en": "Message for the TPP"
}
},
"$ref": "#\/definitions\/_tppMessage"
},
"consentStatus": {
"type": "string",
"description": "Estado de la transacción (solicitud de consentimiento identificado por consent-id)",
"x-ibm-languages": {
"description": {
"en": "Status of the transaction (consent request identified by consent-id)"
}
},
"example": "AcceptedTechnicalValidation"
}
}
}
{
"properties": {
"psuMessage": {
"type": "string",
"description": "Texto a mostrar al PSU",
"x-ibm-languages": {
"description": {
"en": "Text to display to the PSU"
}
},
"example": "Informacion PSU"
},
"tppMessage": {
"$ref": "#\/definitions\/_tppMessage",
"description": "Mensaje para el TPP",
"x-ibm-languages": {
"description": {
"en": "Message for the TPP"
}
}
},
"access": {
"x-ibm-languages": {
"description": {
"en": "Access requested to services. Only sub attributes with tags \"accounts\", \"balances\" and \"transactions\" are accepted. Additionally, the ASPSP can support the \"availableAccounts\" or \"allPsd2\" sub attributes with the value \"all-accounts\". "
}
},
"$ref": "#\/definitions\/_AccountAccess"
},
"recurringIndicator": {
"type": "boolean",
"description": "true: acceso recurrente a la cuenta. false: un solo acceso.",
"x-ibm-languages": {
"description": {
"en": "true: recurring access to the account. false: a single access. "
}
},
"example": "true"
},
"validUntil": {
"type": "string",
"description": "Fecha hasta la que el consentimiento solicita acceso. Para crear el consentimiento con el máximo tiempo de acceso posible se debe usar el valor: 9999-12-31 Cuando se recupere el consentimiento, la fecha máxima posible vendrá ajustada.",
"x-ibm-languages": {
"description": {
"en": "Date until the consent requests access. To create the consent with the maximum possible access time the value must be used: 9999-12-31 When the consent is recovered, the maximum possible date will be set. "
}
},
"example": "2018-05-17"
},
"frequencyPerDay": {
"type": "integer",
"description": "Indica la frecuencia de acceso a la cuenta por día. 1 si es de un solo acceso.",
"x-ibm-languages": {
"description": {
"en": "Indicates the frequency of access to the account per day. 1 if it is single access."
}
},
"example": "4"
},
"lastActionDate": {
"type": "string",
"description": "Fecha de la última modificación realizada sobre el consentimiento.",
"x-ibm-languages": {
"description": {
"en": "Date of the last modification made on the consent."
}
},
"example": "2018-01-01"
},
"consentStatus": {
"type": "string",
"example": "valid",
"description": "Valores permitidos: empty, valid, blocked, expired, deleted",
"x-ibm-languages": {
"description": {
"en": "Allowed values: empty, valid, blocked, expired, deleted"
}
}
},
"transactionStatus": {
"type": "string",
"description": "Estado de la transacción. Valores definidos en anexos.",
"x-ibm-languages": {
"description": {
"en": "Status of the transaction. Values defined in annexes."
}
},
"example": "ACCP"
}
},
"required": [
"access",
"recurringIndicator",
"validUntil",
"transactionStatus",
"lastActionDate",
"frequencyPerDay",
"consentStatus"
]
}
{
"properties": {
"psuMessage": {
"type": "string",
"description": "Texto a mostrar al PSU",
"x-ibm-languages": {
"description": {
"en": "Text to display to the PSU"
}
},
"example": "Mensaje PSU"
},
"tppMessage": {
"description": "Mensaje para el TPP",
"x-ibm-languages": {
"description": {
"en": "Message for the TPP"
}
},
"$ref": "#\/definitions\/_tppMessage",
"example": "Mensaje para el TPP"
}
}
}
{
"properties": {
"href": {
"type": "string",
"description": "URL para el link",
"x-ibm-languages": {
"description": {
"en": "URL for the link"
}
},
"example": "https:\/\/hub.example.es\/authorize"
}
},
"additionalProperties": false
}
{
"properties": {
"href": {
"type": "string",
"description": "URL asociada al link",
"x-ibm-languages": {
"description": {
"en": "URL associated with the link"
}
},
"example": "\/v1\/payments\/sepa-credit-transfers\/123-qwe-456"
}
},
"additionalProperties": false
}
{
"properties": {
"href": {
"type": "string",
"example": "\/v1\/payments\/sepa-credit-transfers\/123-qwe-456\/status",
"description": "URL del link",
"x-ibm-languages": {
"description": {
"en": "URL of the link"
}
}
}
},
"additionalProperties": false
}
{
"properties": {
"href": {
"type": "string",
"example": "\/v1\/payments\/sepa-credit-transfers\/123-qwe-456\/authorisations\/123auth456"
}
},
"additionalProperties": false
}
{
"properties": {
"href": {
"type": "string",
"example": "https:\/\/hub.example.es\/authorize",
"description": "URL asociada al link",
"x-ibm-languages": {
"description": {
"en": "URL associated with the link"
}
}
}
},
"additionalProperties": false
}
{
"properties": {
"href": {
"type": "string",
"example": "https:\/\/hub.example.es\/authorize",
"description": "URL asociada al link",
"x-ibm-languages": {
"description": {
"en": "URL associated with the link"
}
}
}
},
"additionalProperties": false
}
{
"properties": {
"scaRedirect": {
"example": "",
"$ref": "#\/definitions\/Link_scaRedirect",
"description": "En caso de SCA por redirección. Link donde el navegador del PSU debe ser redireccionado por el TPP.",
"x-ibm-languages": {
"description": {
"en": "In case of SCA by redirection. Link where the PSU browser must be redirected by the TPP."
}
}
},
"startAuthorisation": {
"properties": [],
"example": "",
"$ref": "#\/definitions\/Link_StartAuthorisation",
"description": "En caso de que un inicio explícito de la autorización de la transacción sea necesario (no hay selección del método SCA)",
"x-ibm-languages": {
"description": {
"en": "In case an explicit start of the transaction authorization is necessary (there is no selection of the SCA method)"
}
}
},
"startAuthorisationWithAuthenticationMethodSelection": {
"properties": [],
"example": "",
"description": "Link al end-point de autorización donde el sub-recurso de autorización tiene que ser generado mientras se selecciona el método SCA. Este enlace es contenido bajo las mismas condiciones que el campo \"scaMethods\"",
"x-ibm-languages": {
"description": {
"en": "Link to the authorization end-point where the authorization sub-resource has to be generated while selecting the SCA method. This link is contained under the same conditions as the \"scaMethods\" field"
}
},
"$ref": "#\/definitions\/Link_StartAuthorisationWithAuthenticationMethodSelection"
},
"self": {
"$ref": "#\/definitions\/Link_self",
"description": "link al recurso creado por esta petición.",
"x-ibm-languages": {
"description": {
"en": "link to the resource created by this request."
}
}
},
"status": {
"description": "Link para recuperar el estado de la transacción.",
"x-ibm-languages": {
"description": {
"en": "Link to retrieve the status of the transaction."
}
},
"$ref": "#\/definitions\/Link_status"
},
"scaStatus": {
"description": "Link para consultar el estado SCA correspondiente al sub-recurso de autorización. Este link es solo contenido si un sub-recurso de autorización ha sido creado.",
"x-ibm-languages": {
"description": {
"en": "Link to check the SCA status corresponding to the authorization sub-resource. This link is only content if an authorization sub-resource has been created."
}
},
"$ref": "#\/definitions\/Link_scaStatus"
}
},
"additionalProperties": false
}
{
"properties": {
"account": {
"$ref": "#\/definitions\/_AccountReference",
"description": "Cuenta sobre la que se realizará la consulta de fondos.",
"x-ibm-languages": {
"description": {
"en": "Account on which the funds inquiry will be carried out."
}
}
},
"cardNumber": {
"type": "string",
"description": "Número de tarjeta de la tarjeta emitida por el PIISP. Debe ser enviada si está disponible.",
"x-ibm-languages": {
"description": {
"en": "Card number of the card issued by the PIISP. It must be sent if available."
}
},
"example": "4548-8100-0000-0001"
},
"cardExpiryDate": {
"type": "string",
"description": "Fecha de caducidad de la tarjeta emitida por el PIISP. (Formato ISODate)",
"x-ibm-languages": {
"description": {
"en": "Expiration date of the card issued by the PIISP. (ISODate format)"
}
},
"example": "2018-05-17"
},
"cardInformation": {
"type": "string",
"description": "Explicación adicional del producto.",
"x-ibm-languages": {
"description": {
"en": "Additional explanation of the product."
}
},
"example": "Informacion adicional"
},
"registrationInformation": {
"type": "string",
"description": "Información adicional acerca del proceso de registro para el PSU. Por ej. una referencia al contrato entre TPP\/PSU",
"x-ibm-languages": {
"description": {
"en": "Additional information about the registration process for the PSU. Eg a reference to the contract between TPP \/ PSU"
}
},
"example": "Informacion adicional"
}
},
"additionalProperties": false,
"required": [
"account"
]
}
{
"properties": {
"consentStatus": {
"type": "string",
"description": "Estado de autenticación del consentimiento. Ver valores definidos en 6.5 Estados de consentimiento",
"x-ibm-languages": {
"description": {
"en": "Status of consent authentication. See values defined in 6.5 consent states"
}
}
},
"consentId": {
"type": "string",
"description": "Identificador del recurso que referencia al consentimiento. Debe ser contenido si se generó un consentimiento.",
"x-ibm-languages": {
"description": {
"en": "Identifier of the resource that references the consent. It must be contained if a consent was generated."
}
}
},
"scaMethods": {
"description": "Este elemento es contenido si SCA es requerido y si el PSU puede elegir entre diferentes métodos de autenticación. Si este dato es contenido también se informará el link \"startAuthorisationWithAuthenticationMethodSelection”. Esto métodos deberán ser presentados al PSU. Solo si ASPSP soporta selección del método SCA",
"x-ibm-languages": {
"description": {
"en": "This element is contained if SCA is required and if the PSU can choose between different authentication methods. If this data is contained, the link \"startAuthorisationWithAuthenticationMethodSelection\" will also be reported. These methods must be submitted to the PSU. Note: Only if ASPSP supports selection of the SCA method "
}
},
"$ref": "#\/definitions\/_authentication_object_list"
},
"_links": {
"description": "Lista de hipervínculos para ser reconocidos por el HUB. Tipos soportados en esta respuesta: • scaRedirect: en caso de SCA por redirección. Link donde el navegador del PSU debe ser redireccionado por el Hub. • startAuthorisation: en caso de que un inicio explícito de la autorización de la transacción sea necesario (no hay selección del método SCA) • startAuthorisationWithAuthenticationMethodSelection: link al end-point de autorización donde el sub-recurso de autorización tiene que ser generado mientras se selecciona el método SCA. Este enlace es contenido bajo las mismas condiciones que el campo \"scaMethods\" • self: link al recurso de inicio de pago creado por esta petición. • status: link para recuperar el estado de la transacción. • scaStatus: link para consultar el estado SCA correspondiente al sub-recurso de autorización. Este link es solo contenido si un sub-recurso de autorización ha sido creado. (Si no hay autorización explícita este enlace debe venir obligatoriamente)",
"x-ibm-languages": {
"description": {
"en": "List of hyperlinks to be recognized by the HUB. Types supported in this response: • scaRedirect: in case of SCA by redirection. Link where the PSU browser must be redirected by the Hub. • startAuthorisation: in case an explicit start of the transaction authorization is necessary (there is no selection of the SCA method) • startAuthorisationWithAuthenticationMethodSelection: link to the authorization end-point where the authorization sub-resource has to be generated while selecting the SCA method. This link is contained under the same conditions as the \"scaMethods\" • self: link to the payment initiation resource created by this request. • status: link to retrieve the status of the transaction. • scaStatus: link to check the SCA status corresponding to the authorization sub-resource. This link is only content if an authorization sub-resource has been created. (If there is no explicit authorization this link must come mandatory) "
}
},
"example": "",
"$ref": "#\/definitions\/_links"
},
"tppMessages": {
"description": "Mensaje para el TPP enviado a través del HUB.",
"x-ibm-languages": {
"description": {
"en": "Message for the TPP sent through the HUB."
}
},
"$ref": "#\/definitions\/_tppMessage"
},
"psuMessage": {
"type": "string",
"description": "Texto enviado al TPP a través del HUB para ser mostrado al PSU.",
"x-ibm-languages": {
"description": {
"en": "Text sent to the TPP through the HUB to be displayed to the PSU."
}
}
}
},
"additionalProperties": false,
"required": [
"consentStatus",
"_links",
"consentId"
]
}
{
"properties": {
"propiedad-nueva-1": {
"type": "string"
}
},
"additionalProperties": false
}
{
"properties": {
"consentStatus": {
"type": "string",
"description": "Estado del consentimiento. Ver valores definidos en 6.5 Estados de consentimiento",
"x-ibm-languages": {
"description": {
"en": "Status of consent. See values defined in 6.5 consent states"
}
},
"example": "valid"
},
"psuMessage": {
"type": "string",
"description": "Texto enviado al TPP a través del HUB para ser mostrado al PSU.",
"x-ibm-languages": {
"description": {
"en": "Text sent to the TPP through the HUB to be displayed to the PSU."
}
},
"example": "Información para PSU"
},
"tppMessage": {
"$ref": "#\/definitions\/_tppMessage"
}
},
"additionalProperties": false
}
{
"properties": {
"account": {
"description": "Cuenta sobre la que se realizará la consulta de fondos.",
"x-ibm-languages": {
"description": {
"en": "Account on which the funds inquiry will be carried out."
}
},
"$ref": "#\/definitions\/_AccountReference"
},
"cardNumber": {
"type": "string",
"description": "Número de tarjeta de la tarjeta emitida por el PIISP. Debe ser enviada si está disponible.",
"x-ibm-languages": {
"description": {
"en": "Card number of the card issued by the PIISP. It must be sent if available."
}
},
"example": "4548-8100-0000-0001"
},
"cardInformation": {
"type": "string",
"description": "Explicación adicional del producto.",
"x-ibm-languages": {
"description": {
"en": "Additional explanation of the product."
}
},
"example": "Texto de ejemplo"
},
"registrationInformation": {
"type": "string",
"description": "Información adicional acerca del proceso de registro para el PSU. Por ej. una referencia al contrato entre TPP\/PSU",
"x-ibm-languages": {
"description": {
"en": "Additional information about the registration process for the PSU. Eg a reference to the contract between TPP \/ PSU"
}
},
"example": "Informacion adicional"
},
"consentStatus": {
"type": "string",
"description": "Estado del consentimiento. Valores definidos en anexos.",
"x-ibm-languages": {
"description": {
"en": "Status of consent. Values defined in annexes."
}
},
"example": "valid"
},
"psuMessage": {
"type": "string",
"description": "Texto enviado al TPP a través del HUB para ser mostrado al PSU.",
"x-ibm-languages": {
"description": {
"en": "Text sent to the TPP through the HUB to be displayed to the PSU."
}
},
"example": "Mensaje de ejemplo"
},
"tppMessages": {
"description": "Mensaje para el TPP enviado a través del HUB.",
"x-ibm-languages": {
"description": {
"en": "Message for the TPP sent through the HUB."
}
},
"$ref": "#\/definitions\/_tppMessage"
}
},
"additionalProperties": false,
"required": [
"account",
"consentStatus"
]
}
{
"properties": {
"authenticationType": {
"type": "string"
},
"authenticationVersion": {
"type": "string"
},
"authenticationMethodId": {
"type": "string"
},
"name": {
"type": "string"
},
"explanation": {
"type": "string"
}
}
}
{
"type": "array",
"items": {
"$ref": "#\/definitions\/_authentication_object"
}
}