API de Redsys para PSD2
Endpoint entorno Integracion
Paths
/api-entrada-xs2a/services/{aspsp}/v1.1/payments/{payment-product}
Simple payment start
Message sent by the TPP to the ASPSP through the HUB to create a Single payment initiation.
Identificador consumidor APIS
Name of the ASPSP to which you wish to make the request.
{
"enum": [
"sepa-credit-transfers",
"instant-sepa-credit-transfers",
"target-2-payments",
"cross-border-credit-transfers"
]
}application / json
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"
}This data is contained if the payment initiation transaction is part of a session (AIS / PIS combination). It will contain the consent of the AIS consent that was made prior to the start of payment. . Ex: Consent-ID: 123-qwer-456
Identifier that the PSU uses to identify itself to its ASPSP. It can be reported even if an OAuth token is being used and, in such a case, the ASPSP could check that the PSU-ID and token match.
PSU-ID type. Necessary in scenarios where the PSU has several PSU-IDs as access possibilities.
"Company" identifier in the Online Channels.
Type of PSU-Corporate-ID required by the ASPSP to identify its contents.
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
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"
If equal to true, the TPP prefers to initiate the authorization process separately, e.g. due to the need for authorization of a set of operations simultaneously.
This field could be used by the TPP to inform the ASPSP about the Brand used by the TPP towards the PSU. This information can be used to improve communication between the ASPSP and the PSU or the ASPSP and the TPP.
Note: This field will be ignored if informed by the TPP.
Note: This field will be ignored if informed by the TPP.
Note: This field will be ignored if informed by the TPP.
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
HTTP/1.1 201 Created
/api-entrada-xs2a/services/{aspsp}/v1.1/bulk-payments/{payment-product}
Bulk payment start
This message is sent by the TPP to the HUB for the realization of bulk payment initiation
Identificador consumidor APIS
Name of the ASPSP to which you wish to make the request.
{
"enum": [
"sepa-credit-transfers",
"instant-sepa-credit-transfers",
"target-2-payments",
"cross-border-credit-transfers"
]
}application / json
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"
}This data is contained if the payment initiation transaction is part of a session (AIS / PIS combination). It will contain the consent of the AIS consent that was made prior to the start of payment. . Ex: Consent-ID: 123-qwer-456
Identifier that the PSU uses to identify itself to its ASPSP. It can be reported even if an OAuth token is being used and, in such a case, the ASPSP could check that the PSU-ID and token match.
PSU-ID type. Necessary in scenarios where the PSU has several PSU-IDs as access possibilities.
"Company" identifier in the Online Channels.
Type of PSU-Corporate-ID required by the ASPSP to identify its contents.
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
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"
If equal to true, the TPP prefers to initiate the authorization process separately, e.g. due to the need for authorization of a set of operations simultaneously.
This field could be used by the TPP to inform the ASPSP about the Brand used by the TPP towards the PSU. This information can be used to improve communication between the ASPSP and the PSU or the ASPSP and the TPP.
Note: This field will be ignored if informed by the TPP.
Note: This field will be ignored if informed by the TPP.
Note: This field will be ignored if informed by the TPP.
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
HTTP/1.1 201 Created
/api-entrada-xs2a/services/{aspsp}/v1.1/periodic-payments/{payment-product}
Recurring/Periodic Payment Initiation
Message sent by the TPP to the ASPSP through the Hub to create a recurring / periodic payment start. The recurring payment initiation functionality is covered by the Berlin Group specification as the initiation of a specific permanent order. A TPP can send a recurring payment start where the start date, frequency and, conditionally, end date are provided. Once authorized by the PSU, the payment will be executed by the ASPSP, if possible, following the “permanent order” as sent by the TPP. No additional actions are required by the TPP. In this context, this payment is considered a periodic payment to differentiate payment from other types of recurring payments where third parties are initiating the same amount of money. Note: for permanent orders for payment initiation, the ASPSP will always request SCA with Dynamic linking. Exemptions are not allowed.
Identificador consumidor APIS
Name of the ASPSP to which you wish to make the request.
{
"enum": [
"sepa-credit-transfers",
"instant-sepa-credit-transfers",
"target-2-payments",
"cross-border-credit-transfers"
]
}application / json
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"
}This data is contained if the payment initiation transaction is part of a session (AIS / PIS combination). It will contain the consent of the AIS consent that was made prior to the start of payment. . Ex: Consent-ID: 123-qwer-456
Identifier that the PSU uses to identify itself to its ASPSP. It can be reported even if an OAuth token is being used and, in such a case, the ASPSP could check that the PSU-ID and token match.
PSU-ID type. Necessary in scenarios where the PSU has several PSU-IDs as access possibilities.
"Company" identifier in the Online Channels.
Type of PSU-Corporate-ID required by the ASPSP to identify its contents.
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
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"
If equal to true, the TPP prefers to initiate the authorization process separately, e.g. due to the need for authorization of a set of operations simultaneously.
This field could be used by the TPP to inform the ASPSP about the Brand used by the TPP towards the PSU. This information can be used to improve communication between the ASPSP and the PSU or the ASPSP and the TPP.
Note: This field will be ignored if informed by the TPP.
Note: This field will be ignored if informed by the TPP.
Note: This field will be ignored if informed by the TPP.
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
HTTP/1.1 201 Created
/api-entrada-xs2a/services/{aspsp}/v1.1/{payment-service}/{payment-product}/{payment-id}/status
Obtain payment status information
This message is sent by the TPP to the HUB to request information on the status of the payment initiation requested by the TPP
Identificador consumidor APIS
Name of the ASPSP to which you wish to make the request.
Payment product to use.
{
"enum": [
"payments",
"bulk-payments",
"periodic-payments"
]
}Payment product to use.
{
"enum": [
"sepa-credit-transfers",
"instant-sepa-credit-transfers",
"target-2-payments",
"cross-border-credit-transfers"
]
}Identifier of the resource that refers to the initiation of payment. Previously sent in response to a TPP payment initiation message to the HUB.
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"
}Supported response format.
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-Encoding: 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: GET. Ex: PSU-Http-Method: GET
{
"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
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
HTTP/1.1 200 Ok
/api-entrada-xs2a/services/{aspsp}/v1.1/{payment-service}/{payment-product}/{payment-id}
Retrieve payment Initiation information
This message is sent by the TPP to the HUB to request information about a payment start
Identificador consumidor APIS
Name of the ASPSP to which you wish to make the request.
Payment product to use.
{
"enum": [
"payments",
"bulk-payments",
"periodic-payments"
]
}Payment product to use.
{
"enum": [
"sepa-credit-transfers",
"instant-sepa-credit-transfers",
"target-2-payments",
"cross-border-credit-transfers"
]
}Identifier of the resource that refers to the initiation of payment. Previously sent in response to a TPP payment initiation message to the HUB.
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"
}Supported response format.
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-Encoding: 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: GET. Ex: PSU-Http-Method: GET
{
"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
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
HTTP/1.1 200 Ok
Cancel payment start
This request is sent by the TPP to the ASPSP through the Hub and allows to initiate the cancellation of a payment. Depending on the payment service, the payment product and the implementation of the ASPSP, this request may be sufficient to cancel the payment or authorization may be necessary.
Identificador consumidor APIS
Name of the ASPSP to which you wish to make the request.
Payment product to use.
{
"enum": [
"payments",
"bulk-payments",
"periodic-payments"
]
}Payment product to use.
{
"enum": [
"sepa-credit-transfers",
"instant-sepa-credit-transfers",
"target-2-payments",
"cross-border-credit-transfers"
]
}Identifier of the resource that refers to the payment initiation. Previously sent in response to a payment initiation message from the HUB to the ASPSP.
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"
}If "true", the TPP has communicated to the HUB that it prefers SCA by redirection. If "false", the TPP has communicated to the HUB that it prefers not to be redirected for SCA and the procedure will be by decoupled flow. If the parameter is not used, the ASPSP will choose the SCA flow to apply depending on the SCA method chosen by the TPP/PSU. EMBEDDED NOT SUPPORTED IN THIS VERSION
TPP URI where the transaction flow should 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.
If this URI is contained, the TPP is requesting to redirect the transaction flow to this address instead of the TPP-Redirect-URI in case of a negative result of the SCA method by redirection.
If true, the TPP prefers to start the authorization process separately, e.g. due to the need for authorization of a set of operations simultaneously. If false or the parameter is not used, there is no TPP preference. The TPP assumes a direct authorization of the transaction in the next step. Note: ASPSP may not take this into account if it does not support it.
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-Encoding: 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: GET, POST, PUT, PATCH, DELETE. Ex: PSU-Http-Method: GET
{
"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
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
HTTP/1.1 202 Ok
Definitions
{
"type": "object",
"required": [
"country",
"townName"
],
"properties": {
"streetName": {
"type": "string",
"description": "Calle",
"x-ibm-languages": {
"description": {
"en": "Street"
}
},
"example": "Ejemplo de Calle"
},
"buildingNumber": {
"type": "string",
"description": "Numero",
"x-ibm-languages": {
"description": {
"en": "Number"
}
},
"example": "5"
},
"townName": {
"type": "string",
"description": "Ciudad",
"x-ibm-languages": {
"description": {
"en": "City"
}
},
"example": "Cordoba"
},
"postCode": {
"type": "string",
"description": "Codigo Postal",
"x-ibm-languages": {
"description": {
"en": "Postal Code"
}
},
"example": "14100"
},
"country": {
"type": "string",
"description": "Pais",
"x-ibm-languages": {
"description": {
"en": "Country"
}
},
"example": "ES"
}
}
}
{
"required": [
"authenticationMethodId",
"authenticationType",
"name"
],
"properties": {
"authenticationType": {
"type": "string"
},
"authenticationVersion": {
"type": "string"
},
"authenticationMethodId": {
"type": "string"
},
"name": {
"type": "string"
},
"explanation": {
"type": "string"
}
}
}
{
"type": "object",
"properties": {
"iban": {
"properties": [],
"type": "string",
"example": "ES2640000418401234567599",
"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."
}
},
"example": "20385778983000760236"
},
"pan": {
"properties": [],
"type": "string",
"description": "Primary Account Number de la tarjeta. Puede ser tokenizada por el ASPSP para cumplir los requerimientos de PCI DSS.",
"x-ibm-languages": {
"description": {
"en": "Primary Account Number of the card. It can be tokenized by the ASPSP to meet the PCI DSS requirements."
}
},
"example": "1234567891234567"
},
"maskedPan": {
"properties": [],
"type": "string",
"description": "Primary Account Number de la tarjeta en forma enmascarda.",
"x-ibm-languages": {
"description": {
"en": "Primary Account Number of the card in masked form."
}
},
"example": "123456******4567"
},
"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."
}
},
"example": "27821234567"
},
"currency": {
"properties": [],
"type": "string",
"example": "EUR",
"description": "Moneda",
"x-ibm-languages": {
"description": {
"en": "Currency"
}
}
}
}
}
{
"type": "object",
"required": [
"amount",
"currency"
],
"properties": {
"currency": {
"type": "string",
"description": "Moneda del importe",
"x-ibm-languages": {
"description": {
"en": "Currency of the amount"
}
},
"example": "EUR"
},
"amount": {
"type": "string",
"description": "Cantidad del importe",
"x-ibm-languages": {
"description": {
"en": "Amount of the amount"
}
},
"example": "500.00"
}
}
}
{
"required": [
"href"
],
"type": "object",
"properties": {
"href": {
"type": "string",
"description": "Contiene un enlace a un recurso",
"example": "\/v1.1\/payments\/sepa-credit-transfers\/asd-1234-jkl"
}
}
}
{
"type": "object",
"properties": {
"scaRedirect": {
"type": "object",
"description": "URL utilizada para la realización de SCA, mediante redirección del navegador del PSU.",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
},
"scaOAuth": {
"type": "object",
"description": "El enlace para recuperar un documento JSON que especifica los detalles del servidor de autorizaciones de ASPSP. El documento JSON sigue la definición dada en https:\/\/tools.ietf.org\/html\/draft-ietf-oauth-discovery. Solo para ASPSPs que requieran Ejecución de pago.",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
},
"startAuthorisation": {
"type": "object",
"description": "Enlace al endpoint donde la autorizaición de la transacción o la autorización de la transacción de cancelación debe ser iniciada.",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
},
"startAuthorisationWithAuthenticationMethodSelection": {
"type": "object",
"description": "Link al endpoint donde la autorización de una transacción o de una transacción de cancelación debe ser iniciada, donde el método SCA debe ser informado con la correspondiente llamada.",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
},
"selectAuthenticationMethod": {
"type": "object",
"description": "Enlace donde el TPP puede seleccionar el método de autenticación de 2º factor aplicable para el PSU, en caso de haber más de uno.",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
},
"self": {
"type": "object",
"description": "El enlace al recurso creado para la solicitud. Este enlace puede utilizarse posteriormente para recuperar el estado de la transacción.",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
},
"status": {
"type": "object",
"description": "El enlace para recuperar el estado de la transacción. Por ejemplo, estado de inicio de pago.",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
},
"scaStatus": {
"type": "object",
"description": "Enlace para recuperar el estado de la autorización o sub-recurso de autorización de cancelación.",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
},
"account": {
"type": "object",
"description": "Link al recurso que proporciona los datos de una cuenta.",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
},
"balances": {
"type": "object",
"description": "Link al recurso que proporciona los balances de la cuenta.",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
},
"transactions": {
"type": "object",
"description": "Link al recurso que proporciona las transacciones de la cuenta.",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
},
"cardAccount": {
"type": "object",
"description": "Link al recurso que proporciona los datos de una cuenta de tarjeta.",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
},
"cardTransactions": {
"type": "object",
"description": "Link al recurso que proporciona las transacciones de la cuenta de tarjeta.",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
},
"transactionDetails": {
"type": "object",
"description": "Enlace al recurso proporcionando detalles de una transacción específica. NO SOPORTADO EN ESTA VERSIÓN",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
},
"first": {
"type": "object",
"description": "Enlace de navegación para informes de cuentas paginados.",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
},
"next": {
"type": "object",
"description": "Enlace de navegación para informes de cuentas paginados.",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
},
"previous": {
"type": "object",
"description": "Enlace de navegación para informes de cuentas paginados.",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
},
"last": {
"type": "object",
"description": "Enlace de navegación para informes de cuentas paginados.",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
},
"download": {
"type": "object",
"description": "Enlace de descarga para grandes paquetes de datos AIS. Solo para camt-data.",
"additionalProperties": {
"$ref": "#\/definitions\/Href"
}
}
},
"additionalProperties": true
}
{
"type": "array",
"items": {
"$ref": "#\/definitions\/Other"
}
}
{
"type": "array",
"items": {
"$ref": "#\/definitions\/AuthenticationObject"
}
}
{
"type": "array",
"items": {
"$ref": "#\/definitions\/SingleBulkPayment"
}
}
{
"type": "array",
"items": {
"$ref": "#\/definitions\/TppMessage"
}
}
{
"required": [
"others"
],
"type": "object",
"properties": {
"others": {
"$ref": "#\/definitions\/List_Other",
"description": "Lista de \"others\"",
"x-ibm-languages": {
"description": {
"en": "List of \"others\""
}
}
}
}
}
{
"type": "object",
"required": [
"identification"
],
"properties": {
"identification": {
"type": "string",
"description": "Entrada proporcionada por una lista de códigos ISO externa",
"x-ibm-languages": {
"description": {
"en": "Input provided by an external ISO code list"
}
}
}
}
}
{
"type": "object",
"properties": {
"organisationId": {
"$ref": "#\/definitions\/OrganisationIdentification",
"description": "Entrada proporcionada por una lista de códigos ISO externa",
"x-ibm-languages": {
"description": {
"en": "Input provided by an external ISO code list"
}
}
}
}
}
{
"type": "object",
"required": [
"debtorAccount",
"payments"
],
"properties": {
"batchBookingPreferred": {
"type": "boolean",
"description": "Si este elemento es true, el PSU prefiere solo una anotación. Si este elemento es igual a false, el PSU prefiere anotaciones individuales de todas las transacciones individuales contenidas. El ASPSP seguirá esta preferencia de acuerdo al contrato con el PSU.",
"x-ibm-languages": {
"description": {
"en": "If this element is true, the PSU prefers only one annotation. If this element is equal to false, the PSU prefers individual annotations of all the individual transactions contained. The ASPSP will follow this preference according to the contract with the PSU. "
}
},
"example": "true"
},
"requestedExecutionDate": {
"type": "string",
"description": "Si es contenido, los pagos contenidos en el lote serán ejecutados en la fecha indicada. Este campo podría no ser usado junto con el campo requestedExecutionTime",
"x-ibm-languages": {
"description": {
"en": "If it is content, the payments contained in the lot will be executed on the indicated date. This field may not be used together with the requestedExecutionTime field"
}
}
},
"requestedExecutionTime": {
"type": "string",
"description": "Si es contenido, los pagos contenidos en el lote serán ejecutados en la fecha\/hora indicada. Este campo podría no ser usado junto con el campo requestedExecutionDate",
"x-ibm-languages": {
"description": {
"en": "If it is content, the payments contained in the lot will be executed on the date \/ time indicated. This field may not be used together with the requestedExecutionDate field"
}
}
},
"debtorAccount": {
"$ref": "#\/definitions\/AccountReference",
"description": "Cuenta del ordenante.",
"x-ibm-languages": {
"description": {
"en": "Account of the payer."
}
}
},
"payments": {
"items": {
"$ref": "#\/definitions\/SingleBulkPayment"
},
"description": "Este elemento es un array de inicios de pago en notación JSON para los productos de pago soportados. Excluyendo los datos: • debtorAccount • requestedExecutionDate • requestedExecutionTime",
"x-ibm-languages": {
"description": {
"en": "This element is an array of payment starts in JSON notation for supported payment products. Excluding data: • debtorAccount • requestedExecutionDate • requestedExecutionTime "
}
},
"$ref": "#\/definitions\/Response_BulkPayment"
},
"paymentInformationId": {
"type": "string",
"description": "Identificador único asignado por la parte iniciadora para identificar el pago bulk. Este atributo puede ser usado por el ASPSP como un campo opcional.",
"x-ibm-languages": {
"description": {
"en": "Unique identifier assigned by the initiating party to identify the bulk payment. This attribute can be used by the ASPSP as an optional field."
}
}
}
}
}
{
"required": [
"startDate",
"frequency"
],
"allOf": [
{
"$ref": "#\/definitions\/SinglePayment"
},
{
"properties": {
"startDate": {
"type": "string",
"description": "El primer día aplicable de ejecución desde esta fecha es el primer pago",
"x-ibm-languages": {
"description": {
"en": "The first applicable day of execution from this date is the first payment"
}
}
},
"executionRule": {
"type": "string",
"description": "Define el comportamiento cuando las fechas del pago recurrente caen en fin de semana o festivo. Entonces el pago se ejecuta el día laboral anterior o posterior",
"x-ibm-languages": {
"description": {
"en": "Define the behavior when recurring payment dates fall on weekends or holidays. Then the payment is executed the previous or subsequent business day"
}
}
},
"endDate": {
"type": "string",
"description": "El último día aplicable de ejecución. Si no viene se trata de una orden permanente sin fin.",
"x-ibm-languages": {
"description": {
"en": "The last applicable day of execution. If it does not come, it is an endless permanent order."
}
}
},
"frequency": {
"type": "string",
"description": "La frecuencia del pago recurrente resultante de esta orden permanente",
"x-ibm-languages": {
"description": {
"en": "The frequency of recurring payment resulting from this permanent order"
}
}
},
"dayOfExecution": {
"type": "string",
"description": "La fecha se refiere a la zona horaria del ASPSP",
"x-ibm-languages": {
"description": {
"en": "The date refers to the time zone of the ASPSP"
}
}
}
}
}
]
}
{
"required": [
"paymentId",
"transactionStatus",
"_links"
],
"properties": {
"transactionStatus": {
"type": "string",
"description": "Estado de la transaccion",
"x-ibm-languages": {
"description": {
"en": "Transaction Status"
}
},
"example": "RCVD"
},
"paymentId": {
"properties": [],
"type": "string",
"description": "Identificador del recurso que referencia a la iniciación de pago.",
"x-ibm-languages": {
"description": {
"en": "Identifier of the resource that refers to the initiation of payment."
}
},
"example": "1b3ab8e8-0fd5-43d2-946e-d75958b172e7"
},
"transactionFees": {
"properties": [],
"description": "Comisiones asociadas al pago.",
"x-ibm-languages": {
"description": {
"en": "Fees associated with payment."
}
},
"example": "",
"$ref": "#\/definitions\/Amount"
},
"currencyConversionFee": {
"type": "object",
"description": "Podría ser usado por el ASPSP para transportar comisiones por conversión específica de la moneda asociada a la transferencia de crédito iniciada.",
"additionalProperties": {
"$ref": "#\/definitions\/Amount"
},
"x-ibm-languages": {
"description": {
"en": "It could be used by the ASPSP to carry currency-specific conversion fees associated with the initiated credit transfer."
}
}
},
"estimatedTotalAmount": {
"type": "object",
"description": "Importe el cual se estima que será retirado de la cuenta del ordenante. Nota: este importe incluye comisiones.",
"additionalProperties": {
"$ref": "#\/definitions\/Amount"
},
"x-ibm-languages": {
"description": {
"en": "Amount estimated to be withdrawn from the payer´s account. Note: this amount includes commissions."
}
}
},
"estimatedInterbankSettlemenAmount": {
"type": "object",
"description": "Importe estimado a ser transferido al beneficiario.",
"additionalProperties": {
"$ref": "#\/definitions\/Amount"
},
"x-ibm-languages": {
"description": {
"en": "Estimated amount to be transferred to the beneficiary."
}
}
},
"transactionFeeIndicator": {
"properties": [],
"type": "boolean",
"description": "Si es igual a \"true\", la transacción implicará una comisión según el ASPSP o según lo acordado entre ASPSP y PSU. Si es igual a \"false\", la transacción no implicará ninguna comisión adicional para el PSU.",
"x-ibm-languages": {
"description": {
"en": "If it is equal to \"true\", the transaction will involve a commission according to the ASPSP or as agreed between ASPSP and PSU. If it is equal to \"false\", the transaction will not imply any additional commission for the PSU. "
}
},
"example": "\"transactionFeeIndicator\": true"
},
"scaMethods": {
"$ref": "#\/definitions\/List_AuthenticationObject",
"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": {
"properties": [],
"description": "Lista de hipervínculos para ser reconocidos por el TPP. Tipos soportados en esta respuesta:",
"x-ibm-languages": {
"description": {
"en": "List of hyperlinks to be recognized by the TPP. Types supported in this answer: "
}
},
"$ref": "#\/definitions\/Links"
},
"psuMessage": {
"properties": [],
"type": "string",
"example": "Informacion para el PSU",
"description": "Texto a mostrar al PSU.",
"x-ibm-languages": {
"description": {
"en": "Text to display to the PSU."
}
}
},
"tppMessages": {
"properties": [],
"$ref": "#\/definitions\/List_TppMessage",
"description": "Mensaje para el TPP",
"x-ibm-languages": {
"description": {
"en": "Message for the TPP"
}
}
}
},
"additionalProperties": false
}
{
"type": "object",
"properties": {
"transactionStatus": {
"type": "string",
"description": "Estado de la transacción de pago. Valores definidos en 9.4 Estados de transacción"
},
"fundsAvailable": {
"type": "boolean",
"description": "Este dato es contenido si es soportado por el ASPSP, si una confirmación de fondos ha sido realizada y si el “transactionStatus” es ATCT, ACWC, ACCP"
},
"psuMessage": {
"type": "string",
"description": "Texto a mostrar al PSU."
},
"tppMessages": {
"$ref": "#\/definitions\/List_TppMessage",
"description": "Mensaje para el TPP."
},
"ownerNames": {
"description": "Listado de nombres de propietarios de la cuenta.",
"x-ibm-languages": {
"description": {
"en": "List of names of account owners."
}
},
"additionalProperties": {
"$ref": "#\/definitions\/AccountOwner"
}
},
"psuName": {
"type": "string",
"description": "Nombre del PSU conectado.En caso de cuentas corporativas, esto podría ser la persona que actúe en nombre de la empresa.",
"x-ibm-languages": {
"description": {
"en": "Name of the connected PSU. In case of corporate accounts, this could be the person acting on behalf of the company."
}
},
"example": "Heike Mustermann"
}
},
"required": [
"transactionStatus"
]
}
{
"allOf": [
{
"$ref": "#\/definitions\/SinglePayment"
},
{
"properties": {
"transactionStatus": {
"type": "string",
"description": "Estado de la transacción. Valores definidos en anexos. Código corto."
},
"psuMessage": {
"type": "string",
"description": "Texto enviado al TPP a través del HUB para ser mostrado al PSU."
},
"tppMessages": {
"$ref": "#\/definitions\/List_TppMessage",
"description": "Mensaje para el TPP enviado a través del HUB."
}
}
}
],
"required": [
"debtorAccount",
"transactionStatus",
"instructedAmount",
"creditorAccount",
"creditorName"
]
}
{
"properties": {
"transactionStatus": {
"type": "string",
"description": "Estado de la transacción."
},
"scaMethods": {
"$ref": "#\/definitions\/List_AuthenticationObject",
"description": "Este elemento es contenido si SCA es requerido y si el PSU puede elegir entre diferentes métodos de autenticación. "
},
"_links": {
"$ref": "#\/definitions\/Links",
"description": "Lista de hipervínculos para ser reconocidos por el TPP. Dependen de la decisión que tome el ASPSP dinámicamente al evaluar la operación. "
},
"psuMessage": {
"type": "string",
"description": "Texto enviado al TPP a través del HUB para ser mostrado al PSU."
},
"tppMessages": {
"$ref": "#\/definitions\/List_TppMessage",
"description": "Mensaje para el TPP enviado a través del HUB."
}
},
"required": [
"transactionStatus"
]
}
{
"type": "object",
"properties": {
"unitCurrency": {
"type": "string",
"description": "Moneda en la que el tipo de intercambio es expresado en moneda extranjera. En el siguiente ejemplo 1EUR = xxxCUR, la unidad monetaria es el EUR.",
"example": "USD",
"x-ibm-languages": {
"description": {
"en": "Currency in which the exchange rate is expressed in foreign currency. In the following example 1EUR = xxxCUR, the currency unit is EUR."
}
}
},
"exchangeRate": {
"type": "string",
"description": "Factor usado para convertir un importe en una moneda a otra. Refleja el precio en el cual una moneda fue comprada con otra moneda.",
"example": "0.8",
"x-ibm-languages": {
"description": {
"en": "Factor used to convert an amount in one currency to another. Reflects the price at which one currency was purchased with another currency."
}
}
},
"contractIdentification": {
"type": "string",
"description": "Identificación única para identificar el contrato de cambio de divisas",
"example": "1234-qeru-23",
"x-ibm-languages": {
"description": {
"en": "Unique identification to identify the foreign exchange contract"
}
}
},
"rateType": {
"type": "string",
"description": "Especifica el tipo usado para completar el cambio de moneda. Valores permitidos: SPOT, SALE, AGRD.",
"x-ibm-languages": {
"description": {
"en": "Specifies the type used to complete the currency exchange. Allowed values: SPOT, SALE, AGRD."
}
}
}
}
}
{
"required": [
"reference"
],
"type": "object",
"properties": {
"reference": {
"type": "string",
"description": "Refencia actual"
},
"referenceType": {
"type": "string",
"description": "Tipo de la refencia"
},
"referenceIssuer": {
"type": "string",
"description": "Emisor de la refencia"
}
}
}
{
"type": "array",
"items": {
"$ref": "#\/definitions\/Remittance"
}
}
{
"type": "object",
"properties": {
"endToEndIdentification": {
"type": "string",
"description": "Identificador único end to end.",
"x-ibm-languages": {
"description": {
"en": "Unique end to end identifier."
}
}
},
"instructionIdentification": {
"type": "string",
"description": "Identificación única de la instrucción asignada por la parte instructora",
"x-ibm-languages": {
"description": {
"en": "Unique identification of the instruction assigned by the instructing party"
}
}
},
"debtorName": {
"type": "string",
"description": "Nombre del ordenante",
"x-ibm-languages": {
"description": {
"en": "Name of payer"
}
}
},
"debtorAccount": {
"type": "object",
"description": "Cuenta del ordenante. Nota: este campo puede ser opcional en algunos servicios como pagos bulk",
"additionalProperties": {
"$ref": "#\/definitions\/AccountReference"
},
"x-ibm-languages": {
"description": {
"en": "Account of the payer. Note: this field may be optional in some services such as bulk payments."
}
}
},
"debtorId": {
"type": "string"
},
"ultimateDebtor": {
"type": "string"
},
"instructedAmount": {
"type": "object",
"description": "Información de la transferencia realizada.",
"additionalProperties": {
"$ref": "#\/definitions\/Amount"
},
"x-ibm-languages": {
"description": {
"en": "Transfer information made."
}
}
},
"currencyOfTranfer": {
"type": "string"
},
"exchangeRateInformation": {
"type": "object",
"additionalProperties": {
"$ref": "#\/definitions\/PaymentExchangeRate"
}
},
"creditorAccount": {
"type": "object",
"description": "Cuenta del ordenante. Nota: este campo puede ser opcional en algunos servicios como pagos bulk",
"additionalProperties": {
"$ref": "#\/definitions\/AccountReference"
},
"x-ibm-languages": {
"description": {
"en": "Account of the payer. Note: this field may be optional in some services such as bulk payments."
}
}
},
"creditorAgent": {
"type": "string",
"description": "BIC de la cuenta del beneficiario",
"example": "XXXLESMMXXX",
"x-ibm-languages": {
"description": {
"en": "BIC of the beneficiary's account"
}
}
},
"creditorName": {
"type": "string",
"description": "Nombre del beneficiario",
"example": "Nombre",
"x-ibm-languages": {
"description": {
"en": "Beneficiary Name"
}
}
},
"creditorId": {
"type": "string"
},
"creditorAddress": {
"type": "object",
"description": "Direccion Beneficiario",
"additionalProperties": {
"$ref": "#\/definitions\/Address"
},
"x-ibm-languages": {
"description": {
"en": "Beneficiary Address"
}
}
},
"creditorNameAndAddress": {
"type": "string"
},
"purposeCode": {
"type": "string",
"description": "Lista de códigos ISO",
"x-ibm-languages": {
"description": {
"en": "List of ISO codes"
}
}
},
"chargeBearer": {
"type": "string",
"description": "Valores permitidos: Valores permitidos: • DEBT • CRED • SHAR • SLEV",
"example": "SLEV",
"x-ibm-languages": {
"description": {
"en": "Allowed values: Allowed values: • DEBT • CRED • SHAR • SLEV"
}
}
},
"serviceLevel": {
"type": "string",
"description": "Nivel de servicio.",
"x-ibm-languages": {
"description": {
"en": "Level of service."
}
}
},
"remittanceInformationUnstructured": {
"type": "string",
"description": "Informacion Adicional",
"example": "Informacion adicional",
"x-ibm-languages": {
"description": {
"en": "Additional Information"
}
}
},
"remittanceInformationUnstructuredArray": {
"type": "array",
"items": {
"type": "string"
}
},
"remittanceInformationStructured": {
"type": "object",
"additionalProperties": {
"$ref": "#\/definitions\/Remittance"
}
},
"remittanceInformationStructuredArray": {
"type": "object",
"additionalProperties": {
"$ref": "#\/definitions\/List_Remittance"
}
},
"requestedExecutionDate": {
"type": "string",
"description": "Fecha de ejecución",
"x-ibm-languages": {
"description": {
"en": "Date of execution"
}
}
},
"requestedExecutionTime": {
"type": "string",
"description": "Fecha\/hora de ejecución",
"x-ibm-languages": {
"description": {
"en": "Date\/time of execution"
}
}
}
},
"additionalProperties": true
}
{
"required": [
"paymentId",
"transactionStatus",
"_links"
],
"type": "object",
"properties": {
"transactionStatus": {
"type": "string",
"description": "Estado de la transaccion",
"example": "RCVD",
"x-ibm-languages": {
"description": {
"en": "Transaction Status"
}
}
},
"paymentId": {
"type": "string",
"description": "Identificador del recurso que referencia a la iniciación de pago.",
"example": "1b3ab8e8-0fd5-43d2-946e-d75958b172e7",
"x-ibm-languages": {
"description": {
"en": "Identifier of the resource that refers to the initiation of payment."
}
}
},
"transactionFees": {
"type": "object",
"description": "Comisiones asociadas al pago.",
"additionalProperties": {
"$ref": "#\/definitions\/Amount"
},
"x-ibm-languages": {
"description": {
"en": "Fees associated with payment."
}
}
},
"transactionFeeIndicator": {
"type": "boolean",
"description": "Si es igual a \"true\", la transacción implicará una comisión según el ASPSP o según lo acordado entre ASPSP y PSU. Si es igual a \"false\", la transacción no implicará ninguna comisión adicional para el PSU.",
"example": false,
"x-ibm-languages": {
"description": {
"en": "If it is equal to \"true\", the transaction will involve a commission according to the ASPSP or as agreed between ASPSP and PSU. If it is equal to \"false\", the transaction will not imply any additional commission for the PSU. "
}
}
},
"scaMethods": {
"type": "object",
"description": "Este elemento es contenido si SCA es requerido y si el PSU puede elegir entre diferentes métodos de autenticación.",
"additionalProperties": {
"$ref": "#\/definitions\/List_AuthenticationObject"
},
"x-ibm-languages": {
"description": {
"en": "This element is content if SCA is required and if the PSU can choose between different authentication methods."
}
}
},
"choosenScaMethod": {
"type": "object",
"description": "NO SOPORTADO EN ESTA VERSIÓN. SOLO EMBEBIDO",
"additionalProperties": {
"$ref": "#\/definitions\/AuthenticationObject"
},
"x-ibm-languages": {
"description": {
"en": "NOT SUPPORTED IN THIS VERSION. EMBEDDED ONLY"
}
}
},
"_links": {
"type": "object",
"description": "Lista de hipervínculos para ser reconocidos por el TPP. Tipos soportados en esta respuesta:",
"additionalProperties": {
"$ref": "#\/definitions\/Links"
},
"x-ibm-languages": {
"description": {
"en": "List of hyperlinks to be recognized by the TPP. Types supported in this answer: "
}
}
},
"psuMessage": {
"type": "string",
"description": "Texto enviado al TPP a través del HUB para ser mostrado al PSU.",
"example": "Mensaje de ejemplo",
"x-ibm-languages": {
"description": {
"en": "Text sent to the TPP through the HUB to be displayed to the PSU."
}
}
},
"tppMessages": {
"type": "object",
"description": "Mensaje para el TPP enviado a través del HUB.",
"additionalProperties": {
"$ref": "#\/definitions\/List_TppMessage"
},
"x-ibm-languages": {
"description": {
"en": "Message for the TPP sent through the HUB."
}
}
}
},
"additionalProperties": true
}
{
"required": [
"paymentId",
"transactionStatus",
"_links"
],
"type": "object",
"properties": {
"transactionStatus": {
"type": "string",
"description": "Estado de la transaccion",
"example": "RCVD",
"x-ibm-languages": {
"description": {
"en": "Transaction Status"
}
}
},
"paymentId": {
"type": "string",
"description": "Identificador del recurso que referencia a la iniciación de pago.",
"example": "1b3ab8e8-0fd5-43d2-946e-d75958b172e7",
"x-ibm-languages": {
"description": {
"en": "Identifier of the resource that refers to the initiation of payment."
}
}
},
"transactionFees": {
"type": "object",
"description": "Comisiones asociadas al pago.",
"additionalProperties": {
"$ref": "#\/definitions\/Amount"
},
"x-ibm-languages": {
"description": {
"en": "Fees associated with payment."
}
}
},
"transactionFeeIndicator": {
"type": "boolean",
"description": "Si es igual a \"true\", la transacción implicará una comisión según el ASPSP o según lo acordado entre ASPSP y PSU. Si es igual a \"false\", la transacción no implicará ninguna comisión adicional para el PSU.",
"example": false,
"x-ibm-languages": {
"description": {
"en": "If it is equal to \"true\", the transaction will involve a commission according to the ASPSP or as agreed between ASPSP and PSU. If it is equal to \"false\", the transaction will not imply any additional commission for the PSU. "
}
}
},
"scaMethods": {
"type": "object",
"description": "Este elemento es contenido si SCA es requerido y si el PSU puede elegir entre diferentes métodos de autenticación.",
"additionalProperties": {
"$ref": "#\/definitions\/List_AuthenticationObject"
},
"x-ibm-languages": {
"description": {
"en": "This element is content if SCA is required and if the PSU can choose between different authentication methods."
}
}
},
"choosenScaMethod": {
"type": "object",
"description": "NO SOPORTADO EN ESTA VERSIÓN. SOLO EMBEBIDO",
"additionalProperties": {
"$ref": "#\/definitions\/AuthenticationObject"
},
"x-ibm-languages": {
"description": {
"en": "NOT SUPPORTED IN THIS VERSION. EMBEDDED ONLY"
}
}
},
"_links": {
"type": "object",
"description": "Lista de hipervínculos para ser reconocidos por el TPP. Tipos soportados en esta respuesta:",
"additionalProperties": {
"$ref": "#\/definitions\/Links"
},
"x-ibm-languages": {
"description": {
"en": "List of hyperlinks to be recognized by the TPP. Types supported in this answer: "
}
}
},
"psuMessage": {
"type": "string",
"description": "Texto enviado al TPP a través del HUB para ser mostrado al PSU.",
"example": "Mensaje de ejemplo",
"x-ibm-languages": {
"description": {
"en": "Text sent to the TPP through the HUB to be displayed to the PSU."
}
}
},
"tppMessages": {
"type": "object",
"description": "Mensaje para el TPP enviado a través del HUB.",
"additionalProperties": {
"$ref": "#\/definitions\/List_TppMessage"
},
"x-ibm-languages": {
"description": {
"en": "Message for the TPP sent through the HUB."
}
}
}
},
"additionalProperties": true
}
{
"type": "object",
"properties": {
"instructedAmount": {
"$ref": "#\/definitions\/Amount",
"description": "Información de la transferencia realizada.",
"x-ibm-languages": {
"description": {
"en": "Transfer information made."
}
}
},
"creditorName": {
"type": "string",
"description": "Nombre del beneficiario",
"x-ibm-languages": {
"description": {
"en": "Beneficiary Name"
}
},
"example": "Nombre"
},
"creditorAccount": {
"$ref": "#\/definitions\/AccountReference",
"description": "Cuenta del ordenante. Nota: este campo puede ser opcional en algunos servicios como pagos bulk",
"x-ibm-languages": {
"description": {
"en": "Account of the payer. Note: this field may be optional in some services such as bulk payments."
}
}
},
"creditorAgent": {
"type": "string",
"description": "BIC de la cuenta del beneficiario",
"x-ibm-languages": {
"description": {
"en": "BIC of the beneficiary's account"
}
},
"example": "XXXLESMMXXX"
},
"creditorAddress": {
"$ref": "#\/definitions\/Address",
"description": "Direccion Beneficiario",
"x-ibm-languages": {
"description": {
"en": "Beneficiary Address"
}
}
},
"remittanceInformationUnstructured": {
"type": "string",
"description": "Informacion Adicional",
"x-ibm-languages": {
"description": {
"en": "Additional Information"
}
},
"example": "Informacion adicional"
},
"endToEndIdentification": {
"type": "string",
"description": "Identificador único de la operación asignado por la parte iniciadora (TPP)"
},
"chargeBearer": {
"type": "string",
"description": "Valores permitidos: Valores permitidos: • DEBT • CRED • SHAR • SLEV",
"x-ibm-languages": {
"description": {
"en": "Allowed values: Allowed values: • DEBT • CRED • SHAR • SLEV"
}
},
"example": "SLEV"
}
}
}
{
"properties": {
"category": {
"type": "string",
"description": "Categoría del tipo de mensaje recibido. Posibles valores: ERROR o WARNING",
"x-ibm-languages": {
"description": {
"en": "Category of the type of message received. Possible values: ERROR or WARNING "
}
},
"example": "ERROR"
},
"code": {
"properties": [],
"type": "string",
"description": "Código de respuesta.",
"x-ibm-languages": {
"description": {
"en": "Response code."
}
},
"example": "CONSENT_INVALID"
},
"path": {
"properties": [],
"type": "string",
"description": "Path al campo referenciando el error.",
"x-ibm-languages": {
"description": {
"en": "Path to the field referencing the error."
}
}
},
"text": {
"properties": [],
"type": "string",
"description": "Texto adicional explicativo.",
"x-ibm-languages": {
"description": {
"en": "Additional explanatory text."
}
},
"example": "Ejemplo"
}
},
"additionalProperties": false,
"required": [
"code",
"category"
]
}
{
"type": "object",
"properties": {
"name": {
"description": "Nombre propietario de la cuenta.",
"x-ibm-languages": {
"description": {
"en": "Account owner name."
}
}
},
"role": {
"description": "Los siguientes códigos de propietarios son usados: \"owner\",\"legalRepresentative\",\"authorisedUser\"",
"x-ibm-languages": {
"description": {
"en": "The following owner codes are used: \"owner\", \"legalRepresentative\", \"authorizedUser\"."
}
}
}
},
"additionalProperties": true,
"required": [
"name"
]
}