# June

## Markets & coverage

**Corporate signing baskets in Handelsbanken.** We've added support for signing baskets in Handelsbanken for the corporate scope. Signing baskets can now be created for both private and corporate accounts.

**ISO for Handelsbanken Norway.** We've expanded our coverage by adding Handelsbanken Norway to our ISO Payments rail. You can now initiate payments via ISO directly from Handelsbanken Norway accounts. 

**Payments in DNB Sweden.** We've added support for DNB Sweden to our PIS, meaning you can now initiate payments and signing baskets from Swedish accounts in DNB.

---

## Improvements

**Updated guides.** We've enhanced the guides in our documentation with clearer and more detailed steps and examples to provide in-depth explanations of our APIs. The documentation also includes new guides on more recently implemented features, ensuring that you have a comprehensive understanding of Open Payments' offerings and how to implement them.

**Harmonisation of payment statuses across Swedish banks.** We've harmonised payment statuses across Swedish banks to provide a more transparent, simplified and consistent experience. Users will now receive the same clear and standardized status for their payments regardless of the bank they are using. **Note:** This improvement is currently hidden behind a feature flag in order to give you time to test and implement these changes. The harmonised statuses can be enabled by including the `X-Feature-Flags` header with the value `new-statuses` in your requests. 

**Refactored remittance arrays.** We've refactored our remittance arrays for better structure and clarity. The `remittanceInformationStructuredArray` field now only contains structured remittance objects with a `typeCode`, and the `remittanceInformationUnstructuredArray` field only contains unstructured references without a `typeCode` (the `additionalRemittanceInformation` field is an exception and is still considered structured without a `typeCode`). A new validation rule also ensures that if a `typeCode` is provided but no corresponding number, the `referredDocumentInformation` array will be omitted from the `remittanceInformationStructuredArray` object. Additionally, we've removed the old solution for credit notes and now handle credit note functionality solely through the remittance arrays. For backward compatibility, the existing `remittanceInformationStructured` and `remittanceInformationUnstructured` fields will remain available, but we aim to phase them out over time. 

**Balance after transaction in Danske Bank.** The AIS now includes a `balanceAfterTransaction` field in transaction lists for Danske Bank on the last transaction entry of the day. 

---

## Fixes 

**Matching of paymentId in SEB.** We've fixed an issue where some SEB transactions would not be enriched with the matching `paymentId` in the AIS. 

**Matching of paymentId in Danske Bank.** We've fixed an issue where some Danske Bank transactions would not be enriched with the matching `paymentId` in the AIS. 

**Creditor address in Nordea.** We've fixed an issue in Nordea where cross-border payments via ISO would get rejected due to the creditor address not being included in the pain.001 file sent to the bank.

**Signing baskets stuck in Nordea.** We've fixed an issue where signing baskets would get stuck if a payment creation request for one of the payments in the basket failed. 

**Regulatory reporting in DNB.** We've fixed an issue where the `regulatoryReporting` object would not be included in our requests to DNB for `cross-border` payments.

**organisation numbers in KYC.** We've added support for different organisation number lengths in the KYC Service to fix an issue where it would not work in the Netherlands.