# Specification Release Notes source: https://developer.mastercard.com/open-banking-connect/documentation/specification-release-notes/index.md *** ** * ** *** Specified releases of the Open Banking Connect service are detailed here. Any information is only relevant to the stated release. The current release number is **1.64.0**. Note: Release notes were previously delivered in pdf format. For release notes prior to release 1.23.0, refer to [Specification Release Documentation](https://developer.mastercard.com/open-banking-connect/documentation/specification-release-documentation/index.md), where supplementary documentation is also available. ## Release 1.64.0 Sandbox, Pre-Production, and Production {#release-1640-sandbox-pre-production-and-production} Release 1.64.0 provides the following enhancements to all environments, Sandbox, Pre-Production, and Production. * TPPs will receive detailed errors, which already exist in the Open Banking Connect API, for specific expired/invalid consent scenarios. Previously, the generic PROVIDER_ERROR was received. * For Get Account Transactions and Get Transaction Details API responses, the `auxData` object will return the TPP currency exchange details when provided by the bank. These currency details can be returned in the response: `sourceCurrency`, `targetCurrency` and `exchangeRate`. For example, `"auxData":{"exchangeRate":"1", "sourceCurrency":"USD", "targetCurrency": "HUF"}` ## Release 1.61.1 Sandbox, Pre-Production, and Production {#release-1611-sandbox-pre-production-and-production} Release 1.61.1 provides enhancements to the API Specification, including scheduled changes and improvements. Enhancements detailed here are applicable to all environments, Sandbox, Pre-Production, and Production. #### Additional paymentContextCode values for Domestic Payment Initiation Consent {#additional-paymentcontextcode-values-for-domestic-payment-initiation-consent} Mastercard Open Banking Connect has enabled new Payment Context Code (paymentContextCode) values in the Domestic Payment Consent Initiation request (POST /payments/domestic-credit-transfers/consents). * `BillingGoodsAndServicesInAdvance` * `BillingGoodsAndServicesInArrears` * `EcommerceMerchantInitiatedPayment` * `FaceToFacePointOfSale` * `TransferToSelf` * `TransferToThirdParty` * `PispPayee` The `PispPayee` value can be used for banks exposing APIs based on version 3.x of the OBIE specifications. All other values are recommended for use by banks migrating to version 4.0 of the specifications (e.g. HSBC in June). Note that if invalid risk details (e.g. PCC) are included in the request by a TPP, an empty risk object will be sent to the ASPSPs, in order to reduce the probability of rejections. ## Release 1.60.0 Sandbox, Pre-Production, and Production {#release-1600-sandbox-pre-production-and-production} Release 1.60.0 provides enhancements to the API Specification, including scheduled changes and improvements. Enhancements detailed here are applicable to all environments, Sandbox, Pre-Production, and Production. #### Error for expired consent {#error-for-expired-consent} A 400 error is now returned when a TPP submits a Get List of Accounts or Get Account details request to a Revolut ASPSP with a consent older than five minutes. The ASPSP will reject the request and Open Banking Connect will return the following error to the TPP: * "ReasonCode": "PROVIDER_ERROR", * "Description": "New SCA required" #### Error for invalid datas {#error-for-invalid-datas} A 400 error is now returned when a TPP submits invalid data in an Account Information or Payment Initiation request. The ASPSP will reject the request and Open Banking Connect will return the following error to the TPP: * "ReasonCode": "FORMAT_ERROR", * "Description": "Invalid Input" #### Errors for invalid account and MCC data {#errors-for-invalid-account-and-mcc-data} A 400 error is now returned when a TPP submits a Domestic payment initiation consent to UK ASPSPs and provides invalid details in the creditorAccount identification, debtorAccount identification or merchantCategoryCode fields: Creditor account has an invalid format (contains letters or the length is different than eight digits) * "ReasonCode": "PROVIDER_ERROR", * "Description": "Invalid creditorAccount identification"
Debtor account has an invalid format (contains letters or the length is different than eight digits) * "ReasonCode": "PROVIDER_ERROR", * "Description": "Invalid debtorAccount identification"
Merchant Category Code has an invalid format (more than 3-4 characters) * "ReasonCode": "PROVIDER_ERROR", * "Description": "Invalid merchantCategoryCode" #### Handling of UK in Domestic Payment Consent Initiation risk object {#handling-of-uk-in-domestic-payment-consent-initiation-risk-object} Updates have been made to replace 'UK' with 'GB' in the risk.country field for Domestic Payment Consent Initiation requests to Bank of Ireland (UK). This is done to ensure that requests are not rejected by the ASPSP. ## Release 1.59.0 Sandbox, Pre-Production, and Production {#release-1590-sandbox-pre-production-and-production} Cross-Border payments have been removed from the Open Banking Connect API specification to be consistent with the list of supported capabilities. ## Release 1.58.0 {#release-1580} No customer facing changes have been implemented in the API specification in release 1.58.0. ## Release 1.57.0 {#release-1570} Release 1.57.0 provides enhancements to the API Specification, including scheduled changes and improvements. Enhancements detailed here are applicable to all environments, Sandbox, Pre-Production, and Production. #### Error for Consent request when specific payment rails are not supported {#error-for-consent-request-when-specific-payment-rails-are-not-supported} A 400 error is now returned when a TPP submits a Domestic Payment Initiation Consent or a SEPA Payment Initiation Consent request to a bank that does not support specific payment rails ('UK.FasterPayments', 'PL.Elixir', 'HU.DomesticNonEuro', 'SEPA', 'SEPA_INSTANT'): * "ReasonCode": "PROVIDER_ERROR", * "Description": ''LocalInstrument not supported by the bank" #### Error for Get List of Transactions request when specified date range is not supported {#error-for-get-list-of-transactions-request-when-specified-date-range-is-not-supported} A 400 error is now returned when a TPP submits a Get List of Transactions request with a date range which is not supported by the bank. * "ReasonCode": "PROVIDER_ERROR", * "Description": "Requested transaction history is out of bank supported date range" ## Release 1.56.0 {#release-1560} No customer facing changes have been implemented in the API specification in release 1.56.0. ## Release 1.55.0 {#release-1550} No customer facing changes have been implemented in the API specification in release 1.55.0. ## Release 1.54.0 Sandbox and Pre-Production {#release-1540-sandbox-and-pre-production} Release 1.54.0 provides updates to the API functionality and Sandbox testing capabilities. Enhancements detailed here are applicable to both the Sandbox and Pre-Production environments. ### Release enhancements {#release-enhancements} #### Additional PSU details for Delete Consent requests for ASPSPs with Polish API profile {#additional-psu-details-for-delete-consent-requests-for-aspsps-with-polish-api-profile} Additional fields have been added to the Account Information Consent Deletion endpoint to enable ASPSPs to confirm if the PSU is online. These fields are optional and mapped for ASPSPs with Polish API profile only, i.e. only to be used for the Poland market. * `isLivePsuRequest` - This field indicates if the PSU actively initiated the request. * `psuIPAddress` - The forwarded IP address field consists of the corresponding HTTP request IP address field between the PSU and TPP. * `psuAgent` - This field indicates the user-agent for the PSU. ## Release 1.53.0 {#release-1530} No customer facing changes have been implemented in release 1.53.0. ## Release 1.52.0 {#release-1520} Release 1.52.0 provides enhancements to the API Specification, including scheduled changes and improvements. Enhancements detailed here are applicable to all environments, Sandbox, Pre-Production, and Production. #### Error for payment execution scheduled for a bank holiday in a Consent request {#error-for-payment-execution-scheduled-for-a-bank-holiday-in-a-consent-request} A 400 error is now returned when a TPP submits a PIS domestic consent request where the remittanceInformationReference field has more than 18 characters: * Reason Code: "PROVIDER_ERROR" * Description: "Remittance Information Reference (remittanceInformationReference) is invalid" ## Release 1.51.0 {#release-1510} Release 1.51.0 provides enhancements to the Mastercard Open Banking Connect API functionality. Enhancements detailed here are applicable to all environments, Sandbox, Pre-Production, and Production. #### Domestic Payment Credit Transfer and Get Domestic Payment response enhancements {#domestic-payment-credit-transfer-and-get-domestic-payment-response-enhancements} A more granular `transactionStatus` mapping has been implemented in Mastercard Open Banking Connect, avoiding scenarios where `transactionStatus` is not sent in response to Domestic Payment Credit Transfer and Get Domestic Payment Status requests sent by the TPPs. ## Release 1.50.0 {#release-1500} Release 1.50.0 provides enhancements to the API Specification, including scheduled changes and improvements. Enhancements detailed here are applicable to all environments, Sandbox, Pre-Production, and Production. #### Error for payment execution scheduled for a bank holiday in a Consent request {#error-for-payment-execution-scheduled-for-a-bank-holiday-in-a-consent-request-1} A 400 error is now returned when a TPP submits a Consent request with payment execution scheduled for a bank holiday. * Reason Code: "PROVIDER_ERROR" * Description: "Payment execution is scheduled on a bank holiday" ## Release 1.49.0 {#release-1490} Release 1.49.0 provides enhancements to the API Specification, including scheduled changes and improvements. Enhancements detailed here are applicable to all environments, Sandbox, Pre-Production, and Production. #### Error for missing mandatory details in a Consent request {#error-for-missing-mandatory-details-in-a-consent-request} A 400 error is now returned when a TPP submits a Consent request without providing a field required by the ASPSP. * Reason Code: "PROVIDER_ERROR" * Description: "Missing mandatory details" ## Release 1.48.0 {#release-1480} Release 1.48.0 provides updates to the API functionality and Sandbox testing capabilities. Enhancements detailed here are applicable to the Sandbox and Pre-Production, and Production environments unless stated otherwise. ### Release enhancements {#release-enhancements-1} #### Error for SEPA Payment Initiation Consent requests that exceed decimal places limit {#error-for-sepa-payment-initiation-consent-requests-that-exceed-decimal-places-limit} An error is now returned when a TPP submits a SEPA Payment Initiation Consent request with the amount field having more than four decimal places to ASPSPs supporting NextGenPSD2 or STET API profiles. * Reason Code: "FORMAT_ERROR" * Description: "Remainder of division is not zero (amount / decimals factor)" #### Error for Delete AIS Consent requests to ASPSPs that do not have delete capability {#error-for-delete-ais-consent-requests-to-aspsps-that-do-not-have-delete-capability} An error is now returned when a TPP submits a Delete AIS consent request to an ASPSP for which the capability was not implemented. * Reason Code: "PROVIDER_ERROR" * Description: "Delete consent not implemented for this ASPSP" Note: In this instance the consent becomes unusable, but is not deleted from bank records. ## Release 1.47.0 Production {#release-1470-production} Release 1.47.0 provides updates to the API functionality, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-2} #### Dedicated error for an invalid long-lived consent request {#dedicated-error-for-an-invalid-long-lived-consent-request} Short-lived consent is required before long-lived consent can be validated. A dedicated error message has been introduced for instances where a TPP submits an [Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/account-information-consent/index.md) request to Erste bank for long-lived consent, without having a valid short-lived consent. * Reason Code: PROVIDER_ERROR * Description: "Short-lived consent must be submitted before the long-lived one" Note: Short-lived consent requires the AIS consent request `validUntilDateTime` parameter to be `<24 hours`, and long-lived consent to be `>24 hours`. ## Release 1.47.0 Sandbox and Pre-Production {#release-1470-sandbox-and-pre-production} Release 1.47.0 provides updates to the API functionality and Sandbox testing capabilities. Enhancements detailed here are applicable to both the Sandbox and Pre-Production environments unless stated otherwise. ### Release enhancements {#release-enhancements-3} #### Dedicated error for an invalid long-lived consent request {#dedicated-error-for-an-invalid-long-lived-consent-request-1} Short-lived consent is required before long-lived consent can be validated. A dedicated error message has been introduced for instances where a TPP submits an [Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/account-information-consent/index.md) request to Erste bank for long-lived consent, without having a valid short-lived consent. * Reason Code: PROVIDER_ERROR * Description: "Short-lived consent must be submitted before the long-lived one" Note: Short-lived consent requires the AIS consent request `validUntilDateTime` parameter to be `<24 hours`, and long-lived consent to be `>24 hours`. ## Release 1.46.0 Production {#release-1460-production} Release 1.46.0 provides updates to the API functionality, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-4} #### Get List of ASPSPs Enhancements (AIS and PIS) {#get-list-of-aspsps-enhancements-ais-and-pis} The Get List of ASPSPs response had been updated to include the `allLogos` array of objects that includes the details, file type and logo URL, of all ASPSP logos. * [Get List of ASPSPs (AIS)](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) * [Get List of ASPSPs (PIS)](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-list-of-aspsps/index.md) #### Slovak API Profile Enhancements {#slovak-api-profile-enhancements} Updates have been made so that when a TPP submits a Get Account Transactions or Get Transaction Details request to an ASPSP that supports the Slovak API Profile, Mastercard Open Banking Connect returns the debtor and creditor accounts in BBAN format, as provided by the ASPSP. #### Czech API Profile Enhancements {#czech-api-profile-enhancements} Updates have been made so that when a TPP submits a Get Account Transactions or Get Transaction Details request to an ASPSP that supports the Czech API Profile, Mastercard Open Banking Connect returns the debtor and creditor accounts in BBAN format, as provided by the ASPSP. #### Error handling updates {#error-handling-updates} ##### Unsupported consent expiration {#unsupported-consent-expiration} Updates have been made to display an message when TPPs include the `validUntilDateTime` parameter in an AIS Consent Request and customized consent expiration is not supported by the ASPSP. * Source: OBC * Reason Code: PROVIDER_ERROR * Description: "Setting consent expiration not supported by bank" ##### Error translation for existing error messages {#error-translation-for-existing-error-messages} Updates have been made to translate specific errors sent by ASPSPs to existing error messages in Mastercard Open Banking Connect related to invalid, revoked or expired consent. For invalid or revoked consent: * Reason Code:INVALID_TOKEN * Description: "Access Token associated with the Request is invalid or has been revoked" For expired consent: * Reason Code: INVALID_TOKEN * Description: "Access Token associated with the Request has expired"\` The error messages are valid for these endpoints: | **AIS** | **PIS** | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------| | * Get List of Accounts * Get Account Details * Get Account Balances * Get Account Transactions * Get Transaction Details * Delete consent * Get Account Standing Orders Request * Get Raw Consent | * Domestic Credit Transfer - Get Status * SEPA Credit Transfer - Get Status * Cross-border Credit Transfer - Get Status | ## Release 1.46.0 Sandbox and Pre-Production {#release-1460-sandbox-and-pre-production} Release 1.46.0 provides updates to the API functionality and Sandbox testing capabilities. Enhancements detailed here are applicable to both the Sandbox and Pre-Production environments unless stated otherwise. ### Release enhancements {#release-enhancements-5} #### Get List of ASPSPs Enhancements (AIS and PIS) {#get-list-of-aspsps-enhancements-ais-and-pis-1} The Get List of ASPSPs response had been updated to include the `allLogos` array of objects that includes the details, file type and logo URL, of all ASPSP logos. * [Get List of ASPSPs (AIS)](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) * [Get List of ASPSPs (PIS)](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-list-of-aspsps/index.md) #### Slovak API Profile Enhancements {#slovak-api-profile-enhancements-1} Updates have been made so that when a TPP submits a Get Account Transactions or Get Transaction Details request to an ASPSP that supports the Slovak API Profile, Mastercard Open Banking Connect returns the debtor and creditor accounts in BBAN format, as provided by the ASPSP. #### Czech API Profile Enhancements {#czech-api-profile-enhancements-1} Updates have been made so that when a TPP submits a Get Account Transactions or Get Transaction Details request to an ASPSP that supports the Czech API Profile, Mastercard Open Banking Connect returns the debtor and creditor accounts in BBAN format, as provided by the ASPSP. #### Error handling updates {#error-handling-updates-1} ##### Unsupported consent expiration {#unsupported-consent-expiration-1} Updates have been made to display an message when TPPs include the `validUntilDateTime` parameter in an AIS Consent Request and customized consent expiration is not supported by the ASPSP. * Source: OBC * Reason Code: PROVIDER_ERROR * Description: "Setting consent expiration not supported by bank" ##### Error translation for existing error messages {#error-translation-for-existing-error-messages-1} Updates have been made to translate specific errors sent by ASPSPs to existing error messages in Mastercard Open Banking Connect related to invalid, revoked or expired consent. For invalid or revoked consent: * Reason Code:INVALID_TOKEN * Description: "Access Token associated with the Request is invalid or has been revoked" For expired consent: * Reason Code: INVALID_TOKEN * Description: "Access Token associated with the Request has expired"\` The error messages are valid for these endpoints: | **AIS** | **PIS** | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------| | * Get List of Accounts * Get Account Details * Get Account Balances * Get Account Transactions * Get Transaction Details * Delete consent * Get Account Standing Orders Request * Get Raw Consent | * Domestic Credit Transfer - Get Status * SEPA Credit Transfer - Get Status * Cross-border Credit Transfer - Get Status | ## Release 1.45.0 Production {#release-1450-production} Release 1.45.0 provides updates to the API functionality, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-6} #### Czech API Profile - additional checks for Get Accounts requests removed {#czech-api-profile---additional-checks-for-get-accounts-requests-removed} Open Banking Connect will no longer perform additional Get Accounts requests to the ASPSPs, supporting Czech API profile, as part of the Get Account Balances flow. This will eliminate the need for the TPP to include Accounts permission for the consent used as part of Get Account Balances request. #### Transaction amount value {#transaction-amount-value} API Specifications have been updated to reflect the value of the transaction amount, which can be equal to 0 (zero) in these endpoints: * Get Account Transactions * Get Transaction Details Note: TPPs should be prepared to receive a value equal to 0 (zero) in the transaction amount field. #### Domestic Payment Initiation request update {#domestic-payment-initiation-request-update} Changes have been made to enable TPPs to send debtor's IBAN and BIC data in the Domestic Payment Initiation requests. This will enable the PSU to skip account selection in the ASPSP's user interface (if this was enabled and implemented by the ASPSPs using CMA9 API profile outside UK, e.g. MKB). ## Release 1.45.0 Sandbox and Pre-Production {#release-1450-sandbox-and-pre-production} Release 1.45.0 provides updates to the API functionality and Sandbox testing capabilities. Enhancements detailed here are applicable to both the Sandbox and Pre-Production environments unless stated otherwise. ### Release enhancements {#release-enhancements-7} #### Sandbox enhancements {#sandbox-enhancements} Data Sets for Thallium Bank (Budapest API Profile) in Sandbox have been updated to provide more production-like data to improve customers' testing experience. Refer to OB_Connect_Sandbox_DataSets_R1-45-0.xlsx in [Specification Release Documentation](https://developer.mastercard.com/open-banking-connect/documentation/specification-release-documentation/index.md) for the current data set. #### Czech API Profile - additional checks for Get Accounts requests removed {#czech-api-profile---additional-checks-for-get-accounts-requests-removed-1} Open Banking Connect will no longer perform additional Get Accounts requests to the ASPSPs, supporting Czech API profile, as part of the Get Account Balances flow. This will eliminate the need for the TPP to include Accounts permission for the consent used as part of Get Account Balances request. #### Transaction amount value {#transaction-amount-value-1} API Specifications have been updated to reflect the value of the transaction amount, which can be equal to 0 (zero) in these endpoints: * Get Account Transactions * Get Transaction Details Note: TPPs should be prepared to receive a value equal to 0 (zero) in the transaction amount field. #### Domestic Payment Initiation request update {#domestic-payment-initiation-request-update-1} Changes have been made to enable TPPs to send debtor's IBAN and BIC data in the Domestic Payment Initiation requests. This will enable the PSU to skip account selection in the ASPSP's user interface (if this was enabled and implemented by the ASPSPs using CMA9 API profile outside UK, e.g. MKB). ## Release 1.44.1 Production {#release-1441-production} Release 1.44.1 provides updates to the API functionality, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-8} #### Response and error codes {#response-and-error-codes} * A 400 PROVIDER_ERROR general reason code is now returned when the number of requests exceed a rate limit set by the ASPSP. Refer to [Response and Error Codes](https://developer.mastercard.com/open-banking-connect/documentation/response-and-error-codes/index.md) for details. Note: A rate limit on number of allowed requests is imposed by some ASPSPs and usually allows only a specific number of requests per hour to be performed with the same license. Submit the request later to avoid rejections due to exceeded rate limit. * A dedicated PROVIDER_ERROR 400 error response code has been introduced for situations where a TPP includes an invalid account id, or if the account was unlinked from the consent due to issues with previous requests using the same consent id. * A dedicated PROVIDER_ERROR 400 error response code has been introduced to be returned when the ASPSP limit for unattended requests was exceeded. Note: A limit on unattended calls is imposed by some ASPSPs and usually allows only a maximum of four unattended requests per day. To avoid rejections, ensure that the PSU is present (attended call) and provide PSU details in the request. These reason codes are returned in response to these requests: * [Get List of Accounts](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-list-accounts/index.md) * [Get Account Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-details/index.md) * [Get Account Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) * [Get Account Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) * [Get Account Standing Orders](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-standing-orders/index.md) * [Get Account Balances](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-balances/index.md) * [AIS Get Raw Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-raw-consent/index.md) * [PIS Get Raw Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-raw-consent/index.md) ## Release 1.44.1 Sandbox and Pre-Production {#release-1441-sandbox-and-pre-production} Release 1.44.1 provides updates to the API functionality and Sandbox testing capabilities. Enhancements detailed here are applicable to both the Sandbox and Pre-Production environments unless stated otherwise. ### Release enhancements {#release-enhancements-9} #### Response and error codes {#response-and-error-codes-1} * A 400 PROVIDER_ERROR general reason code is now returned when the number of requests exceed a rate limit set by the ASPSP. Refer to [Response and Error Codes](https://developer.mastercard.com/open-banking-connect/documentation/response-and-error-codes/index.md) for details. Note: A rate limit on number of allowed requests is imposed by some ASPSPs and usually allows only a specific number of requests per hour to be performed with the same license. Submit the request later to avoid rejections due to exceeded rate limit. * A dedicated PROVIDER_ERROR 400 error response code has been introduced for situations where a TPP includes an invalid account id, or if the account was unlinked from the consent due to issues with previous requests using the same consent id. * A dedicated PROVIDER_ERROR 400 error response code has been introduced to be returned when the ASPSP limit for unattended requests was exceeded. Note: A limit on unattended calls is imposed by some ASPSPs and usually allows only a maximum of four unattended requests per day. To avoid rejections, ensure that the PSU is present (attended call) and provide PSU details in the request. These reason codes are returned in response to these requests: * [Get List of Accounts](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-list-accounts/index.md) * [Get Account Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-details/index.md) * [Get Account Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) * [Get Account Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) * [Get Account Standing Orders](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-standing-orders/index.md) * [Get Account Balances](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-balances/index.md) * [AIS Get Raw Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-raw-consent/index.md) * [PIS Get Raw Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-raw-consent/index.md) ## Release 1.44.0 Production {#release-1440-production} Release 1.44.0 provides updates to the API functionality, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-10} #### Addition of Variable Recurring Payment processing capability {#addition-of-variable-recurring-payment-processing-capability} Variable Recurring Payment processing capability has been enabled to provide recurring funds movement within UK accounts using Open Banking (faster payment) without the need of user authentication (SCA at bank) for each payment. For details, refer to [Variable Recurring Payments](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/variable-recurring-payments/index.md). Details for each available VRP endpoint are available here: * [Domestic VRP Consent Initiation](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/domestic-vrp-consent-initiation-request/index.md) * [Initiate Single Immediate VRP Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/initiate-single-immediate-domestic-vrp-payment-request/index.md) * [Get VRP Consent Details](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/get-vrp-consent-details-request/index.md) * [Get VRP Payment Details](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/get-vrp-payment-details-request/index.md) * [Exchange PSU Authorization for VRP Access Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/exchange-psu-authorization-for-vrp-access-consent-request/index.md) * [Delete VRP Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/domestic-vrp-consent-initiation-request/index.md) #### Response and error codes {#response-and-error-codes-2} * A dedicated INVALID_TOKEN 400 error response code has been added for the [Get Account Standing Orders](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-standing-orders/index.md) response to inform TPPs when a token associated with a consent has expired. #### Updates to Get Account Transactions and Get Transaction Details responses for ASPSPs with Budapest API profiles {#updates-to-get-account-transactions-and-get-transaction-details-responses-for-aspsps-with-budapest-api-profiles} The following fields have been mapped to the [Get Account Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) and [Get Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) responses for ASPSPs supporting Budapest profile to include sender and receiver details: * `senderName` * `transactionType` ## Release 1.44.0 Sandbox and Pre-Production {#release-1440-sandbox-and-pre-production} Release 1.44.0 provides updates to the API functionality and Sandbox testing capabilities. Enhancements detailed here are applicable to both the Sandbox and Pre-Production environments unless stated otherwise. ### Release enhancements {#release-enhancements-11} #### Addition of Variable Recurring Payment processing capability {#addition-of-variable-recurring-payment-processing-capability-1} Variable Recurring Payment processing capability has been enabled to provide recurring funds movement within UK accounts using Open Banking (faster payment) without the need of user authentication (SCA at bank) for each payment. For details, refer to [Variable Recurring Payments](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/variable-recurring-payments/index.md). Details for each available VRP endpoint are available here: * [Domestic VRP Consent Initiation](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/domestic-vrp-consent-initiation-request/index.md) * [Initiate Single Immediate VRP Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/initiate-single-immediate-domestic-vrp-payment-request/index.md) * [Get VRP Consent Details](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/get-vrp-consent-details-request/index.md) * [Get VRP Payment Details](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/get-vrp-payment-details-request/index.md) * [Exchange PSU Authorization for VRP Access Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/exchange-psu-authorization-for-vrp-access-consent-request/index.md) * [Delete VRP Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/domestic-vrp-consent-initiation-request/index.md) #### Response and error codes {#response-and-error-codes-3} * A dedicated INVALID_TOKEN 400 error response code has been added for the [Get Account Standing Orders](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-standing-orders/index.md) response to inform TPPs when a token associated with a consent has expired. #### Updates to Get Account Transactions and Get Transaction Details responses for ASPSPs with Budapest API profiles {#updates-to-get-account-transactions-and-get-transaction-details-responses-for-aspsps-with-budapest-api-profiles-1} The following fields have been mapped to the [Get Account Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) and [Get Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) responses for ASPSPs supporting Budapest profile to include sender and receiver details: * `senderName` * `transactionType` #### Sandbox data set updates {#sandbox-data-set-updates} A new test bank, Thallium, with Budapest API profile, has been added to the Sandbox data sets. This is for AIS only. Refer to OB_Connect_Sandbox_DataSets_R1-44-0.xlsx in [Specification Release Documentation](https://developer.mastercard.com/open-banking-connect/documentation/specification-release-documentation/index.md) for the current data set. ## Release 1.43.0 Production {#release-1430-production} Release 1.43.0 provides updates to the API functionality, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-12} #### Addition of originalTransactionId field for Get List of Transactions and Get Transaction Details responses {#addition-of-originaltransactionid-field-for-get-list-of-transactions-and-get-transaction-details-responses} The optional field `originalTransactionId` has been added to the [Get List of Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) and [Get Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) responses to enable transaction data to be matched on the ASPSP side. #### Addition of fieldsFormatInformation object for Get List of ASPSPs responses {#addition-of-fieldsformatinformation-object-for-get-list-of-aspsps-responses} The `fieldsFormatInformation` object has been added to the [AIS Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) and [PIS Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-list-of-aspsps/index.md) responses to enable a list of mandatory fields to be included in consent requests if required by the ASPSP. * `fieldsFormatInformation` - List of fields format restrictions required by an ASPSP. * `field` - A field from OBC API which has a restriction required by an ASPSP. * `constraint` - The field format required by an ASPSP. * `mandatoryFields` - List of fields that are required by an ASPSP. ## Release 1.43.0 Sandbox and Pre-Production {#release-1430-sandbox-and-pre-production} Release 1.43.0 provides updates to the API functionality and Sandbox testing capabilities. Enhancements detailed here are applicable to both the Sandbox and Pre-Production environments unless stated otherwise. ### Release enhancements {#release-enhancements-13} #### Addition of originalTransactionId field for Get List of Transactions and Get Transaction Details responses {#addition-of-originaltransactionid-field-for-get-list-of-transactions-and-get-transaction-details-responses-1} The optional field `originalTransactionId` has been added to the [Get List of Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) and [Get Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) responses to enable transaction data to be matched on the ASPSP side. #### Addition of fieldsFormatInformation object for Get List of ASPSPs responses {#addition-of-fieldsformatinformation-object-for-get-list-of-aspsps-responses-1} The `fieldsFormatInformation` object has been added to the [AIS Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) and [PIS Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-list-of-aspsps/index.md) responses to enable a list of mandatory fields to be included in consent requests if required by the ASPSP. * `fieldsFormatInformation` - List of fields format restrictions required by an ASPSP. * `field` - A field from OBC API which has a restriction required by an ASPSP. * `constraint` - The field format required by an ASPSP. * `mandatoryFields` - List of fields that are required by an ASPSP. #### Addition of support for bankTransactionCode in Get Transaction Details and Get Account Transactions responses for specific ASPSPs {#addition-of-support-for-banktransactioncode-in-get-transaction-details-and-get-account-transactions-responses-for-specific-aspsps} The AIS Get Account Transaction Details and Get Account Transactions responses have been enhanced to return the `bankTransactionCode` object for specific ASPSPs. * [Get Account Transaction Details response](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/#response-body) * [Get Account Transactions response](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/#response-body) ## Release 1.42.0 Production {#release-1420-production} Release 1.42.0 provides updates to the API functionality, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-14} #### Addition of bankTransactionCode object for Transactions Details responses {#addition-of-banktransactioncode-object-for-transactions-details-responses} The `bankTransactionCode` object has been added to the [Get Account Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) and [Get Account Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) responses to enable transactions to be identified by business area, domain within a family and sub-product family, or by proprietary transaction code and issuer. * `bankTransactionCode` - Set of elements to fully identify the type of underlying transaction resulting in an entry. * `domain` - Defines the business area of the underlying transaction, such as payments, securities, and so on. * `code` - Specifies the business area of the underlying transaction. * `familyCode` - Specifies the family within a domain. * `subFamilyCode` - Specifies the sub-product family within a specific family. * `proprietary` - Proprietary identification of the bank transaction code, as defined by the issuer. * `code` - Proprietary bank transaction code. * `issuer` - Identification of the issuer of the proprietary bank transaction code. #### Removal of credential fields for Unicredit ASPSP {#removal-of-credential-fields-for-unicredit-aspsp} The Hungarian ASPSP Unicredit no longer requires the `credential` fields. These need to be provided in the Account Information Consent request `accounts` object, as described in ASPSP variations. #### ASPSP variations updated for support of accountNumber.identification {#aspsp-variations-updated-for-support-of-accountnumberidentification} Updates have been made to include `accountNumber.identification` as a mandatory field for Account information consent requests to K\&H ASPSP. ## Release 1.42.0 Sandbox and Pre-Production {#release-1420-sandbox-and-pre-production} Release 1.42.0 provides updates to the API functionality and Sandbox testing capabilities. Enhancements detailed here are applicable to both the Sandbox and Pre-Production environments unless stated otherwise. ### Release enhancements {#release-enhancements-15} #### Addition of bankTransactionCode object for Transactions Details responses {#addition-of-banktransactioncode-object-for-transactions-details-responses-1} The `bankTransactionCode` object has been added to the [Get Account Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) and [Get Account Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) responses to enable transactions to be identified by business area, domain within a family and sub-product family, or by proprietary transaction code and issuer. * `bankTransactionCode` - Set of elements to fully identify the type of underlying transaction resulting in an entry. * `domain` - Defines the business area of the underlying transaction, such as payments, securities, and so on. * `code` - Specifies the business area of the underlying transaction. * `familyCode` - Specifies the family within a domain. * `subFamilyCode` - Specifies the sub-product family within a specific family. * `proprietary` - Proprietary identification of the bank transaction code, as defined by the issuer. * `code` - Proprietary bank transaction code. * `issuer` - Identification of the issuer of the proprietary bank transaction code. #### Sandbox Consent Request scenarios enhancements for requests without a State parameter {#sandbox-consent-request-scenarios-enhancements-for-requests-without-a-state-parameter} The [Sandbox scenarios](https://developer.mastercard.com/open-banking-connect/documentation/sandbox/sandbox-scenarios/index.md) Consent Requests have been enhanced to support Polish ASPSPs that do not return a `State` parameter in the SCA redirect URL. A successful response and SCA redirect URL without STATE parameter will be returned in response to sandbox scenarios, using a specific ASPSPID and RequestId, as detailed in the requests: * Payment Initiation Consent (Scenario #1) * Account Information Consent (Scenario #1) #### Removal of credential fields for Unicredit ASPSP {#removal-of-credential-fields-for-unicredit-aspsp-1} The Hungarian ASPSP Unicredit no longer requires the `credential` fields. These need to be provided in the Account Information Consent request `accounts` object, as described in ASPSP variations. #### ASPSP variations updated for support of accountNumber.identification {#aspsp-variations-updated-for-support-of-accountnumberidentification-1} Updates have been made to include `accountNumber.identification` as a mandatory field for Account information consent requests to K\&H ASPSP. ## Release 1.41.0 Production {#release-1410-production} Release 1.41.0 provides updates to the API functionality, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-16} #### Invalid authorization errors {#invalid-authorization-errors} Two 400 INVALID_AUTHORIZATION error codes have been introduced to indicate when the TPP has sent an authorization string to the ASPSP with an invalid or missing request id for these requests. * [AIS - Exchange the PSU Authorization for Access Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/exchange-psu-consent/index.md) * [PIS - Domestic Payment Initiation Transfer](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-credit-transfer-initiation-request/index.md) * [PIS - SEPA Payment Initiation Transfer](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-credit-transfer-initiation-request/index.md) * PIS - Cross Border Payment Initiation Transfer #### Endpoints support removed from Budapest API profile {#endpoints-support-removed-from-budapest-api-profile} Changes have been made to remove the Budapest API Profile from the AIS [Get Account Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-details/index.md) and [Get Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) endpoints. #### ASPSP Variations {#aspsp-variations} The [ASPSP Variations](https://developer.mastercard.com/open-banking-connect/documentation/aspsp-variations/index.md) directory has been updated to indicate AIS List of accounts support by Hungary ASPSPs. ## Release 1.41.0 Sandbox and Pre-Production {#release-1410-sandbox-and-pre-production} Release 1.41.0 provides updates to the API functionality and Sandbox testing capabilities. Enhancements detailed here are applicable to both the Sandbox and Pre-Production environments. ### Release enhancements {#release-enhancements-17} #### Invalid authorization errors {#invalid-authorization-errors-1} Two 400 INVALID_AUTHORIZATION error codes have been introduced to indicate when the TPP has sent an authorization string to the ASPSP with an invalid or missing request id for these requests. * [AIS - Exchange the PSU Authorization for Access Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/exchange-psu-consent/index.md) * [PIS - Domestic Payment Initiation Transfer](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-credit-transfer-initiation-request/index.md) * [PIS - SEPA Payment Initiation Transfer](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-credit-transfer-initiation-request/index.md) * PIS - Cross Border Payment Initiation Transfer #### Endpoints support removed from Budapest API profile {#endpoints-support-removed-from-budapest-api-profile-1} Changes have been made to remove the Budapest API Profile from the AIS [Get Account Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-details/index.md) and [Get Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) endpoints. #### ASPSP Variations {#aspsp-variations-1} The [ASPSP Variations](https://developer.mastercard.com/open-banking-connect/documentation/aspsp-variations/index.md) directory has been updated to indicate AIS List of accounts support by Hungary ASPSPs. ## Release 1.40.0 Production {#release-1400-production} Release 1.40.0 provides updates to the API functionality, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-18} #### TPP Branding for the PSU authorization screen {#tpp-branding-for-the-psu-authorization-screen} Updates have been made to enable branding to be included for the PSU authorization screen. This screen displays when credentials have not provided in the consent request to ASPSPs that expect credentials. Contact [openbankingeu_support@mastercard.com](mailto:openbankingeu_support@mastercard.com) to set up branding as required. #### PIS Enhancements {#pis-enhancements} ##### Updates to enable ASPSP credentials to be sent for PSU authorization in Consent requests {#updates-to-enable-aspsp-credentials-to-be-sent-for-psu-authorization-in-consent-requests} A new `credentials` field has been added to the Domestic and Cross-Border Payment Initiation Consent requests to enable TPPs to send ASPSPs credentials for PSU authorization. This removes the requirement for an intermediate pop-up screen requesting PSUs to enter credentials. #### API enhancements {#api-enhancements} ##### Updates to the Domestic and Cross-Border Payment Initiation Consent requests {#updates-to-the-domestic-and-cross-borderpayment-initiation-consent-requests} The `credentials` field has been added to the [Domestic Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-initiation-consent-request/index.md) and Cross-Border Payment Initiation Consent requests to enable TPPs to send ASPSPs credentials for PSU authorization. ## Release 1.40.0 Sandbox and Pre-Production {#release-1400-sandbox-and-pre-production} Release 1.40.0 provides updates to the API functionality and Sandbox testing capabilities. Enhancements detailed here are applicable to both the Sandbox and Pre-Production environments. ### Release enhancements {#release-enhancements-19} #### TPP Branding for the PSU authorization screen {#tpp-branding-for-the-psu-authorization-screen-1} Updates have been made to enable branding to be included for the PSU authorization screen. This screen displays when credentials have not provided in the consent request to ASPSPs that expect credentials. Contact [openbankingeu_support@mastercard.com](mailto:openbankingeu_support@mastercard.com) to set up branding as required. #### PIS Enhancements {#pis-enhancements-1} ##### Updates to enable ASPSP credentials to be sent for PSU authorization in Consent requests {#updates-to-enable-aspsp-credentials-to-be-sent-for-psu-authorization-in-consent-requests-1} A new `credentials` field has been added to the Domestic and Cross-Border Payment Initiation Consent requests to enable TPPs to send ASPSPs credentials for PSU authorization. This removes the requirement for an intermediate pop-up screen requesting PSUs to enter credentials. #### API enhancements {#api-enhancements-1} ##### Updates to the Domestic and Cross-Border Payment Initiation Consent requests {#updates-to-the-domestic-and-cross-borderpayment-initiation-consent-requests-1} The `credentials` field has been added to the [Domestic Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-initiation-consent-request/index.md) and Cross-Border Payment Initiation Consent requests to enable TPPs to send ASPSPs credentials for PSU authorization. ## Release 1.39.0 Production {#release-1390-production} Release 1.39.0 provides updates to the API functionality, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-20} #### AIS Enhancements {#ais-enhancements} ##### Updates to Get Account Transactions response for CMA9 ASPSPs {#updates-to-get-account-transactions-response-for-cma9-aspsps} The following fields have been mapped to the Get Account Transactions response for ASPSPs supporting CMA9 profile to include sender and receiver details: * `recipientAccountNumber` * `recipientName` * `recipientAccountNumberScheme` * `senderAccountNumber` * `senderName` * `senderAccountNumberScheme` #### API enhancements {#api-enhancements-2} None. ## Release 1.39.0 Sandbox and Pre-Production {#release-1390-sandbox-and-pre-production} Release 1.39.0 provides updates to the API functionality and Sandbox testing capabilities. Enhancements detailed here are applicable to both the Sandbox and Pre-Production environments. ### Release enhancements {#release-enhancements-21} #### AIS Enhancements {#ais-enhancements-1} ##### Updates to Get Account Transactions response for CMA9 ASPSPs {#updates-to-get-account-transactions-response-for-cma9-aspsps-1} The following fields have been mapped to the Get Account Transactions response for ASPSPs supporting CMA9 profile to include sender and receiver details: * `recipientAccountNumber` * `recipientName` * `recipientAccountNumberScheme` * `senderAccountNumber` * `senderName` * `senderAccountNumberScheme` #### ASPSP Variations {#aspsp-variations-2} The ASPSP Variations directory has been updated to include additional guidance for Revolut bank variations across markets. #### API enhancements {#api-enhancements-3} None. ## Release 1.38.2 Production {#release-1382-production} Release 1.38.2 provides enhancements to the API Specification, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-22} ##### Budapest Bank API profile {#budapest-bank-api-profile} A new Budapest Bank API profile has been introduced to support Budapest bank connectivity. #### API enhancements {#api-enhancements-4} ##### AIS enhancements {#ais-enhancements-2} The Budapest API profile has been added to the list of supported profiles in the `profile` field for the AIS [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) response. ## Release 1.38.2 Sandbox and Pre-Production {#release-1382-sandbox-and-pre-production} Release 1.38.2 provides enhancements to the API Specification and Sandbox testing capabilities. Enhancements detailed here are applicable to both the Sandbox and Pre-Production environments. ### Release enhancements {#release-enhancements-23} ##### Budapest Bank API profile {#budapest-bank-api-profile-1} A new Budapest Bank API profile has been introduced to support Budapest bank connectivity in Sandbox. #### API enhancements {#api-enhancements-5} ##### AIS enhancements {#ais-enhancements-3} The Budapest API profile has been added to the list of supported profiles in the `profile` field for the AIS [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) response. ## Release 1.38.1 Production {#release-1381-production} Release 1.38.1 provides enhancements to the API Specification, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-24} ##### PSU details included in requests to NextGenPSD2 and STET ASPSPs {#psu-details-included-in-requests-to-nextgenpsd2-and-stet-aspsps} Updates have been made in the following fields to provide confirmation to NextGenPSD2 Czech Open Banking Standard (Erste Bank Hungary for example), NextGenPSD2 Slovak Banking API Standard (OTP Bank Hungary for example), and STET ASPSPs that a request is coming from a PSU: * `isLivePsuRequest` - Field providing details to indicate if the PSU actively initiated the request. * `psuIPAddress` - Field containing the IP address of PSU's terminal device. This field becomes mandatory when `isLivePsuRequest` is set to "true". * `psuAgent` - Field containing the PSU's browser agent details. The existing PSU fields `isLivePsuRequest`, `psuIPAddress`, `psuAgent` have been mapped for NextGenPSD2 Czech Open Banking Standard (Erste Bank Hungary for example), NextGenPSD2 Slovak Banking API Standard (OTP Bank Hungary for example), and STET profiles, to provide confirmation that a request is coming from a PSU in the following requests: * AIS Account Information Consent * AIS Get List of Accounts * AIS Get Account Details * AIS Get Account Balances * AIS Get Account Transactions * AIS Get Transaction Details * AIS Exchange PSU Authorization for Access Consent * PIS Domestic Initiation Consent * PIS Domestic Credit Transfer * PIS Domestic Get Payment status * PIS SEPA Initiation Consent * PIS SEPA Credit Transfer * PIS SEPA Get Payment status ##### Response and error codes {#response-and-error-codes-4} Updates have been made to map errors due to ASPSP unavailability to a new 400 PROVIDER_ERROR general reason code. #### API enhancements {#api-enhancements-6} ##### PIS enhancements {#pis-enhancements-2} The Budapest API profile has been added to the list of supported profiles in the `profile` field for the PIS [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-list-of-aspsps/index.md) response. ##### Response and error codes {#response-and-error-codes-5} A 400 PROVIDER_ERROR general reason code has been introduced to map errors due to ASPSP unavailability. Refer to [Response and Error Codes](https://developer.mastercard.com/open-banking-connect/documentation/response-and-error-codes/index.md) for details. ## Release 1.38.1 Sandbox and Pre-Production {#release-1381-sandbox-and-pre-production} Release 1.38.1 provides enhancements to the API Specification and Sandbox testing capabilities. Enhancements detailed here are applicable to both the Sandbox and Pre-Production environments. ### Release enhancements {#release-enhancements-25} ##### PSU details included in requests to NextGenPSD2 and STET ASPSPs {#psu-details-included-in-requests-to-nextgenpsd2-and-stet-aspsps-1} Updates have been made in the following fields to provide confirmation to NextGenPSD2 Czech Open Banking Standard (Erste Bank Hungary for example), NextGenPSD2 Slovak Banking API Standard (OTP Bank Hungary for example), and STET ASPSPs that a request is coming from a PSU: * `isLivePsuRequest` - Field providing details to indicate if the PSU actively initiated the request. * `psuIPAddress` - Field containing the IP address of PSU's terminal device. This field becomes mandatory when `isLivePsuRequest` is set to "true". * `psuAgent` - Field containing the PSU's browser agent details. The existing PSU fields `isLivePsuRequest`, `psuIPAddress`, `psuAgent` have been mapped for NextGenPSD2 Czech Open Banking Standard (Erste Bank Hungary for example), NextGenPSD2 Slovak Banking API Standard (OTP Bank Hungary for example), and STET profiles, to provide confirmation that a request is coming from a PSU in the following requests: * AIS Account Information Consent * AIS Get List of Accounts * AIS Get Account Details * AIS Get Account Balances * AIS Get Account Transactions * AIS Get Transaction Details * AIS Exchange PSU Authorization for Access Consent * PIS Domestic Initiation Consent * PIS Domestic Credit Transfer * PIS Domestic Get Payment status * PIS SEPA Initiation Consent * PIS SEPA Credit Transfer * PIS SEPA Get Payment status ##### Response and error codes {#response-and-error-codes-6} Updates have been made to map errors due to ASPSP unavailability to a new 400 PROVIDER_ERROR general reason code. #### API enhancements {#api-enhancements-7} ##### PIS enhancements {#pis-enhancements-3} The Budapest API profile has been added to the list of supported profiles in the `profile` field for the PIS [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-list-of-aspsps/index.md) response. ##### Response and error codes {#response-and-error-codes-7} A 400 PROVIDER_ERROR general reason code has been introduced to map errors due to ASPSP unavailability. Refer to [Response and Error Codes](https://developer.mastercard.com/open-banking-connect/documentation/response-and-error-codes/index.md) for details. ##### ASPSP variations {#aspsp-variations-3} Updates have been made to include the `credentials.property` and `credentials.value` fields for SEPA payments, SEPA Instant payments, and AIS Account Information Consent requests for Hungary and Belgium. Refer to [ASPSP Variations](https://developer.mastercard.com/open-banking-connect/documentation/aspsp-variations/index.md) for details. ## Release 1.37.0 Production {#release-1370-production} Release 1.37.0 provides enhancements to the API Specification, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-26} ##### PSU details included in requests to CMA9 ASPSPs {#psu-details-included-in-requests-to-cma9-aspsps} Some CMA9 ASPSPs, MKB or Tokarek in Hungary for example, require confirmation that a request is coming from a PSU. Updates have been made to provide the required information in the following fields: * `isLivePsuRequest` - Field providing details to indicate if the PSU actively initiated the request. * `psuIPAddress` - Field containing the IP address of PSU's terminal device. This field becomes mandatory when `isLivePsuRequest` is set to "true". * `psuAgent` - Field containing the PSU's browser agent details. The existing PSU fields `isLivePsuRequest`, `psuIPAddress`, `psuAgent` have been mapped for CMA9 profile to provide confirmation that a request is coming from a PSU in the following requests: * AIS Account Information Consent * AIS Get List of Accounts * AIS Get Account Details * AIS Get Account Balances * AIS Get Account Transactions * AIS Get Transaction Details * AIS Exchange PSU Authorization for Access Consent * PIS Domestic Initiation Consent * PIS Domestic Credit Transfer * PIS Domestic Get Payment status The PSU fields `isLivePsuRequest`, `psuIPAddress`, `psuAgent` have been added and mapped for CMA9 profile to provide confirmation that a request is coming from a PSU in the following requests: * AIS Get Account Standing Orders * AIS Get Raw Consent * PIS Get Raw Consent * PIS Cross-border Payment Credit Transfer * PIS Cross-border Payment Initiation Consent * PIS Cross-border Payment Status ##### Response and error codes {#response-and-error-codes-8} A 400 FORMAT_ERROR code has been introduced for the following requests to indicate when the parameter `isLivePsuRequest`=true and the `psuIPAddress` field has been omitted: * AIS Get Raw Consent * AIS Get Account Standing Orders * PIS Get Raw Consent * PIS Cross-border Payment Initiation Consent * PIS Cross-border Payment Credit Transfer * PIS Cross-border Payment Status #### API enhancements {#api-enhancements-8} ##### AIS enhancements {#ais-enhancements-4} The following requests have been updated to include the PSU fields `isLivePsuRequest`, `psuIPAddress`, `psuAgent`: * [Get Account Standing Orders](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-standing-orders/index.md) * [Get Raw Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-raw-consent/index.md) A 400 FORMAT_ERROR code has been introduced for the following requests to indicate when the parameter `isLivePsuRequest`=true and the `psuIPAddress` field has been omitted: * [Get Raw Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-raw-consent/index.md) * [Get Account Standing Orders](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-standing-orders/index.md) ##### PIS enhancements {#pis-enhancements-4} The following requests have have been updated to include the PSU fields `isLivePsuRequest`, `psuIPAddress`, `psuAgent`: * [PIS Get Raw Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-raw-consent/index.md) * PIS Cross-border Payment Credit Transfer * PIS Cross-border Payment Initiation Consent * PIS Cross-border Payment Status\] A 400 FORMAT_ERROR code has been introduced for the following requests to indicate when the parameter `isLivePsuRequest`=true and the `psuIPAddress` field has been omitted: * [Get Raw Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-raw-consent/index.md) * Cross-border Payment Initiation Consent * Cross-border Payment Credit Transfer * Cross-border Payment Status ## Release 1.37.0 Sandbox and Pre-Production {#release-1370-sandbox-and-pre-production} Release 1.37.0 provides enhancements to the API Specification and Sandbox testing capabilities. Enhancements detailed here are applicable to both the Sandbox and Pre-Production environments. ### Release enhancements {#release-enhancements-27} ##### PSU details included in requests to CMA9 ASPSPs {#psu-details-included-in-requests-to-cma9-aspsps-1} Some CMA9 ASPSPs, MKB or Tokarek in Hungary for example, require confirmation that a request is coming from a PSU. Updates have been made to provide the required information in the following fields: * `isLivePsuRequest` - Field providing details to indicate if the PSU actively initiated the request. * `psuIPAddress` - Field containing the IP address of PSU's terminal device. This field becomes mandatory when `isLivePsuRequest` is set to "true". * `psuAgent` - Field containing the PSU's browser agent details. The existing PSU fields `isLivePsuRequest`, `psuIPAddress`, `psuAgent` have been mapped for CMA9 profile to provide confirmation that a request is coming from a PSU in the following requests: * AIS Account Information Consent * AIS Get List of Accounts * AIS Get Account Details * AIS Get Account Balances * AIS Get Account Transactions * AIS Get Transaction Details * AIS Exchange PSU Authorization for Access Consent * PIS Domestic Initiation Consent * PIS Domestic Credit Transfer * PIS Domestic Get Payment status The PSU fields `isLivePsuRequest`, `psuIPAddress`, `psuAgent` have been added and mapped for CMA9 profile to provide confirmation that a request is coming from a PSU in the following requests: * AIS Get Account Standing Orders * AIS Get Raw Consent * PIS Get Raw Consent * PIS Cross-border Payment Credit Transfer * PIS Cross-border Payment Initiation Consent * PIS Cross-border Payment Status ##### Response and error codes {#response-and-error-codes-9} A 400 FORMAT_ERROR code has been introduced for the following requests to indicate when the parameter `isLivePsuRequest`=true and the `psuIPAddress` field has been omitted: * AIS Get Raw Consent * AIS Get Account Standing Orders * PIS Get Raw Consent * PIS Cross-border Payment Initiation Consent * PIS Cross-border Payment Credit Transfer * PIS Cross-border Payment Status #### API enhancements {#api-enhancements-9} ##### AIS enhancements {#ais-enhancements-5} The following requests have been updated to include the PSU fields `isLivePsuRequest`, `psuIPAddress`, `psuAgent`: * [Get Account Standing Orders](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-standing-orders/index.md) * [Get Raw Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-raw-consent/index.md) A 400 FORMAT_ERROR code has been introduced for the following requests to indicate when the parameter `isLivePsuRequest`=true and the `psuIPAddress` field has been omitted: * [Get Raw Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-raw-consent/index.md) * [Get Account Standing Orders](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-standing-orders/index.md) ##### PIS enhancements {#pis-enhancements-5} The following requests have have been updated to include the PSU fields `isLivePsuRequest`, `psuIPAddress`, `psuAgent`: * [PIS Get Raw Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-raw-consent/index.md) * PIS Cross-border Payment Credit Transfer * PIS Cross-border Payment Initiation Consent * PIS Cross-border Payment Status A 400 FORMAT_ERROR code has been introduced for the following requests to indicate when the parameter `isLivePsuRequest`=true and the `psuIPAddress` field has been omitted: * [Get Raw Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-raw-consent/index.md) * Cross-border Payment Initiation Consent * Cross-border Payment Credit Transfer * Cross-border Payment Status ## Release 1.36.0 Production and Pre-Production {#release-1360-production-and-pre-production} Release 1.36.0 provides enhancements to the API Specification, including scheduled changes and improvements. Enhancements detailed here are applicable to both the Production and Pre-Production environments. ### Release enhancements {#release-enhancements-28} ##### Mandatory fields for Embedded flow authentication {#mandatory-fields-for-embedded-flow-authentication} Some ASPSPs that support Embedded flow, Hungary for example, require TPPs to provide additional PSU authentication details in the Get Account Information Consent request. The following information has been added the Get Account Information Consent request to support PSU authentication: * `accounts` - Object containing a list of accounts. * `accountsReference` - Object containing details of the specific account. * `accountNumber` - Object containing a set of elements used to define the account details. * `SchemeName` - Field containing the account scheme name (only 'IBAN' currently supported.) * `Identification` -- Field containing account identification which can be used on payload-level to address specific accounts. * `Currency` -- Field containing 3 character currency code as required in ISO 4217. #### API enhancements {#api-enhancements-10} ##### AIS enhancements {#ais-enhancements-6} The [Get Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/account-information-consent/index.md) request has been updated as detailed above to support PSU authentication. ## Release 1.36.0 Sandbox {#release-1360-sandbox} Release 1.36.0 provides enhancements to the API Specification and Sandbox testing capabilities. ### Release enhancements {#release-enhancements-29} ##### Sandbox scenarios refund enhancements {#sandbox-scenarios-refund-enhancements} * Additional success [Sandbox scenarios](https://developer.mastercard.com/open-banking-connect/documentation/sandbox/sandbox-scenarios/index.md) have been added to return SEPA Refund Account details, `refundAccount` object with `iban` and `name`, in response to the following requests: * SEPA Payment Credit Transfer Initiation (Scenario #11) * SEPA Get Payment Status (Scenario #12) * Additional failure [Sandbox scenarios](https://developer.mastercard.com/open-banking-connect/documentation/sandbox/sandbox-scenarios/index.md) have been added, indicating "REFUND_CAPABILITY_DISABLED", for instances when a TPP that is not registered for Payment Refunds provides the returnRefundAccount flag in response to the following requests: * Domestic Payment Initiation Consent (Scenario #23) * SEPA Payment Initiation Consent (Scenario #19) * Cross-Border Payment Initiation Consent (Scenario #16) ##### Mandatory fields for Embedded flow authentication {#mandatory-fields-for-embedded-flow-authentication-1} Some ASPSPs that support Embedded flow, Hungary for example, require TPPs to provide additional PSU authentication details in the Get Account Information Consent request. The following information has been added the Get Account Information Consent request to support PSU authentication: * `accounts` - Object containing a list of accounts. * `accountsReference` - Object containing details of the specific account. * `accountNumber` - Object containing a set of elements used to define the account details. * `SchemeName` - Field containing the account scheme name (only 'IBAN' currently supported.) * `Identification` -- Field containing account identification which can be used on payload-level to address specific accounts. * `Currency` -- Field containing 3 character currency code as required in ISO 4217. #### API enhancements {#api-enhancements-11} ##### AIS enhancements {#ais-enhancements-7} The [Get Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/account-information-consent/index.md) request has been updated as detailed above to support PSU authentication. ## Release 1.35.0 Production and Pre-Production {#release-1350-production-and-pre-production} Release 1.35.0 provides enhancements to the API Specification, including scheduled changes and improvements. Enhancements detailed here are applicable to both the Production and Pre-Production environments. ### Release enhancements {#release-enhancements-30} ##### Updates to include refund capability for SEPA payment requests {#updates-to-include-refund-capability-for-sepa-payment-requests} Note: Support for SEPA Payment Refunds is currently in development. This service requires advance registration. To use SEPA Payment Refunds, contact your Mastercard customer contact. Payment Refunds will be facilitated by leveraging the existing SEPA Payment Initiation requests and responses that will include new parameters as detailed below. * A new `RETURN_REFUND_ACCOUNT` flag parameter is available for SEPA Payment Initiation Consent requests to be included when the PSU has provided consent to the TPP to receive and store debtor account details, which can be used to complete a payment refund. * A new `refundAccount` object containing the refund account `iban` and `name` fields has been added to the SEPA Payment Credit Transfer Initiation and SEPA Get Payment Status responses. This object is only available when the TPP has provided the `RETURN_REFUND_ACCOUNT` flag in the SEPA Payment Initiation Consent request. * A new error message `Refund capability not enabled for TPP` has been implemented to return when a TPP that is not registered for SEPA Payment Refunds provides the RETURN_REFUND_ACCOUNT flag in the Consent request. ##### Refund account name for Domestic and Cross-Border Payment Credit Transfer and Get Payment Status responses {#refund-account-name-for-domestic-and-cross-borderpayment-credit-transfer-and-get-payment-status-responses} The `name` field has been added to the `refundAccount` object in Domestic and Cross-Border Payment Credit Transfer and Get Payment Status responses. It contains the name of the debtor account owner, to be used in the `creditorName` field for refund payments. ##### Error update for consentId value {#error-update-for-consentid-value} Updates have been made to include a new error message when the consentID provided in the request is invalid or not found. * Reason Code: INVALID_TOKEN * Description: "Access Token associated with the Request is invalid or has been revoked" ##### Account Information Service tutorial updates {#account-information-service-tutorial-updates} The [Account Information Service tutorial](https://developer.mastercard.com/open-banking-connect/tutorial/consent-ais/step2/index.md) has been updated with details and examples that match the current business rules in the Open Banking Connect API. #### API enhancements {#api-enhancements-12} ##### AIS enhancements {#ais-enhancements-8} * Updates have been made to the following requests to return specific error messages for failures that occur due to an invalid consentId value: * [Get Raw Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-raw-consent/index.md) * [Get List of Accounts](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-list-accounts/index.md) * [Get Account Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-details/index.md) * [Get Account Balances](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-balances/index.md) * [Get Account Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) * [Get Account Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) ##### PIS enhancements {#pis-enhancements-6} * The`RETURN_REFUND_ACCOUNT` flag has been added to the [SEPA Payment Initiation Consent request](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-initiation-consent-request/index.md). * A new `refundAccount` object containing the refund account details has been added to the SEPA [Payment Credit Transfer Initiation](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-credit-transfer-initiation-request/index.md) and SEPA [Get Payment Status request](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-get-payment-status-request/index.md) responses. * The `name` field has been added to the `refundAccount` object in the following Domestic and Cross-Border Payment Credit Transfer and Get Payment Status responses: * [Domestic Payment Credit Transfer Initiation](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-credit-transfer-initiation-request/index.md) * [Domestic Get Payment Status](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/get-payment-status-request/index.md) * Cross-border Payment Credit Transfer Initiation * Cross-border Get Payment Status * Updates have been made to the following requests to return specific error messages for requests that fail due to an invalid consentId value: * [Get Raw Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-raw-consent/index.md) * [Get Domestic Payment Status](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/get-payment-status-request/index.md) * [Get SEPA Payment Status](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-get-payment-status-request/index.md) * Get Cross-border Payment Status ## Release 1.35.0 Sandbox {#release-1350-sandbox} Release 1.35.0 provides enhancements to the API Specification and Sandbox testing capabilities. ### Release enhancements {#release-enhancements-31} ##### Error update for consentId value {#error-update-for-consentid-value-1} Updates have been made to include a new error message when the consentID provided in the request is invalid or not found. * Reason Code: INVALID_TOKEN * Description: "Access Token associated with the Request is invalid or has been revoked" ##### AIS tutorial updates {#ais-tutorial-updates} The [Account Information Service tutorial](https://developer.mastercard.com/open-banking-connect/tutorial/consent-ais/step2/index.md) has been updated with details and examples that match the current business rules in the Open Banking Connect API. #### API enhancements {#api-enhancements-13} ##### AIS enhancements {#ais-enhancements-9} Updates have been made to the following [Account Information Service scenarios scenarios](https://developer.mastercard.com/open-banking-connect/documentation/sandbox/sandbox-scenarios/index.md) to return specific error messages for failures that occur due to an invalid consentId value: * Get Raw Consent * Get List of Accounts * Get Account Details * Get Account Balances * Get Account Standing Orders * Get Account Transactions * Get Account Transaction Details ##### PIS enhancements {#pis-enhancements-7} Updates have been made to the following [Payment Initiation Service scenarios](https://developer.mastercard.com/open-banking-connect/documentation/sandbox/sandbox-scenarios/index.md) to return specific error messages for requests that fail due to an invalid consentId value: * Get Raw Consent Request * Get Domestic Payment Status request * Get SEPA Payment Status request * Get Cross-border Payment Status request ## Release 1.33.0 Production {#release-1330-production} Release 1.33.0 provides enhancements to the API Specification, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-32} ##### Error translation update for invalid consentId value {#error-translation-update-for-invalid-consentid-value} Updates have been made to translate all errors resulting from an invalid consentId value to a 400 response code with the message "Access Token associated with the Request is invalid". ##### Error translation update for disabled refund capability {#error-translation-update-for-disabled-refund-capability} A 400 REFUND_CAPABILITY_DISABLED error message is now displayed when refund capability has not been enabled for the TPP and a Domestic or Cross-Border Payment Initiation Consent request is submitted with the `RETURN_REFUND_ACCOUNT` flag set. Previously, a Provider Error message was returned. ##### Error code Source field update {#error-code-source-field-update} Updates have been made to display the application name 'OBC' as the Source field value for errors. Previously, the package name was displayed. ##### Credential fields update for ASPSPs that support embedded flow {#credential-fields-update-for-aspsps-that-support-embedded-flow} ASPSPs that support embedded flow may require PSU's to provide credentials for authorization. The following updates have been made to provide credential information to ASPSPs: * The `credentials` object has been added to the AIS Account Information Consent and SEPA Payment Initiation Consent requests to enable inclusion of PSU credentials for ASPSPs that support embedded flow. * The `credentials` parameter has been added to the `returnAdditionalData` field for AIS and PIS Get List of ASPSPs requests. This parameter is optional. When this parameter is presented in the request, the `credentialFields` object is included in Get List of ASPSPs responses. This provides the list of credential fields required for authorization through embedded flow. * The `credentialFields` object has been added to the AIS and PIS Get List of ASPSPs responses to provide the list of credential fields required for authorization through embedded flow. ##### SEPA Payment Initiation Consent request's creditorAgent object and creditorAgent.bicfi field updated to Optional {#sepa-payment-initiation-consent-requests-creditoragent-object-and-creditoragentbicfi-field-updated-to-optional} The conditionality of the `creditorAgent` object and `bicfi` field in the SEPA Payment Initiation Consent request have been updated from Mandatory to Optional, as not all ASPSPs require these details. #### API enhancements {#api-enhancements-14} ##### AIS enhancements {#ais-enhancements-10} * The Source field value for errors has been changed to display the application name 'OBC' throughout. * The `credentials` object has been added to the AIS [Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/account-information-consent/index.md) request to enable inclusion of PSU credentials for ASPSPs that support embedded flow. * The `credentials` parameter has been added to the `returnAdditionalData` field for the AIS [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) request. * The `credentialFields` object has been added to the AIS [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) response to provide the list of credential fields required for authorization through embedded flow. ##### PIS enhancements {#pis-enhancements-8} * The Source field value for errors has been changed to display the application name 'OBC' throughout. * The conditionality of the `creditorAgent` object and `bicfi` field in the [SEPA Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-initiation-consent-request/index.md) request have been updated from Mandatory to Optional. * The `credentials` object has been added to the [SEPA Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-initiation-consent-request/index.md) request to enable inclusion of PSU credentials for ASPSPs that support embedded flow. * The `credentials` parameter has been added to the `returnAdditionalData` field for the PIS [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-list-of-aspsps/index.md) request. * The `credentialFields` object has been added to the PIS [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-list-of-aspsps/index.md) response to provide the list of credential fields required for authorization through embedded flow. * The [Domestic Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-initiation-consent-request/index.md) and Cross-border Payment Initiation Consent requests have been updated to include an additional 400 REFUND_CAPABILITY_DISABLED error code to indicate when the the `RETURN_REFUND_ACCOUNT` is flag set and refund capability has not been enabled for the TPP requesting refund account details. ## Release 1.33.0 Sandbox and Pre-Production {#release-1330-sandbox-and-pre-production} Release 1.33.0 provides enhancements to the API Specification, Sandbox testing capabilities and Pre-Production environment. Enhancements detailed here are applicable to both the Sandbox and Pre-Production environments. ### Release enhancements {#release-enhancements-33} ##### Error translation update for invalid consentId value {#error-translation-update-for-invalid-consentid-value-1} Updates have been made to translate all errors resulting from an invalid consentId value to a 400 response code with the message "Access Token associated with the Request is invalid". ##### Error translation update for disabled refund capability {#error-translation-update-for-disabled-refund-capability-1} A 400 REFUND_CAPABILITY_DISABLED error message is now displayed when refund capability has not been enabled for the TPP and a Domestic or Cross-Border Payment Initiation Consent request is submitted with the `RETURN_REFUND_ACCOUNT` flag set. Previously, a Provider Error message was returned. ##### Error code Source field update {#error-code-source-field-update-1} Updates have been made to display the application name 'OBC' as the Source field value for errors. Previously, the package name was displayed. ##### Credential fields update for ASPSPs that support embedded flow {#credential-fields-update-for-aspsps-that-support-embedded-flow-1} ASPSPs that support embedded flow may require PSU's to provide credentials for authorization. The following updates have been made to provide credential information to ASPSPs: * The `credentials` object has been added to the AIS Account Information Consent and SEPA Payment Initiation Consent requests to enable inclusion of PSU credentials for ASPSPs that support embedded flow. * The `credentials` parameter has been added to the `returnAdditionalData` field for AIS and PIS Get List of ASPSPs requests. This parameter is optional. When this parameter is presented in the request, the `credentialFields` object is included in Get List of ASPSPs responses. This provides the list of credential fields required for authorization through embedded flow. * The `credentialFields` object has been added to the AIS and PIS Get List of ASPSPs responses to provide the list of credential fields required for authorization through embedded flow. ##### SEPA Payment Initiation Consent request's creditorAgent object and creditorAgent.bicfi field updated to Optional {#sepa-payment-initiation-consent-requests-creditoragent-object-and-creditoragentbicfi-field-updated-to-optional-1} The conditionality of the `creditorAgent` object and `bicfi` field in the SEPA Payment Initiation Consent request have been updated from Mandatory to Optional, as not all ASPSPs require these details. #### API enhancements {#api-enhancements-15} ##### AIS enhancements {#ais-enhancements-11} * The Source field value for errors has been changed to display the application name 'OBC' throughout. * The `credentials` object has been added to the AIS [Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/account-information-consent/index.md) request to enable inclusion of PSU credentials for ASPSPs that support embedded flow. * The `credentials` parameter has been added to the `returnAdditionalData` field for the AIS [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) request. * The `credentialFields` object has been added to the AIS [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) response to provide the list of credential fields required for authorization through embedded flow. ##### PIS enhancements {#pis-enhancements-9} * The Source field value for errors has been changed to display the application name 'OBC' throughout. * The conditionality of the `creditorAgent` object and `bicfi` field in the [SEPA Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-initiation-consent-request/index.md) request have been updated from Mandatory to Optional. * The `credentials` object has been added to the [SEPA Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-initiation-consent-request/index.md) request to enable inclusion of PSU credentials for ASPSPs that support embedded flow. * The `credentials` parameter has been added to the `returnAdditionalData` field for the PIS [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-list-of-aspsps/index.md) request. * The `credentialFields` object has been added to the PIS [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-list-of-aspsps/index.md) response to provide the list of credential fields required for authorization through embedded flow. * The [Domestic Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-initiation-consent-request/index.md) and Cross-border Payment Initiation Consent requests have been updated to include an additional 400 REFUND_CAPABILITY_DISABLED error code to indicate when the the `RETURN_REFUND_ACCOUNT` is flag set and refund capability has not been enabled for the TPP requesting refund account details. ### Sandbox scenarios {#sandbox-scenarios} No changes. ## Release 1.32.0 Production {#release-1320-production} Release 1.32.0 provides enhancements to the API Specification, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-34} ##### Error translation {#error-translation} Open Banking Connect has been updated to return a 400 error response when an ASPSP is unavailable. Previously, a 500 error code was returned. ##### YAML updates {#yaml-updates} The YAML files have been updated to reflect examples provided within Mastercard Developers. #### API enhancements {#api-enhancements-16} #### AIS enhancements {#ais-enhancements-12} ##### Supported values updated for the schemeName field {#supported-values-updated-for-the-schemename-field} The list of supported values for the `schemeName` field has been updated to include PAN for the Get List of Accounts and Get Account Details responses. #### PIS enhancements {#pis-enhancements-10} The data type for `transactionStatus` has been updated from Enum to String for all payment types in the following endpoints: * Payment Credit Transfer response * Get Payment Status response ## Release 1.32.0 Sandbox {#release-1320-sandbox} Release 1.32.0 provides enhancements to the API Specification and Sandbox testing capabilities. ### Release enhancements {#release-enhancements-35} ##### ASPSP Variations {#aspsp-variations-4} An ASPSP Variations directory is now available to provide information on the different capabilities, fields supported, and standards followed by different ASPSPs. Refer to [ASPSP Variations](https://developer.mastercard.com/open-banking-connect/documentation/aspsp-variations/index.md) for details. The following information is included: * Use Cases supported by ASPSPs within a specific market. * API Standards used by ASPSPs for a specific market. * Optional fields by ASPSP for a specific use case. ##### Simplified ASPSPs Sandbox registration {#simplified-aspsps-sandbox-registration} Updates have been made to enable TPPs to test with ASPSP's sandboxes without having to register their Redirect URL with that ASPSP. ##### Error translation {#error-translation-1} Open Banking Connect has been updated to return a 400 error response when an ASPSP is unavailable. Previously, a 500 error code was returned. ##### YAML updates {#yaml-updates-1} The YAML files have been updated to reflect examples provided within Mastercard Developers. ##### Sandbox data set updates {#sandbox-data-set-updates-1} A new test bank, Cadmium, has been added to the Sandbox data sets to support ten new accounts where IBAN is the account type. Refer to OB_Connect_Sandbox_DataSets_R1-32-0.xlsx in [Specification Release Documentation](https://developer.mastercard.com/open-banking-connect/documentation/specification-release-documentation/index.md) for the current data set. #### API enhancements {#api-enhancements-17} ##### AIS enhancements {#ais-enhancements-13} No changes. ##### PIS enhancements {#pis-enhancements-11} The data type for `transactionStatus` has been updated from Enum to String for all payment types in the following endpoints: * Payment Credit Transfer response * Get Payment Status response ### Sandbox scenarios {#sandbox-scenarios-1} No changes. ## Release 1.31.0 Production {#release-1310-production} Release 1.31.0 provides enhancements to the API Specification, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-36} #### AIS enhancements {#ais-enhancements-14} ##### Supported values updated for the accountType field {#supported-values-updated-for-the-accounttype-field} The list of supported values for the `accountType` field has been updated to include CARD for the Get List of Accounts and Get Account Details responses. ##### PAN value updated for senderAccountNumberScheme and recipientAccountNumberScheme fields {#pan-value-updated-for-senderaccountnumberscheme-and-recipientaccountnumberscheme-fields} PAN value has been updated to uppercase in the list of supported values for `senderAccountNumberScheme` and `recipientAccountNumberScheme` fields for the Get Account Transactions and Get Account Transaction Details responses. ##### Error message updated for TPPs sending validUntilDateTime field in the AIS consent request to ASPSPs {#error-message-updated-for-tpps-sending-validuntildatetime-field-in-the-ais-consent-request-to-aspsps} TPPs will receive a specific error message when sending `validUntilDateTime` in the AIS consent request to ASPSPs with STET API profile. This way TPPs will know that `validUntilDateTime` is what triggered the error message. ### API enhancements {#api-enhancements-18} #### AIS enhancements {#ais-enhancements-15} * The list of supported values for the `accountType` field has been updated to include CARD for the Get List of Accounts and Get Account Details responses. Refer to [Get List of Accounts](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-list-accounts/index.md) and [Get Account Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-details/index.md) for details. * PAN value has been updated to uppercase in the list of supported values for `senderAccountNumberScheme` and `recipientAccountNumberScheme` fields for the Get Account Transactions and Get Account Transaction Details responses. Refer to [Get Account Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) and [Get Account Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md). #### PIS enhancements {#pis-enhancements-12} No changes. ## Release 1.31.0 Sandbox {#release-1310-sandbox} Release 1.31.0 provides enhancements to the API Specification and Sandbox testing capabilities. ### Release enhancements {#release-enhancements-37} #### AIS enhancements {#ais-enhancements-16} ##### Supported values updated for the accountType field {#supported-values-updated-for-the-accounttype-field-1} The list of supported values for the `accountType` field has been updated to include CARD for the Get List of Accounts and Get Account Details responses. ##### Supported values updated for the schemeName field {#supported-values-updated-for-the-schemename-field-1} The list of supported values for the `schemeName` field has been updated to include PAN for the Get List of Accounts and Get Account Details responses. ##### PAN value updated for senderAccountNumberScheme and recipientAccountNumberScheme fields {#pan-value-updated-for-senderaccountnumberscheme-and-recipientaccountnumberscheme-fields-1} PAN value has been updated to uppercase in the list of supported values for `senderAccountNumberScheme` and `recipientAccountNumberScheme` fields for the Get Account Transactions and Get Account Transaction Details responses. ##### Error message updated for TPPs sending validUntilDateTime field in the AIS consent request to ASPSPs {#error-message-updated-for-tpps-sending-validuntildatetime-field-in-the-ais-consent-request-to-aspsps-1} TPPs will receive a specific error message when sending `validUntilDateTime` in the AIS consent request to ASPSPs with STET API profile. This way TPPs will know that `validUntilDateTime` is what triggered the error message. #### Sandbox Scenarios {#sandbox-scenarios-2} ##### Testing Scenarios responses updated for SEPA amount based payments {#testing-scenarios-responses-updated-for-sepa-amount-based-payments} Responses for negative test scenarios have been updated to provide the expected error codes as defined in documented test scenarios. ##### Updated response for Get Payment Status scenarios for CMA9 ASPSPs {#updated-response-for-get-payment-status-scenarios-for-cma9-aspsps} Some Get Payment Status scenarios for CMA9 ASPSPs have been updated to return an error when a valid `consentID` and an invalid, non-existent or unrelated `paymentId` are included in the message. ### API enhancements {#api-enhancements-19} #### AIS enhancements {#ais-enhancements-17} * The list of supported values for the `accountType` field has been updated to include CARD for the Get List of Accounts and Get Account Details responses. Refer to [Get List of Accounts](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-list-accounts/index.md) and [Get Account Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-details/index.md) for details. * The list of supported values for the `schemeName` field has been updated to include PAN for the Get List of Accounts and Get Account Details responses. Refer to [Get List of Accounts](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-list-accounts/index.md) and [Get Account Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-details/index.md) for details. * PAN value has been updated to uppercase in the list of supported values for `senderAccountNumberScheme` and `recipientAccountNumberScheme` fields for the Get Account Transactions and Get Account Transaction Details responses. Refer to [Get Account Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) and [Get Account Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md). #### PIS enhancements {#pis-enhancements-13} No changes. ### Sandbox data sets spreadsheets {#sandbox-data-sets-spreadsheets} No changes. ## Release 1.30.0 Production {#release-1300-production} Release 1.30.0 provides enhancements to the API Specification, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-38} #### AIS enhancements {#ais-enhancements-18} ##### Data Type updated to String for the schemeName field {#data-type-updated-to-string-for-the-schemename-field} The Data Type for the `schemeName` field has been updated from Enum to String for the Get List of Accounts and Get Account Details responses. ##### country field updated to be optionally returned in the Get Account Details response {#country-field-updated-to-be-optionally-returned-in-the-get-account-details-response} The conditionality of the `country` field (`holderAddress` object) in the Get Account Details response has been updated to be optionally returned for all API Profiles. ##### aspsps object updated to Mandatory for the Get List of ASPSPs response {#aspsps-object-updated-to-mandatory-for-the-get-list-of-aspsps-response} The conditionality of the `aspsps` object in the Get List of ASPSPs response has been updated from Optional to Mandatory, as it is always returned to TPPs. ##### Filtering transactions by date for the Get Account Transaction request {#filtering-transactions-by-date-for-the-get-account-transaction-request} Updates have been made to enable TPPs to filter transactions by date using the `bookingDateFrom` and `bookingDateTo` fields when sending requests to ASPSPs with NextGenPSD2 and STET API profiles. ##### Customization enabled for the consent validity period {#customization-enabled-for-the-consent-validity-period} A new `validUntilDateTime`field has been added to the Account Information Consent request to enable TPPs to customize the consent expiration date and time. TPPs can access the AIS data until the expiration expires. This field is applicable for Polish API, CMA9, NextGenPSD2 and STET API Profiles. #### PIS enhancements {#pis-enhancements-14} ##### aspsps object updated to Mandatory for the Get List of ASPSPs response {#aspsps-object-updated-to-mandatory-for-the-get-list-of-aspsps-response-1} The conditionality of the `aspsps` object in the Get List of ASPSPs response has been updated from Optional to Mandatory, as it is always returned to TPPs. ##### CMA9 Payment Initiation Consent updates for debtor account details {#cma9-payment-initiation-consent-updates-for-debtor-account-details} * A new `RETURN_REFUND_ACCOUNT` flag is available for TPP's to provide in Cross-border and Domestic Payment Initiation Consent requests. It should be included when the PSU has provided consent to the TPP to receive and store debtor account details, which can be used to complete a reverse payment. When the `RETURN_REFUND_ACCOUNT` flag is provided in the consent request, TPPs will receive `returnRefundAccount = 'True'` in the consent response. * A new `returnRefundAccount` field is available in responses to specify consent provided by the PSU to TPP to share debtor account details. This information flags to the TPP that debtor account details will be available from the ASPSP in response to subsequent calls to Credit transfer and Payment status endpoints. ##### CMA9 Payment Initiation Credit Transfer response updated to include debtor account details {#cma9-payment-initiation-credit-transfer-response-updated-to-include-debtor-account-details} The following parameters can be provided to the TPP when the TPP originally provided the `RETURN_REFUND_ACCOUNT` flag in a Cross-border or Domestic Payment Initiation Consent Request. The TPP can use this data to submit a reversal of the original payment on behalf of the PSU. * `refundAccount` - Object containing the refund account details (scheme name, account identification number) * `refundAgent` - Object containing the refund agent details (clearing system identification, member identification) ##### CMA9 Get Payment Status response updated to include debtor account details {#cma9-get-payment-status-response-updated-to-include-debtor-account-details} The following parameters can be provided to the TPP when the TPP originally provided the `RETURN_REFUND_ACCOUNT` flag in a Cross-border or Domestic Payment Initiation Consent Request. The TPP can use this data to submit a reversal of the original payment on behalf of the PSU. * `refundAccount` - Object containing the refund account details (scheme name, account identification number) * `refundAgent` - Object containing the refund agent details (clearing system identification, member identification) ### API enhancements {#api-enhancements-20} #### AIS enhancements {#ais-enhancements-19} * The Data Type for the `schemeName` field has been updated from Enum to String for the Get List of Accounts and Get Account Details responses. Refer to [Get List of Accounts](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-list-accounts/index.md) and [Get Account Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-details/index.md)for details. * The conditionality of the `aspsps` object in the Get List of ASPSPs response has been updated from Optional to Mandatory. Refer to [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) for details. The conditionality of the `country` field (`holderAddress` object) in the Get Account Details response has been updated to Optional for all API Profiles. Refer to [Get Account Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-details/index.md) for details. * TPPs can now filter transactions by date using the `bookingDateFrom` and `bookingDateTo` fields when sending requests to ASPSPs with NextGenPSD2 and STET API profiles. Refer to [Get Account Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) for details. * The `validUntilDateTime`field has been added to the Account Information Consent request to enable TPPs to customize the consent expiration date and time. Refer to [Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/account-information-consent/index.md) for details. #### PIS enhancements {#pis-enhancements-15} * The Domestic Payment Initiation Consent request and responses has been updated to include support for the `RETURN_REFUND_ACCOUNT` flag and `returnRefundAccount` field. Refer to [Domestic Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-initiation-consent-request/index.md) for details. * The Domestic Payment Credit Transfer response has been updated to include support for refund account details. Refer to [Domestic Payment Credit Transfer](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-credit-transfer-initiation-request/index.md) for details. * The Get Domestic Payment Status response has been updated to include support for refund account details. Refer to [Get Domestic Payment Status](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/get-payment-status-request/index.md) for details. * The Cross-border Payment Initiation Consent request and responses have been updated to include support for the `RETURN_REFUND_ACCOUNT` flag and `returnRefundAccount` field. * The Cross-border Payment Credit Transfer response has been updated to include support for refund account details. * The Cross-border Get Payment Status response has been updated to include support for refund account details. ## Release 1.30.0 Sandbox {#release-1300-sandbox} Release 1.30.0 provides enhancements to the API Specification and Sandbox testing capabilities. ### Release enhancements {#release-enhancements-39} #### Sandbox data sets enhancements {#sandbox-data-sets-enhancements} ##### IBANs returned for all accounts for Hungarian ASPSPs {#ibans-returned-for-all-accounts-for-hungarian-aspsps} Data sets corresponding to Hungarian ASPSPs have been updated to return IBANs in the `accountNumber` field for all accounts. IBANs now correspond to the format accepted in Hungary, enabling end-to-end account information service testing to be performed. ##### ASPSPs wth CMA9 profile to receive IBANs in the required country format {#aspsps-wth-cma9-profile-to-receive-ibans-in-the-required-country-format} Updates were made to data sets corresponding to ASPSPs with CMA9 Profile to ensure IBANs returned in refund account details correspond to the required country format. #### AIS enhancements {#ais-enhancements-20} ##### Data Type updated to String for the schemeName field {#data-type-updated-to-string-for-the-schemename-field-1} The Data Type for the `schemeName` field has been updated from Enum to String for the Get List of Accounts and Get Account Details responses. ##### aspsps object updated to Mandatory for the Get List of ASPSPs response {#aspsps-object-updated-to-mandatory-for-the-get-list-of-aspsps-response-2} The conditionality of the `aspsps` object in the Get List of ASPSPs response has been updated from Optional to Mandatory, as it is always returned to TPPs. ##### Filtering transactions by date for the Get Account Transaction request {#filtering-transactions-by-date-for-the-get-account-transaction-request-1} Updates have been made to enable TPPs to filter transactions by date using the `bookingDateFrom` and `bookingDateTo` fields when sending requests to ASPSPs with NextGenPSD2 and STET API profiles. ##### Customization enabled for the consent validity period {#customization-enabled-for-the-consent-validity-period-1} A new `validUntilDateTime`field has been added to the Account Information Consent request to enable TPPs to customize the consent expiration date and time. TPPs can access the AIS data until the expiration expires. This field is applicable for Polish API, CMA9, NextGenPSD2 and STET API Profiles. #### PIS enhancements {#pis-enhancements-16} ##### aspsps object updated to Mandatory for the Get List of ASPSPs response {#aspsps-object-updated-to-mandatory-for-the-get-list-of-aspsps-response-3} The conditionality of the `aspsps` object in the Get List of ASPSPs response has been updated from Optional to Mandatory, as it is always returned to TPPs. ##### CMA9 Cross-border Payment Initiation Consent updates for debtor account details {#cma9-cross-border-payment-initiation-consent-updates-for-debtor-account-details} * A new `RETURN_REFUND_ACCOUNT` flag is available for TPP's to provide in Cross-border Payment Initiation Consent requests. It should be included when the PSU has provided consent to the TPP to receive and store debtor account details, which can be used to complete a reverse payment. When the `RETURN_REFUND_ACCOUNT` flag is provided in the consent request, TPPs will receive `returnRefundAccount = 'True'` in the consent response. * A new `returnRefundAccount` field is available in responses to specify consent provided by the PSU to TPP to share debtor account details. This information flags to the TPP that debtor account details will be available from the ASPSP in response to subsequent calls to Credit transfer and Payment status endpoints. ##### CMA9 Cross-border Payment Initiation Credit Transfer response updated to include debtor account details {#cma9-cross-border-payment-initiation-credit-transfer-response-updated-to-include-debtor-account-details} The following parameters can be provided to the TPP when the TPP originally provided the `RETURN_REFUND_ACCOUNT` flag on the Cross-border Payment Initiation Consent Request. The TPP can use this data to submit a reversal of the original payment on behalf of the PSU. * `refundAccount` - Object containing the refund account details (scheme name, account identification number) * `refundAgent` - Object containing the refund agent details (clearing system identification, member identification) ##### CMA9 Cross-border Get Payment Status response updated to include debtor account details {#cma9-cross-border-get-payment-status-response-updated-to-include-debtor-account-details} The following parameters can be provided to the TPP when the TPP originally provided the `RETURN_REFUND_ACCOUNT` flag on the Cross-border Payment Initiation Consent Request. The TPP can use this data to submit a reversal of the original payment on behalf of the PSU. * `refundAccount` - Object containing the refund account details (scheme name, account identification number) * `refundAgent` - Object containing the refund agent details (clearing system identification, member identification) ### API enhancements {#api-enhancements-21} #### AIS enhancements {#ais-enhancements-21} * The `validUntilDateTime`field has been added to the Account Information Consent request to enable TPPs to customize the consent expiration date and time. Refer to [Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/account-information-consent/index.md) for details. * The Data Type for the `schemeName` field has been updated from Enum to String for the Get List of Accounts and Get Account Details responses. Refer to [Get List of Accounts](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-list-accounts/index.md) and [Get Account Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-details/index.md)for details. * The conditionality of the `aspsps` object in the Get List of ASPSPs response has been updated from Optional to Mandatory. Refer to [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) for details. * TPPs can now filter transactions by date using the `bookingDateFrom` and `bookingDateTo` fields when sending requests to ASPSPs with NextGenPSD2 and STET API profiles. Refer to [Get Account Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) for details. #### PIS enhancements {#pis-enhancements-17} * The Cross-border Payment Initiation Consent request and responses have been updated to include support for the `RETURN_REFUND_ACCOUNT` flag and `returnRefundAccount` field. * The Cross-border Payment Credit Transfer response has been updated to include support for refund account details. * The Cross-border Get Payment Status response has been updated to include support for refund account details. ### Sandbox data sets spreadsheets {#sandbox-data-sets-spreadsheets-1} No changes. ## Release 1.29.0 Production {#release-1290-production} Release 1.29.0 provides enhancements to the API Specification, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-40} #### AIS enhancements {#ais-enhancements-22} ##### Get Account Details response updated {#get-account-details-response-updated} The `HolderAddress` object's `Country` field has been updated to be optionally returned for all API profiles. #### PIS enhancements {#pis-enhancements-18} ##### Domestic Payment Initiation Consent updates for debtor account details {#domestic-payment-initiation-consent-updates-for-debtor-account-details} * A new `RETURN_REFUND_ACCOUNT` flag is available for TPP's to provide in requests. It should be included when the PSU has provided consent to the TPP to receive and store debtor account details, which can be used to complete a reverse payment. * A new `returnRefundAccount` field is available in responses to specify consent provided by the PSU to TPP to share debtor account details. This information flags to the TPP that debtor account details will be available from the ASPSP in response to subsequent calls to Credit transfer and Payment status endpoints. ##### Domestic Payment Credit Transfer response updated to include debtor account details {#domestic-payment-credit-transfer-response-updated-to-include-debtor-account-details} The following parameters can be provided to the TPP when the TPP originally provided the `RETURN_REFUND_ACCOUNT` flag on the Payment Initiation Consent Request. The TPP can use this data to submit a reversal of the original payment on behalf of the PSU. * `refundAccount` - Object containing the refund account details (scheme name, account identification number) * `refundAgent` - Object containing the refund agent details (clearing system identification, member identification) ##### Get Domestic Payment Status response updated to include debtor account details {#get-domestic-payment-status-response-updated-to-include-debtor-account-details} The following parameters can be provided to the TPP when the TPP originally provided the `RETURN_REFUND_ACCOUNT` flag on the Payment Initiation Consent Request. The TPP can use this data to submit a reversal of the original payment on behalf of the PSU. * `refundAccount` - Object containing the refund account details (scheme name, account identification number) * `refundAgent` - Object containing the refund agent details (clearing system identification, member identification) ### API enhancements {#api-enhancements-22} #### AIS enhancements {#ais-enhancements-23} None. #### PIS enhancements {#pis-enhancements-19} * The Domestic Payment Initiation Consent request and responses has been updated to include support for the `RETURN_REFUND_ACCOUNT` flag and `returnRefundAccount` field. Refer to [Domestic Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-initiation-consent-request/index.md) for details. * The Domestic Payment Credit Transfer response has been updated to include support for refund account details. Refer to [Domestic Payment Credit Transfer](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-credit-transfer-initiation-request/index.md) for details. * The Get Domestic Payment Status response has been updated to include support for refund account details. Refer to [Get Domestic Payment Status](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/get-payment-status-request/index.md) for details. ## Release 1.29.0 Sandbox {#release-1290-sandbox} Release 1.29.0 provides enhancements to the API Specification and Sandbox testing capabilities. ### Release enhancements {#release-enhancements-41} #### Additional Sandbox bank for testing SEPA payment statuses {#additional-sandbox-bank-for-testing-sepa-payment-statuses} An additional Sandbox bank has been added to enable Sandbox testing for various SEPA payment statuses: * Name - Europium Bank * API Profile - NextGenPSD2 * Country - EE (Estonia) #### AIS enhancements {#ais-enhancements-24} ##### Get Account Details response updated {#get-account-details-response-updated-1} The `HolderAddress` object's `Country` field has been updated to be optionally returned for all API profiles. #### PIS enhancements {#pis-enhancements-20} ##### Domestic Payment Initiation Consent updates for debtor account details {#domestic-payment-initiation-consent-updates-for-debtor-account-details-1} * A new `RETURN_REFUND_ACCOUNT` flag is available for TPP's to provide in requests. It should be included when the PSU has provided consent to the TPP to receive and store debtor account details, which can be used to complete a reverse payment. * A new `returnRefundAccount` field is available in responses to specify consent provided by the PSU to TPP to share debtor account details. This information flags to the TPP that debtor account details will be available from the ASPSP in response to subsequent calls to Credit transfer and Payment status endpoints. ##### Domestic Payment Credit Transfer response updated to include debtor account details {#domestic-payment-credit-transfer-response-updated-to-include-debtor-account-details-1} The following parameters can be provided to the TPP when the TPP originally provided the `RETURN_REFUND_ACCOUNT` flag on the Payment Initiation Consent Request. The TPP can use this data to submit a reversal of the original payment on behalf of the PSU. * `refundAccount` - Object containing the refund account details (scheme name, account identification number) * `refundAgent` - Object containing the refund agent details (clearing system identification, member identification) ##### Get Domestic Payment Status response updated to include debtor account details {#get-domestic-payment-status-response-updated-to-include-debtor-account-details-1} The following parameters can be provided to the TPP when the TPP originally provided the `RETURN_REFUND_ACCOUNT` flag on the Payment Initiation Consent Request. The TPP can use this data to submit a reversal of the original payment on behalf of the PSU. * `refundAccount` - Object containing the refund account details (scheme name, account identification number) * `refundAgent` - Object containing the refund agent details (clearing system identification, member identification) ### API enhancements {#api-enhancements-23} #### AIS enhancements {#ais-enhancements-25} None. #### PIS enhancements {#pis-enhancements-21} * The Domestic Payment Initiation Consent request and responses has been updated to include support for the `RETURN_REFUND_ACCOUNT` flag and `returnRefundAccount` field. Refer to [Domestic Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-initiation-consent-request/index.md) for details. * The Domestic Payment Credit Transfer response has been updated to include support for refund account details. Refer to [Domestic Payment Credit Transfer](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-credit-transfer-initiation-request/index.md) for details. * The Get Domestic Payment Status response has been updated to include support for refund account details. Refer to [Get Domestic Payment Status](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/get-payment-status-request/index.md) for details. ### Sandbox scenarios {#sandbox-scenarios-3} No changes. ### Sandbox data sets spreadsheets {#sandbox-data-sets-spreadsheets-2} The Sandbox Data Sets spreadsheets have been updated for the 1.29.0 release as follows: * AIS * STET API Profile changes have been made to include two new `TypeofRelation` values have been added to identify the type of relationship between the PSU and the account for Get Accounts and Get Account Details * PIS * Nineteen amount-driven scenarios have been included for Sandbox testing of SEPA payment statuses Refer to OB_Connect_Sandbox_DataSets_R1-29-0.xlsx in [Specification Release Documentation](https://developer.mastercard.com/open-banking-connect/documentation/specification-release-documentation/index.md) for the current data set. ## Release 1.28.0 Production {#release-1280-production} Release 1.28.0 provides enhancements to the API Specification, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-42} #### AIS enhancements {#ais-enhancements-26} ##### Additional PSU identifier for AIS endpoints {#additional-psu-identifier-for-ais-endpoints} The optional field `psuTppCustomerId` has been added to specific AIS request messages to enable TPPs to identify their PSU customers. This is intended for future use with Active User billing. Note: `psuTppCustomerId` has been added to all AIS endpoints except Get Status of Inbound API and AIS Connectors, Exchange the PSU Authorization for Access Consent, and AIS - Get LIst of ASPSPs. #### PIS enhancements {#pis-enhancements-22} ##### Inclusion of original payment information for Credit Transfer and Get Payment Status {#inclusion-of-original-payment-information-for-credit-transfer-and-get-payment-status} The following fields have been added to the Credit Transfer and Get Payment Status endpoints for all API standards: * `originalPaymentStatus` - Status of the payment returned by ASPSP * `originalPaymentID` - Payment identification returned by ASPSP ##### Creditor agent name details for SEPA Payment Initiation requests {#creditor-agent-name-details-for-sepa-payment-initiation-requests} The `creditorAgentName`field has been added to SEPA Payment Initiation requests for STET and NextGenPSD2 API profiles. ##### Payment ID included in Get Payment Status message responses {#payment-id-included-in-get-payment-status-message-responses} The `paymentId`field has been added to Get Payment Status message responses for all API profiles. #### Response and error codes {#response-and-error-codes-10} The 400 FORMAT_ERROR has been introduced to indicate when `debtorAccount` needs to be provided when `debtorName` is sent in Domestic Consent requests. ### API enhancements {#api-enhancements-24} #### AIS enhancements {#ais-enhancements-27} The following requests have have been updated to include the optional field `psuTppCustomerId`: * [Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/account-information-consent/index.md) * [Get List of Accounts](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-list-accounts/index.md) * [Get Account Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-details/index.md) * [Get Account Balances](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-balances/index.md) * [Get Account Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) * [Get Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) * [Get Account Standing Orders](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-standing-orders/index.md) * [Delete Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/delete-ais-consent/index.md) #### PIS enhancements {#pis-enhancements-23} * The following responses have been updated to include the `originalPaymentStatus` and `originalPaymentId` fields: * [SEPA Payment Credit Transfer Initiation](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-credit-transfer-initiation-request/index.md) * [SEPA Get Payment Status](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-get-payment-status-request/index.md) * Cross-border Payment Credit Transfer Initiation * Cross-border Get Payment Status * The SEPA Payment Initiation Consent request has been updated to include the `creditorAgentName`field. * The Domestic Payment Initiation Consent request has been updated to include an additional 400 FORMAT_ERROR to indicate `debtorAccount` needs to be provided when `debtorName` is included in the request. Refer to Domestic Payment Initiation Consent request's [Feature specific error codes](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-initiation-consent-request/index.md) for further information. * The `paymentId`field has been added to all Get Payment Status message responses. * [Get Domestic Payment Status](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/get-payment-status-request/index.md) * [Get SEPA Payment Status](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-get-payment-status-request/index.md) * Get Cross-border Payment Status ## Release 1.28.0 Sandbox {#release-1280-sandbox} Release 1.28.0 provides enhancements to the API Specification and Sandbox testing capabilities. ### Release enhancements {#release-enhancements-43} #### AIS enhancements {#ais-enhancements-28} ##### Additional account details in Get Account Details responses from ASPSPs with Polish API profile {#additional-account-details-in-get-account-details-responses-from-aspsps-with-polish-api-profile} The `auxData` field is now included in the Get Account Details response to enable ASPSPs with Polish API profile to include additional account details. ##### Additional PSU identifier for AIS endpoints {#additional-psu-identifier-for-ais-endpoints-1} The optional field `psuTppCustomerId` has been added to specific AIS request messages to enable TPPs to identify their PSU customers. This is intended for future use with Active User billing. Note: `psuTppCustomerId` has been added to all AIS endpoints except Get Status of Inbound API and AIS Connectors, Exchange the PSU Authorization for Access Consent, and AIS - Get LIst of ASPSPs. #### PIS enhancements {#pis-enhancements-24} ##### Inclusion of original payment information for Credit Transfer and Get Payment Status {#inclusion-of-original-payment-information-for-credit-transfer-and-get-payment-status-1} The following fields have been added to the Credit Transfer and Get Payment Status endpoints for all API standards: * `originalPaymentStatus` - Status of the payment returned by ASPSP * `originalPaymentID` - Payment identification returned by ASPSP ##### Creditor agent name details for SEPA Payment Initiation requests {#creditor-agent-name-details-for-sepa-payment-initiation-requests-1} The `creditorAgentName`field has been added to SEPA Payment Initiation requests for STET and NextGenPSD2 API profiles. ##### Payment ID included in Get Payment Status message responses {#payment-id-included-in-get-payment-status-message-responses-1} The `paymentId`field has been added to Get Payment Status message responses for all API profiles. #### Response and error codes {#response-and-error-codes-11} The 400 FORMAT_ERROR has been introduced to indicate when `debtorAccount` needs to be provided when `debtorName` is sent in Domestic Consent requests. ### API enhancements {#api-enhancements-25} #### AIS enhancements {#ais-enhancements-29} The following requests have have been updated to include the optional field `psuTppCustomerId`: * [Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/account-information-consent/index.md) * [Get List of Accounts](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-list-accounts/index.md) * [Get Account Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-details/index.md) * [Get Account Balances](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-balances/index.md) * [Get Account Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) * [Get Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) * [Get Account Standing Orders](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-standing-orders/index.md) * [Delete Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/delete-ais-consent/index.md) #### PIS enhancements {#pis-enhancements-25} * The following responses have been updated to include the `originalPaymentStatus` and `originalPaymentId` fields: * [SEPA Payment Credit Transfer Initiation](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-credit-transfer-initiation-request/index.md) * [SEPA Get Payment Status](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-get-payment-status-request/index.md) * Cross-border Payment Credit Transfer Initiation * Cross-border Get Payment Status * The SEPA Payment Initiation Consent request has been updated to include the `creditorAgentName`field. * The Domestic Payment Initiation Consent request has been updated to include an additional 400 FORMAT_ERROR to indicate `debtorAccount` needs to be provided when `debtorName` is included in the request. Refer to Domestic Payment Initiation Consent request's [Feature specific error codes](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-initiation-consent-request/index.md) for further information. * The `paymentId`field has been added to all Get Payment Status message responses. * [Get Domestic Payment Status](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/get-payment-status-request/index.md) * [Get SEPA Payment Status](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-get-payment-status-request/index.md) * Get Cross-border Payment Status ### Sandbox scenarios {#sandbox-scenarios-4} Open Banking Connect Sandbox data sets were updated for ASPSPs supporting Czech and Slovak API profiles, to be synchronized with ASPSPs supporting NextGenPSD2 API profile. * The following fields were added to the Get Account and Get Account Details requests: * Account Holder Name * Account Number * Account Scheme * The following fields were added to the Get Account Transactions and Get Account Transaction Details requests: * Sender Name * Sender Account Number Scheme * Sender Account Number * Recipient Name * Recipient Account Number Scheme * Recipient Account Number ### Sandbox data sets spreadsheets {#sandbox-data-sets-spreadsheets-3} The Sandbox data sets spreadsheets have been updated to include support for the 1.28.0 release. Refer to OB_Connect_Sandbox_DataSets_R1-28-0.xlsx in [Specification Release Documentation](https://developer.mastercard.com/open-banking-connect/documentation/specification-release-documentation/index.md) for the current data set. ## Release 1.27.1 Production {#release-1271-production} Release 1.27.1 provides enhancements to the API Specification, including scheduled changes and improvements. Note: Additionally, minor changes have been made to the specification, sandbox scenarios and data sets to align with the YAML files. ### Release enhancements {#release-enhancements-44} #### AIS enhancements {#ais-enhancements-30} ##### Creditor and Debtor details in responses from ASPSPs with STET API profile {#creditor-and-debtor-details-in-responses-from-aspsps-with-stet-api-profile} Enhancements have been made to enable TPPs to receive debtor and creditor details in responses for Get Account Transactions and Get Account Transaction Details requests from ASPSPs with STET API profile. The following fields are now received in Get Account Transactions and Get Account Transaction Details responses: * senderName * senderAccountNumber * recipientName * recipientAccountNumber * senderAccountNumberScheme * recipientAccountNumberScheme ##### Additional account details in Get Account Details responses from ASPSPs with Polish API profile {#additional-account-details-in-get-account-details-responses-from-aspsps-with-polish-api-profile-1} The `auxData` field is now included in the Get Account Details response to enable additional account details returned ASPSPs with Polish API profile to be included. #### PIS enhancements {#pis-enhancements-26} None. ### API enhancements {#api-enhancements-26} #### AIS enhancements {#ais-enhancements-31} The `auxData` field has been added to the Get Account Details response to enable ASPSPs with Polish API profile to include additional account details. Refer to [Get Account Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-details/index.md) for further information. #### PIS enhancements {#pis-enhancements-27} None. ## Release 1.27.1 Sandbox {#release-1271-sandbox} Release 1.27.1 provides enhancements to the API Specification and Sandbox testing capabilities. Note: Additionally, minor changes have been made to the specification, sandbox scenarios and data sets to align with the YAML files. ### Release enhancements {#release-enhancements-45} #### AIS enhancements {#ais-enhancements-32} ##### auxData in responses for Get Account Details requests to ASPSP sandboxes {#auxdata-in-responses-for-get-account-details-requests-to-aspsp-sandboxes} auxData is available in responses for Get Account Details requests to ASPSP sandboxes (external to Mastercard) to enable ASPSPs with Polish API profile to include additional account details. Note: Scenarios related to auxData are not currently available in the Open Banking Connect sandbox. ##### Creditor and Debtor details in responses from ASPSPs with STET API profile {#creditor-and-debtor-details-in-responses-from-aspsps-with-stet-api-profile-1} Enhancements have been made to enable TPPs to receive debtor and creditor details in responses for Get Account Transactions and Get Account Transaction Details requests from ASPSPs with STET API Profile. The following fields are now received in Get Account Transactions and Get Account Transaction Details responses: * senderName * senderAccountNumber * recipientName * recipientAccountNumber * senderAccountNumberScheme * recipientAccountNumberScheme #### PIS enhancements {#pis-enhancements-28} None. ### API enhancements {#api-enhancements-27} #### AIS enhancements {#ais-enhancements-33} None. #### PIS enhancements {#pis-enhancements-29} None. ## Release 1.27.0 Production {#release-1270-production} Release 1.27.0 provides enhancements to the API Specification, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-46} #### AIS enhancements {#ais-enhancements-34} ##### Original request information included in all responses {#original-request-information-included-in-all-responses} The `originalRequestInfo` object and `xRequestId` field are now mandatory for all AIS endpoints responses. This ensures that the original request information is returned to TPPs. ##### Maximum records per page set for Get List of ASPSPs {#maximum-records-per-page-set-for-get-list-of-aspsps} The following rules have been applied to Get List of ASPSPs requests to limit the number of records returned per page: * The page size defaults to 50 records per page when no page size is specified. * An error is returned when a page size greater than 50 is specified. * The page size returns the number of records per page specified by the TPP, where the number specified is 50 or less. #### PIS enhancements {#pis-enhancements-30} ##### HSBC limit on characters for Creditor Account Name for Domestic Payments {#hsbc-limit-on-characters-for-creditor-account-name-for-domestic-payments} Open Banking Connect has been updated to truncate the Creditor Account Name for Domestic Payments to HSBC Business. This is to align with HSBC's limitation of 18 characters on Creditor Account Name for Domestic Payments and to avoid unnecessary declines. ##### SEPA Instant Payments for ASPSPs with NextGenPSD2 API profile {#sepa-instant-payments-for-aspsps-with-nextgenpsd2-api-profile} SEPA Instant Payments have been enabled for ASPSPs with NextGenPSD2 API profile. Note: The scope is currently limited to Single Immediate Payments. ##### Idempotency conditions on Domestic, SEPA and Cross-border Credit Transfer requests {#idempotency-conditions-on-domestic-sepa-and-cross-border-credit-transfer-requests} Idempotency conditions on Domestic, SEPA and Cross-border Credit Transfer requests have been amended to enable TPPs to resubmit authorization codes without receiving an error message where the 500 response error had the recoverable flag set to True. ##### Payment status updates {#payment-status-updates} The Payment status of 'RCVD' (Received) for an Original Payment Status of 'ACWP' (AcceptedWithoutPosting) has been replaced with 'ACSC' (AcceptedSettlementCompleted) for clarity in the following requests: * CMA9 Domestic Credit Transfer * CMA9 Domestic Get Payment Status ##### debtorName field included for Domestic Payment Initiation Consent requests {#debtorname-field-included-for-domestic-payment-initiation-consent-requests} The `debtorName` field has been added to Domestic Payment Initiation Consent requests to support TPP requests to CMA9, Polish, NextGenPSD2 and STET API profiles. As a result, Domestic Payment Initiation Consent requests will not be rejected because of missing debtor name data. Tip: In order to avoid rejections, provide debtor account data when including debtorName in the request for domestic payment initiation Note: DebtorName is mandatory for Domestic Payment Initiation Consent requests to the Hungarian NextGenPSD2 ASPSPs "K\&H" and "ERSTE". ### API enhancements {#api-enhancements-28} #### Response and error codes {#response-and-error-codes-12} * The 500 Internal_Error general reason code has been enhanced to refer to the capability to resubmit payment requests where the recoverable flag set to True. Refer to [Response and Error Codes](https://developer.mastercard.com/open-banking-connect/documentation/response-and-error-codes/index.md) for details. * A specific 400 reason code for Get List of ASPSPs has been added to inform TPPs when a page record limit greater than the maximum allowed 50 has been entered. Refer to [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) for details. #### AIS enhancements {#ais-enhancements-35} * The Delete Account Information Consent request endpoint description has been updated to correspond to the implementation on the connectivity partner's side. Refer to Account Information Consent Deletion\](/documentation/aisfeatures/delete-ais-consent/) for details. * The `limit` field for the Get List of ASPSPs request has been updated to include the limit of 50 on records returned per page. Refer to [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) for details. * The `originalRequestInfo` object and `xRequestId` field have been marked as mandatory for the Get Account Standing Orders request. Refer to [Get Account Standing Orders](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-standing-orders/index.md) for details. #### PIS enhancements {#pis-enhancements-31} * The `debtorName` field has been added to Domestic Payment Initiation Consent requests to support TPP requests to CMA9, Polish, NextGenPSD2 and STET API profiles. Refer to [Domestic Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-initiation-consent-request/index.md) for details. * The `localInstrument` field has been updated for the SEPA Payment Initiation Consent Request to indicate support for SEPA Instant Payments for ASPSPs with NextGenPSD2 API profile. Refer to [SEPA Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-initiation-consent-request/index.md) for details. ## Release 1.27.0 Sandbox {#release-1270-sandbox} Release 1.27.0 provides enhancements to the API Specification and Sandbox testing capabilities. ### Release enhancements {#release-enhancements-47} #### AIS enhancements {#ais-enhancements-36} ##### Original request information included in all responses {#original-request-information-included-in-all-responses-1} The `originalRequestInfo` object and `xRequestId` field are now mandatory for all AIS endpoints responses. This ensures that the original request information is returned to TPPs. ##### Maximum records per page set for Get List of ASPSPs {#maximum-records-per-page-set-for-get-list-of-aspsps-1} The following rules have been applied to Get List of ASPSPs requests to limit the number of records returned per page: * The page size defaults to 50 records per page when no page size is specified. * An error is returned when a page size greater than 50 is specified. * The page size returns the number of records per page specified by the TPP, where the number specified is 50 or less. #### PIS enhancements {#pis-enhancements-32} ##### HSBC limit on characters for Creditor Account Name for Domestic Payments {#hsbc-limit-on-characters-for-creditor-account-name-for-domestic-payments-1} Open Banking Connect has been updated to truncate the Creditor Account Name for Domestic Payments to HSBC Business. This is to align with HSBC's limitation of 18 characters on Creditor Account Name for Domestic Payments and to avoid unnecessary declines. ##### SEPA Instant Payments for ASPSPs with NextGenPSD2 API profile {#sepa-instant-payments-for-aspsps-with-nextgenpsd2-api-profile-1} SEPA Instant Payments have been enabled for ASPSPs with NextGenPSD2 API profile. Note: The scope is currently limited to Single Immediate Payments. ##### Idempotency conditions on Domestic, SEPA and Cross-border Credit Transfer requests {#idempotency-conditions-on-domestic-sepa-and-cross-border-credit-transfer-requests-1} Idempotency conditions on Domestic, SEPA and Cross-border Credit Transfer requests have been amended to enable TPPs to resubmit authorization codes without receiving an error message where the 500 response error had the recoverable flag set to True. ##### Payment status updates {#payment-status-updates-1} The Payment status of 'RCVD' (Received) for an Original Payment Status of 'ACWP' (AcceptedWithoutPosting) has been replaced with 'ACSC' (AcceptedSettlementCompleted) for clarity in the following requests: * CMA9 Domestic Credit Transfer * CMA9 Domestic Get Payment Status ##### debtorName field included for Domestic Payment Initiation Consent requests {#debtorname-field-included-for-domestic-payment-initiation-consent-requests-1} The `debtorName` field has been added to Domestic Payment Initiation Consent requests to support TPP requests to CMA9, Polish, NextGenPSD2 and STET API profiles. As a result, Domestic Payment Initiation Consent requests will not be rejected because of missing debtor name data. Tip: In order to avoid rejections, provide debtor account data when including debtorName in the request for domestic payment initiation Note: DebtorName is mandatory for Domestic Payment Initiation Consent requests to the Hungarian NextGenPSD2 ASPSPs "K\&H" and "ERSTE". ### API enhancements {#api-enhancements-29} #### Response and error codes {#response-and-error-codes-13} * The 500 Internal_Error general reason code has been enhanced to refer to the capability to resubmit payment requests where the recoverable flag set to True. Refer to [Response and Error Codes](https://developer.mastercard.com/open-banking-connect/documentation/response-and-error-codes/index.md) for details. * A specific 400 reason code for Get List of ASPSPs has been added to inform TPPs when a page record limit greater than the maximum allowed 50 has been entered. Refer to [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) for details. #### AIS enhancements {#ais-enhancements-37} * The Delete Account Information Consent request endpoint description has been updated to correspond to the implementation on the connectivity partner's side. Refer to Account Information Consent Deletion\](/documentation/aisfeatures/delete-ais-consent/) for details. * The `limit` field for the Get List of ASPSPs request has been updated to include the limit of 50 on records returned per page. Refer to [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) for details. * The `originalRequestInfo` object and `xRequestId` field have been marked as mandatory for the Get Account Standing Orders request. Refer to [Get Account Standing Orders](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-standing-orders/index.md) for details. #### PIS enhancements {#pis-enhancements-33} * The `debtorName` field has been added to Domestic Payment Initiation Consent requests to support TPP requests to CMA9, Polish, NextGenPSD2 and STET API profiles. Refer to [Domestic Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-initiation-consent-request/index.md) for details. * The `localInstrument` field has been updated for the SEPA Payment Initiation Consent Request to indicate support for SEPA Instant Payments for ASPSPs with NextGenPSD2 API profile. Refer to [SEPA Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-initiation-consent-request/index.md) for details. ### Sandbox scenarios {#sandbox-scenarios-5} #### Sandbox data sets spreadsheets {#sandbox-data-sets-spreadsheets-4} The Sandbox data sets spreadsheets have been updated to include support for the 1.27.0 release. Refer to OB_Connect_Sandbox_DataSets_R1-27-0.xlsx in [Specification Release Documentation](https://developer.mastercard.com/open-banking-connect/documentation/specification-release-documentation/index.md) for the current data set. #### Account Information Service scenarios {#account-information-service-scenarios} The Delete Consent Request scenario's endpoint description has been updated to correspond to the implementation on the connectivity partner's side. Refer to the Delete Consent Request scenario in [Sandbox Scenarios](https://developer.mastercard.com/open-banking-connect/documentation/sandbox/sandbox-scenarios/index.md) for details. #### Payment Initiation Service scenarios {#payment-initiation-service-scenarios} The SEPA Payment Initiation Consent Request scenario has been updated to allow for an instance where an unsupported API profile is sed to request a SEPA instant payment. #### Account Information Service tutorial {#account-information-service-tutorial} None. ## Release 1.26.0 Production {#release-1260-production} Release 1.26.0 provides enhancements to the API Specification, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-48} #### AIS enhancements {#ais-enhancements-38} ##### TypeOfRelation field type update {#typeofrelation-field-type-update} The type and limitation details of the `typeOfRelation` field for the Get List of Accounts and Get Account Details requests have been amended to display as a String type and to support any values returned by ASPSPs. Previously, they displayed as an Enum type, which could result in values not displaying for the `typeOfRelation` field if an ASPSP returned an incorrect value set. #### PIS enhancements {#pis-enhancements-34} ##### SEPA instant payments {#sepa-instant-payments} Enhancement have been made to enable TPPs to initiate SEPA instant payments from ASPSPs with STET profile. ##### Idempotency conditions on Payment Credit Transfer requests {#idempotency-conditions-on-payment-credit-transfer-requests} Idempotency conditions on Payment Credit Transfer requests have been amended to enable TPPs to resubmit authorization codes without receiving an error message, in the rare event that the initial presentment of the authorization code fails. Note: This enhancement was technically live in Release 1.25.0, though the feature could not be fully used until additional development was completed. It can now be used as intended.
### API enhancements {#api-enhancements-30} #### AIS enhancements {#ais-enhancements-39} * The parameters of the `status` field for the following requests have been modified to be consistent with the codes available in the AIS YAML file: * Get Account Transaction request * Get Transaction Details request Refer to the [Get Accounts Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) and [Get Account Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) requests for details. * The type and limitation details of the `typeOfRelation` field for the following requests have been amended to display as a String type: * Get List of Accounts * Get Account Details Refer to the [Get List of Accounts](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-list-accounts/index.md) and [Get Account Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-details/index.md) requests for details. * Additional details have been added to the `psuAgent` field to clarify how it can be used for applicable AIS requests. Refer to the [Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/account-information-consent/index.md) request for an example. #### Response and error codes {#response-and-error-codes-14} * A dedicated INVALID_TOKEN general HTTP error response code has been added to inform TPPs when a token associated with a consent has expired. Refer to [Response and Error Codes](https://developer.mastercard.com/open-banking-connect/documentation/response-and-error-codes/index.md) for details. * TPPs now receive an appropriate error when submitting Cross Border payments to ASPSPs using the PolishAPI, as Cross Border payments are not supported. Refer to the NOT_ALLOWED general HTTP error response code in [Response and Error Codes](https://developer.mastercard.com/open-banking-connect/documentation/response-and-error-codes/index.md) for the error details. #### PIS enhancements {#pis-enhancements-35} * The `SEPA_INSTANT` parameter has been added to the Payment Initiation Consent request's `localInstrument` field to enable TPPs to initiate SEPA instant payments from ASPSPs with STET profile. Refer to the request body table in [SEPA Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-initiation-consent-request/index.md) for details. * The parameters of the `transactionStatus` field for the Domestic, SEPA and Cross-border (Payment Credit Transfer Initiation and Get Payment Status) endpoints have been modified to be consistent with the codes available in the PIS YAML file. * Additional details have been added to the `psuAgent` field to clarify how it can be used for applicable PIS requests. Refer to the [SEPA Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-initiation-consent-request/index.md) request for an example. ## Release 1.26.0 Sandbox {#release-1260-sandbox} Release 1.26.0 provides enhancements to the API Specification and Sandbox testing capabilities. ### Release enhancements {#release-enhancements-49} #### AIS enhancements {#ais-enhancements-40} ##### TypeOfRelation field type update {#typeofrelation-field-type-update-1} The type and limitation details of the `typeOfRelation` field for the Get List of Accounts and Get Account Details requests have been amended to display as a String type and to support any values that are returned by ASPSPs. Previously, they displayed as an Enum type, which could result in values not displaying for the `typeOfRelation` field if an ASPSP returned an incorrect value set. #### PIS enhancements {#pis-enhancements-36} ##### SEPA instant payments {#sepa-instant-payments-1} Enhancement have been made to enable TPPs to initiate SEPA instant payments from ASPSPs with STET profile. ##### Idempotency conditions on Payment Credit Transfer requests {#idempotency-conditions-on-payment-credit-transfer-requests-1} Idempotency conditions on Payment Credit Transfer requests have been amended to enable TPPs to resubmit authorization codes without receiving an error message, in the rare event that the initial presentment of the authorization code fails. Note: This enhancement was technically live in Release 1.25.0, though the feature could not be fully used until additional development was completed. It can now be used as intended.
### API enhancements {#api-enhancements-31} #### AIS enhancements {#ais-enhancements-41} * The parameters of the `status` field for the following requests have been modified to be consistent with the codes available in the AIS YAML file: * Get Account Transaction request * Get Transaction Details request Refer to the [Get Accounts Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) and [Get Account Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) requests for details. * The type and limitation details of the `typeOfRelation` field for the following requests have been amended to display as a String type: * Get List of Accounts * Get Account Details Refer to the [Get List of Accounts](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-list-accounts/index.md) and [Get Account Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-details/index.md) requests for details. * Additional details have been added to the `psuAgent` field to clarify how it can be used for applicable AIS requests. Refer to the [Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/account-information-consent/index.md) request for an example. #### PIS enhancements {#pis-enhancements-37} * The `SEPA_INSTANT` parameter has been added to the Payment Initiation Consent request's `localInstrument` field to enable TPPs to initiate SEPA instant payments from ASPSPs with STET profile. Refer to the request body table in [SEPA Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-initiation-consent-request/index.md) for details. * The parameters of the `transactionStatus` field for the Domestic, SEPA and Cross-border (Payment Credit Transfer Initiation and Get Payment Status) endpoints have been modified to be consistent with the codes available in the PIS YAML file. * Additional details have been added to the `psuAgent` field to clarify how it can be used for applicable PIS requests. Refer to the [SEPA Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-initiation-consent-request/index.md) request for an example. ### Sandbox scenarios {#sandbox-scenarios-6} #### Sandbox data sets spreadsheets {#sandbox-data-sets-spreadsheets-5} The Sandbox data sets spreadsheets have been updated to include support for the 1.26.0 release. Refer to OB_Connect_Sandbox_DataSets_R1-26-0.xlsx in [Specification Release Documentation](https://developer.mastercard.com/open-banking-connect/documentation/specification-release-documentation/index.md) for the current data set. #### Account Information Service scenarios {#account-information-service-scenarios-1} The HTTP Status for all 50x error codes have been updated to 500. #### Payment Initiation Service scenarios {#payment-initiation-service-scenarios-1} * Additional test scenarios have been added to support the testing of SEPA Instant Payments. Refer to the SEPA Payment Initiation Consent Request, SEPA Payment Credit Transfer Initiation Request and SEPA Get Payment Status Request scenarios in [Sandbox Scenarios](https://developer.mastercard.com/open-banking-connect/documentation/sandbox/sandbox-scenarios/index.md) for details. * The HTTP Status for all 50x error codes has been updated to 500. #### Account Information Service tutorial {#account-information-service-tutorial-1} None. ## Release 1.25.0 Production {#release-1250-production} Release 1.25.0 provides enhancements to the API Specification, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-50} #### AIS enhancements {#ais-enhancements-42} ##### PSU data authorization {#psu-data-authorization} Third Party Providers (TPPs) can now include the following PSU data in Exchange PSU Authorization for Access Consent requests to ASPSPs with PolishAPI profile: * psuIpAddress * psuAgent * isLivePsuRequest ##### Standing Order requests to ASPSPs with CMA9 profile {#standing-order-requests-to-aspsps-with-cma9-profile} The following enhancements have been made to support standing order requests to Account Servicing Payment Service Providers (ASPSPs) with CMA9 profile: * The Get Account Standing Orders request has been implemented to enable TPPs to obtain a list of standing order schedules from an ASPSP to be shared with a PSU. * TPPs can now specify an access permission keyword of 'standingorders' to the account/consents endpoint from the Get Account Information Consent request. * The capability for ASPSPs to return standing orders information is now available for the Get List of ASPSPs request. #### PIS enhancements {#pis-enhancements-38} ##### PSU data in SEPA requests {#psu-data-in-sepa-requests} The following requests have been enhanced to enable TPPs to include the PSU data fields `psuIpAddress`, `psuAgent` and `isLivePsuRequest`, in requests to ASPSPs with PolishAPI profile: * SEPA Payment Initiation Consent request * SEPA Payment Credit Transfer Initiation request * SEPA Get Payment Status request ##### Idempotency conditions on Payment Credit Transfer requests {#idempotency-conditions-on-payment-credit-transfer-requests-2} Idempotency conditions on Payment Credit Transfer requests have been amended to enable TPPs to resubmit authorization codes without receiving an error message, in the rare event that the initial presentment of the authorization code fails. ### Specification enhancements {#specification-enhancements} #### AIS enhancements {#ais-enhancements-43} * The Exchange PSU Authorization for Access Consent request has been enhanced to enable TPPs to include PSU data in requests to Polish ASPSPs. Refer to the request body table in [Exchange the PSU Authorization for Access Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/exchange-psu-consent/index.md) for details. * The Get Account Standing Orders request has been implemented to enable TPPs to obtain a list of standing order schedules from an ASPSP to be shared with a PSU. Refer to [Get Account Standing Orders](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-standing-orders/index.md) for details. * An access permission keyword of 'standingorders' has been added to the Get Account Information Consent request. Refer to [Get Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/account-information-consent/index.md) for details. * The Get List of ASPSPs request has been updated to include the capability for ASPSPs to return standing orders information. Refer to [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) for details. #### PIS enhancements {#pis-enhancements-39} * The SEPA Payment Initiation Consent request has been updated to include PSU data in requests to ASPSPs with PolishAPI profile. Refer to the request body table in [SEPA Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-initiation-consent-request/index.md) for details. * The SEPA Payment Credit Transfer Initiation request has been updated to include PSU data in requests to ASPSPs with PolishAPI profile. Refer to the request body table in [SEPA Payment Credit Transfer Initiation](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-credit-transfer-initiation-request/index.md) for details. * The SEPA Get Payment Status request has been updated to include PSU data in requests to ASPSPs with PolishAPI profile. Refer to the request body table in [SEPA Get Payment Status](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-get-payment-status-request/index.md) for details. ## Release 1.25.0 Sandbox {#release-1250-sandbox} Release 1.25.0 provides enhancements to the API Specification and Sandbox testing capabilities. ### Release enhancements {#release-enhancements-51} #### AIS enhancements {#ais-enhancements-44} ##### PSU data authorization {#psu-data-authorization-1} Third Party Providers (TPPs) can now include the following PSU data in Exchange PSU Authorization for Access Consent requests to ASPSPs with PolishAPI profile: * psuIpAddress * psuAgent * isLivePsuRequest ##### Standing Order requests to ASPSPs with CMA9 profile {#standing-order-requests-to-aspsps-with-cma9-profile-1} The following enhancements have been made to support standing order requests to Account Servicing Payment Service Providers (ASPSPs) with CMA9 profile: * The Get Account Standing Orders request has been implemented to enable TPPs to obtain a list of standing order schedules from an ASPSP to be shared with a PSU. * Additional test scenarios have been added to CMA9 pseudo ASPSPs to support the Get Account Standing Orders request. * TPPs can now specify an access permission keyword of 'standingorders' to the account/consents endpoint from the Get Account Information Consent request. * The capability for ASPSPs to return standing orders information is now available for the Get List of ASPSPs request. #### PIS enhancements {#pis-enhancements-40} ##### PSU data in SEPA requests {#psu-data-in-sepa-requests-1} The following requests have been enhanced to enable TPPs to include the PSU data fields `psuIpAddress`, `psuAgent` and `isLivePsuRequest`, in requests to ASPSPs with PolishAPI profile: * SEPA Payment Initiation Consent request * SEPA Payment Credit Transfer Initiation request * SEPA Get Payment Status request ##### Idempotency conditions on Payment Credit Transfer requests {#idempotency-conditions-on-payment-credit-transfer-requests-3} Idempotency conditions on Payment Credit Transfer requests have been amended to enable TPPs to resubmit authorization codes without receiving an error message, in the rare event that the initial presentment of the authorization code fails. ### Specification enhancements {#specification-enhancements-1} #### AIS enhancements {#ais-enhancements-45} * The Exchange PSU Authorization for Access Consent request has been enhanced to enable TPPs to include PSU data in requests to Polish ASPSPs. Refer to the request body table in [Exchange the PSU Authorization for Access Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/exchange-psu-consent/index.md) for details. * The Get Account Standing Orders request has been implemented to enable TPPs to obtain a list of standing order schedules from an ASPSP to be shared with a PSU. Refer to [Get Account Standing Orders](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-standing-orders/index.md) for details. * An access permission keyword of 'standingorders' has been added to the Get Account Information Consent request. Refer to [Get Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/account-information-consent/index.md) for details. * The Get List of ASPSPs request has been updated to include the capability for ASPSPs to return standing orders information. Refer to [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) for details. #### PIS enhancements {#pis-enhancements-41} * The SEPA Payment Initiation Consent request has been updated to include PSU data in requests to ASPSPs with PolishAPI profile. Refer to the request body table in [SEPA Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-initiation-consent-request/index.md) for details. * The SEPA Payment Credit Transfer Initiation request has been updated to include PSU data in requests to ASPSPs with PolishAPI profile. Refer to the request body table in [SEPA Payment Credit Transfer Initiation](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-payment-credit-transfer-initiation-request/index.md) for details. * The SEPA Get Payment Status request has been updated to include PSU data in requests to ASPSPs with PolishAPI profile. Refer to the request body table in [SEPA Get Payment Status](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/sepa-get-payment-status-request/index.md) for details. ### Sandbox scenarios {#sandbox-scenarios-7} #### Sandbox data sets spreadsheets {#sandbox-data-sets-spreadsheets-6} The Sandbox data sets spreadsheets have been updated to include support for testing standing order requests to ASPSPs with CMA9 profile. Refer to OB_Connect_Sandbox_DataSets_R1-25-0.xlsx in [Specification Release Documentation](https://developer.mastercard.com/open-banking-connect/documentation/specification-release-documentation/index.md) for details. #### Account Information Service scenarios {#account-information-service-scenarios-2} Additional test scenarios have been added to CMA9 pseudo ASPSPs to support the Get Account Standing Orders request. Refer to the Get Account Standing Orders request scenario in [Sandbox Scenarios](https://developer.mastercard.com/open-banking-connect/documentation/sandbox/sandbox-scenarios/index.md) for details. #### Payment Initiation Service scenarios {#payment-initiation-service-scenarios-2} None. #### Account Information Service tutorial {#account-information-service-tutorial-2} The Account Information Service tutorial has been updated to include information on the Get Account Standing Orders request. Refer to "section 5.8 Get Account Standing Orders request" of the OB_Connect_API_Sandbox_Scenarios_1-25-0_v1-0.pdf in [Specification Release Documentation](https://developer.mastercard.com/open-banking-connect/documentation/specification-release-documentation/index.md) for details. ## Release 1.24.0 Production {#release-1240-production} Release 1.24.0 provides enhancements to the API Specification, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-52} #### AIS enhancements {#ais-enhancements-46} The following AIS requests have been enhanced to enable TPPs to include PSU data in requests to ASPSPs with PolishAPI profile: * Account Information Consent request * Get List of Accounts request * Get Account Details request * Get Account Balances request * Get Account Transactions request * Get Transaction details request #### PIS enhancements {#pis-enhancements-42} * CMA9 Domestic Payments have been updated to enable OB Connect to interpret payment status as "PDNG" (Pending) rather than "ACSP" (AcceptedSettlementInProgress) when the original status received from the ASPSP is identified as "Pending". * The following PIS Domestic Payments requests have been enhanced to enable TPPs to include PSU data in requests to ASPSPs with PolishAPI profile: * Payment Initiation Consent request * Payment Credit Transfer Initiation request * Get Payment Status request ### Specification enhancements {#specification-enhancements-2} #### Response and error codes {#response-and-error-codes-15} * A dedicated INVALID_TOKEN general HTTP error response code has been added to inform TPPs when a token associated with a consent has expired. Refer to [Response and Error Codes](https://developer.mastercard.com/open-banking-connect/documentation/response-and-error-codes/index.md) for details. * TPPs now receive an appropriate error when submitting Cross Border payments to ASPSPs using the PolishAPI, as Cross Border payments are not supported. Refer to the NOT_ALLOWED general HTTP error response code in [Response and Error Codes](https://developer.mastercard.com/open-banking-connect/documentation/response-and-error-codes/index.md) for the error details. #### Account Information Service {#account-information-service} * The Account Information Consent request has been updated to include PSU data in requests to ASPSPs with PolishAPI profile in the following fields: * `isLivePsuRequest` * `psuIPAddress` * `psuAgent` Refer to the request body table in [Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/account-information-consent/index.md) for details. * The `psuAgent`field has been added to include additional PSU data in requests to ASPSPs with PolishAPI profile to the following requests: * Get Account Information Consent. Refer to the request body table in [Get Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/account-information-consent/index.md) for details. * Get List of Accounts request. Refer to the request body table in [Get List of Accounts](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-list-accounts/index.md) for details. * Get Account Details request. Refer to the request body table in [Get Account Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-details/index.md) for details. * Get Account Balances request. Refer to the request body table in [Get Account Balance](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-balances/index.md) for details. * Get Account Transactions request. Refer to the request body table in [Get Account Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) for details. * Get Transaction Details request. Refer to the request body table in [Get Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) for details. #### Payment Information Service {#payment-information-service} None. #### Payment Information Service - Domestic {#payment-information-service---domestic} * The Payment Initiation Consent request has been updated to include PSU data in requests to ASPSPs with PolishAPI profile in the following fields: * `isLivePsuRequest` * `psuIPAddress` * `psuAgent` Refer to the request body table in [Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-initiation-consent-request/index.md) for details. * The Payment Credit Transfer Initiation request has been updated to include PSU data in requests to ASPSPs with PolishAPI profile in the following fields: * `isLivePsuRequest` * `psuIPAddress` * `psuAgent` Refer to the request body table in [Payment Credit Transfer Initiation](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-credit-transfer-initiation-request/index.md) for details. * The Get Payment Status request has been updated to include PSU data in requests to ASPSPs with PolishAPI profile in the following fields: * `isLivePsuRequest` * `psuIPAddress` * `psuAgent` Refer to the request body table in [Get Payment Status](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/get-payment-status-request/index.md) for details. #### Payment Information Service - SEPA {#payment-information-service---sepa} None. #### Payment Information Service - Cross Border (International) Payment {#payment-information-service---cross-border-international-payment} None. ## Release 1.24.0 Sandbox {#release-1240-sandbox} Release 1.24.0 provides enhancements to the API Specification and Sandbox testing capabilities. ### Sandbox environment enhancements {#sandbox-environment-enhancements} #### New markets {#new-markets} Additional banks have been added in Sandbox to enable TPPs to test using Belgian and Luxembourg ASPSPs with NextGenPSD2 API profile. For the bank details, refer to OB_Connect_Sandbox_DataSets_R1-24-0.xlsx in [Specification Release Documentation](https://developer.mastercard.com/open-banking-connect/documentation/specification-release-documentation/index.md). #### New NextGenPSD2 testing scenarios {#new-nextgenpsd2-testing-scenarios} TPPs are now able to test the following scenarios with ASPSPs with NextGenPSD2 API profile in Sandbox: * Debtor Account Number Scheme = PAN and Debtor Account Number is in PAN format * Creditor Account Number Scheme = IBAN and Creditor Account Number is in IBAN format * Creditor Account Number Scheme = IBAN and Creditor Account Number is in IBAN format and Debtor Account Number is missing * Creditor Account Number Scheme = IBAN and Creditor Account Number is in IBAN format and Debtor Account Number Scheme is missing ### Release enhancements {#release-enhancements-53} #### AIS enhancements {#ais-enhancements-47} The following AIS requests have been enhanced to enable TPPs to include PSU data in requests to ASPSPs with PolishAPI profile: * Account Information Consent request * Get List of Accounts request * Get Account Details request * Get Account Balances request * Get Account Transactions request * Get Transaction details request #### PIS enhancements {#pis-enhancements-43} * CMA9 Domestic Payments have been updated to enable OB Connect to interpret payment status as "PDNG" (Pending) rather than "ACSP" (AcceptedSettlementInProgress) when the original status received from the ASPSP is identified as "Pending". * The following PIS Domestic Payments requests have been enhanced to enable TPPs to include PSU data in requests to ASPSPs with PolishAPI profile: * Payment Initiation Consent request * Payment Credit Transfer Initiation request * Get Payment Status request ### Specification enhancements {#specification-enhancements-3} #### Response and error codes {#response-and-error-codes-16} * A dedicated INVALID_TOKEN general HTTP error response code has been added to inform TPPs when a token associated with a consent has expired. Refer to [Response and Error Codes](https://developer.mastercard.com/open-banking-connect/documentation/response-and-error-codes/index.md) for details. * TPPs now receive an appropriate error when submitting Cross Border payments to ASPSPs using the PolishAPI, as Cross Border payments are not supported. Refer to the NOT_ALLOWED general HTTP error response code in [Response and Error Codes](https://developer.mastercard.com/open-banking-connect/documentation/response-and-error-codes/index.md) for the error details. #### Account Information Service {#account-information-service-1} * The Account Information Consent request has been updated to include PSU data in requests to ASPSPs with PolishAPI profile in the following fields: * `isLivePsuRequest` * `psuIPAddress` * `psuAgent` Refer to the request body table in [Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/account-information-consent/index.md) for details. * The `psuAgent`field has been added to include additional PSU data in requests to ASPSPs with PolishAPI profile to the following requests: * Get Account Information Consent. Refer to the request body table in [Get Account Information Consent](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/account-information-consent/index.md) for details. * Get List of Accounts request. Refer to the request body table in [Get List of Accounts](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-list-accounts/index.md) for details. * Get Account Details request. Refer to the request body table in [Get Account Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-details/index.md) for details. * Get Account Balances request. Refer to the request body table in [Get Account Balance](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-balances/index.md) for details. * Get Account Transactions request. Refer to the request body table in [Get Account Transactions](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) for details. * Get Transaction Details request. Refer to the request body table in [Get Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) for details. #### Payment Information Service {#payment-information-service-1} None. #### Payment Information Service - Domestic {#payment-information-service---domestic-1} * The Payment Initiation Consent request has been updated to include PSU data in requests to ASPSPs with PolishAPI profile in the following fields: * `isLivePsuRequest` * `psuIPAddress` * `psuAgent` Refer to the request body table in [Payment Initiation Consent](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-initiation-consent-request/index.md) for details. * The Payment Credit Transfer Initiation request has been updated to include PSU data in requests to ASPSPs with PolishAPI profile in the following fields: * `isLivePsuRequest` * `psuIPAddress` * `psuAgent` Refer to the request body table in [Payment Credit Transfer Initiation](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/payment-credit-transfer-initiation-request/index.md) for details. * The Get Payment Status request has been updated to include PSU data in requests to ASPSPs with PolishAPI profile in the following fields: * `isLivePsuRequest` * `psuIPAddress` * `psuAgent` Refer to the request body table in [Get Payment Status](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/get-payment-status-request/index.md) for details. #### Payment Information Service - SEPA {#payment-information-service---sepa-1} None. #### Payment Information Service - Cross Border (International) Payment {#payment-information-service---cross-border-international-payment-1} None. ## Release 1.23.1 Production {#release-1231-production} Release 1.23.1 provides enhancements to the API Specification, including scheduled changes and improvements. ### Release enhancements {#release-enhancements-54} #### AIS enhancements {#ais-enhancements-48} ##### Account transactions {#account-transactions} The responses to the TPPs sent by ASPSPs with NextGenPSD2 profile now include the transaction's sender name, sender scheme, recipient name and recipient scheme details in the following fields: * `senderName` * `senderAccountNumberScheme` * `recipientName` * `recipientAccountNumberScheme` ##### Account transaction details {#account-transaction-details} The responses to the TPPs sent by the ASPSPs with NextGenPSD2 profile now include the transaction's sender account and the recipient account details in the following fields: * `senderAccountNumberScheme` * `recipientAccountNumberScheme` ##### Get list of ASPSPs {#get-list-of-aspsps} The response provided to TPPs now supports pagination, as it can contain a significant number of records. #### Polish API profile {#polish-api-profile} SEPA Standing Orders requests sent by TPPs to the ASPSPs with PolishAPI profile will be rejected by OBC, as they are not currently supported. ### Specification enhancements {#specification-enhancements-4} #### Response and error codes {#response-and-error-codes-17} An additional NOT_ALLOWED general HTTP error response code has been added to inform users when a feature is not available for a given provider. Refer to [Response and Error Codes](https://developer.mastercard.com/open-banking-connect/documentation/response-and-error-codes/index.md) for details. #### Account Information Service {#account-information-service-2} * Two parameters have been added to the Get list of ASPSPs request body to support pagination in the response: * `limit` - sets the amount of ASPSPs to be loaded per page. * `offset` - indicates the ASPSP from which to load the list of ASPSPs. Refer to the request body table in [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) for details. * A new parameter has been added to the Get list of ASPSPs response body to support pagination. * `offset` - contains the ID of the ASPSP from which to request the next batch of ASPSPs. Refer to the response body table in [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) for details. * Two parameters have been added to the Get Account Transaction Details response body to include details of the scheme of both the sender's and receiver's account number. * `senderAccountNumberScheme` - name of the scheme which identifies the account number belonging to the sender/debtor of the transaction. * `recipientAccountNumberScheme` - name of the scheme which identifies the account number belonging to the recipient/creditor of the transaction. Refer to the response body table in [Get Account Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) for details. * New parameters have been added to the Get Account Transactions response body to include details of the sender name, sender account, recipient name and recipient account. * `senderName` - name of the debtor in current transaction (sender's name). * `recipientName` - name of the creditor in current transaction (recipient's name). * `senderAccountNumberScheme` - name of the scheme which identifies the account number belonging to the sender/debtor of the transaction. * `recipientAccountNumberScheme` - name of the scheme which identifies the account number belonging to the recipient/creditor of the transaction. Refer to the response body table in [Get Account Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions/index.md) for details. #### Payment Information Service {#payment-information-service-2} * Two parameters have been added to the Get list of ASPSPs request body to support pagination. * `limit` - sets the amount of ASPSPs to be loaded per page. * `offset` - indicates the ASPSP from which to load the next batch. Refer to the request body table in [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-list-of-aspsps/index.md) for details. * A new parameter has been added to the Get list of ASPSPs response body to support pagination. * `offset` - contains the ID of the ASPSP from which to request the next batch of ASPSPs. Refer to the response body table in [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-list-of-aspsps/index.md) for details. #### Payment Information Service - Domestic {#payment-information-service---domestic-2} None. #### Payment Information Service - SEPA {#payment-information-service---sepa-2} None. #### Payment Information Service - Cross Border (International) Payment {#payment-information-service---cross-border-international-payment-2} None. ## Release 1.23.1 Sandbox {#release-1231-sandbox} Release 1.23.1 provides additional hotfix enhancements to the Sandbox environment to align with functionality available in the Production environment. ### Release enhancements {#release-enhancements-55} #### AIS enhancements {#ais-enhancements-49} ##### Account transactions {#account-transactions-1} Responses to the TPPs sent by ASPSPs with NextGenPSD2 profile now include the transaction's sender name, sender account number, sender scheme, recipient name, recipient account number and recipient scheme details in the following fields: * `senderName` * `senderAccountNumber` * `senderAccountNumberScheme` * `recipientName` * `recipientAccountNumber` * `recipientAccountNumberScheme` #### PIS enhancements {#pis-enhancements-44} None. ### Specification enhancements {#specification-enhancements-5} #### Account Information Service {#account-information-service-3} ##### Account transactions {#account-transactions-2} * Additional parameters are available from the Get Account Transaction Details response body which include details of the sender name, sender account number, sender scheme, recipient name, recipient account number and recipient scheme details. * `senderName` - name of the debtor in current transaction (sender's name). * `senderAccountNumber` - unique and unambiguous identification for the account between the account owner and the account servicer * `senderAccountNumberScheme` - name of the scheme which identifies the account number belonging to the sender/debtor of the transaction. * `recipientName` - name of the creditor in current transaction (recipient's name). * `recipientAccountNumber` - unique and unambiguous identification for the account between the account owner and the account servicer. * `recipientAccountNumberScheme` - name of the scheme which identifies the account number belonging to the recipient/creditor of the transaction. Refer to the response body table in [Get Account Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) for details. #### Payment Information Service {#payment-information-service-3} None. #### Payment Information Service - Domestic {#payment-information-service---domestic-3} None. #### Payment Information Service - SEPA {#payment-information-service---sepa-3} None. #### Payment Information Service - Cross Border (International) Payment {#payment-information-service---cross-border-international-payment-3} None. ### Sandbox scenarios {#sandbox-scenarios-8} #### Sandbox data sets spreadsheets {#sandbox-data-sets-spreadsheets-7} None. #### Account Information Service scenarios {#account-information-service-scenarios-3} None. #### Payment Initiation Service scenarios {#payment-initiation-service-scenarios-3} None. ##### Account Information Service tutorial {#account-information-service-tutorial-3} The Account Information Service tutorial has been updated to include the `senderAccountNumber`, `recipientAccountNumber`, `senderName`, `senderAccountNumberScheme`, `recipientName` and `recipientAccountNumberScheme` fields in the Get transaction details response. Refer to "section 5.7 Get Transaction Details request" of the OB_Connect_API_Sandbox_Scenarios_1-23-1_v1-0.pdf in [Specification Release Documentation](https://developer.mastercard.com/open-banking-connect/documentation/specification-release-documentation/index.md) for details. ## Release 1.23.0 Sandbox {#release-1230-sandbox} Release 1.23.0 provides enhancements to the API Specification and Sandbox testing capabilities. ### Sandbox environment enhancements {#sandbox-environment-enhancements-1} The YAML files have been updated to version 1.23.0. ### Release enhancements {#release-enhancements-56} #### AIS enhancements {#ais-enhancements-50} ##### Transaction details {#transaction-details} The responses to the TPPs sent by the ASPSPs with NextGenPSD2 profile now include the transaction's sender account and the recipient account details in the following fields: * `senderAccountNumberScheme` * `recipientAccountNumberScheme` ##### Get list of ASPSPs {#get-list-of-aspsps-1} The response provided to TPPs now supports pagination, as it can contain a significant number of records. #### PolishAPI profile {#polishapi-profile} SEPA Standing Orders requests sent by TPPs to the ASPSPs with PolishAPI profile will be rejected by OBC, as they are not currently supported. #### Sandbox Reference Application {#sandbox-reference-application} A new "Select Type Of Redirect" drop-down option enables users to select parameters by which to format the URL for the redirect location specified by the TPP in the consent request. ### Specification enhancements {#specification-enhancements-6} #### Response and error codes {#response-and-error-codes-18} An additional NOT_ALLOWED general HTTP error response code has been added to inform users when a feature is not available for a given provider. Refer to [Response and Error Codes](https://developer.mastercard.com/open-banking-connect/documentation/response-and-error-codes/index.md) for details. #### Account Information Service {#account-information-service-4} * Two parameters have been added to the Get list of ASPSPs request body to support pagination in the response: * `limit` - sets the amount of ASPSPs to be loaded per page. * `offset` - indicates the ASPSP from which to load the list of ASPSPs. Refer to the request body table in [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) for details. * A new parameter has been added to the Get list of ASPSPs response body to support pagination. * `offset` - contains the ID of the ASPSP from which to request the next batch of ASPSPs. Refer to the response body table in [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/ais-get-list-of-aspsps/index.md) for details. * Two parameters have been added to the Get Account Transaction Details response body to include details of the scheme of both the sender's and receiver's account number. * `senderAccountNumberScheme` - name of the scheme which identifies the account number belonging to the sender/debtor of the transaction. * `recipientAccountNumberScheme` - name of the scheme which identifies the account number belonging to the recipient/creditor of the transaction. Refer to the response body table in [Get Account Transaction Details](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/get-account-transactions-details/index.md) for details. #### Payment Information Service {#payment-information-service-4} * Two parameters have been added to the Get list of ASPSPs request body to support pagination. * `limit` - sets the amount of ASPSPs to be loaded per page. * `offset` - indicates the ASPSP from which to load the next batch. Refer to the request body table in [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-list-of-aspsps/index.md) for details. * A new parameter has been added to the Get list of ASPSPs response body to support pagination. * `offset` - contains the ID of the ASPSP from which to request the next batch of ASPSPs Refer to the response body table in [Get List of ASPSPs](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/pis-get-list-of-aspsps/index.md) for details. #### Payment Information Service - Domestic {#payment-information-service---domestic-4} None. #### Payment Information Service - SEPA {#payment-information-service---sepa-4} None. #### Payment Information Service - Cross Border (International) Payment {#payment-information-service---cross-border-international-payment-4} None. ### Sandbox scenarios {#sandbox-scenarios-9} #### Sandbox data sets spreadsheets {#sandbox-data-sets-spreadsheets-8} None. #### Account Information Service scenarios {#account-information-service-scenarios-4} None. #### Payment Initiation Service scenarios {#payment-initiation-service-scenarios-4} ##### SEPA Payment Initiation Consent request {#sepa-payment-initiation-consent-request} * Scenarios for Standing Order requests from ASPSPs to TPPs with PolishAPI profiles have been removed, as they are not supported by Open Banking Connect. Refer to the SEPA Payments scenarios in [Sandbox Scenarios](https://developer.mastercard.com/open-banking-connect/documentation/sandbox/sandbox-scenarios/index.md) for the current scenarios. * Scenarios have been amended to return a response of `NOT_ALLOWED` for Standing Order requests from ASPSPs to TPPs with PolishAPI profiles. See scenarios 7 and 8 of the SEPA Payment Initiation Consent Request scenario in [Sandbox Scenarios](https://developer.mastercard.com/open-banking-connect/documentation/sandbox/sandbox-scenarios/index.md) for details. #### Account Information Service tutorial {#account-information-service-tutorial-4} The Account Information Service tutorial has been updated to include the `senderAccountNumberScheme` and `recipientAccountNumberScheme` fields in the Get transaction details response. Refer to "section 5.8 Get Transaction Details request" of the OB_Connect_API_Sandbox_Scenarios_1-23-0_v1-0.pdf in [Specification Release Documentation](https://developer.mastercard.com/open-banking-connect/documentation/specification-release-documentation/index.md) for details.