EzyPlatform now supports marking media as paymentRequired, with the status stored using the payment_required metadata key. This enables the platform to identify media that can only be accessed after a successful payment.

The MediaDetailsModel, AdminMediaDetailsResponse, and MediaDetailsResponse models now include the paymentRequired field, allowing both the Admin API and Web API to indicate whether a media item requires payment.

Both UpdateMediaRequest and UpdateMediaIncludeUrlRequest have been extended with two new fields: updatePaymentRequired and paymentRequired. These fields allow clients to update the payment-required status when editing media.

MediaService now provides saveMediaPaymentRequired(...) and isPaymentRequiredByMediaId(...) for storing and retrieving the payment-required status of media items.

The Admin Media Details dialog now includes a Payment Required checkbox, allowing administrators to enable or disable payment protection directly while editing media.

Website Settings now include the Allow users to update media payment requirement option. When disabled, the Web API automatically ignores any attempt by users to update the paymentRequired status.

When users download media through the Website, the platform now checks whether the media requires payment. If payment is required and the user is not authenticated, an authentication error is returned. If the user is authenticated, the platform publishes the validate_user_payment_required event, allowing external plugins or applications to implement their own payment validation logic before granting access.

MediaDownloadEvent now includes RequestArguments, giving event handlers additional request context when validating media access. A corresponding WebValidateUserPaymentRequiredEventSchemaFetcher has also been added to describe the schema of the validate_user_payment_required event.

Introduced the new SaveMetaRequest together with its converter to SaveMetaModel, providing a more consistent and extensible way to save metadata.

WebGlobalExceptionHandler now uses WebViews.redirectToLogin(...) for login redirection, ensuring a consistent authentication flow throughout the platform.

AdminMediaModelDecorator.decorate(...) has been optimized by loading the owner admin, owner user, and media duration in parallel, reducing response time when displaying media details.

Added translations for the new labels allow_user_update_media_payment_required and payment_required in Vietnamese, Japanese, Korean, and Chinese.

Updated com.mysql.cj.jdbc.Driver.acceptsURL(...) by removing the throws SQLException declaration. In addition, MediaControllerServiceTest has been updated to verify that the paymentRequired status is correctly returned when retrieving media details.