August Release

.NET 10 Upgrade

Upgrade Dotnet 8 to Dotnet 10

The Payments Service has been upgraded to the latest supported platform version. This is a behind-the-scenes improvement that helps keep the service secure, stable and supported while maintaining the same experience for end users.

· Upgraded the underlying Payments Service infrastructure to a newer supported platform version.

· Improved long-term security, performance and supportability of the service.

· Completed the upgrade without changing existing user-facing functionality.

Production issues

A data synchronisation issue affecting DBS information between systems has been resolved. This helps ensure referee DBS records remain aligned across FA platforms, improving data accuracy and reducing the risk of discrepancies.

· Fixed an issue where DBS information was not consistently synchronised between source systems and referee records.

· Improved accuracy and consistency of DBS data across referee-related services.

· Reduced the likelihood of mismatched DBS information appearing in FA systems.

Notifications Re-platforming 

Notifications Replatform - Referees Notifications

Additional referee registration notifications have been migrated onto the new notification platform. This ensures referees receive clear, timely updates about important changes to their registration status, improving communication and reducing uncertainty.

· Referees now receive confirmation when a registration refund has been processed.

· Referees are notified when an automatic renewal for the next season has been cancelled.

· Improved visibility of key registration events through consistent and reliable communications.

Azure Key Vault Implementation 

Improvements have been made to how sensitive system credentials and configuration information are managed within the Payments Service. This strengthens security, reduces operational risk and helps ensure the service remains reliable and compliant as it continues to support FA payment processes.

· Improved the security of the Payments Service by moving sensitive credentials into a central, protected location.

· Reduced the risk of unauthorised access to system configuration and connection details.

· Enhanced the reliability and maintainability of the service across development, test and production environments.