Upon pass the ui data type validation, it will issue request to web api. If the request is available and valid, it will proceed to the application/domain for business rules validation. Example, deposit amount has to be positive amount, deposit amount has to be multiple of 10.
Upon pass the application/domain for business rules validation, it will move to infrastructure layer where this will be entity validation using for example FluentValidation to ensure input data again has the valid data type and length defined in the EF Core entity model.
So basically there are 4 layers of validation? UI -> Web Api -> Application/Domain/Business -> Infrastructure (ie EF Core ORM).
Domain-Driven-Design is not needed here. So, I combine Application and Domain into same layer.
Added extra thoughts: I realize that FluentValidation has extension for Web Api which means that the flow is better imo.